I'm running Xorg server 1.6.3, intel driver 2.9.1. Linux kernel 2.6.31 with KMS enabled. Hardware is G33. Starting X is fine, but switching to another VT (i.e. a text mode VT) freezes the display; the mouse cursor becomes invisible but there is no switch to text mode and whatever was on the X screen when I switched away remains visible. The switch to the other VT was otherwise successful (I can type commands and my system responds). When I switch back to the X VT, the mouse cursor re-appears and I am able to continue the X session. I can run two X servers in parallel and switch between them no problems. Without KMS everything works as it should. I see the same problem with Intel driver version 2.8.1.
Sorry, intel driver version 2.9.0, not 2.9.1 More details: Chipset: G33 System architecture - x86 (32 bit) xf86-video-intel: 2.9.0 (also with 2.8.1) xserver: 1.6.3 mesa: 7.5.2 libdrm: 2.4.14 kernel: 2.6.31 motherboard: Gigabyte GA-G33-DS3R display connector: VGA
> Starting X is fine, but switching to another VT (i.e. a text mode VT) freezes > the display; the mouse cursor becomes invisible but there is no switch to text > mode and whatever was on the X screen when I switched away remains visible. The > switch to the other VT was otherwise successful (I can type commands and my > system responds). When I switch back to the X VT, the mouse cursor re-appears > and I am able to continue the X session. > is the fbcon kernel module loaded, or built into the kernel?
No, the fbcon module is neither loaded nor built in to the kernel. From the kernel .config file: # CONFIG_FRAMEBUFFER_CONSOLE is not set.
> --- Comment #3 from Davin McCall <davmac@davmac.org> 2009-09-30 17:14:17 PST --- > No, the fbcon module is neither loaded nor built in to the kernel. > > From the kernel .config file: > # CONFIG_FRAMEBUFFER_CONSOLE is not set. > this is your problem then. without fbcon, you don't get a console on kms.
Julien is right. You need fbcon.
see also bug 22040
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.