No, the Catalyst driver does not use KMS.
During the installation process the radeon KMS code is disabled, then after reboot the Catalyst driver starts up the "traditional UMS way".
Of course NOT. Very unlikely that will ever happen.
No, the Catalyst driver does not use KMS.
During the installation process the radeon KMS code is disabled, then after reboot the Catalyst driver starts up the "traditional UMS way".
Hey Cuppa!
Ubuntu just released a driver for laptop... it doesn't work (again), but Jockey now finds it^^
Sorry for the double post, but I can't seem to find an edit button!
Anyways... error is still the same
(II) Module "ddc" already built-in
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x4a3248]
[...]
18: /usr/bin/X (0x400000+0x25d59) [0x425d59]
Segmentation fault at address (nil)
Caught signal 11 (Segmentation fault). Server aborting
can someone post his xorg.conf ?
somehow it doesnt configure it in my system and its blank.
(ubuntu 10.04)
didn'twork for you ?Code:sudo aticonfig --initial
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Section "Files"
EndSection
Section "Module"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
sudo aticonfig --initial
didnt work for me, got just blank xorg.conf
thx for ur xorg, got it working now![]()