![]() |
|
|||||||
| AMD/ATI Linux Technical support and discussion of the ATI/AMD proprietary Linux driver. |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
Hi,
I've installed with succes the new 8.31.5 ATI driver on my fc6. It works perfectly on my laptop Dell 610 with X300 graphical card. Problem is when i, plug an external display + "a big display" xorg.conf my computer just freezes after a while (before this freeze it works fine). I've got the following message into the /var/log/Xorg.0.log file. (II) fglrx(0): [drm] removed 1 reserved context for kernel (II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xd000 at 0xb7e95000 (EE) fglrx(0): === [swlDalHelperSetControllerConfigForRemap] === CWDDC ControllerSetConfig failed: 6 - 0 Here is the copy of my dual display (big display) config file (/etc/X11/xorg.conf): # Xorg configuration created by system-config-display Section "ServerLayout" Identifier "srv_layout" Screen "aticonfig-Screen[0]" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Synaptics" "CorePointer" EndSection Section "Files" EndSection Section "Module" Load "dri" Load "glx" Load "extmod" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "fr" EndSection Section "InputDevice" Identifier "Synaptics" Driver "synaptics" Option "Device" "/dev/input/mice" Option "Protocol" "auto-dev" Option "Emulate3Buttons" "yes" Option "LeftEdge" "120" Option "RightEdge" "830" Option "TopEdge" "120" Option "BottomEdge" "650" Option "FingerLow" "14" Option "FingerHigh" "15" Option "MaxTapMove" "110" Option "VertScrollDelta" "20" Option "HorizScrollDelta" "20" Option "MinSpeed" "0.3" Option "MaxSpeed" "0.75" EndSection Section "Monitor" ### Comment all HorizSync and VertSync values to use DDC: Identifier "aticonfig-Monitor[0]" ModelName "LCD Panel 1400x1050" ### Comment all HorizSync and VertSync values to use DDC: HorizSync 31.5 - 90.0 VertRefresh 59.0 - 75.0 Option "dpms" # Option "VendorName" "ATI Proprietary Driver" # Option "ModelName" "Generic Autodetecting Monitor" EndSection Section "Monitor" Identifier "aticonfig-Monitor[1]" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Device" Identifier "aticonfig-Device[0]" Driver "fglrx" Option "AGPMode" "4" Option "/etc/X11/xorg.conf.fglrx-28" "-28" Option "OverlayOnCRTC2" "1" Option "UseEDID" "FALSE" Option "AddARGBGLXVisuals" "TRUE" BusID "PCI:1:0:0" EndSection Section "Device" Identifier "aticonfig-Device[1]" Driver "fglrx" Option "AGPMode" "4" Option "UseEDID" "FALSE" Option "AddARGBGLXVisuals" "TRUE" BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" Identifier "aticonfig-Screen[0]" Device "aticonfig-Device[0]" Monitor "aticonfig-Monitor[0]" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[1]" Device "aticonfig-Device[1]" Monitor "aticonfig-Monitor[1]" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" EndSubSection EndSection Section "Extensions" Option "Composite" "Disable" EndSection Any idea, of what is wrong there ? Sherl |
|
#2
|
|||
|
|||
|
So you have a big desktop going and then you try to enable an additional display? So you're trying to use a total of three displays? If so, more than two displays aren't currently supported by the fglrx drivers.
|
|
#3
|
|||
|
|||
|
Hi Michael,
No, i'm using both! - a unique LCD condiguration when i'm at home - a dual display config (LCD + external display) when i'm at the office And when a i use big desktop configuration "for the dual display support" i've got the freeze problem. Sh |
|
#4
|
|||
|
|||
|
And about how long does it take till it freezes? You just mention it's a while. So after a "while" the display freezes and totally locks up?
|
|
#5
|
|||
|
|||
|
Yes after less than 10 minutes, X is freezed.
I can do [Ctrl][alt][Del] to kill X or whatever (i can display the console mode either). I just have to reboot... Sh |
|
#6
|
|||
|
|||
|
Sounds like it might be a driver bug. If you have any more specific details as to your system configuration/environment, I can probably try to reproduce it.
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|