Announcement

Collapse
No announcement yet.

RV770 Support Added To RadeonHD Driver

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

  • #16
    Originally posted by bridgman View Post
    3D support is provided today by the proprietary drivers. From your earlier post in this thread it looks like your initial fglrx install wasn't working properly for some reason... my guess is that you had a "DRI support disabled" message in your log file and had no acceleration as a result.

    Let's get that fixed first. Can you pls post a log file from fglrx ?
    Thanks bridgman, here is the Xorg.0.log output, it seems to me that DRI is enabled though
    (this is only a small part showing some modules being loaded; if you wish, I can post the huge file also, or I can email to you). Thanks a lot.


    (II) LoadModule: "i2c"
    (II) Loading /usr/lib/xorg/modules/libi2c.so
    (II) Module i2c: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.2.0
    ABI class: X.Org Video Driver, version 1.0
    (II) LoadModule: "bitmap"
    (II) Reloading /usr/lib/xorg/modules/fonts/libbitmap.so
    (II) Loading font Bitmap
    (II) LoadModule: "ddc"
    (II) Loading /usr/lib/xorg/modules/libddc.so
    (II) Module ddc: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Video Driver, version 1.0
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading sub module "drm"
    (II) LoadModule: "drm"
    (II) Loading /usr/lib/xorg/modules/linux/libdrm.so
    (II) Module drm: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension SHAPE
    (II) Loading extension MIT-SUNDRY-NONSTANDARD
    (II) Loading extension BIG-REQUESTS
    (II) Loading extension SYNC
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XC-MISC
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-Misc
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension TOG-CUP
    (II) Loading extension Extended-Visual-Information
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "freetype"
    (II) Loading /usr/lib/xorg/modules/fonts/libfreetype.so
    (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
    compiled for 7.1.1, module version = 2.1.0
    Module class: X.Org Font Renderer
    ABI class: X.Org Font Renderer, version 0.5
    (II) Loading font FreeType
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    (II) Module glx: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3
    (==) AIGLX enabled
    (II) Loading extension GLX
    (II) LoadModule: "int10"
    (II) Loading /usr/lib/xorg/modules/libint10.so
    (II) Module int10: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Video Driver, version 1.0
    (II) LoadModule: "vbe"
    (II) Loading /usr/lib/xorg/modules/libvbe.so
    (II) Module vbe: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.1.0
    ABI class: X.Org Video Driver, version 1.0
    (II) LoadModule: "vesa"
    (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    (II) Module vesa: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.3.0
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 1.0
    (II) LoadModule: "kbd"
    (II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
    (II) Module kbd: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.1.0
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 0.6
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.1.1
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 0.6
    (II) VESA: driver for VESA chipsets: vesa
    (II) Primary Device is: PCI 01:05:0
    (--) Chipset vesa found


    UPDATE: Hey bridgman, I think you are pointing in the right direction: at the end of the Xorg.0.log file there is this info:


    (==) RandR enabled
    (II) Setting vga for screen 0.
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension XFree86-Bigfont
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing built-in extension XEVIE
    (EE) AIGLX: Screen 0 is not DRI capable
    (II) Loading local sub module "GLcore"
    (II) LoadModule: "GLcore"
    (II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so
    (II) Module GLcore: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3
    (II) GLX: Initialized MESA-PROXY GL provider for screen 0
    (**) Option "CoreKeyboard"
    (**) Generic Keyboard: Core Keyboard
    (**) Option "Protocol" "standard"
    (**) Generic Keyboard: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) Generic Keyboard: XkbRules: "xorg"
    (**) Option "XkbModel" "pc104"
    (**) Generic Keyboard: XkbModel: "pc104"
    (**) Option "XkbLayout" "us"
    (**) Generic Keyboard: XkbLayout: "us"
    (**) Option "CustomKeycodes" "off"
    (**) Generic Keyboard: CustomKeycodes disabled
    (**) Option "Protocol" "ImPS/2"
    (**) Configured Mouse: Device: "/dev/input/mice"
    (**) Configured Mouse: Protocol: "ImPS/2"
    (**) Option "CorePointer"
    (**) Configured Mouse: Core Pointer
    (**) Option "Device" "/dev/input/mice"
    (**) Option "Emulate3Buttons" "true"
    (**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
    (**) Configured Mouse: ZAxisMapping: buttons 4 and 5
    (**) Configured Mouse: Buttons: 9
    (II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
    (II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
    xkb_keycodes { include "xfree86+aliases(qwerty)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc105)+us" };
    xkb_geometry { include "pc(pc104)" };
    (II) Configured Mouse: ps2EnableDataReporting: succeeded
    Last edited by Maxei; 07-13-2008, 02:18 PM. Reason: more information

    Comment


    • #17
      DRI terminology is confusing -- there is the "DRI framework" (ddx driver, drm and 3d all working together), there is the "DRI extension" in X, there is "DRI support" in the ddx driver, and they all mean something different.

      In this case the logs are saying that the DRI extension is being loaded by the X server but that is only one small piece of what is needed to make acceleration work. In your case you are running the vesa driver instead of fglrx so nothing further is even trying to happen -- the vesa driver does not even initialize the rest of the dri framework and has no acceleration code anyways.

      You need to go back to running fglrx -- might be easiest to uninstall and re-install from scratch depending on how much tweaking you have done since the original installation.

      Also if you are running Hardy it would probably be best to just go into the restricted driver manager and enable the restricted driver -- that gets you 8.3 automatically and that's the version Ubuntu chose for Hardy.
      Last edited by bridgman; 07-13-2008, 02:45 PM.

      Comment


      • #18
        Originally posted by bridgman View Post
        DRI terminology is confusing -- there is the "DRI framework" (ddx driver, drm and 3d all working together), there is the "DRI extension" in X, there is "DRI support" in the ddx driver, and they all mean something different.

        In this case the logs are saying that the DRI extension is being loaded by the X server but that is only one small piece of what is needed to make acceleration work. In your case you are running the vesa driver instead of fglrx so nothing further is even trying to happen -- the vesa driver does not even initialize the rest of the dri framework and has no acceleration code anyways.

        You need to go back to running fglrx -- might be easiest to uninstall and re-install from scratch depending on how much tweaking you have done since the original installation.

        Hi bridgman, I have set back the fglrx driver and made a full reboot to get the xorg.0.log file: here it is. I notice some differences, as expected, but I don't understand fully what would be the meaning, please take a look. these are pieces that seemed to me important; please tell me your opinion, thanks a lot.


        (==) fglrx(0): NoAccel = NO

        (II) Loading sub module "xaa"
        (II) LoadModule: "xaa"
        (II) Loading /usr/lib/xorg/modules/libxaa.so
        (II) Module xaa: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.2.0
        ABI class: X.Org Video Driver, version 1.0
        (==) fglrx(0): NoDRI = NO
        (II) Loading sub module "fglrxdrm"
        (II) LoadModule: "fglrxdrm"
        (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
        (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
        compiled for 7.1.0, module version = 8.50.3
        .......
        ........
        II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
        (II) fglrx(0): detected X.org 7.1.1.0
        (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): ********************************************* *
        (II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x10000000
        (==) fglrx(0): Write-combining range (0xd0000000,0x10000000)
        (II) fglrx(0): FBMM initialized for area (0,0)-(1728,8191)
        (II) fglrx(0): FBMM auto alloc for area (0,0)-(1728,1050) (front color buffer - assumption)
        (II) fglrx(0): Largest offscreen area available: 1728 x 7141
        (==) fglrx(0): Backing store disabled
        (II) Loading extension FGLRXEXTENSION
        (II) Loading extension ATITVOUT
        (**) fglrx(0): DPMS enabled
        (WW) fglrx(0): Textured Video not supported without DRI enabled.
        (WW) fglrx(0): Video Overlay not supported on AVIVO based graphics cards. For XVideo support use Option "TexturedVideo".
        ...........
        ...........
        (==) RandR enabled
        (II) Initializing built-in extension MIT-SHM
        (II) Initializing built-in extension XInputExtension
        (II) Initializing built-in extension XTEST
        (II) Initializing built-in extension XKEYBOARD
        (II) Initializing built-in extension XC-APPGROUP
        (II) Initializing built-in extension SECURITY
        (II) Initializing built-in extension XINERAMA
        (II) Initializing built-in extension XFIXES
        (II) Initializing built-in extension XFree86-Bigfont
        (II) Initializing built-in extension RENDER
        (II) Initializing built-in extension RANDR
        (II) Initializing built-in extension COMPOSITE
        (II) Initializing built-in extension DAMAGE
        (II) Initializing built-in extension XEVIE
        (EE) AIGLX: Screen 0 is not DRI capable
        (II) Loading local sub module "GLcore"
        (II) LoadModule: "GLcore"
        (II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so
        (II) Module GLcore: vendor="X.Org Foundation"
        compiled for 7.1.1, module version = 1.0.0
        ABI class: X.Org Server Extension, version 0.

        Comment


        • #19
          OK, at least the problem is clear -- the kernel module is not initializing properly so you are not getting any acceleration. The following line is where things seem to go wrong :

          (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
          Not sure if that is an installation issue or system configuration issue but let's try some simple things first. Tried downloading your motherboard manual to check for BIOS settings but it's going very slowly so will ask you to look instead... any settings like "Remap memory" or "Enable memory over 4GB" or something ?

          Comment


          • #20
            must one also use those remap features of the bios to use ati cards under windows?

            Comment


            • #21
              Originally posted by bridgman View Post
              OK, at least the problem is clear -- the kernel module is not initializing properly so you are not getting any acceleration. The following line is where things seem to go wrong :



              Not sure if that is an installation issue or system configuration issue but let's try some simple things first. Tried downloading your motherboard manual to check for BIOS settings but it's going very slowly so will ask you to look instead... any settings like "Remap memory" or "Enable memory over 4GB" or something ?

              Sorry, couldn't find anything like that in the BIOS.

              Maybe there is something I did wrong in the xorg configuration? If I do :

              $ glxinfo |grep 'direct', I get:

              direct rendering: No
              OpenGL renderer string: Mesa GLX Indirect

              Comment


              • #22
                As long as you are running a stock x conf file there shouldn't be any problems there. Which distro are you running and how did you install the driver (ie use the installer directly or build a package for your distro and install that) ? Guessing you're running the 64-bit OS build ?

                Easy way to know if it's a memory / sbios issue would be to power down and remove 1 or 2 GB of RAM for a test. All the usual cautions about static protection, of course, (ie go get some tinfoil ).

                Comment


                • #23
                  Originally posted by bridgman View Post
                  As long as you are running a stock x conf file there shouldn't be any problems there. Which distro are you running and how did you install the driver (ie use the installer directly or build a package for your distro and install that) ? Guessing you're running the 64-bit OS build ?

                  Easy way to know if it's a memory / sbios issue would be to power down and remove 1 or 2 GB of RAM for a test. All the usual cautions about static protection, of course, (ie go get some tinfoil ).
                  Hey bridgman, thanks. I' running Debian Etch. I first built a package then installed.

                  Honestly I'm surprised that you'd think it's a RAM memory issue, AFAIK, nobody has reported problems using this mobo, which by the way can support 8 GB. So, to resume, I remove one slab and leave the other slab in place, reboot, then, am I expecting DRI to work? If is that easy I will try and post. Thanks

                  Comment


                  • #24
                    Just to be clear, I don't think it is a problem with your RAM, just the fact that the mobo sbios often remaps some of the 4GB (the part where you have to make a hole in the address space for things like IO and video card memory) up above 4GB, and there seem to be a lot of issues with how that remapping being done. I don't know exactly where the issues are and haven't had time to really drill down with the developers, but what I have seen is that updating the system BIOS to latest available seems to fix a lot of these problems.

                    Some mobo sbioses have an ability to disable remapping but your board either doesn't have that option or it is hidden (do you have hidden options behind alt-F1 by any chance ?).

                    Removing 2GB eliminates memory remapping issues as a potential problem -- if it works, we know to focus on memory remapping, and if it doesn't work, then we can focus on other things. Either way we learn something.

                    Redeeman, I don't know what the situation is with Windows drivers and >4GB but will ask. Linux has been keeping me plenty busy, and I only have 2GB in my home system
                    Last edited by bridgman; 07-14-2008, 11:25 PM.

                    Comment


                    • #25
                      Gigabyte uses Ctrl-F1 for extra settings.

                      Comment


                      • #26
                        Whoops... thanks !

                        Comment


                        • #27
                          Thanks for the BIOS tip, kano. Well I found the option you were talking about, bridgman: enable memory over 4GB. It was set as enable memory under 4GB. So I tested the option "enable memory over 4GB" and when X server started, I got a total crap in the screen. only grayish lines. Control+alt+backspace could not restart X server. So I had to use the power button to switch off the pc. I reverted to the option "memory under 4GB" and was ok. Then I removed one slab of memory, as you suggested and started. According to this, there is no DRI:

                          ~$ glxinfo |grep 'direct'
                          direct rendering: No
                          OpenGL renderer string: Mesa GLX Indirect

                          I am puzzled. When I type:

                          ~$ fglrxinfo
                          display: :0.0 screen: 0
                          OpenGL vendor string: Mesa project: www.mesa3d.org
                          OpenGL renderer string: Mesa GLX Indirect
                          OpenGL version string: 1.2 (1.5 Mesa 6.5.1)


                          It's strange that there is nothing like "ATI vendor" stuff.
                          Is this normal or maybe the fglrx driver loaded may not be the one from ATI but from a debian repository? How could I know this is the right ATI driver, and not any other?
                          The info I have for this fglrx-driver is:
                          version 8.501-1
                          Video driver for the ATI graphics accelerators
                          Video driver for the ATI Radeon and FireGL graphics accelerators.

                          This version of the ATI driver officially supports:
                          * RADEON X1300, X1600, X1800, X1900
                          * RADEON 8500, 9000, 9100, 9200, 9500, 9550, 9600, 9700, 9800
                          * RADEON X800, X700, X600, X300 series (AGP and PCI Express)
                          * MOBILITY RADEON 9000, 9200, 9600, 9800, X700
                          * MOBILITY RADEON 9000/9100 IGP Series
                          * FireGL 8700, 8800, E1, E2, X1, X2, X3, Z1, T2
                          * MOBILITY FireGL 9100, T2

                          Caution: This software driver provides only 2D support for the
                          ATI RADEON 9100 IGP and ATI RADEON 9100 PRO IGP.

                          This package provides 2D display drivers
                          and hardware accelerated OpenGL for X.Org 1:7.0.0.

                          So, there is nothing about HD3xxx chips or cards. What do you think? thanks.

                          Comment


                          • #28
                            For debian you can run:

                            http://kanotix.com/files/install-fglrx-debian.sh

                            My script currently installs 8-6, if you plan to use wine use:

                            -v 8-5

                            as option.

                            Comment


                            • #29
                              Solved!

                              Originally posted by Kano View Post
                              For debian you can run:

                              http://kanotix.com/files/install-fglrx-debian.sh

                              My script currently installs 8-6, if you plan to use wine use:

                              -v 8-5

                              as option.
                              Kano. Chapeau. Thanks a lot for your script. All went perfect! I stopped breathing for a few seconds when I saw the message: building package for ubuntu-edgy (since Iam using debian-etch, I dont know how it came to work, though)

                              :~$ fglrxinfo
                              display: :0.0 screen: 0
                              OpenGL vendor string: ATI Technologies Inc.
                              OpenGL renderer string: ATI Radeon HD 3200 Graphics
                              OpenGL version string: 2.1.7659 Release


                              Now I have direc rendering

                              ~$ glxinfo |grep 'direct'
                              direct rendering: Yes

                              I checked the CPU % use by xorg. I dragged a window making circles in the screen as fast as possible, and xorg used up to 70% of CPU. Not bad when I compare to 100% in the previous setting.

                              Thanks a lot again. I highly reccomend your script. great job kano.

                              PS> Oh, I just forgot to use the option you mentioned. Yes I want to run wine, so I guess now will have to re-install wine or something like that?
                              Last edited by Maxei; 07-16-2008, 11:05 PM.

                              Comment


                              • #30
                                You don't need to reinstall wine - you only have to change driver if you get corruptions with wine.

                                Comment

                                Working...
                                X