Bug 2401

Summary: DVI monitor misdetected w/ Soltek SL-B7C-FGR mobo
Product: xorg Reporter: CrystalCowboy <schuller>
Component: Driver/RadeonAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: high CC: erik.andren
Version: 6.8.1Keywords: l10n
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description CrystalCowboy 2005-01-27 14:19:18 UTC
With "radeon" driver and radeon 92xx card in AGP slot, display shows colorful
but uninterpretible stripes or other artifacts reminiscent of sync failure, when
X starts. Mobo is Soltek SL-B7C-FGR with KM400A Northbridge and integrated
Unichrome graphics. I have tried Radeon 9200 and 9250 cards in tha AGP slot.
With radeon driver, problem is as described. Graphics cards test fine with
radeon driver on other mobos. I have switched to the "vesa" driver, which works.
I have seen this problem with all versions of x.org under Fedora Core 2 and Core
3, with several 1024x768 or 1280x1024 LCD monitors. Most recent version of xorg
tested is xorg-x11-6.8.1-12.FC3.21 under FC3.
Comment 1 Alex Deucher 2005-01-28 15:30:19 UTC
what type of monitor ae you trying to use?  DVI? crt?  you may need to force the
type using the monitorlayout option. see bug 1559
Comment 2 CrystalCowboy 2005-01-31 07:53:27 UTC
(In reply to comment #1)
> what type of monitor ae you trying to use?  DVI? crt?  you may need to force the
> type using the monitorlayout option. see bug 1559

Problem occurs with both VGA HD15 monitor attachment and DVI monitor attachment.
Other than changing Driver "radeon" to "vesa", no other changes are needed to
get X working. Hsync, Vsync etc. are set correctly. I will look into monitorlayout.
Comment 3 CrystalCowboy 2005-01-31 10:19:03 UTC
MonitorLayout has no effect.

xorg.conf file: 
http://staff.chess.cornell.edu/~schuller/xorg.conf

X log file with "radeon" driver:
http://staff.chess.cornell.edu/~schuller/Xorg.0.log.monitorlayout

X log file with "vesa" driver:
http://staff.chess.cornell.edu/~schuller/Xorg.0.log.vesa
Comment 4 T. Hood 2005-09-23 09:31:39 UTC
(In reply to comment #0)
> With "radeon" driver and radeon 92xx card in AGP slot, display shows colorful
> but uninterpretible stripes or other artifacts reminiscent of sync failure


The log shows that you are using two displays.  Which display works and which
one doesn't.  Please give more details about these monitors.
Comment 5 CrystalCowboy 2005-09-25 09:40:33 UTC
(In reply to comment #4)
> The log shows that you are using two displays.  Which display works and which
> one doesn't.  Please give more details about these monitors.

The log is wrong. I am using only one monitor, correctly defined in the
xorg.conf file as a NED LCD71V (typical 1280x1024 LCD with DVI and HD15
connectors). Note that the log file with the VESA driver shows no indication of
a second monitor.
Comment 6 T. Hood 2005-09-29 03:56:54 UTC
See #1559.
Comment 7 Erik Andren 2006-04-02 18:42:29 UTC
Whats the status of this bug using a current version of xorg / radeon driver?
Comment 8 Erik Andren 2006-05-10 06:28:55 UTC
Ping to the bug submitter!
Comment 9 CrystalCowboy 2006-05-11 02:17:11 UTC
I have Fedora Core 5 installed now with the latest updates as of this morning
(2006-05-10). kernel 2.6.16-1.2111_FC5, xorg-x11-drivers-7.0-2. I currently have
a  monitor hooked up to the VGA (HD15) port.

The problem persists. When I set the driver in /etc/X11/xorg.conf to be
"radeon", on the next start of X the screen comes up black.

The latest /var/log/Xorg.0.log is at:
http://staff.chess.cornell.edu/~schuller/060510_xlog

The end of "dmesg" output is:
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 21
[drm] Initialized radeon 1.22.0 20051229 on minor 0
agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: Badness. Don't know which AGP mode to set. [bridge_agpstat:1f000a0a
vga_agpstat:ff00021b fell back to:- bridge_agpstat:1f000208 vga_agpstat:ff00021b]
agpgart: Bridge couldn't do AGP x4.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode
[drm] Loading R200 Microcode
Comment 10 CrystalCowboy 2006-05-11 02:20:02 UTC
(In reply to comment #9)
> I have Fedora Core 5 installed now with the latest updates as of this morning
> (2006-05-10). kernel 2.6.16-1.2111_FC5, xorg-x11-drivers-7.0-2. I currently have
> a  monitor hooked up to the VGA (HD15) port.
> 
> The problem persists. When I set the driver in /etc/X11/xorg.conf to be
> "radeon", on the next start of X the screen comes up black.
> 
> The latest /var/log/Xorg.0.log is at:
> http://staff.chess.cornell.edu/~schuller/060510_xlog
> 
> The end of "dmesg" output is:
> ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 21
> [drm] Initialized radeon 1.22.0 20051229 on minor 0
> agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
> agpgart: Badness. Don't know which AGP mode to set. [bridge_agpstat:1f000a0a
> vga_agpstat:ff00021b fell back to:- bridge_agpstat:1f000208 vga_agpstat:ff00021b]
> agpgart: Bridge couldn't do AGP x4.
> agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode
> agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode
> [drm] Loading R200 Microcode

current xorg.conf file which produced the above:
http://staff.chess.cornell.edu/~schuller/060510_xorg.conf

I am still operating with the vesa driver.
Comment 11 CrystalCowboy 2006-05-20 00:33:08 UTC
(In reply to comment #10)
I went into the BIOS and switched it from "AGP 8X" to "AGP 4X" and now it works
with the radeon driver.
Comment 12 CrystalCowboy 2006-05-20 05:43:23 UTC
I have three of these machines. The one with FC5 and a second one with FC4
(kernel 2.6.16-1.2096_FC4,  xorg-x11 6.8.2-37) both work unconditionally, with
either a VGA or a DVI monitor connection.

A third machine, with FC4 (kernel 2.6.12-1.1398_FC4, updated to
xorg-x11-6.8.2-37.FC4.49.2.1) , works for VGA but not with DVI. I can live with
this, and can write it off as a bad card.

thanks.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.