Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 39

Thread: RV770 Support Added To RadeonHD Driver

  1. #11
    Join Date
    Dec 2007
    Posts
    2,320

    Default

    Quote Originally Posted by Maxei View Post
    Hi, I'm using the vesa driver for the amd/ati hd3200 (780G) chipset (Gigabyte GA-MA78G-DS3H mobo). The problem I have is extremely heavy CPU use by Xorg, whenever any action is done (move a window, open an application, watch a dvd, etc). CPU use may go beyond 100%. I don't use Compiz or any 3D stuff. I mean, I am doing just usual plain 2D work. The problem is worst in KDE 3.5 compared to Gnome.
    Please can you explain me: is this due to lack of 2D hardware acceleration by the vesa driver?
    The vesa driver provides no acceleration at all. You are also limited to the mode list supported by the bios. It's basically a fallback driver.

  2. #12
    Join Date
    Jul 2008
    Posts
    21

    Default

    Quote Originally Posted by agd5f View Post
    The vesa driver provides no acceleration at all. You are also limited to the mode list supported by the bios. It's basically a fallback driver.


    Thanks. Do you mean that the BIOS from Gigabyte is limiting the function of the driver? Is there any settings that you recommend to modify in the bios?
    I also have another question: Do you know if the radeonhd driver support this chipset? Actually, I am asking because of mixed information I found. If you have updated information i will appreciate it. Thanks a lot again.
    Last edited by Maxei; 07-11-2008 at 09:33 PM.

  3. #13
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,385

    Default

    There are two different BIOSes on a typical PC - a "system BIOS" on the motherboard and a "video BIOS" either on the graphics card or (in the case of an integrated graphics chip) also on the motherboard. The system BIOS handles everything except graphics, while the video BIOS handles graphics.

    Your "BIOS settings" affect the system BIOS, but the VESA driver uses the video BIOS, so typically "BIOS settings" won't make a difference here.

    The radeonhd driver does support the 780 as long as you have a fairly recent version. Older versions did not yet have support added, and there was a post here recently mentioning that one of the outputs (display port) was not supported on any of the open drivers today; that may have been the source of your mixed information.

    We also do not have 3d acceleration available in any of the open source drivers today, but that should chance once we are able to release the remaining 3d engine programming information for the 6xx family (we released 3d engine info for 5xx in Feb 08).

  4. #14
    Join Date
    Jul 2008
    Posts
    21

    Default

    Quote Originally Posted by bridgman View Post
    There are two different BIOSes on a typical PC - a "system BIOS" on the motherboard and a "video BIOS" either on the graphics card or (in the case of an integrated graphics chip) also on the motherboard. The system BIOS handles everything except graphics, while the video BIOS handles graphics.

    Your "BIOS settings" affect the system BIOS, but the VESA driver uses the video BIOS, so typically "BIOS settings" won't make a difference here.

    The radeonhd driver does support the 780 as long as you have a fairly recent version. Older versions did not yet have support added, and there was a post here recently mentioning that one of the outputs (display port) was not supported on any of the open drivers today; that may have been the source of your mixed information.

    We also do not have 3d acceleration available in any of the open source drivers today, but that should chance once we are able to release the remaining 3d engine programming information for the 6xx family (we released 3d engine info for 5xx in Feb 08).
    Great, Thanks for that info pal, I earned something today
    I'm happy to know that the radeonhd driver supports the ati 780g chipset. I will give it a try. I don't care about 3D support at this point, but certainly I expect 3D support to be provided someday, either by the open source or proprietary drivers. Thank you.

  5. #15
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,385

    Default

    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 ?
    Last edited by bridgman; 07-12-2008 at 09:49 PM.

  6. #16
    Join Date
    Jul 2008
    Posts
    21

    Default

    Quote 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 at 02:18 PM. Reason: more information

  7. #17
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,385

    Default

    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 at 02:45 PM.

  8. #18
    Join Date
    Jul 2008
    Posts
    21

    Default

    Quote 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.

  9. #19
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,385

    Default

    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 ?

  10. #20
    Join Date
    Oct 2007
    Posts
    370

    Default

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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •