| Message ID | EBB7CD28-D698-484A-AE0B-942ECB4B0970@exactcode.de |
|---|---|
| State | New |
| Headers | show |
Index: package/base/module-init-tools/modprobe.conf.data =================================================================== --- package/base/module-init-tools/modprobe.conf.data (revision 29092) +++ package/base/module-init-tools/modprobe.conf.data (revision 29093) @@ -203,5 +203,4 @@ alias char-major-89-* i2c-dev alias net-pf-24 pppoe -# do not auto-load (e.g. on boot) -blacklist ide-generic +blacklist cirrusfb # plain black screen in Qemu
Hi, I saw that some pretty long time ago, but didn't care enough to investigate, just disabled the cirrus fb in T2 (http://t2-project.org): rene@8way:t2-trunk-clean$ svn log -r29093 ------------------------------------------------------------------------ r29093 | rene | 2008-05-27 09:37:57 +0200 (Tue, 27 May 2008) | 4 lines * updated linux26 module blacklist, do not list ide-generic (that's handled these days), but add cirrusfb, which causes a pure black screen in Qemu ------------------------------------------------------------------------ rene@8way:t2-trunk-clean$ svn di -c r29093 On 26.01.2010, at 17:02, Alexander Graf wrote: > > On 26.01.2010, at 15:44, Jan Kiszka wrote: > >> Hi, >> >> just received some Linux guest kernel that refuses to properly use its >> framebuffer console under QEMU (probably any version, tried down to some >> 0.10.x). It turned out that it has CONFIG_FB_CIRRUS enabled and fails to >> initialize the display when this is actually used. Anyone came across >> this before or has some idea what goes wrong? > > The only thing I've seen that might be a similar issue is that the Cirrus driver on Windows NT 4 just shows a black screen with KVM. > > Alex >