From: David J Ring Jr <n1ea@arrl.net>
To: linux-fbdev@vger.kernel.org
Subject: Re: Getting FB to work in Console
Date: Sun, 13 Nov 2011 18:58:19 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1111131829410.2535@localhost.localdomain> (raw)
In-Reply-To: <CADO5RbhunU1X7mWwGDbVRc1FSPKBaLudAVav0TMkBoQ_1zp0Mw@mail.gmail.com>
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Ë1268f1-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
>
next prev parent reply other threads:[~2011-11-13 18:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 23:42 Getting FB to work in Console D.J.J. Ring, Jr.
2011-11-13 1:00 ` Florian Tobias Schandinat
2011-11-13 2:46 ` David J Ring Jr
2011-11-13 16:57 ` Anatolij Gustschin
2011-11-13 18:58 ` David J Ring Jr [this message]
2011-11-13 19:11 ` David J Ring Jr
2011-11-13 20:00 ` Geert Uytterhoeven
2011-11-13 20:11 ` Anatolij Gustschin
2011-11-13 20:53 ` Anatolij Gustschin
2011-11-13 21:17 ` David J Ring Jr
2011-11-13 21:21 ` David J Ring Jr
2011-11-13 21:39 ` Anatolij Gustschin
2011-11-13 21:44 ` Bruno Prémont
2011-11-13 22:48 ` David J Ring Jr
2011-11-13 22:50 ` David J Ring Jr
2011-11-14 0:15 ` Anatolij Gustschin
2011-11-14 0:32 ` Anatolij Gustschin
2011-11-14 1:10 ` David J Ring Jr
2011-11-14 18:58 ` Anatolij Gustschin
2011-11-14 20:09 ` D.J.J. Ring, Jr.
2011-11-14 20:25 ` Bruno Prémont
2011-11-14 21:50 ` David J Ring Jr
2011-11-14 23:38 ` D.J.J. Ring, Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1111131829410.2535@localhost.localdomain \
--to=n1ea@arrl.net \
--cc=linux-fbdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox