Comment # 31
on bug 56139
from Alexandre Demers
Here are the videos. Sorry, they were recorded with my iPod and they are inverted. Normal boot sequence before the culprit commit (kernel 3.6) http://www.filedropper.com/k36 A normal boot sequence with kernel 3.6 from grub 2 to booting console. Resolution is kept from grub to console, there is no sync problem and no purple flicker. A problematic boot with kernel 3.7-rc5 using gfxpayload=keep in Grub 2. http://www.filedropper.com/k37keep It starts normally, the booting console uses the same resolution as Grub 2. However, possibly when radeon driver kicks in, there is a purple flicker followed by a wrong (badly synced) display (shifted by about half a screen to the right). The result could have been a black screen, a couple of interlaced vertical lines or a different shifted display. A non problematic boot with kernel 3.7-rc5 using gfxpayload=text in Grub 2. http://www.filedropper.com/k37text It doesn't show the purple flicker we see in the previous video, it just flickers as a normal boot would do, but it does show the purple color from time to time. However, the display is OK. A problematic suspend/resume sequence with 3.7-rc5 (gfxpayload doesn't change anything) http://www.filedropper.com/k37suspend Going in suspend mode just after booting up. When resuming, X/gdm briefly appears, then it crashes. The computer continue to run, but the display stays black and no input can be used (tried to switch console and reboot but it doesn't work). Often, it will reboot by itself after some time. Suspend and resume work great before the culprit commit or if I remove the changes in "...mc_stop()"
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
