>> Only with bochsfb or with vesafb (+ fbdev xorg driver) too? > > vt-switching with vesafb/X11 works fine on a grml 64-bit image. However, xorg > uses vesa driver in this case, not fbdev (fbdev / fbdevhw xorg modules are > initially loaded but then unloaded). X11 uses 1280x768 and vesafb uses 1024x768 > according to dmesg. You should be able to force the fbdev driver using xorg.conf. > But i haven't been able to test ubuntu+vesafb. Ubuntu kernels use efifb > (CONFIG_FB_EFI=y) and fbconsoles don't work at all with this driver + > qemu/seabios/vgastd. I think this is a grub2 setup issue. Grub2 can pass gfx mode params to the linux kernel in a way efifb is able to handle. > vt7 http://picpaste.de/bochsfb-badstart-AirrXZuF.png > vt1 http://www.picpaste.de/bochsfb-badstart-f1-EO10MVdF.png > it still happens with the latest bochsfb driver (tested with 3.6.0 though, not > 3.7.0-rc3 yet) Most likely this is a guest-side bug and not specific to bochsfb. Console switching depends on all parties being cooperative. Nothing stops an application writing to the framebuffer even it isn't running on the foreground console. cheers, Gerd -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
