Hello Anatolij,
Nice to hear from you and thank you for your suggestions.
I did what you said and now I have a /dev/fb0 with permissions
ls /dev/fb0 -alsh
0 crw-rw---- 1 root video 29, 0 Nov 13 18:25 /dev/fb0
Output of cat /proc/fb
No output.
Output of cat proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=cb1268f1-4e20-4409-87b1-3d882c14102c ro nomodeset
Output of dmesg | grep vesa
No output.
When I try to run links2 -g now I get these errors:
~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.2.10 |~~~~~~~~~~~~~~~~~~~~~~~~~~
(c) 2001-2008 The world wide DirectFB Open Source Community
(c) 2000-2004 Convergence (integrated media) GmbH
----------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2010-06-30 18:37)
(!) DirectFB/FBDev: Error opening '/dev/fb0'!
--> No such device
(!) DirectFB/Core: Could not initialize 'system_core' core!
--> Not supported!
I hope that is helpful.
David
On Sun, 13 Nov 2011, Anatolij Gustschin wrote:
You have to add write permissions for the group also. Check if
/dev/fb0 can be accessed if you create it by using
sudo mknod /dev/fb0 c 29 0 -m 660
sudo chown :video /dev/fb0
What is the output of following commands on your system?
cat /proc/fb
cat /proc/cmdline
dmesg | grep vesa
Anatolij
--
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
