Cannot boot 2.6.8 kernel from ext3 root partition on Ultra5
I have an Ultra5 that I've been running Sarge (testing - official snapshot 11/07/04, kernel 2.4.27). I downloaded and installed kernel-image-2.6.8-1-sparc64_2.6.8-5_sparc.deb, and also the corresponding source deb. I compiled my own custom 2.6.8 kernel and installed it. Both of the 2.6.8 kernels panic during boot-up. The following is the last 6 lines on the screen from an attempted boot: NET: Registered protocol family 1 NET: Registered protocol family 17 VFS: Cannot open root device hda2 or unknown-block(0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) 0Press L1-A to return to the boot prom When I use the Debian binary, I can press [Stop]-A to get back to the boot PROM, but when I use my self-compiled kernel, this does nothing - I have to use the hard power switch on the back of the CPU. Maybe this has something to do with the fact that I compiled Sun keyboard mouse support as modules (I want to use a USB KB mouse on a PCI USB card as the primary console)? My silo.conf looks like this: == root=/dev/hda2 partition=1 default=linux-usb read-only timeout=100 image=/vmlinuz-sun label=linux-sun initrd=initrd-sun image=/vmlinuz-usb label=linux-usb initrd=initrd-usb image=/vmlinuz-268 label=linux-268 initrd=initrd-268 image=/vmlinuz-268usb label=linux-268usb initrd=initrd-268usb == After booting into a 2.4.27 kernel, 'df -h' gives me this: == FilesystemSize Used Avail Use% Mounted on /dev/hda2 3.7G 2.7G 846M 77% / tmpfs 62M 0 62M 0% /dev/shm /dev/hda1 90M 22M 63M 26% /boot == In the Debian kernel, they have ext3 support as a module. In my kernel, I compiled it in monolithically. The only feature I don't have enabled is EXT3_FS_SECURITY. Everything else related to ext3 is enabled. Anybody out ther know what might be causing this? Any suggestions would be greatly appreciated. -Dan
Re: USB keyboard mouse on Sun Ultra 5 w/PCI USB card
After many attempts at trying to disable Sun KB mouse support in the Debian-supplied 2.4.27 source, nothing worked. First of all, with kernel 2.4.27, there are no options for Sun KB mouse support listed in xconfig. One has to manually edit .config to change these settings. Even after manually editing .config, I found that my settings were put back to monolithic support for the Sun KB mouse, presumably by the file (srcroot)/arch/sparc64/config.in which has some lines like define_boolean CONFIG_SUN_KEYBOARD=y etc. etc.. I changed these to define_tristate CONFIG_SUN_KEYBOARD=m etc. etc., and the compile failed exactly when looking for a routine called handle_keyboard_event or something similar. So apparently, the sparc64 port of the 2.4.27 kernel does NOT like to have Sun KB mouse support disabled. I then downloaded the 2.6.8 kernel source from Debian, and lo and behold! Sun KB mouse support are configurable from xconfig (kconfig). So I compiled up a lean, mean 2.6.8 kernel with Sun KB mouse support as modules. The compile went fine, but now I have a new problem, as explained in my new post, Cannot boot 2.6.8 kernel from ext3 root partition on Ultra5 (http://lists.debian.org/debian-sparc/2004/12/msg00174.html) Disable support for the sun keyboard or build it as a module but don't load it. BTW, Is there a way I can add something to, e.g., modules.conf (or one of the manual tweak files since modules.conf is auto-generated) in order to tell the kernel, never load the Sun keyboard module, even if you find a Sun keyboard attached? Thanks again. -Dan
Re: Cannot boot 2.6.8 kernel from ext3 root partition on Ultra5
Daniel E. Jonsen wrote: I have an Ultra5 that I've been running Sarge (testing - official snapshot 11/07/04, kernel 2.4.27). I downloaded and installed kernel-image-2.6.8-1-sparc64_2.6.8-5_sparc.deb, and also the corresponding source deb. I compiled my own custom 2.6.8 kernel and installed it. Both of the 2.6.8 kernels panic during boot-up. The following is the last 6 lines on the screen from an attempted boot: NET: Registered protocol family 1 NET: Registered protocol family 17 VFS: Cannot open root device hda2 or unknown-block(0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) 0Press L1-A to return to the boot prom Could you paste the log _up to_ the VFS: Cannot open... message? You use an Ultra 5, so your initrd should be loading the 'cmd64x' module for the stock kernel, and it should work. Or do you use a different setup? Thanks -- Joshua Kwan signature.asc Description: OpenPGP digital signature
Re: Cannot boot 2.6.8 kernel from ext3 root partition on Ultra5
Joshua Kwan wrote: NET: Registered protocol family 1 NET: Registered protocol family 17 VFS: Cannot open root device hda2 or unknown-block(0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) 0Press L1-A to return to the boot prom Could you paste the log _up to_ the VFS: Cannot open... message? You use an Ultra 5, so your initrd should be loading the 'cmd64x' module for the stock kernel, and it should work. Or do you use a different setup? Thanks Is there a way I can copy/paste these messages? I used a good old fashioned pen and paper to write down the last six lines. I really would like to avoid using this method for the whole boot sequence, which is about 50 lines. Again, I have to press [Stop]-A and do reset-all, or use the hard power switch on the back of the CPU. Can I still get dmesg-like output from failed boot attempts after flipping the switch? If so, how? If not, are there any key lines in the boot sequence that I should zero in on? I suppose if I really start to pull my hair out I could conceivably use pen and paper on 50 lines, but that would take me about an hour... Thanks -Dan
Re: Cannot boot 2.6.8 kernel from ext3 root partition on Ultra5
Daniel E. Jonsen wrote: Is there a way I can copy/paste these messages? I used a good old fashioned pen and paper to write down the last six lines. I really would like to avoid using this method for the whole boot sequence, which is about 50 lines. You can use a serial console. Discussing how to do that is kind of out of the scope of this message, Google can help you out on that. Basically, though, all I need is stuff related to 'CMD64X' (if there isn't any, that is a problem) and IDE. Common sense should be enough to get what I need. :) -- Joshua Kwan signature.asc Description: OpenPGP digital signature
SPARC Boot Issues
Regarding your boot problem, I suspect your kernel configuration is missing features you need. Please consider the following URL's premade kernel configurations. I suggest you compare them to yours to ensure you have an adequate feature set for your particular situation. http://dev.gentoo.org/~ciaranm/configs/kernel/2.6.x/
