WINE & 2.6.32 Kernels

[tpreitzel]

I'm using Bluewhite64, a Slackware derivative. Lately, my computer is hard locking within 2 seconds when selecting the audio tab of winecfg. I have many video and audio devices on my system which never interfered with WINE previously. The only major change that I made was moving to a 2.6.32 kernel and updating git versions of mesa/drm/radeon drivers. I've tried old versions of WINE and recent versions of WINE with the 2.6.32 kernel and ALL versions of WINE hard lock my computer. No, I will NOT remove 2.6.32 just to use WINE. This problem needs to be solved as I simply can't believe that I'm the only one experiencing this nightmare. My system boots up video cameras with uvcvideo,pwc,em28xx and gspca_spca505 drivers along with ALSA support. My main audio driver is an onboard HDA-Intel. I can use WINE if I don't attempt to select the audio tab of winecfg which simply brings up and hourglass and hard locks the computer within a second. If I attempt to run applications which use audio, the applications simply hang, but don't hard lock the computer.

[tpreitzel]

I'm beginning to suspect the bleeding edge mesa/drm/radeon drivers as the culprit. I'll sit tight and continue updating the drivers over the next week or so. Hopefully, this problem will just disappear.

[vitamin]

WINE & 2.6.32 Kernels
Lately, my computer is hard locking within 2 seconds when selecting the audio tab of winecfg.

Works fine here with 2.6.32. Make sure you have alsa sound selected.

[tpreitzel]

Where does winecfg store the audio information, because I can't check the settings via the audio tab of winecfg... my system freezes.

BTW, I just tried AMD's latest fglrx driver and the problem remains so it's probably not related to the open source drivers. I suspect something changed in WINE and some incompatibility exists with the 2.6.32 kernel and the emulation libraries used by Bluewhite64 v 13.0. I don't know which but it's lockup city like I've never seen previously on Linux.

[tpreitzel]

Every time I run a wine application, I get the following couple of lines from dmesg:

hda-intel: Too big adjustment 32
hda-intel: Too big adjustment 32

For example, I just tried running Comanche 4 from NovaLogic. Just before the intro appears, the desktop (XFCE 4.6.1) crashes to the command line. If I try to startx again, the whole computer freezes. If I just reboot from the command line, the system will reboot.

[vitamin]

Where does winecfg store the audio information

Code: Select all

[HKEY_CURRENT_USER\Software\Wine\Drivers]
Audio="alsa"

[tpreitzel]

Thanks. I used regedit to add a Drivers key because it totally missing. I assume winecfg creates the Drivers key? Under the Drivers key, I added a string Audio=alsa, but the lockups continue. I have the following error when running winecfg:

err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element

ALSAmixer -c0 shows all the elements of the hda-intel mixer just fine so I don't know what the problem is. Essentially, WINE is unusable with audio. I did get audio to work with WINE when playing NovaLogic's F-22 Lightning 3, but something is really screwed up with WINE's audio or some combination theref. Applications without sound run under WINE without locking up the computer. Applications with sound generally will cause a crash to the command line or lock of the computer. I don't know. It's hard to identify the true culprit in this mess, but it seems to be WINE. All of my other applications including audio run fine without WINE.

[vitamin]

Applications with sound generally will cause a crash to the command line or lock of the computer.

Wine is 100% user space app. If you have a complete computer lockup - look at your drivers/kernel. Unprivileged user space app by definition can't do that.

[tpreitzel]

OK,

I just built the latest stable kernel, 2.6.32.1. In the process, I have NOT installed one of my drivers yet for the AverTV Hybrid Volar Max, which uses a proprietary binary driver. I do NOT know at this point if that binary driver is related to this problem. I don't think so because of the following error. I'm inclined to guess that the ia32 emulation libraries used with Bluewhite64 need to be updated for use with WINE. Looking at the error, what's your opinion?

err:module:load_builtin_dll failed to load .so lib for builtin L"winenas.drv": libaudio.so.2: cannot open shared object file: No such file or directory
err:module:load_builtin_dll failed to load .so lib for builtin L"wineesd.drv": libesd.so.0: wrong ELF class: ELFCLASS64

[tpreitzel]

The title shows the offending kernel driver which appears to be causing the problem with the lockups. I'll do more testing, but I'm pretty sure the problem isn't the h826d driver itself, but the USB wrapper, averusbh826d ... <sigh>

I'll stay in touch... The wrapper and driver work well enough outside WINE which is strange ... WINE is doing something that causes this USB wrapper to lockup the computer.

[DaVince]

Wine calls upon more library functions than any other regular application, especially in sound and video. So it might actually be exposing a (serious) bug in the sound or video drivers.

[tpreitzel]

Although, the averusbh826d.ko driver was causing the lockup with the OLDER version of WINE, I'm no longer experiencing lockups with WINE 1.1.44 with the SAME version of Avermedia's driver! So, the problem was due to WINE (at least partly) after all! I understand that WINE 1.1.44 has new audio code for OpenAL which likely fixed the problem with the hard lockups ...