Announcement

Collapse
No announcement yet.

Ubuntu Gets Another ATI Catalyst Driver Handout

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • xpander
    replied
    sudo aticonfig --initial

    didnt work for me, got just blank xorg.conf

    thx for ur xorg, got it working now

    Leave a comment:


  • kernelOfTruth
    replied
    Originally posted by xpander View Post
    can someone post his xorg.conf ?
    somehow it doesnt configure it in my system and its blank.
    (ubuntu 10.04)
    didn't
    Code:
    sudo aticonfig --initial
    work for you ?

    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

    Leave a comment:


  • xpander
    replied
    can someone post his xorg.conf ?
    somehow it doesnt configure it in my system and its blank.
    (ubuntu 10.04)

    Leave a comment:


  • bautz
    replied
    Originally posted by TheWretched View Post
    Anyways... error is still the same
    I tested latest catalyst with xorg 1.7.6 but still the same error as you

    I'm on Archlinux x86_64 kernel 2.6.33, sony vaio eb1z1e with ATI HD5650

    Leave a comment:


  • TheWretched
    replied
    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

    Leave a comment:


  • TheWretched
    replied
    Hey Cuppa!

    Ubuntu just released a driver for laptop... it doesn't work (again), but Jockey now finds it^^

    Leave a comment:


  • bridgman
    replied
    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".

    Leave a comment:


  • Kano
    replied
    Of course NOT. Very unlikely that will ever happen.

    Leave a comment:


  • csaket
    replied
    is it possible to use kms with the new drivers?

    Leave a comment:


  • Cuppa-Chino
    replied
    Originally posted by Cuppa-Chino View Post
    hi krionius or other radeon mobility hd 5650 users:
    as I just cannot get it to work, xorg.0.log seems to show segmentation, I would be grateful if you could confirm the following things please:
    a) distro - mine is lucid lynx beta 1 amd64 fresh install
    b) version installed 1,2,3 or 4 (am guessing 3 ??) -- fglrx_8.721-0ubuntu3_amd64.deb - I tried 3 and 4
    c) xorg.conf just the standard from sudo aticonfig --initial ie mine is
    Code:
    Section "Device"
    	Identifier  "aticonfig-Device[0]-0"
    	Driver      "fglrx"
    	BusID       "PCI:1:0:0"
    EndSection

    d) exact device yours is returned as - mine is:
    Code:
    $ lspci -nn -vv | grep Radeon
    01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5600 Series] [1002:68c1] (prog-if 00 [VGA controller])
    01:00.1 Audio device [0403]: ATI Technologies Inc Redwood HDMI Audio [Radeon HD 5600 Series] [1002:aa60]

    e) make/model of your laptop -- mine is sony e-series

    thanks a million
    ok no progress but another idea: http://bbs.archlinux.org/viewtopic.php?pid=732254

    pointed at the DDC /EDID of the laptop screen potentially being the source of the segfault. I tried reading the EDID with powerstrip in windows but that failed: no data readable . In windows the screen ended up with microsoft as manufacturer etc.

    could somebody tell me if it is possible to HARD drop DDC/EDID reading with the xorg.conf, I have googled and tried things like:
    Code:
    Option "UseEDID" "FALSE"
    Option "NoDDC" "true"
    but that has not worked for me.

    Leave a comment:

Working...
X