* Aaron Digulla
Am 20.06.22 um 00:34 schrieb Peter Maffter:
Am 19.06.22 um 22:10 schrieb Per Jessen:
The challenge for openSUSE is to let people fix what ain't broke - without breaking it.
So how can I as a simple user fix the compile errors that nVidia drivers have with the new kernel 5.18.1?
Would it have been very hard for Suse to check and give me some information like: "We Tumbleweed guys tested current nVidia drivers with this new kernel. It does not work. It throws compile errors. So for the time being and for your benefit we will not install 5.18.1 on your machine and keep the older kernel. Please read here: <some further Suse information about this problem>" ?
I run into this once or twice per year which is not that bad and extremely infuriating when it happens.
From my point of view, the main problem is that most updates run without a hitch. So when it happens, I usually want to do something. And I can't because the computer behaves oddly. Since this is rare, I don't do a full backup before every update.
Now I have an unknown problem and must spend time to find out what it is instead of doing what I planned to do.
The next problem is that my PC knows what's wrong (it has written an error somewhere) but I have to find this error, first. It's also not always clear which of the many errors that I find are the reason for the current problem. So there is a lot of knowledge involved which the opensuse devs have - so many issues are obvious for them - but not for me.
Anyway.
I think there are two solutions for this "package X often breaks when Y is also installed" problem:
a) Set up an automated build system tries to compiles all the involved packages when one of them changes.
For NVIDIA, you'd need a server somewhere with an NVIDIA card installed. NVIDIA should be able and willing to set this up - this would help their business.
If this build fails, it's not allowed to push the new package(s) to any repo.
The obvious drawback here is that it could block security fixes in the kernel which would work for all those people without an nvidia driver.
b) Add a mechanism to zypper or rpm for brittle&important package combinations where someone says "I tested this combination and it works" or maybe even "we know this combination won't work; don't try".
If the computer which is running "zypper up" has a different combination, it should stop and warn the person trying to update. If the combinations is known broken, zypper should refuse to continue.
Maybe people running opensuse could get a tool to report "works for me" and "fails for me" to get more combinations into the system that are good or dangerous.
fwiw: I have utilized nvidia for many years and it is not uncommon for any particular nvidia card to fail for a particular kernel/driver or for the driver to be issued somewhat late. that said, it is infrequent and is simple to boot the previous kernel and not be concerned with anything else. soon another driver and/or kernel will be issued and solve the problem. the important thing is to accurately report the conditions and equipment so the maintainers may determine the correction needed. emphasis on "accurately report the conditions and equipment" it is virtually impossible to test against all possible conditions! -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc