Thank you Stefan for clearing this up for me. Indeed, building against HEAD is arguably an overkill.
So am I getting this correct that NVidia drivers' breakage is detected proactively after all? If so, does nVidia driver breakage prevent a Tumbleweed snapshot from being released?
Thank you in advance.
On Tue, Apr 16, 2019 at 6:05 PM Stefan Dirsch firstname.lastname@example.org wrote:
On Tue, Apr 16, 2019 at 05:14:34PM +0300, Andrei Dziahel wrote:
See, having them distributed separately is just fine (by me).
What is not quite OK is that when kernel breaks NVIDIA kernel module, there seems to be no way for anyone to know that, except via tracking that rglinuxtech blog (/cc sndirtsch@suse: am I correct?). You guys probably do have an in-house SUSE-only OBS installation, do you? If so, it is feasible to set up continuous builds of https://build.opensuse.org/project/show/X11:Drivers:Video against https://build.opensuse.org/project/show/Kernel:HEAD in there, isn't it?
We do test build against Tumbleweed, which I believe should be sufficient. How many users are using bleeding edge Kernel:HEAD and are expecting NVIDIA drivers running afterwards?
When installing the Tumbleweed NVIDIA driver RPMs after a kernel update a rebuild of the NVIDIA kernel modules is triggered, so unless changes in the kernel break the build of the driver, things are working also after a reboot of the new kernel. Luckily breaking the build doesn't happen so often. In this case I'm seing the failure in the TW test build, fix it ASAP and push the RPMs to NVIDIA immediately.
Hope this helps.
On Wed, Mar 20, 2019 at 2:33 AM Simon Lees email@example.com wrote:
On 20/03/2019 03:04, Andrei Dziahel wrote:
Had anyone at SUSE tried to reach NVIDIA asking them for permission to use desktop drivers in openQA so failing to build kernel module of theirs would be soft fail at least?
The issue in some way is less a nvidia thing and more a kernel developer / licensing thing, in the past some kernel developers have felt that the nvidia driver violates the kernels licensing terms, as such openSUSE has respected the kernel developers with this opinion by not shipping / having nvidia drivers running within the openSUSE project. Atleast thats my recollection, I could remember wrong.
On Tue, Mar 19, 2019 at 1:25 PM Mathias Homann Mathias.Homann@opensuse.org wrote:
Am 2019-03-19 11:01, schrieb Stasiek Michalski:
> On the third hand, all the stuff I read on the opensuse lists about > tumbleweed > and its "quirks" is why I'm *not* using tumbleweed. > > - nvidia and tumbleweed kernels
Maybe somebody will realize at some point that dkms is a better option with a distro that changes kernels every week.
AFAIK the nvidia drivers already use DKMS, and build "on the fly" when you install/upgrade the package. Problem is, Kernel 5.x did "something" that might break nvidia drivers...
I've been told that it does not concern the desktop drivers, but what I've seen on the -factory list suggests otherwise.
anyway, it's just so much more convenient for end users to get an automated package update to trigger the process than doing it manually - been there, done that for years until suse started having packages. This way all I have to do is click on the little rocket in ansible tower. Once. For X machines. ;)
Simon Lees (Simotek) http://simotek.net
Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: firstname.lastname@example.org To contact the owner, e-mail: email@example.com
-- Regards, Andrei Dziahel
-- Regards, Stefan Dirsch
Public Key available
Stefan Dirsch (Res. & Dev.) SUSE LINUX GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany
SUSE Linux GmbH, GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg)