From: Marc Koschewski <marc@osknowledge.org>
To: Chris Boot <bootc@bootc.net>
Cc: Marc Koschewski <marc@osknowledge.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-rc2-mm1 problems
Date: Thu, 24 Nov 2005 12:04:37 +0100 [thread overview]
Message-ID: <20051124110435.GA13110@stiffy.osknowledge.org> (raw)
In-Reply-To: <43859B03.5000302@bootc.net>
* Chris Boot <bootc@bootc.net> [2005-11-24 10:50:43 +0000]:
> Marc Koschewski wrote:
> >* Chris Boot <bootc@bootc.net> [2005-11-23 23:45:49 +0000]:
> >
> >
> >>On another note, I can't get the binary nVidia drivers to work, they
> >>complain about the following unresolved symbols:
> >>
> >>[4294682.396000] nvidia: module license 'NVIDIA' taints kernel.
> >>[4294682.396000] nvidia: Unknown symbol pci_enable_device
> >>[4294682.396000] nvidia: Unknown symbol pci_dev_put
> >>[4294682.396000] nvidia: Unknown symbol pci_get_device
> >>[4294682.396000] nvidia: Unknown symbol __pci_register_driver
> >>[4294682.396000] nvidia: Unknown symbol pci_bus_write_config_byte
> >>[4294682.396000] nvidia: Unknown symbol pci_unregister_driver
> >>[4294682.396000] nvidia: Unknown symbol pci_bus_read_config_dword
> >>[4294682.396000] nvidia: Unknown symbol pci_bus_read_config_word
> >>[4294682.396000] nvidia: Unknown symbol pci_bus_write_config_dword
> >>[4294682.397000] nvidia: Unknown symbol pci_set_master
> >>[4294682.397000] nvidia: Unknown symbol pci_bus_write_config_word
> >>[4294682.397000] nvidia: Unknown symbol pci_get_class
> >>[4294682.397000] nvidia: Unknown symbol pci_disable_device
> >>[4294682.397000] nvidia: Unknown symbol pci_bus_read_config_byte
> >>
> >
> >
> >http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14
>
> Hi there,
>
> Thanks for that link, although I'm not sure exactly what you're pointing
> me at. I discovered last night (too late for me to post to LKML) that it
> was caused by a funny patch by Greg KH to mark most of the PCI symbols
> as EXPORT_SYMBOL_GPL. Once backed out it works fine. Go figure.
>
The nvidia module's problem should probably dicussed somewhere else as well
as should any out-of-kernel-tree module's probs. You won't get much
attention here ...
Marc
prev parent reply other threads:[~2005-11-24 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 23:45 2.6.15-rc2-mm1 problems Chris Boot
2005-11-24 10:45 ` Marc Koschewski
2005-11-24 10:50 ` Chris Boot
2005-11-24 11:04 ` Marc Koschewski [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=20051124110435.GA13110@stiffy.osknowledge.org \
--to=marc@osknowledge.org \
--cc=bootc@bootc.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.