The UnitedLinux SP2 patch set includes the kernel k_smp-2.4.19-249, which doesn't boot on my system. At least, it didn't boot after following the normaly YaST2 based install. I haven't tried to debug it thoroughly (I spent the last few hours figuring out how to revert the kernel.) so I'm not sure if the kernel is broken, or the kernel *install* is broken. BTW, the "boot installed system" option on the install disk is a nice touch. I found it by accident, it is really worthy of a place in the printed documentation. -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
The UnitedLinux SP2 patch set includes the kernel k_smp-2.4.19-249, which doesn't boot on my system. At least, it didn't boot after
Strange. Thanks for telling. Let's see whether we can help somehow...
following the normaly YaST2 based install. I haven't tried to debug it thoroughly (I spent the last few hours figuring out how to revert the kernel.) so I'm not sure if the kernel is broken, or the kernel *install* is broken.
Do you use lilo? Did you run lilo again after the test? Did the older kernel work for you? What kind of system do you have?
BTW, the "boot installed system" option on the install disk is a nice touch. I found it by accident, it is really worthy of a place in the printed documentation.
It's even default now in our products... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andreas Jaeger aj-at-suse.de |suse-amd64| wrote:
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
following the normaly YaST2 based install. I haven't tried to debug it thoroughly (I spent the last few hours figuring out how to revert the kernel.) so I'm not sure if the kernel is broken, or the kernel *install* is broken.
Do you use lilo? Did you run lilo again after the test? Did the older kernel work for you? What kind of system do you have?
Not LILO, grub-0.92-247. I noticed that the install of -249 also created a vmlinuz.installed from the old kernel, but the "failsafe" boot selection didn't work either. Dual Opteron 244, 1Gig, Adaptec SCSI interface and a single SCSI disk, IDE cdrom and ZIP drive. Fairly conventional, actually. Since even the .installed kernel didn't boot, but I was able to but things back together with an rpm -Uvh --oldpackage k_smp-*.rpm, I wonder if the modules were not installed/depmoded properly by the patch. Sorry, I'm used to LILO (and would have known to run lilo after an install) and I'm used to aboot on the alpha not needing any special effort. I believe grub is happy with its lst file and can read the filesystem just fine. -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
Andreas Jaeger aj-at-suse.de |suse-amd64| wrote:
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
following the normaly YaST2 based install. I haven't tried to debug it thoroughly (I spent the last few hours figuring out how to revert the kernel.) so I'm not sure if the kernel is broken, or the kernel *install* is broken. Do you use lilo? Did you run lilo again after the test? Did the older kernel work for you? What kind of system do you have?
Not LILO, grub-0.92-247. I noticed that the install of -249 also created a vmlinuz.installed from the old kernel, but the "failsafe" boot selection didn't work either.
Dual Opteron 244, 1Gig, Adaptec SCSI interface and a single SCSI disk, IDE cdrom and ZIP drive. Fairly conventional, actually.
Yes, that should be fine.
Since even the .installed kernel didn't boot, but I was able to but things back together with an rpm -Uvh --oldpackage k_smp-*.rpm, I wonder if the modules were not installed/depmoded properly by the patch.
Or mkinitrd not called? But this is done via the rpm automatically.
Sorry, I'm used to LILO (and would have known to run lilo after an install) and I'm used to aboot on the alpha not needing any special effort. I believe grub is happy with its lst file and can read the filesystem just fine.
Exactly, grub shouldn't case a problem. Can you try again with the new kernel and write down where it fails? I need some more details... Cheers, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Depending on the chipset of this board (I assume AMD 8000 series tunnels), the IDE ZIP may be a good idea to remove from the system - a USB CMOS flash drive is better for back up with out conflicts. The firmware of ZIP drives does confuse the ACPI state of most chipsets bar Intel. Andrew Cotterill Senior Technical Engineer http://www.epox.org -----Original Message----- From: Andreas Jaeger [mailto:aj@suse.de] Sent: 25 July 2003 07:06 To: Stephen Williams Cc: suse-amd64@suse.com Subject: Re: [suse-amd64] kernel k_smp-2.4.19-249 doesn't work? "Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
Andreas Jaeger aj-at-suse.de |suse-amd64| wrote:
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
following the normaly YaST2 based install. I haven't tried to debug it thoroughly (I spent the last few hours figuring out how to revert the kernel.) so I'm not sure if the kernel is broken, or the kernel *install* is broken. Do you use lilo? Did you run lilo again after the test? Did the older kernel work for you? What kind of system do you have?
Not LILO, grub-0.92-247. I noticed that the install of -249 also created a vmlinuz.installed from the old kernel, but the "failsafe" boot selection didn't work either.
Dual Opteron 244, 1Gig, Adaptec SCSI interface and a single SCSI disk, IDE cdrom and ZIP drive. Fairly conventional, actually.
Yes, that should be fine.
Since even the .installed kernel didn't boot, but I was able to but things back together with an rpm -Uvh --oldpackage k_smp-*.rpm, I wonder if the modules were not installed/depmoded properly by the patch.
Or mkinitrd not called? But this is done via the rpm automatically.
Sorry, I'm used to LILO (and would have known to run lilo after an install) and I'm used to aboot on the alpha not needing any special effort. I believe grub is happy with its lst file and can read the filesystem just fine.
Exactly, grub shouldn't case a problem. Can you try again with the new kernel and write down where it fails? I need some more details... Cheers, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andrew Cotterill (EPoX UK) andy-at-epox.org |suse-amd64| wrote:
Depending on the chipset of this board (I assume AMD 8000 series tunnels), the IDE ZIP may be a good idea to remove from the system - a USB CMOS flash drive is better for back up with out conflicts. The firmware of ZIP drives does confuse the ACPI state of most chipsets bar Intel.
AMD-8111 northbridge. Actually, the ZIP drive has been working fine for me so far. The system did lock up on me when I added a Microtec USB Cameramate, but I've been in no hurry to debug that at the moment. -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
Andreas Jaeger aj-at-suse.de |suse-amd64| wrote:
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
Since even the .installed kernel didn't boot, but I was able to but things back together with an rpm -Uvh --oldpackage k_smp-*.rpm, I wonder if the modules were not installed/depmoded properly by the patch.
Or mkinitrd not called? But this is done via the rpm automatically.
It was called.
Can you try again with the new kernel and write down where it fails? I need some more details...
It crashed very early. After grub loaded it, the screen went dark, then within 5 seconds the computer rebooted. I was unable to see any boot messages from the new kernel. The unfortunate part about the kernel rpms is that the module set is not versioned with the kernel (i.e. there is no -249 modules directory) so it is a little tricky setting up a backup kernel for when it fails. -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
Andreas Jaeger aj-at-suse.de |suse-amd64| wrote:
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
Since even the .installed kernel didn't boot, but I was able to but things back together with an rpm -Uvh --oldpackage k_smp-*.rpm, I wonder if the modules were not installed/depmoded properly by the patch. Or mkinitrd not called? But this is done via the rpm automatically.
It was called.
Can you try again with the new kernel and write down where it fails? I need some more details...
It crashed very early. After grub loaded it, the screen went dark, then within 5 seconds the computer rebooted. I was unable to see any boot messages from the new kernel.
Add "vga=0" to the linuxrc command line to not use the graphical screen. That way you can see even the early boot messages. Another solution is attaching a serial console and logging the output there. A third idea: Wait until the middle of next week, I'll test some odd systems with the new kernel and see whether really all of them work (as they did so far).
The unfortunate part about the kernel rpms is that the module set is not versioned with the kernel (i.e. there is no -249 modules directory) so it is a little tricky setting up a backup kernel for when it fails.
I agree, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
The UnitedLinux SP2 patch set includes the kernel k_smp-2.4.19-249, which doesn't boot on my system. At least, it didn't boot after
Strange. Thanks for telling. Let's see whether we can help somehow...
following the normaly YaST2 based install. I haven't tried to debug it thoroughly (I spent the last few hours figuring out how to revert the kernel.) so I'm not sure if the kernel is broken, or the kernel *install* is broken.
Do you use lilo? Did you run lilo again after the test? Did the older kernel work for you? What kind of system do you have?
BTW, the "boot installed system" option on the install disk is a nice touch. I found it by accident, it is really worthy of a place in the printed documentation.
It's even default now in our products... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (3)
-
Andreas Jaeger -
Andrew Cotterill (EPoX UK) -
Stephen Williams