Salix Forums

All that's going on with the modules is there is some stuff in there from when you tried to fix your video with the old kernel. It doesn't matter because as soon as you reboot, everything will be pointing at 3.2 not 2.6.

Looks fine to judge from that output

mimosa wrote:All that's going on with the modules is there is some stuff in there from when you tried to fix your video with the old kernel. It doesn't matter because as soon as you reboot, everything will be pointing at 3.2 not 2.6.

Looks fine to judge from that output

Cool. So I just need to run "update-grub" and then reboot?

I don't know grub at all well, but I think so! If in doubt, try sg2conf.

mimosa wrote:I don't know grub at all well, but I think so! If in doubt, try sg2conf.

Looks normal to me. I'll try a reboot now

OK, I could see that Grub booted into the new kernel. X wouldn't start. I tried "startx" but got an error about not being able to find "nvidia". I downloaded the proprietary driver installer as documented here. I started the installer, but have run into a new problem. There is something called a "CC version check" that has failed. I am warned that the compiler used to compile the kernel (gcc 4.6) "does not exactly match the current compiler (gcc 4.5)". I am then told that "The Linux 2.6 kernel module loader rejects kernel modules built with a version of gcc that does not exactly match that of the compiler used to build the running kernel" It continues "If you know what you are doing and want to ignore the gcc version check, select "No" to continue installation. Otherwise select "Yes" to abort installation, set the CC environment to the name of the compiler used to compile your kernel, and restart installation."

Sound like I need to install a newer version of the gcc compiler. Does anyone have an opinion on this?

It's likely you'll find the right gcc in the same repo you downloaded the current kernel from. However, the workaround being suggested will probably be effective, and it's conceivable that updating gcc could cause other trouble.

I'm a bit puzzled by the mention of 2.6 in that message, though. Maybe it means that there's no longer a problem about gcc versions for 3.2, in which case that's a point in favour of the workaround. In nay case, I think the worst thing that can happen is it won't work and you need to try the other way.
to see which modules you have loaded might be interesting. You would hope to see a long list!

I am not sure what I should look for with lsmod. I found "rtlwifi rtl8192ce", but ifconfig doesn't report any network card. The main thing however, is that with getting the Nvidia driver compiled and installed. I have gotten the eth0 connection working, so I suppose I could use wget to download a newer version of gcc if necessary, but the question of course is 1) whether I need it, and 2) what installing it would do to the rest of the system..
Edit:
As you mention, changing the "CC environment" is suggested as a work around, but I am again truly out of my depth here. I have no idea what the "CC environment" is, nor how to reconfigure it. Most importantly, I lack the overview to determine if this will help, or just dig me further down in a hole.

I'd try first saying "no" to the Nvidia gcc check, and maybe it'll work. If not, try updating gcc. Go to the root of the same repo you downloaded the kernel packages from, find gcc in packages.txt or similar, and that'll tell you the subdirectory to look for it in. slapt-get on my machine tells me there are various associated packages for gcc 4.5.2, but I think for building the Nvidia kernel module you only need the main one. Install it with spkg -u and try again. If you don't blacklist it, it will revert to the old version next time the package manager does an upgrade. Whether that is a good thing may depend on the circumstances, but if you run into trouble compiling anything in the future, you know what to do If you do want to keep the new gcc, it's probably necessary to upgrade all the associated packages; but if I'm right to think you don't need them for the Nvidia compilation, there's no rush.

lsmod was just to see if anything is going on like what happened to me. I had precisely no modules loaded! Count yourself lucky ...

EDIT

Here you go:
That looks like the main 64 bit package.

OK, I tried to continue, but the compile failed. A look in the log pinpoints two things as I see it. The first is that there is a report that the kernel configuration is invalid. The second problem seems to be an error message that "GLIBC_2.14" was not found.

Maybe you need to get that from current too. This is starting to seem rather hard going!

EDIT

http://ftp.ntua.gr/pub/linux/slackware/ ... 6_64-4.txz