Bug 245965

Thanks for the bug report.  We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Created attachment 158412 [details]
xorg.log from xorg.conf

This is the log file from starting with a xorg.conf (config file attached next)

Created attachment 158413 [details]
xorg.conf

the xorg.conf to go with the log file

Created attachment 158414 [details]
xorg.log from autodetect

attached is the x.org log from starting with no xorg.conf file

Details provided. Let me know if you need any more info.

xorg-x11-drv-i810-2.1.0-1.fc7 has been pushed to the Fedora 7 testing repository.  If problems still persist, please make note of it in this bug report.

Actually, please, make note here even if the upgrade didn't help.

It didn't work. I'm going to roll back to the original one that worked and get
the original log. then upgrade again.

The 2.1.0 driver all exhibits some interesting bits that weren't seen prev. If I
remove the xorg.conf file with the external screen attached it detects the
1280x1024 fine and starts up. If I then remove the laptop from the dock and
startup again (ie go home) just on my laptop screen (1440x900) it doesn't detect
it properly so you get the X doesn't start dialog do you want to configure it. I
spec the screen res and it starts fine. It did this with the prev version too
but the difference is that the previous version would clip the screen (IE the
screen seemed to be 1440 wide but only showed 1280 - you could loose the mouse
off the side) now its extremely flickery and you need to go to a console and rm
the xorg.conf and Ctrl+Alt+Bkspc to get it back.

When there's no xorg.conf file it also does weird things with the UK keyboard
but that's another bug entirely!

Before downgrading to the older driver, could we get an output of xrandr -q
command, please?

[root@localhost ~]# xrandr -q
Screen 0: minimum 640 x 480, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 (normal left inverted right) 0mm x 0mm
   1280x1024      75.0* 
   1024x768       75.0  
   800x600        75.0  
   640x480        75.0  
[root@localhost ~]# 

OK this is weird! As a follow on from my Comment #8 above when not docked I get
a totally different output. So to cover my setups a little better:

Dell D620 laptop with a 1440x900 14.1 inch display (there's 2 options when
ordering) and a Ddock replicator. Attached to the Ddock are 2 identical HP 19
inch LCD displays (one to the DVI port and one to the VGA port.

[root@localhost log]# lspci | grep 945GM
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT
Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS, 943/940GML
Express Integrated Graphics Controller (rev 03)
[root@localhost log]# 

At work when connected to the dock I run with the laptop closed off (in theory)
the 2 LCDs (works fine in windows). When elsewhere I run off the laptop display. 

When moving to the dock (working previously on the laptop 1440x900 display
moving 2 external lcds) I now get a buzzing static display (its recognizable but
it looks like its displaying the first 1280 and wrapping the remainder of the
1440). I remove the xorg.conf do a ctrl+alt+bkspc and it auto detects and away I
go (see xrandr above for output).

When moving from the dock (working previously on external lcd) to the built in
1440x900 I get X will not start (will attach logs shortly) and I have to go
through the config druid. It only detects 800x600 so I have to specify a
1440x900 generic LCD. It then starts as expected. The interesting part of this
is if you look through the TUI log files its using the i810 driver not the intel
driver.

Below is the xrandr for just the local laptop panel.... interesting that it sees
the vga etc now.... disconnected!

[root@localhost ~]# xrandr -q
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 1440 x 1440
VGA disconnected (normal left inverted right)
LVDS connected 1440x900+0+0 (normal left inverted right) 304mm x 190mm
   1440x900       60.0*+
   1360x768       59.8     60.0  
   1280x800       60.0  
   1152x864       60.0  
   1280x768       60.0  
   1280x720       60.0  
   1024x768       60.0  
   800x600        60.3  
   640x480        59.9  
TMDS-1 disconnected (normal left inverted right)
TV disconnected (normal left inverted right)
[root@localhost ~]# 

Created attachment 159001 [details]
laptop display no dock auto detect log

I had 2 different logs from during the "we can't start X process". One from the
initial startup and one from during the detection before manually specifying
the display resolution of 1440x900. Doing a diff on them just gave some
different hex addresses so they are the same.... so here's one for ref

So does this still occur?  It sounds like you're sometimes using the i810 
driver, what happens if you always use the intel driver?

No I was always using the Intel driver (the i810 driver didn't detect the
1440x900 res of the laptop. Unfortunately I don't have this setup anymore as
I've changed jobs. The VGA screen disappeared between 2.0.0 and 2.1.0

Ah ok.  Well there have been a few VGA detection fixes since 2.1.0, so this 
bug is probably fixed.  But it sounds like you can't test anymore so we should 
probably just close this bug.

We don't do it -- we may eventually (for some inexplicable reason ;-)) actually
provide update for F7 and then it could get fixed. Otherwise it will get closed
together with all other F7 bugs when F7 will ceased to be supported.

Closing this as I can't properly test it and the xorg-intel driver has changed
so much between when I reported this and what I'm running now (Fedora 9 rawhide
- basically F9 Beta).