Corrupt display while/after booting on VIA P4M900 internal graphiccard

[drose]

Binary package hint: xserver-xorg-video-via

Booting Hardy Alpha 5 on an ASROCK P4VM900 (Pentium4, Chipset VT8237S/P4M900 integrated DeltaChrome graphics) the screen is corrupt. The graphic output shows parallel offsets of aprox. 20 pixel per line. The aprox. 20 pixel pieces are alternately filled with screen pixels and blank pixels. Thus the output is overlayed by it self over the whole screen.

The boot screen is o.k., but when x server starts (i assume) the screen gets corrupted. Booting in failsafe mode ist possible.

Maybe the DeltaChrome driver has a bug or the chipset will not be detected correct during boot time. Because of the corrupted display Ubuntu can not be controlled and there is no attachment available.

Binary package hint: xserver-xorg-video-via driver ??

This bug seems to be similar to #140070 but covers the whole screen and starts during booting.

[Timo Aaltonen (tjaalton)]

Please attach your /var/log/Xorg.0.log, and a picture of the corruption if possible.

[Oliver Göthel (godeezy)]

This bug is related to the driver version of openchrome. Version 0.2.902 provides correct drivers for the ASRock P4VM900-SATA2 board. Unfortunately Hardy is stuck at version 0.2.901. Please update...

[Connor Imes (ckimes)]

Since this is supposedly fixed in newer versions, can we close this bug report? If the OP can check if the problem still exists in Intrepid, that would be great.
Intrepid is using version 1:0.2.903-0ubuntu3

[Connor Imes (ckimes)]

Oliver, you said this bug was fixed in 0.2.902 so I'll mark as Fix Committed for now. Would you happen to have a link to an upstream bug report for that?
Timo, can you please confirm that this works in Intrepid?

[Connor Imes (ckimes)]

Intrepid and Jaunty are using versions that this should be fixed in. I will mark this bug as Fix Released, but if the problem persists, please re-open the bug by changing the status back to New. Thanks!

[Flávio Etrusco (etrusco)]

It su-- err, it's not nice when reporters just vanish :-/

Anyway, just as a reminder in case this bug gets reopened, fedora is using a newer svn snapshot and it seems they're confident enough to push it as an update to f10:
http://article.gmane.org/gmane.linux.redhat.fedora.testers/68103 (just scroll to the end)

One of the bugs fixed, https://bugzilla.redhat.com/show_bug.cgi?id=469504, sounds a little similar to this one and I'm still experiencing it with latest jaunty packages (xserver-xorg-video-openchrome=1:0.2.903+svn713-1ubuntu1).