Has the YOU kernel error been fixed at the YOU sites?
Hi All, Has SUSE fixed the kernel 2.6.8-24.10 update pkg at the repository yet. It seems derilect that this bug is still crippling systems. PeterB -- -- Proud SUSE user since 5.2 Loving SUSE 9.2 My BLOG == http://vancampen.org/blog --
On Mon, 27 Dec, 2004 at 19:33:18 -0600, Peter B Van Campen wrote:
Hi All,
Has SUSE fixed the kernel 2.6.8-24.10 update pkg at the repository yet.
Yes, it's fixed. I ran YOU two days ago, and had no trouble afterwards. /Jon -- YMMV
On Tuesday 28 December 2004 01:24, Jon Clausen wrote:
On Mon, 27 Dec, 2004 at 19:33:18 -0600, Peter B Van Campen wrote:
Hi All,
Has SUSE fixed the kernel 2.6.8-24.10 update pkg at the repository yet.
Yes, it's fixed.
I ran YOU two days ago, and had no trouble afterwards.
/Jon -- YMMV
I ran it today and got a kernel panic: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,2) Jerome
Susemail wrote:
On Tuesday 28 December 2004 01:24, Jon Clausen wrote:
Yes, it's fixed.
I ran YOU two days ago, and had no trouble afterwards.
/Jon -- YMMV
I ran it today and cannot get a graphical environment anymore. I should note, however, that it did tell me to run /sbin/lilo (because I'm using lilo) before rebooting. When I tried to do that I received an error "/etc/lilo.config not found". I'm not proficient enough to change the initrd stuff (if that's even what I need to do). Any ideas here? Thanks in advance Jack
I ran the update on my GRUB 9.2 box & it worked . I am curious what factors make it fail on some boxes. ...eric
On Tuesday 28 December 2004 17:24, Eric Weil wrote:
I ran the update on my GRUB 9.2 box & it worked .
I am curious what factors make it fail on some boxes.
...eric
It looks like we're getting different failures. I ran 9.2 DVD-installation-repair but it didn't help. I'm using GRUB. Jerome
According to the NOVELL forums it has been fixed as of today: http://forums.suselinuxsupport.de/ ...eric
On Tuesday 28 December 2004 9:46 pm, Eric Weil wrote:
According to the NOVELL forums it has been fixed as of today:
http://forums.suselinuxsupport.de/
...eric
Hi Eric, On my 9.2 P-III dual sys I recovered the sys with the use of install DVD1 >install > repair >automatic repair. Allow it to repair 'booting'. Then I had to goto /usr/src/linux and issue as root 'make cloneconfig' , then you must remove and then re-install the nvidia drivers. There may still be some voodoo needed; I don't completely understand the nvidia driver process yet! Marcus Meissner od SUSE wrote this this morning: after the YOU kernel install, before re-booting, he requests you to do: "In a running system, run "mkinitrd" as root. This will restore the symlink. Check with ls -l /boot/initrd that it points to a initrd-2.6.8-24.10-xxxx where xxxx is default, smp or bigsmp. For nonbooting systems, boot a rescue system, mount the installed system, chroot into it, and run "/sbin/mkinitrd" which should restore the symlink there. (Or just use ln -s with the correct paths.) Ciao, Marcus I take this to mean that the YOU patch was erroniously forgetting to do the LINK of the new initrd-2.6.8-24.10-default (or whatever is right) to initrd. PeterB p.s. If anyone has gotten a working sys w/o re-doing the nvidia stuff, please let us know -- -- Proud SUSE user since 5.2 Loving SUSE 9.2 My BLOG == http://vancampen.org/blog --
participants (5)
-
Eric Weil -
Jack Brooks -
Jon Clausen -
Peter B Van Campen -
Susemail