Announcement

Collapse
No announcement yet.

Fglrx 8.6 or 8.7 doesn't work with Intel AGP at all

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

  • Fglrx 8.6 or 8.7 doesn't work with Intel AGP at all

    Here I am, back once again struggling with this proprietary driver. About 6 months ago I tried to set up my video card (X700 256mb AGP) to work with the new driver that supported AIGLX.

    http://www.phoronix.com/forums/showthread.php?t=7228
    http://www.phoronix.com/forums/showthread.php?t=7799

    It was a suffering, I lost many hours of useless work because it just didn't worked. At that time I switched to the open source radeon driver but now I wanna try the proprietary driver again. More suffering. I've tried thousands of different configurations, tested in many scenarios and that's my situation:

    If my intel_agp module is loaded, without kdm started I can modprobe fglrx correctly without any error, but when I start kdm I just get a blank screen and computer is frozen. I blacklisted some modules:
    Code:
    blacklist agpgart
    blacklist intel_agp
    blacklist radeon
    blacklist drm
    and now fglrx loads, and kdm starts, but I get these errors in my Xorg.0.log, if I disable intel_agp looks like fglrx is not able to load a agp module(does it have one ? or do I really have to use intel_agp ? )

    Code:
    (EE) fglrx(0): [agp] unable to acquire AGP, error -1023
    (EE) fglrx(0): cannot init AGP
    ...
    (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized. 
    (WW) fglrx(0): ***********************************************
    (WW) fglrx(0): * DRI initialization failed!                  *
    (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
    (WW) fglrx(0): * 2D acceleraton available (MMIO)             *
    (WW) fglrx(0): * no 3D acceleration available                *
    (WW) fglrx(0): ********************************************* *
    (EE) fglrx(0): XMM failed to open CMMQS connection.
    No 3d acceleration and no nice features of the driver is enabled :-(

    Before anything I had made many tests:
    Different versions of the driver: from 8.5 to 8.7
    Different versions of the kernel: 2.6.24 and 2.6.25

    I even compiled another kernel (2.6.24) with these notes in mind:
    http://xoomer.alice.it/flavio.stanch...installer.html
    even though my image kernel's .config file was alread as it should be I recompiled, and no difference. I tried debian's fglrx packages and created packages with the installer from ati.amd.com, no difference.

    PLEASE somebody help me
    if you know a magic trick that convinces this driver to not freeze with intel_agp module, or know if fglrx has a generic agp module and how to use it/make it work I'd appreciate that.
    I already tried switching this option on and off and no difference:
    Code:
    Option      "UseInternalAGPGART" "no"
    In windoze my system works fine, I play games and everything else, my card is not damaged.

    My system:
    Saphire Radeon x700 AGP 8x 128 bits 256 MB DDR1

    * CRT 19" monitor: model AOC 9klr Spectrum with a 1280x1024 resolution.

    * Motherboard/chipset model: Intel D865PERL / intel i865P

    * Processor type : Pentium 4 2.6ghz HT 512kb cache Northwood core socket 478

    * Ammount of memmory: 2GB DDR400

    * Distro used: Debian Sid 32bit (unstable)

    * Kernel version: 2.6.24-etchnhalf-customized kernel

    * Xorg version: 1.4.2

    * catalyst 8.7

    I think my next step is to debug, if anyone can provide me information on how to proceed.

    Thanks in advance.

  • #2
    Well that option is useless for kernel 2.6. It was only working for kernel 2.4. Be sure you use the kernel agp driver.

    Comment


    • #3
      AFAIK we rely on external AGP support, ie we are not using any kind of built in AGP driver. Not sure if blacklisting drm only takes out the open source drm or also blocks the fglrx drm from running, but my first thought is not to blacklist anything but radeon and start debugging in that direction.

      Can you pastebin your log without the blacklisting ?

      Comment


      • #4
        logs

        Originally posted by bridgman View Post
        AFAIK we rely on external AGP support, ie we are not using any kind of built in AGP driver. Not sure if blacklisting drm only takes out the open source drm or also blocks the fglrx drm from running, but my first thought is not to blacklist anything but radeon and start debugging in that direction.

        Can you pastebin your log without the blacklisting ?
        Hi there Kano and Bridgman, thanks for the help.

        I blacklisted only radeon module and disabled automatic startup of kdm. I logged in the text console and them manually modprobe fglrx, no errors. When I started kdm blank screen and the computer hangs. I waited log time to check if it would load after some time but no luck.

        This is the /var/log/Xorg.0.log file
        http://pastebin.com/m5116b7cb

        This is the /var/log/syslog file:
        http://pastebin.com/m153c7be0

        this is /var/log/kdm file:
        http://pastebin.com/mbf6c283

        this is my /etc/X11/xorg.conf
        http://pastebin.com/m57032b1a

        After the tests I switched back to radeon open source drivers, that's why you'll see radeon messages in the syslog file

        Thanks in advance guys.

        Comment


        • #5
          same problem here with Intel 875 chipset

          I've been wrestling with the Radeon 3850 and Linux Catalyst 8.7 for nearly a week. Same type of problems, "cant acquire AGP" and "perpetual Mesa". Please see the following link for all the gory details:
          http://www.linuxquestions.org/questi...driver-660211/

          Unfortunately there does not appear to be an open source equivalent that supports the Radeon 3850 so it's either make this work or punt!

          At least I was able to get rid of the "cant acquire AGP" error by loading the drm module, but I'm still left without 2D acceleration. And loading drm may not be a fix anyway if it short circuits fglrx's drm.
          I'll keep plugging away, but sure could use some help. I'll keep everyone posted on any progress I make. Please do the same. Thanks.

          Pete

          P.S. Yes, the Radeon 3850 works flawlessly under XP! Argh!

          Comment


          • #6
            Maybe change AGP size in BIOS.

            Comment


            • #7
              Originally posted by Kano View Post
              Maybe change AGP size in BIOS.
              Already tried that. I decreased the aperture size to 128mb but no success.
              I'll try decreasing it to 64mb maybe it has an effect. When I get home and test that I'll post the result.

              Originally posted by nbi1 View Post
              I'll keep plugging away, but sure could use some help. I'll keep everyone posted on any progress I make. Please do the same. Thanks.
              I'll do that nbil. Actually I received an email from one of the ati devs to join the beta testers group, but I ended up not subscribing because at that time I was too much busy with college and work, but I regretted that... If I'd had done that at that time, maybe they would have fixed it. I'll try to subscribe now anyway. The more AGP users we have in the beta testers group the better it is for us.

              Comment


              • #8
                Originally posted by nbi1 View Post
                I've been wrestling with the Radeon 3850 and Linux Catalyst 8.7 for nearly a week. Same type of problems, "cant acquire AGP" and "perpetual Mesa". Please see the following link for all the gory details:
                http://www.linuxquestions.org/questi...driver-660211/

                Unfortunately there does not appear to be an open source equivalent that supports the Radeon 3850 so it's either make this work or punt!
                seems like radeonhd supports your card:
                http://wiki.x.org/wiki/radeonhd#head...e209b3d80e137d
                just install the xserver-xorg-video-radeonhd package and use radeonhd instead of fglrx or ati in xorg.conf

                which model is your card Sapphire ?

                Comment


                • #9
                  Originally posted by Kano View Post
                  Maybe change AGP size in BIOS.
                  Already tried all sizes ranging from 4-512 MB. No impact on video.

                  Comment


                  • #10
                    Originally posted by israel_miranda View Post
                    seems like radeonhd supports your card:
                    http://wiki.x.org/wiki/radeonhd#head...e209b3d80e137d
                    just install the xserver-xorg-video-radeonhd package and use radeonhd instead of fglrx or ati in xorg.conf

                    which model is your card Sapphire ?
                    No, HIS. The radeon notes I discovered previously didn't cover it. I'll give that link a try. Many thanks.

                    Comment


                    • #11
                      We don't have the 3d engine running in the open source drivers yet, so the only acceleration available is shadowfb, but everything else should be supported well.

                      Comment


                      • #12
                        Originally posted by bridgman View Post
                        We don't have the 3d engine running in the open source drivers yet, so the only acceleration available is shadowfb, but everything else should be supported well.
                        Who are you responding to and which open source drivers are you referring to? radeonhd ?

                        I'm getting very exasperated with the lack of basic functionality such as accelerated 2D X so phrases like "everything else should be supported well" have a tendency to rile me up, especially given that the unfruitful time spent on my Radeon 3850 so far exceeds my life's sum total of time spent on all other graphic cards under linux!

                        Your explanation for poor 2D that you gave in another thread misses the mark, most linux users like myself are not die-hard gamers. We want solid 2D for starters and as full time working people getting accelerated 2D working can't be a month long research project. I have no idea what ATI management was possibly thinking, but if ATI products can't reliably deliver the basics without muss and fuss then ATI is doomed in this market. In this context fglrx is a total disaster.

                        Do you know of any drivers (I don't care about the source) that can produce satisfactory 2D for X for a Radeon 3850 ?
                        Thanks.

                        Comment


                        • #13
                          Originally posted by nbi1 View Post
                          Unfortunately there does not appear to be an open source equivalent that supports the Radeon 3850 so it's either make this work or punt!
                          I think I was replying to you.

                          Originally posted by nbi1 View Post
                          Your explanation for poor 2D that you gave in another thread misses the mark, most linux users like myself are not die-hard gamers.
                          I'm drawing a blank here, can you give me a clue ?

                          Originally posted by nbi1 View Post
                          We want solid 2D for starters and as full time working people getting accelerated 2D working can't be a month long research project.
                          Modern GPUs do not have 2d engines, so everything is accelerated with the 3d engine -- which in turn means that until the 3d engine is running we can't implement 2d, 3d or video acceleration.

                          Originally posted by nbi1 View Post
                          especially given that the unfruitful time spent on my Radeon 3850 so far exceeds my life's sum total of time spent on all other graphic cards under linux!
                          You have been going down some interesting paths -- mixing open source drm with fglrx ddx driver is definitely a no-chance-of-success approach. I took a look at your bug report but didn't see the useful parts of the x log -- can you pls paste the full log there ?

                          Your conf file looks a bit funny -- wouldn't hurt to turn VideoOverlay off although I doubt that will make a difference to this problem.

                          Originally posted by nbi1 View Post
                          Do you know of any drivers (I don't care about the source) that can produce satisfactory 2D for X for a Radeon 3850 ?
                          Thanks.
                          Was there a problem with your original installation or did you just decide that the driver must not be working because specific 2d functions were slow ? EDIT - never mind, I found the answer in the second link.
                          Last edited by bridgman; 08-04-2008, 02:58 PM.

                          Comment


                          • #14
                            Originally posted by bridgman View Post
                            I guess I was replying to you. Depending on what you meant by "equivalent" the answer could either be reasonable or wrong. From your subsequent post I'm guessing "wrong"



                            I'm drawing a blank here, can you give me a clue ?



                            Modern GPUs do not have 2d engines, so everything is accelerated with the 3d engine -- which in turn means that until the 3d engine is running we can't implement 2d, 3d or video acceleration.
                            That's what I was referring to. This is well and fine from a technical perspective, but has implications for any vendor trying to address the needs of a market that is predominantly 2D! As someone else explained to you we'd rather have ATI put a label on the box saying "NOT SUITED FOR LINUX" than make misleading statements about a driver that doesn't even deliver the basics. I've read all the official AMD/ATI docs and at no time did I get the impression that I wouldn't get working 2D at a minimum. If we can't get that, then what use is the driver?


                            Originally posted by bridgman View Post
                            You have been going down some interesting paths -- mixing open source drm with fglrx ddx driver is definitely a no-chance-of-success approach. I took a look at your bug report but didn't see the useful parts of the x log -- can you pls paste the full log there ?

                            Your conf file looks a bit funny -- wouldn't hurt to turn VideoOverlay off although I doubt that will make a difference to this problem.



                            Was there a problem with your original installation or did you just decide that the driver must not be working because specific 2d functions were slow ? EDIT - never mind, I found the answer in the second link.
                            Originally I followed the 8.7 Catalyst instructions to the letter. That gave me crap 2D so I turned to the backport which doesn't seem to support the 3850. That led me to decide I better try 8.7 again. But as you can see I've experienced many problems including the two all time leaders "perpetual mesa" and "can't acquire AGP". Given these two have plagued fglrx for a long time can't ATI dedicate the resources to lay these to rest?

                            Regarding drm you only have to google to find out why I'm at where I'm at. This has been kicked around on several forums without a definitive answer. The safest approach seems to be building the drm module to make it available as needed. If you can definitively tell me drm should not be built for fglrx use then I'd be happy to omit it. And next you can tell me how to eliminate the resulting "cant acquire AGP".

                            Are you telling me that accelerated 2D for X is an achievable goal in 8.7 or do I need to pursue another avenue?

                            In general I'm very amenable to working with vendors to resolve linux issues, but I've got to get the sense there's a good faith effort being put forth by the vendor. So far in the case of ATI and Catalyst 8.7 for linux I'm feeling horn swaggled.

                            Comment


                            • #15
                              Originally posted by nbi1 View Post
                              That's what I was referring to. This is well and fine from a technical perspective, but has implications for any vendor trying to address the needs of a market that is predominantly 2D! As someone else explained to you we'd rather have ATI put a label on the box saying "NOT SUITED FOR LINUX" than make misleading statements about a driver that doesn't even deliver the basics. I've read all the official AMD/ATI docs and at no time did I get the impression that I wouldn't get working 2D at a minimum. If we can't get that, then what use is the driver?
                              I don't really understand you here. Accelerated 2D and 3D was available from roughly the time the card launched. As near as I can figure from your posts something went wrong with your installation so you didn't get acceleration. In your case I think you also picked up some bad advice from the internet and wasted a bunch of time as a result, which is unfortunate but does sometimes happen.



                              Originally posted by nbi1 View Post
                              Originally I followed the 8.7 Catalyst instructions to the letter. That gave me crap 2D so I turned to the backport which doesn't seem to support the 3850. That led me to decide I better try 8.7 again. But as you can see I've experienced many problems including the two all time leaders "perpetual mesa" and "can't acquire AGP". Given these two have plagued fglrx for a long time can't ATI dedicate the resources to lay these to rest?
                              Since "perpetual mesa" means "something went wrong with the installation on my particular combination of hardware, distro, updates and drivers" I doubt we will ever get rid of it completely, but it is happening a lot less these days now that the installer has been opened up to allow independent maintenance of distro-specific packaging scripts.

                              Doing a Google search for "can't acquire AGP" gave me only 3 hits, one of them from your post. The other two seem related to a motherboard BIOS bug which allowed the AGP aperture to be allocated above 2^^32 which a lot of hardware apparently can't handle.

                              Originally posted by nbi1 View Post
                              Regarding drm you only have to google to find out why I'm at where I'm at. This has been kicked around on several forums without a definitive answer. The safest approach seems to be building the drm module to make it available as needed. If you can definitively tell me drm should not be built for fglrx use then I'd be happy to omit it. And next you can tell me how to eliminate the resulting "cant acquire AGP".
                              I can definitively tell you drm should not be built for fglrx. re: getting rid of the error message, please post your full x log to the bugzilla ticket so we can all see what is going on.

                              Originally posted by nbi1 View Post
                              Are you telling me that accelerated 2D for X is an achievable goal in 8.7 or do I need to pursue another avenue?
                              Yes.

                              Originally posted by nbi1 View Post
                              In general I'm very amenable to working with vendors to resolve linux issues, but I've got to get the sense there's a good faith effort being put forth by the vendor. So far in the case of ATI and Catalyst 8.7 for linux I'm feeling horn swaggled.
                              Why do you say that ?
                              Last edited by bridgman; 08-04-2008, 04:11 PM.

                              Comment

                              Working...
                              X