----- Original Message ----- From: "Ben Rosenberg" To: "SLE" Sent: Monday, December 17, 2001 8:54 AM Subject: Re: [SLE] Newbie Q: Kernel Sources

Do this...

rpm -Uvh --nodeps --force kernel-source-2.4.16.SuSE-20.i386.rpm\

This will replace it. :)

Cheers!

* Jason A.Van Cleve (jason@vancleve.com) [011216 23:52]: ->Hello, -> ->I just stumbled through an upgrade to kernel 4.4.16--though it couldn't have been much easier. But I need to install the sources too, in order to install an NVidia driver for my vid' card. I'm having a bit of trouble doing this: I have kernel 2.4.0 sources installed--SuSE 7.1 does this by default--and so when I try to install the 2.4.16 sources, it tells me: -> ->root@jason:/usr/src/packages > rpm -Uvh kernel-source-2.4.16.SuSE-20.i386.rpm ->error: failed dependencies: -> linux conflicts with linclude-2.4.0.SuSE-6 -> lx_sus22 conflicts with linclude-2.4.0.SuSE-6 -> ->Well, it won't let me uninstall that package: -> <snip>

Jacen, If I'm not mistaken (what, me mistaken?--nah), this solution will replace the old kernel sources minus the mods, i.e. .config file and such. This is a bad idea unless you are purging your system of the old kernels along with the sources. Most people keep the previous kernel(s) around while they test out the new. If so, you may need to update the modules at a future point and will find a deadend due to the old sources being absent. As you probably know, /usr/src/linux should be a symlink to /usr/src/linux-2.4.0 (or whatever your version). The best solution is to delete the /usr/src/linux symlink, make sure the old source tree exists under its own name (/usr/src/linux-2.4.0), then install the new source with "-ivh" instead of "-Uvh". -i does a straight install of the package without removing the old one first, while -U deletes the old files first, then installs the new one. If you are wiping the old kernels or are sure you will never recompile them again, then -Uvh is fine. Just something to consider. Ciao, John

Hi Jason, After building and installing your nvidia driver did you do a depmod? Maybe this is the problem. Kind regards, Simon Jason A.Van Cleve wrote:

Thanks, John, that's useful. I've already followed Ben's suggestion, which enabled me to compile the nvidia driver. It's all right in this case to destroy the old source, because due to a bug in my motherboard, running that old kernel, 2.4.0, had been demolishing my linux root partition (I had to upgrade to 2.4.4 just to keep the system running). So I wouldn't want to run or compile 2.4.0 anymore.

Bad news is, the nvidia driver still won't work. :< When I startx I get an error something like:

(EE) Failed to load module "nvidia" (file does not exists, 0)

If you know what that may mean, I welcome your input. This is where I'm stuck now.

--Jason Van Cleve

On Mon, 17 Dec 2001 20:17:21 +0100, "John Scott" stammered:

...

----- Original Message ----- From: "Ben Rosenberg" To: "SLE" Sent: Monday, December 17, 2001 8:54 AM Subject: Re: [SLE] Newbie Q: Kernel Sources

...

Do this...

rpm -Uvh --nodeps --force kernel-source-2.4.16.SuSE-20.i386.rpm\

This will replace it. :)

Cheers!

* Jason A.Van Cleve (jason@vancleve.com) [011216 23:52]: ->Hello, -> ->I just stumbled through an upgrade to kernel 4.4.16--though it couldn't

have been much easier. But I need to install the sources too, in order to install an NVidia driver for my vid' card. I'm having a bit of trouble doing this: I have kernel 2.4.0 sources installed--SuSE 7.1 does this by default--and so when I try to install the 2.4.16 sources, it tells me:

...

-> ->root@jason:/usr/src/packages > rpm -Uvh

kernel-source-2.4.16.SuSE-20.i386.rpm

...

->error: failed dependencies: -> linux conflicts with linclude-2.4.0.SuSE-6 -> lx_sus22 conflicts with linclude-2.4.0.SuSE-6 -> ->Well, it won't let me uninstall that package: ->

<snip>

Jacen, If I'm not mistaken (what, me mistaken?--nah), this solution will replace the old kernel sources minus the mods, i.e. .config file and such. This is a bad idea unless you are purging your system of the old kernels along with the sources. Most people keep the previous kernel(s) around while they test out the new. If so, you may need to update the modules at a future point and will find a deadend due to the old sources being absent. As you probably know, /usr/src/linux should be a symlink to /usr/src/linux-2.4.0 (or whatever your version). The best solution is to delete the /usr/src/linux symlink, make sure the old source tree exists under its own name (/usr/src/linux-2.4.0), then install the new source with "-ivh" instead of "-Uvh". -i does a straight install of the package without removing the old one first, while -U deletes the old files first, then installs the new one. If you are wiping the old kernels or are sure you will never recompile them again, then -Uvh is fine. Just something to consider.

Ciao,

John

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com