Comment 10 for bug 1029865
Revision history for this message
|
|
#10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The hw is convinced something is attached. Is the physical connector dirty? Does plugging in and removing a real monitor clear the erroneous state? Does Windows work?
About the only brute force you have available is to do a forced hw probe instead of checking the state changed, or to always use the EDID detection (which then breaks those monitors without EDID).