Announcement

Collapse
No announcement yet.

fglrx, 64bit linux and sb600 dma issue

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

  • #16
    energyman; most testing is done on the kernels which are delivered in release versions of the "supported distros"; RHEL, SuSE and Ubuntu. We do advance testing on pre-release versions of those distros but do not block driver release for a failure on a pre-release distro.

    Kano; yes, the secret is out

    Comment


    • #17
      Ok I would only like to ask this, and thank you for answering in advance:
      -Can you identify the problem in your lab? (I have tried on 2 similar systems and the result is the same - black screen, second system was AMD770+SB600, 6GB ram and HD4650; I have also tried on Intel P45+ICH10R, 8GB ram and HD4850, and no problem there)
      -Will there by any chance be a solution for this issue in future releases of fglrx?

      @energyman: I have tried only with 2.6.27 and 2.6.28 kernels.

      @Kano: LOL

      P.S. I'm just trying to help solve the problem and if its somewhere else, fine, but I would like to use fglrx on 64bit linux on my system without "sacrificing" 2GB of ram to the gods.
      Last edited by Kizo; 02-19-2009, 06:18 PM.

      Comment


      • #18
        My understanding is that the problems vary from mobo to mobo, but invariably they go away with an SBIOS update. In cases where we can't get a BIOS upgrade from the mobo vendor we may have to start working around the remaining problems in the driver on a case-by-case basis, but that is one of those "bottomless pit" kind of tasks.

        In cases where the mobo is all AMD we may have an easier time influencing the mobo vendor to fix the BIOS.

        Comment


        • #19
          Ok tnx for the answer.
          Until then i will have to rely on radeon or radeonhd then.
          I read radeon will have acceleration for r6xx/r7xx soon, so I guess there may be a workaround after all.

          Thanks everyone.

          Comment


          • #20
            well, there is a reason why I made sure that my mobo does not have a sb600 when I was looking around for a new one

            Comment


            • #21
              @bridgman: P.S. My mobo is ASRock ALiveXFire-eSATA2 (AMD 480X Crossfire + SB600, so its all AMDŽ ), just in case you could persuade ASRock to issue a fixed BIOS release. Tnx
              Last edited by Kizo; 02-19-2009, 07:20 PM.

              Comment


              • #22
                Originally posted by energyman View Post
                well, there is a reason why I made sure that my mobo does not have a sb600 when I was looking around for a new one
                Probably nothing to do with graphics drivers though, right ? The graphics drivers don't use any SB resources AFAIK.

                Comment


                • #23
                  @energyman: LOL ... Well it looked ok when I was bying it, + then I had only 2GB of ram and the world was a happier place to live in.

                  Comment


                  • #24
                    Well, I have the A770Crossfire from Asrock. 770 chipset + SB700. When I run into a usb bug (usb2+usb1.1 devices with only ehci driver loaded makes usb bus lock up), amd dev on lkml said that this bug should be fixed in bios - and provided a patch for ehci in case bios was not fixed (I was very satisfied, the amd guys reacted fast and their fix works very well for me!). So Asrock pumps out bios' even for their elderly mobos - but they don't incorporate fixes. ....

                    I learnt in the past that hardware problems caused by wired hardware bugs are a good thing to report on lkml. Of course stuff that is only reproducable with cs drivers will be shut down quickly. ...

                    Comment


                    • #25
                      Ugh...

                      Ugh.... I've been pulling my hair out for the better part of a week on this one. I too am running the SB600 SouthBridge on an MSI motherboard. Been chasing every combination of methods to install the latest / previous Catalyst drivers, only to end up with a backtrace at then of my Xorg logs or segfaults when running openGL stuff. I've got 4GB of memory in the box (AMD64), and running 2.6.27. After reading this post, I added mem=2048M to my boot options, and BAM... everything is working.

                      This is a set-top / mediacenter box, so the 4GB is way overkill, I just bought it because it was cheap.

                      I definitely appreciate you taking the time to report this issue in such detail. I would definitely count this in the "workaround" category, and not a solution, but I'm glad to be up and running again.

                      Comment


                      • #26
                        Originally posted by bridgman View Post
                        Probably nothing to do with graphics drivers though, right ? The graphics drivers don't use any SB resources AFAIK.
                        not ressources - but maybe the drivers set up a mem region and trample on the SB600's toes?

                        Comment


                        • #27
                          Originally posted by bjoneson View Post
                          Ugh.... I've been pulling my hair out for the better part of a week on this one. I too am running the SB600 SouthBridge on an MSI motherboard. Been chasing every combination of methods to install the latest / previous Catalyst drivers, only to end up with a backtrace at then of my Xorg logs or segfaults when running openGL stuff. I've got 4GB of memory in the box (AMD64), and running 2.6.27. After reading this post, I added mem=2048M to my boot options, and BAM... everything is working.

                          This is a set-top / mediacenter box, so the 4GB is way overkill, I just bought it because it was cheap.

                          I definitely appreciate you taking the time to report this issue in such detail. I would definitely count this in the "workaround" category, and not a solution, but I'm glad to be up and running again.
                          If you have MSI there is a good chance that you hava an option in the BIOS called "Memory Remapping" or "Memory Hole" or something like that (I don't have it on my ASRock). Try enabling that option with 4GB of ram, it might fix the issue.
                          Cheers.

                          P.S. @energyman: good to know that info about your usb problem, tnx

                          Comment


                          • #28
                            hey kizo bridgman and all who reading this thread i think my thread is also very near on your prob take a look maybe we find an answer

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

                            Comment

                            Working...
                            X