Bug#524335: Not that severe, after all

2009-04-16 Thread Cyrille Chépélov
severity 524335 normal
title 524335 has trouble resetting the hardware into the intended state 
thanks

After a reboot, the driver did produce a working screen, in 1600x1050 at
the GDM prompt.

After logging on, for some reason the screen went pink and slightly
garbled, and at a 1440x900ish resolution, but that was functional enough
to reach for the gRandR applet and put it back into 1600x1050. So far
(and after several similar tries) the result is satisfactorily in 2D.

Seems the problem will be over once the slight issue with completely
resetting the hardware state on mode changes is solved.

Thanks

-- Cyrille





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#524335: Not that severe, after all

2009-04-16 Thread Brice Goglin
Cyrille Chépélov wrote:
 severity 524335 normal
 title 524335 has trouble resetting the hardware into the intended state   
 thanks

 After a reboot, the driver did produce a working screen, in 1600x1050 at
 the GDM prompt.

 After logging on, for some reason the screen went pink and slightly
 garbled, and at a 1440x900ish resolution, but that was functional enough
 to reach for the gRandR applet and put it back into 1600x1050. So far
 (and after several similar tries) the result is satisfactorily in 2D.

 Seems the problem will be over once the slight issue with completely
 resetting the hardware state on mode changes is solved.
   

By the way, you might want to try with upstream drm kernel modules since
they bring better support for your board.

Brice




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org