Problem running Kernel 2.6.0

oopicmaster · 12-22-2003, 02:52 PM

Ive compiled every option in the IDE chipset menu,

Now Im back to the original error message.

Is there a way for me to view all of the messages that print out during a good boot? If I could do this, then I could see everything that gets loaded with 2.4.22. Maybe its stored in a log file somewhere?

oopicmaster · 12-22-2003, 03:19 PM

It seems like the kernel is not recognizing the root partition as reiser, and loading the reiser fs driver. Im pretty sure that this is the point of failure. This driver is compiled into the kernel. Is there a way that I can specifically tell the kernel that the fs is reiser, instead of having the kernel attempt to figure it out via detection?

/bin/bash · 12-22-2003, 04:58 PM

To view your boot messages try this:
dmesg | more

What does this command return?
rdev /boot/vmlinuz-2.6.0

oopicmaster · 12-22-2003, 05:16 PM

rdev /boot/vmlinuz-2.6.0 returns the same as rdev /boot/vmlinuz-2.4.22

which is

Root device /dev/hda7

Ive noticed that the 2.4.22 kernel spits out

NET:..... somthing or other...

then

FAT: bogus logical sector size 12851

The 2.6.0 kernel spits out the NET message, but doesnt spit out the FAT message during boot.

/bin/bash · 12-22-2003, 06:41 PM

What is /dev/hda6? You have it listed as being ext2. Do you have ext2 built into your kernel?

<edit> Never mind, I see you have ext2 built in the kernel. Could you post your lilo.conf and also the result of this command:
ls -l /boot

BTW what distro are you using? Debian? Does it put kernels in /boot or /?

oopicmaster · 12-22-2003, 09:53 PM

My Kernels are in /boot which is /dev/hda6

The kernel recognizes this device but doesnt recognize / or hda7

/bin/bash · 12-22-2003, 10:14 PM

Do you have a symlink to new System.map-2.6.0? Don't know if it will help.

cd /boot
rm -f System.map
ln -s System.map-2.6.0 System.map

Then I think you have to rerun lilo.

oopicmaster · 12-23-2003, 12:50 AM

OK....

New development...

By manipulating some stuff in the kernel configuration... I have gotten to another point....

I boots passed the other error and I am now getting to a point where it prints the following:

fsck.ext2: No such file or directory while trying to open /dev/hda6

/dev/hda6:
The superblock could not be read or does not describe a correct ext2 filesystem... yadda, yadda, yadda...

Then

fsck failed. Please repair manually and reboot. The root filesystem is currently mounted read-only....

Then I get a:

Give root password to login:

oopicmaster · 12-23-2003, 01:06 AM

AHA!!!

A bit more tinkering and Ive got a login prompt... In addition to some other settings I had to turn on the Ext2 Extended attributes to get the kernel to recognize /dev/hda6.

MAN that was a pain in the keester...

Now all I have to do is figure out what I DONT need to compile... process of elimination

Thanks all...

TheOneKEA · 12-23-2003, 06:57 AM

Weird - you must have done something to the filesystem with your 2.4.22 kernel that 2.6.0 doesn't like. Was this 2.4.22 kernel a vendor kernel?

oopicmaster · 12-23-2003, 10:19 AM

No... the 2.4.22 wasnt a vendor kernel... I downloaded it... like 2.6.0 from kernel.org

The original kernel (I forget the version) was from a SUSE 7.3 distribution.

Now I have to get the network, and everything else running again, but at least I can log in....

BTW

One of the things I did was to select EVERY IDE chipset.... How can I go about finding out exactly which one the kernel is actually using. This way I can drop all the others.

/bin/bash · 12-23-2003, 12:11 PM

One of the things I did was to select EVERY IDE chipset.... How can I go about finding out exactly which one the kernel is actually using. This way I can drop all the others.

Look in /proc/ide, I have a via mobo and a file /proc/ide/via. Also cat /proc/ide/drivers will tell you which ide drivers are being used.
ide-floppy version 0.99.newide
ide-cdrom version 4.59-ac1
ide-disk version 1.18