public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] resource mapping wrong? pci-x nvidia fails to load
Date: Tue, 14 Mar 2006 11:08:38 -0300	[thread overview]
Message-ID: <342e1090603140608xd9dc585s1e1593cf57c02435@mail.gmail.com> (raw)
In-Reply-To: <200603141437.56952.listjiro@gmail.com>

On 3/14/06, Jimmy Rosen <listjiro@gmail.com> wrote:
> Hi folks, perhaps someone can shed some light on this problem?
>
> nvidia driver fails to load. In dmesg I find this:
>
> nvidia: module license 'NVIDIA' taints kernel.
> ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:03:00.0 to 64
> NVRM: The IO regions for your NVIDIA card are invalid.
> NVRM: Your system BIOS may have misconfigured your graphics card.
> NVRM: bar1 (framebuffer) appears to be wrong: 0x0 0x0
> ACPI: PCI interrupt for device 0000:03:00.0 disabled
> nvidia: probe of 0000:03:00.0 failed with error -1
> NVRM: the NVIDIA probe routine was not called for 1 device(s)!!
> NVRM: no devices probed, aborting!
> NVRM: this often occurs when rivafb is loaded and claims the device's
> resources.
> NVRM: try removing the rivafb module (or reconfiguring your kernel to
> remove
> NVRM: rivafb support) and then try loading the NVIDIA kernel module
> again.

Have you tried doying what the module message told you to? Remove
rivafb from you kernel and then load the nvidia module.

>
> Now, this is an NVidia GeForce 6600 PCI-X card on an Intel SE7525RP2
> motherboard with 1GB ram. Kernel 2.6.15 gentoo sources r1, nvidia
> drivers nvidia-kernel 1.0.6629-r5 and nvidia-glx 1.0.6629-r6.
>
> According to what little I've found on the web, there seems to be
> something weird with bios? I've tried cmos clear, and restarting with
> all cards unplugged, but I can't get it to work.
> Some sites suggested there might be some bios settings left if the
> pci-x had been plugged in before the ram expansion, which was the
> case here.

I don't think its your BIOS, probably a imcompatibility between riva
framebuffer support and nvidia module. As I remember, you can use just
VESA for framebuffer and disable this specific framebuffer driver.
That might solve your problem.

--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-03-14 14:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14 13:37 [gentoo-user] resource mapping wrong? pci-x nvidia fails to load Jimmy Rosen
2006-03-14 13:58 ` Mike Williams
2006-03-14 14:08 ` Daniel da Veiga [this message]
2006-03-14 15:21   ` Jimmy Rosen
2006-03-15 12:00     ` Mike Williams
2006-03-15 13:18     ` Daniel da Veiga
2006-03-16  5:01 ` Richard Fish
2006-03-16 14:49   ` Jimmy Rosen

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=342e1090603140608xd9dc585s1e1593cf57c02435@mail.gmail.com \
    --to=danieldaveiga@gmail.com \
    --cc=gentoo-user@lists.gentoo.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