2.6.6 kernel compile problem

lamnk · 05-25-2004, 09:42 AM

Hello,
I have some problem with compiling kernel 2.6.6 from Suse 9.1 . After reboot I cannot start some services and X window ( something like: blah blah ... read only file system ), then at log in I have this error:

Code:

FATAL: Cannot change permissions of TTY: Read only file system"

Maybe I have mounted hard drive read-only ? Anyone has idea about this ??

Thanks in advance.

marghorp · 05-25-2004, 09:57 AM

Boot into single mode.

Check the permissions of /

lamnk · 05-25-2004, 12:24 PM

just found this in boot.log

Code:

<5>RAMDISK: Compressed image found at block 0
<4>VFS: Mounted root (ext2 filesystem).
<5>ReiserFS: hda7: found reiserfs format "3.6" with standard journal
<5>ReiserFS: hda7: using ordered data mode
<5>ReiserFS: hda7: journal params: device hda7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
<5>ReiserFS: hda7: checking transaction log (hda7)
<5>ReiserFS: hda7: Using r5 hash to sort names
<4>VFS: Mounted root (reiserfs filesystem) readonly.
<5>Trying to move old root to /initrd ... failed
<5>Unmounting old root

then i ran fsck.reiserfs /dev/hda7 and the result is:

Code:

File system seems to be mounted read only

what should i do to make file system become read-write ??? I cannot chmod nor write anything .

marghorp · 05-25-2004, 01:57 PM

unmount it and mount it read-write

umount -a -t reiserfs
mount -t reiserfs /dev/hda7 /where/you/mount/it/ussually

This should give you read write access. If not, you should do the same, just add some more parameters.

lamnk · 05-25-2004, 03:02 PM

it doesn't work

when I un-mount and re-mount it always says hda7 already mounted.

/etc/mtab:

Code:

/dev/hda7 / reiserfs rw,alc,user_xattr 0 0

I think it's already read-write ?

marghorp · 05-25-2004, 03:03 PM

Try to make it into
/dev/hda7 / /reiserfs default 0 0

lamnk · 05-25-2004, 03:24 PM

the problem is: i cannot write any file !

(

marghorp · 05-25-2004, 03:40 PM

even in single mode? Booting into single mode in Red hat is simple. It is probably simple in suse too. Once in single mode, you should have all the privileges, and rw permissions.

lamnk · 05-25-2004, 05:39 PM

Yep, even in single mode

I've realized that when i tried to

Code:

umount -a -l -t reiserfs

2 times then

Code:

/ not mounted

ok then I re-mount :

Code:

mount -t reiserfs /dev/hd7 /

it says again that /dev/hda7 was already mounted !

marghorp · 05-25-2004, 05:41 PM

Did you try to change the fstab file? rw,.... to defualt?

Try this.

lamnk · 05-26-2004, 05:01 PM

It's said to be a fault of SuSE 9.1, some people have the same problem as mine. So i decided to reinstall, everything seem ok until i realized that every applications lag, its not like before. Did some test and here is the result of cpuinfo:

Code:

d047:/home/lam # cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 7
model name      : AMD Duron(tm) Processor
stepping        : 1
cpu MHz         : 497.866
cache size      : 64 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
bogomips        : 985.19

The problem is: my CPU clock is 950 MHz, not 500MHz !! I dont know why, since i found this in boot.msg:

Code:

<4>Detected 945.946 MHz processor.
..........
<4>Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
<4>Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
<6>checking if image is initramfs...it isn't (no cpio magic); looks like an ini$
<6>Looking for DSDT in initrd ...No customized DSDT found in initrd!
<6>Freeing initrd memory: 1102k freed
<7>CPU:     After generic identify, caps: 0383f9ff c1cbf9ff 00000000 00000000
<7>CPU:     After vendor identify, caps: 0383f9ff c1cbf9ff 00000000 00000000
<6>CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
<6>CPU: L2 Cache: 64K (64 bytes/line)
<7>CPU:     After all inits, caps: 0383f9ff c1cbf9ff 00000000 00000020
<6>Intel machine check architecture supported.
<6>Intel machine check reporting enabled on CPU#0.
<4>CPU: AMD Duron(tm) Processor stepping 01
<6>Enabling fast FPU save and restore... done.
<6>Enabling unmasked SIMD FPU exception support... done.

jspenguin · 05-26-2004, 08:09 PM

You have to remount it read-write. Try 'mount -o remount,rw /dev/hda7'. Then you can edit your fstab.

lamnk · 05-27-2004, 05:01 AM

Quote:

Originally posted by jspenguin
You have to remount it read-write. Try 'mount -o remount,rw /dev/hda7'. Then you can edit your fstab.

err, thanks but i have re-installed suse. The problem is now SuSE stole 400 MHz of my cpu.

DiWi · 06-03-2004, 03:13 AM

After I went though the same nightmare, here's a short howto guide, how it works:

First before you compile and install the new kernel make a rescue entry:
change to /boot/grub and edit the menu.lst file. Copy the section title Linux kernel... and initrd

Change the new menu entry to point to the original vmlinuz and initrd (should be vmlinuz-2.6.4-54.5-default and initrd-2.4.6-54.5-default)
Save the file and reboot. Try to boot with the newly created entry. If this works fine, you have a rescue point.

Now change the /etc/fsstab file as mentioned before. Reboot to get a new etc/mtab file. Check if the drive is mounted correctly.

Last but not least, compile & install the kernel and modules
make install
make modules_install

Change to the /boot directory again and check with ls -l the vmlinuz and initrd links. They should be set to the newly created kernel and modules (initrd)

Do a reboot and try if it's working. Otherwise, you can boot with the rescue entry

Dirk

ajfabbri · 06-07-2004, 01:13 PM

Quote:

Originally posted by marghorp
Try to make it into
/dev/hda7 / /reiserfs default 0 0

Actually it is "defaults". If you use "default", you'll see the same problem.

I also deleted my /etc/mtab before rebooting and it worked. Yay.