Hi all,
ive just installed wine1.3 on my kUbuntu 10.04 to check if CS:Source is running on my system - and it doesnt, as usual.
When i start CS:S in fullscreen, my Monitor turns off (no signal) and my terminals on F1-F6 are just black. The monitor is not to bring on again, the only thing i can do is to reboot by login into ssh from another machine or press the power button to turn off.
When i start CS:S with parameter "-startwindowed" everything runs fine - until i switch to fullscreen mode.
Any suggestions?
My System:
wine 1.3.0 beta
kUbuntu 10.04
Intel Core2Duo E8400 / 4GB
ATI HD4830 with fglrx 2:8.723.1 (newest from ubuntu repo)
Counterstrike Source: Monitor turns off when starting
-
James Mckenzie
Counterstrike Source: Monitor turns off when starting
LukasW <[email protected]> wrote:
James McKenzie
Look for an X crash in your syslog. Looks like you have to re-install or downgrade your video drivers.Sent: Aug 19, 2010 8:03 AM
To: [email protected]
Subject: [Wine] Counterstrike Source: Monitor turns off when starting
Hi all,
ive just installed wine1.3 on my kUbuntu 10.04 to check if CS:Source is running on my system - and it doesnt, as usual.
When i start CS:S in fullscreen, my Monitor turns off (no signal) and my terminals on F1-F6 are just black. The monitor is not to bring on again, the only thing i can do is to reboot by login into ssh from another machine or press the power button to turn off.
When i start CS:S with parameter "-startwindowed" everything runs fine - until i switch to fullscreen mode.
Any suggestions?
James McKenzie
hi,
after some reading ive tested turning off Desktop GL-Effects. First that doesnt worked, too, but after setting the fullscreen resolution to native it works.
Unfortunately it only works in lokal mode with bots. When i play online it crashes after 2-3 mins. And it crashes so hard, i cant even get control with magic-sysrq keys.
Cant find anything unusual in my logs.
after some reading ive tested turning off Desktop GL-Effects. First that doesnt worked, too, but after setting the fullscreen resolution to native it works.
Unfortunately it only works in lokal mode with bots. When i play online it crashes after 2-3 mins. And it crashes so hard, i cant even get control with magic-sysrq keys.
Cant find anything unusual in my logs.
ok, ive got output from wine with "wine Steam.exe > steam.log 2>&1".
This time magic-sysrq was working, so i was able to make a clean emergency shutdown (term,kill,flush2disk,unmount,reboot).
Last line of the log is (left out "fixme" messages):
This time magic-sysrq was working, so i was able to make a clean emergency shutdown (term,kill,flush2disk,unmount,reboot).
Last line of the log is (left out "fixme" messages):
Google has some old results, but no solutions... i do not even think that this is the problem. Maybe its something with networking - local games with bots are working well.
err:ntdll:RtlpWaitForCriticalSection section 0x14b7814 "?" wait timed out in thread 001f, blocked by 0020, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x14b7814 "?" wait timed out in thread 001f, blocked by 0020, retrying (60 sec)
(... some fixme messages...)
err:ntdll:RtlpWaitForCriticalSection section 0x6899ea20 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 0024, blocked by 0009, retrying (60 sec)
Counterstrike Source: Monitor turns off when starting
On 2010-08-20 (August, Friday) 08:07:27 LukasW wrote:
Your problem isn't related to Wine, it is (with almost 100% probability)
because of buggy video driver. Theoretically you can report the problem to ATI,
wait for some months, then retest, then report next problem... Or you can try
practical approach and buy NVidia card and play your game now (assuming Wine
supports it, find the entry for your game in AppDB to be sure). There is no
sarcasm in my message. This is the way it is.
ATI drivers have so many bugs in them that you very likely to find them in many
3D applications, especially on Linux (in my personal experience they drivers
for Windows are much better but still worse than NVidia's; on Linux NVidia is
only practical choice if you want to play games or use 3D CAD applications).
Anyway, if you see that your X server or kernel crashing - you know that you
are dealing with problem not related to Wine in any way. However, Wine often
triggers some "hidden" bugs in video driver, so this is why many people
mistakenly think about such problems as Wine bugs. If this happens, no matter
what video card you are using, you should report it to the manufacturer of your
video chipset and hope they will fix the problem for you.
Wine is an user-space application - it can't crash the kernel or X server.it crashes after 2-3 mins. And it crashes so hard, i cant even get control
with magic-sysrq keys.
...
This time magic-sysrq was working, so i was able to make a clean emergency
shutdown
Your problem isn't related to Wine, it is (with almost 100% probability)
because of buggy video driver. Theoretically you can report the problem to ATI,
wait for some months, then retest, then report next problem... Or you can try
practical approach and buy NVidia card and play your game now (assuming Wine
supports it, find the entry for your game in AppDB to be sure). There is no
sarcasm in my message. This is the way it is.
ATI drivers have so many bugs in them that you very likely to find them in many
3D applications, especially on Linux (in my personal experience they drivers
for Windows are much better but still worse than NVidia's; on Linux NVidia is
only practical choice if you want to play games or use 3D CAD applications).
Anyway, if you see that your X server or kernel crashing - you know that you
are dealing with problem not related to Wine in any way. However, Wine often
triggers some "hidden" bugs in video driver, so this is why many people
mistakenly think about such problems as Wine bugs. If this happens, no matter
what video card you are using, you should report it to the manufacturer of your
video chipset and hope they will fix the problem for you.
