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 21:17:45 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1111132106180.2425@localhost.localdomain> (raw)
In-Reply-To: <CADO5RbhunU1X7mWwGDbVRc1FSPKBaLudAVav0TMkBoQ_1zp0Mw@mail.gmail.com>
OK so how do I get a frame buffer driver loaded?
I don't have any backlisted framebuffer drivers, what is stopping me from
loading a frame buffer driver?
Does anyone know what I have to do?
David
On Sun, 13 Nov 2011, Anatolij Gustschin wrote:
> Hello David,
>
> On Sun, 13 Nov 2011 19:10:59 -0500 (EST)
> David J Ring Jr <n1ea@arrl.net> wrote:
>
>> Hello Anatolij,
>>
>> And when I reboot /dev/fb0 disappears again.
>
> Yes, this is expected since there is no frame buffer
> driver loaded in your system.
>
>> What is very strange to me is that when I run links2 -g the error message
>> says that /dev/fb0 does not exist, while if I list the file it says that
>> it is there ls /dev/fb0 says the file is there.
>
> I'll try to explain my understanding of the issue.
> The device node file /dev/fb0 is only an interface to the frame
> buffer driver. It can be created by the kernel automatically if
> there is a graphic chip in the system and the appropriate frame
> buffer driver is loaded and some device filesystem is initialized
> and mounted, e.g. devtmpfs device filesystem.
>
> Or /dev/fb0 can be created by the user, but if it has been created
> by the user and there is no frame buffer driver running, then the
> driver interface cannot be opened since no corresponding driver
> responds when an application tries to open the device. This is
> the error message that you currently see.
>
> When you create the device node file under /dev at runtime, it will
> disappear when rebooting, since the device file system under /dev
> will be unmounted. Even if there is a /dev directory on your hard
> disk with some existing device nodes, e.g. fb0 existing, there
> is still a possibility that you won't see these nodes at runtime.
> If the kernel creates device system at runtime and it is mounted
> under /dev, the content of this device system will be populated
> with device nodes for registered devices. When there is no frame
> buffer driver loaded, no fb0 device will be registered, no device
> node will be created.
>
> Hope this helps,
>
> Anatolij
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-11-13 21:17 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
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 [this message]
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.1111132106180.2425@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