Hi, Tom, The reason insmod fails (90% sure) is that nVidia RPMs had to be rebuilt from src.rpm with current kernel source headers (do not forget to run "cloneconfig; make dep" first. Please note you do not need to rebuild the kernel itself. Also, it is a good idea to update kerenl/kernel source themselves from official SuSE update directory. Please note that after installing kernel modules yo need to run "depmod -a" first. Quite possible that you have to edit /etc/modules.conf manually. On Saturday, Feb 22, 2003, at 01:21 Europe/Helsinki, Tom Nicholson wrote:
Yes, it's me and thanks for the tip. I'm definitely looking at other chipsets. (and distros.) And as to your thoughts on what's required for nforce, I've done everything I think reasonable. Insmod fails with error messages as I've reported. The drivers build, yielding nvnet.o and nvaudio.o, etc. however entries in /etc/modules remain #'ed out (after rpm updates.) The modules fail to load at command line and complain about tainting the kernel. I didn't try the tar.gz method because the instructions for it involve rebuilding a new suse kernel. And I don't think the suse kernel is the problem. The yast installer selects the chipset nforce and builds for amd + nforce. I may try it later, but I had to go ahead and deliver the built system Thursday to its owner.
winxp installs easily and runs fast on nforce. It shouldn't involve hand-wringing and gut-wrenching failures to install a second hd or partition and boot Suse Linux as a 2nd os.
If you look at nv News Forum (www.nvnews.net) you'll see others who have posted re: installing for nforce and nforce2 chipsets. The ones who are getting them to work are redhat and mandrake. I don't think there's one suse post, maybe one, mine. There are at least two websites mentioned whose authors have put up long, elaborate instructions on how to get things to work on other distros. I guess downloading redhat or mandrake is the only option for me for now. Both of them have their quirks and limitations too. And suse has the best documentation and normally the best installation of all I've tried.
Dear Tom,
Is that you who initially posted problem with Athlon, MSI and NVidia GeForce4?
If yes, please read carefully.
1) The choice of Athlon and nForce2 chipset was wrong from the beginning. nForce2 chipset is not widely used by Linux users (in fact, it is quite rare chipset), and therefore, its kernel support may not be adequate (or it lags far behind compared with Intel chipset support).
2) Probably you have to manually load proprietary nVidia drivers with insmod, and the configure network. I am not sure about the sound.
3) I am also have unhappy experience with AthlonXP and VIA chipset. ALL problems and artifacts have gone after I have replaced m/b with AMD 761 chipset.
4) If you want less headache, just use Intel P4 and Intel chipsets.