From: James Simmons <jsimmons@infradead.org>
To: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: neofb problems with 2.6.0-test1-ac3 etc. -- kernel-2.6.x ignoramus
Date: Tue, 29 Jul 2003 18:09:04 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0307291807490.5874-100000@phoenix.infradead.org> (raw)
In-Reply-To: <20030726124907.GB22804@charite.de>
> This is my framebuffer. It works, but switching back and forth between
> X11 and the fbconsole totally trashes the framebuffer.
>
> fbset -depth 16
>
> fixes things again. To see what I see, look at:
> http://sbserv.stahl.bau.tu-bs.de/~hildeb/fbfubar/
This is because the X server is not fbdev aware. Try adding the UseFBDev
option in your XF86Config. That shoudl fix your problems.
next prev parent reply other threads:[~2003-07-29 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 12:49 neofb problems with 2.6.0-test1-ac3 etc. -- kernel-2.6.x ignoramus Ralf Hildebrandt
2003-07-29 17:09 ` James Simmons [this message]
2003-07-29 20:37 ` Ralf Hildebrandt
2003-07-29 21:31 ` James Simmons
2003-07-30 5:09 ` Ralf Hildebrandt
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=Pine.LNX.4.44.0307291807490.5874-100000@phoenix.infradead.org \
--to=jsimmons@infradead.org \
--cc=Ralf.Hildebrandt@charite.de \
--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;
as well as URLs for NNTP newsgroup(s).