-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2013-10-10 a las 19:06 +1100, Basil Chupin escribió:
On 10/10/13 07:59, Carlos E. R. wrote:
Did he not have multiversion active for the kernel? He should have been able to boot the previous kernel from grub menu.
As far as I am concerned this makes no difference from personal experience. When a new kernel is installed the grub menu tries to boot the system with the new kernel and you don't have a choice of booting with anything else - even trying the "Safe Mode" results in the same process.
Having multversion active in sysconfig only means that the old kernels are not removed from /boot. If you look at your /boot you will see that while you may a hundred kernel versions sitting there, the @intrd and @vmlinuz are pointing at the latest installed kernel.
Then you have something wrong in your setup. In my machines it boots by default the new kernel, yes, but, be it grub 1 or 2, I get an extra entry to boot the old kernel. in grub2 you have to select the "advanced" entry, and there you should have two (or more) normal boot entries, and two (or more) failsafe entries. Of those two one is for the old kernel and another for the new kernel. In grub 1 you simply get a list of all kernels, with two entries for each (normal and failsafe). - -- Cheers Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iF4EAREIAAYFAlJWnvUACgkQja8UbcUWM1z9dQD+P82K9qI+8HUoeRmyjIVobJ2Y MFxzlBuPFUBOq05Jt0YA/ja1efLQiiNJGQMSbPixBJ9PL2qdUkGz49EEb/ug0CTX =qu4B -----END PGP SIGNATURE-----