Bug 453812 - xserver autoconf doesn't care about xgi
xserver autoconf doesn't care about xgi
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-sis (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-02 14:05 EDT by Will Woods
Modified: 2018-04-11 06:48 EDT (History)
1 user (show)

See Also:
Fixed In Version: xorg-x11-server-Xorg-1.5.1-9.fc10
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-10 11:39:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Xorg.0.log (422.60 KB, text/plain)
2008-07-07 10:52 EDT, Will Woods
no flags Details
X.log from anaconda on a sis-chipset machine (429.30 KB, text/plain)
2008-10-06 14:06 EDT, Will Woods
no flags Details

  None (edit)
Description Will Woods 2008-07-02 14:05:50 EDT
My awesome XGI Volari Z7 video chip is not autodetected, and I end up with vesa.

PCI id is 18ca:0020; see below for more info.

(--) PCI:*(0@5:7:0) XGI Technology Inc. (eXtreme Graphics Innovation) Volari Z7
rev 0, Mem @ 0xfc000000/0, 0xfe6c0000/0, I/O @ 0x00
00dc80/0, BIOS @ 0x????????/65536
(==) Matched vesa for the autoconfigured driver
New driver is "vesa"

[root@norfair ~]# lspci -vv -nn -s 5:7
05:07.0 VGA compatible controller [0300]: XGI Technology Inc. (eXtreme Graphics
Innovation) Volari Z7 [18ca:0020] (prog-if 00 [VGA controller])
	Subsystem: Dell Device [1028:01ae]
	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-
	BIST result: 00
	Region 0: Memory at fc000000 (32-bit, prefetchable) [size=32M]
	Region 1: Memory at fe6c0000 (32-bit, non-prefetchable) [size=256K]
	Region 2: I/O ports at dc80 [size=128]
	Expansion ROM at fe600000 [disabled] [size=64K]
	Capabilities: [40] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Comment 1 Matěj Cepl 2008-07-02 17:48:06 EDT
Please attach your X server config file (/etc/X11/xorg.conf), X server log file
(/var/log/Xorg.*.log), and /var/log/anaconda.xlog to the bug report as
individual uncompressed file attachments using the bugzilla file attachment link

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.
Comment 2 Will Woods 2008-07-03 09:38:46 EDT
As mentioned in the bug report - this is with *autoconfiguration* in X. So
there's no xorg.conf. And I included the relevant section of Xorg.0.log already.
Comment 3 Matěj Cepl 2008-07-04 08:59:27 EDT
Will, et tu, Brute? Could we get whole /var/log/Xorg.*.log, please?
Comment 4 Will Woods 2008-07-07 10:52:40 EDT
Created attachment 311166 [details]
Comment 5 Will Woods 2008-07-07 10:53:44 EDT
Xorg.0.log attached.
Comment 6 Matěj Cepl 2008-07-08 10:17:34 EDT
E.g., that zillion of lines "Failed to find device matching" is actually quite
Comment 7 Adam Jackson 2008-07-14 17:55:34 EDT
Updating summary so I have some idea what's going on.

The "Failed to find device" thing should be gone now, at least.
Comment 8 Will Woods 2008-10-06 14:06:50 EDT
Created attachment 319582 [details]
X.log from anaconda on a sis-chipset machine

Nope - the "Failed to find device" thing persists in current rawhide. 

This Xorg.0.log is from anaconda, during a rawhide install.
Comment 9 Adam Jackson 2008-10-07 14:10:51 EDT
Alright you.  Try xorg-x11-server-Xorg-1.5.1-9.fc10 and let me know how it goes.
Comment 10 Will Woods 2008-10-10 11:39:53 EDT
Works like a charm. No more "Failed to find device" messages in the log, either.

Note You need to log in before you can comment on or make changes to this bug.