Comment 10 for bug 127008
Revision history for this message
| Bryce Harrington (bryce) wrote Re: Alternate install of Tribe-4 corrupts video display when installing packages | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Looking through all the duplicates for this bug, it appears pretty much everyone's hardware is amd64 and gm965. The issues appears to have all been noticed in August, around tribe3/tribe4.
Looking at the xresprobe changelog, this appears to coincide with a change made by Matthew Garrett to add support for the Intel driver. This didn't *cause* the bug, but probably just revealed it; prior to this, xresprobe wouldn't be able to deal with -intel. However, my guess is that the root issue is in the intel driver, not in xresprobe itself; xresprobe simply triggers it.
Can anyone reproduce the issue after installation by running 'xresprobe intel'? If so, could you then try running 'xrandr --output TV --off' and then 'xresprobe intel' and see if that makes it go away?
There are reports upstream with this chipset that the TV out detection can confuse the resolution detection algorithms. If this is the case here, then we need to ensure tv out is disabled for this card. See https:/
Section "Monitor"
Identifier "TVOutput"
Option "Disable" "true"
EndSection
Then in the Device section add:
Option "monitor-TV" "TVOutput"
If it can be determined that TV-out is not the cause of this issue, then we should probably report it upstream; I could not find other reports of this behavior in the xorg or debian bug trackers.