public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Kemi <jakob.kemi@telia.com>
To: linux-kernel@vger.kernel.org
Subject: 2.5.70 damaged my nvidia card?
Date: Wed, 28 May 2003 15:05:49 +0200	[thread overview]
Message-ID: <3ED4B42D.4040204@telia.com> (raw)

(please CC me as I'm not subscribed.)

Hi,

I have an VIA KT333 + Athlon box with an old, noname AGP GeForce 400 MX 
card.
Upon first booting 2.5.70 i noticed heavy screen flicker. (never seen 
with 2.4.x or 2.5.x < 2.5.70) it behaved nice once in X, upon the next 
reboot i did some work in the console (X not started). Still lots of 
flickering and a misplaced text cursor in text-mode. So i decided to go 
back to my old 2.4 kernel but was unable to boot since my BIOS no longer 
recognizes my graphics card.
When I run the box with an old PCI card as my primary adapter and the 
AGP geforce card as secondary the Geforce card doesnt seem to run it's 
VGA BIOS (no boot message). X also refuses to detect the Geforce card. 
Is it possible that the new console layer or the new agp gart code or 
whatever in 2.5.70 poked in the wrong registers and replaced the BIOS 
flash rom on the GeForce with garbage?
Of course it could very well be something else, but the fact that it 
happened _exactly_ when I switched kernel makes me suspicious.
Some googling reveals that the screen might flicker during flashing of 
the graphics BIOS on geforce cards. Unfortunately since I don't know the 
brand of my card I can't try to replace it's bios.
I should also add that the 2.5.70 build was without framebuffer and that 
other AGP graphic adapters still works in my computer and that my 
Geforce card also doesn't work in other machines.

Any ideas? How much does the kernel poke with the graphic card?

	/ Jakob Kemi


             reply	other threads:[~2003-05-28 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 13:05 Jakob Kemi [this message]
2003-05-28 13:21 ` 2.5.70 damaged my nvidia card? Dave Jones
2003-05-28 14:02   ` Jakob Kemi
2003-05-28 20:11   ` David Ford

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=3ED4B42D.4040204@telia.com \
    --to=jakob.kemi@telia.com \
    --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