AHS users: Liquorix kernel 6.12 in ahs-staging

[Stevo]

Could anyone test the July rev of the 390xx legacy driver build currently in AHS with 6.12? Sid just added a patch in November, and I have some doubts it could have fixed a broken 6.12 build, so we might have to wait. If it's OK, moving to main could be around the corner.

Code: Select all

nvidia-graphics-drivers-legacy-390xx (390.157-9) unstable; urgency=medium

  * Backport nv_get_kern_phys_address() changes from 555.42.02 to fix kernel
    module build with gcc-14 on arm*.

 -- Andreas Beckmann <anbe@debian.org>  Mon, 04 Nov 2024 09:16:04 +0100

nvidia-graphics-drivers-legacy-390xx (390.157-8) unstable; urgency=medium

  * Backport CONFIG_MITIGATION_RETPOLINE changes from 470.256.02.
  * Backport follow_pfn changes from 550.90.07 to fix kernel module build for
    Linux 6.10.
  * bug-script: Report 'apt-cache policy' (535.183.06-1).

 -- Andreas Beckmann <anbe@debian.org>  Fri, 26 Jul 2024 22:29:09 +0200

[dolphin_oracle]

Could anyone test the July rev of the 390xx legacy driver build currently in AHS with 6.12? Sid just added a patch in November, and I have some doubts it could have fixed a broken 6.12 build, so we might have to wait. If it's OK, moving to main could be around the corner.

Code: Select all

nvidia-graphics-drivers-legacy-390xx (390.157-9) unstable; urgency=medium

  * Backport nv_get_kern_phys_address() changes from 555.42.02 to fix kernel
    module build with gcc-14 on arm*.

 -- Andreas Beckmann <anbe@debian.org>  Mon, 04 Nov 2024 09:16:04 +0100

nvidia-graphics-drivers-legacy-390xx (390.157-8) unstable; urgency=medium

  * Backport CONFIG_MITIGATION_RETPOLINE changes from 470.256.02.
  * Backport follow_pfn changes from 550.90.07 to fix kernel module build for
    Linux 6.10.
  * bug-script: Report 'apt-cache policy' (535.183.06-1).

 -- Andreas Beckmann <anbe@debian.org>  Fri, 26 Jul 2024 22:29:09 +0200

ahs legacy 390 does not build. (390.157-8~mx23ahs)

[Stevo]

Could anyone test the July rev of the 390xx legacy driver build currently in AHS with 6.12? Sid just added a patch in November, and I have some doubts it could have fixed a broken 6.12 build, so we might have to wait. If it's OK, moving to main could be around the corner.

Code: Select all

nvidia-graphics-drivers-legacy-390xx (390.157-9) unstable; urgency=medium

  * Backport nv_get_kern_phys_address() changes from 555.42.02 to fix kernel
    module build with gcc-14 on arm*.

 -- Andreas Beckmann <anbe@debian.org>  Mon, 04 Nov 2024 09:16:04 +0100

nvidia-graphics-drivers-legacy-390xx (390.157-8) unstable; urgency=medium

  * Backport CONFIG_MITIGATION_RETPOLINE changes from 470.256.02.
  * Backport follow_pfn changes from 550.90.07 to fix kernel module build for
    Linux 6.10.
  * bug-script: Report 'apt-cache policy' (535.183.06-1).

 -- Andreas Beckmann <anbe@debian.org>  Fri, 26 Jul 2024 22:29:09 +0200

ahs legacy 390 does not build. (390.157-8~mx23ahs)

Yeah, I had my doubts based on the changelog. The rest of the drivers, except for nvidia-driver 535, are similarly outdated.
Hopefully having 6.12 in Sid will light a fire there.

[Eadwine Rose]

the option will be in mx-tweak shortly. just waiting on a few more translations.

169 has two issues:

no capital start of the sentence, and virtualbox is spelled wrong.

[dolphin_oracle]

the option will be in mx-tweak shortly. just waiting on a few more translations.

169 has two issues:

no capital start of the sentence, and virtualbox is spelled wrong.

Oops

[dolphin_oracle]

@Eadwine Rose new string should be up, if not now, soon.

that particular text is a tooltip.

[Eadwine Rose]

Thanks :)

[amlo]

I can report some progress with my issue of Plasma Wayland locking up after login. With kernel 6.15.2-1-liquorix-amd64 #1 ZEN SMP PREEMPT_DYNAMIC liquorix 6.15-1~mx23ahs (2025-06-18), which I signed with a MOK, I am now *unable* to login (login failed) rather than having a full lockup, as I reported viewtopic.php?t=85235 a couple days ago.

[Stevo]

That might have something to do with the revoked Wayland upgrade in the repos.

[amlo]

Is there a workaround, @Stevo such as uninstall the revoked/reinstall the non-revoked? Or is that still under development? If there's a script I could test, I'd be happy to.