http://qa.mandrakesoft.com/show_bug.cgi?id=2728
Product: drakxtools
Component: XFdrake
Summary: DREI,Dual Monitors with ATI Radeon and ATI 128, and
Monitor Resolutions
Version: 9.1-13mdk
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: critical
Priority: P2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
This issue involves both monitors going blank and the total lock up of the
system when you try to startx after configuring the system for dual monitor
support with an ATI 128 AIW or ATI Radeon AIW card and an ATI Xpert128. I have
seen it happen with VIA boards, ASUS boards, with both P4s and Celerons. I have
determined that, while this issue appears to be based on an apparent limitation
in XFree86, it was caused by how Mandrake configured the system. I know this
because after I downloaded XFree86 and configured it manually there were no
problems. The issue appears to be that Xpert128 cannot seem to use DRI in
concert with a Radeon AIW or 128 AIW cards. It may be because the driver does
not support it or it may be an actual bug. I think it may be the former because
XFree86s own distribution will not run DRI at all for this configuration. The
configuration tool does try to configure DRI but it then detects the problem and
keeps both screens at 16 colors which means it never really loads DRI. At first
I tried disabling DRI which works but sucks. Then after tweaking some settings I
learned that if you use the device configuration below that it will work and
still let you use DRI with AIW card. I have noted the changes from the default.
There also seems to be an issue with Mandrake not configuring the second monitor
correctly when the first monitor is Plug and Play but the second is not. The
second monitor always stays at 640x480, unless you go in an write your own
monitor section. Standard monitor settings work they are just not there, ie no
HorizSync or VertRefresh so it does not know how to draw the higher resolutions.
One caveat about the above mentioned issues on my system the AGP card is set to
be initialized first by the BIOS. I have seen that it does not lock up if the
PCI inits first but neither does it work correctly. The screens are still miss
sized and the resolution is still wrong. While initializing PCI first is default
the default BIOS setting, in WinSucks this is the only way to get access to AIW
cards video and tuner features and is how the systems will come configured from
store if you have an AIW card. I am not sure if this limitation with AIW cards
is also true with Linux, but I think it may be because of how these cards are
designed to advertise their components to the operating system. I was once
reading the Matrox builds intelligence into their cards to avoid this very same
problem.
Well, if I am totally off base please forgive me but I hope this helps at least
set you on the right direction.
Section "Device"
Identifier "device1"
VendorName "ATI"
BoardName "ATI Radeon"
Driver "radeon"
Screen 0
BusID "PCI:1:0:0"
Option "DPMS"
Option "AGPMode" "4" *Change One: XFree86 suggested this and insmod agpgart
EndSection
Section "Device"
Identifier "device2"
VendorName "ATI"
BoardName "ATI Rage 128"
Driver "r128"
Screen 0
BusID "PCI:2:9:0"
Option "DPMS"
Option "no_accel" *Change 2: This is the important one to fix the lock up
Option "UseCCEFor2D" "false" *Change 3: XFree86 suggest this too.
EndSection
Thanks,
Robert
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
