On Thu, Feb 1, 2024 at 5:49 PM Leigh Scott wrote:
>
> > Thanks for holding the push to testing, I have managed to patch nvidia
> > 545.xx and
> > 550.xx so
> 470.xx is also patched.
>
> I think it is ok to push the new kernel to testing, the legacy nvidia drivers
> shouldn't hold up the new
On 2/2/24 10:48, Leigh Scott wrote:
Thanks for holding the push to testing, I have managed to patch nvidia 545.xx
and
550.xx so
470.xx is also patched.
I think it is ok to push the new kernel to testing, the legacy nvidia drivers
shouldn't hold up the new kernel.
Thank you for doing this
> Thanks for holding the push to testing, I have managed to patch nvidia 545.xx
> and
> 550.xx so
470.xx is also patched.
I think it is ok to push the new kernel to testing, the legacy nvidia drivers
shouldn't hold up the new kernel.
--
___
devel
> On Thu, Feb 1, 2024 at 1:45 AM Leigh Scott wrote:
>
> This is not accurate. The 6.7.3 (and 6.6.15) updates did break the
> nvidia driver. It has nothing to do with debugging being enabled. A
> proper and valid bugfix:
>
> 5ec8e8ea8b7783fab150cf86404fc38cb4db8800 mm/sparsemem: fix race in
>
On Thu, Feb 1, 2024 at 1:45 AM Leigh Scott wrote:
>
> Kernel-6.7.3 still has debugging enabled which will break the nvidia driver
This is not accurate. The 6.7.3 (and 6.6.15) updates did break the
nvidia driver. It has nothing to do with debugging being enabled. A
proper and valid bugfix:
Kernel-6.7.3 still has debugging enabled which will break the nvidia driver
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6859
https://forums.developer.nvidia.com/t/linux-6-7-beta-550-40-07-error-modpost-gpl-incompatible-module-nvidia-ko-uses-gpl-only-symbol-rcu-read-lock/280908
--
Hey Folks,
As most of you might know, Kernel 6.7 Test Week is currently happening[0]
I have figured out that, I can't login to FAS from the Kernel Test
Result site[1].
If you are also someone who is stuck, please follow the infra issue
filed here[2].
And please submit the results here[3]
If you