wine users - Jun 2009 - Unable to use alsa, unusable driver for winecfg

Got a problem with wine.

I compiled the 1.1.24 version and a lot of things work very fine. But I
can't use the Alsa driver output.
When launching winecfg and selecting the Audio tab, a dialog box tell me that
the driver "alsa" is present in the registry but unusable and asks me
to remove it from the registry.

I don't know why the alsa driver is unusable. I have the correct libraries
(/usr/local/lib/wine/winealsa.drv.so) and there's no dependencies problems
on these libraries. When I launch winecfg with the the WINEDEBUG=+driver
environment variable, I got the following messages :

> 
> trace:driver:OpenDriver (L"winealsa.drv", (null), 0x00000000);
> trace:driver:DRIVER_TryOpenDriver32 (L"winealsa.drv", 00000000);
> trace:driver:DRIVER_SendMessage Before call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0001 p1=00000000 p2=00000000
> trace:driver:DRIVER_SendMessage After  call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0001 p1=00000000 p2=00000000 => 00000001
> trace:driver:DRIVER_SendMessage Before call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0002 p1=00000000 p2=00000000
> trace:driver:DRIVER_SendMessage After  call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0002 p1=00000000 p2=00000000 => 00000001
> trace:driver:DRIVER_SendMessage Before call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0003 p1=00000000 p2=00000000
> trace:driver:DRIVER_SendMessage After  call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0003 p1=00000000 p2=00000000 => 00000000
> trace:driver:DRIVER_AddToList DRV_OPEN failed on driver 0x1314f0
> trace:driver:DRIVER_TryOpenDriver32 Unable to load 32 bit module
L"winealsa.drv": load failed
> trace:driver:DRIVER_GetLibName registry: L"winealsa.drv",
L"Drivers32", 0x32f662, 522
> trace:driver:DRIVER_GetLibName system.ini: L"winealsa.drv",
L"Drivers32", 0x32f662, 522
> 

I haven't pulseaudio (removed it) and I don't what else I could do.

Tried to move ~/.wine and launched wine to create a new configuration, same
problem, except it doesn't tell me that alsa is present in the registry.

Using Debian Sid 64 bits.

On Mon, Jun 29, 2009 at 7:14 AM, ThE_TemPLaR<wineforum-user at winehq.org>
wrote:
> Got a problem with wine.
>
> I compiled the 1.1.24 version and a lot of things work very fine. But I
can't use the Alsa driver output.
> When launching winecfg and selecting the Audio tab, a dialog box tell me
that the driver "alsa" is present in the registry but unusable and
asks me to remove it from the registry.
>
> I don't know why the alsa driver is unusable. I have the correct
libraries (/usr/local/lib/wine/winealsa.drv.so) and there's no dependencies
problems on these libraries. When I launch winecfg with the the
WINEDEBUG=+driver environment variable, I got the following messages :
>
>
>>
>> trace:driver:OpenDriver (L"winealsa.drv", (null),
0x00000000);
>> trace:driver:DRIVER_TryOpenDriver32 (L"winealsa.drv",
00000000);
>> trace:driver:DRIVER_SendMessage Before call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0001 p1=00000000 p2=00000000
>> trace:driver:DRIVER_SendMessage After ?call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0001 p1=00000000 p2=00000000 => 00000001
>> trace:driver:DRIVER_SendMessage Before call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0002 p1=00000000 p2=00000000
>> trace:driver:DRIVER_SendMessage After ?call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0002 p1=00000000 p2=00000000 => 00000001
>> trace:driver:DRIVER_SendMessage Before call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0003 p1=00000000 p2=00000000
>> trace:driver:DRIVER_SendMessage After ?call32 proc=0x7d565710
drvrID=00000000 hDrv=0x1314f0 wMsg=0003 p1=00000000 p2=00000000 => 00000000
>> trace:driver:DRIVER_AddToList DRV_OPEN failed on driver 0x1314f0
>> trace:driver:DRIVER_TryOpenDriver32 Unable to load 32 bit module
L"winealsa.drv": load failed
Do you have 32-bit alsa libs installed?

-- 
-Austin

Well yeah. Prepackaged wine builds works with alsa without problem. So I guess
something went wrong at the compilation time since the alsa driver were
compiled, I'm wondering.

Anyway :

Code:

gamer at TACHIBANA:~$ ls -l /usr/lib32/libasound.so.2
lrwxrwxrwx 1 root root 18 2009-06-24 11:52 /usr/lib32/libasound.so.2 ->
libasound.so.2.0.0
gamer at TACHIBANA:~$ ldd /usr/lib32/libasound.so.2
	linux-gate.so.1 =>  (0xf7f45000)
	libm.so.6 => /lib32/libm.so.6 (0xf7e2f000)
	libdl.so.2 => /lib32/libdl.so.2 (0xf7e2b000)
	libpthread.so.0 => /lib32/libpthread.so.0 (0xf7e13000)
	librt.so.1 => /lib32/librt.so.1 (0xf7e0b000)
	libc.so.6 => /lib32/libc.so.6 (0xf7cb2000)
	/lib/ld-linux.so.2 (0xf7f46000)