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!
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!
FS#21474 - nouveau does not reinitialize display after wake from sleep
Attached to Project:
Arch Linux
Opened by Paul Sadauskas (rando) - Tuesday, 26 October 2010, 06:36 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 26 October 2010, 10:39 GMT
Opened by Paul Sadauskas (rando) - Tuesday, 26 October 2010, 06:36 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 26 October 2010, 10:39 GMT
|
DetailsDescription:
MacBook Pro (Mid 2010 model) with nvidia NV50 using nouveau driver. Using both `extra/xf86-video-nouveau` and xf86-video-nouveau-git in AUR, the display fails to resume after sleep. Happens when closing the lid, and using `pm-suspend`, even after removing pm scripts 98video-quirks and 99-video as suggested in other bug trackers. After sleeping, the display never comes on, nor does the display backlight. Switching to a non-X virtual terminal (eg, Ctrl-Alt-F1) does not restore the display, either. The laptop is responsive, keyboard backlight comes on, and I can type `sudo reboot` into a terminal that I left focused before sleeping, and the laptop shuts down and reboots, with the display working after reboot. Attached is messages.log of the sleep (first line), and the resume (line 35 or so). Please let me know what additonal information is needed. |
This task depends upon
Comment by Jan de Groot (JGC) -
Tuesday, 26 October 2010, 08:21 GMT
I don't think it makes much sense to report that here. Nouveau is an experimental project, and if the git version doesn't work either, then it's not something we can solve. Please report this upstream.