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#48121 - Nvidia 361.28-1 upgrade causes API mismatch

Attached to Project: Arch Linux
Opened by Ryan Owens (ryanvade) - Wednesday, 10 February 2016, 17:53 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 13 February 2016, 00:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After upgrading to 361.28-1 X does not start. The cause appears to be an API mismatch with the kernel module.
https://ptpb.pw/kgbq

I have nvidia,nvidia-libgl, nvidia-utils, lib32-nvidia-libgl, lib32-nvidia-utils installed and updated. I attempted to use the nvidia-dkms package but it has the same result.

Hardware:
i5-4690K
GTX 970 STRIX
16BG RAM
256 GB Samsung EVO SSD
1TB WD Blue HDD
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 13 February 2016, 00:16 GMT
Reason for closing:  Not a bug
Comment by Ryan Owens (ryanvade) - Wednesday, 10 February 2016, 18:24 GMT
Also, I am using the current kernel in the core repo and a reboot does not help.
Comment by Doug Newgard (Scimmia) - Wednesday, 10 February 2016, 19:09 GMT
That looks like you have a mismatch between nvidia and nvidia-utils
Comment by Ryan Owens (ryanvade) - Wednesday, 10 February 2016, 21:46 GMT
package versions are both 361.28
Comment by Ryan Owens (ryanvade) - Wednesday, 10 February 2016, 22:04 GMT
After upgrading to 361.28-2 (for nvidia-utils/*nvidia-libgl since nvidia 361.28-2 has not been released yet) I am still experiencing the same problem. However, if I unload the kernel module then reload it the problem goes away.
Comment by Doug Newgard (Scimmia) - Wednesday, 10 February 2016, 22:56 GMT
Right, you have to load the new kernel module on update. This is normal.
Comment by Ryan Owens (ryanvade) - Thursday, 11 February 2016, 02:25 GMT
  • Field changed: Percent Complete (100% → 0%)
Having to unload then load the kernel module after every reboot is not normal behaviour.
Comment by Doug Newgard (Scimmia) - Thursday, 11 February 2016, 02:25 GMT
Do you have the module in the initramfs? If so, did you update that?
Comment by Doug Newgard (Scimmia) - Friday, 12 February 2016, 15:14 GMT
Ping?
Comment by Ryan Owens (ryanvade) - Friday, 12 February 2016, 23:04 GMT
It seems that the latest nvidia-utils and nvidia-libgl updates fixed things. Not sure what the problem was though. Rebuilding the initramfs happened after the upgrade.

Loading...