[opensuse] Kernel update
Hi, I am running suse 11.1 on this laptop. I have found that if I update the computer, the cooling fans stop running and never come on again after reboot. I have traced this to a recent kernel update from 2.6.27.45-0.1 to 2.6.27.48. If I downgrade to the previous kernel to get the fans back on, the new kernel always shows up as an patch available. If I update all packages, the kernel gets updated. Is there a way to prevent this kernel from upgrading from 2.6.27.45 in yast? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Mark Misulich <munguanaweza@gmail.com> [10-17-10 23:32]:
I am running suse 11.1 on this laptop. I have found that if I update the computer, the cooling fans stop running and never come on again after reboot. I have traced this to a recent kernel update from 2.6.27.45-0.1 to 2.6.27.48. If I downgrade to the previous kernel to get the fans back on, the new kernel always shows up as an patch available. If I update all packages, the kernel gets updated.
Is there a way to prevent this kernel from upgrading from 2.6.27.45 in yast?
Lock it. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2010-10-17 at 23:29 -0400, Mark Misulich wrote:
Is there a way to prevent this kernel from upgrading from 2.6.27.45 in yast?
Taboo. And a Bugzilla to get the regression solved, eventually. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky8Br8ACgkQtTMYHG2NR9UNBQCfblh9rzuTLys7R3kM6cD9ENMB dvgAn2I4ALv3M75v7HnqvGfXf5Jbh/Lo =XdRq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-10-18 at 10:35 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday, 2010-10-17 at 23:29 -0400, Mark Misulich wrote:
Is there a way to prevent this kernel from upgrading from 2.6.27.45 in yast?
Taboo.
And a Bugzilla to get the regression solved, eventually.
- -- Cheers, Carlos E. R.
Hi, well, what I meant was that if I click on yast>online updates, what next presents are patches. I can click on it and place a taboo on it. If I then select package groups>all packages, then from the file menu select package>all in this list>update if newer package available, the taboo I just placed on the kernel patch is overridden. I also have a taboo on installing libflashsupport and strigi, but these also are overridden and I have to go back and place taboos on these again. I can go back and reset the patch not to install, but even after doing this I still have the kupdaterapplet showing that there are new software updates available, even though I have placed taboos on updating the kernel. So, how do I make this all more permanent so that the software understands that I really mean it when I place taboos and say don't update these. So don't present me with updates for software that I don't want to update. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Mark Misulich <munguanaweza@gmail.com> [10-18-10 09:10]: ...
I can go back and reset the patch not to install, but even after doing this I still have the kupdaterapplet showing that there are new software updates available, even though I have placed taboos on updating the kernel.
So, how do I make this all more permanent so that the software understands that I really mean it when I place taboos and say don't update these. So don't present me with updates for software that I don't want to update.
use zypper from the cl: as root zypper al <kernel-version##> kernel-desktop-2.6.35.1-3.1.x86_64 yast will respect the locks, at least in my experience :^) -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-10-18 at 09:08 -0400, Mark Misulich wrote: ...
So, how do I make this all more permanent so that the software understands that I really mean it when I place taboos and say don't update these. So don't present me with updates for software that I don't want to update.
Create a fake rpm of the same name and a much higer version number, and install it. This will fool any rpm installer or updater. I have used that trick years ago, sucessfully. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAky8S2cACgkQtTMYHG2NR9V31wCgk8Xy4BFUMmzMccMQ1vEU7SQw g3sAoJk1EzVDGvUoh0dDscJrwe9Mp3dh =/sOz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-10-18 at 10:35 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday, 2010-10-17 at 23:29 -0400, Mark Misulich wrote:
Is there a way to prevent this kernel from upgrading from 2.6.27.45 in yast?
Taboo.
And a Bugzilla to get the regression solved, eventually.
- -- Cheers, Carlos E. R.
Hi, I tried Patrick's suggestion as below: use zypper from the cl: as root zypper al <kernel-version##> kernel-desktop-2.6.35.1-3.1.x86_64 but it didn't work, yast still updates the kernel to the later version. How may I remove these zypper locks? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Mark Misulich <munguanaweza@gmail.com> [10-22-10 13:47]:
I tried Patrick's suggestion as below:
use zypper from the cl: as root zypper al <kernel-version##> kernel-desktop-2.6.35.1-3.1.x86_64
but it didn't work, yast still updates the kernel to the later version. How may I remove these zypper locks?
zypper rl <kernel-version##> ps: *most* cl apps provide help via- app --help in this case zypper --help zypper al --help ... gud luk, -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2010-10-22 at 13:46 -0400, Mark Misulich wrote:
but it didn't work, yast still updates the kernel to the later version. How may I remove these zypper locks?
I will not say: why don't you simply ask zypper for help and look for your self? Just 10 seconds. zypper --help - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkzB334ACgkQtTMYHG2NR9XtCgCfUnzJqid42Ss0uB6e6ckGGHMn 7g4An1KwtL0Q78YayCp1AJx+M49zMuK3 =Bb1B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2010-10-22 at 21:01 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Friday, 2010-10-22 at 13:46 -0400, Mark Misulich wrote:
but it didn't work, yast still updates the kernel to the later version. How may I remove these zypper locks?
I will not say: why don't you simply ask zypper for help and look for your self? Just 10 seconds.
zypper --help Well, I did do Zypper man and found the command
#zypper rl and tried that, but it didn't work. Zypper stalled and then timed out without removing the lock. I thought that I must have had the wrong command, so I asked for help. I tried it again later, and it worked. So whatever was wrong, fixed itself. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2010-10-22 at 15:13 -0400, Mark Misulich wrote:
Well, I did do Zypper man and found the command
#zypper rl
and tried that, but it didn't work. Zypper stalled and then timed out without removing the lock. I thought that I must have had the wrong command, so I asked for help.
You could have said that...
I tried it again later, and it worked. So whatever was wrong, fixed itself.
Maybe it was refreshing, or the database was locked while used by another process. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkzCH9oACgkQtTMYHG2NR9VFpgCeOcce9ksTbDuDR3tEJen4b+NO IWQAniiW1omg+tc3zW7yaLyeSXYkrLTt =kK05 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Carlos E. R. -
Mark Misulich -
Patrick Shanahan