v.slow Xv performance in fglrx 8.8 - help needed

[warped]

Hi *

Forgive me maybe lame question but I'm new in ATI (till now using almost exclusively Nv).
I just added propietary drived to my diskless Myth frontend based on minimyth.
My hw is ASUS M3A78 Pro (AMD780=HD3200 based). Kernel is 2.6.25.10. Xorg is 7.3
I have following issues:
-for SD video I have 5-10fps
-OpenGL rendered UI takes AGES.

In Myth logs it looks like Xv isn't supported or doesn't provide Xv blitter.

2008-08-31 22:11:47.758 Opening ALSA audio device 'default'.
Xlib:  extension "XVideo" missing on display ":0.0".
2008-08-31 22:11:55.920 VideoOutputXv Error: XVideo output requested, but is not supported by display.
Xlib:  extension "XVideo" missing on display ":0.0".
2008-08-31 22:11:55.959 VideoOutputXv Error: XVideo output requested, but is not supported by display.
2008-08-31 22:11:55.960 VideoOutputXv: Desired video renderer 'xv-blit' not available.
                        codec 'MPEG2' makes 'opengl,xshm,xlib,' available, using 'opengl' instead.
greedyhdeint: size changed from 0 x 0 -> 720 x 576
2008-08-31 22:11:56.575 OSD Theme Dimensions W: 640 H: 480
Xlib:  extension "XFree86-VidModeExtension" missing on display ":0.0".
2008-08-31 22:11:58.487 VideoOutputXv Error: GetRefreshRate(): X11 ModeLine query failed
2008-08-31 22:11:58.488 TV: Changing from None to WatchingPreRecorded
2008-08-31 22:11:58.489 New DB connection, total: 3
greedyhdeint: size changed from 0 x 0 -> 720 x 576
2008-08-31 22:11:58.492 Realtime priority would require SUID as root.
Xlib:  extension "XFree86-VidModeExtension" missing on display ":0.0".
2008-08-31 22:11:58.494 VideoOutputXv Error: GetRefreshRate(): X11 ModeLine query failed
2008-08-31 22:11:58.494 Video timing method: USleep with busy wait
2008-08-31 22:11:58.523 Connected to database 'mythconverg' at host: 192.168.1.254

Interesting message is in kernel log: "GART Table is not in FRAME_BUFFER range"

Aug 31 22:08:59 (none) user.warn kernel: fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
Aug 31 22:08:59 (none) user.info kernel: [fglrx] Maximum main memory to use for locked dma buffers: 867 MBytes.
Aug 31 22:08:59 (none) user.info kernel: [fglrx]   vendor: 1002 device: 9610 count: 1
Aug 31 22:08:59 (none) user.info kernel: [fglrx] ioport: bar 1, base 0xd000, size: 0x100
Aug 31 22:08:59 (none) user.info kernel: [fglrx] PAT is enabled successfully!
Aug 31 22:08:59 (none) user.info kernel: [fglrx] module loaded - fglrx 8.52.3 [Aug  1 2008] with 1 minors
Aug 31 22:09:42 (none) user.info kernel: [fglrx] GART Table is not in FRAME_BUFFER range 
Aug 31 22:09:42 (none) user.info kernel: [fglrx] Reserved FB block: Shared offset:0, size:1000000 
Aug 31 22:09:42 (none) user.info kernel: [fglrx] Reserved FB block: Unshared offset:3ffc000, size:4000 
Aug 31 22:10:41 (none) user.info kernel: [fglrx] GART Table is not in FRAME_BUFFER range 
Aug 31 22:10:41 (none) user.info kernel: [fglrx] Reserved FB block: Shared offset:0, size:1000000 
Aug 31 22:10:41 (none) user.info kernel: [fglrx] Reserved FB block: Unshared offset:3ffc000, size:4000 
Aug 31 22:11:22 (none) user.info kernel: [fglrx] GART Table is not in FRAME_BUFFER range 
Aug 31 22:11:22 (none) user.info kernel: [fglrx] Reserved FB block: Shared offset:0, size:1000000 
Aug 31 22:11:22 (none) user.info kernel: [fglrx] Reserved FB block: Unshared offset:3ffc000, size:4000

