Announcement

Collapse
No announcement yet.

AMD 8.42.3 Driver Released -- The Baby Is Born!

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • After such a not-so-smooth compiz experience, I could not help wondering if 8.42.3 is a REAL release.
    Anyone who can tell me it is not true?

    Comment


    • If anyone has a fix for the flickering video problem please post.

      Ubuntu Gutsy 32bit x1600 mobility

      Comment


      • I was a little disappointed to find that 8.42.3 does not support the FireGL V5250 in my Thinkpad T60p.

        So I applied the patch (successfully) specifying
        #define HACK_PCIID 0x71c4

        -- this is the pci id of my V5250 as reported by /sbin/lspci -n

        I then built my xorg.conf with the crucial addition of
        ChipId 0x71c5

        in the "Device" section

        -- other varient suggestions are welcome

        X starts, but I've yet to get a workable config.

        I was hoping I'd have decent power management/screen flipping at last, but so far 8.42 has been disappointing.

        Has anyone gone through a similar process with 8.42?

        Here's my basic file (which works with 8.35)
        # Xorg configuration created by pyxf86config

        Section "ServerLayout"
        Identifier "Default Layout"
        Screen 0 "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" "gb"
        EndSection

        Section "InputDevice"
        Identifier "Synaptics"
        Driver "synaptics"
        Option "Device" "/dev/input/mice"
        Option "Protocol" "auto-dev"
        Option "Emulate3Buttons" "yes"
        Option "LeftEdge" "1700"
        Option "RightEdge" "5300"
        Option "TopEdge" "1700"
        Option "BottomEdge" "4200"
        Option "FingerLow" "25"
        Option "FingerHigh" "30"
        Option "MaxTapTime" "180"
        Option "MaxTapMove" "220"
        Option "VertScrollDelta" "100"
        Option "MinSpeed" "0.06"
        Option "MaxSpeed" "0.12"
        Option "AccelFactor" "0.0010"
        Option "SHMConfig" "on"
        EndSection

        Section "Monitor"
        Identifier "aticonfig-Monitor[0]"
        Option "VendorName" "ATI Proprietary Driver"
        Option "ModelName" "Generic Autodetecting Monitor"
        Option "DPMS" "true"
        EndSection

        Section "Device"
        Identifier "aticonfig-Device[0]"
        Driver "fglrx"
        Option "VideoOverlay" "on"
        #Option "MonitorLayout" "AUTO, CRT"
        Option "DesktopSetup" "0x00000100"
        Option "EnableMonitor" "lvds,tmds1"
        Option "ForceMonitors" "lvds,tmds1"
        ChipId 0x71c5
        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 "Extensions"
        Option "Composite" "0"
        EndSection

        Yet with this my 2nd screen (1st is lvds - internal laptop, second is tmds1 - DVI) doesn't even come on...

        Trying aticonfig --enable-monitor=lvds,tmds1 --effective=now just gives
        ati_dm: DGLRX)EnableDisplays failed when try to enable display: a.

        Comment


        • Ok, after a reboot the 2nd screen does enable, however I cannot get it to run at 1600x1200 (native) on this second screen. Instead it's at 1024x768

          Also ccc doesn't run

          There was a problem initializing Catalyst Control Centre..

          - possibly due to the patched pci id?

          Comment


          • Originally posted by planetf1 View Post
            Ok, after a reboot the 2nd screen does enable, however I cannot get it to run at 1600x1200 (native) on this second screen. Instead it's at 1024x768

            Also ccc doesn't run

            There was a problem initializing Catalyst Control Centre..

            - possibly due to the patched pci id?
            I've got a working dual-head layout (1280x800+1600x1200):
            Code:
                Option      "backingstore" "true"
                Option      "DesktopSetup" "vertical,reverse"
                Option      "EnableMonitor" "lvds,crt1"
                Option      "Mode2" "1600x1200"
                Option      "EnablePrivateBackZ" "on"
            This is the relevant part of my xorg.conf (Section Device).
            There is nothing more needed for me.
            Works with 3D on both screens.

            The driver does now work fine for me with xorg-server-1.4.
            I even recognized, that I now can switch to console "sometimes", unfortunately it's not reliable.

            Comment


            • I used it for about 30 minutes (Ubuntu 7.10) before I found that it was slower than the FGLRX+XGL I had been using earlier. Video was better with XGL, as was simple things like moving a window and switching applications.

              The difference was minor, to be sure (maybe 10-20%), but noticable - and since I don't use any DRI apps then XGL is the ticket for me. It was pretty cool to be running compiz and having glxinfo show the full DRI support.

              That said, now that AIGLX is actually _IN THE DRIVER_ it will probably improve such that in the next release or two it will surpass the performance I enjoy with XGL today.

              Oh, and the video tearing was AWFUL. It was very bad with XV, GL, and GL2 in MPlayer. Yikes.


              EDIT:

              Yes, I tried XGL on top of 8.42.3. It was faster than AIGLX, but still slower than the previous driver. My guess is that with the driver rewrite they optimized the rendering paths for more "game" style needs (lots of polys, multitextures, bump mapping), but not the kinds of things compiz needs (big areas with textures that are 1:1 for screen pixels). Compiz competes with the functional eye-candy of Vista and Leopard - and with the newest Linux distros running it by default, the speed will eventually get there I'm sure.


              EDIT2:

              If there are some xorg.conf options I could try to boost AIGLX (and video playback) performance, I'd love to try them out. The straight 2d performance of the FGLRX driver is quite nice (using metacity), so a combination of that with the 3d accellerated stuff would be amazing. I feel confident that they will eventually get there.
              Last edited by Antiphonal; 24 October 2007, 12:38 PM.

              Comment


              • Originally posted by JackDanielz View Post
                If anyone has a fix for the flickering video problem please post.

                Ubuntu Gutsy 32bit x1600 mobility
                If you want video to work without flickering try using x11 in mplayer, vlc, smplayer, gnome mplayer etc. that worked for me. But I still have flickering when running Zattoo and Google Earth. Does anybody else get this black screen when starting a video file and then the video starts?

                Regards

                Andr?

                Comment


                • i'm running compiz and all effects are working, but text is not displaying almost everywhere, and in konsole forexample it doesn't redrawing (text just staying on the screen, even if you deleting it)
                  what is the problem, does anybody has a solution?

                  Comment


                  • I tried the X11 rendering in MPlayer. WAY too slow, but no flicker. It was almost impossible for the player to sync the video - it was that bad.

                    Comment


                    • I have ugly menu borders on kde windows. See here:
                      http://img86.imageshack.us/my.php?im...orders1fr2.jpg

                      Anyone knows how to fix that? I disabled the kde menu effects, but that didn't help.

                      Comment

                      Working...
                      X