RV770 Support Added To RadeonHD Driver

[phoronix]

Phoronix: RV770 Support Added To RadeonHD Driver

The Novell developers behind the xf86-video-radeonhd driver have yet to receive their hardware samples from AMD for the Radeon HD 4850 or Radeon HD 4870, but there is already AtomBIOS-based support for these next-generation graphics processors. This open-source driver now has basic mode-setting support, but the 2D and 3D work is still to come.

http://www.phoronix.com/vr.php?view=12583

[Lothar]

Does this new driver also include support for the Radeon HD 3200 IGP?

[bridgman]

Radeonhd has had support for the HD3200 for a while now, although I don't remember if support was added before the last release. You might need more recent code from git.

Current support is display/modesetting + shadowfb acceleration only, ie no 3d, but 3d is in the works.

[chithanh]

I thought the modesetting support for HD3200 was still incomplete (no DisplayPort support eg. for ASRock A780FullDisplayPort). Has this changed in current git?

[bridgman]

Ahh yes. Display port has not been a priority on any of the chips that support it (HD32xx, HD34xx, HD36xx, HD48xx) since there are very few displays out there, but it is on the list for implementation and having full atombios support will be a big help to getting display port running.

So yes, this will help with display port but does not add support today.

[chithanh]

Good to hear that it is being worked on.

Using DisplayPort seems to be the only way to connect two digital displays to 780G chipsets, as DVI+HDMI combination is not supported (at least by the boards on the market today).

[bridgman]

Interesting... and odd. It's almost impossible to buy a discrete care that does *not* have 2 DVI ports, wonder why mobo's are so different ? Maybe the only way to get the 2nd digital output is to give up 4 PCIE lanes, will check...

EDIT - according to their specs the Gigabyte GA-MA78GM and Asus M3A78-EMH each have 1 DVI + 1 HDMI port. Always hard to be sure without actually holding one in your hands and all the pics on the websites seem to be "lifestyle" shots showing how exciting your life will be if you buy this motherboard :confused:

http://www.compusa.com/include/AddCartfromGallery.asp?EdpNo=3739365&Sku=A455-2400&imgcart=1&imgcounter=5

[chithanh]

According to its specifications, the ASUS M3A78-EMH only supports this:
Dual VGA output support:
RGB & DVI/HDMI And the user manual for the Gigabyte GA-MA78GM-S2H says

Dual
Display
Combination Supported or Not
DVI-D + D-Sub Yes
DVI-D + HDMI No
HDMI + D-Sub Yes
It looks to me like this is either a hardware limitation of the 780G, or the manufacturers were too cheap to route DVI and HDMI outputs to different ports on the chipset.

[bridgman]

Yep... sounds like there's just a single set of dedicated digital outputs and you have to steal PCIE lines for the second one. That said, IIRC there's a different output block used for the muxed output and I'm pretty sure we have seen it used on at least one 780 mobo. We have definitely seen it used on 690s.

[Maxei]

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? I installed the newest proprietary ATI driver (v 8.6) and the Xorg CPU use was even worst than vesa, so I reverted to vesa again. However, vesa driver does not allow me to get the full screen resolution. Am I doing something wrong or the drivers are still unfinished even at 2D? Is there any driver that fully support this chipset?

Thanks a lot for your help.


Gigabyte GA-MA78G-DS3H mobo connected to a digital Acer 22"
AMD AThlon X2 64 5000+
4G DDR2 800MHZ

[agd5f]

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.

[Maxei]

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.

[bridgman]

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

[Maxei]

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.

[bridgman]

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 ?

[Maxei]

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

[bridgman]

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.

[Maxei]

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.

[bridgman]

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 ?

[Redeeman]

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

[Maxei]

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

[bridgman]

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 ;)).

[Maxei]

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

[bridgman]

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 ;)

[Kano]

Gigabyte uses Ctrl-F1 for extra settings.

[bridgman]

Whoops... thanks !

[Maxei]

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.

[Kano]

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.

[Maxei]

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?

[Kano]

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

[Maxei]

I have reported before that in my system, the CPU was used intensively by xorg. With the ATI proprietary fglrx driver, it helped to reduce the slowliness in the applications, and eliminated dvd jerky playback in gnome.

But in KDE is a different story. Playing a DVD with Kaffeine gives black rectangles flickering in the screen. Clicking in the menus of Kaffeine cause them to flicker too. If Kaffeine is reduced to a small window and another application cover is full screen, then I can see the black window of Kaffeine overlaying the application.

Top shows also that xorg, both in Gnome and KDE, uses the CPU at very high %, although this only for a short moment. But this is not normal. My previous system had a 1GHz CPU with an old Radeon 9250 card and never saw that kind of problems.

I still believe that the ATI propietary driver still does not provide perfect support for this integrated gpu, HD-3200

Or can someone with a similar system tell me if my xorg.conf should be modified? Here is my present configuration. Thanks for your suggestions.

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Default Screen" 0 0
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "Files"

# path to defoma fonts
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
# Load "extmod"
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
EndSection

Section "Monitor"
Identifier "AL2223W"
Option "DPMS"
EndSection

