You are not logged in.
Hi,
When I reactivate my HP 8440p from standby, the screen is just white or starts flickering which looks as follows:
My laptop never comes back again, even if I wait a long time.
Any idea how to fix this problem?
Some additional information:
# lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [NVS 3100M] (rev a2)Using nouveau. The official Nvidia driver caused more problems than the nouveau driver, so I'd like to keep using nouveau.
System is up to date.
Offline
Four years later, received many software updates and still having this problem. Just checked out the journal and found the following:
When I suspend, nouveau writes the following log entries:
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: DRM: suspending console...
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: DRM: suspending display...
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: DRM: evicting buffers...
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: DRM: suspending client object trees...
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: DRM: suspending kernel object tree...But when I resume, I get these lines:
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: DRM: resuming kernel object tree...
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: DRM: resuming client object trees...
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: DRM: resuming display...
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: disp: outp 00:0006:0344: link training failed
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: disp: outp 00:0006:0344: link training failed
Mar 24 22:15:00 myNotebook kernel: nouveau 0000:01:00.0: disp: outp 00:0006:0344: link not trained before attachSo, we see, link training failed. But what does it mean for me? Can I write a script that resets the display on resume or something like that?
Any idea what's the problem? I can't imagine that I am the only one having this issue.
UPDATE: just updated the BIOS to 2.3.0.0 but did not solve the issue.
Last edited by jsnlry (2016-03-24 23:01:51)
Offline