Hi all!
I have installed DirectFB 1.3.0 and XDirectFB (latest from cvs, compiled
with xorg-server-1.3.0.0) on a virtual machine (VM), running Ubuntu
(2.6.22-16-server). Now I'm happy :) and I finnaly can run couple
applications that require GUI (like skype).
My question is: how can I hide XDirectFB so it can be accessed _only_ via
vnc (or alike), but nothing should be rendered on a VM terminal? I'd like to
have XDirectFB running in memory only, without affecting the way VM booted
before (with bunch of boot messages and finally with 'login' prompt). By the
way "x11vnc 0.9.3" is already working with XDirectFB just fine even though I
didn't use "--enable-vnc" during my build!
The thing is - to make Ubuntu create and use /dev/fb0 device I had to boot
it with kernel parameter "vga=<whatever-mode-number>" and since then VM
terminal puts: "Starting up ... " message and nothing else till the boot
completes and XDirectFB starts. Then I see all the GUI-related applications,
that I start via another ssh session, rendered on the VM terminal and
anybody, passing by computer running VMPlayer, can interfere with
application without being asked for authorization.
On the other hand, if I start Ubuntu without kern parameter "vga=<...>" then
/dev/fb0 will not be created and XDirectFB obviously fail to start:
=========[quote]=========
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
--> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment
variable.
(!) DirectFB/Core: Could not initialize 'system_core' core!
--> Initialization error!
(#) DirectFBError [XDirectFBInitOutput(): DirectFBCreate]: Initialization
error!
Fatal server error:
no screens found
AbortDDX
Quitting XDirectFB...
# fbset -i
open /dev/fb0: No such file or directory
# ls -l /dev/fb*
ls: /dev/fb*: No such file or directory
=========[/quote]=========
Now, if I try to create /dev/fb0 device(s) manually, the result will be the
same:
=========[quote]=========
from: Using framebuffer devices on Intel platforms
url: http://tldp.org/HOWTO/Framebuffer-HOWTO-5.html
. . .
You'll need to create the framebuffer device in /dev. You need one per
framebuffer device, so all you need to do is to type in mknod /dev/fb0 c 29
0 for the first one. Subsequent ones would be in multiples of 32, so for
example to create /dev/fb1, you would need to type in mknod /dev/fb1 c 29
32, and so on up to the eighth framebuffer device (mknod /dev/fb7 c 29 224)
. . .
# mknod /dev/fb0 c 29 0
# ls -l /dev/fb*
crw-r--r-- 1 root root 29, 0 2009-03-12 12:43 /dev/fb0
# fbset -i
open /dev/fb0: No such device
=========[/quote]=========
As you can see, even after /dev/db0 was created (by mknod) it still kinda
dead baby for fbset. And fbset keep insisting: "No such device".
Please help me to hide the precious creature (like DirectFB really is:) on
some deeper levels of Linux subconscious, so only Linux aware of it, but not
a public : )
Thanks,
Have a good one!!1
Dmitry
_______________________________________________
directfb-users mailing list
directfb-users@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
