I'm trying to use the NVIDIA driver so I can play NWN and some other
games which won't run with the stock XFree (xserver-xfree86_4.3.0-5)
driver. When I run "make" in the NVIDIA_kernel directory I get alot of
undefined variables:
/lib/modules/2.6.4/build/include/asm/mpspec.h:20: error: `MAX_MP_BUSSES' undeclared here (not in a function)
/lib/modules/2.6.4/build/include/asm/mpspec.h:20: error: conflicting types for `mp_bus_id_to_type'
/lib/modules/2.6.4/build/include/asm/mpspec.h:8: error: previous declaration of `mp_bus_id_to_type'
/lib/modules/2.6.4/build/include/asm/mpspec.h:22: error: `MAX_IRQ_SOURCES' undeclared here (not in a function)
/lib/modules/2.6.4/build/include/asm/mpspec.h:24: error: `MAX_MP_BUSSES' undeclared here (not in a function)
/lib/modules/2.6.4/build/include/asm/mpspec.h:24: error: conflicting types for `mp_bus_id_to_pci_bus'
/lib/modules/2.6.4/build/include/asm/mpspec.h:12: error: previous declaration of `mp_bus_id_to_pci_bus'
/lib/modules/2.6.4/build/include/asm/mpspec.h:50: error: `MAX_APICS' undeclared here (not in a function)
And that's just for starters. Does anyone know if there's a way to get
this to compile cleanly or is it SoL until a new driver is released
(running 1.0.4191 currently).
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Life is not a destination, it's a journey.
Microsoft produces 15 car pileups on the highway.
Don't stop traffic to stand and gawk at the tragedy.
On Thu, 11 Mar 2004 07:31:00 -0500 "Robert L. Harris" <[email protected]> wrote:
> And that's just for starters. Does anyone know if there's a way to get
> this to compile cleanly or is it SoL until a new driver is released
> (running 1.0.4191 currently).
At least for x86 the latest driver (1.0-5336) is compatible with 2.6.x
(didn't test on 2.6.4 though).
Regards,
Nerijus
Robert L. Harris wrote:
> And that's just for starters. Does anyone know if there's a way to get
> this to compile cleanly or is it SoL until a new driver is released
> (running 1.0.4191 currently).
Get the new driver http://www.nvidia.com/object/linux.html Quite a few have
been released since 1.0.4191, in fact you're running the driver that was
released December 11, 2002, try an update ;)
On Thu, 11 Mar 2004 15:07:03 +0200 (EET)
Nerijus Baliunas <[email protected]> bubbled:
> On Thu, 11 Mar 2004 07:31:00 -0500 "Robert L. Harris"
> <[email protected]> wrote:
>
> > And that's just for starters. Does anyone know if there's a way to get
> > this to compile cleanly or is it SoL until a new driver is released
> > (running 1.0.4191 currently).
>
> At least for x86 the latest driver (1.0-5336) is compatible with 2.6.x
> (didn't test on 2.6.4 though).
nvidia 5336 works with 2.6.4 here. (but it has a basic sysfs patch
applied by gentoo)
Regards,
Martin
--
MyExcuse:
kernel panic: write-only-memory (/dev/wom0) capacity exceeded.
Martin Zwickel <[email protected]>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
On Thursday 11 March 2004 12:31, Robert L. Harris wrote:
[snip]
> And that's just for starters. Does anyone know if there's a way to get
> this to compile cleanly or is it SoL until a new driver is released
> (running 1.0.4191 currently).
Alternatively, pop along to http://minion.de/, where you can still pick up 2.6
patches for older drivers (we recognise that for some people, the newest
drivers break things).
--
Cheers,
Alistair.
personal: alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student: CS/AI Undergraduate
contact: 7/10 Darroch Court,
University of Edinburgh.
Yeah, went poking around the website and found the link up there. I've
always just used the ftpsite out of habit. gonna go bang my head on a
desk now.
Thus spake Dennis Bliefernicht ([email protected]):
> Robert L. Harris wrote:
> >And that's just for starters. Does anyone know if there's a way to get
> >this to compile cleanly or is it SoL until a new driver is released
> >(running 1.0.4191 currently).
> Get the new driver http://www.nvidia.com/object/linux.html Quite a few have
> been released since 1.0.4191, in fact you're running the driver that was
> released December 11, 2002, try an update ;)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
> ** CRM114 Whitelisted by: [email protected] **
>
> ** ACCEPT: CRM114 Whitelisted by: [email protected] **
>
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Life is not a destination, it's a journey.
Microsoft produces 15 car pileups on the highway.
Don't stop traffic to stand and gawk at the tragedy.
I tried 5336 with 2.6.4-rc2-mm1 and it locks the box up completely after
switching to kdm. It worked with 2.6.3-mm4 previously, now even that
kernel gets a lock up. I've done a reiserfsck --rebuild-tree which
repaired some files and left 10 files in /lost+found and I can't
determine what they are.
I am currently using 2.6.4-rc2-mm1 with the standard SuSE 9.0 Driver "nv".
I also went back to the minion.de release and still got a lockup, I
guess it's down to some of those files in lost+found that are missing.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
That's weird:
uname -a
Linux garaged 2.6.4-rc2-mm1 #1 SMP Wed Mar 10 20:27:04 CST 2004 i686 Intel(R)
Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
$ lsmod | grep nv
nvidia 2075144 12
Running KDE, using kdm, with nvidia module, no problem, I notice a slight
difference on fonts, but I dont know if it's my imagination.
Been using nvidia modules for quite a few 2.6.x kernels, most of them mmX.
without problems
Max
--
Linux garaged 2.6.3-mm3 #2 SMP Tue Feb 24 15:44:58 CST 2004 i686 Intel(R)
Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GS/S d- s: a-29 C++(+++) ULAHI+++ 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+ z**
------END GEEK CODE BLOCK------
gpg-key: http://garaged.homeip.net/gpg-key.txt
Max Valdez wrote:
>That's weird:
>uname -a
>Linux garaged 2.6.4-rc2-mm1 #1 SMP Wed Mar 10 20:27:04 CST 2004 i686 Intel(R)
>Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
>
>$ lsmod | grep nv
>nvidia 2075144 12
>
>
>Running KDE, using kdm, with nvidia module, no problem, I notice a slight
>difference on fonts, but I dont know if it's my imagination.
>
>Been using nvidia modules for quite a few 2.6.x kernels, most of them mmX.
>without problems
>
>Max
>
>
Something strange happened, I shall try 2.6.4-mm1 shortly to see if it
is still the same. I reckon though that I've suffered a filesystem
corruption.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
In a futile gesture against entropy, Sid Boyce wrote:
> Max Valdez wrote:
> >Been using nvidia modules for quite a few 2.6.x kernels, most of them mmX.
> >without problems
I'm using it here with 2.6.4, no problems as yet.
> Something strange happened, I shall try 2.6.4-mm1 shortly to see if it
> is still the same. I reckon though that I've suffered a filesystem
> corruption.
A quick thought - have you got CONFIG_REGPARM enabled in the kernel
config? If so, disable it and try again. (It's almost certain to
cause crashes with binary modules.)
--
Adam Jones ([email protected])(http://www.yggdrasl.demon.co.uk/)
.oO("Hizbollah Central Press Office" )
PGP public key: http://www.yggdrasl.demon.co.uk/pubkey.asc
on x86 all nvidia driver will compile and run with 2.6 kernels using nimion
patches.
nvidia driver on 2.6.4 won't run if you compile the kernel with
-mregparm=3 (CONFIG_REGPARM enabled). Then you will get the most wonderfull oops
of your life.
bests
Luigi
On Thu, 11 Mar 2004, Nerijus Baliunas wrote:
> Date: Thu, 11 Mar 2004 15:07:03 +0200 (EET)
> From: Nerijus Baliunas <[email protected]>
> To: Robert L. Harris <[email protected]>
> Cc: Linux-Kernel <[email protected]>
> Subject: Re: NVIDIA and 2.6.4?
>
> On Thu, 11 Mar 2004 07:31:00 -0500 "Robert L. Harris" <[email protected]> wrote:
>
> > And that's just for starters. Does anyone know if there's a way to get
> > this to compile cleanly or is it SoL until a new driver is released
> > (running 1.0.4191 currently).
>
> At least for x86 the latest driver (1.0-5336) is compatible with 2.6.x
> (didn't test on 2.6.4 though).
>
> Regards,
> Nerijus
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Adam Jones wrote:
>In a futile gesture against entropy, Sid Boyce wrote:
>>/ Max Valdez wrote:/
>>/ >Been using nvidia modules for quite a few 2.6.x kernels, most of
them mmX. /
>>/ >without problems/
>I'm using it here with 2.6.4, no problems as yet.
>>/ Something strange happened, I shall try 2.6.4-mm1 shortly to see if
it /
>>/ is still the same. I reckon though that I've suffered a filesystem /
>>/ corruption./
> A quick thought - have you got CONFIG_REGPARM enabled in the kernel
> config? If so, disable it and try again. (It's almost certain to
> cause crashes with binary modules.)
I haven't had CONFIG_REGPARM set in any of the kernels. 2.6.4-rc2-mm1
was fine until after I first booted 2.6.4-mm1, then neither would work
with nvidia. I also got some strange stuff happening, including checksum
errors on the driver and I had to download it again from nvidia.com on
two occasions, the first redownload reinstalled once, then chksum
errors, the second redownload did the same as well as chksum
segfaulting, since then it's been fine. See also the garbage I get out
of vi in an earlier posting.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
Sid Boyce wrote:
> Adam Jones wrote:
> >In a futile gesture against entropy, Sid Boyce wrote:
> >>/ Max Valdez wrote:/
>
> >>/ >Been using nvidia modules for quite a few 2.6.x kernels, most of
> them mmX. /
> >>/ >without problems/
>
> >I'm using it here with 2.6.4, no problems as yet.
>
> >>/ Something strange happened, I shall try 2.6.4-mm1 shortly to see
> if it /
> >>/ is still the same. I reckon though that I've suffered a filesystem /
> >>/ corruption./
>
> > A quick thought - have you got CONFIG_REGPARM enabled in the kernel
> > config? If so, disable it and try again. (It's almost certain to
> > cause crashes with binary modules.)
> I haven't had CONFIG_REGPARM set in any of the kernels. 2.6.4-rc2-mm1
> was fine until after I first booted 2.6.4-mm1, then neither would work
> with nvidia. I also got some strange stuff happening, including
> checksum errors on the driver and I had to download it again from
> nvidia.com on two occasions, the first redownload reinstalled once,
> then chksum errors, the second redownload did the same as well as
> chksum segfaulting, since then it's been fine. See also the garbage I
> get out of vi in an earlier posting.
> Regards
> Sid.
>
*** CORRECTION *** 2.6.4-rc2-mm1 is the one that caused the trouble as
stated in the first post. I'm yet to boot up 2.6.4-mm1.
Some of the files in lost+found seem to be kde settings which I noticed
were missing and had to setup again.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
On Fri, 12 Mar 2004 18:24:01 GMT, Adam Jones <[email protected]> said:
> In a futile gesture against entropy, Sid Boyce wrote:
> > Max Valdez wrote:
>
> > >Been using nvidia modules for quite a few 2.6.x kernels, most of them mmX.
> > >without problems
>
> I'm using it here with 2.6.4, no problems as yet.
>
> > Something strange happened, I shall try 2.6.4-mm1 shortly to see if it
> > is still the same. I reckon though that I've suffered a filesystem
> > corruption.
>
> A quick thought - have you got CONFIG_REGPARM enabled in the kernel
> config? If so, disable it and try again. (It's almost certain to
> cause crashes with binary modules.)
Also, the NVidia driver uses a bit of kernel stack, so it's incompatible
with the CONFIG_4KSTACKS option in recent -mm kernels...
Valdis . Kletnieks wrote:
> On Fri, 12 Mar 2004 18:24:01 GMT, Adam Jones
<adam@xxxxxxxxxxxxxxxxxxxx> said:
>>/ In a futile gesture against entropy, Sid Boyce wrote:/
>>/ > Max Valdez wrote:/
>>/ /
>>/ > >Been using nvidia modules for quite a few 2.6.x kernels, most of
them mmX./
>>/ > >without problems/
>/> /
>>/ I'm using it here with 2.6.4, no problems as yet./
>>/ /
>>/ > Something strange happened, I shall try 2.6.4-mm1 shortly to see
if it /
>>/ > is still the same. I reckon though that I've suffered a filesystem /
>>/ > corruption./
>>/ /
>>/ A quick thought - have you got CONFIG_REGPARM enabled in the kernel/
>>/ config? If so, disable it and try again. (It's almost certain to/
>>/ cause crashes with binary modules.)/
> Also, the NVidia driver uses a bit of kernel stack, so it's incompatible
> with the CONFIG_4KSTACKS option in recent -mm kernels...
I have that enabled, so I shall turn it off. /var/log/XFree86.0.log
shows it's getting so far then the lockup happens.
(==) ModulePath set to "/usr/X11R6/lib/modules"
(**) Option "AllowMouseOpenFail"
(**) Option "Xinerama" "off"
(**) Option "RandR" "on"
(++) using VT number 7
(WW) Open APM failed (/dev/apm_bios) (No such device)
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.2
XFree86 Video Driver: 0.6
XFree86 XInput driver : 0.4
XFree86 Server Extension : 0.2
XFree86 Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
On Monday 15 March 2004 04:36, Steve Youngs wrote:
> * Valdis Kletnieks <[email protected]> writes:
> > On Fri, 12 Mar 2004 18:24:01 GMT, Adam Jones <[email protected]>
said:
> >> A quick thought - have you got CONFIG_REGPARM enabled in the kernel
> >> config? If so, disable it and try again. (It's almost certain to
> >> cause crashes with binary modules.)
>
> $ zgrep REGPARM /proc/config.gz
> CONFIG_REGPARM=y
>
> $ grep nvidia /proc/modules
> nvidia 2066568 22 - Live 0xe0b2d000
>
> $ uname -r
> 2.6.4-sy1
>
> No problems here. :-)
>
> > Also, the NVidia driver uses a bit of kernel stack, so it's
> > incompatible with the CONFIG_4KSTACKS option in recent -mm
> > kernels...
>
> Will have to remember that for 2.6.5, I'll let you know how it goes.
> Thanks, Valdis.
can you let me know how to compile the nvidia drivers for 4KSTACK? cause in
the 2.6.5-rc1-mm1 is no more option to deactivate 4KSTACK.
thx!
greets
Dominik Karall wrote:
> On Monday 15 March 2004 04:36, Steve Youngs wrote:
>
>>* Valdis Kletnieks <[email protected]> writes:
>> > On Fri, 12 Mar 2004 18:24:01 GMT, Adam Jones <[email protected]>
>
> said:
>
>> >> A quick thought - have you got CONFIG_REGPARM enabled in the kernel
>> >> config? If so, disable it and try again. (It's almost certain to
>> >> cause crashes with binary modules.)
>>
>> $ zgrep REGPARM /proc/config.gz
>>CONFIG_REGPARM=y
>>
>> $ grep nvidia /proc/modules
>>nvidia 2066568 22 - Live 0xe0b2d000
>>
>> $ uname -r
>>2.6.4-sy1
>>
>>No problems here. :-)
>>
>> > Also, the NVidia driver uses a bit of kernel stack, so it's
>> > incompatible with the CONFIG_4KSTACKS option in recent -mm
>> > kernels...
>>
>>Will have to remember that for 2.6.5, I'll let you know how it goes.
>>Thanks, Valdis.
>
>
> can you let me know how to compile the nvidia drivers for 4KSTACK? cause in
> the 2.6.5-rc1-mm1 is no more option to deactivate 4KSTACK.
> thx!
Complain to NVidia. It's the binary-only part of the driver that's the
real stack hog.
--
Brian Gerst
On Tue, 16 Mar 2004 21:49:40 +0100, Dominik Karall <[email protected]> said:
> can you let me know how to compile the nvidia drivers for 4KSTACK? cause in
> the 2.6.5-rc1-mm1 is no more option to deactivate 4KSTACK.
Get the 2.6.5-rc1-mm1-broken-out.tar.bz2, untar it, then
patch -p1 -R < broken-out/4k-stacks-always-on.patch
Yes, the *right* thing would be for NVidia to fix the binary. However, this
is a lot more expedient than waiting. :)
On Tuesday 16 March 2004 22:19, you wrote:
> On Tue, 16 Mar 2004 21:49:40 +0100, Dominik Karall <[email protected]>
said:
> > can you let me know how to compile the nvidia drivers for 4KSTACK? cause
> > in the 2.6.5-rc1-mm1 is no more option to deactivate 4KSTACK.
>
> Get the 2.6.5-rc1-mm1-broken-out.tar.bz2, untar it, then
>
> patch -p1 -R < broken-out/4k-stacks-always-on.patch
>
> Yes, the *right* thing would be for NVidia to fix the binary. However,
> this is a lot more expedient than waiting. :)
thx, works now with 8k stack size :)
greets