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#10403 - nvidia driver needs rebuild against kernel 2.6.25.3

Attached to Project: Arch Linux
Opened by Hussam Al-Tayeb (hussam) - Tuesday, 13 May 2008, 02:38 GMT
Last edited by Thomas Bächler (brain0) - Tuesday, 13 May 2008, 10:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

The 'config' changes between kernel 2.6.25 and 2.6.25.3 packages require a rebuild of the nvidia driver. Otherwise, 3d accelerated stuff may cause a system freeze.
This task depends upon

This task blocks these from closing
 FS#10399 - Crash after upgrade to kernel 2.6.25.3-1 
Closed by  Thomas Bächler (brain0)
Tuesday, 13 May 2008, 10:31 GMT
Reason for closing:  Fixed
Comment by Thomas Bächler (brain0) - Tuesday, 13 May 2008, 07:09 GMT
You mean the TASKSTATS changes require module rebuilds? Or the group scheduler?

Did you try rebuilding and can confirm that it fixes the problems?
Comment by Mark (Lifty) - Tuesday, 13 May 2008, 07:48 GMT
I'm having a nvidia card and don't know if my problem is related to this matter. Since yesterdays update to 2.6.25.3 my KDEmod freezes the system at startup. I thought the problem was on the new kernel itself because of only about 5 packages being updated this time. Kdm runs just fine. The freeze only occures after logging in in kdm and before the bootsplash appears. Now I'm back at kernel 2.6.24 and everything is normal again.

Is it enough to just edit abs PKGBUILD for the nvidia driver to build it for the new testing kernel?
Comment by Thomas Bächler (brain0) - Tuesday, 13 May 2008, 07:50 GMT
If you use the testing PKGBUILD, you don't even have to edit it. Just rebuild it.
Comment by Mark (Lifty) - Tuesday, 13 May 2008, 08:33 GMT
Rebuilding the driver solves it!
Comment by Thomas Bächler (brain0) - Tuesday, 13 May 2008, 08:48 GMT
Okay, that means I have to rebuild all modules again.

Loading...