My Qs are:
-do You believe issue with frame_buffer might be source of such slow performance ?

-is there any magic option in Xorg.conf to make fglrx at least with the same speed magnitude for video like Nv...or fglrx is simply slow and thats it ?

Integration of fglrx was done by reverse engineering ATI install scripts- so taking into account that driver is working - there shouldn't be any mistakes. All files are binary - only kernel DRM module was compiled (some kernel config tweaking was needed).
Maybe I should twek kernel config more ?. IF so - can somebody hint me in which config area I should look deeper ?


BTW: I tried radeohd - but at this moment Xv isn't supported and it looks like it will take some time as for R7xx first 3D accel should be implemented (as 2D accel is based on 3D).

milion thx in advance for help !

[forum1793]

fglrx is MUCH faster than vesa, radeon, or radeonhd. The issue is the catalyst drivers are still being debugged/developed for linux, as near as I can tell.

If you do lsmod, does fglrx show up. If not this needs to be fixed. If it doesn't show up, the fglrx_drv located in /usr/lib/xorg... is loaded and is something comparable to vesa. This works OK but is slower. When X is running, open a term, do lsmod and see if fglrx is loaded. The catalyst version matters. For my hardware, catalyst 8.5 is last that works. 8.6-8.8 goof up myth (although I've read about a work around where you alter the monitor or something by one pixel, I haven't tried).

In myth in video settings my default video player is mplayer -vo x11. (This basically is xshm). I've tried others (directly with mplayer) and they work to varying degrees.

In TV playback, I tell it if rez>0 to use XvMc. Although I will admit I don't understand this part very well. Xv and Xvmc didn't use to work for me. They do now maybe because of change to xorg.conf regarding texture and overlay (see below).

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection

Section "Device"
	Identifier  "aticonfig-Device[0]"
	Driver      "fglrx"
        Option "VideoOverlay" "off"
        Option "TexturedVideo" "on"
        Option "OpenGLOverlay" "off"
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]"
	Device     "aticonfig-Device[0]"
	Monitor    "aticonfig-Monitor[0]"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

[bridgman]

BTW: I tried radeohd - but at this moment Xv isn't supported and it looks like it will take some time as for R7xx first 3D accel should be implemented (as 2D accel is based on 3D).

FYI we expect that EXA and Textured Video acceleration will show up before 3D acceleration. Both require the 3D engine but the work required to add 6xx/7xx support to EXA and Textured Video currently seems to be quite a bit less than adding 6xx/7xx support to Mesa.

[warped]

If you do lsmod, does fglrx show up. If not this needs to be fixed. If it doesn't show up, the fglrx_drv located in /usr/lib/xorg... is loaded and is something comparable to vesa. This works OK but is slower.

Thx for trying help.
drm module is loaded. lsmod reports OK.
version of drm module is 8.52.3.
I changed xorg.conf to exacly Yours - still v.slow.

Here is my xorg.log

        (++) from command line, (!!) notice, (II) informational,
