Created attachment 326555 [details]
Xorg.log from IBM P260 that can do 1280x1024@75 (no xorg.conf)
It seems that openchrome stuck on LCD's resolution even I have external CRT connected and LCD on my notebook is off (by driver).
I had no luck with xorg.conf fiddling. The situation is the same even no xorg.conf in place.
I have: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01)
01:00.0 0300: 1106:7205 (rev 01) (prog-if 00 [VGA controller])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (500ns min)
Interrupt: pin A routed to IRQ 4
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=64M]
Region 1: Memory at d1000000 (32-bit, non-prefetchable) [size=16M]
Capabilities: <access denied>
The notebook is Acer Aspire 1350. I've got 1024x768@60.
I was able to run higher resolution with older drivers.
xorg-x11-drv-openchrome-0.2.903-1.fc10.i386 (no updates yet in repo).
To be more precise and accurate - I've got only 1024x768@60 on external CRT.
My notebook can do on its own LCD 1024x768.
My IBM P260 CRT can do 1280x1024@85 in MS Windows but in Linux 1024x768@60 only.
From the log, the driver is activating both the LCD and the CRT. openchrome is currently not dual head capable, so it uses the same resolution on the 2 outputs, the lower common denominator wins. You can disable the LCD panel by adding the following line to the Device section of your xorg conf :
Option "ActiveDevice" "CRT"
Lemme know if it helps.
Yes, ActiveDevice works with my CRT. Thank you.
But without ActiveDevice the situation differ:
1) with CRT (IBM P260)
- CRT is active, all is visible and Ok
- LCD is Off
2) with Dell data projector
- nothing is shown on both output devices
Should I try some experimental patches or builds or do some testing?
Logged as http://www.openchrome.org/trac/ticket/271
Could you update to the latest version, retest and report back to see if this still remains an issue for you.
You can get the latest update from here.
There's no way to "fix" this bug until openchrome grows dual head support. Currently, there's no way to have a different resolution and refresh rate on different output, the lower one will apply to both output. See comment #4.
Hopefully, dual head support shouldn't be too far away, I'll make sure to update both the rawhide package and the F10 testing package as soon as it enters upstream.
In the Ubuntu this error also exist.
But in Ubuntu case, also mouse cursor is not visible on the secondary display.
Do you also have problems with cursor?
I created patch which should solve problems with cursor.
The patch is available at:
Created attachment 346220 [details]
patch which should solve problems with cursor.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
Is closed befor, only removing my needinfo.