From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: krose+linux-kernel@krose.org
Cc: ken@krwtech.com, linux-kernel@vger.kernel.org
Subject: Re: NVIDIA proprietary driver problem
Date: Fri, 12 Sep 2003 18:28:12 +0200 [thread overview]
Message-ID: <20030912162812.GA10942@vana.vc.cvut.cz> (raw)
In-Reply-To: <Pine.LNX.4.56.0309121023440.973@death>
On Fri, Sep 12, 2003 at 10:29:43AM -0400, Ken Witherow wrote:
> On Fri, 12 Sep 2003, Kyle Rose wrote:
>
> > > What motherboard is it?
> >
> > Tyan Tiger MP, dual Athlon MP 1800's.
>
> I've got the same motherboard and processors with a GF4 MX420
>
> I'm running 2.6.0-test5 with the 4496 drivers with the patches from
> minion.de without any problems.
>
> Sep 9 00:06:08 death kernel: nvidia: no version magic, tainting kernel.
> Sep 9 00:06:08 death kernel: nvidia: module license 'NVIDIA' taints
> kernel.
> Sep 9 00:06:08 death kernel: 1: nvidia: loading NVIDIA Linux x86 nvidia.o
> Kernel Module 1.0-4496 Wed Jul 16 19:03:09 PDT 2003
BIOS has setting whether IRQ should be assigned to the VGA card
or not - default is not, and if you'll leave it this way, you'll get
no IRQ:
platan:~# lspci -s 0:0e.0 -vb
00:0e.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Rage XL
Flags: bus master, stepping, medium devsel, latency 66, IRQ 255
Memory at 51000000 (32-bit, non-prefetchable)
I/O ports at 1000
Memory at 50001000 (32-bit, non-prefetchable)
Capabilities: [5c] Power Management version 2
If you'll change BIOS's setting, your Nvidia (or vsync code on matroxfb) should
work.
Petr Vandrovec
next prev parent reply other threads:[~2003-09-12 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 13:44 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 [this message]
2003-09-12 17:11 ` Kyle Rose
2003-09-12 15:37 ` Samuel Flory
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=20030912162812.GA10942@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=ken@krwtech.com \
--cc=krose+linux-kernel@krose.org \
--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
all inboxes | Powered by JetHome®