From: Tom Gundersen <teg@jklm.no>
To: linux-fbdev@vger.kernel.org
Subject: Re: [BUG] simplefb not showing any output
Date: Fri, 06 Sep 2013 17:12:51 +0000 [thread overview]
Message-ID: <CAG-2HqXbjMFRtRWvB4awGO2f_iJwAg6ZKHga7dcYuQPyO9b=YA@mail.gmail.com> (raw)
In-Reply-To: <CAG-2HqXhLcRX-oi4JchD=m7tZpDYyePKhWvkFU1ZZPEuqJ2JqQ@mail.gmail.com>
On Fri, Sep 6, 2013 at 6:57 PM, David Herrmann <dh.herrmann@gmail.com> wrote:
> ( 2 more mails and you might get the fbdev ML right ;) )
Modern technology...
> - Is CONFIG_FB_EFI enabled? If not, please enable it and try again
> (hint: CONFIG_FB_VESA doesn't hurt either)
FB_EFI was enabled, FB_VESA was not, but I'll enable it. Out of
interest, how could this affect the situation? If I understand
correctly these drivers won't be loaded as long as simple-framebuffer
is created, or am I missing something?
> - Could you try the _same_ kernel config but disable CONFIG_X86_SYSFB.
> This will avoid creating simple-fb devices and instead load efifb
> again. Does efifb work? Does efifb print the same offsets as your
> simplefb printk()?
Yeah, efifb works fine, I'll double-check everything and note down the offsets.
> - Are you sure that it's an simplefb problem? Please make sure fbcon
> is enabled (could you attach your dmesg output?). You could also try
> SSH'ing into the machine and starting some fbdev program (like X with
> xf86-video-fbdev installed). Or does fbcon with efifb work?
fbcon with efifb works fine (so I guess trying X is not necessary?).
Cheers,
Tom
next prev parent reply other threads:[~2013-09-06 17:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 16:14 [BUG] simplefb not showing any output Tom Gundersen
2013-09-06 16:57 ` David Herrmann
2013-09-06 17:12 ` Tom Gundersen [this message]
2013-09-06 17:19 ` David Herrmann
2013-09-06 17:46 ` Tom Gundersen
2013-09-07 11:47 ` Tom Gundersen
2013-09-07 12:25 ` David Herrmann
2013-09-07 13:02 ` Tom Gundersen
2013-09-09 2:36 ` Alexandre Courbot
2013-09-09 2:40 ` Alexandre Courbot
2013-09-09 9:46 ` David Herrmann
2013-09-09 15:47 ` Stephen Warren
2013-09-10 2:34 ` Stephen Warren
2013-10-02 15:01 ` David Herrmann
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='CAG-2HqXbjMFRtRWvB4awGO2f_iJwAg6ZKHga7dcYuQPyO9b=YA@mail.gmail.com' \
--to=teg@jklm.no \
--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).