Hm?
You wrote yourself that it got uninstalled when you selected it for installation…
Again, what packages do you actually have installed now?
rpm -qa | grep -E "kmp|kernel"
What did I misunderstand?
I don’t know, I don’t see what you are doing.
Maybe you misunderstand YaST’s symbols/icons, i.e. what install and delete means…
But just to be clear: we are talking about YaST->Software Management here, right?
Not YaST->Online Update, which purpose is to make sure all official updates (“patches”) get installed and therefore has a different behavior.
I tried that last night. Same result. Yast simply cancels the “lock” and upgrades to versions that don’t work on this machine.
YaST should not simply cancel the lock, only if it is necessary (but even then it would ask you).
Unless you actually used YaST->Online Update…
Regarding “versions that don’t work on this machine”: what actual problems do you have with kernel 3.16.7-48.1?
This one should work, 3.16.7-45.1 was broken.
zypper lr -d
With this repo list you do not get updates that “contained a mixture of versions including possibly 13.2, “LEAP”, and who knows what else”.
You only get updates intended for 13.2.
Entirely possible, since anything I’ve tried since that v45 “upgrade” has failed.
It is YaST Software Management, not YaST Online Update.
These packages need to be installed:
yast2-online-update-configuration
So I don’t even have a full install of Online Update (?). Never have opened it up before 5 minutes ago.
Yeh, I get it - “would”, “should”, “could”, “ought”, “might”… and when it “asks me” the options always include upgrading to 3.16.7-48.1 or not making the change.
Primary problem is network connection; every time there’s a major kernel change I have to re-install the (0005-r8168-8.042.00.tar.bz2) driver for my realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (on motherboard) which uses the r8168 driver which is NOT included in the recent kernels. The kernel includes r8169 which is absolutely incompatible with my hardware.
kernel 3.16.7-48.1 does not even detect a NIC, so how do I install a driver for a non-existent NIC?
Other notable problem is sound unconfigurable in 3.16.7-48.1. I don’t know why, and haven’t been booted up with it long enough to notice all faults.
Well, SOMETHING in 3.16.7-45.1 certainly included something extra, just considering the download time and errors/fails. SUSE Paste
Tell it to install kernel-desktop-3.16.7-42.1 rather, then answer to uninstall kernel-desktop-base when you’re asked.
Been there, did that. It doesn’t ask me anything, just uncontrollably updates to 3.16.7-48.
The next thing I’m going to do is uninstall virtualbox-guest-kmp-default-5.0.26_k3.16.7_42-51.1.x86_64 … if it lets me.
Do you really need all those kmp packages?
Better remove them if not.
xen-kmp-desktop is what pulls the unwanted kernels in, because you have it installed for kernel 3.16.7-45.1 and 3.16.7-48.1 (so YaST needs to install kernel-desktop(-base)-3.16.7-45.1 and -48.1 to fulfill the dependencies).
virtualbox-guest-kmp-default is useless for you anyway, first it is not needed on the host, and second it is for kernel-default.
Speaking of that, better remove kernel-default too.
[FONT=Lucida Grande]kernel 3.16.7-48.1 does not even detect a [/FONT]NIC, so how do I install a driver for a non-existent NIC?
Just like you would if it would detect it.
And it should detect it afterwards I think.
Though if weak-updates is working properly, it should create a symlink to the kernel module for the newer kernel (if it’s compatible).
Yeh, I get it - “would”, “should”, “could”, “ought”, “might”… and when it “asks me” the options always include upgrading to 3.16.7-48.1 or not making the change.
So it did ask you and not removed the lock all by itself.
And if kernel 3.16.7-48.1 is required by something you install, there are only those two options, install kernel 3.16.7-48.1 too or don’t make a change at all.
Should be obvious, no?
Other notable problem is sound unconfigurable in 3.16.7-48.1.
And what does that mean?
3.16.7-45.1’s bug caused sound not working for normal users, it should work fine with 3.16.7-48.1 (as others have confirmed, and I can confirm too).
What exactly is unconfigurable where?
Yes, I’ve also been “burnt” by the “POSIX ACL support broken by kernel-desktop-3.16.7-45” issue and the issues around “removing the ‘bad’ kernel version”.
It seems that, when deleting “bad” kernel (and other Multi-Version things such as Oracle’s VirtualBox), the only way to proceed safely and correctly, is to use the following method in YaST Software Manager: *View -->> Package Groups -->> Multiversion Packages
*[HR][/HR]By the way, I got “badly burnt” by the KDE4 Plasma behaviour due to the “POSIX ACL” issue:
The KDE4 Plasma desktop lost it’s appearance settings.
Hm?
Can you be a but more specific?
What “quirk” is there, and what things does it break?
The link you gave doesn’t mention anything in this regard, and it would be news to me either.
It seems that, when deleting “bad” kernel (and other Multi-Version things such as Oracle’s VirtualBox), the only way to proceed safely and correctly, is to use the following method in YaST Software Manager: *View –>> Package Groups –>> Multiversion Packages
*
This is one way (and it is a good way to find all multiversion packages), but definitely not the only one that works.
In the end, regarding (un)installation it doesn’t do anything different than Search->kernel->Versions would.
By the way, I got “badly burnt” by the KDE4 Plasma behaviour due to the “POSIX ACL” issue:
The KDE4 Plasma desktop lost it’s appearance settings.
The “KDE Wallet Manager” lost it’s database.
KDE “Kontact” lost some of it’s “KMail” settings.
I find it hard to believe that those problems were caused by the kernel update.
AFAIK Plasma, Akonadi, and kwallet do not use ACLs.
Also I didn’t have those problems here (and yes, I did boot 3.16.7-45.1).
When I searched for “kernel” and deleted the 3.16.7-45.1 version there, YaST then proceeded to install the “kernel-desktop-base” 3.16.7-45.1 package as well as deleting the 3.16.7-45.1 “kernel-desktop” package.
Yes, everything was perfectly OK for a day or two with the 3.16.7-45.1 Desktop Kernel but, yesterday, before I had a chance to patch to 3.16.7-48, the KDE4 Plasma Desktop lost it’s settings and, after applying the 3.16.7-48 patch, KMail and KWallet misbehaved.
I didn’t revert to the previous (functioning) kernel version.
But this will also happen if you use View –>> Package Groups –>> Multiversion Packages.
As I already tried to explain a few times in this thread, if something (some kmp package) requires kernel-desktop-3.16.7-45.1, YaST (and zypper) will install kernel-desktop-base-3.16.7-45.1 instead to fulfill that dependency when you try to uninstall it.
Remove that “offending” kmp package as well, and it should work.
Yes, everything was perfectly OK for a day or two with the 3.16.7-45.1 Desktop Kernel but, yesterday, before I had a chance to patch to 3.16.7-48, the KDE4 Plasma Desktop lost it’s settings and, after applying the 3.16.7-48 patch, KMail and KWallet misbehaved.
Well, strange, and I have no idea why that would be.
But probably not related to the kernel IMHO.
Aaahhh!!
That was it! – In Multiversion Packages the VM packages were also listed and, I simultaneously deleted the related Oracle VirtualBox version as well – which is why it worked the 2nd time around . . .
kernel-desktop-3.16.6-2.1.x86_64 still shows here but YaST doesn’t show it.
Is there a cli code that will return the dependencies for kernel-desktop-3.16.6-2.1.x86_64 so I can delete them too … or am I treading in dangerous territory?
I don’t understand the term “weak-updates” - haven’t heard that one before.
I guess I was confused by the use of “ask”. I did get a dialog which allowed me to set the actions I wanted to see, but I never got the result I expected.
Now that I understand about having things installed that require things I’m trying to delete as dependencies, it makes sense and I’m going about cleaning up as much as I can.
Pegasus:~ # rpm -e --allmatches xen-kmp-desktop ipset-kmp-desktop virtualbox-guest-kmp-default kernel-default kernel-default-devel kernel-desktop-base
error: package xen-kmp-desktop is not installed
error: package ipset-kmp-desktop is not installed
error: package virtualbox-guest-kmp-default is not installed
error: package kernel-default is not installed
error: package kernel-desktop-base is not installed
Pegasus:~ #
Progress!
Only if you know what you’re doing. I am only an egg.
When I tried 3.16.7-48.1, sound card settings had no effect … no sound any way I tried.
I’ll start another post on that specific subject after I get network up in 3.16.7-48.1.
For this conversation I am running on 3.16.7-42.1.
Click on “Versions” below the package lists, and you should see all installed and available versions.
The normal view only shows the highest version.
Is there a cli code that will return the dependencies for kernel-desktop-3.16.6-2.1.x86_64 so I can delete them too … or am I treading in dangerous territory?
sudo rpm -e kernel-desktop-3.16.6
or
sudo zypper rm kernel-desktop-3.16.6
As explained in the link dcurtisfra posted.
I don’t understand the term “weak-updates” - haven’t heard that one before.
It’s a script that is being run on kernel updates, it tries to make all installed kernel modules available to all other kernels by creating appropriate symlinks.
The only errors/fails I see in there are related to virtualbox-guest-kmp-desktop, which is useless on real hardware anyway (and you removed it already now).
rpm wants the name of the package (maybe including the version number), which would be kernel-firmware or kernel-firmware-20141122git or kernel-firmware-20141122git-5.1 in this case.
But you should probably not uninstall kernel-firmware. This is necessary on many systems, as it includes firmware that’s required to operate/use certain hardware.
Does “rpm -qa” show only “installed” programs or also “available” ones?
Only the installed ones.
rpm doesn’t know anything about the configured repos.
A reference to a character in a book, “Stranger In A Strange Land” by Robert Heinlein, denoting a condition of Self as not yet fully-formed, with much yet to be learned.
Highly recommended reading…
I’ll do some more experimenting here with 3.16.7-48.1 and see what works - or not.
