On Mon, 02 Jan 2006 23:19:27 +1100, Grant wrote:

> No, I let the installer write a new xorg.conf, now why do you think
> the nvidia installer would write out a new xorg.conf with some other
> driver?

I was not aware that the new installers do that for you.

Mine still requires that you edit xorg.conf by hand after compiling and
even reminds me to do so. I guess I'm still in the dark ages

Having no need for newer driver features I just stick with what works.

># lsmod
>Module Size Used by
>nvidia 4085328 12

Clearly you do have it loaded.

As I said before - IGNORE )

>Those GNU/Linux screen savers crap all over the windoze ones.

Yup!

Franklin wrote:

> On Mon, 02 Jan 2006 23:19:27 +1100, Grant wrote:
>
>> No, I let the installer write a new xorg.conf, now why do you think
>> the nvidia installer would write out a new xorg.conf with some other
>> driver?
>
> I was not aware that the new installers do that for you.
>
> Mine still requires that you edit xorg.conf by hand after compiling and
> even reminds me to do so. I guess I'm still in the dark ages
>
> Having no need for newer driver features I just stick with what works.
>

I'll second that. I have a Geoforce 2 in my laptop. The last time I
'upgraded' to the latest nvidea driver (a few months back) it stop my
laptop powering down so I went back to an old version.

Ian

On Mon, 02 Jan 2006 04:58:56 -0800, Andreas Paasch wrote:

> If I understood how to compile a kernel and knew what you talked about in
> terms of localversion, I might be able to roll my own kernel.

Here's the option...

CONFIG_LOCALVERSION=""

If you kernel is version 2.6.9 and you select an A for the local
version your modules for that compile will be...

/lib/modules/2.6.9A

uname -r will return..

2.6.9A

This way you can try multiple compiles of the same kernel and keep your
modules from being overwritten. Mandrake uses it to signify a Mandrake
kernel.

I'm using 2.6.14.3 with Slack. Since it works for me why don't you grab
the source from kernel.org AND from slackware (so you'll have a
Slack .config file) and install it.

Go to...

ftp://ftp.slackware.no/pub/Linux/sla...-10.2/testing/
packages/linux-2.6.13/

Or a short URL...

http://tinyurl.com/csly5

And upgrade all the packages in there (For Slack version 10.2)

Take the .config file and copy it to /usr/src/linux-2.6.14.3

Do -

makeoldconfig
make bzImage
make modules
make modules_install

If there are any options in the new kernel that the old kernel didn't
have you will be prompted to make a choice. Usually the default is fine.

Now you will have two different kernel source trees. Grab the package I
used from my website in this directory...

ftp://ftp.rsgibson.com/pub/linux/NVidia/

Now you'll have the original 2.4 and 2.6 kernel plus 2.6.14.3 one that
I used and is known to work and a known to work NVidia driver.

Try it out a few times - You can specify which kernel/modules version to
use but I'd use a 2.6 kernel as I suspect NVidia might be using the
same.

> But, so far that doesn't seem an option. What reminds me, the test26.s
> kernel doesn't seem to have the kernel-source available anywhere so I
> guess I gotta go with 2.4.31 on a default Slack10.2

Look around in that directory I pointed out for Slackware. The 2.6
kernel is in testing. The alsa stuff must be upgraded also.

> In general, so far all posts have given a little input to my knowledge and
> I'll test it out later today or tomorrow. Most of what's been suggested so
> far, I have already done, but failed.

Well this worked for me. AFAIK the NVidia driver merely makes a module
and won't overwrite system files like the brain dead ATI driver does.
So you should be able to test a few things out and not hose the system.

On Mon, 02 Jan 2006 19:39:01 GMT, Ron Gibson <rsgibson@verizon.net> wrote:

>Do -
>
>makeoldconfig
>make bzImage
>make modules
>make modules_install

Erm... for 2.6 series try:

$ make oldconfig
$ make
$ su
# INSTALL_PATH=/boot make install
# make modules_install

Grant.

On Tue, 03 Jan 2006 07:17:51 +1100, Grant wrote:

>>makeoldconfig
>>make bzImage
>>make modules
>>make modules_install

> Erm... for 2.6 series try:

> $ make oldconfig
> $ make
> $ su
> # INSTALL_PATH=/boot make install
> # make modules_install

I prefer not to do it that way. I've done it the same way for over ten
years and I'm happy with the results. Therefore my suggesting doing it
any other way is giving advice in matters I don't have extensive
experience in.

On Mon, 02 Jan 2006 23:42:04 GMT, Ron Gibson <rsgibson@verizon.net> wrote:

>I prefer not to do it that way. I've done it the same way for over ten
>years and I'm happy with the results. Therefore my suggesting doing it
>any other way is giving advice in matters I don't have extensive
>experience in.

Bah, stick in the mud )

Main thing is to trust the method that works for _you_, caught me
in the middle of compile / test 22 new -hf32.1 hotfix kernels:

http://bugsplatter.mine.nu/test/linux-2.4/

Cheers,
Grant.

On Tue, 03 Jan 2006 10:51:48 +1100, Grant wrote:

>>I prefer not to do it that way. I've done it the same way for over ten
>>years and I'm happy with the results. Therefore my suggesting doing it
>>any other way is giving advice in matters I don't have extensive
>>experience in.

> Bah, stick in the mud )

Sorry

> Main thing is to trust the method that works for _you_, caught me in the
> middle of compile / test 22 new -hf32.1 hotfix kernels:

Yeah. I like one step at a time. One reason is I usually have 3 kernel
source trees and I wanna be extra careful and not make a mistake.

On Mon, 02 Jan 2006 04:58:56 -0800, Andreas Paasch wrote:

> Ron,
>
> If I understood how to compile a kernel and knew what you talked about in
> terms of localversion, I might be able to roll my own kernel.
>
> But, so far that doesn't seem an option. What reminds me, the test26.s
> kernel doesn't seem to have the kernel-source available anywhere so I
> guess I gotta go with 2.4.31 on a default Slack10.2
>
> In general, so far all posts have given a little input to my knowledge and
> I'll test it out later today or tomorrow. Most of what's been suggested so
> far, I have already done, but failed. I better check my BIOS settings too,
> could be they are the trouble makers.
>
> /Andreas

One thing that prevented me from using the driver compile option - I
didn't have the kernel source package installed yet. I'm surprised nobody
y else mentioned that.

Kevin