I'm using radeonhd dirver for my radeon HD 3650 card Machine: Asus M51T kernel: 2.6.29 I installed packages radeonhd and drm-module from git from the r6xx_r7xx_branch System crashes when I logout from X and when I try to switch between virtual consoles ctrl+alt+f.. the screen becomes black and computer does not react on anything. The only way I can turn off my computer is power button. If I replace drm-module acceleration dissapears and problem also, but it's impossible to work without acceleration (webpages are scrolling very slowly) What do I do to fix it? ---------------------------------------------------- Wciel się w Richarda B. Riddicka w najnowszej grze akcji science fiction. THE CHRONICLES OF RIDDICK: Assault On Dark Athena już w sprzedaży! http://klik.wp.pl/?adr=http%3A%2F%2Fcorto.www.wp.pl%2Fas%2Fchronicles_of_riddick.html&sid=740 -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
2009/5/21
I'm using radeonhd dirver for my radeon HD 3650 card Machine: Asus M51T kernel: 2.6.29 I installed packages radeonhd and drm-module from git from the r6xx_r7xx_branch System crashes when I logout from X and when I try to switch between virtual consoles ctrl+alt+f.. the screen becomes black and computer does not react on anything. The only way I can turn off my computer is power button. If I replace drm-module acceleration dissapears and problem also, but it's impossible to work without acceleration (webpages are scrolling very slowly) What do I do to fix it?
Make sure you are using at least version 1.2.5. Alex -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Thursday 21 May 2009 6:57:23 am chemaniak@wp.pl wrote:
I'm using radeonhd dirver for my radeon HD 3650 card Machine: Asus M51T kernel: 2.6.29 I installed packages radeonhd and drm-module from git from the r6xx_r7xx_branch System crashes when I logout from X and when I try to switch between virtual consoles ctrl+alt+f.. the screen becomes black and computer does not react on anything. The only way I can turn off my computer is power button. If I replace drm-module acceleration dissapears and problem also, but it's impossible to work without acceleration (webpages are scrolling very slowly) What do I do to fix it?
What level of radeonhd are you running? What about your desktop? I was running kde 4.2.85/Qt 4.5.1 with the latest git radeonhd with the option EXANoUploadToScreen and getting basically your problem, though I never disabled the drm module. (Without this option, I was getting hangs during normal operation.) Now I'm back to kde 4.2.3/Qt4.5.1, and I merely have screen corruption, no hanging... much better ;-) -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On May 21, 09 14:57:23 +0200, chemaniak@wp.pl wrote:
System crashes when I logout from X and when I try to switch between virtual consoles ctrl+alt+f.. the screen becomes black and computer does not react on anything.
Can you check whether you can still log in from remote? If you don't have a second computer, can you check whether SysRq+U, SysRq+B still works (e.g. the kernel still runs)? In the later case, please check /var/log/Xorg.0.log (before starting a new X session) whether the server crashed.
The only way I can turn off my computer is power button. If I replace drm-module acceleration dissapears and problem also, but it's impossible to work without acceleration (webpages are scrolling very slowly)
When disabling DRI you should explicitly use
Option "AccelMethod" "shadowfb"
because the driver (ATM) cannot fall back to this acceleration method
and will run completely unaccelerated.
CU
Matthias
--
Matthias Hopf
3-06-2009 at 18:09 Matthias Hopf wrote:
Can you check whether you can still log in from remote? If you don't have a second computer, can you check whether SysRq+U, SysRq+B still works (e.g. the kernel still runs)? In the later case, please check /var/log/Xorg.0.log (before starting a new X session) whether the server crashed.
I can't login from remote (no pings, no ssh). Neither SysRq+U nor SysRq+B works. /var/log/Xorg.0.log looks exactly the same as after launching xorg server, so the crash leaves no trace in Xorg.0.log: Last two lines: (II) config/hal: Adding input device Video Bus (II) config/hal: Adding input device Video Bus Maybe there's a way to launch xserver in more verbose debug mode? ---------------------------------------------------- Wyjątkowy koncert! Phil Manzanera,Leszek Możdżer,Charles Hayward, Yaron Stavi. 7 czerwca godz. 20.00 Opera Leśna Sopot. Więcej info http://klik.wp.pl/?adr=http%3A%2F%2Fcorto.www.wp.pl%2Fas%2Ffirebirds2.html&sid=754 -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Jun 05, 09 11:41:58 +0200, chemaniak@wp.pl wrote:
3-06-2009 at 18:09 Matthias Hopf wrote:
Can you check whether you can still log in from remote? If you don't have a second computer, can you check whether SysRq+U, SysRq+B still works (e.g. the kernel still runs)? In the later case, please check /var/log/Xorg.0.log (before starting a new X session) whether the server crashed.
I can't login from remote (no pings, no ssh). Neither SysRq+U nor SysRq+B works. /var/log/Xorg.0.log looks exactly the same as after launching xorg server, so the crash leaves no trace in Xorg.0.log: Last two lines: (II) config/hal: Adding input device Video Bus (II) config/hal: Adding input device Video Bus
Maybe there's a way to launch xserver in more verbose debug mode?
Yes, try X -logverbose 7 -verbose 7
However, in a crash it's very likely that you don't see the last few
lines in the log, because the kernel hasn't written them out.
You're more likely to see them in a ssh session on the screen.
Matthias
--
Matthias Hopf
participants (4)
-
Alex Deucher -
chemaniak＠wp.pl -
Darin McBride -
Matthias Hopf