public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Kemi <jakob.kemi@telia.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.70 damaged my nvidia card?
Date: Wed, 28 May 2003 16:02:26 +0200	[thread overview]
Message-ID: <3ED4C172.9020904@telia.com> (raw)
In-Reply-To: <20030528132153.GA27632@suse.de>

Thanks for your fast reply,

Dave Jones wrote:
> On Wed, May 28, 2003 at 03:05:49PM +0200, Jakob Kemi wrote:
> 
>  > 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).
> 
> most (if not all) modern BIOS's have an "Init {AGP/PCI} display first"
> option. You may need to fiddle with that.

Of course, but should't the AGP bios report itself during initialization 
even when 'Init PCI display first' is set, or is the legacy BIOS 
completely ignored on the secondary adapter?

>  > 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?
> 
> Extremely unlikely. WRT agpgart, it pokes chipset registers, not
> graphic card registers.
> 
> It may even be that the two cards you have won't play together.
> Try them both _independantly_ before jumping to conclusions about
> wiped BIOSes etc.

The PCI card was installed afterwards to be able to use the computer at 
all since it now refuses to boot with the geforce card. I've tried to 
use the PCI card as the primary card and only use the geforce card with 
X to see if it'd work that way (which it didn't).

	/ Jakob Kemi


  reply	other threads:[~2003-05-28 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 13:05 2.5.70 damaged my nvidia card? Jakob Kemi
2003-05-28 13:21 ` Dave Jones
2003-05-28 14:02   ` Jakob Kemi [this message]
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=3ED4C172.9020904@telia.com \
    --to=jakob.kemi@telia.com \
    --cc=davej@codemonkey.org.uk \
    --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