From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Zoup <Zoup@zoup.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Frame Buffer Problem .
Date: Tue, 9 Sep 2003 12:19:05 +0200 [thread overview]
Message-ID: <C89A06A7261@vcnet.vc.cvut.cz> (raw)
On 9 Sep 03 at 13:37, Zoup wrote:
> got blank screen when enable Frame Buffer console on 2.6.0-test5 :)
> Config file attached .
Do not enable vga16, vesafb and riva together. Decided for only one
of them, and use just that one. Although your configuration should give
you /dev/fb0 on riva, /dev/fb1 on vesafb and /dev/fb2 on vga16,
it looks like that you got reordered framebuffers somehow. Did not you
pass 'video=vga16fb:XXXX' option to the kernel? What kernel cmdline you
used?
Other possibility is that vga16 setup confused your hardware enough for
picture to disappear... Doing 'cat /proc/fb > /non-working-fbs;
dmesg >> /non-working-fbs' after you boot your system with non-working
display could give us clue what's going on. But in any case, do not use
more than one fbdev...
Petr Vandrovec
next reply other threads:[~2003-09-09 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 10:19 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-09 9:07 Frame Buffer Problem Zoup
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=C89A06A7261@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=Zoup@zoup.org \
--cc=linux-kernel@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