Announcement

Collapse
No announcement yet.

AMD 8.36.5 Driver -- The Still no fglrx AIGLX Support Edition

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

  • #46
    Thanks for the information without breaking your AMD-Betatester-NDA Now try to do the same with the release date

    Comment


    • #47
      Hi, Michael -

      Just wondering if you were back in town and had a spare few to answer the questions I had had regarding changes in the drivers from 8.32.5 to all versions > 8.32.5; I'm still having the same problem(s), now with more machines.

      I've taken this as far as I can go without the benefit of your assistance (as packager of the drivers) or some other rather deep technical insight. At this point, I really need to resolve this - somehow. I posted another summary regarding the latest system that won't work with any driver > 8.32.5; it's a completely different system, card, etc. than my others; about the only thing they have in common is FC6 (and its X server, etc.).

      Thanks in advance for your help,
      Larry Morley

      Comment


      • #48
        Yes, I am now back from JavaOne and almost caught up in all the work.

        In 8.32.5 was the 2.6.19 support in the mainstream code, switching from using system-config-display to aticonfig for the X configuration. In 8.33.6 atiogl_a_dri.so was removed since that was a blob related to R200 that was removed from the driver itself. /etc/ati/control was also introduced mainstream in that version.

        In 8.34 was Fedora 7 support with a Linux 2.6.20 patch (temporary). In 8.35 fireglcontrolpanel was removed and then linked to the new Catalyst Control Center.

        Then in 8.36 the Linux 2.6.20 patch was removed along with adding esut.a and glesx.so..
        Michael Larabel
        http://www.michaellarabel.com/

        Comment


        • #49
          Originally posted by Michael View Post
          Yes, I am now back from JavaOne and almost caught up in all the work.
          First, thanks for getting back to me; I know how much of a joy it is trying to get caught up (or kept up). Second, thanks for the history; hopefully, it'll help explain what happened.

          I verified again that the version 8.33.6 is the one where X on the systems I'm trying to get working here go off into the weeds upon attempting to load libfglrxdrm.so. That's consistent with the fact that the server starts up (albeit without DRI/DRM support) if I make libfglrxdrm.so unavailable. The problem has occurred with every Radeon X1600 (R500 based) I've tried, and also with two 9800s (R350 based AGP cards). In all cases the OS was FC6, and version 8.32.5 of the driver works.

          Tried mixing peices of different driver versions (eg., to see if adding back in atiogl would allow the driver to work, etc.); but, the X server detected the version mismatch and wouldn't load.

          So, at this point, it would appear that the question is one of "what do several X1600 / R500 cards and two Radeon 9800's (R350) have in common with the 200's, so much so that removing a chunk of code to support one would affect the other?" As far as I can tell, the code for libfglrxdrm isn't published, so there's not much I can do there...

          It almost has to be something simple. Either that, or I'm missing something that's dead obvious. Either way, I would love to know what's going on.

          What I was seeing with respect to file locations seems to be related to how the driver is instaled (eg., as a module, or as a group of RPMs). I hecked that again too, and there are quite a few differences as fa rwhere

          Does anything at all spring to mind? This iust too bizarre.

          Thanks again,
          Larry

          Comment


          • #50
            Is there any errors in your Xorg.0.log or anything "weird" in your xorg.conf? I have done at least 50 new Fedora installs since 8.32 and haven't run into a issue like you describe.
            Michael Larabel
            http://www.michaellarabel.com/

            Comment


            • #51
              Originally posted by Michael View Post
              Is there any errors in your Xorg.0.log or anything "weird" in your xorg.conf? I have done at least 50 new Fedora installs since 8.32 and haven't run into a issue like you describe.
              Maybe you can check his thread:

              http://phoronix.net/forums/showthread.php?t=2828

              Comment


              • #52
                Originally posted by Michael View Post
                Is there any errors in your Xorg.0.log or anything "weird" in your xorg.conf? I have done at least 50 new Fedora installs since 8.32 and haven't run into a issue like you describe.
                Have you tried reverting to a very simple xorg.conf? A configuration as basic as you can have, just to see if it starts up properly?
                Michael Larabel
                http://www.michaellarabel.com/

                Comment


                • #53
                  No fglrx 8.37 this week

                  Comment


                  • #54
                    Originally posted by Michael View Post
                    Is there any errors in your Xorg.0.log
                    Nope; just two benign warnings from statements that aticonfig itself puts in the thing:
                    Code:
                    $ grep WW /var/log/Xorg.0.log
                            (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
                    (WW) fglrx: No matching Device section for instance (BusID PCI:2:0:1) found
                    (WW) fglrx(0): Option "VendorName" is not used
                    (WW) fglrx(0): Option "ModelName" is not used
                    $ grep EE /var/log/Xorg.0.log
                    Current Operating System: Linux zeus.cslimits.net 2.6.20-1.2948.ljm #1 SMP PREEMPT Mon May 7 16:57:11 EDT 2007 i686
                            (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
                    (II) Loading extension MIT-SCREEN-SAVER
                    or anything "weird" in your xorg.conf?
                    No there too; I have tried a lot of different settings (and combinations of settings); none of them ever made a difference with respect to the lockup-on-X-startup problem though. Currently, xorg.conf reads:

                    Code:
                    Section "ServerLayout"
                            Identifier     "single head configuration"
                            Screen      0  "aticonfig-Screen[0]" 0 0
                            InputDevice    "Mouse0" "CorePointer"
                            InputDevice    "Keyboard0" "CoreKeyboard"
                    EndSection
                    
                    Section "Files"
                            FontPath     "unix/:7100"
                    EndSection
                    
                    Section "Module"
                            Load  "dri"
                            Load  "glx"
                    EndSection
                    
                    Section "ServerFlags"
                            Option      "AIGLX" "off"
                    EndSection
                    
                    Section "InputDevice"
                            Identifier  "Mouse0"
                            Driver      "mouse"
                            Option      "Protocol" "IMPS/2"
                            Option      "Device" "/dev/input/mice"
                            Option      "ZAxisMapping" "4 5"
                            Option      "Emulate3Buttons" "yes"
                    EndSection
                    
                    Section "InputDevice"
                            Identifier  "Keyboard0"
                            Driver      "kbd"
                            Option      "XkbModel" "pc105"
                            Option      "XkbLayout" "us"
                    EndSection
                    
                    Section "Monitor"
                            Identifier   "aticonfig-Monitor[0]"
                            Option       "VendorName" "ATI Proprietary Driver"
                            Option       "ModelName" "Generic Autodetecting Monitor"
                            Option       "DPMS" "true"
                            DisplaySize  340        270
                            HorizSync    31.0 - 80.0
                            VertRefresh  56.0 - 75.0
                    EndSection
                    
                    Section "Device"
                            Identifier  "aticonfig-Device[0]"
                            Driver      "fglrx"
                    EndSection
                    
                    Section "Screen"
                            Identifier "aticonfig-Screen[0]"
                            Device     "aticonfig-Device[0]"
                            Monitor    "aticonfig-Monitor[0]"
                            DefaultDepth     24
                            SubSection "Display"
                                    Viewport   0 0
                                    Depth     24
                                    Modes    "1280x1024" "1152x864" "1024x768" "800x600"
                            EndSubSection
                    EndSection
                    
                    Section "DRI"
                            Group        0
                            Mode         0666
                    EndSection
                    
                    Section "Extensions"
                            Option      "Composite" "False"
                            Option      "XVideo" "Enable"
                    EndSection
                    As far as I know that's about as vanilla as one can get it - again, though, if I'm missing something obvious...

                    I have done at least 50 new Fedora installs since 8.32 and haven't run into a issue like you describe.
                    All in (more or less) the following manner, right?

                    Code:
                    rpm -e `rpm -qa | grep "^ATI"`
                    rpm -e `rpm -qa | grep "kernel-module.*ATI"`
                    and then either:

                    Code:
                    sh ./ati-driver-installer-8.x.y-x86.x86_64.run --buildpkg Fedora/FC6
                    or

                    Code:
                    sh ./ati-driver-installer-8.x.y-x86.x86_64.run --extract
                    cd fglrx-install*
                    <apply any patches, etc. needed here...>
                    sh ./ati-installer.sh 8.x.y --buildpkg Fedora/FC6
                    cd ..
                    and finally

                    Code:
                    rpm -Uvh --force `ls *.rpm`
                    or

                    Code:
                    rpm -Uvh --force *.rpm
                    etc.

                    I'm certain that I'm not having an rpmbuild problem; I can always managed to get the RPMs to build; they have everything they're supposed to have, at least according to rpm -qipl - but, for whatever reason, my track record is 180 degrees out of phase with yours; I have not yet been able to get one single card working with anything newer than 8.32.5. On one machine, I even tried using the livna drivers; the results were exactly the same.

                    What's even more peculiar is I can't seem to screw the "vintage" drivers up: I can remove the 8.32.5 driver using rpm -e, or rm it's files, or whatever - at which point X won't start - but, upon reinstalling it (w/ rpm -Uvh --force), X comes back to life every single time.

                    Is there *anything* that looks out of order, unusual, shouldn't be there, etc. in the above? There's gotta be something I'm either missing, overlooking, etc. This is just too wierd.

                    Thanks
                    Larry

                    Comment


                    • #55
                      do any1 know if AIGLX will ever come? I am soon switching to NVidia. this is fu'''ng annoying. I want to play win games (like counter-strike) with OpenGL AND have Beryl, without logging in and out all the time. This, AMD, is crappy work.

                      Comment


                      • #56
                        Originally posted by krypton View Post
                        do any1 know if AIGLX will ever come? I am soon switching to NVidia. this is fu'''ng annoying. I want to play win games (like counter-strike) with OpenGL AND have Beryl, without logging in and out all the time. This, AMD, is crappy work.
                        It is coming.
                        Michael Larabel
                        http://www.michaellarabel.com/

                        Comment


                        • #57
                          Michael -

                          Originally posted by Michael View Post
                          Have you tried reverting to a very simple xorg.conf? A configuration as basic as you can have, just to see if it starts up properly?
                          I think our posts & replies are starting to overlap / cross; sorry about that. In the message I posted just prior to this one, in response to your question (above), I indicated that yes, I have tried a simple xorg.conf. I've tried others, too; none of them make a difference for drivers version 8.32.5 and up. In that same post, I also outlined the installation procedure I've been using; perhaps there's something there I'm missing. The other post which someone referenced earlier (http://phoronix.net/forums/showthread.php?t=2828)) I made after encountering the exact same problems on a completely different machine (different processor, different motherboard, card was AGP as opposed to PCI-e & had a different series (it was a R350 as opposed to R500)).

                          At any rate, thanks for the help, and sorry for the confusion; just so it's clear what the heck I'm talking about, I've tried both simple and esoteric xorg.conf's; I've tried stock kernels and my usual custom tailored one. About the only thing that seems to make a difference is whether or not DRI/DRM is actually running; after going over the ptrace, etc. output I gathered after I ran xinit under it, the drivers are all dying after libfglrxdrm.so loads; once that library is loaded by Xorg, the server goes off into some sort of loop where it's busy-waiting (in ring 0 code), the system deadlocks, etc.; if I can keep it from loading, X comes up - but I don't have DRI, and therefore, don't have accellerated graphics functionality - so it'd be extremely presumptious for me to say "this is all due to libfglrxdrm.so".

                          That said, is there anything "funny" about Fedora Core 6's X server? Or DRM/DRI implementation?

                          As I noted in the other post (http://phoronix.net/forums/showthread.php?t=2828) I did find an older howto and tried following it; it stated the kernel had to be rebuilt without DRM/DRI support; all that resulted in was no DRI, at all, though, and no improvement.

                          Is my installation procedure the same as the one you've been using? I can post the kernel config I'm using currently; however, since nothing I've changed there has had any effect on X, I've held off on doing that to avoid further clouding the issue.

                          This is really, really strange; at this point, I would say it almost has to come down to a simple, seemingly trivial thing that I'm either missing, or have installed and shouldn't; or that I'm doing, or not doing; etc.

                          Thanks again,

                          Larry

                          Comment


                          • #58
                            Michael:
                            You seem to be the wiz about these fora, can you tell me if there is any particular issue getting the AGP version of pcie cards running on these drivers?
                            Is there some hidden, undocumented elsewhere setting in xorg.conf or in module parameters for fglrx that I can set to make my hot new card work?
                            My trusty 9600 is back in and works a charm on the xorg.conf I set up for the X1650 Pro, all is working on either DVI out or AGP out and no problems with vt switching on 8.35.5. 8.36.5 works as well. The 1650 agp stops *dead* at dri installation complete.
                            The errors in Xorg.0.log while loading the drivers for the X1650Pro are :
                            (grep -e WW -e EE Xorg.0.log)
                            Code:
                            (WW) The directory "/usr/share/fonts/TTF/" does not exist.
                            (WW) The directory "/usr/share/fonts/OTF" does not exist.
                            (WW) The directory "/usr/share/fonts/CID/" does not exist.
                            (WW) Ignoring unrecognized extension "AIGLX"
                            (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
                            (EE) end of block range 0x7ffffff < begin 0xf0000000
                            (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
                            (EE) end of block range 0x7ffffff < begin 0xf0000000
                            (WW) LoadModule: given non-canonical module name "glesx.so"
                            (WW) fglrx(0): Option "IgnoreEDID" is not used
                            (WW) fglrx(0): Option "NoTV" is not used
                            (WW) fglrx(0): Option "DynamicClocks" is not used
                            (WW) fglrx(0): Option "VendorName" is not used
                            (WW) fglrx(0): Option "ModelName" is not used

                            I'm not sure what the 'end of block range' errors mean and I can't see the glesx.so warning being a blocker. Typically it looks like ATI is scrapping some options from the driver settings without telling us...

                            Any Suggestions hints, tips, tricks or moderate abuses of sanity?

                            (Gentoo, 2.6.20 r7, Nforce2, Amd64, LCD @ 1440x900 on agp or dvi, 25 years computer systems experience from mainframe to pc to unix to networks)

                            Comment


                            • #59
                              Can you post your xorg.conf? I don't know the last time I touched an AGP card, but in a recent driver there was a fix for AGP cards using a PCI-E chipset with a Rialto bridge.

                              I can look around and ask some people at AMD if need be. I've ran into a few other people recently that have the same problem (or close to the same problem) as yours.
                              Michael Larabel
                              http://www.michaellarabel.com/

                              Comment


                              • #60
                                Originally posted by Michael View Post
                                Can you post your xorg.conf? I don't know the last time I touched an AGP card, but in a recent driver there was a fix for AGP cards using a PCI-E chipset with a Rialto bridge.

                                I can look around and ask some people at AMD if need be. I've ran into a few other people recently that have the same problem (or close to the same problem) as yours.
                                I'm fairly sure this is pretty plain...


                                Code:
                                #xorg.conf
                                # File generated by xorgconfig.
                                #
                                # Copyright 2004 The X.Org Foundation
                                Section "Module"
                                
                                        Load            "glx"
                                        #Load           "GLcore
                                        Load            "dri"
                                #       Load            "dbe"     # Double buffer extension
                                        Load            "extmod"
                                        SubSection "extmod"
                                                Option       "omit xfree86-dga"   # don't initialise the DGA extension
                                                Option       "omit XVideo"
                                        EndSubSection
                                        Load            "fbdevhw"
                                        Load            "type1"
                                        Load            "freetype"
                                        Load            "record"
                                
                                EndSection
                                
                                
                                Section "Files"
                                
                                   FontPath     "/usr/share/fonts/misc/"
                                   FontPath     "/usr/share/fonts/Type1/"
                                   FontPath     "/usr/share/fonts/100dpi/"
                                   FontPath     "/usr/share/fonts/75dpi/"
                                EndSection
                                
                                Section "InputDevice"
                                   Identifier  "Keyboard1"
                                   Driver      "kbd"
                                   Option       "AutoRepeat" "500 30"
                                   Option       "XkbRules" "xorg"
                                   Option       "XkbModel" "pc105"
                                   Option       "XkbLayout" "us"
                                EndSection
                                
                                Section "InputDevice"
                                
                                   Identifier  "Mouse1"
                                   Driver      "mouse"
                                   Option       "Protocol" "Auto"   # Auto detect
                                   Option       "Device" "/dev/input/mice"
                                   Option       "ZAxisMapping" "4 5 6 7"
                                   Option       "Emulate3Buttons"
                                
                                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]"
                                        Option "IgnoreEDID"             "off"
                                        Option "NoTV"                   "yes"
                                
                                        Driver      "fglrx"
                                EndSection
                                
                                Section "Screen"
                                   Identifier "aticonfig-Screen[0]"
                                   Device     "aticonfig-Device[0]"
                                   Monitor    "aticonfig-Monitor[0]"
                                   DefaultDepth     24
                                   SubSection "Display"
                                            Depth     24
                                   EndSubSection
                                EndSection
                                
                                Section "ServerLayout"
                                   Identifier     "Simple Layout"
                                   Screen      0  "aticonfig-Screen[0]" 0 0
                                   InputDevice    "Mouse1" "CorePointer"
                                   InputDevice    "Keyboard1" "CoreKeyboard"
                                #   Option         "AIGLX" "false"
                                EndSection
                                
                                Section "Extensions"
                                      Option "Composite" "disable"
                                EndSection
                                
                                 Section "DRI"
                                    Mode 0666
                                 EndSection

                                I've also run this with the xorg.conf down to pretty barebones options -- -dri/glx/freetype and just about nothing else...

                                Comment

                                Working...
                                X