Folks, Here's another fun one. I made the mistake of letting YOU run "hands free". Among other things, it installed the 2.4.199 kernel. This broke several things on my system. Is there any reasonable way to "downgrade" to 2.4.166? I tried just booting the alternate kernel, and got a panic of not being able to mount the root OS. I'm guessing the answer is No, but thought I'd check. -- -Josh Berkus Aglio Database Solutions San Francisco
On Thursday 15 April 2004 01.05, Josh Berkus wrote:
Folks,
Here's another fun one.
I made the mistake of letting YOU run "hands free". Among other things, it installed the 2.4.199 kernel. This broke several things on my system. Is there any reasonable way to "downgrade" to 2.4.166? I tried just booting the alternate kernel, and got a panic of not being able to mount the root OS.
I'm guessing the answer is No, but thought I'd check.
Yes, of course you can. Just grab the 2.4.21-166 rpm from somewhere and "rpm -Uvh --oldpackage" it. Two points though, if it really did break things, you should report it to suse (or to this list) with more details on the error message, and secondly, I believe the current version in update is 2.4.21-202, so maybe whatever problem you have is already fixed?!
Anders,
Yes, of course you can. Just grab the 2.4.21-166 rpm from somewhere and "rpm -Uvh --oldpackage" it.
Ok, will try.
Two points though, if it really did break things, you should report it to suse (or to this list) with more details on the error message, and secondly, I believe the current version in update is 2.4.21-202, so maybe whatever problem you have is already fixed?!
Hmmm ... not likely. The two things it broke were: Win4Lin -- they don't have a SuSE 2.4.199 kernel yet, and MadWifi drivers -- some compiling problem on 2.4.199 that I'm not eager to debug right now. -- -Josh Berkus Aglio Database Solutions San Francisco
Anders,
Yes, of course you can. Just grab the 2.4.21-166 rpm from somewhere and "rpm -Uvh --oldpackage" it.
Hmmm. No good. The RPM did not update the /boot directory -- meaning that it wouldn't have booted, had I proceeded. Better stick with something that at least boots. -- -Josh Berkus Aglio Database Solutions San Francisco
On Thursday 15 April 2004 02.06, Josh Berkus wrote:
Anders,
Yes, of course you can. Just grab the 2.4.21-166 rpm from somewhere and "rpm -Uvh --oldpackage" it.
Hmmm. No good. The RPM did not update the /boot directory -- meaning that it wouldn't have booted, had I proceeded.
I beg your pardon? I've installed several dozen suse kernel rpms, and I've never seen one yet that didn't update /boot. Is /boot on a separate partition, and was in mounted when you installed the rpm?
Better stick with something that at least boots.
I thought you said you had run 2.4.21-166 before and it worked?!
Anders,
I beg your pardon? I've installed several dozen suse kernel rpms, and I've never seen one yet that didn't update /boot. Is /boot on a separate partition, and was in mounted when you installed the rpm?
It's on the same partition. The package I installed is kernel-source-2.4.166-i586.rpm. There isn't another kernel package that I can find, on my system or off it. To demonstrate: temoku:/var/lib/YaST2/you/mnt/i386/update/9.0/rpm/i586 # rpm -Uvh --force kernel-source-2.4.21-166.i586.rpm Preparing... ########################################### [100%] 1:kernel-source ########################################### [100%] temoku:/var/lib/YaST2/you/mnt/i386/update/9.0/rpm/i586 # cd /boot temoku:/boot # ls . initrd-2.4.21-199-default .. initrd.shipped Kerntypes-2.4.21-199-default lost+found System.map message System.map-2.4.19-4GB.pre-win4lin vmlinux-2.4.21-199-default.gz System.map-2.4.21-199-default vmlinuz System.map.win4lin vmlinuz-2.4.21-199-default boot vmlinuz.shipped config-2.4.21-199-default win4lin grub win4lin.config initrd As you can see, boot still has the same vmlinuz etc. -- -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Enterprise vertical business josh@agliodbs.com and data analysis solutions (415) 752-2387 and database optimization fax 651-9224 utilizing Open Source technology San Francisco
On Thursday 15 April 2004 02.30, Josh Berkus wrote:
Anders,
I beg your pardon? I've installed several dozen suse kernel rpms, and I've never seen one yet that didn't update /boot. Is /boot on a separate partition, and was in mounted when you installed the rpm?
It's on the same partition. The package I installed is kernel-source-2.4.166-i586.rpm. There isn't another kernel package that I can find, on my system or off it.
To demonstrate:
temoku:/var/lib/YaST2/you/mnt/i386/update/9.0/rpm/i586 # rpm -Uvh --force kernel-source-2.4.21-166.i586.rpm Preparing... ########################################### [100%] 1:kernel-source ########################################### [100%] temoku:/var/lib/YaST2/you/mnt/i386/update/9.0/rpm/i586 # cd /boot temoku:/boot # ls . initrd-2.4.21-199-default .. initrd.shipped Kerntypes-2.4.21-199-default lost+found System.map message System.map-2.4.19-4GB.pre-win4lin vmlinux-2.4.21-199-default.gz System.map-2.4.21-199-default vmlinuz System.map.win4lin vmlinuz-2.4.21-199-default boot vmlinuz.shipped config-2.4.21-199-default win4lin grub win4lin.config initrd
As you can see, boot still has the same vmlinuz etc.
Indeed, because the package kernel-source contains not the actual kernel, but the kernel source. You want a package called either k_deflt-2.4.21-166 or k_athlon-2.4.21-166 or k_smp-2.4.21-166, depending on your architecture (k_athlon for AMD machines, k_smp for multi-CPU machines, and k_deflt for everything else)
Anders,
You want a package called either k_deflt-2.4.21-166 or k_athlon-2.4.21-166 or k_smp-2.4.21-166, depending on your architecture (k_athlon for AMD machines, k_smp for multi-CPU machines, and k_deflt for everything else)
Aha. Ok, I presume that I'll want to install the kernel_source package at the same time? In any case, I think I'll wait until I have some means of backing this system up. -- -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Enterprise vertical business josh@agliodbs.com and data analysis solutions (415) 752-2387 and database optimization fax 651-9224 utilizing Open Source technology San Francisco
On Thursday 15 April 2004 02.36, Josh Berkus wrote:
Anders,
You want a package called either k_deflt-2.4.21-166 or k_athlon-2.4.21-166
or
k_smp-2.4.21-166, depending on your architecture (k_athlon for AMD machines, k_smp for multi-CPU machines, and k_deflt for everything else)
Aha. Ok, I presume that I'll want to install the kernel_source package at the same time?
You just did :) The sources are now in /usr/src/linux-2.4.21-166 and yes, since you said you were going to compile a third party driver, you'll need the kernel source. You'll also need to prepare it with cd /usr/src/linux make mrproper make cloneconfig make dep before you compile the driver (after you've rebooted to the new/old kernel)
In any case, I think I'll wait until I have some means of backing this system up.
always a good idea when you do big changes like upgrade a kernel or glibc
On Wednesday 14 April 2004 16:15, Anders Johansson wrote:
On Thursday 15 April 2004 02.06, Josh Berkus wrote:
Anders,
Yes, of course you can. Just grab the 2.4.21-166 rpm from somewhere and "rpm -Uvh --oldpackage" it.
Hmmm. No good. The RPM did not update the /boot directory -- meaning that it wouldn't have booted, had I proceeded.
I beg your pardon? I've installed several dozen suse kernel rpms, and I've never seen one yet that didn't update /boot. Is /boot on a separate partition, and was in mounted when you installed the rpm?
I can guarentee that this does not always work in a downgrade situation as I had the same problem downgrading a kernal after I let YOU upgrade it. (YOU mistakenly installed a Athelon kernal on a SMP machine.) Nothing in /boot was upgraded, and as a consequence the old kernal tried to boot, but was not found.. Big mess. Rescue CD saved the day and I had to forceably install the old kernal again. So don't be so sure this always works untill you've tried a downgrade or two. -- _____________________________________ John Andersen
On Thursday 15 April 2004 03.37, John Andersen wrote:
On Wednesday 14 April 2004 16:15, Anders Johansson wrote:
On Thursday 15 April 2004 02.06, Josh Berkus wrote:
Anders,
Yes, of course you can. Just grab the 2.4.21-166 rpm from somewhere and "rpm -Uvh --oldpackage" it.
Hmmm. No good. The RPM did not update the /boot directory -- meaning that it wouldn't have booted, had I proceeded.
I beg your pardon? I've installed several dozen suse kernel rpms, and I've never seen one yet that didn't update /boot. Is /boot on a separate partition, and was in mounted when you installed the rpm?
I can guarentee that this does not always work in a downgrade situation as I had the same problem downgrading a kernal after I let YOU upgrade it. (YOU mistakenly installed a Athelon kernal on a SMP machine.) Nothing in /boot was upgraded, and as a consequence the old kernal tried to boot, but was not found.. Big mess. Rescue CD saved the day and I had to forceably install the old kernal again.
So don't be so sure this always works untill you've tried a downgrade or two.
I've tried a lot more than two. When you're playing with the latest mantel kernels, you frequently find versions that fail miserably, forcing you to downgrade. If nothing was modified in /boot, then you did something wrong.
On Wednesday 14 April 2004 17:41, Anders Johansson wrote:
On Thursday 15 April 2004 03.37, John Andersen wrote:
On Wednesday 14 April 2004 16:15, Anders Johansson wrote:
On Thursday 15 April 2004 02.06, Josh Berkus wrote:
Anders,
Yes, of course you can. Just grab the 2.4.21-166 rpm from somewhere and "rpm -Uvh --oldpackage" it.
Hmmm. No good. The RPM did not update the /boot directory -- meaning that it wouldn't have booted, had I proceeded.
I beg your pardon? I've installed several dozen suse kernel rpms, and I've never seen one yet that didn't update /boot. Is /boot on a separate partition, and was in mounted when you installed the rpm?
I can guarentee that this does not always work in a downgrade situation as I had the same problem downgrading a kernal after I let YOU upgrade it. (YOU mistakenly installed a Athelon kernal on a SMP machine.) Nothing in /boot was upgraded, and as a consequence the old kernal tried to boot, but was not found.. Big mess. Rescue CD saved the day and I had to forceably install the old kernal again.
So don't be so sure this always works untill you've tried a downgrade or two.
I've tried a lot more than two. When you're playing with the latest mantel kernels, you frequently find versions that fail miserably, forcing you to downgrade.
If nothing was modified in /boot, then you did something wrong.
Exactly my point YOU (Yast Online Update) did something wrong. I had to correct it manually by rebuilding my grub scripts. -- _____________________________________ John Andersen
participants (3)
-
Anders Johansson -
John Andersen -
Josh Berkus