Latest update: Have tried kernel 2.5.15: Some issue with the ramdisk. Will try a non-gzipped version of rescue9.1 and see what happens. It did write the following before panicking, though: hub.c: new USB device 00:1d.7-3, assigned address=2 usb.c: _USB device not accepting new address=2 (error=-71) When booting with USB 2.0 disabled the 2.5.15 kernel in stead said: usb-uhci.c: ENXIO 80000280, flags 0, urb f6766b00, burb f6766c00 2.5.42: Also had issues with the ramdisk. It seemed to be related to gunzip as well as the Oops mentioned gunzip.... Before the Oops it said: drivers/usb/core/hub.c: new USB device 00:1d.0-1, assigned address=2 Invalid operand: 0000 <Oops> Apparently, it wasn't the answer to the Universe, Life and Everything just yet... 2.5.46: I have a picture of the stuff that was on screen before the kernel panic. Too much to write down. Get it here: http://www.martinm-76.dk/Images/Kernel/2.5.46.jpg This is hard work -- I sure hope it gets me some results... :-/ At least I have become slightly better acquainted with the boot process... ;) /Martin. ----- "Martin Møller" <martin@mail.martinm-76.dk> wrote:
Okay... Here's the latest from 2.5-land:
I have copied the rescue image from SUSE Linux 9.1 to use as my initrd with the 2.5 kernels. I have called it 'rescue9.1' and invoke it like this:
### Testkernel ### title Linux 2.5.37 root (hd1,2) kernel /boot/linux-2.5.37 root=/dev/ram0 ramdisk_size=65536 rescue=1 showopts vga=ask initrd /boot/rescue9.1
title Linux 2.5.55 root (hd1,2) kernel /boot/linux-2.5.55 root=/dev/ram0 ramdisk_size=65536 rescue=1 showopts vga=ask initrd /boot/rescue9.1
title Linux 2.5.75 root (hd1,2) kernel /boot/linux-2.5.75 root=/dev/ram0 ramdisk_size=65536 rescue=1 showopts vga=ask initrd /boot/rescue9.1
Status:
2.5.37 - Gets as far as trying to do something with the ramdisk. Apparently doesn't like that it is not reiserfs and the kernel panics.
Seems the ramdisk is gzip compressed. Maybe I should try with a gunzipped version.
2.5.55 - Boots up all the way, but does make some usb comments, including 'cable is bad'. I have tried to write them down as accurately as I could:
First boot, without ramdisk (I had forgotten to specify it in menu.lst): hub 1-0:0: debounce: port 1: delay 100 ms stable 4 status 0x501 hub 1-0:0: debounce: port 3: delay 100 ms stable 4 status 0x501
Second time, with ramdisk (maybe the above was there as well, but I didn't notice it): hub 1-3:0 debounce: port 2: delay 100 ms stable 4 status 0x101 (not quite sure about this one)
cannot enable port2: Maybe the USB cable is bad? <many of those> hub 1-3:0: New USB device on port 2, assigned address 14 hub 1-3.2: USB device not accepting new address (error=-71)
The machine seems pretty responsive but load is approximately 1.0 as all times. Still way better than the latest 2.6 kernels though, where load is normally around 3.0 for whatever reason -- I had no trouble using the keyboard and my USB disc was detected. XFS is not in this kernel so I couldn't mount anything.
2.5.75 - Tried it since I had built it anyway. It initializes the ramdisks and loop devices then ..... nothing.
I guess the best thing to try now is a middle ground between 2.5.37 and 2.5.55, which would be 2.5.46...
/Martin.
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org