Ok, been have fits try to "make" the NVIDIA kernel mod. Upon running "make --dry-run" it says the the version of the CC is different then that used for the kernel and that (among 3 options) should make CC to the version of the c compiler I have. I'm not sure how this might be done (e.g. point the nvidia kernel mod to the right compiler) and just what version compiler I have. This is the message I got crrey:/usr/src/packages/SOURCES/NVIDIA_kernel-1.0-2313 # make --dry-run rm -f nv.o os-interface.o os-registry.o Module-linux nv_compiler.h NVdriver if [ -z ]; then \ if [ 2.95.3 != 2.95.3 ]; then \ echo " "; \ echo "You appear to be compiling the NVdriver kernel module with "; \ echo "a compiler different from the one that was used to compile "; \ echo "the running kernel. This may be perfectly fine, but there "; \ echo "are cases where this can lead to unexpected behaviour and "; \ echo "system crashes. "; \ echo " "; \ echo "If you know what you are doing and want to override this "; \ echo "check, you can do so by setting IGNORE_CC_MISMATCH. "; \ echo " "; \ echo "In any other case, set the CC environment variable to the "; \ echo "name of the compiler that was used to compile the kernel. "; \ echo " "; \ echo -en "\033[1;31m"; \ echo -e "*** Failed cc sanity check. Bailing out! ***"; \ echo -en "\033[0m"; \ exit 1; \ fi \ fi cc -c -Wall -Wno-unknown-pragmas -Wno-multichar -O -D__KERNEL__ -DMODULE -D_LOOSE_KERNEL_NAMES -D_X86_=1 -Di386=1 -DUNIX -DLINUX -DNV4_HW -DNTRM -DRM20 -D_GNU_SOURCE -DRM_HEAPMGR -D_LOOSE_KERNEL_NAMES -DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVEL=2313 -I. -I/lib/modules/2.4.10-4GB/build/include nv.c cc -c -Wall -Wno-unknown-pragmas -Wno-multichar -O -D__KERNEL__ -DMODULE -D_LOOSE_KERNEL_NAMES -D_X86_=1 -Di386=1 -DUNIX -DLINUX -DNV4_HW -DNTRM -DRM20 -D_GNU_SOURCE -DRM_HEAPMGR -D_LOOSE_KERNEL_NAMES -DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVEL=2313 -I. -I/lib/modules/2.4.10-4GB/build/include os-interface.c cc -c -Wall -Wno-unknown-pragmas -Wno-multichar -O -D__KERNEL__ -DMODULE -D_LOOSE_KERNEL_NAMES -D_X86_=1 -Di386=1 -DUNIX -DLINUX -DNV4_HW -DNTRM -DRM20 -D_GNU_SOURCE -DRM_HEAPMGR -D_LOOSE_KERNEL_NAMES -DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVEL=2313 -I. -I/lib/modules/2.4.10-4GB/build/include os-registry.c ld -r -o Module-linux nv.o os-interface.o os-registry.o ld -r -o NVdriver Module-linux Module-nvkernel size NVdriver if [ `id -ur` != 0 ]; then \ echo Please run \"make install\" as root.; \ else \ if [ -d /lib/modules/2.4.10-4GB/kernel/video ]; then \ rm -f /lib/modules/2.4.10-4GB/kernel/video/NVdriver; \ rmdir --ignore-fail-on-non-empty /lib/modules/2.4.10-4GB/kernel/video; \ fi && \ mkdir -p /lib/modules/2.4.10-4GB/kernel/drivers/video && \ /usr/bin/install -m 0664 -o root -g root NVdriver /lib/modules/2.4.10-4GB/kernel/drivers/video/NVdriver && \ /sbin/depmod -a && \ /sbin/modprobe NVdriver && \ ./makedevices.sh && \ echo "NVdriver installed successfully."; \ fi crrey:/usr/src/packages/SOURCES/NVIDIA_kernel-1.0-2313 # Any one have an idea? TIA, Curtis On Monday 03 December 2001 07:34, Jesse Marlin wrote:
Cleary_Mike@emc.com writes:
That's what I did too. Untarred, CD into the directory & type "make install".
Yes, I know - I need capture all the error messages. They scrolled by so fast I couldn't see them. I tried re-directing the output of "make install" to a file, but this did not pick up the error messages. Is there a good way to capture all the output?
A tried and true method is:
make > my_make.log 2>&1
This redirects stdout to my_make.log and stderr to where stdout is going.
TIA,
MIke ------------------------------------------------------ Cleary_Mike@emc.com x6033 ----------------------------------------------------------------- Overflow on /dev/null, please empty the bit bucket.
-----Original Message----- From: Michael Nelson [mailto:michaelnel@earthlink.net] Sent: Monday, December 03, 2001 11:09 AM To: Cleary_Mike@emc.com Cc: suse-linux-e@suse.com Subject: Re: [SLE] New NVIDIA drivers
On Mon, Dec 03, 2001 at 09:17:04AM -0500, Cleary_Mike@emc.com wrote: -> OK, so how does one get either the src rpm's or -> the tar files to build? I couldn't get either to build -> on my box (stock 7.3 install, 2.4.10).
One could start out with describing in detail what fails when one tries following the instructions.
All I did was change into the respective directories after untarring the tarballs and type "make install".
Michael
--
"# chmod a+x /bin/laden"
Michael Nelson San Francisco, CA
-- 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