From: n0ano@indstorage.com
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Problem about NVidia driver 1.0-2880 on Linux-ia64 kernel 2.4.18
Date: Sun, 12 May 2002 21:30:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905575@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905571@msgid-missing>
Yi-
Last I heard nVidia drivers for Linux consisted of source wrappers
around a binary only driver. Unless you can get nVidia to release
ALL of their driver source (extremely unlikely) or, alternatively, get
nVidia to rlease IA64 binaries you're pretty much out of luck.
On Sat, May 11, 2002 at 04:59:59PM +0800, Wang Yi wrote:
> There is no any mistake reported when build and install NVIDIA_kernel
> dirver and NVIDIA_GLX driver.
> glxinfo of XFree86 can provide corrent information after the new driver
> is installed.
> My OpenGL programs work well without recompilation.But when I rebuild
> them, the ld report
> /usr/lib/libGLcore.so.1: undefined reference to
> '__nvsym10421'
>
> The RedHat Linux for Itanium 7.1 installed on my machine has a version
> 2.4.3 kernel, which cannot match the requirement of the NVdriver. So I
> downloaded and installed the 2.4.18 kernel.
> I unpack linux kernel 2.4.18 at ~/linux and build it successfully. It
> works well also.
>
> when I build the NVIDIA_kernel driver, I use the following command :
> make SYSINCLUDE=~/linux/include
>
> I have tried several time to rebuild the driver. But the results are
> same.
Content-Description: Card for Wang Yi
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@indstorage.com
Ph: 303/652-0870x117
next prev parent reply other threads:[~2002-05-12 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-11 8:59 [Linux-ia64] Problem about NVidia driver 1.0-2880 on Linux-ia64 kernel 2.4.18 Wang Yi
2002-05-12 21:30 ` n0ano [this message]
2002-05-13 20:26 ` David Mosberger
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=marc-linux-ia64-105590701905575@msgid-missing \
--to=n0ano@indstorage.com \
--cc=linux-ia64@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