|
Description
Michael Eschweiler
2007-07-14 01:42:37 UTC
Are you still seeing this problem with the latest driver? Please attach xorg.conf and Xorg.0.log. I can confirm this with Gutsy and -intel driver 2:2.1.1-0ubuntu9. Created attachment 12331 [details]
Xorg.0.log with new Intel driver
Created attachment 12332 [details]
lspci -vvnn
Created attachment 12333 [details]
xorg.conf
Would you please try the following patch to see if the problem is fixed?
Thanks,
Hong
diff --git a/src/i830_crt.c b/src/i830_crt.c
index d7762a0..7def610 100644
--- a/src/i830_crt.c
+++ b/src/i830_crt.c
@@ -162,9 +162,12 @@ i830_crt_detect_hotplug(xf86OutputPtr output)
const int timeout_ms = 1000;
int starttime, curtime;
- temp = INREG(PORT_HOTPLUG_EN);
+ /* clear the CRT hotplug status bits first */
+ OUTREG(PORT_HOTPLUG_STAT, CRT_HOTPLUG_MONITOR_MASK);
- OUTREG(PORT_HOTPLUG_EN, temp | CRT_HOTPLUG_FORCE_DETECT | (1 << 5));
+ temp = INREG(PORT_HOTPLUG_EN);
+ OUTREG(PORT_HOTPLUG_EN,
+ temp | CRT_HOTPLUG_FORCE_DETECT | (1 << 5) | CRT_HOTPLUG_INT_EN);
for (curtime = starttime = GetTimeInMillis();
(curtime - starttime) < timeout_ms; curtime = GetTimeInMillis())
Created attachment 12687 [details]
Xorg.0.log witch patched Ubuntu Gutsy Gibbon Intel driver after xorg.conf removal
Many thanks for your patch but problem still appears.
Still gdm starts with 640x480 instead of 1024x768.
If I use my normal xorg.conf and replace i810 with intel X crashes. I am going to attach a gdb report soon.
(In reply to comment #7) > Created an attachment (id=12687) [details] > Xorg.0.log witch patched Ubuntu Gutsy Gibbon Intel driver after xorg.conf > removal > > Many thanks for your patch but problem still appears. Sorry, the patch only works on new chips (945 and 965..). It seems we can't detect the connected monitors, will work on this to see if we can find any solution... > Still gdm starts with 640x480 instead of 1024x768. > If I use my normal xorg.conf and replace i810 with intel X crashes. I am going > to attach a gdb report soon. > For i810 driver, it filters out the 1024x768 mode because of the hysnc range: (II) I810(0): Builtin Default Monitor: Using default hsync range of 31.50-37.90 kHz You can try to add HorizSync to your monitor section to enlarge the hysnc range. Thanks, Hong Created attachment 12696 [details]
Xorg.0.log with patched Ubuntu Intel driver
Created attachment 12697 [details]
xorg.conf
Created attachment 12698 [details]
Xorg.0.log with i810 driver (HorizSync have to been activated in xorg.conf to get 1024x768)
How it is possible to get a gdb backtrace of Xorg which crashes directly after start so it is not possible to get a pid and attach it? But according to log it only seems to be a ddc/resolution since it shutdown normally. Thanks for your reply. Manual adding of HorizSync only works with i810 driver. The Intel driver seems to ignore these because of modesetting I guess. (In reply to comment #13) > Thanks for your reply. Manual adding of HorizSync only works with i810 driver. > The Intel driver seems to ignore these because of modesetting I guess. > Yes, you have to stick with the i810 driver currently :( With the Intel driver, we can't detect the connected CRT monitor: (II) intel(0): Output VGA disconnected (II) intel(0): EDID for output VGA (II) intel(0): Output VGA disconnected (EE) intel(0): No valid modes. So X server exits without success. We need to figure out a better solution for monitor detection for this chipset. Created attachment 12731 [details] [review] 2nd try Please have a try on the attached patch. Thanks, Hong Created attachment 12763 [details]
Xorg.0.log.old with 2nd try patched Ubuntu Intel driver
Many thanks for your patch but I got still the same or a similar error. Btw. is HorizSync needed with your 2nd try Patch? (In reply to comment #18) > Btw. is HorizSync needed with your 2nd try Patch? > Should not, I am not sure why we can't correctly detect your VGA connection status. This caused your problem. Thanks, Hong It seems to be a general problem with the 845 chipset since there are some duplicates for and posts under the Ubuntu bug report https://bugs.launchpad.net/bugs/135093 . I don't know if there are more but all of the reporters seem to have the Brookdale-G version. Matthew Garrett reports that -intel does not support chipsets older than 855. "Before 855, it's possible to attach basically arbitrary LVDS encoders to the chipset - the BIOS knows how to talk to them, but -intel doesn't use the BIOS so needs to have code for each of them individually. As far as I know, the entire set isn't currently supported." So if this is the case, we need to know if -i810 should be retained permanently for use with older chipsets, or if there are any plans/efforts to incorporate the code into -intel. No, Bryce. The released packages have supported the ivch which is in every 830 laptop we've seen so far. The 845 laptops almost all have ch7017, which is also supported at least upstream (not sure if it was in 2.1 or not). The remaining chip, which we've seen one instance of, is a natsemi device which we can't find specs for. And the bug you're commenting on appears to be about a desktop anyway. unggnu: please open your own bug for your own issue, and include Option "ModeDebug" "YES" in your device section. No additional patches. Original submitter: Could we get your log with option "ModeDebug" "YES"? Created attachment 13414 [details]
Testcase with MODE DEBUG
Test case with the MODE DEBUG option.
Created attachment 13564 [details] xorg.0.log with modedebug turned on. extracted from comment# 24. (In reply to comment #24) > Created an attachment (id=13414) [details] > Testcase with MODE DEBUG > > Test case with the MODE DEBUG option. > Would you please use the intel driver instead of the vesa driver? Thanks, Hong Created attachment 13972 [details] Xorg.conf used for MODEDEBUG test In response to comment 25. Test case is with Intel driver, not VESA. However Xorg is reporting VESA for some reason. Will repeat test and publish results Created attachment 13973 [details]
Xorg log with MODEBUG and xorg.conf above
Created attachment 13974 [details]
13972: Xorg.conf used for MODEDEBUG test
Created attachment 13975 [details]
13972: Xorg.conf used for MODEDEBUG test
Created attachment 13976 [details] Xorg log with MODEBUG and xorg.conf above In response to comment 26, the Intel driver is being used despite the VESA messages shown. I have attached the xorg.conf and xorg.0.log. Created attachment 13977 [details]
lspci output from above test
Note Unknown device mentioned at line 9
Created attachment 13978 [details]
ddcprobe
(In reply to comment #31) > Created an attachment (id=13976) [details] > Xorg log with MODEBUG and xorg.conf above > > In response to comment 26, the Intel driver is being used despite the VESA > messages shown. I have attached the xorg.conf and xorg.0.log. > Weird... it shouldn't be... Created attachment 14076 [details]
Updated Xorg.0.log with MODEDEBUG and xorg.conf
Refreshed Xorg.conf, no changes made but VESA messages gone replaced with intel error messages.
Shofi, would you please also attach you kernel dmesg? For all who have problem with 845G, you are saying a 845G laptop? If so, it seems I have made a big mistake for I am trying to find out why VGA can't be detected while it is not connected. For all who have i810 work on your machine, would you please try to dump the registers when it is working. The tool is in the xf86-video-intel/src/reg_dump, you will need libpciaccess to compile this tool. Thanks, Hong It seems 845G laptop uses ch7017 module to drive the LVDS output. But I didn't see any ch7017 related info in your xorg log. Would you please ensure that ch7017 module is existed in your distribution (usually it is on /usr/lib/xorg/modules/drivers/)? Thanks, Hong Created attachment 14116 [details]
dmesg log as requested
dmesg log as requested
Created attachment 14117 [details]
location of module ch7017
Module ch7017 present within filesystem, but is not visible using lsmod. I cannot insert it using modprobe or insmod, but I assume that is because I cannot use these commands.
(In reply to comment #40) > Created an attachment (id=14117) [details] > location of module ch7017 > > Module ch7017 present within filesystem, but is not visible using lsmod. I > cannot insert it using modprobe or insmod, but I assume that is because I > cannot use these commands. > Sorry for the confusion, ch7017 is a module for X server (not for kernel). Our drive will try all the compiled modules one by one to try to detect which output is active. f.e this is when we are trying the sil164 module (in xorg log). (II) Loading sub module "sil164" (II) LoadModule: "sil164" (II) Loading /usr/lib/xorg/modules/drivers//sil164.so (II) Module sil164: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (II) intel(0): I2C bus "DVOI2C_E" initialized. (EE) intel(0): detecting sil164 (EE) intel(0): Unable to read from DVOI2C_E Slave 112. We have an array in i830_dvo.c file (i830_dvo_drivers[]), and we will try one by one until we find one active output. The problem is in your log, the last module we tried is tfp410 (which is not active), but the driver didn't try ch7017 module which is after the tfp410. Which driver version are you using? Would you please give the latest driver a try? Or would you please try to move the following block in i830_dvo_drivers[] to a front position to have a try. { .type = I830_OUTPUT_DVO_LVDS, .modulename = "ch7017", .fntablename = "ch7017_methods", .dvo_reg = DVOC, .address = 0xea, .symbols = ch7017_symbols, .gpio = GPIOE, } Thanks, Hong Created attachment 14140 [details] i830_drv.c from ubntu Gutsy (2:2.1.1-0ubuntu9) Am using Ubuntu Gutsy with driver version 2:2.1.1-0ubuntu9(gutsy). This has been raised as a downstream bug in https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/135093 The code block mentioned previously does not appear in the file; it only references a module called ch7xxx. Would you review the module source (attached) and comment if this is correct. (In reply to comment #42) > Created an attachment (id=14140) [details] > i830_drv.c from ubntu Gutsy (2:2.1.1-0ubuntu9) > The ch7017 related code has been commented out. Would you please try the upstream driver. You can get it by $ git-clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel Thanks, Hong Created attachment 14179 [details]
Xorg.0.log using recompiled driver
The latest driver works, but all 3D ability is now gone. glxinfo reports no direct rendering.
Created attachment 14180 [details]
glxinfo
libGL error: drmMap of framebuffer failed (Invalid argument)
libGL error: reverting to (slow) indirect rendering
Apologies if it seems I'm spamming this bug. I'm keen to help fix this.
Tested liveCD of Ubuntu Hardy alpha 4 with the latest drivers. Intel driver now working with ch7017 chipset and acceleration. Good to know this works now. So I'm closing this one. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.