(II) All system resource ranges:
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
(II) Primary Device is: PCI 01:05:0
(II) ATI Proprietary Linux Driver Version Identifier:8.52.3
(II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.522                    
(II) ATI Proprietary Linux Driver Build Date: Aug  1 2008 00:30:27
(II) AMD Video driver is running on a device belonging to a group targeted for this release
(II) AMD Video driver is signed
(II) resource ranges after xf86ClaimFixedResources() call:
(II) fglrx(0): pEnt->device->identifier=0x9c57bd8
(II) resource ranges after probing:
(II) Setting vga for screen 0.
(II) fglrx(0): === [atiddxPreInit] === begin
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
(II) fglrx(0): PCI bus 1 card 5 func 0
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(II) fglrx(0): Loading PCS database from /etc/ati/amdpcsdb
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(==) fglrx(0): Gamma Correction for II is 0x06419064
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VbeVersion is 768, OemStringPtr is 0xc00001c8,
(II) fglrx(0): VESA VBE Version 3.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
(II) fglrx(0): VESA VBE OEM Software Rev: 10.80
(II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc. 
(II) fglrx(0): VESA VBE OEM Product: RS780
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
(II) Loading sub module "dri"
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
(II) Loading extension XFree86-DRI
(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."
(II) fglrx(0): Using adapter: 1:5.0.
(II) fglrx(0): [FB] Find the MC FB aperturs range(MCFBBase = 0xc0000000, MCFBSize = 0x4000000)
(II) fglrx(0): PCI card detected
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module "ddc" already built-in
(II) fglrx(0): ***Display: ConnectedDisplayTypes=0x00000001, disabled=0x00000000
(II) fglrx(0): Connected Display1: CRT on primary DAC [crt1]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: IVM  Model: 5395  Serial#: 201
(II) fglrx(0): Year: 2006  Week: 49
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Analog Display Input,  Input Voltage Level: 0.700/0.300 V
(II) fglrx(0): Sync:  Separate  Composite  SyncOnGreen
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 41  vert.: 31
(II) fglrx(0): Gamma: 2.20
(II) fglrx(0): DPMS capabilities: Off; RGB/Color Display
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.640 redY: 0.329   greenX: 0.300 greenY: 0.600
(II) fglrx(0): blueX: 0.149 blueY: 0.060   whiteX: 0.312 whiteY: 0.328
(II) fglrx(0): Supported VESA Video Modes:
((II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): clock: 162.0 MHz   Image Size:  408 x 306 mm
(II) fglrx(0): h_active: 1600  h_sync: 1664  h_sync_end 1856 h_blank_end 2160 h_border: 0
(II) fglrx(0): v_active: 1200  v_sync: 1201  v_sync_end 1204 v_blanking: 1250 v_border: 0
(II) fglrx(0): Serial No: 05806S6C00201
(II) fglrx(0): Ranges: V min: 56  V max: 86 Hz, H min: 24  H max: 83 kHz, PixClock max 170 MHz
(II) fglrx(0): Monitor name: PLE511
(II) fglrx(0): EDID (in hex):
(II) fglrx(0):  00ffffffffffff0026cd9553c9000000
(II) fglrx(0):  311001030e291f782ade50a3544c9926
(II) fglrx(0):  0f5054bfef8031594559614761598140
(II) fglrx(0):  8180a9400101483f403062b0324040c0
(II) fglrx(0):  130098321100001e000000ff00303538
(II) fglrx(0):  30365336433030323031000000fd0038
(II) fglrx(0):  56185311000a202020202020000000fc
(II) fglrx(0):  00504c453531310a2020202020200086
(II) fglrx(0): End of Display1 EDID data --------------------
(II) fglrx(0): Primary Controller - CRT on primary DAC
(II) fglrx(0): Internal Desktop Setting: 0x00000001
(II) fglrx(0): Total of 41 modes found for primary display.
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) fglrx(0): [pcie] 261120 kB allocated
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 7.1.0.90
(II) Loading sub module "glx"
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
(II) Loading extension GLX
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
(II) [drm] DRM interface version 1.0
(II) [drm] DRM open master succeeded.
(II) fglrx(0): [drm] Using the DRM lock SAREA also for drawables.
(II) fglrx(0): [drm] framebuffer handle = 0x1a000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): X context handle = 0x1
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0):     Name: fglrx
(II) fglrx(0):     Version: 8.52.3
(II) fglrx(0):     Date: Aug  1 2008
(II) fglrx(0):     Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0):     Build-Kernel UTS_RELEASE:        2.6.25.10
(II) fglrx(0):     Build-Kernel MODVERSIONS:        no
(II) fglrx(0):     Build-Kernel __SMP__:            no
(II) fglrx(0):     Build-Kernel PAGE_SIZE:          0x1000
(II) fglrx(0): [drm] register handle = 0x0001c000
(II) fglrx(0): Interrupt handler installed at IRQ 18.
(II) fglrx(0): Exposed events to the /proc interface
(II) fglrx(0): DRI initialization successfull!
(II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x01004000
(II) fglrx(0): FBMM initialized for area (0,0)-(1600,2624)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1600,1200) (front color buffer - assumption)
(II) fglrx(0): Largest offscreen area available: 1600 x 1424
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(II) LoadModule: "glesx"
(II) Loading /usr/lib/xorg/modules//glesx.so
(II) Module glesx: vendor="X.Org Foundation"
(II) Loading extension GLESX
(II) fglrx(0): GLESX enableFlags = 26
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
(II) fglrx(0): GLESX is enabled
(II) LoadModule: "amdxmm"
(II) Loading /usr/lib/xorg/modules//amdxmm.so
(II) Module amdxmm: vendor="X.Org Foundation"
(II) fglrx(0): [DRI] installation complete
(II) fglrx(0): Direct rendering enabled
(II) fglrx(0): Finished Initialize PPLIB!
(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 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) Loading sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
(II) fglrx(0): Enable the clock gating!
(II) <default pointer>: Setting Device option to "/dev/input/mice"
(II) evaluating device (<default keyboard>)
(II) XINPUT: Adding extended input device "<default keyboard>" (type: KEYBOARD)
(II) evaluating device (<default pointer>)
(II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE)
(II) <default pointer>: ps2EnableDataReporting: succeeded

