Saga continues below.
On Thursday 01 July 2004 21:45, Paul C. Leopardi wrote:
On Thursday 01 July 2004 16:22, edward winston wrote:
I was having the same problems, and here is what
i did "
1) make cloneconfig
2) export MAKEFLAGS=O=/usr/src/linux-obj/$ARCH/$FLAVOR
3) sh <nviddia>.run --kernel-source-path=/usr/src/linux
Thanks for the tip. I've already done step 1).
For step 2), I created makeflags.sh containing
export MAKEFLAGS="O=/usr/src/linux-obj/`uname -i`/$1"
and then ran (as root)
. ./makeflags.sh default
Step 3) then worked OK.
I'll report this to nVIDIA. Steps 1) and 2) were not needed for 1.0-5332,
with the patch from http://www.minion.de
, so I don't see why they should be
needed for 1.0-6106.
Thomas Hertweck sent me a private email point out that these steps have been
needed all along, even for the 1.0-5332 from www.minion.de
. The reason why I
did not see this might be that the kernel-default package contains a
I checked 1.0-5332 after updating my kernel-default and kernel-source to
2.6.5-7.95. Sure enough, the nvidia-installer.log said:
-> A precompiled kernel interface for kernel '2.6.5-7.95-default' has been
executing: 'cd ./usr/src/nv; /usr/bin/ld -d -r -o nvidia.ko
-> Kernel module linked successfully.
is in the file list for the package kernel-default-2.6.5-7.95.
I then read /usr/src/linux/README.SUSE and discovered a package I had not
known about: kernel-syms. With kernel-syms installed, it is not necessary to
use Step 1) to install 1.0-6106.
After installing kernel-syms-2.6.5-7.95, I logged in as root, changed to
runlevel 3, changed directory to where I had downloaded the nVIDIA installer
. ./makeflags-SUSE.README.sh, containing the line:
export MAKEFLAGS= \
"-C /lib/modules/$(uname -r)/build O=/lib/modules/$(uname -r)/build"
The install worked.
I now believe that nVIDIA should add some relevant info about SuSE,
kernel-syms and MAKEFLAGS to their README.txt, which is also linked from
SuSE could write an article for the Support Database, describing the problem
and its solution.
Finally, at some stage, SuSE should take a look at changing the precompiled
interface from 1.0-5332 to 1.0-6106, and changing the YOU download script to
match. Probably for SuSE 9.2?