linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Henriksson <andreas@fjortis.info>
To: James Simmons <jsimmons@infradead.org>
Cc: Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [FBDEV BK] Updates and fixes.
Date: Tue, 15 Apr 2003 22:04:37 +0200	[thread overview]
Message-ID: <20030415200437.GA13773@gem> (raw)
In-Reply-To: <Pine.LNX.4.44.0304152004350.8236-100000@phoenix.infradead.org>

On Tue, Apr 15, 2003 at 08:21:43PM +0100, James Simmons wrote:
> > 	nVidia Corporation NV11 [GeForce2 MX] (rev b2)
> > 
> > this seems to work OK.  The penguins initially have a white background, then
> > the background goes black, then they go away.  Perhaps that is intentional. 
> > But it gets to a readable login prompt.
> 
> That is the stable code. As for the white background that is strange.
> 

This happens for me too (white background that goes away when there
eventually is text that hits that area and overwrites it). 
2.5.67 + extra stuff from bk + pnp + fbdev from april 11 with an Intel 8xx
integrated card.

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset Graphics Controller] (rev 02)

I also have an additional problem, the whole picture jumps slightly up
and down all the time, plus I have a thin corruptionline from side to
side that walks up and down on the screen. Like an old tv.

My lilo.conf append line looks like this:
append="video=i810fb:xres:1024,yres:768,bpp:16,hsync1:30,hsync2:82, \
vsync1:50,vsync2:75,accel"

I've tried several different modes but they all appear to give about the
same effect.

... and I'm using a TFT screen (ViewSonic ViewPanel VG181), if that
matters (not using DVI though).

At the same time I installed the 2.5 kernel I also upgraded to XFree86
4.2.1 (from 4.1, the default in debian woody) and the exact same
behaviour happened in X too (jumping slightly up and down, thin line of
corruption and I couldn't get the xvideo extension to show anything but
a blue screen in programs that used xv. [mplayer]). It all went away
when I upgraded to XFree86 4.3. Don't know if that'll help you any but I
thought it's better to mention it all.


I'll try a new kernel (with a newer fbdev patch) as soon as the dust
settles. If you want me to try out any special patch or kernel version
tell me and I'll do it as soon as I can.


Regards,
Andreas Henriksson

  reply	other threads:[~2003-04-15 19:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14  4:47 [FBDEV BK] Updates and fixes James Simmons
2003-04-14  7:58 ` Andrew Morton
2003-04-14  8:53   ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-04-15 19:25     ` James Simmons
2003-04-15 19:21   ` James Simmons
2003-04-15 20:04     ` Andreas Henriksson [this message]
2003-04-16  6:20     ` [Linux-fbdev-devel] " Geert Uytterhoeven
2003-04-14 19:15 ` Linus Torvalds
2003-04-15 19:49   ` James Simmons
2003-04-23 16:32 ` Pavel Machek

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=20030415200437.GA13773@gem \
    --to=andreas@fjortis.info \
    --cc=akpm@digeo.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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).