errors while compiling kernel

Drone4four · 07-07-2006, 10:16 PM

Sandman1 and thrice` in #Slackman have narrowed down my kernel panic to two possible causes with my kernel compilation:

1. a misconfigured reiserfs support
2. a misconfigured ide interface

The solution? First I needed to reboot with the Slackware 10.2 livecd and enter on boot: “bare.i root=/dev/hda3 noinitrd ro”. This allows my Slackware distro to boot using the krenel on the livecd. This way I can log into my normal user accounts and navigate my file system with my GUI. I cd into the linux kernel directory I was using before and enter “make menuconfig” With the configuration menu up, I need to navigate to and then check Device Drivers > ATAPI/IDE/xxx. I must do the same for File systems >> Reiserfs support and make sure it’s marked with a “*” and not just an “M”. Then I continue the kernel compile process. For example, I’m using Sandy’s guide found here, ftp://thesandman01.homelinux.com/Tutorials/kernel.txt

I’d like to emphasize the last step described in the above kernel.txt guide: enter “/sbin/lilo”.

I rebooted …and the kernel panic still exists. Just a reminder, the kernel panic looks like this:

Code:

FS: Cannot open root device "303" or unknown-block(3,3) 
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount fs on unknown-block(3,3)

Therefore I’m going to follow WindowBreaker’s detailed guidance now and report back with the results. I probalby could have followed WindowBreaker's instructions before. I'm sorry I didn't.

=D

edit:added kernel panic error reminder
edit:sp + grammar

Drone4four · 07-07-2006, 10:25 PM

Quote:

Originally Posted by katayamma

Why won't you just become root before you do the make & make install? That would solve any permission problems you have. In fact, I can't really think of a reason you wouldn't want to build/install a kernel as root.

I'm confused. Enlighten me please.

Good point, katayamma. I've done all my recent make modules_install commands as super user.

Drone4four · 07-07-2006, 10:30 PM

Quote:

Originally Posted by WindowBreaker

I think what messed you up is the 'root = /dev/????' entry lilo used when installing the new kernel.

Thanks for bringing lilo up. All entries in my lilo configuration files are correct (I think):

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x256
vga = normal
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda3
  label = Linux-2.4.31 
  read-only
# Linux bootable partition config ends
image = /boot/bzImage-2.6.17.3
 root = /dev/hda3
 label = Linux-2.6.17.3
 read-only

After assertibg my lilo.conf might be problematic, WindowBreaker suggested that perhaps compiling my filesystem is the problem:

Quote:

Originally Posted by WindowBreaker

If that doesn't work, and you're sure lilo.conf is correct - then make sure the appropriate filesystem support is compiled into the new kernel. If you're using reiserfs on your root partition, note that I don't think it's compiled into the 2.6.x kernels by default.

You're right about the filesystem support not being compiled by default. As I pointed out in post #16, I have tried compiling reiserfs into my new kernel which has not fixed the kernel panic.

edit:sp x3
edit:grammar and paragraph flow

WindowBreaker · 07-08-2006, 05:36 AM

Something does not add up. The .config file you posted shows that support for both ext3 & reiserfs is compiled into the kernel. However, previous posts show that running

Code:

make modules_install

clearly installs kernel modules for both filesystems.

Quote:

bash-3.00# make modules_install
INSTALL fs/ext3/ext3.ko
INSTALL fs/jbd/jbd.ko
INSTALL fs/reiserfs/reiserfs.ko

Post #5 shows you're working with kernel 2.6.17.2. If so, why would you copy the bzImage from a 2.6 kernel onto a file named vmlinuz-ide-2.4.31 (post #3)?

Is it possible that the symbolic link /usr/src/linux is still pointing to your old kernel?

Show us the output from

Code:

ls -l /usr/src
find /usr/src -name bzImage -mtime -14 -exec ls -l '{}' \;
find /usr/src -name .config -mtime -14 -exec ls -l '{}' \;

If you want to know where the bzImage file is located right after compiling your new kernel

Code:

find /usr/src -name bzImage -mmin -5 -exec ls -l '{}' \;

where '-mmin 5' will limit the search to files modified in the last 5 minutes (tweak as necessary).

Drone4four · 07-09-2006, 03:18 AM

WindowBreaker, I appprecitate the care you've put into assissting me troubleshoot my kernel panics.

Quote:

Originally Posted by WindowBreaker

Post #5 shows you're working with kernel 2.6.17.2. If so, why would you copy the bzImage from a 2.6 kernel onto a file named vmlinuz-ide-2.4.31 (post #3)?

Basically after my post #11, I cowardly gave up. I nuked slackware out of frustration and tried a different distro. Days later I returned to slackware. About one week after the nuke, I re-retried compiling my kernel again (this time with 2.6.16.3). Last week I was using 2.6.16.2. To no surprise, I get the exact same errors. All you need to know: 2.6.16.2 doesn't exist anymore on my HD. That should address your observation about things not adding up, WindowBreaker.

As of right now, mostly Sandy form #slackman held my hand through the configuring my kernel with specific options set. Two essentail settings which had to be configured into my kernel are:

Code:

Device Drivers -> ATAPI/ATAPI/MFM/RLL support
<*>       generic/default IDE Chipset Support

Device Drivers -> Network device support -> Ethernet (10 or 100Mbit)
<*>	Realtek RTL-8129/8139/8139 PCI Fast Ethernet Adapter support

I think there were some more settings Sandy made me configure, but I can't remember exactly. At any rate, those corrections still produce a (different) kernel panic. The resolution? I need now to append noresume in lilo to be able to login and get a CLI. That's good. I've made progress. However, I can't startx because my drivers were configured origninally for the stock kernel. After uninstaling, the reinstallation stops with the following error:

Code:

Compiling new agpgart module...
Compiling DRM module...

ERROR: Kernel modules did not compile

The DRI drivers can not be installed without the latest kernel modules.  Installation will be aborted. See the dri.log file for information on what went wrong.

The dri.log reads as follows:

Code:

make-f Makefile.linux DRM_MODULES=gdg.ko modules
make[1]: Entering directory /tmp/dripkg/drm 
make -C /lib/modules/2.6.17.3/build SUBDIRS='pwd' DRMSRCDIR='pwd' modules 
make[2]:Entering director '/tmp/linux-2.6.16.3' 
rm: cannot remove '/tmp/dripkg/drm.tmp_version/CVS'" Is a directory 
make[2] ***[crmodverdir] Error 1
make[2] Leaving directory '/tmp/linux-2.6.16.3' 
make[1]  ***[modules] Error 2
make[1] Leaving directory '/tmp/dripkg/drm'
make: *** [gdg.ko] Error 2

So WindowBreaker, do you think it's still necessay that I follow your suggested instructions?:

Quote:

Is it possible that the symbolic link /usr/src/linux is still pointing to your old kernel?

Show us the output from

Code:

ls -l /usr/src
find /usr/src -name bzImage -mtime -14 -exec ls -l '{}' \;
find /usr/src -name .config -mtime -14 -exec ls -l '{}' \;

If you want to know where the bzImage file is located right after compiling your new kernel

Code:

find /usr/src -name bzImage -mmin -5 -exec ls -l '{}' \;

where '-mmin 5' will limit the search to files modified in the last 5 minutes (tweak as necessary).

edit:specific kernel configurations+ grammar + flow
edit:sp