Announcement

Collapse
No announcement yet.

AMD 8.39.4 Driver Released -- 8.35 no longer does it better

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

  • #76
    yum install compat-libstdc++*
    Michael Larabel
    http://www.michaellarabel.com/

    Comment


    • #77
      Thanks .. now it works - correct resolution etc
      Unfortunately I was hoping that POWERPLAY would start to work like magic... but the reality is - no POWERPLAY with the X1600 card in a MacBook Pro C2D thus the fans are running like turbines ...

      Comment


      • #78
        Originally posted by crumpet View Post
        Thanks .. now it works - correct resolution etc
        Unfortunately I was hoping that POWERPLAY would start to work like magic... but the reality is - no POWERPLAY with the X1600 card in a MacBook Pro C2D thus the fans are running like turbines ...

        crumpet,

        did you do anything to get resolution settings to work? can you
        post your xorg.conf? thanks!

        Comment


        • #79
          Originally posted by swannema View Post
          Another masterpiece from AMD, at least now they admit it is for testing only.
          This driver comes with a nice logo that overlays all windows on my system.
          AMD- Testing use only.

          I guess they uploaded the beta version.

          Any ideas how to get rid of that logo, besides downloading the driver again in a couple of days.
          This is fixed in the 8.39.4 driver posted by ATI on 7/25.
          If you are using a distro pkg it will need to be rebuilt using the new 8.39.4 installer.

          Charles

          Comment


          • #80
            Standard xorg.conf generated by system-config-display ... and then
            aticonfig --initial


            # Xorg configuration created by system-config-display

            Section "ServerLayout"
            Identifier "single head configuration"
            Screen 0 "aticonfig-Screen[0]" 0 0
            InputDevice "Keyboard0" "CoreKeyboard"
            EndSection

            Section "Files"
            EndSection

            Section "Module"
            EndSection

            Section "ServerFlags"
            Option "AllowMouseOpenFail" "yes"
            EndSection

            Section "InputDevice"
            Identifier "Keyboard0"
            Driver "kbd"
            Option "XkbModel" "pc105"
            Option "XkbLayout" "gb"
            EndSection

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

            Section "Device"
            Identifier "Videocard0"
            Driver "vesa"
            EndSection

            Section "Device"
            Identifier "aticonfig-Device[0]"
            Driver "fglrx"
            Option "Centermode" "off"
            Option "PseudoColorVisuals" "off"
            Option "OpenGLOverlay" "off"
            Option "VideoOverlay" "off"
            EndSection

            Section "Screen"
            Identifier "Screen0"
            Device "Videocard0"
            DefaultDepth 24
            SubSection "Display"
            Viewport 0 0
            Depth 24
            EndSubSection
            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
            Last edited by crumpet; 07-24-2007, 06:50 PM.

            Comment


            • #81
              Originally posted by Michael View Post
              The problem with F7 x86_64 is falling back to an issue inside the blob. At this point there isn't much you can do about it, but AMD has been aware of this x86_64 issue for a month or two since I personally discussed it with them.
              Ironic, considering that nowadays the AMD 64 chip is so ubiquitous!

              Partha
              www.parha.com

              Comment


              • #82
                Originally posted by crumpet View Post
                Standard xorg.conf generated by system-config-display ... and then
                aticonfig --initial

                thanks... this works for me. i did have to add "Modes 1600x1200" to
                set it to my liking; no big deal, though.

                it didn't occur to me to use system-config-display.

                Comment


                • #83
                  Hmm, Michael posted that Dell wants better ATI drivers for Linux... That's really good =). Thanks DELL (and Michael for the heads up).

                  http://www.phoronix.com/?page=news_item&px=NTkxOA

                  (I don't want to go off-topic here, but I think it's related)

                  Comment


                  • #84
                    Wow, if Dell starts complaining to manufacturers, they'd better listen. I'm sure ati doesn't want Dell to start stocking only nvidia cards with their linux boxes. It might lead Dell to stock only nvidia cards with ALL their boxes. This is ideally how the system works:
                    -manufacturers write lousy drivers, so systems have strange issues
                    -consumers complain to the distributer about problems
                    -distributer complains to manufacturer that their customers don't like manufacturers stuff, backed by the implication that if they don't shape up, the distributer will move to the competition.

                    If Dell is willing to put their muscle behind these complaints, I think it will convince even ATI/AMD's stratified management that more resources need to go into linux driver development. We'll see.
                    Last edited by TechMage89; 07-24-2007, 11:16 PM.

                    Comment


                    • #85
                      Originally posted by d2kx View Post
                      I could only explain this with the new OpenGL application file, but Michael said it is just preparation work. But when the new OpenGL is in, I think you will not get 60 FPS but 100 FPS if you look at how bad fglrx works in comparison with the Windows driver.
                      about 13% increase is still a lot. I wish every release did that. for the last several releases the change was 0 or almost.

                      Comment


                      • #86
                        custom modelines

                        Any word on if they restored custom modeline support? Any word on if they give a crap?

                        Comment


                        • #87
                          I just installed the re-release of the 8.39.4 drivers, and had the exact same problem that crumpet did. I use Ubuntu 7.04 Feisty Fawn, and so don't have system-config-display. I did do a "dpkg-reconfigure xserver-xorg" and then 'aticonfig --initial' as root. Then, I proceeded to fix my xorg.conf to make it look like crumpet's, and finally when it came up... still no 1440x900!

                          Even xrandr didn't list 1440x900 as a usable resolution.

                          Eventually I ended up upgrading down to 8.38.7, restoring my old xorg.conf, and back to the normal ati bugginess.

                          Also, I've had a problem with ati's drivers for years now, having to do with using dual monitors, one a 1440x900 LCD screen, and the other a standard dell CRT.

                          The problem: If I have my secondary monitor (the dell CRT) plugged in at all, at the gdm login screen, I get an ugly bar of junk at the bottom, which seems to be filled with leftover stuff from VRAM. Thankfully this goes away after logging in.. but it's quite annoying due to a secondary effect. It also returns back to normal if I manually unplug the CRT.
                          This causes the mouse's perceived position to be offset from it's onscreen position. What I mean by this is: I see the mouse below where it is on the squished gdm login screen. I can click on the left button to change sessions only if I move the mouse to where the button should be appearing onscreen, in the lower left corner... into the bar of VRAM junk.

                          I may upload a quick photo to show this problem.

                          EDIT:
                          Here's a pic of my LCD

                          Here's the CRT

                          And as you can see in this one... the mouse is below in the "bar o crap", while the options button is hilighted. If I were to click, it would open the menu. It's pretty hard to judge where the mouse actually is this way.
                          Last edited by TrinitronX; 07-31-2007, 01:04 AM.

                          Comment


                          • #88
                            *sigh*
                            Has anyone gotten ModeLines working with this driver? I've a 1440x900 LCD monitor and this driver barfs hard (Sig11) with modelines in xorg.conf - and the driver is overdriving the monitor as far as I can tell -- I know for a fact that 1920x1200 isn't listed in the supported modes for his monitor -- and the fonts look awful as a result - further - there isn't even an option for the correct mode in the list........
                            bah.

                            Mind you -- I *am* seeing a performance improvement -- small but there - in game.

                            Comment


                            • #89
                              Originally posted by Alistair View Post
                              Mind you -- I *am* seeing a performance improvement -- small but there - in game.
                              You will see a much, much bigger improvement in the following months

                              I love ET: QW Beta and can't wait to play the full game with the new fglrx under Linux

                              Comment


                              • #90
                                Ah, the good old junk. Happily for me it's not that big on my display, it appears only in the area of the "watermark".

                                Comment

                                Working...
                                X