Kernel issue - which is "safe"
I recently had problems upgrading to 9.1 and ended up doing a fresh install via ftp and all seemed OK. I did a YOU online update to make sure I had the latest security patches, and as warned I left out doing the kernel patch. At this stage I had installed the default-kernel 2.6.4-52 and mkinitrd 1.0-197. I have been using apt-get to update my system, sometimes with synaptic but now mostly just with apt-get. This has worked well for my 8, 8.1 and 8.2 versions. Now I am still on a steep learning curve so haven't got down to compiling sources etc but have been improving my knowledge of linux generally. I started having problems when I first updated 9.1 via apt, I had reviewed the sources list and removed the prpm sources and also kernel-of-the-day just in case I got into uncharted territory with possibly unstable releases. Included in the update was default-kernel 2.6.5-7.104 and mkinitrd 1.0- 199.50. All seemed OK until I turned off my computer (which I rarely do) to check a fan. When I rebooted it was taken a long time and so I went to the text screen (F2) and could simply see a rolling screen of text looping. I believe that this started with an fsck (? check of the ide drive, and then kept looping. I am not sure but is what is referred to as "kernel panic"? Anyway to cut a long story short and to remove the ugly site of me cursing and swearing and other more horrible sights. I only solved this (eventually) by reverting to the original default kernel 2.6.4-52 and mkinitrd 1.0-197. I have read about some of the other kernel issues here and my question is whether I should now simply stay with this kernel and mkinitrd version to avoid further issues? Thanks John __________ This email has been pre-scanned using the latest Anti Virus software for your peace of mind.
On Tuesday 24 August 2004 01:29, John wrote:
I have read about some of the other kernel issues here and my question is whether I should now simply stay with this kernel and mkinitrd version to avoid further issues?
Install a new kernel manually with the command rpm -ihv kernel-default_XXXX.iX86.rpm The -i option keeps the *current* kernel, and installs the new kernel alongside. The previous kernel will be accessible as vmlinuz.previous and initrd.previous, while the new kernel will be accessible as vmlinuz and initrd. The next step is rebooting your pc to see if the new kernel does not cause problems, and if it does, the previous kernel is still accessible. It might be handy to add a 'Boot previous kernel'-entry in /boot/grub/menu.lst. It is possible to have more than 2 kernels installed. Cheers, Leen
On Tuesday 24 August 2004 01:29, John wrote:
I have read about some of the other kernel issues here and my question is whether I should now simply stay with this kernel and mkinitrd version to avoid further issues?
Install a new kernel manually with the command
rpm -ihv kernel-default_XXXX.iX86.rpm
The -i option keeps the *current* kernel, and installs the new kernel alongside.
The previous kernel will be accessible as vmlinuz.previous and initrd.previous, while the new kernel will be accessible as vmlinuz and initrd.
The next step is rebooting your pc to see if the new kernel does not cause problems, and if it does, the previous kernel is still accessible.
It might be handy to add a 'Boot previous kernel'-entry in /boot/grub/menu.lst.
It is possible to have more than 2 kernels installed.
Cheers,
Leen
Hi Leen, Thanks kindly for that advice, I will certainly try that method and keep the instructions. Kind regards, John __________ This email has been pre-scanned using the latest Anti Virus software for your peace of mind.
participants (2)
-
John
-
Leendert Meyer