AMD's UVD2-based XvBA Finally Does Something On Linux

[energyman]

yeah, I mean, before amd64 was around there was nobody else using 64bit libs....

[deanjo]

which just shows how incredible standards can be.

Logically it does not make sense.

Take that up with the Linux Foundation since they maintain the FHS. It is however the "standard" and there for compatibility reasons for older code that predates 64-bit.

[energyman]

which just shows how incredible standards can be.

Logically it does not make sense.

[deanjo]

FHS says:

"The 64-bit architectures PPC64, s390x, sparc64 and AMD64 must place 64-bit libraries in /lib64, and 32-bit (or 31-bit on s390) libraries in /lib."

[deanjo]

Sorry fhs not lsb

[deanjo]

except when they land in /usr/lib32 where they belong.

IIRC LSB specifies /usr/lib not /usr/lib32

[energyman]

except when they land in /usr/lib32 where they belong.

[deanjo]

usually on 64 bit systems /usr/lib is a symlink to /usr/lib64

Ummm not really. Compatibility libraries are usually in /usr/lib as well in 64-bit systems.

[energyman]

usually on 64 bit systems /usr/lib is a symlink to /usr/lib64

[peter124]

tried vainfo after that, i got.
libva: libva version 0.31.1
libva: User requested driver 'fglrx'
libva: Trying to open /usr/local/lib/dri/fglrx_drv_video.so
libva: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

I used the tips from page 101 and set
export LIBVA_DRIVER_NAME="fglrx"

Now I find with strace that mplayer tries to open
/usr/lib64/libXvBAW.so.1
which I don't have.

I use Opensuse 11.3 which contains only this library in
/usr/lib

Any ideas?