© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I hear you.
It happens both with the intel driver and with the standard 'modesetting' driver.
Quite a few people appear to have this problem from what I could glean out there.
I understand the reluctance at this layer to look into this, but it is a fairly common problem, and I get the impression wherever I see this reported that there is no-one even trying.
I am not blaming anyone here.
I was simply hoping for a bit more help than passing this off as some other group's issue.
I have probably already spent 12h+ with many attempts to bypass this, trying different monitors, modelines, looking for newer intel driver versions, switching to and fro between the intel and the standard driver, overriding edid info, different HDMI cables, different kernel versions (as far as I could get them). I have run out of ideas and lost *a lot* of sleep.
Thanks.