It is strange... X should automatically load the nVidia driver when it
needs it.
All modules which are auto-loaded are loaded via /etc/modules.conf
You need to set that up correctly, your system configuration program
program should do it for you. If it doesn't, use a text editor. It'll be
Chris Wilkinson wrote:
Would it be safe to add the insmod
command to rc.local or similar?
Thats exactly what I did. No problems.
Cheers,
- Dave
http://www.digistar.com/~dmann/
Hi there,
Chris Wilkinson wrote:
command to rc.local or similar? Or perhaps there is a program
I'm unaware of that can save the module settings, so that this
'dirty' piece of code can be loaded without question! :-)
Thanks for the advice guys. I put 'nvidia' into /etc/modules
and now wonderful
Hi there,
I just installed the latest nVidia Detonator Linux driver. When
I rebooted the system to use the new driver the display manager
failed to start x. The logs say it has trouble finding the nvidia
kernel module, so I did 'lsmod' and confirmed that the module
wasn't loaded. I then did
in my debian install there is a file called /etc/modules, try adding it
there. My /etc/modules follows. With regards to tainting - it basically
means that you cannot expect to get help/support with any kernel
problems because a kernel module can completely change how the kernel
works at run time
Its quite odd but the previous nVidia module didn't cause any grief
at all and I've only made a minor point update...
It is strange... X should automatically load the nVidia driver when it
needs it.
I am wanting to compile a module from the latest cvs in order to get some new feature
(module is cpia.o, features are for intel qx3 microscope).
If I put the 3 or four files (cpia.c, cpia.h, cpia_usb.c, cpia_pp.c) into the correct
place in the kernel tree, can I just make modules
One can compile a new module without a kernel rebuild - even a module
that has not been used by the current kernel.
You should at least try it - copy the files to the right place,
make modules modules_install
depmod -a
modprobe cpia
And report back to the group :-)
Also -
yeah that worked, cool.
much quicker than a 20 minute complete recompile.
On Thu, 31 Oct 2002 08:46:23 +1300
C Falconer [EMAIL PROTECTED] wrote:
One can compile a new module without a kernel rebuild - even a module
that has not been used by the current kernel.
You should at least try it -
20 minutes? Jeez I remember compiling 1.3.something on a 386 with 4 Mb
ram... it took 6 hours and that was a small kernel!
You young things today got no appreciation for the power of modern
equipment *grump*
When I was your age we used to have 4 kilobytes TOTAL! And we LIKED IT!
rant
...
Pete the Pirate
-Original Message-
From: C Falconer [mailto:cf;avonside.school.nz]
Sent: Thursday, 31 October 2002 9:36 a.m.
To: Linux Users Group
Subject: Re: How to deal with new kernel module code?
20 minutes? Jeez I remember compiling 1.3.something on a 386 with 4 Mb
ram
to deal with new kernel module code?
20 minutes? Jeez I remember compiling 1.3.something on a 386 with 4 Mb
ram... it took 6 hours and that was a small kernel!
You young things today got no appreciation for the power of modern
equipment *grump*
When I was your age we used to have 4
On Thu, 2002-10-31 at 09:45, Jeremy Bertenshaw wrote:
4MB!!! Sheer luxury! some of us only had 2MB on our 386's!!
When I was your age we used to have 4 kilobytes TOTAL! And we LIKED IT!
erm - powers of 1000 ? :-)
Peter van Hout wrote:
I remember working for a local IT computer that had an old Burroughs
computer that had hard disk platters that were 1.4 metres wide and 6mm
thick AND (wait for it) real CORE memory...
I lecturer at uni once related a story to us.
Some guys came to benchmark the
On Thu, Oct 31, 2002 at 09:45:14AM +1300, Jeremy Bertenshaw wrote:
4MB!!! Sheer luxury! some of us only had 2MB on our 386's!!
20 minutes? Jeez I remember compiling 1.3.something on a 386 with 4 Mb
ram... it took 6 hours and that was a small kernel!
On Thu, Oct 31, 2002 at 09:52:05AM +1300,
Any one out there using an AOpen 32x12x48x CDRW? Can you please tell me
what kernel module it uses?
I installed that model drive last week, on a system running rh7.2
I didn't need to play with kernel modules at all. The only thing i did was
insert the 'append=' line into /etc/lilo.conf
Hi,
Any one out there using an AOpen 32x12x48x CDRW? Can you please tell me
what kernel module it uses?
I have compiled in scsi support but would like to know what else I have
to add.
I have compiled kernel to get alsa support and sound and unwittingly
rendered my cdrom/rw unusable. Note
On Wed, 22 May 2002, Mark Carey wrote:
Hi,
Any one out there using an AOpen 32x12x48x CDRW? Can you please tell me
what kernel module it uses?
You have to reserve the ide for the scsi module so add something like
hdd=ide-scsi to your kernel boot params. This is crucial (I assume you
use
ide-scsi was the call, recompiled all good.
Thanks to all who responded so quickly.
A burning we will go, a burning we will go ..
Mark
19 matches
Mail list logo
