You are not logged in.
Pages: 1
## Using Wine in Chakra Linux
Around September of 2012, The Chakra Project began to make big changes to their system and it's workings. Chakra became the first distro to drop i686 support, finally added in systemd and PulseAudio, and moved /lib to /usr/lib .
For some users, Wine now happens to have big problems running some applications. I collected all the information I could find on the problem I had and managed to fix most of the severe ones, so hopefully we could add in more tips.
### 3D Graphics Drivers
If you are using a 64-bit version of Chakra (which everybody does now), you might notice that apps with 3D graphics may no longer work. If run from the command line, you may find an error similar to this one:
Chakra fixme:d3d:wined3d_guess_card No card selector available for GL vendor 0x4 and card vendor 0000 (using GL_RENDERER "Gallium 0.4 on llvmpipe (LLVM 0x301)").This means that Wine was unable to find a driver to work with your graphics card. But, why? Chakra already installs it for us, doesn't it? However, we all use 64-bit installs now, so we don't have the 32-bit drivers that Wine requires.
No worries. Just install the package below that fits your graphics card:
* Intel Integrated Graphics: `lib32-intel-dri`
* AMD/ATI Radeon (official drivers?): `lib32-ati-dri`
* AMD/ATI Radeon (Catalyst): `lib32-catalyst-utils`
* Nvidia: `lib32-nouveau-dri`
#### Notice
Some programs that go into fullscreen mode (example: most of the Touhou games), still have problems afterwards, culminating in the following error:
*** glibc detected *** /home/iruel/.th08/th08.exe: malloc(): memory corruption: 0x7d743b28 ***This is an issue which still needs to be researched to see if this is an upstream regression related to the new version of Wine, or a problem in Chakra.
### Sound is glitchy/crackly/distorted
New installs of Chakra have PulseAudio installed as the primary sound system. This can sometimes cause issues with Wine, since Wine interfaces with PulseAudio's ALSA emulation layer, which is not a perfect solution.
The PulseAudio sound server uses a timer-based audio scheduling by default instead of the traditional interrupt-driven approach.
Timer-based scheduling may expose issues in some ALSA drivers. On the other hand, other drivers might be glitchy without it on, so check to see what works on your system.
By default, Chakra's PulseAudio package has timer-based scheduling disabled. To turn timer-based scheduling on, replace the line:
load-module module-udev-detect tsched=0in `/etc/pulse/default.pa` by:
load-module module-udev-detectThen restart the PulseAudio server.
pulseaudio --kill
pulseaudio --start#### Temporarily disable PulseAudio
Sometimes PulseAudio just won't work out right. Because completely uninstalling Pulseaudio is not a viable solution, we need to somehow temporarily disable it.
We can use the `pasuspender` command for this, which is already included with PulseAudio. Bring up a terminal, run the command for the program preceded by `pasuspender --` , and you're good to go. After it's done, pulseaudio will work normally.
pasuspender -- wine th123.exeLast edited by iruel (2012-10-05 08:40:54)
Offline
It would be nice if this was moved into a wiki article.
Offline
If the switch to no consolekit and new polkit works, then disabling time scheduler for pulse might be possible to remove (it is a Chakra patch to stop a few known issue's with notifications delay and crackling sound.
Removal of consolekit is in staging now.
Offline
*** glibc detected *** /home/iruel/.th08/th08.exe: malloc(): memory corruption: 0x7d743b28 ***This is an issue which still needs to be researched to see if this is an upstream regression related to the new version of Wine, or a problem in Chakra.
I believe this is a 100% chakra 'lib32' driver problem, something about syncing them form testing, fact is wine32 doesn't work ATM.
Offline
Pages: 1
