I never used to have this problem, but i'm running current (swaret used every few days to keep it so, it's currently completely uptodate). Using a custom 2.6.11 kernel though.

However, if i want to check something and ctl-alt-F1 to the main console, check messages printed there, then try to ctl-alt-f7 bakc to x, x shows up, and immediately freezes.


I don't know what information would be neccecery here, so if anything is needed please jsut ask


I'd like to sort this out as i hate being unable to use those hotkeys, they're far too useful.



thanks

-0-

Did you notice this problem with 2.6.10? I personally have had tons of problems with 2.6.11
I just stayed with my 2.6.10-ck03 kernel. 2.6.11 became a hassle and I figured I'd wait till 2.6.12 and see if stuff gets fixed.

What is your video card, have you framebuffer enabled and what Xorg driver do you use for your video card ?

radeon mobility U1, utter piece of shit that it is

I havaen't been able to get direct rendering fixed with it

direct rendering appears to start in the logs, but then stops working, it worked with 2.6,10, however to do so i had to recompile x (i'd rather not bother with doing so if i can, it's irritating to say the least)


Framebuffer support is indeed on in the console, using the "radeon" X.org driver, using cvs versions of mesa and DRM drivers (not kernel specific ones) but not using cvs X. using pat's 6.8.2 packages, from the current tree.

There is good chance that it is a framebuffer issue as the system switch from the
framebuffer driver and the X driver when you ctl+alt+F7

At least, try boot without framebuffer (vga=normal) to test