From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: Getting FB to work in Console
Date: Sun, 13 Nov 2011 21:44:14 +0000 [thread overview]
Message-ID: <20111113224414.5ee64c2c@neptune.home> (raw)
In-Reply-To: <CADO5RbhunU1X7mWwGDbVRc1FSPKBaLudAVav0TMkBoQ_1zp0Mw@mail.gmail.com>
On Sun, 13 November 2011 Anatolij Gustschin <agust@denx.de> wrote:
> On Sun, 13 Nov 2011 21:16:52 -0500 (EST)
> David J Ring Jr <n1ea@arrl.net> wrote:
>
> > OK so how do I get a frame buffer driver loaded?
>
> Check if some frame buffer drivers are installed
> in your system, so e.g. run
>
> ls /lib/modules/`uname -r`/kernel/drivers/video
>
> to see if there are any frame buffer driver modules
> installed.
>
> Then you have to select the suitable driver for your
> graphic card and load it by running
>
> modprobe drivername
>
> > 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?
>
>
> Usually the driver should be loaded automatically if
> it is installed. Maybe some error happened while loading
> the driver. Dump the kernel log messages by running dmesg
> and check if there was an attempt to load the driver for
> your graphic card.
The other case might be a mainsteam GPU (radeon, nouveau, intel) and
KMS support built in (or available as module) but disabled by "nomodeset"
cmdline option that did show up in a previous post.
Just booting with "vga=0x31a" (or another value more appropriate for
attached screen -- see Documentation/fb/vesafb.txt for list) might
provide a basic framebuffer device.
lspci for the affected system will certainly help at least indicating
which driver would be the right one.
Bruno
next prev parent reply other threads:[~2011-11-13 21:44 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
2011-11-13 21:21 ` David J Ring Jr
2011-11-13 21:39 ` Anatolij Gustschin
2011-11-13 21:44 ` Bruno Prémont [this message]
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=20111113224414.5ee64c2c@neptune.home \
--to=bonbons@linux-vserver.org \
--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;
as well as URLs for NNTP newsgroup(s).