Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
Hi, I'm not sure if this is an user error or my mirror is just outdated, so ignore this if it was already dealt with. I'm running stable, with the addition of pu to sources.list, setting its priority to 100 and pinning *nvidia* from pu with priority of 500. First, nvidia-cuda-dev and/or nvidia-cuda-toolkit (I was trying to follow the official debian wiki to install cuda) are not installable because they (or one of these packages) pull the tesla driver which is still the unpatched version and thus the build fails with the same GPL compliant error. Second, nvidia-driver-libs:i386 cannot be installed because some packages do not have an updated version available yet: > The following packages have unmet dependencies: > nvidia-driver-libs:i386 : Depends: libgl1-nvidia-glvnd-glx:i386 (= > 525.147.05-7~deb12u1) but it is not going to be installed >Depends: nvidia-egl-icd:i386 (= > 525.147.05-7~deb12u1) but it is not going to be installed >Recommends: libglx-nvidia0:i386 (= > 525.147.05-7~deb12u1) but it is not going to be installed >Recommends: libgles-nvidia1:i386 (= > 525.147.05-7~deb12u1) but it is not going to be installed >Recommends: libgles-nvidia2:i386 (= > 525.147.05-7~deb12u1) but it is not going to be installed >Recommends: libnvidia-encode1:i386 (= > 525.147.05-7~deb12u1) but it is not going to be installed >Recommends: nvidia-vulkan-icd:i386 (= > 525.147.05-7~deb12u1) but it is not going to be installed >Recommends: libnvidia-allocator1:i386 (= > 525.147.05-7~deb12u1) but it is not going to be installed > E: Unable to correct problems, you have held broken packages. Thanks, Zaha signature.asc Description: OpenPGP digital signature
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On 15/02/2024 19.54, Jonathan Wiltshire wrote: >Revised draft: ACK. This update addresses problems in three non-free driver packages supporing s/supporing/supporting/ Andreas
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
Hi, On Thu, Feb 15, 2024 at 05:48:37PM +, Dan Coleman wrote: > As a user facing this issue, I'd rather have the release as soon as possible. > It's already been a couple days. But that's just a user perspective! If you really can't wait another 24 hours, please feel free to install the packages from bookworm-proposed-updates and help with testing them. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On Thu, Feb 15, 2024 at 07:08:30PM +0100, Andreas Beckmann wrote: > On 15/02/2024 18.44, Jonathan Wiltshire wrote: > > On Thu, Feb 15, 2024 at 02:24:05PM +0100, Andreas Beckmann wrote: > > > On 14/02/2024 11.01, Jonathan Wiltshire wrote: > > > > On Sun, Feb 11, 2024 at 11:23:00PM +0100, Andreas Beckmann wrote: > > > > > We need to push 4 packages together to stable-updates: > > > > > nvidia-graphics-drivers > > > > > nvidia-settings > > > > > nvidia-graphics-drivers-tesla-470 > > > > > nvidia-graphics-drivers-tesla > > > > > > > > According to my list there's just nvidia-graphics-drivers-tesla missing > > > > now; does that match yours? > > > > > > Seems installable in sid now, so just uploaded to PU. These 4 should be > > > ready for stable-updates. > > > > Thanks; accepted all four, and the builds have just come in. > > > > I can release as early as tonight (19:52) but I don't know if that's a bit > > of a rush. Should I hang on until tomorrow evening in case of any > > late-breaking issues? > > Tomorrow is probably better. Agreed. > > We also need to put some thought into an announcement text. Here's a draft > > starting point: > > > > === > > This update addresses problems in four non-free packages to support nVidia > > graphics cards. > > three non-free driver packages ? Oh, I counted nvidia-graphics-drivers twice, sorry. > > The Linux kernel update included in Debian 12.5 marked two functions as > > GPL-only, making them inaccessible to non-free kernel modules. > not correct ... > > The Linux kernel update in Debian 12.5 changed an inlined function to call > two GPL-only symbols, making that function inaccessible to non-free kernel > modules. Yes, ok. > > As a result, > > the nVidia kernel modules cannot be built via DKMS at installation time for > > the updated kernel. > > > > This issue could not be resolved in time for the release of Debian 12.5. > > (And perhaps something along this:) > > Additionally src:nvidia-graphics-drivers and src:nvidia-settings have been > enabled to build for ppc64el, in order to turn > src:nvidia-graphics-drivers-tesla into transitional packages to ease future > updates. That's a bit wordy - I'll draft below. > > The following packages have been updated to correct the problem. > > > , as well as > > fixing detection of Tesla 470 compatibility: > Drop, that was a regression introduced in -6 and -6~deb12u1, it only existed > for a few days. Ok. Revised draft: === This update addresses problems in three non-free driver packages supporing nVidia graphics cards. The Linux kernel released in Debian 12.5 changed an inlined function to call two GPL-only symbols, making that function inaccessible to non-free kernel modules. As a result, the nVidia kernel modules cannot be built via DKMS at installation time for the updated kernel. This issue could not be resolved in time for the release of Debian 12.5. In addition, the source packages nvidia-graphics-drivers and nvidia-settings now build binaries for ppc64el, and nvidia-graphics-drivers-tesla builds transitional packages to ease future updates. The following packages have been updated to correct the problem: Source package Fixed version == = nvidia-graphics-drivers nvidia-graphics-drivers-tesla nvidia-graphics-drivers-tesla-470 nvidia-settings If you use the affected packages, we recommend you upgrade to these versions. === -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On 15/02/2024 18.44, Jonathan Wiltshire wrote: On Thu, Feb 15, 2024 at 02:24:05PM +0100, Andreas Beckmann wrote: On 14/02/2024 11.01, Jonathan Wiltshire wrote: On Sun, Feb 11, 2024 at 11:23:00PM +0100, Andreas Beckmann wrote: We need to push 4 packages together to stable-updates: nvidia-graphics-drivers nvidia-settings nvidia-graphics-drivers-tesla-470 nvidia-graphics-drivers-tesla According to my list there's just nvidia-graphics-drivers-tesla missing now; does that match yours? Seems installable in sid now, so just uploaded to PU. These 4 should be ready for stable-updates. Thanks; accepted all four, and the builds have just come in. I can release as early as tonight (19:52) but I don't know if that's a bit of a rush. Should I hang on until tomorrow evening in case of any late-breaking issues? Tomorrow is probably better. We also need to put some thought into an announcement text. Here's a draft starting point: === This update addresses problems in four non-free packages to support nVidia graphics cards. three non-free driver packages ? The Linux kernel update included in Debian 12.5 marked two functions as GPL-only, making them inaccessible to non-free kernel modules. not correct ... The Linux kernel update in Debian 12.5 changed an inlined function to call two GPL-only symbols, making that function inaccessible to non-free kernel modules. As a result, the nVidia kernel modules cannot be built via DKMS at installation time for the updated kernel. This issue could not be resolved in time for the release of Debian 12.5. (And perhaps something along this:) Additionally src:nvidia-graphics-drivers and src:nvidia-settings have been enabled to build for ppc64el, in order to turn src:nvidia-graphics-drivers-tesla into transitional packages to ease future updates. The following packages have been updated to correct the problem. , as well as fixing detection of Tesla 470 compatibility: Drop, that was a regression introduced in -6 and -6~deb12u1, it only existed for a few days. PackageFixed version ===== nvidia-graphics-drivers nvidia-graphics-drivers-tesla nvidia-graphics-drivers-tesla-470 nvidia-settings If you use the affected packages, we recommend you upgrade to these versions. === Feedback? Thanks,
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
Original Message On Feb 15, 2024, 12:44 PM, Jonathan Wiltshire < j...@debian.org> wrote: On Thu, Feb 15, 2024 at 02:24:05PM +0100, Andreas Beckmann wrote: > On 14/02/2024 11.01, Jonathan Wiltshire wrote: > > On Sun, Feb 11, 2024 at 11:23:00PM +0100, Andreas Beckmann wrote: > > > We need to push 4 packages together to stable-updates: > > > nvidia-graphics-drivers > > > nvidia-settings > > > nvidia-graphics-drivers-tesla-470 > > > nvidia-graphics-drivers-tesla > > > > According to my list there's just nvidia-graphics-drivers-tesla missing > > now; does that match yours? > > Seems installable in sid now, so just uploaded to PU. These 4 should be > ready for stable-updates. Thanks; accepted all four, and the builds have just come in. I can release as early as tonight (19:52) but I don't know if that's a bit of a rush. Should I hang on until tomorrow evening in case of any late-breaking issues? As a user facing this issue, I'd rather have the release as soon as possible. It's already been a couple days. But that's just a user perspective! We also need to put some thought into an announcement text. Here's a draft starting point: === This update addresses problems in four non-free packages to support nVidia graphics cards. The Linux kernel update included in Debian 12.5 marked two functions as GPL-only, making them inaccessible to non-free kernel modules. As a result, the nVidia kernel modules cannot be built via DKMS at installation time for the updated kernel. This issue could not be resolved in time for the release of Debian 12.5. The following packages have been updated to correct the problem, as well as fixing detection of Tesla 470 compatibility: Package Fixed version === == nvidia-graphics-drivers nvidia-graphics-drivers-tesla nvidia-graphics-drivers-tesla-470 nvidia-settings If you use the affected packages, we recommend you upgrade to these versions. === Feedback? Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1 -- To unsubscribe, send mail to 1063675-unsubscr...@bugs.debian.org.
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On Thu, Feb 15, 2024 at 02:24:05PM +0100, Andreas Beckmann wrote: > On 14/02/2024 11.01, Jonathan Wiltshire wrote: > > On Sun, Feb 11, 2024 at 11:23:00PM +0100, Andreas Beckmann wrote: > > > We need to push 4 packages together to stable-updates: > > > nvidia-graphics-drivers > > > nvidia-settings > > > nvidia-graphics-drivers-tesla-470 > > > nvidia-graphics-drivers-tesla > > > > According to my list there's just nvidia-graphics-drivers-tesla missing > > now; does that match yours? > > Seems installable in sid now, so just uploaded to PU. These 4 should be > ready for stable-updates. Thanks; accepted all four, and the builds have just come in. I can release as early as tonight (19:52) but I don't know if that's a bit of a rush. Should I hang on until tomorrow evening in case of any late-breaking issues? We also need to put some thought into an announcement text. Here's a draft starting point: === This update addresses problems in four non-free packages to support nVidia graphics cards. The Linux kernel update included in Debian 12.5 marked two functions as GPL-only, making them inaccessible to non-free kernel modules. As a result, the nVidia kernel modules cannot be built via DKMS at installation time for the updated kernel. This issue could not be resolved in time for the release of Debian 12.5. The following packages have been updated to correct the problem, as well as fixing detection of Tesla 470 compatibility: PackageFixed version ===== nvidia-graphics-drivers nvidia-graphics-drivers-tesla nvidia-graphics-drivers-tesla-470 nvidia-settings If you use the affected packages, we recommend you upgrade to these versions. === Feedback? Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On 14/02/2024 11.01, Jonathan Wiltshire wrote: On Sun, Feb 11, 2024 at 11:23:00PM +0100, Andreas Beckmann wrote: We need to push 4 packages together to stable-updates: nvidia-graphics-drivers nvidia-settings nvidia-graphics-drivers-tesla-470 nvidia-graphics-drivers-tesla According to my list there's just nvidia-graphics-drivers-tesla missing now; does that match yours? Seems installable in sid now, so just uploaded to PU. These 4 should be ready for stable-updates. Andreas
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On Sun, Feb 11, 2024 at 11:23:00PM +0100, Andreas Beckmann wrote: > We need to push 4 packages together to stable-updates: > nvidia-graphics-drivers > nvidia-settings > nvidia-graphics-drivers-tesla-470 > nvidia-graphics-drivers-tesla According to my list there's just nvidia-graphics-drivers-tesla missing now; does that match yours? Thanks, Jonathan -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
Hi Andreas, On Mon, Feb 12, 2024 at 12:37:44AM +0100, Andreas Beckmann wrote: > On 11/02/2024 21.36, Salvatore Bonaccorso wrote: > > If I can add a comment: I (but note I'm not wearing a > > nvidia-graphics-drivers maintainer hat) would support that, as there > > are enough people affected by this. This is quite unfortunate and I'm > > open to hear ideas how we can try to avoid such fallouts. > > I was aware of the bug (#1062932) but not of the fact a point release was > upcoming. Even if I had been aware of the point release I'm not sure if I > had realized the impact of this bug to make me yell ;-) > Perhaps once point release dates have been choosen, this could be announced > to d-d-a@ as well. > I'm not following debian-release@ ... -ENOTIME > > > As you know we are strictly following upstream stable series (and > > trying our best to keep an eye on as well regression reports upstream, > > but OOT modules are not explicitly tested, so neither the nvidia ones) > > Are autopkgtests being run for proposed-updates? That should have shown the > issue. Yes there are in fact autopkgtests being run, so this should have been catched (and at least decided what to do, i.e. not release 6.1.76-1, nod ideal, or deal during the still allowed window with the nvidia drivers as well). But to be very honest: I did miss this regression report on the overview page. At least according to Paul on IRC the test should have been run. > It was unfortunate that this upstream backported change appeared in > proposed-updates first and in sid only a few days later. And the > metapackages from linux-signed-amd64 are still depending on the version > before this change was introduced ... so I only could reproduce the issue > (and verify fixes) manually. (The module build test done during the package > build did not use the regressing headers.) Right, 6.6.15 upload to unstable had a couple of issues, first failing to build the arch:all packages then the linux-signed-amd64 were waiting to be processed, and once that happened, we have now a FTBFS due to interaction with a new kmod upload (Filled #1063804). It is not that usual that otherwise we would have that change in bookworm (queued in proposed-updates) before we had a similar change in unstable (or experimental). > Then I had to spent quite some time verifying that the issue only happened > on amd64 and since the 460 series (despite of ppc64el having even more calls > to pfn_valid() dating back to the 418 series). I would like to thank you again for the time you invested here to deal with that issue! > Andreas > > PS: @Salvatore: Looking forward to see some linux 6.8 packages in > experimental s.t. I can throw them in my module build chroot to see what > breaks next :-) Or do you already have some early build available somewhere > while experimental is still preparing 6.7? We have to move 6.7.y next to unstable. But I'm not completely sure if we are there yet, need to ask Bastian Blank about the plan. After that experimental is freed we can go aehad with 6.8.y for experimental, but there are yet no packages to test with :( Regards, Salvatore
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
Keeping an eye on the Release Calendar can help too: https://release.debian.org/release-calendar.ics Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On Mon, 2024-02-12 at 17:59 +, Jonathan Wiltshire wrote: > The point release dates go to > debian-stable-annou...@lists.debian.org which > is very low traffic. Actually, that's one place they *don't* go in advance. The first mail to -stable-announce is at the point that processing of uploads is already frozen. (They do go to -project@ldo, amongst others, which is also generally not too busy.) Sending to d-d-a would require a second mail in each case, as the main announcement is to debian-release@ BCCed to several other lists and team aliases. From memory of previous discussions, dda was avoided both for that reason and because it doesn't really capture the right audience (not everyone who cares about point releases is a DD, and "many" DDs don't particularly care about stable updates). If it would help, we could easily add an additional address to the notification list. Regards, Adam
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On Mon, Feb 12, 2024 at 12:37:44AM +0100, Andreas Beckmann wrote: > On 11/02/2024 21.36, Salvatore Bonaccorso wrote: > > If I can add a comment: I (but note I'm not wearing a > > nvidia-graphics-drivers maintainer hat) would support that, as there > > are enough people affected by this. This is quite unfortunate and I'm > > open to hear ideas how we can try to avoid such fallouts. > > I was aware of the bug (#1062932) but not of the fact a point release was > upcoming. Even if I had been aware of the point release I'm not sure if I > had realized the impact of this bug to make me yell ;-) > Perhaps once point release dates have been choosen, this could be announced > to d-d-a@ as well. > I'm not following debian-release@ ... -ENOTIME The point release dates go to debian-stable-annou...@lists.debian.org which is very low traffic. But I agree it's likely that it would have been a hidden problem anyway. > > As you know we are strictly following upstream stable series (and > > trying our best to keep an eye on as well regression reports upstream, > > but OOT modules are not explicitly tested, so neither the nvidia ones) > > Are autopkgtests being run for proposed-updates? That should have shown the > issue. > > It was unfortunate that this upstream backported change appeared in > proposed-updates first and in sid only a few days later. And the > metapackages from linux-signed-amd64 are still depending on the version > before this change was introduced ... so I only could reproduce the issue > (and verify fixes) manually. (The module build test done during the package > build did not use the regressing headers.) > > Then I had to spent quite some time verifying that the issue only happened > on amd64 and since the 460 series (despite of ppc64el having even more calls > to pfn_valid() dating back to the 418 series). > > Andreas > > PS: @Salvatore: Looking forward to see some linux 6.8 packages in > experimental s.t. I can throw them in my module build chroot to see what > breaks next :-) Or do you already have some early build available somewhere > while experimental is still preparing 6.7? -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On 11/02/2024 21.36, Salvatore Bonaccorso wrote: If I can add a comment: I (but note I'm not wearing a nvidia-graphics-drivers maintainer hat) would support that, as there are enough people affected by this. This is quite unfortunate and I'm open to hear ideas how we can try to avoid such fallouts. I was aware of the bug (#1062932) but not of the fact a point release was upcoming. Even if I had been aware of the point release I'm not sure if I had realized the impact of this bug to make me yell ;-) Perhaps once point release dates have been choosen, this could be announced to d-d-a@ as well. I'm not following debian-release@ ... -ENOTIME As you know we are strictly following upstream stable series (and trying our best to keep an eye on as well regression reports upstream, but OOT modules are not explicitly tested, so neither the nvidia ones) Are autopkgtests being run for proposed-updates? That should have shown the issue. It was unfortunate that this upstream backported change appeared in proposed-updates first and in sid only a few days later. And the metapackages from linux-signed-amd64 are still depending on the version before this change was introduced ... so I only could reproduce the issue (and verify fixes) manually. (The module build test done during the package build did not use the regressing headers.) Then I had to spent quite some time verifying that the issue only happened on amd64 and since the 460 series (despite of ppc64el having even more calls to pfn_valid() dating back to the 418 series). Andreas PS: @Salvatore: Looking forward to see some linux 6.8 packages in experimental s.t. I can throw them in my module build chroot to see what breaks next :-) Or do you already have some early build available somewhere while experimental is still preparing 6.7?
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On 11/02/2024 23.13, Jonathan Wiltshire wrote: Yes, I've been watching the trickle of bugs being merged. As soon as Andreas has chance to upload I'll get it out via stable-updates and an SUA issued. src:nvidia-graphics-drivers is already in stable-NEW due to nvidia-suspend-common. We need to push 4 packages together to stable-updates: nvidia-graphics-drivers nvidia-settings nvidia-graphics-drivers-tesla-470 nvidia-graphics-drivers-tesla Andreas
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On Sun, Feb 11, 2024 at 09:36:02PM +0100, Salvatore Bonaccorso wrote: > If I can add a comment: I (but note I'm not wearing a > nvidia-graphics-drivers maintainer hat) would support that, as there > are enough people affected by this. This is quite unfortunate and I'm > open to hear ideas how we can try to avoid such fallouts. Yes, I've been watching the trickle of bugs being merged. As soon as Andreas has chance to upload I'll get it out via stable-updates and an SUA issued. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
Hi Jonathan, On Sun, Feb 11, 2024 at 12:29:45AM +, Jonathan Wiltshire wrote: > Control: tag -1 confirmed > > On Sat, Feb 10, 2024 at 11:00:58PM +0100, Andreas Beckmann wrote: > > [ Reason ] > > 1) A backported (by upstream) change in Linux 6.1.76 (included in > > today's point release) broke compilation of the non-free nvidia kernel > > module. A patched version of the driver is available in sid. > > > > 2) In order to simplify future maintenance of the many Nvidia driver > > packages (also in stable and oldstable) I'm going to remove the > > distinction between "normal" and "Tesla" drivers (they were at the > > same version in stable anyway). The Tesla specific bits > > (src:nvidia-graphics-drivers-tesla) will be merged into > > src:nvidia-graphics-drivers (that mainly means addition of the ppc64el > > architecture to these packages, and building some binary packages from > > src:nvidia-graphics-drivers instead: nvidia-powerd, nvidia-cuda-mps). > > nvidia-detect has been updated, too, as it no longer needs to > > distinguish the Tesla variants. > > There will be one further update to src:nvidia-graphics-drivers-tesla > > in stable that turns these packages into transitional packages depending > > on their counterparts from src:nvidia-graphics-drivers. (Separate PU > > request upcoming.) > > There will also be a PU request for nvidia-settings, as we need to > > enable building that on ppc64el. (The src:nvidia-settings-tesla package > > will then become obsolete.) > > > > 3) In order to better integrate the nvidia driver with the system power > > management, a new package nvidia-suspend-common is being introduced > > which properly ships and enables some systemd units that were previously > > only being shipped as examples. These power management changes are an > > enhancement for the 525 series, but seem to be required in the 535 > > series. (We will have to switch to the 535 LTSB series in stable soon, > > as 525 has reached EoL. 535 will be supported till mid 2026, so that will > > be the last driver branch switch for bookworm.) > > nvidia-suspend-common was already prepared in the previous pu update, > > but not yet enabled on stable as it hadn't undergone enough testing. As > > no new issues have popped up on sid, I'm confident to enable this in > > stable now. > > Please go ahead. Is this something we should release early through > stable-updates, given the breakage is caused by a point release? If I can add a comment: I (but note I'm not wearing a nvidia-graphics-drivers maintainer hat) would support that, as there are enough people affected by this. This is quite unfortunate and I'm open to hear ideas how we can try to avoid such fallouts. As you know we are strictly following upstream stable series (and trying our best to keep an eye on as well regression reports upstream, but OOT modules are not explicitly tested, so neither the nvidia ones) Regards, Salvatore
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
Control: tag -1 confirmed On Sat, Feb 10, 2024 at 11:00:58PM +0100, Andreas Beckmann wrote: > [ Reason ] > 1) A backported (by upstream) change in Linux 6.1.76 (included in > today's point release) broke compilation of the non-free nvidia kernel > module. A patched version of the driver is available in sid. > > 2) In order to simplify future maintenance of the many Nvidia driver > packages (also in stable and oldstable) I'm going to remove the > distinction between "normal" and "Tesla" drivers (they were at the > same version in stable anyway). The Tesla specific bits > (src:nvidia-graphics-drivers-tesla) will be merged into > src:nvidia-graphics-drivers (that mainly means addition of the ppc64el > architecture to these packages, and building some binary packages from > src:nvidia-graphics-drivers instead: nvidia-powerd, nvidia-cuda-mps). > nvidia-detect has been updated, too, as it no longer needs to > distinguish the Tesla variants. > There will be one further update to src:nvidia-graphics-drivers-tesla > in stable that turns these packages into transitional packages depending > on their counterparts from src:nvidia-graphics-drivers. (Separate PU > request upcoming.) > There will also be a PU request for nvidia-settings, as we need to > enable building that on ppc64el. (The src:nvidia-settings-tesla package > will then become obsolete.) > > 3) In order to better integrate the nvidia driver with the system power > management, a new package nvidia-suspend-common is being introduced > which properly ships and enables some systemd units that were previously > only being shipped as examples. These power management changes are an > enhancement for the 525 series, but seem to be required in the 535 > series. (We will have to switch to the 535 LTSB series in stable soon, > as 525 has reached EoL. 535 will be supported till mid 2026, so that will > be the last driver branch switch for bookworm.) > nvidia-suspend-common was already prepared in the previous pu update, > but not yet enabled on stable as it hadn't undergone enough testing. As > no new issues have popped up on sid, I'm confident to enable this in > stable now. Please go ahead. Is this something we should release early through stable-updates, given the breakage is caused by a point release? Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu Control: affects -1 + src:nvidia-graphics-drivers Control: block 1063363 with -1 Control: block 1062932 with -1 [ Reason ] 1) A backported (by upstream) change in Linux 6.1.76 (included in today's point release) broke compilation of the non-free nvidia kernel module. A patched version of the driver is available in sid. 2) In order to simplify future maintenance of the many Nvidia driver packages (also in stable and oldstable) I'm going to remove the distinction between "normal" and "Tesla" drivers (they were at the same version in stable anyway). The Tesla specific bits (src:nvidia-graphics-drivers-tesla) will be merged into src:nvidia-graphics-drivers (that mainly means addition of the ppc64el architecture to these packages, and building some binary packages from src:nvidia-graphics-drivers instead: nvidia-powerd, nvidia-cuda-mps). nvidia-detect has been updated, too, as it no longer needs to distinguish the Tesla variants. There will be one further update to src:nvidia-graphics-drivers-tesla in stable that turns these packages into transitional packages depending on their counterparts from src:nvidia-graphics-drivers. (Separate PU request upcoming.) There will also be a PU request for nvidia-settings, as we need to enable building that on ppc64el. (The src:nvidia-settings-tesla package will then become obsolete.) 3) In order to better integrate the nvidia driver with the system power management, a new package nvidia-suspend-common is being introduced which properly ships and enables some systemd units that were previously only being shipped as examples. These power management changes are an enhancement for the 525 series, but seem to be required in the 535 series. (We will have to switch to the 535 LTSB series in stable soon, as 525 has reached EoL. 535 will be supported till mid 2026, so that will be the last driver branch switch for bookworm.) nvidia-suspend-common was already prepared in the previous pu update, but not yet enabled on stable as it hadn't undergone enough testing. As no new issues have popped up on sid, I'm confident to enable this in stable now. [ Impact ] Users are unable to use the non-free nvidia module. [ Tests ] Only module building can be (and has been) tested. Everything else requires use of nvidia hardware and the driver. [ Risks ] This time there is no new upstream release involved, but some larger packaging changes which have been taken unchanged from sid. I prefer to not mix a new upstream version in there as well. [ Checklist ] [*] *all* changes are documented in the d/changelog [*] I reviewed all changes and I approve them [*] attach debdiff against the package in (old)stable [*] the issue is verified as fixed in unstable [ Changes ] nvidia-graphics-drivers (525.147.05-6~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. -- Andreas Beckmann Sat, 10 Feb 2024 22:03:15 +0100 nvidia-graphics-drivers (525.147.05-6) unstable; urgency=medium * Apply pfn_valid patch from gentoo to fix kernel module build for Linux 6.1.76, 6.6.15, 6.7.3, 6.8. (Closes: #1063363, #1062932) * nvidia-detect: Tesla and regular driver packages have been merged. * nvidia-detect: Add superficial autopkgtest for checking codename support. * Update lintian overrides. -- Andreas Beckmann Fri, 09 Feb 2024 20:43:30 +0100 nvidia-graphics-drivers (525.147.05-5) unstable; urgency=medium * Switch src:nvidia-graphics-drivers to the Tesla driver series. * Build for ppc64el. * Build all unversioned packages from src:nvidia-graphics-drivers. * Enable nvidia-suspend-common. (Closes: #1059581, #1056557, #1062281) * nvidia-suspend-common: Depend on kbd for chvt. (Closes: #1058081) * New Romanian (ro) debconf translations by Remus-Gabriel Chelu. (Closes: #1059590) -- Andreas Beckmann Tue, 23 Jan 2024 18:13:36 +0100 debian/README.source | 61 ++- debian/bug-control.mk | 4 +- debian/changelog | 406 +-- debian/control | 116 -- debian/control.in | 14 +- debian/control.md5sum | 8 +- debian/copyright | 8 +- debian/detect/nvidia-418.ids | 304 -- debian/detect/nvidia-470.ids | 439 - debian/detect/nvidia-detect.in | 117 +++--- debian/detect/nvidia-tesla.ids | 370 - debian/gbp.conf| 1 + debian/libnvidia-eglcore.lintian-overrides.in | 1 + debian/libnvidia-glcore.lintian-overrides.in | 1 + debian/not-installed.in| 17 - debian/nvidia-detect.install |
