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#72103 - XOrg fails after upgrating to nvidia driver from 470.63.01-4-x86_64 to 470.63.01-7-x86_64

Attached to Project: Arch Linux
Opened by Victor Eduardo Bazterra (baites) - Saturday, 11 September 2021, 14:30 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 12 October 2021, 22:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: After upgrading to new nvidia package from 470.63.01-4-x86_64 to 470.63.01-7-x86_64 xorg fail to initialize.

* Kernel: 5.13.13-arch1-1
Package: nvidia-470.63.01-7-x86_64

* Nvidia card on supermicro X11SSL-F:

lspci | grep -E "VGA|3D"
00:13.0 Non-VGA unclassified device: Intel Corporation 100 Series/C230 Series Chipset Family Integrated Sensor Hub (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1)
06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)

* config and/or log files etc.

Pacman hook:

cat /etc/pacman.d/hooks/nvidia.hook
[Trigger]
Operation=Install
Operation=Upgrade
Operation=Remove
Type=Package
Target=nvidia
Target=linux

[Action]
Description=Update Nvidia module in initcpio
Depends=mkinitcpio
When=PostTransaction
NeedsTargets
Exec=/bin/sh -c 'while read -r trg; do case $trg in linux) exit 0; esac; done; /usr/bin/mkinitcpio -P'

Xorg configuration:

...
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BusID "PCI:1:0:0"
EndSection
...

Steps to reproduce:

> pacman -S nvidia
> # reboot machine

xorg log is attached.

Mitigation: downgrade to 470.63.01-4-x86_64

> sudo pacman -U /var/cache/pacman/pkg/nvidia-470.63.01-4-x86_64.pkg.tar.zst
> # reboot machine

Any help will appreciated!
   Xorg.0.log (5.2 KiB)
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 12 October 2021, 22:51 GMT
Reason for closing:  Upstream
Comment by JumaX9 (jumax9) - Thursday, 16 September 2021, 20:39 GMT
I have the same problem. The problem also persist with the updated kernel (5.14). I think it is not able to load any nvidia modules (`lsmod | grep nvidia` doesn't show any of `nvidia`, `nvidia-drm` etc as it usually does).
Attaching my Xorg.0.log file.
   Xorg.0.log (5.8 KiB)
Comment by Victor Eduardo Bazterra (baites) - Thursday, 16 September 2021, 21:09 GMT
@jumax9 I also tested going to 470.63.01-8-x86_64 with same kernel (sorry I have zfs in my system) and same issue.
Comment by Victor Eduardo Bazterra (baites) - Friday, 01 October 2021, 20:16 GMT
Update: I recently updated to kernel version 5.14.7-arch1-1 and 470.63.01-4-x86_64 stop working for me. In summary, the following combination of kernel and driver version is working for me now:

5.14.7-arch1-1
nvidia-470.74-2
nvidia-utils-470.74-1

I guess you could close the ticket at least because of me.

Thanks,
Victor

Comment by JumaX9 (jumax9) - Friday, 01 October 2021, 22:07 GMT
For me is still broken (even with that same combination of packages). Did you modify something else when you installed those packages?
Comment by Victor Eduardo Bazterra (baites) - Saturday, 02 October 2021, 01:15 GMT
@jumax9 no, I did not. I am using the same configuration as shown in the ticket including the pacman hook. The old driver stopped working as soon I updated the new kernel. I am certain I was running the old driver because nvidia was in my IgnorePkg. Then I switch to a virtual console, force to update nvidia driver, and reboot.
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 12 October 2021, 22:46 GMT
Sorry guys, there's still absolutely no information here that I can use to diagnose this as a problem in our packaging. I suspect this might be an upstream problem of some kind. Feel free to reopen if you get more definitive information.

Loading...