From: Samuel Flory <sflory@rackable.com>
To: Kyle Rose <krose+linux-kernel@krose.org>
Cc: Maciej Soltysiak <solt@dns.toxicfilms.tv>, linux-kernel@vger.kernel.org
Subject: Re: NVIDIA proprietary driver problem
Date: Fri, 12 Sep 2003 08:37:05 -0700 [thread overview]
Message-ID: <3F61E821.6070209@rackable.com> (raw)
In-Reply-To: <87r82mf6j9.fsf@nausicaa.krose.org>
Kyle Rose wrote:
> Maciej Soltysiak <solt@dns.toxicfilms.tv> writes:
>
>
>>>Sep 11 23:37:57 nausicaa kernel: 0: nvidia: Can't find an IRQ for your NVIDIA card!
>>>Sep 11 23:37:57 nausicaa kernel: 0: nvidia: Please check your BIOS settings.
>>>Sep 11 23:37:57 nausicaa kernel: 0: nvidia: [Plug & Play OS ] should be set to NO
>>
>>I wonder why pnp os should be off?
>>Linux does support pnp, and is a pnp os. Isn't it?
>>
>>Have you tried disabling apic? Maybe it's an apic or irq routing bug?
>
>
> SMP without APIC doesn't make sense, but I suppose I could try running
> a non-SMP kernel to see if the problem goes away. Still, APIC is
> active in test4 and the driver works there.
Try without ACPI support. At boot do acpi=off.
>
>
>>What motherboard is it?
>
>
> Tyan Tiger MP, dual Athlon MP 1800's.
>
> Cheers,
> Kyle
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
prev parent reply other threads:[~2003-09-12 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 13:44 NVIDIA proprietary driver problem Kyle Rose
2003-09-12 13:54 ` Maciej Soltysiak
2003-09-12 14:03 ` Kyle Rose
2003-09-12 14:29 ` Ken Witherow
2003-09-12 16:28 ` Petr Vandrovec
2003-09-12 17:11 ` Kyle Rose
2003-09-12 15:37 ` Samuel Flory [this message]
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=3F61E821.6070209@rackable.com \
--to=sflory@rackable.com \
--cc=krose+linux-kernel@krose.org \
--cc=linux-kernel@vger.kernel.org \
--cc=solt@dns.toxicfilms.tv \
/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