Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#79011 - [nvidia] Updating to 535.54.03-5(&-6) causes system to freeze on boot

Attached to Project: Arch Linux
Opened by 1reverseengineer (1reverseengineer) - Friday, 07 July 2023, 14:08 GMT
Last edited by Antonio Rojas (arojas) - Friday, 07 July 2023, 15:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I updated my ArchLinux packages via pacman -Syu --ignore=linux yesterday which updated all packages except for the linux kernel (due to ongoing issues with 6.4.1 so I simply excluded it for now).

This updated the nvidia drivers from ‘535.54.03-3’ to ‘nvidia 535.54.03-6’.
Upon restarting my machine in the morning, I discovered that my machine was stuck displaying my UEFI / mainboard manufacturer boot logo in front of a black-screen, after the system passed the GRUB bootloader selector.

The machine (visually) was practically frozen / dead (you can still switch to TTY2 CLI but the GUI is practically dead)

Upon a lengthy bug hunting phase I was able to track back the bug to the NVIDIA display drivers.

After downgrading to 535.54.03-3 did my machine boot up normally again / not get stuck after the GRUB bootloader. It’s important to note that 535.54.03-5 is not a viable downgrade as it also contains the bug.

I’m happy to assist any nvidia developer with an ‘nvidia-bug-report.sh’ output, which I ran while the bug was occurring. (I’m not sure if the log file contains any private information so I’ll wait for further instructions and not post it publicly).

Thank you for reading and have a good day.

Additional info:
- Affected package version(s)
--> 535.54.03-5
--> 535.54.03-6

- Logs and configs:
--> Due to privacy concerns, I'll wait for further instructions.

Steps to reproduce:
Upgrade from say 535.54.03-3 to 535.54.03-5 or in my case 535.54.03-6.
Test on Linux kernel: 6.3.9.
This task depends upon

Closed by  Antonio Rojas (arojas)
Friday, 07 July 2023, 15:23 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Friday, 07 July 2023, 14:27 GMT
You can't ignore the kernel and update the binary modules that are built for that kernel. Of course it doesn't work!

Partial updates are unsupported.

Loading...