Announcement

Collapse
No announcement yet.

ATI R600/700 OSS 3D Driver Reaches Gears Milestone

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

  • I still can't get it running on my Karmic with kernel 2.6.30. Mainline kernels don't work (glxgears returns -22 error). So I decided to build latest drm modules by easy-drm-modules-installer script. Still no luck. I got a lot of messages like:

    [ 32.045787] radeon: disagrees about version of symbol drm_open
    [ 32.045790] radeon: Unknown symbol drm_open
    [ 32.045861] radeon: disagrees about version of symbol drm_fasync
    [ 32.045863] radeon: Unknown symbol drm_fasync
    [ 32.045933] radeon: disagrees about version of symbol drm_poll
    [ 32.045935] radeon: Unknown symbol drm_poll
    [ 32.046004] radeon: disagrees about version of symbol drm_get_resource_len
    [ 32.046007] radeon: Unknown symbol drm_get_resource_len
    [ 32.046096] radeon: disagrees about version of symbol drm_core_get_reg_ofs
    [ 32.046098] radeon: Unknown symbol drm_core_get_reg_ofs
    [ 32.046207] radeon: disagrees about version of symbol drm_irq_uninstall
    [ 32.046210] radeon: Unknown symbol drm_irq_uninstall
    [ 32.046286] radeon: disagrees about version of symbol drm_get_dev

    Comment


    • With changes made in last ~12 hours, hd3200 now gets 900+ fps in glxgears. eduke32 still goofed up. The changes, most likely in agd5f's drm 3D seemed to have helped hd3200 performance.

      Comment


      • Originally posted by FarJumper View Post
        I still can't get it running on my Karmic with kernel 2.6.30. Mainline kernels don't work (glxgears returns -22 error). So I decided to build latest drm modules by easy-drm-modules-installer script. Still no luck. I got a lot of messages like:

        [ 32.045787] radeon: disagrees about version of symbol drm_open
        [ 32.045790] radeon: Unknown symbol drm_open
        I'm not familiar with the script that you mention, but these messages mean that the headers used to compile the modules are from a kernel different from the one running.

        Comment


        • I would use my script

          Comment


          • Originally posted by lucky_ View Post
            Is it normal to have direct rendering YES even though I don't have 3D capable driver yet ?
            If I read through glxinfo's output I get a GL_RENDERER software rasterizer, how can I be sure to have 3D acceleration if glxinfo somehow fails to report correct things ?
            Is glxinfo still relevant ?
            Software rendering is direct too. Old guides saying to look if glxinfo says direct or no direct rendering are all outdated. Now you have to do glxinfo |grep OpenGL to see if renderer is Mesa DRI. (It is also good idea to check that correct mesa version is printed if you have problems.)

            Comment


            • Originally posted by suokko View Post
              Software rendering is direct too. Old guides saying to look if glxinfo says direct or no direct rendering are all outdated.
              and were wrong to begin with

              Comment


              • Ok thx, I was really suspicious about those guides, and GL RENDERER "software raserization" sounded really "not hardware acceleration for you".

                Comment


                • Originally posted by lucky_ View Post
                  Ok thx, I was really suspicious about those guides, and GL RENDERER "software raserization" sounded really "not hardware acceleration for you".
                  Yeah, software rasterizer does considerably advanced software rendering. Currently it's the only way with an ATi card to get OpenGL 2.1 with open drivers. (albeit running very very slowly)

                  Comment


                  • Am I correct in understanding that you can use the kernel part of the drm (the one from the latest 2.6.31) , and that all the work is now going into libdrm + mesa + radeon?

                    Or is the kernel drm component (the one that supports 600/700 3D calls) that I believe was merged in recently also in a state of flux?

                    Comment


                    • Originally posted by pingufunkybeat View Post
                      Am I correct in understanding that you can use the kernel part of the drm (the one from the latest 2.6.31) , and that all the work is now going into libdrm + mesa + radeon?

                      Or is the kernel drm component (the one that supports 600/700 3D calls) that I believe was merged in recently also in a state of flux?
                      The kernel DRM components haven't been merged into anything, you still have to use agd5f's repo for those. It is considered possible the stuff would be entering 2.6.32.

                      Comment

                      Working...
                      X