Red Hat Bugzilla – Bug 389011
Xorg fails on VIA UniChrome Pro IGP when openchrome set as driver
Last modified: 2008-08-02 19:40:35 EDT
Description of problem:
VIA UniChrome Pro IGP on board graphics is not detected correctly and xorg fails
if the via driver is selected.
The vesa driver works.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install F8
2. Check to see what xorg.conf driver is set to (it will be vesa)
3. Shutdown X, Change driver to via, start X
X will fail to start
X should start
lspci -vvv info
01:00.0 VGA compatible controller: VIA Technologies, Inc. UniChrome Pro IGP (rev
01) (prog-if 00 [VGA])
Subsystem: VIA Technologies, Inc. UniChrome Pro IGP
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (500ns min)
Interrupt: pin A routed to IRQ 20
Region 0: Memory at f4000000 (32-bit, prefetchable) [size=64M]
Region 1: Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at fc000000 [disabled] [size=64K]
Capabilities:  Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities:  AGP version 3.0
Status: RQ=256 Iso- ArqSz=0 Cal=7 SBA+ ITACoh- GART64- HTrans-
64bit- FW- AGP3+ Rate=x4,x8
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
Created attachment 262621 [details]
xorg.conf used with via set as driver
Created attachment 262631 [details]
xorg log file when display set to via
Here is the Smolt profile, incase it's of any help:
Mass migration: via -> openchrome.
Please retry with xorg-x11-drv-openchrome. This is the successor to
Created attachment 275001 [details]
xorg.log file from openchrome driver
This does indeed manage to bring up an X display on the machine.
I'm unsure as to what performance I should expect with this driver, but it
seems to be a little sluggish.
Also when X starts, there are what seems to be a number of false starts before
the display settles... i.e. X display starts to appear, then back to console,
then back to the X "watch" in the center of the screen before finally the GDM
login screen redraws.
Created attachment 275011 [details]
xorg.conf file with openchrome driver
Could we get /var/log/Xorg.0.log as well, please?
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.
I had a similar problem with my laptop six months ago. I did a bit of googling
around and found (might have been on a Ubuntu forum) that a manual edit to
xorg.conf was needed. Here is the relevant section:
Option "EnableAGPDMA" "true"
VendorName "Videocard vendor"
BoardName "VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter"
This improved graphics performance (as measured by glxgears) from 150
frames/second to about 600 frames/second.
Kernel is 184.108.40.206-115.fc8
(In reply to comment #10)
> I had a similar problem with my laptop six months ago. I did a bit of googling
> around and found (might have been on a Ubuntu forum) that a manual edit to
> xorg.conf was needed. Here is the relevant section:
> Section "Device"
> Identifier "Videocard0"
> Driver "via"
> BusID "PCI:1:0:0"
> Option "EnableAGPDMA" "true"
> VendorName "Videocard vendor"
> BoardName "VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter"
> This improved graphics performance (as measured by glxgears) from 150
> frames/second to about 600 frames/second.
> Kernel is 220.127.116.11-115.fc8
via driver is off topic for this bug. Please switch to openchrome driver, it
replaces the unmaintained via driver.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.
I also had this problem when using the same (1106:3344) graphics device.
The openchrome driver update to F8
(https://admin.fedoraproject.org/updates/F8/FEDORA-2007-2870) worked great for
me with this device.
Additionally I found a similar problem noted with Ubuntu: