Bug 43248 - Starting teeworlds results in black screen
Summary: Starting teeworlds results in black screen
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: high normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2011-11-25 12:23 UTC by Sandeep
Modified: 2014-02-18 00:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

dmesg output (75.75 KB, patch)
2011-11-25 12:23 UTC, Sandeep
no flags Details | Splinter Review
output of lspci (2.12 KB, text/plain)
2011-11-25 12:23 UTC, Sandeep
no flags Details

Description Sandeep 2011-11-25 12:23:06 UTC
Created attachment 53856 [details] [review]
dmesg output

Asus K53TA laptop. AMD A6-3400M with integrated Radeon HD6520G and discrete Radeon HD6650M. Display is through 6520G.

Ubuntu 11.04 64 bit with kernel 3.2-rc1 and xorg-edgers ppa.

When I start teeworlds, the screen goes blank (the display seems to be switched off). However I am able to switch to command line using Ctrl + Alt + F1 and running:

sudo service gdm start 


sudo service gdm stop

restarts Gnome for me.

dmesg shows some errors with atombios.
Comment 1 Sandeep 2011-11-25 12:23:37 UTC
Created attachment 53857 [details]
output of lspci
Comment 2 Sandeep 2011-11-25 16:02:45 UTC
This happens for OpenArena as well.

Trine on the other hand works properly (on low detail)
Comment 3 BDM 2012-12-02 20:34:28 UTC
I'm having the same problem with the same dmesg output with the same chipset HD6520 for any game that sets true full screen graphics mode on Ubuntu 12.10. If I use a game, like Titanion, that can be closed by simple keystrokes, I can manage to escape the black screen and get back to my normal desktop. 

Also perhaps unrelated, setting to a lower resolution desktop mode 800x600, or lower seems to set an incorrect mode that garbles the screen. That too I can escape if I have an xrandr ready to enable me to do so. 

Here's uname -a

Linux falcon 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Relevant part of dmesg
[  681.224351] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[  681.224364] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E2F6 (len 2585, WS 4, PS 4) @ 0xE9E0
[  681.259083] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery reached max voltage
[  681.259095] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed

I think the driver is partially broken for this chipset.
Comment 4 Sandeep 2014-02-18 00:43:59 UTC
Works properly now. Currently using Linux 3.14.rc2 and Mesa 10.0.3 on 64 bit Arch Linux

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.