Updated Last Night- Kernel Bug Now.

I can't boot my laptop. It shows grub, I select suse11 and it displays

(filesystem stuff)

EDD probe
decompressing linux.... done
booting the kernel




BUG: Int 6: CR2 00000000
[/b]

Any thoughts, the laptop's CD drive is broken, which means I have to spend double the time to reinstall.

I can't boot my laptop. It shows grub, I select suse11 and it displays
Any thoughts, the laptop's CD drive is broken, which means I have to spend double the time to reinstall.
[/b]

Hi,

I have the same problem after today's updates the system will not boot anymore.

I have booted a live-cd, mounted the harddisk and accessed it with a chroot.

What I noticed is that the symlink "initrd" in /boot points to a nonexistent file "initrd-2.6.25-......" (initrd --> initrd-2.6.25-.....).

I have reinstalled the package "kernel-default" with zypper, but still did not get the new initrd matching the new kernel.

So it seems that the latest kernel updates are borked.

stefan

Hi,

I have the same problem after today's updates the system will not boot anymore.

I have booted a live-cd, mounted the harddisk and accessed it with a chroot.

What I noticed is that the symlink "initrd" in /boot points to a nonexistent file "initrd-2.6.25-......" (initrd --> initrd-2.6.25-.....).

I have reinstalled the package "kernel-default" with zypper, but still did not get the new initrd matching the new kernel.

So it seems that the latest kernel updates are borked.

stefan
[/b]

well that sucks, I think I have to reinstall then.

well that sucks, I think I have to reinstall then.
[/b]

reinstall? that would set you back to the beta3 level then. If it is a update gone bad I am sure it will get fixed and then you can just reinstall the kernel to get it fixed, takes a lot less effort then the entire system (especially if you have tuned it to your needs)

when a correct kernel gets out this would be all that is needed to fix it:

1) boot live-cd
2) open terminal
3) sudo su -
4) mkdir /mnt/disk
4) mount /dev/{device_of_your_harddisk} /mnt/disk (for most {device_of_your_harddisk} would be /dev/sdaX where X is the partition of your root disk, in my case /dev/sda1)
5) chroot /mnt/disk
6) zypper remove kernel-default
7) zypper install kernel-default

voila!

and you'd be all set ... IF it is a bug AND they fix it soon ...
stefan

reinstall? that would set you back to the beta3 level then. If it is a update gone bad I am sure it will get fixed and then you can just reinstall the kernel to get it fixed, takes a lot less effort then the entire system (especially if you have tuned it to your needs)

when a correct kernel gets out this would be all that is needed to fix it:

1) boot live-cd
2) open terminal
3) sudo su -
4) mkdir /mnt/disk
4) mount /dev/{device_of_your_harddisk} /mnt/disk (for most {device_of_your_harddisk} would be /dev/sdaX where X is the partition of your root disk, in my case /dev/sda1)
5) chroot /mnt/disk
6) zypper remove kernel-default
7) zypper install kernel-default

voila!

and you'd be all set ... IF it is a bug AND they fix it soon ...
stefan
[/b]

Hi stefan & quickshade.

That is a good tip..
Guess you could also do this booting with the beta3 cd and revert back to the old kernel that is on the cd. Saves having to wait till the next factory kernel gets placed.

If you guys get that setup would be good to post what you did seeing I think more will have this issue.

Cheers,
Wj

Hi stefan & quickshade.

That is a good tip..
Guess you could also do this booting with the beta3 cd and revert back to the old kernel that is on the cd. Saves having to wait till the next factory kernel gets placed.

If you guys get that setup would be good to post what you did seeing I think more will have this issue.

Cheers,
Wj
[/b]

when I boot my Fedora_9_x64 setup back to OpenSuSe beta3+ i will give it a shot and report back, hopefully they will have a fix for this before then and it would be nice to know if more people have this issue or of it was just bad luck. I was running a fully updated i386 beta3 installed from the KDE4 live cd.

stefan

I can't boot my laptop. It shows grub, I select suse11 and it displays
Any thoughts, the laptop's CD drive is broken, which means I have to spend double the time to reinstall.
[/b]

Maybe related to this ....
https://bugzilla.novell.com/show_bug.cgi?id=392198

... I need to reply to the "need info".

Maybe related to this ....
https://bugzilla.novell.com/show_bug.cgi?id=392198

... I need to reply to the "need info".
[/b]

mmm i don't know, beta3 was Very stable for me with a 100% boot succes until the last updates and now i have NO initrd-2.6.25-42.2 file in /boot anymore so it doesn't boot any of the times I try it.

it is more like this one, for me at least:
https://bugzilla.novell.com/show_bug.cgi?id=389177

a mere

sudo mkinitrd

should be enough to fix this but for now it will not run in my chrooted environment because it cannot find the root device.

stefan

mmm i don't know, beta3 was Very stable for me with a 100% boot succes until the last updates and now i have NO initrd-2.6.25-42.2 file in /boot anymore so it doesn't boot any of the times I try it.

it is more like this one, for me at least:
https://bugzilla.novell.com/show_bug.cgi?id=389177

a mere

sudo mkinitrd

should be enough to fix this but for now it will not run in my chrooted environment because it cannot find the root device.

stefan
[/b]

My main problem is I don't have a working CD drive.

My system after update today will not boot. It will boot in the failsafe mode but can't use if the graphics are hozed. Hope they soon have a downloadable fix.