Bug 238747

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 155664 [details]
Xorg.0.log

I shutdown the laptop, connect external 19" samsung screen and power on the
laptop. Only the external screen is on by default and when fedora 6 boots-up I
end up with 800x600 resolution! :( Sometimes it is 1024x768 and only once it
booted to monitor's native 1280x1024 resolution

Created attachment 155665 [details]
xorg.conf-external-booted-to-800_600

xorg.conf with laptop booting to 800x600 resolution.

I'm going to backup xorg.conf and remove it and send you the results you asked
for.

Created attachment 155667 [details]
Xorg.0.log.autodetected

Whis is Xorg.0.log with removed /etc/X11/xorg.conf

Even with removed /etc/X11/xorg.conf with autodetect I get only 800x600 resolution!

Can you please tell me if you are looking at this bug? I would like to help fix
this bug but soon I'll be switching to Fedora 7 or wait for Fedora 8.

Are you also waiting for Fedora 8 and not even looking at this bug?

This ought to be significantly improved in F7 with the intel driver.

I backed up my xorg.conf file and then I felt safe enough to play around with
the settings.

I started system-config-display and changed video driver from i810 to intel. Now
laptop boots to 1024x768 on both screens.

But I still can't force X to boot to 1280x1024 or to be precise it desktop
switches to 1280x1024 resolution but both screens stay at 1024x768 resolution so
I can pan around this biger desktop but that is not usable.

So what you are saying is that i810 driver is being abandoned and intel driver
is taking it's place?

Can you point me to some much needed resources for howto setup my external
monitor to switch to 1280x1024 resolution - or even better how to setup dualscreen. 

Setting up dual-screen with system-config-display doesn't work - it produces non
workable xorg.conf files that freeze the system. I tries setting it up and it
creates videocard0 with driver "intel" and videocard1 with driver "vesa" ?!? Why?

I am not sure, whether I would characterize i810 driver as abandoned, but
certainly the main effort of Keith Packard & co. is focused on intel driver.

For the rest, I will pass this bug to developers.

(In reply to comment #8)

> So what you are saying is that i810 driver is being abandoned and intel driver
> is taking it's place?

Yes.

> Can you point me to some much needed resources for howto setup my external
> monitor to switch to 1280x1024 resolution - or even better how to setup
dualscreen. 

What does the 'xrandr' tool report for this monitor configuration?

> Setting up dual-screen with system-config-display doesn't work - it produces non
> workable xorg.conf files that freeze the system. I tries setting it up and it
> creates videocard0 with driver "intel" and videocard1 with driver "vesa" ?!? Why?

Because system-config-display hasn't been fixed yet.

$ xrandr 
 SZ:    Pixels          Physical       Refresh
*0   1024 x 768    ( 382mm x 300mm )  *60  
Current rotation - normal
Current reflection - none
Rotations possible - normal left inverted right 
Reflections possible - none


do you need any other feedback from me? I'm happy to help fix bugs :)

xrandr -q 
would be helpful

here you go:

$ xrandr -q
 SZ:    Pixels          Physical       Refresh
*0   1024 x 768    ( 382mm x 300mm )  *60  
Current rotation - normal
Current reflection - none
Rotations possible - normal left inverted right 
Reflections possible - none

ps. I don't see any difference with "-q" parameter.

$ xrandr --verbose
 SZ:    Pixels          Physical       Refresh
*0   1024 x 768    ( 382mm x 300mm )  *60  
Current rotation - normal
Current reflection - none
Rotations possible - normal left inverted right 
Reflections possible - none
Setting size to 0, rotation to normal
Setting reflection on neither axis

$ xrandr --version
Server reports RandR version 1.1

Fedora Core 6 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora 7, 8, or
Rawhide)? If this issue turns out to still be reproducible, please let us know
in this bug report. If after a month's time we have not heard back from you, we
will have to close this bug as CANTFIX.

Setting status to NEEDINFO, and awaiting information from the reporter.

[This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or
Gecko. If you see any other reason, why this bug shouldn't be closed, please,
comment on it here.]

Hm, yeah the latest driver shouldn't have this problem.  There are some config 
options that might affect this though, depending on your configuration:
  - the 'virtual' directive in your xorg.conf Screen section
    needs to be big enough to handle the largest desktop you want to handle
    (e.g. width of crt + width of laptop by max(height of crt, height of 
laptop for a 'side by side' configuration)
  - the driver may be failing to get EDID info from your monitor
    the log should show this.

So please try with the latest driver bits and confirm your virtual setting.  
Attach the log if the bug still occurs.

I'm now using intel driver and not i810. Is this new i810 driver available for
FC6 or only on Fedora 8?

I think he talks about intel drvier; i810 is really almost dead.

well i810 is the default driver on Fedora Core 6, and I filed a bug for i810.
I switched to intel driver a long time a go and I don't see this bug with intel
driver.

If you like please close the bug.

OK, thanks for letting us know (yes, the package which brings intel driver is
still called i810; that might be the bad thing, but we haven't made it so).