ATI is the worst brand for Linux, so if the problem are your drivers, I'm afraid you've got to find help on fixing the driver's issue rather than a WINE issue caused by the buggy driver and not WINE itself.<br>
<br>IMHO, while you wait for the RadeonHD driver you'll earn enough money (even if unemployed) to get an NVIDIA card of the same range :P.<br><br><div class="gmail_quote">On Tue, Mar 4, 2008 at 6:24 AM, Marc <<a href="mailto:budalokkos@gmail.com">budalokkos@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">En/na Austin English ha escrit:<br>
<div class="Ih2E3d">> On Mon, Mar 3, 2008 at 9:52 AM, Marc <<a href="mailto:budalokkos@gmail.com">budalokkos@gmail.com</a>> wrote:<br>
><br>
>> The problem is that after some time playing, my X hang and I can't even<br>
>> close session with Ctrl+Alt+Tab or change it with Ctrl+Alt+F1 . It<br>
>> happens at an unknown moment, something between 1 minute and 30 minutes<br>
>> after starting the game. My only option is to start an ssh session from<br>
>> another computer and write down "killall game.exe". This command allows<br>
>> me to recover the functionality of my system and start again the game.<br>
>><br>
><br>
> Sounds like buggy drivers. You could try the open source/vesa drivers<br>
> and see if you still have problems. Wine by definition as a user<br>
> process can't lockup the system (unless ran as root).<br>
><br>
</div>No, I can't:<br>
VESA -> Game needs 3d acceleration<br>
ATI -> Not working for my graphics card<br>
RadeonHD -> I can start the game, but game is totally unplayable.<br>
<div class="Ih2E3d">><br>
>> My system is:<br>
>> -ATI X1600 with fglrx driver version 8.452.1.<br>
>> -Debian Lenny with KDE.<br>
>> -Wine 0.9.56 from sources<br>
>><br>
><br>
> ATI is known for buggy drivers...<br>
><br>
</div>So, I can't do anything else than wait for the promising RadeonHD<br>
drivers to get better performance?<br>
The wine log message I wrote on the other email does not give any clue<br>
on what could be happening, other than my buggy binary driver?<br>
(err:ntdll:RtlpWaitForCriticalSection section 0x6e4181c "?" wait timed<br>
out in thread 0028, blocked by 0027, retrying (60 sec))<br>
<br>
<br>
</blockquote></div><br>