From: Christian Hesse <christian.hesse@linuxob.de>
To: linux-kernel@vger.kernel.org
Cc: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
Subject: Re: FB: vesafb garbled after using X11 with nv driver
Date: Thu, 11 Nov 2004 23:31:00 +0100 [thread overview]
Message-ID: <200411112331.05405.christian.hesse@linuxob.de> (raw)
In-Reply-To: <20041111215530.GB24338@charite.de>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Thursday 11 November 2004 22:55, Ralf Hildebrandt wrote:
> I use the nv driver in XFree and the vesafb for the framebuffer console.
> vesafb works fine, I get the bootlogo and all during boot.
>
> Once X11 starts up and I want to switch back to the framebuffer
> console using CTRL-ALT-F1, the framebuffer is garbled. The screen is
> flickering, as if the vertical synchronisation is lost. Colors seem to
> be OK, I get grey garbage on black background.
>
> Switching back to X11 using ALT-F7 works OK, the X11 screen looks fine.
>
> I made two screenshots to illuminate what I'm seeing:
> http://www.stahl.bau.tu-bs.de/~hildeb/bugreport/dsc02089.jpg
> http://www.stahl.bau.tu-bs.de/~hildeb/bugreport/dsc02090.jpg
> (watch out, high resolution)
>
> It's not entirely clear if it's an issue of the nv driver or the vesafb
> in the kernel.
I have a similar problem. With open source nv and vesafb the virtual terminal
looks like this if I switch back to the framebuffer:
http://linux.eworm.net/nv_offset.jpg
Everything is moved to the left, the right area is repeated some time and
fills the rest of the screen.
As binary nvidia module works without this problem I support it's a problem of
nv...
--
Christian Hesse
geek by nature
linux by choice
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2004-11-11 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 21:55 FB: vesafb garbled after using X11 with nv driver Ralf Hildebrandt
2004-11-11 22:31 ` Christian Hesse [this message]
2004-11-11 22:34 ` 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=200411112331.05405.christian.hesse@linuxob.de \
--to=christian.hesse@linuxob.de \
--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