I'm using the the modesettings branch at the latest commit:
Author: Alan Hourihane <email@example.com>
Date: Tue Aug 8 11:28:42 2006 +0100
I did the following:
Xorg -config /root/xorg.conf.new -logfile X.log -logverbose 8
Xorg fails to start up.
The log shows that no DDC or EDID info is displayed wich I guess
is the reason for the message:
Fatal server error:
No modes found on either pipe
Created attachment 6561 [details]
Created attachment 6562 [details]
xorg.conf.new create by Xorg -configure
Created attachment 6586 [details] [review]
Could you apply this patch and attach a new log? I'm wondering what your
default vertical refresh ranges are coming out as, or if I'm not getting them
right for some reason.
Created attachment 6594 [details]
Xserver log from driver with patch 1 applied
With the patched driver -configure select the vga driver.
I edited to use i810.
I do not see any output that shows that the EDID was read.
With the unichrome via driver I see a block of feedback that
shows me the DDC and EDID info.
The new I2C code may help. Plus, the fallback monitor code is different now.
I've got this same problem. Using xorg-server 18.104.22.1681 everything works
In xorg-server 22.214.171.1243 no DDC Modelines are gathered from the EDID. That's
the most notable difference in the xorg.0.logs I'll post both of them if it helps.
Created attachment 8221 [details]
My xorg.conf and the logs from 901 and 903 xorg-server
Just tar'd the three files together so I wouldn't have to upload three
different files :)
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
I just reviewed all the changes to hw/xfree86 between 126.96.36.1991 and 188.8.131.523
and saw nothing DDC related. If that's the only variable you changed, that
would seem to confirm the "subtle timing issues" guess I had for most of these
Also, though it's more convenient for the uploader, taring the files together
means that I'm almost surely not going to look at your logs when I'm trolling
the bug database looking for things I can fix today.
Created attachment 8886 [details]
version 901 X.log
Created attachment 8887 [details]
Version 903 Log
Created attachment 8888 [details]
Now you have no excuses ;)
The bug priority was upgraded (P2->high) with the bugzilla configuration change.
I'm Changing the priority back to the normal one.
Sorry for the spam.
Since this appears to be subtle timing issues on just 945 hardware, I'm clearing katamari release blocker status
David, it looks like your logs are using old, pre-native mode setting drivers. Can you try again with recent releases of the server and Intel driver?
Unfortunately, I cannot as I no longer have that laptop. :( sorry. It was work's and I had to give it back
Ok, well we've seen 945 get EDID info correctly in most cases these days, so I'll go ahead and close this one. (Not that we don't have bugs in this area, but there's not much we can do about this particular one, so I'll assume it's fixed :)