Section "Device"

Identifier "ATI Technologies Inc ATI Default Card"
Driver "fglrx"
Option "UseInternalAGPGART" "yes"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "MonitorLayout" "AUTO, AUTO"
Option "UseEvents" "boolean"
# Option "NoAccel" "false"
# Option "DRI" "true"
# Option "RenderAccel" "true"
# Option "XAANoOffscreenPixmaps" "true"
# Option "AccelMethod" "EXA"
# Option "FBTexPercent" "50"
BusID "PCI:1:5:0"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc ATI Default Card"
Monitor "AL2223W"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1680x1050" "1600x1200" "1440x1440" "1280x1024" "1280x960" "1280x800" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1680x1050" "1600x1200" "1440x1440" "1280x1024" "1280x960" "1280x800" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1680x1050" "1600x1200" "1440x1440" "1280x1024" "1280x960" "1280x800" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1680x1050" "1600x1200" "1440x1440" "1280x1024" "1280x960" "1280x800" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1680x1050" "1600x1200" "1440x1440" "1280x1024" "1280x960" "1280x800" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1680x1050" "1600x1200" "1440x1440" "1280x1024" "1280x960" "1280x800" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection

Section "Extensions"
Option "Composite" "1"
EndSection

[bridgman]

The config options are definitely wrong for the graphics block -- starting with the 5xx generation we completely changed the display block and no longer use the overlay for normal video playback. The older chips had dedicated video processing hardware in the overlay block, but newer chips use shaders to perform the back end video processing. This will result in higher CPU utiliization but also makes it possible to run the video through a compositor (although we're not doing that yet).

I would comment out all of the Option lines in Device, but at minimum you want VideoOverlay off and TexturedVideo on. That said, the driver gets most of its settings from amdpcsdb, and those contents are set & viewed using CCCLE or the aticonfig utility.

Are the settings in your xorg.conf left over from the earlier card ?

Anyways, first thing IMO would be to comment out all the Display option lines (leave Identifier and Driver), then take a look in amdpcsdb using aticonf. Try starting with aticonfig --help and that will give you the rest of the info you need.

[Kano]

No, these options are written by my script. Because that was the way to enable Xv with older releases. I can not check which series a card is and then enable or disable those options. It was definitely not my fault that the older fglrx drivers _required_ those options.

[bridgman]

Makes sense. It may be that the aticonfig --initial (or whatever) command sets up enough stuff in amdpcsdb so that the modern drivers ignore the problematic entries anyways, not sure.

If the options are just required for older drivers then I guess it might be feasible for your scripts to switch on driver version so you don't have to actually probe the card ?

[Kano]

Usually those options are not critical, some of em are just ignored. The TexturedVideo option is one of the options which is absolutely nonsence anyway, because the driver has to switch that itself. I basically write those:

Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"

That means that the driver should use Xv. It does not say anything about what _how_ the driver should provide Xv, it is still up to the driver. If the user has to specify that if he wants to see a video correctly then fglrx is faulty. The aticonfig tools is one of the worst things ever created. My perl/sed replacements work much better. Also I can not see any logic in aticonfig, it writes only a template with initial - and a very bad one when the xorg.conf looked a bit more complex before. In some cases the tool just segfaults anyway - so no way to rely on it.

[bridgman]

Yeah, the problem is that the options are too low-level. The "VideoOverlay" option doesn't mean "enable Xv", it means "have Xv use the dedicated video processor built into the overlay block of older ATI parts". TexturedVideo means "have Xv use shaders".

I think we do need options more like the ones you are talking about, eg "enable Xv" but those are not the options we have today.

[Kano]

Why not use the new way directly when the old is not possible?

[Maxei]

Thank you bridgman and kano for posting comments. Although this goes a bit far from my limited knowledge, I do agree that kano's script modified the Device section as is shown, and it uncommented the options that I was testing with the previous (bad) installed fglrx.

So, if I well understood, this integrated GPU is relatively new, and hence the options that kano suggested may not apply to it?

Alright. I'll have to play around with the options to find out if something can improve (or worsen!) the driver's function. I will try that, begining by uncomenting all, except what brigdmnan suggests, understanding that the option "enable Xv" does not exist yet.
I will post latter on. Thank you.

[Maxei]

I have tested the xorg options, by commenting out all the options, and by enabling them also. To me, there are no noticeable differences. It's like the fglrx driver just ignores whatever option is in the device section.:confused:

Anyway, I solved the flickering of the kaffeine window in KDE by disabling the transparency and shadow effects in KDE control center.

Xorg CPU use is very high at moments and is the same whether I coment out all options or leave them enabled.

One more thing. When I logout from KDE using the logout button, I lose the X server. I get a black screen, and CTRL+ALT+BACKSPACE cannot rescue it, so I have to switch the power button off then on to get back. But if I restart the xserver with CTRL+ALT+BACKSPACE (instead of using that logout button) I can get back to the gdm. strange, but maybe this has nothing to do with the driver.

I hope that ATI developers take a closer look at this driver, maybe some more fixing is needed, especially to provide 3D support. Thanks