[forum1793]

The fglrx stuff in your xorg.conf come from fglrx_drv located in /usr/lib/xorg... This is fine. But you also want flgrx.ko loaded as a module before starting X.

drm module should not be loaded. Mine is not loaded nor does the module even exist. When I look into xorg.log there is still much mention of drm.

I believe fglrx MODULE cannot be loaded if drm MODULE is loaded. These modules should be in the /lib area as opposed to the /usr/lib/xorg area.

Try the following:
get out of X.
become root (su or logout and into root)

rmmod drm
modprobe fglrx
startx

If modprobe fglrx gives errors then you need to run the catalyst program. Try to get 8.5 if you have 780g. If you can't do that try the newest and read up on changing the monitor dimensions or something like that by one pixel. You should be able to find by searching on phoronix.

Now see if it runs faster. If it does, as root delete or rename drm.ko in your /lib/modules/2.6.25.16/kernel/drivers/char directory. The only thing you need here is fglrx.ko.

I've run mine with and without agpgart (agpgart.ko) and noticed no difference.

edit: the .ko from the modules will not show up in lsmod.

Good luck.

[warped]

I believe fglrx MODULE cannot be loaded if drm MODULE is loaded.

Thx for replay.

Right. I believe in Your case DRM.ko is direct rendering manager from other graphics drivers or it is generic drm for Xorg supplied drivers like radeon/radeonhd. Taking above into account it is obvious that they shouldn't be loaded simultaneously as they are playing the same role.
In my case there is no drm.ko loaded so my issue is related to something other :-(

At this moment I belive issue is not related to setup/instalation of fglrx - as all logs looks OK, but it might be related to following areas:

1."GART Table is not in FRAME_BUFFER range" warning in kernel logs.

2.my enviroment state (kernel/Xorg configs) is somehow not proper for fglrx.

3.poor compability of fglrx with not mainstream linux distros - as my enviroment is v.carefully assembled appliance based on linux components.

For 3 I assumed: if logs are not complaining about any erros/warinng - all should be OK. This assumption works well for Nv bin drivers, but unfortunatelly not Yet for fglrx.

BTW: do somebody know what is role of libAMDxVBA.so ?
I have problems with autoinclussion this lib into image, so for tests after system boot I copy this lib manually and restart X. Unfortunately presence or absence of this lib changes nothing...

br

[forum1793]

I get same gart table message. Mine shows up in /var/log/messages. Is that where your's comes from?

Sep  2 07:34:43 xxx kernel: [fglrx] GART Table is not in FRAME_BUFFER range

RE .ko stuff: OK, good response. I posted since I didn't know what you meant by drm module is loaded and lsmod is OK.

Do you have xv package/program loaded? When I look at my package manager, I have three programs that might be related. These are:
libXv-1.0.4-i486-1 - has /usr/lib/libXv.so among others
libXvMC-1.0.4-i486-1 - has /usr/lib/libXvMC.so among others
xv-3.10a-i486-5 - although this looks like image manipulation program and is probably not relevant.

I see in you xorg.log file that the resolution is 1600x1200? For my hardware (780g with integrated hd3200) I can't go much higher than 1280x768 (roughly). The on-board chip does allow ~1900xsomething at 30hz but I found I didn't like it (can't remember specifics).

Edit: just tried with video set to ~1600 by 1080 (1080 seems to be highest I can go). glxgears takes a 20% hit. Mythtv does not display one of my recordings. I just get blank myth-video screen. I would suggest you trying at lower resolution.

[warped]

Regarding Xv - I have installed and working Xv as this system has also installed Nv and Nv7050 works as expected.

I decide to verify my HW/fglrx under well known software - KnoppMyth. Surpice - KM5.5 and 8.8/8.7/8.6/8.5 all are lacking Xv in the same way like my system.
So now it looks like issue isn't related to my appliance - but to fglrx/HW.
Honestly speaking I'm surprised that ATI bin drivers are so worse comparing to Nv...

Now Q is more generic: how to get fglrx working on KM5.5 and ASUS M3A78 ?
On KM myth returns: "Cannot allocate requested video surface".
In Xorg.cong I have enabled textures, disabled Overlay, dri and Opengl.
There is no any errors/warnings reported by xorg.log and kernel log except famous "GART Table is not in FRAME_BUFFER range" entry in kernel log.


Do somebody has idea why generic driver isn't working under generic hw and well known software ?

[bridgman]

In Xorg.cong I have enabled textures, disabled Overlay, dri and Opengl.

If you disable DRI I don't think you will get any acceleration, including Xv.

[warped]

If you disable DRI I don't think you will get any acceleration, including Xv.

I managed Xv working under KnoppMyth. Issue was in enabling textures and ALSO updating /etc/ati/amdpcsdb file via aticonfig tool. Now I know that HW/fglrx are Xv capable on my hw and works OK.
When I analyze xorg.log from: appliance and KnopMyth I see following differences:

KnopMyth:
-xorg7.1 based
-there is Xv extension provided by loaded Xorg extmod module

My appliance:
-xorg7.3 based
-myth log says

2008-08-31 22:11:55.920 VideoOutputXv Error: XVideo output requested, but is not supported by display.
Xlib:  extension "XVideo" missing on display ":0.0".

-in xorg.log there is no extmod references at all

So maybe lack of Xv in my appliance is a result of missing Xvideo extension (as Xorg haven't/can't it loaded)?

Now I don't know: is lacking of xorg.log entries related to extmod module in xorg7.3 an result of:

-wrong Xorg7.3 compilation options in my appliance so extmod module is not available (btw: in Xorg.log there is no msgs like can't loaded extmod)

-is rather normal as in 7.3 extmod is build-in while in 7.1 is separately loaded (thats why I see respected entries it in KnopMyth and don't see them in appliance)

it will be great when somebody with Xorg7.3 and fglrx send me his Xorg.log as I it will allow me compare and investigate where is problem with my Xorg7.3 and fglrx...

thx in advance