public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jurriaan <thunder7@xs4all.nl>
To: Michal Semler <cijoml@volny.cz>
Cc: linux-kernel@vger.kernel.org, jsimmons@infradead.org,
	vandrove@vc.cvut.cz
Subject: Re: very buggy 3DFx framebuffer support!!! :(
Date: Sun, 9 Mar 2003 06:54:53 +0100	[thread overview]
Message-ID: <20030309055453.GA9064@middle.of.nowhere> (raw)
In-Reply-To: <E18rmiu-0000ew-00@notas>

From: Michal Semler <cijoml@volny.cz>
Date: Sat, Mar 08, 2003 at 11:23:18PM +0100
> Hello,
> 
> I found out very buggy 3DFx framebuffer support :(
> 
> when I select nothing when console bootings, I got white background under 
> Tux, rolling up with black background of text. Then everything under Tux has 
> black background and white text, but there, where is tux icon everything on 
> the right side of the icon has still white background
> 
> when I select in lilo 
> append="video=tdfx:1024x768-24@75"
> 
> my console gets screws up and I can't see anything under it. X windows but 
> works.
> 
> When I boot computer without append and then call it with fbset -a 
> 1024x768-75 things are the same ;( and I still can select Xwindows with alt+f7
> 
> Please can anybody fix this?
> 
> Linux 2.4.20 vanilla, gcc 3.0.4, Debian woody 3.0r1, 3DFx card, P3 733 
> Coppermine
> 
What 3dfx card? Output in log-files? Dmesg-output? output of 'dmesg' ?

Jurriaan
-- 
If Big Brother is watching you, stare back, he doesn't like it.
	Shannon
GNU/Linux 2.5.63 SMP/ReiserFS 3948 bogomips load av: 0.24 0.37 0.20

  reply	other threads:[~2003-03-09  5:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-08 22:23 very buggy 3DFx framebuffer support!!! :( Michal Semler
2003-03-09  5:54 ` Jurriaan [this message]
2003-03-09 11:19   ` Michal Semler
2003-03-09 11:22   ` Paolo Ornati

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=20030309055453.GA9064@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --cc=cijoml@volny.cz \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    /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