Red Hat Bugzilla – Bug 199764
i810 modesetting regression (<= i865)
Last modified: 2008-08-02 19:40:34 EDT
Description of problem:
I've been tracking rawhide for a while, and I recently upgraded to the new
intel i810 driver. X stopped working with the new i810 driver unfortunately.
if I do xinit I get the following error after X doesn't start:
Build Date: 13 July 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 21 16:00:08 2006
(==) Using config file: "/etc/X11/xorg.conf"
(EE) I810(0): detecting sil164
(EE) I810(0): Unable to read from DVOI2C_E Slave 112.
(EE) I810(0): detecting ch7xxx
(EE) I810(0): Unable to read from DVOI2C_E Slave 236.
(EE) I810(0): DDC Analog 0, 00005010
(EE) I810(0): DDC DVO 1, 0000501C
Executing (ax == 0x5f01) BIOS call at i830_driver.c:617
Fatal server error:
No modes found on either pipe
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
This is on an intel ICH3 chipset in an IBM thinkpad x30.
Normally I'd expect X to just sort of work :)
The exact rev of the intel driver is 1.6.0-11.20060713modset.fc6
Attached is my xorg.conf and the Xorg.0.log
Created attachment 132844 [details]
Created attachment 132845 [details]
What happens when you turn DDC back on? (comment out Option "NoDDC")
No change. I added Option NoDCC "true" in an attempt to work around the current
problem. I can set it to false or comment it out with no effect.
Any better with recent intel driver snapshots? The version in F7 now should
have this sorted.
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
No information requested was provided, so I close this bug as INSUFFICIENT_DATA.
Reporter, if you could, please, reopen with additional information.