Announcement

Collapse
No announcement yet.

8.42.3 and FireGL

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

  • 8.42.3 and FireGL

    If anyone tries 8.42.3 on FireGL cards please post your results here...

  • #2
    8.43 adds official FireGL certification
    Michael Larabel
    http://www.michaellarabel.com/

    Comment


    • #3
      doesn't work, but might get it going with some pci-id-hacks.

      Comment


      • #4
        Aaaaaaaaaaaaaaaaaaaaaaaaaaggggghhhh!!!!

        Originally posted by Michael View Post
        8.43 adds official FireGL certification
        Sorry, sick and **&%! tired of waiting. How do I hack it?

        Comment


        • #5
          Originally posted by chrisr View Post
          Sorry, sick and **&%! tired of waiting. How do I hack it?
          I know this is not what you want to hear, but I know the wait for fglrx 8.43 will be worth it for FireGL along with other features coming.
          Michael Larabel
          http://www.michaellarabel.com/

          Comment


          • #6
            Easy for you to say...

            Originally posted by Michael View Post
            I know this is not what you want to hear, but I know the wait for fglrx 8.43 will be worth it for FireGL along with other features coming.
            You didn't spend a small fortune on a laptop you can't use for months on end! (Although I doubt that NVIDIA graphics would have been much better.)

            Now how do I hack it?

            Comment


            • #7
              Ask Kano, The Master.

              Comment


              • #8
                and success. I do get an AMD Unsupported Hardware in the bottom right corner tho'

                I followed the steps from http://www.phoronix.com/forums/showthread.php?t=5203

                but applied the patch manually.

                now let's test aiglx on this z61p

                Comment


                • #9
                  So close, and yet still so far...

                  Following these instructions and using a chip ID of "0x71D5" (Radeon X1700) for my FireGL V5250, I have managed to:

                  - enable DRI
                  - enable AIGLX
                  - run Compiz
                  - run celestia with OpenGL 2.0 support (although it interacts badly with Compiz)
                  - run glxgears with approx 2400 fps

                  This is all great! However, it fails at the final hurdle of running World of Warcraft, where it presents me with a completely black login screen. I am thinking that this must be a configuration issue, because everything else is working so well.

                  Obviously I have the "unsupported hardware" rectangle in the bottom RH corner of the screen, and these messages are written to my kernel log:

                  [fglrx] Maximum main memory to use for locked dma buffers: 1898 MBytes.
                  [fglrx] ASYNCIO init succeed!
                  [fglrx] PAT is enabled successfully!
                  [fglrx] module loaded - fglrx 8.42.3 [Oct 19 2007] on minor 0
                  BUG: sleeping function called from invalid context at include/asm/semaphore.h:99
                  in_atomic():1, irqs_disabled():0
                  [<f924b178>] __ke_down_struct_sem+0x14/0x2b [fglrx]
                  [<f924fd4f>] firegl_remove_all_drawables+0x3f/0x100 [fglrx]
                  [<f92527c9>] firegl_release_helper+0x6b9/0xa20 [fglrx]
                  [<f9255e7b>] firegl_takedown+0x6b/0xc50 [fglrx]
                  [<f925568f>] firegl_release+0x12f/0x190 [fglrx]
                  [<f9249c4c>] ip_firegl_release+0xf/0x12 [fglrx]
                  [<c0167302>] __fput+0xb5/0x15d
                  [<c0164f00>] filp_close+0x51/0x58
                  [<c010702b>] do_syscall_trace+0x13d/0x182
                  [<c0165e5b>] sys_close+0x67/0x9e
                  [<c0103ee2>] syscall_call+0x7/0xb
                  =======================
                  BUG: sleeping function called from invalid context at include/asm/semaphore.h:99
                  in_atomic():1, irqs_disabled():0
                  [<f924b178>] __ke_down_struct_sem+0x14/0x2b [fglrx]
                  [<f924fd4f>] firegl_remove_all_drawables+0x3f/0x100 [fglrx]
                  [<f92527c9>] firegl_release_helper+0x6b9/0xa20 [fglrx]
                  [<f9255e7b>] firegl_takedown+0x6b/0xc50 [fglrx]
                  [<f925568f>] firegl_release+0x12f/0x190 [fglrx]
                  [<f9249c4c>] ip_firegl_release+0xf/0x12 [fglrx]
                  [<c0167302>] __fput+0xb5/0x15d
                  [<c0164f00>] filp_close+0x51/0x58
                  [<c010702b>] do_syscall_trace+0x13d/0x182
                  [<c0165e5b>] sys_close+0x67/0x9e
                  [<c0103ee2>] syscall_call+0x7/0xb
                  [<c02a0000>] unix_shutdown+0x113/0x13b
                  =======================
                  [fglrx] Maximum main memory to use for locked dma buffers: 1898 MBytes.
                  [fglrx] Reserve Block - 0 offset = 0Xfffb000 length = 0X5000
                  [fglrx] Reserve Block - 1 offset = 0X0 length = 0X1000000
                  [fglrx] Reserve Block - 2 offset = 0Xffbb000 length = 0X40000

                  Those BUGs worry me...

                  Comment


                  • #10
                    Firegl v3200

                    Originally posted by nicweb View Post
                    If anyone tries 8.42.3 on FireGL cards please post your results here...
                    I tried the patch with the new drivers on my Firegl V3200, but it didn't work.... Anyone have any suggestions other than wait another month?

                    Comment


                    • #11
                      Trouble with libGL.so.1

                      I am finding that the dynamic linker is unwilling to find libGL.so.1.2 in the /usr/lib/fglrx directory, despite there correctly being an entry in /etc/ld.so.conf.d that lists the directory name. I was forced to add a symlink /usr/lib/libGL.so.1 to the /usr/lib/fglrx/libGL.so.1.2 shared object.

                      When I tried to run prelink on glxinfo, I received the following error:

                      prelink: /usr/bin/glxinfo: Cannot prelink against non-PIC shared library /usr/lib/libGL.so.1

                      Comment


                      • #12
                        Originally posted by chrisr View Post
                        I am finding that the dynamic linker is unwilling to find libGL.so.1.2 in the /usr/lib/fglrx directory, despite there correctly being an entry in /etc/ld.so.conf.d that lists the directory name. I was forced to add a symlink /usr/lib/libGL.so.1 to the /usr/lib/fglrx/libGL.so.1.2 shared object.

                        When I tried to run prelink on glxinfo, I received the following error:

                        prelink: /usr/bin/glxinfo: Cannot prelink against non-PIC shared library /usr/lib/libGL.so.1
                        I had that same problem, but gutsy had switched me over to vesa drivers..... this bulletproof-x stuff is kinda a pain, you have to run displayconfig-gtk as root and set the driver used back to the opensource ati drivers and maybe set up xorg.conf how it was before trying to move to fglrx and uninstalling fglrx.... OR, just revert back to fglrx

                        Comment


                        • #13
                          No, that's not it.

                          Originally posted by wlindner View Post
                          I had that same problem, but gutsy had switched me over to vesa drivers.....
                          If I don't link manually to libGL.so.1.2 then programs like glxinfo and glxgears completely refuse to run because they cannot locate the libGL.so.1 library. So there's no possibility of being secretly switched back to Mesa.

                          Comment


                          • #14
                            Hmm i can't seem to get direct rendering working for my V5200 on Arch Linux. Anyone have any success?

                            Comment


                            • #15
                              Did you remember to reload the fglrx kernel module?

                              Originally posted by mintcoffee View Post
                              Hmm i can't seem to get direct rendering working for my V5200 on Arch Linux. Anyone have any success?
                              My direct rendering didn't work straight away because I only upgraded the RPMs and forgot that I would need to unload the fglrx.ko from v8.40.4 as well.

                              Then I had to install a symlink in /usr/lib to /usr/lib/fglrx/libGL.so.1 by hand.

                              Which ChipID are you using in your xorg.conf file?

                              Comment

                              Working...
                              X