Catalyst 10.1 prouduction support for Karmic

[jamey0824]

I laugh at this, the driver has broken packing for the very system it claims to support. Anyways, how can I work around this broken packaging and install this. umm on Karmic that is.

[Melcar]

You don't need to make packages. Just do:

sudo sh ati-driver-installer-10-1-x86.x86_64.run

You can also try the fix in post #56 (haven't tried it myself yet):
http://www.phoronix.com/forums/showt...t=21739&page=6

[jamey0824]

To simple, thanks. I guess i got in the habit of using the cchtml install guide. I think i originally did because of having driver install problem. Perhaps ati fixed whatever that was.

[RealNC]

Note that doing this will result in an installation outside the package manager with all the problems that come with that (uninstallation and updates.)

[Melcar]

Uninstalling is as simple as running sh ./fglrx-uninstall.sh inside the /usr/share/ati folder. After that you can proceed to install the next version. With this method you can't use XvBA though, if that project interests you.

[monraaf]

With this method you can't use XvBA though, if that project interests you.

How's that?

[Melcar]

Wenever I install the driver that way I can't use XvBA, with the following vainfo error:

libva: libva version 0.31.0-sds4
Xlib:  extension "XFree86-DRI" missing on display ":0.0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/va/drivers/fglrx_drv_video.so
xvba_video: error: dlopen(libXvBAW.so.1): libXvBAW.so.1: cannot open shared object file: No such file or directory
libva error: /usr/lib/va/drivers/fglrx_drv_video.so init failed
libva: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

I get no such error and working XvBA when I install with packages however.

[monraaf]

Hmm, just tried it again.

libva: libva version 0.31.0-sds4
Xlib:  extension "XFree86-DRI" missing on display ":0.0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/va/drivers/fglrx_drv_video.so
libva: va_openDriver() returns 0

Seems to initialize fine here. Maybe a 32/64 bit difference? Kano probably has the answer

Playback is still FUBAR here though.

[Melcar]

Yeah. It's a 32/64bit thing. Using the installer doesn't get you the proper 64bit libraries or something like that, while with packages it does.