Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): > Hi, > why is first framebuffer (or X) blanked while using second? I shoul use > some switch to prevent this? Or vt from which the process is started is > always blanked?
I guess the blanking is caused by the switch to a new vt that is allocated by DirectFB. You may try the "--no-vt-switch" option, but another problem will be the usage of input devices. I don't know how to multiple keyboards for different framebuffers. At least you can delete the input drivers installed by DirectFB, this may enable you to use X with input on the first and DirectFB with output only on the second framebuffer. However there needs to be an option for disabling loading of all or specific input drivers. Imagine using only a remote control as input for DirectFB (e.g. using dfbsee) and the rest for your X ;) -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" convergence integrated media GmbH -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
