Re: [opensuse] openSuSe 10.3 hangs after kernel update
I booted from the 64b installation DVD and chose boot installed system, and
that only tried to boot the "bad" kernel (i.e. system hangs with same errors).
I tried doing update system but that did not quit ego well. Can I even "update" a very
current 10.3 to the initial 10.3 DVD kernel level? Sounds like that may not work either.
I think I need to install a working kernel from scratch. I see openSuSE released a new kernel two
days back...
Given I cannot boot to this machine what is the best way to install a new kernel? I can boot using
a live DVD (openSuSE Ubuntu, etc...) and try to compile the kernel and then copy it to the 10.3
kernel directory, but I am not sure this approach will work.
I notice yast did not save my old kernels so I cannot edit grub's menu.lst to use an older working
kernel.
Is there a way to configure yast to not delete an old kernel when a new one is installed?
Giving I update to this non-function kernel using yast, I am still not clear why I seem to have ended up
with the wrong kernel. How do I protect from this happening again?
Thanks,
Vahe
----- Original Message ----
From: David C. Rankin
Am Montag, 4. Februar 2008 schrieb Vahe Avedissian:
am running openSuSE x64 (AMD) and my machine now hangs early during
boot
request_module: runaway loop modprobe binfmt-464c
I googled
I just used YaST to update to the latest kernel (vmlinuz-2.6.22.16-01). I the process with the following message repeated several times: this and all I could find was either 32bie ELF file on an x64
bit machine, or a bad/incompatible disk controller driver.
For me, your problem looks like
https://bugzilla.novell.com/show_bug.cgi?id=333689
off or undo
I suspect the install did not go correctly. What is the best way to back the kernel update and revert to the
The easiest way would be to boot from the 64 bit installation DVD. Then,
select the grub menu item "Boot Installed System". If this works, you will
be able to re-install the correct x86_64 kernel by simply using YaST.
HTH
Jan All of the old kernels are contained in the /updates repository. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-02-07 at 09:32 -0800, Vahe Avedissian wrote:
I booted from the 64b installation DVD and chose boot installed system, and that only tried to boot the "bad" kernel (i.e. system hangs with same errors).
No, you need to start the live system in the rescue dvd, mount your root filesystem, and chown to it. As somebody else wrote (Anders Johansson): ] In the past few releases, you can't just do a chroot from the rescue ] system. You have to (assuming the root partition is mounted on /mnt) ] ] mount -o bind /proc /mnt/proc ] mount -o bind /sys /mnt/sys ] mount -o bind /dev /proc/dev ] ] then you can do the chroot Once you do the chroot, you can fire up yast and force a reinstall of the kernel. In theory, the automatic rescue thing should work, but... :-?
Is there a way to configure yast to not delete an old kernel when a new one is installed?
No. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHq6NTtTMYHG2NR9URAvDBAJ4qKeX1M9K2vLaNRvTM36FLsGGk3ACeNKlH sm8RoYJku6eHW0YFCyR1G54= =NnVl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 07 February 2008 06:33:20 pm Carlos E. R. wrote:
The Thursday 2008-02-07 at 09:32 -0800, Vahe Avedissian wrote:
I booted from the 64b installation DVD and chose boot installed system, and that only tried to boot the "bad" kernel (i.e. system hangs with same errors).
No, you need to start the live system in the rescue dvd, mount your root filesystem, and chown to it.
As somebody else wrote (Anders Johansson):
] In the past few releases, you can't just do a chroot from the rescue ] system. You have to (assuming the root partition is mounted on /mnt) ] ] mount -o bind /proc /mnt/proc ] mount -o bind /sys /mnt/sys ] mount -o bind /dev /proc/dev ] ] then you can do the chroot
Once you do the chroot, you can fire up yast and force a reinstall of the kernel.
In theory, the automatic rescue thing should work, but... :-?
Is there a way to configure yast to not delete an old kernel when a new one is installed?
No.
The easiest way for me is to copy old kernel modules in /lib/modules to safe place, the same with /boot and restore what I want after update and before reboot. Add old kernel to /boot.grub/menu.lst and than reboot. I actually have symlinks vmlinuz-old and initrd-old so I update them insted of menu.lst. Than everybody is happy, YaST has new kernel and I have old. -- Regards, Rajko. See http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-02-07 at 21:12 -0600, Rajko M. wrote:
On Thursday 07 February 2008 06:33:20 pm Carlos E. R. wrote:
(you should qualify the time with the timezone :-) )
Is there a way to configure yast to not delete an old kernel when a new one is installed?
No.
The easiest way for me is to copy old kernel modules in /lib/modules to safe place, the same with /boot and restore what I want after update and before reboot. Add old kernel to /boot.grub/menu.lst and than reboot. I actually have symlinks vmlinuz-old and initrd-old so I update them insted of menu.lst. Than everybody is happy, YaST has new kernel and I have old.
Well, but by that method the old kernel is not listed by rpm. Instead, you can download the kernel update manually and install it manually: this way you can have both kernels listed. It would be a nice feature if Yast could do this trick with vital rpms. What yast does is an update of the kernel rpm, meaning that the old one is uninstalled and the new one installed. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHrDr0tTMYHG2NR9URAk3AAJ0RQ/4XbIzd+fvkAV6rr3DLs/2pvACfRdMw iFjfSQscsPPxRu2AnpWmyjo= =Hmeb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2008/02/08 12:20 (GMT+0100) Carlos E. R. apparently typed:
Well, but by that method the old kernel is not listed by rpm. Instead, you can download the kernel update manually and install it manually: this way you can have both kernels listed.
It would be a nice feature if Yast could do this trick with vital rpms.
+2
What yast does is an update of the kernel rpm, meaning that the old one is uninstalled and the new one installed.
It's worse than that. You can rpm -ivh the new kernel to have both old and new before doing other updates, and yast will dutifully reinstall the kernel you just installed as well as removing the old one you kept on purpose. So, at least test the new kernel first before letting yast have its way, to be sure the only kernel yast leaves you with actually works. Right now with one of my systems the factory kernels are incompatible with an X session lasting more than a few seconds. Any more than that, and the system is instantly put into unrecoverable sleep mode. -- "For God so loved the world that he gave his one and only Son, that whoever believes in him shall not perish but have eternal life." John 3:16 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-02-08 at 15:16 -0500, Felix Miata wrote:
What yast does is an update of the kernel rpm, meaning that the old one is uninstalled and the new one installed.
It's worse than that. You can rpm -ivh the new kernel to have both old and new before doing other updates, and yast will dutifully reinstall the kernel you just installed as well as removing the old one you kept on purpose.
:-(
So, at least test the new kernel first before letting yast have its way, to be sure the only kernel yast leaves you with actually works.
I always check what yast wants to install carefully. Right now, it wants to update xinelib, even though I have a version compiled by myself, which on previous suse version automatically meant "protected" status. I will have to reinstall my rpm with release number .999 :-(
Right now with one of my systems the factory kernels are incompatible with an X session lasting more than a few seconds. Any more than that, and the system is instantly put into unrecoverable sleep mode.
Ouch :-( My 10.3 goes dozing unless there is keyboard activity or some other interrupt. I have my router permanently pinging my PC so that it doesn't sleep "on foot" - it simply stops processing, tasks stops, display stops... waiting for a mouse move, key press, network packet... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHrMHctTMYHG2NR9URAob2AJ4jzK6r8sru0ptXpDtrBGaxuyFONgCfR6TW SaYwwjX0akLpm/zCQ9hksCc= =b1vz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Freitag, 8. Februar 2008 schrieb Carlos E. R.:
The Thursday 2008-02-07 at 09:32 -0800, Vahe Avedissian wrote:
I booted from the 64b installation DVD and chose boot installed system, and that only tried to boot the "bad" kernel (i.e. system hangs with same errors).
No, you need to start the live system in the rescue dvd, mount your root filesystem, and chown to it.
Too bad, I hoped that there is still the possibility to boot the installed system with the original kernel.
As somebody else wrote (Anders Johansson): [mount --bind]
I know, that was the reason to let Vahe first try it the easy way. BTW, there is a bug report about the "missing" documentation of the rescue process when using a dynamic /dev: https://bugzilla.novell.com/show_bug.cgi?id=293691 Gruß Jan -- Don't force it, get a larger hammer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos E. R. -
Felix Miata -
Jan Ritzerfeld -
Rajko M. -
Vahe Avedissian