Tiny Core Linux

Tiny Core Extensions => TCE Talk => Topic started by: Stone.Giant on May 20, 2015, 01:25:29 AM

Title: [SOLVED] NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on May 20, 2015, 01:25:29 AM
I will not be surprise if most of you don't raise an eyebrow in my new thread. Yep it's a Nvidia one- or the most notorious one as per tinypoodle quote & quote. I already read Tinyfun's thread and yes... we suffered the same fate.
Quote
ERROR: Unable to find the kernel source tree for the currently running kernel.
       Please make sure you have installed the kernel source files for your
       kernel and that they are properly configured; on Red Hat Linux systems,
       for example, be sure you have the 'kernel-source' or 'kernel-devel' RPM
       installed.  If you know the correct kernel source files are installed,
       you may specify the kernel source path with the '--kernel-source-path'
       command line option.
 

Already installed linux-kernel-sources-env.tcz and linux-3.16.2_api_headers.tcz. And still to no avail. I guess no one surpirsed. By the way my graphic card is NVIDIA 5500FX series.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on May 20, 2015, 02:47:11 AM
'works for me with:
Code: [Select]
$ sudo ./NVIDIA-Linux-x86-173.14.39-pkg1.run --kernel-source-path=/usr/src/linux-3.16.6..but refuses to install the driver because I don't have the hardware.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on May 20, 2015, 05:27:09 AM
I did not find any /usr/src directory

Code: [Select]
tc@box:/$ sudo find / -name linux
/tmp/tcloop/gcc/usr/local/lib/gcc/i486-pc-linux-gnu/4.9.1/include-fixed/linux
/tmp/tcloop/linux-3.16.2_api_headers/usr/include/linux
/tmp/tcloop/ncurses/usr/local/share/terminfo/l/linux
/usr/include/linux
/usr/share/terminfo/l/linux
/usr/local/share/terminfo/l/linux
/usr/local/lib/gcc/i486-pc-linux-gnu/4.9.1/include-fixed/linux
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on May 20, 2015, 05:30:22 AM
You need to create the directory /usr/src, copy the kernel source there, unpack it and prepare it.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on May 20, 2015, 06:08:10 AM
Did you mean I copy the linux-kernel-sources-env.tcz to /src folder I created? How can I unpack it?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Misalf on May 20, 2015, 06:22:48 AM
You might want to take a look at
linux-kernel-sources-env.tcz
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on May 20, 2015, 06:28:08 AM
Did you mean I copy the linux-kernel-sources-env.tcz to /src folder I created? How can I unpack it?

No, you copy http://www.tinycorelinux.net/6.x/x86/release/src/kernel/linux-3.16.6-patched.txz to /usr/src and unpack it with "tar xf linux-3.16.6-patched.txz".

..but the linux-kernel-sources-env extension should also do that for you.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on May 20, 2015, 07:37:20 AM
I already run out of storage memory. Can I adjust the storage capacity of /HOME/tc directory?

Code: [Select]
[tc@box:~$ sudo tar -xf linux-3.16.6-patched.txz
tar: write error: No space left on device
tc@box:~$ fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1          66      525312  82 Linux swap
Partition 1 does not end on cylinder boundary
/dev/sda2   *          66        9730    77624320  83 Linux

tc@box:~$ df -hT /home
Filesystem           Type            Size      Used Available Use% Mounted on
rootfs               rootfs        907.1M    898.6M      8.6M  99% /
tc@box:~$ sudo tar -xf linux-3.16.6-patched.txz
tar: write error: No space left on device

/code]
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on May 20, 2015, 08:14:50 AM
If you don't have enough ram it would be better to unpack the kernel source on a hd or usb stick.

..and it would be better not to use "sudo tar..." and use "tar..." instead.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on May 20, 2015, 08:46:12 AM
Juanito   did the driver actually build? perhaps with a message saying that the driver failed to load?

because I've been attempting to build this driver (actually various versions up to latest NVIDIA-Linux-x86-346.59.run) but have so far failed with the generic ERROR: Unable to load the kernel module 'nvidia.ko' etc etc  on investigation I found that the driver doesn't build and can not be found on the system.

I have of course used linux-kernel-sources-env extension to prep the sources, however when that ultimately fails to produce an nvidia driver module I try manually preparing the sources.  Evengoing so far as to patch the patched-sources so they prepare without warnings yet still am unable to find the module after completion.

still an ongoing project

Error log too large to attach, so
Code: [Select]
nvidia-installer command line:
    ./nvidia-installer
    --kernel-source-path=/usr/src/linux-3.16.6

Using: nvidia-installer ncurses user interface
-> License accepted.
-> Installing NVIDIA driver version 340.76.
-> Performing CC sanity check with CC="/usr/local/bin/cc".
-> Using the kernel source path '/usr/src/linux-3.16.6' as specified by the '--kernel-source-path' commandline option.
-> Kernel source path: '/usr/src/linux-3.16.6'
-> Kernel output path: '/usr/src/linux-3.16.6'
-> Performing rivafb check.
-> Performing nvidiafb check.
-> Performing Xen check.
-> Performing PREEMPT_RT check.
-> Cleaning kernel module build directory.
   executing: 'cd ./kernel; /usr/local/bin/make clean'...
-> Building NVIDIA kernel module:
   executing: 'cd ./kernel; /usr/local/bin/make module SYSSRC=/usr/src/linux-3.16.6 SYSOUT=/usr/src/linux-3.16.6 NV_BUILD_MODULE_INSTANCES='...
   NVIDIA: calling KBUILD...
   make[1]: Entering directory '/usr/src/linux-3.16.6'
   test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
   echo >&2; \
   echo >&2 "  ERROR: Kernel configuration is invalid."; \
   echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
   echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it."; \
   echo >&2 ; \
   /bin/false)
   mkdir -p /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/.tmp_versions ; rm -f /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/.tmp_versions/*
   /usr/local/bin/make -f scripts/Makefile.build obj=/tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel
     cc -Wp,-MD,/tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/.nv.o.d  -nostdinc -isystem /tmp/tcloop/gcc/usr/local/bin/../lib/gcc/i486-pc-linux-gnu/4.9.1/include -I./arch/x86/include -Iarch/x86/include/generated  -Iinclude -I./arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/l
   inux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -m32 -msoft-float -mregparm=3 -freg-struct-return -mno-mmx -mno-sse -fno-pic -mpreferred-stack-boundary=2 -march=i486 -mtune=generic -maccumulate-outgoing-args -Wa,-mtune=generic32 -ffreestanding -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fno-delete-null-pointer-checks -Os -Wno-maybe-uninitialized -Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -fno-var-tracking-assignments -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -DCC_HAVE_ASM_GOTO -DNV_MODULE_INSTANCE=0 -DNV_BUILD_MODULE_INSTANCES=0 -UDEBUG -U_D
   EBUG -DNDEBUG -I/tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"340.76\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -DNV_UVM_ENABLE -D__linux__ -DNV_DEV_NAME=\"nvidia\"  -DMODULE  -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nv)"  -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv.o /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv.c
   In file included from include/uapi/linux/stddef.h:1:0,
                    from include/linux/stddef.h:4,
                    from ./include/uapi/linux/posix_types.h:4,
                    from include/uapi/linux/types.h:13,
                    from include/linux/types.h:5,
                    from include/uapi/linux/capability.h:16,
                    from include/linux/capability.h:15,
                    from include/linux/sched.h:15,
                    from include/linux/utsname.h:5,
                    from /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-linux.h:44,
                    from /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv.c:13:
   include/asm-generic/qrwlock.h: In function 'queue_write_trylock':
   include/asm-generic/qrwlock.h:93:35: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
             cnts, cnts | _QW_LOCKED) == cnts);
                                      ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
   ./arch/x86/include/asm/uaccess.h: In function 'copy_from_user':
   ./arch/x86/include/asm/uaccess.h:712:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (likely(sz < 0 || sz >= n))
                             ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
   ./arch/x86/include/asm/uaccess.h: In function 'copy_to_user':
   ./arch/x86/include/asm/uaccess.h:730:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (likely(sz < 0 || sz >= n))
                             ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
     cc -Wp,-MD,/tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/.nv-acpi.o.d  -nostdinc -isystem /tmp/tcloop/gcc/usr/local/bin/../lib/gcc/i486-pc-linux-gnu/4.9.1/include -I./arch/x86/include -Iarch/x86/include/generated  -Iinclude -I./arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -m32 -msoft-float -mregparm=3 -freg-struct-return -mno-mmx -mno-sse -fno-pic -mpreferred-stack-boundary=2 -march=i486 -mtune=generic -maccumulate-outgoing-args -Wa,
   -mtune=generic32 -ffreestanding -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fno-delete-null-pointer-checks -Os -Wno-maybe-uninitialized -Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -fno-var-tracking-assignments -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -DCC_HAVE_ASM_GOTO -DNV_MODULE_INSTANCE=0 -DNV_BUILD_MODULE_INSTANCES=0 -UDEBUG -U_DEBUG -DNDEBUG -I/tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"340.76\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -DNV_UVM_ENABLE -D__linux__ -DNV_DEV_NAME=\"nvidia\"  -DMODULE  -D"KBUILD_STR(s)=#s" -D"KBUILD_BASEN
   AME=KBUILD_STR(nv_acpi)"  -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-acpi.o /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-acpi.c
   In file included from include/uapi/linux/stddef.h:1:0,
                    from include/linux/stddef.h:4,
                    from ./include/uapi/linux/posix_types.h:4,
                    from include/uapi/linux/types.h:13,
                    from include/linux/types.h:5,
                    from include/uapi/linux/capability.h:16,
                    from include/linux/capability.h:15,
                    from include/linux/sched.h:15,
                    from include/linux/utsname.h:5,
                    from /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-linux.h:44,
                    from /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-acpi.c:15:
   include/asm-generic/qrwlock.h: In function 'queue_write_trylock':
   include/asm-generic/qrwlock.h:93:35: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
             cnts, cnts | _QW_LOCKED) == cnts);
                                      ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
   ./arch/x86/include/asm/uaccess.h: In function 'copy_from_user':
   ./arch/x86/include/asm/uaccess.h:712:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (likely(sz < 0 || sz >= n))
                             ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
   ./arch/x86/include/asm/uaccess.h: In function 'copy_to_user':
   ./arch/x86/include/asm/uaccess.h:730:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (likely(sz < 0 || sz >= n))
                             ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
     cc -Wp,-MD,/tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/.nv-chrdev.o.d  -nostdinc -isystem /tmp/tcloop/gcc/usr/local/bin/../lib/gcc/i486-pc-linux-gnu/4.9.1/include -I./arch/x86/include -Iarch/x86/include/generated  -Iinclude -I./arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -m32 -msoft-float -mregparm=3 -freg-struct-return -mno-mmx -mno-sse -fno-pic -mpreferred-stack-boundary=2 -march=i486 -mtune=generic -maccumulate-outgoing-args -Wa,-mtune=generic32 -ffreestanding -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fno-delete-null-pointer-checks -Os -Wno-m
   aybe-uninitialized -Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -fno-var-tracking-assignments -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -DCC_HAVE_ASM_GOTO -DNV_MODULE_INSTANCE=0 -DNV_BUILD_MODULE_INSTANCES=0 -UDEBUG -U_DEBUG -DNDEBUG -I/tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"340.76\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -DNV_UVM_ENABLE -D__linux__ -DNV_DEV_NAME=\"nvidia\"  -DMODULE  -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nv_chrdev)"  -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-chrdev.o /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-chrdev.c
   In file included from include/uapi/linux/stddef.h:1:0,
                    from include/linux/stddef.h:4,
                    from ./include/uapi/linux/posix_types.h:4,
                    from include/uapi/linux/types.h:13,
                    from include/linux/types.h:5,
                    from include/uapi/linux/capability.h:16,
                    from include/linux/capability.h:15,
                    from include/linux/sched.h:15,
                    from include/linux/utsname.h:5,
                    from /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-linux.h:44,
                    from /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-chrdev.c:15:
   include/asm-generic/qrwlock.h: In function 'queue_write_trylock':
   include/asm-generic/qrwlock.h:93:35: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
             cnts, cnts | _QW_LOCKED) == cnts);
                                      ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
   ./arch/x86/include/asm/uaccess.h: In function 'copy_from_user':
   ./arch/x86/include/asm/uaccess.h:712:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (likely(sz < 0 || sz >= n))
                             ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
   ./arch/x86/include/asm/uaccess.h: In function 'copy_to_user':
   ./arch/x86/include/asm/uaccess.h:730:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (likely(sz < 0 || sz >= n))
                             ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
     cc -Wp,-MD,/tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/.nv-cray.o.d  -nostdinc -isystem /tmp/tcloop/gcc/usr/local/bin/../lib/gcc/i486-pc-linux-gnu/4.9.1/include -I./arch/x86/include -Iarch/x86/include/generated  -Iinclude -I./arch/x86/include/uapi -Iarch/x86/include/ge
   nerated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -m32 -msoft-float -mregparm=3 -freg-struct-return -mno-mmx -mno-sse -fno-pic -mpreferred-stack-boundary=2 -march=i486 -mtune=generic -maccumulate-outgoing-args -Wa,-mtune=generic32 -ffreestanding -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fno-delete-null-pointer-checks -Os -Wno-maybe-uninitialized -Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -fno-var-tracking-assignments -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -DCC_HAVE
   _ASM_GOTO -DNV_MODULE_INSTANCE=0 -DNV_BUILD_MODULE_INSTANCES=0 -UDEBUG -U_DEBUG -DNDEBUG -I/tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"340.76\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -DNV_UVM_ENABLE -D__linux__ -DNV_DEV_NAME=\"nvidia\"  -DMODULE  -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nv_cray)"  -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-cray.o /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-cray.c
   In file included from include/uapi/linux/stddef.h:1:0,
                    from include/linux/stddef.h:4,
                    from ./include/uapi/linux/posix_types.h:4,
                    from include/uapi/linux/types.h:13,
                    from include/linux/types.h:5,
                    from include/uapi/linux/capability.h:16,
                    from include/linux/capability.h:15,
                    from include/linux/sched.h:15,
                    from include/linux/utsname.h:5,
                    from /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-linux.h:44,
                    from /tmp/selfgz15527/NVIDIA-Linux-x86-340.76/kernel/nv-cray.c:15:
   include/asm-generic/qrwlock.h: In function 'queue_write_trylock':
   include/asm-generic/qrwlock.h:93:35: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
             cnts, cnts | _QW_LOCKED) == cnts);
                                      ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
   ./arch/x86/include/asm/uaccess.h: In function 'copy_from_user':
   ./arch/x86/include/asm/uaccess.h:712:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (likely(sz < 0 || sz >= n))
                             ^
   include/linux/compiler.h:159:40: note: in definition of macro 'likely'
    # define likely(x) __builtin_expect(!!(x), 1)
                                           ^
   ./arch/x86/include/asm/uaccess.h: In function 'copy_to_user':
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on May 20, 2015, 08:50:44 AM
Code: [Select]
ERROR: Kernel configuration is invalid.
      include/generated/autoconf.h or include/config/auto.conf are missing.
      Run 'make oldconfig && make prepare' on kernel src to fix it."

this appears to be the culprit, however the files do exist
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Misalf on May 20, 2015, 09:42:37 AM
I was able to build version 304.125 (for legacy cards).
I removed  /usr/lib/*tls*.*
and I think to remember the installer is confused about
/user/local/lib/X11/
vs
/user/local/lib/xorg/
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on May 20, 2015, 11:31:06 PM
If you don't have enough ram it would be better to unpack the kernel source on a hd or usb stick.

..and it would be better not to use "sudo tar..." and use "tar..." instead.

Is it Ram? I think it is storage capacity of /home directory (default of 2GB in other linux distro) that I ran out of for, I already deleted some files and have 40MB left but the linux-kernel-source is 70MB. How can I adjust to 10GB the storage capacity of /Home directory?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: gerald_clark on May 20, 2015, 11:51:27 PM
Home is in  RAM.  Use your hard drive.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on May 21, 2015, 01:47:01 AM
Juanito   did the driver actually build? perhaps with a message saying that the driver failed to load?
No, I got the same errors as you.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on May 23, 2015, 11:50:31 AM
Home is in  RAM.  Use your hard drive.

What about if i save in /usr/local, will be it still in RAM? Does all linux distros's Home directory stored in RAM? I have begin a sad realization here about how Linux utilize RAM as storage not as medium between apps and kernels.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Rich on May 23, 2015, 12:46:07 PM
Hi Stone.Giant
Code: [Select]
What about if i save in /usr/local, will be it still in RAM?Yes.
Code: [Select]
Does all linux distros's Home directory stored in RAM?No. You might want to consider setting up a persistent home directory. Have you taken the time to read this:
http://tinycorelinux.net/corebook.pdf
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on May 24, 2015, 03:14:24 AM
No. You might want to consider setting up a persistent home directory. Have you taken the time to read this:
http://tinycorelinux.net/corebook.pdf

Thanks for the manual. BTW in Tinyfun's thread he mentioned that u are a keeper of Nvidia extension. Do you still have that extensions that i could use?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Rich on May 24, 2015, 10:42:52 AM
Hi Stone.Giant
Quote
BTW in Tinyfun's thread he mentioned that u are a keeper of Nvidia extension.
I built the 96.43.20 extension. Most of the NVidia extensions were built by Arslan S.
Quote
Do you still have that extensions that i could use?
The extension I built does not support your card, see:
http://tinycorelinux.net/4.x/x86/tcz/nvidia-96.43.20-3.0.3-tinycore.tcz.info
You might want to read through this thread:
http://forum.tinycorelinux.net/index.php/topic,12965.msg71206.html#msg71206
You will also find the build scripts I used in reply #8.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on May 24, 2015, 04:35:55 PM
I was able to build version 304.125 (for legacy cards).
I removed  /usr/lib/*tls*.*
and I think to remember the installer is confused about
/user/local/lib/X11/
vs
/user/local/lib/xorg/

Misalf I believe you're right about the X11 vs Xorg confusion..   I just built nvidia.ko version-346.72
now to begin testing..
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on May 25, 2015, 10:27:31 PM
If I do a persistent storage bootcode, will my file automatically transferred to hdd?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Rich on May 25, 2015, 10:51:20 PM
Hi Stone.Giant
Quote
If I do a persistent storage bootcode, will my file automatically transferred to hdd?
Yes. Before you start, copy your  tce/mydata.tgz  to  tce/mydata.tgz.original. This way you have a backup in case you mess up.
Add the  home=sda2  boot code. Reboot your machine. Edit your  /opt/,filetool.lst  file and remove any entries listing home.
Run a backup. Do another reboot to verify your home is persistent.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 01, 2015, 02:51:09 AM
Hi Stone.Giant
Quote
If I do a persistent storage bootcode, will my file automatically transferred to hdd?
Yes. Before you start, copy your  tce/mydata.tgz  to  tce/mydata.tgz.original. This way you have a backup in case you mess up.
Add the  home=sda2  boot code. Reboot your machine. Edit your  /opt/,filetool.lst  file and remove any entries listing home.
Run a backup. Do another reboot to verify your home is persistent.

I already performed a persistent storage bootcode, i did backup my mydata.tgz.original and deleted all entries with /home in filetool.lst, but all my files are completely wiped out and did not transfer to hdd. Also my Seamonkey browser malfunctioned because it was originally stored in ~/tc directory. How can I determine now if it uses the hdd as storage?

Code: [Select]
[tc@box:~$ df -hT /
Filesystem           Type            Size      Used Available Use% Mounted on
rootfs               rootfs        907.1M     96.7M    810.4M  11% /
/code]

[code]tc@box:~$ seamonkey
libasound is already installed!
dbus-glib is already installed!
gtk2 is already installed!
/etc/sysconfig/tcedir/ondemand/seamonkey: line 3: /home/tc/seamonkey/seamonkey: not found

Code: [Select]
tc@box:/mnt/sda2/tce$ showbootcodes
initrd=/tce/boot/core.gz quiet home=sda2 swapfile={sda2} waitusb=5:UUID="3b489518-7cda-4146-b00c-4222fa977793" tce=UUID="3b489518-7cda-4146-b00c-4222fa977793" BOOT_IMAGE=/tce/boot/vmlinuz


sent usig fifth
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 01, 2015, 03:56:09 AM
For home to be persistent without backing up home then you'll need to specify where to make home's permanent storage using a boot code.
your bootcodes indicate home is located on the same partition as a swapfile?? 
Also why use curly braces swapfile={sda2} ??    (I think swapfile=sda2 is correct)

for example, here I specify where to store my permanent home:   home=UUID="8eb3e1f8-c1ee-2bac-f66d-070f73960f62"
Code: [Select]
menuentry "TC-6-x86 Vesa" {
search --no-floppy --fs-uuid --set=root 8eb3e1f8-c1ee-2bac-f66d-070f73960f62
linux /linux/vmlinuz-3166 tz=GMT quiet waitusb=5:UUID="8eb3e1f8-c1ee-2bac-f66d-070f73960f62" tce=UUID="8eb3e1f8-c1ee-2bac-f66d-070f73960f62"/tc6-x86 opt=UUID="8eb3e1f8-c1ee-2bac-f66d-070f73960f62" home=UUID="8eb3e1f8-c1ee-2bac-f66d-070f73960f62" mydata=mydata32.vesa
initrd /linux/rootfs-630.gz /linux/modules-3166.gz
}
Code: [Select]
tc@box:~$ showbootcodes
BOOT_IMAGE=/linux/vmlinuz-3166 tz=GMT quiet waitusb=5:UUID=8eb3e1f8-c1ee-2bac-f66d-070f73960f62 tce=UUID=8eb3e1f8-c1ee-2bac-f66d-070f73960f62/tc6-x86 opt=UUID=8eb3e1f8-c1ee-2bac-f66d-070f73960f62 home=UUID=8eb3e1f8-c1ee-2bac-f66d-070f73960f62 mydata=mydata32.vesa

Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 01, 2015, 04:52:14 AM
I returned to my last post to expand on the persistent home issue (but found my time was up and no longer able to edit!!) 
your bootcodes indicate home is located on the same partition as a swapfile??    A swapfile is for use when a fat filesystem is available, however home afaik can not reside on a fat partition.   So which is it??
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 01, 2015, 07:44:29 AM
My swapfile is sda1 formatted to swap partition and my home is sda2 formatted to ext4 using gparted. i'll check it out maybe I mistype my extrnsion when i reformatted my computer.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 01, 2015, 03:30:36 PM
Aaaaah ok so was a typo


Sent from my iPhone using Tapatalk
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 04, 2015, 12:08:52 AM
Yes. I have misspecified my swap partition when I reformatted my machine. Is there any side effects to it?

Code: [Select]
tc@box:~$ showbootcodes
initrd=/tce/boot/core.gz quiet home=sda2 swapfile={sda2} waitusb=5:UUID="3b489518-7cda-4146-b00c-4222fa977793" tce=UUID="3b489518-7cda-4146-b00c-4222fa977793" BOOT_IMAGE=/tce/boot/vmlinuz
tc@box:~$ fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1          66      525312  82 Linux swap
Partition 1 does not end on cylinder boundary
/dev/sda2   *          66        9730    77624320  83 Linux

How can I verify Im using my HDD as persistent storage?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Rich on June 04, 2015, 12:32:29 AM
Hi Stone.Giant
Code: [Select]
tc@box:~/guilib/grabber$ cat /proc/mounts | grep /dev/sd
/dev/sda3 /mnt/sda3 ext3 rw,relatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/sda3 /home ext3 rw,relatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/sda3 /opt ext3 rw,relatime,barrier=1,nodelalloc,data=ordered 0 0
tc@box:~/guilib/grabber$
This shows my  home  and  opt  directories are persistent.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 04, 2015, 09:09:13 AM
Code: [Select]
tc@box:~$ cat /proc/mounts | grep /dev/sd
/dev/sda2 /mnt/sda2 ext4 rw,relatime,data=ordered 0 0
/dev/sda2 /home ext4 rw,relatime,data=ordered 0 0

My files were not transfer to hdd they were completely wiped out. I only backup mydata.tgz
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: gerald_clark on June 04, 2015, 09:25:10 AM
Use the mc file manager to look in mydata.tgz and see if your data is there.  If not, you did not back it up.
If it is there, it should be extracted at boot.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 04, 2015, 09:37:38 AM
Hi Stone.Giant
Quote
If I do a persistent storage bootcode, will my file automatically transferred to hdd?
Yes. Before you start, copy your  tce/mydata.tgz  to  tce/mydata.tgz.original. This way you have a backup in case you mess up.
Add the  home=sda2  boot code. Reboot your machine. Edit your  /opt/,filetool.lst  file and remove any entries listing home.
Run a backup. Do another reboot to verify your home is persistent.

i think it will not gona load coz i renamed my original mydata.tgz to mydata.tgz.original even my file is there
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: gerald_clark on June 04, 2015, 09:42:54 AM
You were told to copy, not rename.
Copy your backup to mydata.tgz and reboot.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 04, 2015, 09:53:05 AM
yes i did copy using command

Code: [Select]
tc@box:/mnt/sda2/tce$ cp -pi mydata.tgz mydata.tgz.original
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 04, 2015, 10:09:26 AM
I used mc.tcz to view the contents of mydata.tgz i did not see any home folder only these 3
/etc
/opt
/usr
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 04, 2015, 10:56:26 AM
how can i define the UUID of my hdd?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: gerald_clark on June 04, 2015, 11:19:18 AM
You don't.  Run blkid to find out what it is.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 04, 2015, 11:21:57 AM
All ok now. I reload my original mydata.tgz and disable persistent storage then returned again to persistent storage. All my files were transferred. I think the main cause of the problem is the swap and home are on the same partition (sda2). I redefine my home and swap partitions.

Code: [Select]
tc@box:~$ cat /proc/mounts | grep /dev/sd
/dev/sda2 /mnt/sda2 ext4 rw,relatime,data=ordered 0 0
/dev/sda2 /home ext4 rw,relatime,data=ordered 0 0
tc@box:~$ ls
Desktop/                             jre-8u45-linux-i586.tar.gz
Downloads/                           jre1.8.0_45/
Introducing the Lily Camera.mp4      linux-3.16.6-patched.txz
NVIDIA-Linux-x86-173.14.39-pkg1.run  nvidia-error ID4786
alsareadme                           nvidia-installer.log
alsasound_start.sh                   seamonkey/
dillo-3.0.4.1/                       seamonkey-2.33.1.tar.bz2
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 04, 2015, 12:02:20 PM
Here is my progress now, going back to the original problem...

Code: [Select]
$ sudo ./NVIDIA-Linux-x86-173.14.39-pkg1.run --kernel-source-path=/usr/src/linux-3.16.6

It gave me an error

(http://i61.tinypic.com/23tfhpk.jpg)
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: gerald_clark on June 04, 2015, 12:15:07 PM
Use a symbolic link to point /usr/src to a directory on your hard disk.  Then follow the instructions you were given to extract the sources.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 04, 2015, 08:37:25 PM
Use a symbolic link to point /usr/src to a directory on your hard disk.  Then follow the instructions you were given to extract the sources.

point to which directory?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: gerald_clark on June 04, 2015, 09:01:04 PM
The one where you are going to store the files.  I have a feeling you are in over your head.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 04, 2015, 10:31:19 PM
My SOP is to install any programs in $HOME which is now in HDD using persistent storage bootcode. Is this correct?
Code: [Select]
tc@box:/usr/src/linux-3.16.6$ln -s /usr/src/linux-3.16.6 /home/tc

Will it be better if i manually install headers? Where will it be installed?
Code: [Select]
tc@box:/usr/src/linux-3.16.6$ make headers_install
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 05, 2015, 02:53:07 AM
I suggest you use the linux-kernel-sources-env extension to prepare the kernel source.

Before loading the extension, create a symlink to your permanent home:
Code: [Select]
$ mkdir -p /home/tc/usr/src
$ cd /usr
$ sudo ln -s /home/tc/usr/src src

..and then load linux-kernel-sources-env
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 05, 2015, 04:05:10 PM
I already finished loading linux-kernel-sources-env. Now what is the next step?
(http://i62.tinypic.com/2nbge8j.png)
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 06, 2015, 03:42:05 AM
unpack the nvidia source and try to compile the driver..
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: jls on June 07, 2015, 08:51:43 AM
Hi
Build scripts for the nvidia driver already exists for tc 4.x, thanks to arslanserc:
https://code.google.com/p/tc-ext-tools/source/browse/packages/nvidia/ (https://code.google.com/p/tc-ext-tools/source/browse/packages/nvidia/)
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 08, 2015, 04:09:25 AM
Hi
Build scripts for the nvidia driver already exists for tc 4.x, thanks to arslanserc:
https://code.google.com/p/tc-ext-tools/source/browse/packages/nvidia/ (https://code.google.com/p/tc-ext-tools/source/browse/packages/nvidia/)

can I use that with TC 6.x ?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 08, 2015, 06:38:12 AM
I got error

Code: [Select]
$ sudo ./NVIDIA-Linux-x86-173.14.39-pkg1.run --kernel-source-path=/usr/src/linux-3.16.6
(http://i58.tinypic.com/335bg4i.png)
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Misalf on June 08, 2015, 07:11:32 AM
IIRC, you're supposed to compile the nvidia drivers in CLI while not running X.

Also you will need  procps.tcz  .
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 08, 2015, 07:14:22 AM
If you have compiletc, perl5, ncurses-dev, bash and bc loaded things should work.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: jls on June 08, 2015, 08:39:16 AM
Hi
Build scripts for the nvidia driver already exists for tc 4.x, thanks to arslanserc:
https://code.google.com/p/tc-ext-tools/source/browse/packages/nvidia/ (https://code.google.com/p/tc-ext-tools/source/browse/packages/nvidia/)

can I use that with TC 6.x ?
Hi Stone.Giant
Try it and please report the eventual errors
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 08, 2015, 09:42:21 AM
Hi
Build scripts for the nvidia driver already exists for tc 4.x, thanks to arslanserc:
https://code.google.com/p/tc-ext-tools/source/browse/packages/nvidia/ (https://code.google.com/p/tc-ext-tools/source/browse/packages/nvidia/)

can I use that with TC 6.x ?
Hi Stone.Giant
Try it and please report the eventual errors

I depend on .tcz extensions. im a newbie could you teach me how to use it?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 08, 2015, 09:47:59 AM
I got newer error. I already made a symlink to /usr from /home/seed/usr/src
Code: [Select]
seed@avocado:/usr$ ls -l
total 0
drwxr-sr-x    2 root     root          3640 Jun  8 20:52 bin/
drwxr-xr-x   36 root     root          3020 Sep 17  2014 include/
drwxr-xr-x    6 root     root          1300 Jun  8 20:52 lib/
lrwxrwxrwx    1 root     root            30 Jun  8 21:08 linux-3.16.6 -> home/seed/usr/src/linux-3.16.6
drwxr-xr-x   15 tc       staff          320 Jun  8 21:35 local/
drwxr-xr-x    2 root     root           560 May  3 12:38 sbin/
drwxr-xr-x   16 root     root           320 Sep 17  2014 share/

I exited X-server (Ctrl+Alt+F1) and sudo kill <Nvidia PID>. When I executed this command this is what I got...
Code: [Select]
seed@avocado:~$ sudo ./NVIDIA-Linux-x86-173.14.39-pkg1.run -kernel-source-path=/
usr/linux.3.16.6

(http://i62.tinypic.com/1r985g.jpg)

WWW?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Misalf on June 08, 2015, 09:54:50 AM
It should be
Code: [Select]
/usr/src/linux.3.16.6
not
Code: [Select]
/usr/linux.3.16.6

CTRL+ALT+F1 does not exit X.
CTRL+ALT+Backspace does.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 08, 2015, 10:58:33 AM
It should be
Code: [Select]
/usr/src/linux.3.16.6
not
Code: [Select]
/usr/linux.3.16.6

CTRL+ALT+F1 does not exit X.
CTRL+ALT+Backspace does.

You mean I place my symlink to /usr/src? I shud make a folder first.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Misalf on June 08, 2015, 11:27:15 AM
I did not need to use  --kernel-source-path  when I compiled the nvidia drivers.
Maybe because the kernel sources where stored at the correct location in my case.

However, I just noticed that you didn't use the correct command parameter.
Code: [Select]
-kernel-source-path
vs
Code: [Select]
--kernel-source-path
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 08, 2015, 12:04:43 PM
I did not need to use  --kernel-source-path  when I compiled the nvidia drivers.
Maybe because the kernel sources where stored at the correct location in my case.

However, I just noticed that you didn't use the correct command parameter.
Code: [Select]
-kernel-source-path
vs
Code: [Select]
--kernel-source-path

Sorry for the typo, but i did use the correct synta in CLI. Is it ok to use the /usr/linux-3.16.6 as destination folder or Nvidia installation script is configured to find it in /usr/src/linux3.16.6?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 09, 2015, 06:26:38 AM
The nvidia script should work with where ever you set "--kernel-source-path" to.

I see from the build script link that it uses "--extract-only" and then a bunch of individual commands to get things done, maybe this might be a better way to go?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 09, 2015, 07:33:34 AM
As u can see in the picture I have some scarce file included in my symlink (which made it in red text if u ls -l). I already deleted my previous symlink and created a new one.
Quote
(http://i62.tinypic.com/2nbge8j.png)

i also tried to rerun linux-kernel-sources-env but it gave error:
(http://i57.tinypic.com/2ujk22b.png)

now it gave me again this error

Quote
ERROR: The kernel source path '/usr/src/linux-3.16.6' does not exist.  Please
       make sure you have installed the kernel source files for your kernel and
       that they are properly configured; on Red Hat Linux systems, for
       example, be sure you have the 'kernel-source' or 'kernel-devel' RPM
       installed.  If you know the correct kernel source files are installed,
       you may specify the kernel source path with the '--kernel-source-path'
       command line option.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 09, 2015, 08:57:25 AM

Try running linux-kernel-sources-env and NVIDIA-Linux-x86-173.14.39pkg1.run as default user


Sent from my iPad using Tapatalk HD
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 09, 2015, 09:54:54 AM
Having said that, NVIDIAxxxxxxx.run should be run as  root  via sudo nvidiaxxxxxxx.run


Sent from my iPad using Tapatalk HD
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Misalf on June 09, 2015, 10:11:56 AM
Sooner or later you will probably face the situation where you need to create an extension out of the compiled files so they survive a reboot. I suggest you take Rich's scripts, which I did too, with minor modifications.
Hi Stone.Giant
[...]
You might want to read through this thread:
http://forum.tinycorelinux.net/index.php/topic,12965.msg71206.html#msg71206
You will also find the build scripts I used in reply #8.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Misalf on June 09, 2015, 11:08:07 AM
Downloading the scripts currently doesn't work at my end so I post the ones that I still have around.

Make sure to change the VERS variable to the version nuber of the driver you want to compile in both scripts.
Also save the scripts in the same directory where  NVIDIA-Linux-x86-$VERS.run  is located.
After saving them and making them executable, exit out of X (CTRL+ALT+Backspace).
Then run  ./create-nvidia-raw  (as normal user).

create-nvidia-raw
Code: [Select]
#!/bin/sh
KERN=`uname -r`
VERS="319.17"

tce-load -w compiletc findutils squashfs-tools procps
tce-load -i compiletc findutils squashfs-tools procps

touch NOW
sleep 5
sudo sh ./NVIDIA-Linux-x86-$VERS.run --accept-license --no-network
rm -f nvidia-raw.tar.gz
rm -rf nvidia-raw
mkdir -p nvidia-raw/rawpackage
find /usr -newer NOW -not -type d > nvidia-raw.list
find /lib -newer NOW -not -type d | grep /lib/modules/$KERN/kernel/drivers/ >> nvidia-raw.list
tar -T nvidia-raw.list -czvf nvidia-raw.tar.gz
cd nvidia-raw/rawpackage
tar -xf ../../nvidia-raw.tar.gz
cd ..
#sudo nvidia-xconfig --mode=1280x1024 --force-generate --virtual=1280x1024


I'm not entirely sure but you might need to manually copy created files from
/usr/local/lib/X11
to
/usr/local/lib/xorg
(you might need to edit the created extension if the drivers won't work after reboot)

At this point, the driver is already installed but won't survive a reboot.
Try  startx  to see if things work.

Note the last line which is commented out in above script. This command is sometimes needed in order to create a working  xorg.conf .
If that's the case, (Failed in waitforX) execute said command with your desired resolution, try  startx  again, and if things work, add  etc/X11  to your  /opt/.filetool.lst  and do a backup.


If that went well, run  ./create-nvidia-package  (also as normal user)

create-nvidia-package
Code: [Select]
#!/bin/sh
KERN=`uname -r`
VERS="319.17"

cd nvidia-raw
sudo rm -rf package
mkdir package
cp -r rawpackage/* package
mv package/usr/share package/usr/local/
mv package/usr/local/share/applications/nvidia-settings.desktop package/usr/local/share/applications/nvidia-$VERS-$KERN.desktop
sed -i 's/Exec=/Exec=sudo /' package/usr/local/share/applications/nvidia-$VERS-$KERN.desktop
sed -i 's/Icon=/Icon=nvidia-settings\nIcon=/' package/usr/local/share/applications/nvidia-$VERS-$KERN.desktop
sed -i 's/Icon=\/usr/X-FullPathIcon=\/usr\/local/' package/usr/local/share/applications/nvidia-$VERS-$KERN.desktop

mkdir package/usr/local/tce.installed
echo -e "#!/bin/sh\nln -sf /usr/local/lib/xorg/modules/extensions/libglx.so.$VERS /usr/local/lib/xorg/modules/extensions/libglx.so" > package/usr/local/tce.installed/nvidia-$VERS-$KERN
sudo chown -R root:staff package/usr/local/tce.installed
sudo chmod -R 775 package/usr/local/tce.installed
mv package/lib/modules package/usr/local/lib/
gzip package/usr/local/lib/modules/$KERN/kernel/drivers/video/nvidia.ko
rm -f package/usr/bin/nvidia-uninstall
rm -f package/usr/bin/nvidia-installer
rm -rf package/lib
rm -f package/usr/lib/*tls*.*

rm -f nvidia-$VERS-$KERN.tcz
mksquashfs package nvidia-$VERS-$KERN.tcz
md5sum nvidia-$VERS-$KERN.tcz > nvidia-$VERS-$KERN.tcz.md5.txt
cd package
find -not -type d | cut -c3- | sort -d > ../nvidia-$VERS-$KERN.tcz.list
cd ..


Then move the created extension to  /etc/sysconfig/tcedir/optional/ .
Add the extension to  /etc/sysconfig/tcedir/onboot.lst .
Reboot.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 09, 2015, 11:35:15 AM
I also find Ctrl+Alt+backspace doesn't always remove the lock on the adapter however pkill Xorg does


Sent from my iPhone using Tapatalk
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 09, 2015, 01:28:34 PM
Here's my progress: I now successfully climbed up to next level of error. Kindly download attachment (149KB)

http://www.4shared.com/file/sotDqYIpba/nvidia-installer.html (http://www.4shared.com/file/sotDqYIpba/nvidia-installer.html)l

Quote
ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed.  Please see the file
       '/var/log/nvidia-installer.log' for details.  You may find suggestions
       on fixing installation problems in the README available on the Linux
       driver download page at www.nvidia.com.
 

I'll gona test Rich's scripts in later time.



Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 10, 2015, 06:30:48 AM
what's my next move?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Misalf on June 10, 2015, 07:32:37 AM
I can't download the file you uploaded.
Can you use pastebin.com? You can post as guest there. No need for an account.

I'm going to recompile my nvidia extension using Rich's scripts now. I'll see if I can automate any needed renaming of folders.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 10, 2015, 08:02:41 AM
I can't download the file you uploaded.
Can you use pastebin.com? You can post as guest there. No need for an account.

I'm going to recompile my nvidia extension using Rich's scripts now. I'll see if I can automate any needed renaming of folders.

Kindly seach for nvidia173.14.39_installer-log in pastebin.com. Thanks
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Misalf on June 10, 2015, 09:08:19 AM
This one?  http://pastebin.com/wUeeX085
(BTW, you should have gotten a link from pastebin to be able to post here what you pasted there.)
Lots of warnings.. Honestly, I don't know.
Maybe the kernel source isn't prepared properly.
In that case, this might help:
http://wiki.tinycorelinux.net/wiki:custom_kernel


I just did the following successfully...
Edited create-nvidia-raw:
Code: [Select]
#!/bin/sh
KERN=`uname -r`
VERS="304.125"

tce-load -w compiletc findutils squashfs-tools procps
tce-load -i compiletc findutils squashfs-tools procps

touch NOW
sleep 5
sudo sh ./NVIDIA-Linux-x86-$VERS.run \
--accept-license \
--no-network \
--no-runlevel-check \
--x-module-path=/usr/local/lib/xorg/modules

rm -f nvidia-raw.tar.gz
rm -rf nvidia-raw
mkdir -p nvidia-raw/rawpackage
find /usr -newer NOW -not -type d > nvidia-raw.list
find /lib -newer NOW -not -type d | grep /lib/modules/$KERN/kernel/drivers/ >> nvidia-raw.list
tar -T nvidia-raw.list -czvf nvidia-raw.tar.gz
cd nvidia-raw/rawpackage
tar -xf ../../nvidia-raw.tar.gz
cd ..
rm -f /usr/lib/*tls*.*

#sudo nvidia-xconfig --mode=1280x1024 --force-generate --virtual=1280x1024
Removed any nvidia drivers from  onboot.lst .
Rebboted.
Core tryed to startx -> failed in waitforX (no wonder, there's no driver currently).
Did this in linux console (I have 2GB RAM):
Code: [Select]
tce-load -i linux-kernel-sources-env
linux-kernel-sources-env.sh
./create-nvidia-raw
startx
It compiles right away without errors and X launches. Also  sudo nvidia-settings  works.
You might need to already have a valid xorg.conf though. If X doesn't start, do:
sudo nvidia-xconfig --mode=1280x1024 --force-generate --virtual=1280x1024
Or whatever screen res you need. Also, nvidia might need to be listed as Driver in the Device section of xorg.conf.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 10, 2015, 09:25:40 AM
I had another look at this:

* the kernel kbuild fails at this test:
Code: [Select]
include/config/auto.conf:
$(Q)test -e include/generated/autoconf.h -a -e $@ || ( \
echo >&2; \
echo >&2 "  ERROR: Kernel configuration is invalid."; \
echo >&2 "         include/generated/autoconf.h or $@ are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)

if the kernel source has been prepared, both autoconf.h and auto.conf are present, but busybox and coreutils test both fail here.

Replacing the whole lot with "include include/generated/autoconf.h" makes things work, but shouldn't be neccessary.

* the fix-build-with-linux-3.16.patch is required.

After all this, NVIDIA-Linux-x86-173.14.39-pkg1 compiles.

* install overwrites the Xorg /usr/local/lib/libGL.so and /usr/local/lib/xorg/modules/extensions/libglx.so, which might not be good.

If you pm me, I can provide a link to nvidia-173.14.39-3.16.3-tinycore.tcz to test if you wish - I have no suitable hardware so the packaging might not be correct...
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Misalf on June 10, 2015, 10:11:06 AM
Quote
* install overwrites the Xorg /usr/local/lib/libGL.so and /usr/local/lib/xorg/modules/extensions/libglx.so, which might not be good.

The driver version I use has this option
Code: [Select]
./NVIDIA-Linux-x86-304.125.run -A
...
  --no-opengl-files
      Do not install any of the OpenGL-related driver files.
...
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 10, 2015, 02:32:34 PM
Quote
Replacing the whole lot with "include include/generated/autoconf.h"
It's not clear exactly how to duplicate this, any help please?

Also
Quote
the fix-build-with-linux-3.16.patch is required
is this the patch from Ubuntu forums?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 10, 2015, 03:02:40 PM
I'm referring to the kernel top level Makefile. Replace the text I pasted with "include include/generated/autoconf.h" (I haven't figured out why this should be necessary).

The patch is here:

http://www.tinycorelinux.net/6.x/x86/tcz/src/nvidia_driver/NVIDIA-Linux-x86-173.14.39-pkg1.patch

Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 10, 2015, 04:27:43 PM
Aaah...  ok thank I think I understand now :)   Sorry I was looking at your fix and was drawing a total blank on what this was.. 
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 10, 2015, 04:46:47 PM
I've noticed the two config files which are listed in the failed test are totally different from each other.  While the set parameters of the config appear similar, each line has an additional textural prefix.. not sure if that matters?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 11, 2015, 04:05:07 AM
I understood that "test -e filename1 -a -e filename2"  should return true if filename1 AND filename2 exist. I don't believe the files need to be identical.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 11, 2015, 05:20:59 AM
I just loaded the test nvidia extension (I don't have nvidia hardware) with Xorg-7.7-3d.

If Xorg-7.7-3d is loaded first then the start-up script from the test nvidia extension will not overwrite the libGL and libglx symlinks.

..which is a good thing as Xorg-7.7 will not start if I manually point the symlinks to libGL.so.173.14.39 and libglx.so.173.14.39.

Loading the nvidia module (which I wouldn't expect to work without nvidia hardware) gives this:
Code: [Select]
$ sudo modprobe nvidia
modprobe: can't load module nvidia (kernel.tclocal/drivers/video/nvidia.ko.gz): unknown symbol in module, or unknown parameter

$ modinfo nvidia
filename:       kernel.tclocal/drivers/video/nvidia.ko.gz
license:        NVIDIA
alias:          char-major-195-*
alias:          pci:v000010DEd*sv*sd*bc03sc02i00*
alias:          pci:v000010DEd*sv*sd*bc03sc00i00*
depends:        agpgart
vermagic:       3.16.6-tinycore SMP mod_unload 486

$ lsmod | grep agpgart
agpgart                24576  2 drm,intel_gtt
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: curaga on June 11, 2015, 06:14:20 AM
dmesg will tell you which symbol.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 11, 2015, 06:59:14 AM
Indeed:
Code: [Select]
nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
..and so one more thing that needs patching

I see also that Xorg will probably not detect nvidia hardware and something like this is required:
Code: [Select]
$ cat /etc/X11/xorg.conf.d/20-nvidia.conf

Section "Device"
        Identifier "My GPU"
        Driver "nvidia"
EndSection
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 11, 2015, 08:03:30 AM
The acpi patch is at:

http://tinycorelinux.net/6.x/x86/tcz/src/nvidia_driver/NVIDIA-Linux-x86-173.14.39-pkg1.run_acpi.patch

@Stone.Giant - the test extension with the recompiled nvidia driver is also reposted.

I've now gone about as far as I can without nvidia hardware:
Code: [Select]
$ sudo modprobe nvidia
modprobe: can't load module nvidia (kernel.tclocal/drivers/video/nvidia.ko.gz): No such device

$ dmesg | grep -i nvidia
nvidia: module license 'NVIDIA' taints kernel.
NVRM: No NVIDIA graphics adapter found!
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 11, 2015, 01:05:00 PM
I understood that "test -e filename1 -a -e filename2"  should return true if filename1 AND filename2 exist. I don't believe the files need to be identical.
It was just a thought,  I assumed that was likely the case though hadn't found it in the script yet. meanwhile have been looking for clues as to why neither file was not at the path expected


Sent from my iPad using Tapatalk HD
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 11, 2015, 01:09:10 PM
Both files were in the expected place in the prepared kernel source, that's why I'm puzzled as to why the test fails  :)
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 11, 2015, 03:59:14 PM
I've created symlinks to the src files at every possible expected location, yet...     I'm missing something still !

I can extract the very latest nvidia sources, and build all driver modules yet the driver continues to segfault during loading..

Aaaarg!
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: curaga on June 12, 2015, 07:36:39 AM
@coreplayer2

Are you also using an old, unsupported driver? The 173 legacy driver was last updated 2013...
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 12, 2015, 12:10:06 PM
@ curaga   A summary of hardware
Among my PC's I have 3 with Nvidia video cards,

My main PC uses one of the latest Maxwell GM204 chips (out for almost a year) supported by driver v346.72

Other PC's use older hardware which are supported by the latest legacy 340.76 (almost all older Nvidia hardware are supported by this Legacy  Linux driver)
Geforce GTX 560
Geforce GTX 260m



The legacy v340.76 is the driver we should be creating with kernel 3.16.6 to support all but the very latest Nvidia hardware.
The driver v346.72 supports the latest hardware http://www.nvidia.com/download/driverResults.aspx/81760/en-us (http://www.nvidia.com/download/driverResults.aspx/81760/en-us)

it is the Nvidia driver 346.72 in 3.16.6 on my latest hardware (which is fully supported by this driver) that fails the the config test, yet if built segfaults when installed

To assist, I have attempted to run Nvidia driver 173 on my oldest Geforce GTX 200 series hardware, so far without success.  While I can not find more info on the NVIDIA-Linux-x86-173.14.39,  I found NVIDIA-Linux-x86-173.14.30 info in the archives which supports the desktop version but not the mobile version of the hardware I have.  The driver usually reports if the hardware is not supported, but not so in this case.



Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: curaga on June 12, 2015, 01:47:39 PM
Oh, if the latest fails, you should report the bug to nvidia.
Title: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 12, 2015, 03:31:56 PM
Yes have done that already.  Their latest 352.09  beta driver compiles and installs in tx-6 / 3.16.6 without error,  however the driver segfaults when Xorg is run

I wrote a script to gather all the log data after the driver crashes before the inevitable REISUB..  which I'm collecting now

Code: [Select]
[drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 0
NVRM: loading NVIDIA UNIX x86 Kernel Module  352.09  Tue May 12 13:54:22 PDT 2015
nvidia-settings[19438]: segfault at b8c5d984 ip b8c5d984 sp bf9c5eec error 14


Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 13, 2015, 06:27:18 AM
I've uploaded the nvidia-340.76 driver to the same place if you'd like to test - note that I did not create symlinks to the nvidia libGL and libglx.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 13, 2015, 11:14:42 AM
Ok thx


Sent from my iPhone using Tapatalk
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on June 13, 2015, 01:34:43 PM
To assist, I have attempted to run Nvidia driver 173 on my oldest Geforce GTX 200 series hardware, so far without success.  While I can not find more info on the NVIDIA-Linux-x86-173.14.39,  I found NVIDIA-Linux-x86-173.14.30 info in the archives which supports the desktop version but not the mobile version of the hardware I have.  The driver usually reports if the hardware is not supported, but not so in this case.

Here is my driver info from Nvidia site. Hope this helps http://pastebin.com/eAqxzaWT (http://pastebin.com/eAqxzaWT)

BTW I've done separate/simultaneous activities regarding compilation and installtion

To Rich and Misalf: I cannot run the create-nvidia-raw it returned me again the error "Cannot build kernel module"

To Juanito: I load both xorg-7.7.3d and nvidia-173.14.39-3.16.6-tinycore.tcz at CLI. It just says OK dont know if its working. When shud I run the patch shud I chmod it to shell executable? BTW I have only 32-bit machine. The 300 series is for 64-bit

To jls_legalize: I already installed tc-ext-tools. Why I got warning
Quote
sh: .: line 28: can't open '/etc/init.d/tet-functions'
how can I uninstall it? Kindly review my PM
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 13, 2015, 02:01:08 PM
I load both xorg-7.7.3d and nvidia-173.14.39-3.16.6-tinycore.tcz at CLI. It just says OK dont know if its working. When shud I run the patch shud I chmod it to shell executable? BTW I have only 32-bit machine. The 300 series is for 64-bit

nvidia-173.14.39-3.16.6-tinycore should contain everything you need (and it is 32-bit) - the first thing to try is "sudo modprobe nvidia" and check for error messages at the console and in dmesg.

If this works OK, then you need to create an /etc/X11/xorg.conf.d/20-nvidia.conf as per a few posts ago and then try "xorg -nolisten tcp" and report any errors.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 13, 2015, 03:23:14 PM
Ok I've been testing the Legacy nvidia-340 driver "nvidia-340.76-3.16.6-tinycore.tcz" using my oldest notebook which uses an Nvidia GTX 260m card and the preliminary results are good  :)

but first..

I had to make a dep file
nvidia-340.76-3.16.6-tinycore.tcz.dep
Code: [Select]
graphics-3.16.6-tinycore.tcz
gtk2.tcz
shared-mime-info.tcz
pkg-config.tcz
xorg-server-dev.tcz


next I rm -f ~/.xsession
Then loaded the following using tce-load -i
nvidia-xorg-conf.tcz  (this is my old working /etc/X11 config file from a previous tc5 / nvidia install whether I needed it or not is still untested)
nvidia-340.76-3.16.6-tinycore.tcz  (without symlinks)
Xorg-7.7-3d.tcz
startx

And Xorg-7.7-3d loaded using the nvidia-340.x.x driver also loading the Nvidia VDPAU driver

:D

Attached are the most important extracts of the logs I captured

notice that nvidia-smi will not run because of missing libnvidia-ml.so module, and
without the symlinks as per the read-me file Xorg is (if I read this correctly) using software GLX rendering..?

Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 13, 2015, 04:05:42 PM
nvidia-340.76-3.16.6-tinycore Legacy driver extension

using nvidia-xconfig to make a correct /etc/X11/xorg.conf file works great also

create dep file
nvidia-340.76-3.16.6-tinycore.tcz.dep
Code: [Select]
graphics-3.16.6-tinycore.tcz
gtk2.tcz
shared-mime-info.tcz
pkg-config.tcz
xorg-server-dev.tcz


Code: [Select]
tce-load -i nvidia-340.76-3.16.6-tinycore.tcz
tce-load -i Xorg-7.7-3d.tcz
sudo mkdir -p /etc/X11
sudo nvidia-xconfig
startx

Things still to do are
make desktop file
resolve GLX symlinks


Thanks Juanito,  I wondered if you had any trouble compiling the legacy driver?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 13, 2015, 04:22:06 PM
There was the same kernel kdrive (test -e blah blah) error, but no problems to compile it other than that.
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: coreplayer2 on June 13, 2015, 11:10:42 PM
Thats good news  8)

Meanwhile I added a startup file; if /etc/X11/xorg.conf file is not found then a new xorg.conf file is created and works well even on my difficult to configure notebook with it's 192x1200 screen
Code: [Select]
#!/bin/sh
#ln -sf /usr/local/lib/xorg/modules/extensions/libglx.so.340.76 /usr/local/lib/xorg/modules/extensions/libglx.so
[ -f /usr/local/lib/libGL.so.1 ] || ln -sf /usr/local/lib/libGL.so.340.76 /usr/local/lib/libGL.so.1
[ -f /usr/local/lib/libGL.so ] || ln -sf /usr/local/lib/libGL.so.1 /usr/local/lib/libGL.so

[ -d /etc/X11 ] || mkdir -p /etc/X11
while [ ! -f /etc/X11/xorg.conf ]; do
nvidia-xconfig
done

with the above startup file I load only these two extensions in the onboot.lst then xorg boots to a desktop using the nvidia driver
Code: [Select]
nvidia-340.76-3.16.6-tinycore.tcz
Xorg-7.7-3d.tcz



The Nvidia adapter driver and nvidia VDPAU driver work fine, though there are a couple of minor details..

Because of the lack of GLX module xorg looks for a software glx, but module is missing..?
Code: [Select]
[    21.748] (II) AIGLX: Screen 0 is not DRI2 capable
[    21.748] (EE) AIGLX: reverting to software rendering
[    21.748] (EE) AIGLX error: dlopen of /usr/local/lib/dri/swrast_dri.so failed (/usr/local/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
[    21.748] (EE) GLX: could not load software renderer
[    21.748] (II) GLX: no usable GL providers found for screen 0


Also missing is nvidia-application-profiles-340.76-key-documentation which causes nvidia-settings (the only reason for a desktop file btw) to use default profile
Code: [Select]
ERROR: nvidia-settings could not find the registry key file. This file should have been installed along with this driver at either
       /usr/share/nvidia/nvidia-application-profiles-340.76-key-documentation or /usr/share/nvidia/nvidia-application-profiles-key-documentation.
I couldn't find either softwware glx or profile in the extension

Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Juanito on June 14, 2015, 05:33:57 AM
I added:

* libnvidia-ml.so symlink
* start-up script
* dep file
* nvidia-application-profiles-340.76-key-documentation
* renamed *desktop file

..and reposted the extension.

Note that your start-up script has commented out the creation of the libglx symlink and the libGL symlinks will only be created if they don't exist - maybe you could force these to test hardware acceleration?
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on August 09, 2015, 10:29:26 AM
Hello, everybody this is how I've gone so far now. And I need my OpenGL to work.
(http://i57.tinypic.com/dbtm4l.png)

But my game is crashing
(http://i61.tinypic.com/2s1vgba.png)

Code: [Select]
Wine cannot find the ncurses library (libncurses.so.5).
err:ole:CoCreateInstance apartment not initialised
err:winediag:X11DRV_WineGL_InitOpenglInfo The Mesa OpenGL driver is using software rendering, most likely your OpenGL drivers haven't been installed correctly (using GL renderer "Software Rasterizer", version "2.1 Mesa 7.8.1").
fixme:advapi:SetSecurityInfo stub
fixme:d3d_caps:wined3d_guess_card No card selector available for GL vendor 0x4 and card vendor 0000 (using GL_RENDERER "Software Rasterizer").
fixme:win:EnumDisplayDevicesW ((null),0,0x33f33c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33f5e4,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33f61c,0x00000000), stub!
tc@box:~$ Xlib: sequence lost (0x10000 > 0x73) in reply type 0x3!
Xlib: sequence lost (0x10000 > 0x7a) in reply type 0x0!
X Error of failed request:  0
  Major opcode of failed request:  91 (X_QueryColors)
  Serial number of failed request:  0
  Current serial number in output stream:  122


I also noticed that my libwfb.so is not symlink to libnvidia-wfb.so.173.14.39
Code: [Select]
tc@box:/usr/local/lib/X11/modules$ ls -l
total 16
drwxr-xr-x    2 root     root           340 May 28  2010 dri/
drwxr-sr-x    2 tc       staff         1700 Aug  9 21:20 drivers/
drwxr-sr-x    2 tc       staff          260 Aug  9 21:20 extensions/
drwxr-xr-x    2 root     root           400 May 28  2010 input/
lrwxrwxrwx    1 root     root            60 Aug  9 21:13 libexa.la -> /tmp/tcloop/Xorg-7.5-dev/usr/local/lib/X11/modules/libexa.la
lrwxrwxrwx    1 root     root            56 Aug  9 21:13 libexa.so -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/libexa.so
lrwxrwxrwx    1 root     root            59 Aug  9 21:13 libfb.la -> /tmp/tcloop/Xorg-7.5-dev/usr/local/lib/X11/modules/libfb.la
lrwxrwxrwx    1 root     root            55 Aug  9 21:13 libfb.so -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/libfb.so
lrwxrwxrwx    1 root     root            62 Aug  9 21:13 libint10.la -> /tmp/tcloop/Xorg-7.5-dev/usr/local/lib/X11/modules/libint10.la
lrwxrwxrwx    1 root     root            58 Aug  9 21:13 libint10.so -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/libint10.so
lrwxrwxrwx    1 root     root            88 Aug  9 21:22 libnvidia-wfb.so.1 -> /tmp/tcloop/nvidia-173.14.39-3.0.3-tinycore/usr/local/lib/X11/modules/libnvidia-wfb.so.1
lrwxrwxrwx    1 root     root            96 Aug  9 21:22 libnvidia-wfb.so.173.14.39 -> /tmp/tcloop/nvidia-173.14.39-3.0.3-tinycore/usr/local/lib/X11/modules/libnvidia-wfb.so.173.14.39
lrwxrwxrwx    1 root     root            63 Aug  9 21:13 libshadow.la -> /tmp/tcloop/Xorg-7.5-dev/usr/local/lib/X11/modules/libshadow.la
lrwxrwxrwx    1 root     root            59 Aug  9 21:13 libshadow.so -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/libshadow.so
lrwxrwxrwx    1 root     root            65 Aug  9 21:13 libshadowfb.la -> /tmp/tcloop/Xorg-7.5-dev/usr/local/lib/X11/modules/libshadowfb.la
lrwxrwxrwx    1 root     root            61 Aug  9 21:13 libshadowfb.so -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/libshadowfb.so
lrwxrwxrwx    1 root     root            60 Aug  9 21:13 libvbe.la -> /tmp/tcloop/Xorg-7.5-dev/usr/local/lib/X11/modules/libvbe.la
lrwxrwxrwx    1 root     root            56 Aug  9 21:13 libvbe.so -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/libvbe.so
lrwxrwxrwx    1 root     root            62 Aug  9 21:13 libvgahw.la -> /tmp/tcloop/Xorg-7.5-dev/usr/local/lib/X11/modules/libvgahw.la
lrwxrwxrwx    1 root     root            58 Aug  9 21:13 libvgahw.so -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/libvgahw.so
lrwxrwxrwx    1 root     root            60 Aug  9 21:13 libwfb.la -> /tmp/tcloop/Xorg-7.5-dev/usr/local/lib/X11/modules/libwfb.la
lrwxrwxrwx    1 root     root            56 Aug  9 21:13 libwfb.so -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/libwfb.so
lrwxrwxrwx    1 root     root            60 Aug  9 21:13 libxaa.la -> /tmp/tcloop/Xorg-7.5-dev/usr/local/lib/X11/modules/libxaa.la
lrwxrwxrwx    1 root     root            56 Aug  9 21:13 libxaa.so -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/libxaa.so
lrwxrwxrwx    1 root     root            66 Aug  9 21:13 libxf8_16bpp.la -> /tmp/tcloop/Xorg-7.5-dev/usr/local/lib/X11/modules/libxf8_16bpp.la
lrwxrwxrwx    1 root     root            62 Aug  9 21:13 libxf8_16bpp.so -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/libxf8_16bpp.so
drwxr-xr-x    2 root     root            80 May 28  2010 linux/
drwxr-xr-x    2 root     root           440 May 28  2010 multimedia/
lrwxrwxrwx    1 root     root            57 Aug  9 21:13 v10002d.uc -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/v10002d.uc
lrwxrwxrwx    1 root     root            57 Aug  9 21:13 v20002d.uc -> /tmp/tcloop/Xorg-7.5/usr/local/lib/X11/modules/v20002d.uc
Title: Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on August 09, 2015, 10:30:25 AM
This is my Xorg.0.log
Code: [Select]
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33.3-tinycore i686
Current Operating System: Linux box 3.0.3-tinycore #90210 SMP Thu Aug 18 11:28:07 EEST 2011 i686
Kernel command line: initrd=/tce/boot/tinycore.gz quiet swapfile=UUID=48a2aff6-701d-468f-8e45-4c3cd727215f home=UUID=80a71a3b-dd34-4cfa-a927-a8dec4c18463 opt=UUID=80a71a3b-dd34-4cfa-a927-a8dec4c18463 pause showapps i8042.nopnp waitusb=5:UUID="80a71a3b-dd34-4cfa-a927-a8dec4c18463" tce=UUID="80a71a3b-dd34-4cfa-a927-a8dec4c18463" BOOT_IMAGE=/tce/boot/vmlinuz
Build Date: 28 May 2010  06:50:29PM
 
Current version of pixman: 0.30.0
        Before reporting problems, check www.tinycorelinux.com
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug  9 21:23:06 2015
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(==) Not automatically adding devices
(==) Not automatically enabling devices
(WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/local/lib/X11/fonts/100dpi/" does not exist.
        Entry deleted from font path.
(==) FontPath set to:
        /usr/local/lib/X11/fonts/misc/,
        /usr/local/lib/X11/fonts/TTF/,
        /usr/local/lib/X11/fonts/Type1/,
        /usr/local/lib/X11/fonts/75dpi/
(==) ModulePath set to "/usr/local/lib/X11/modules"
(II) Loader magic: 0x819471c
(II) Module ABI versions:
        X.Org ANSI C Emulation: 0.4
        X.Org Video Driver: 6.0
        X.Org XInput driver : 7.0
        X.Org Server Extension : 2.0
(--) using VT number 2

(--) PCI:*(0:1:0:0) 10de:0326:0000:0000 rev 161, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) LoadModule: "extmod"
(II) Loading /usr/local/lib/X11/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/local/lib/X11/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/local/lib/X11/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 1.0.0
        ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/local/lib/X11/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 1.0.0
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/local/lib/X11/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 1.1.0
        ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(II) Loading /usr/local/lib/X11/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
        compiled for 4.0.2, module version = 1.0.0
        Module class: X.Org Video Driver
(II) LoadModule: "kbd"
(II) Loading /usr/local/lib/X11/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 1.4.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 7.0
(II) LoadModule: "mouse"
(II) Loading /usr/local/lib/X11/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 1.5.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 7.0
(II) NVIDIA dlloader X Driver  173.14.39  Wed Nov 27 15:02:30 PST 2013
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/local/lib/X11/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 1.0.0
        ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/local/lib/X11/modules/libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 1.0.0
        ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Enabling RENDER acceleration
(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
(EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
(EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
(EE) NVIDIA(0):     you continue to encounter problems, Please try
(EE) NVIDIA(0):     reinstalling the NVIDIA driver.
(II) NVIDIA(0): NVIDIA GPU GeForce FX 5500 (NV34) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 262144 kBytes
(--) NVIDIA(0): VideoBIOS: 04.34.20.69.00
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce FX 5500 at PCI:1:0:0:
(--) NVIDIA(0):     LG L1730S (CRT-0)
(--) NVIDIA(0): LG L1730S (CRT-0): 350.0 MHz maximum pixel clock
(II) NVIDIA(0): Assigned Display Device: CRT-0
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0):     will be used as the requested mode.
(==) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0):     "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
(--) NVIDIA(0): DPI set to (95, 96); computed from "UseEdidDpi" X config
(--) NVIDIA(0):     option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) NVIDIA(0): Initialized AGP GART.
(II) NVIDIA(0): Unable to connect to the ACPI daemon; the ACPI daemon may not
(II) NVIDIA(0):     be running or the "AcpidSocketPath" X configuration option
(II) NVIDIA(0):     may not be set correctly.  When the ACPI daemon is
(II) NVIDIA(0):     available, the NVIDIA X driver can use it to receive ACPI
(II) NVIDIA(0):     events.  For details, please see the "ConnectToAcpid" and
(II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0):     Config Options in the README.
(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/local/lib/X11/modules/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "XkbRules" "base"
(**) Keyboard0: XkbRules: "base"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard0: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(**) Option "Protocol" "auto"
(**) Option "Device" "/dev/psaux"
(II) Mouse0: Setting mouse protocol to "ExplorerPS/2"
(**) Mouse0: Device: "/dev/psaux"
(**) Mouse0: Protocol: "auto"
(**) Option "CorePointer"
(**) Mouse0: always reports core events
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons" "no"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse0: ZAxisMapping: buttons 4 and 5
(**) Mouse0: Buttons: 9
(**) Mouse0: Sensitivity: 1
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(**) Mouse0: (accel) keeping acceleration scheme 1
(**) Mouse0: (accel) acceleration profile 0
(II) Mouse0: Setting mouse protocol to "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded
(II) UnloadModule: "kbd"
(II) UnloadModule: "mouse"
(II) NVIDIA(0): Initialized AGP GART.
(II) NVIDIA(0): Unable to connect to the ACPI daemon; the ACPI daemon may not
(II) NVIDIA(0):     be running or the "AcpidSocketPath" X configuration option
(II) NVIDIA(0):     may not be set correctly.  When the ACPI daemon is
(II) NVIDIA(0):     available, the NVIDIA X driver can use it to receive ACPI
(II) NVIDIA(0):     events.  For details, please see the "ConnectToAcpid" and
(II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0):     Config Options in the README.
(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(**) NVIDIA(0): DPMS enabled
(==) RandR enabled
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/local/lib/X11/modules/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "XkbRules" "base"
(**) Keyboard0: XkbRules: "base"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard0: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) Mouse0: Setting mouse protocol to "ExplorerPS/2"
(**) Mouse0: Device: "/dev/psaux"
(**) Mouse0: Protocol: "auto"
(**) Option "CorePointer"
(**) Mouse0: always reports core events
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons" "no"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse0: ZAxisMapping: buttons 4 and 5
(**) Mouse0: Buttons: 9
(**) Mouse0: Sensitivity: 1
(**) Mouse0: (accel) keeping acceleration scheme 1
(**) Mouse0: (accel) acceleration profile 0
(II) Mouse0: Setting mouse protocol to "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded
Title: [SOLVED] Re: NVIDIA-Linux-x86-173.14.39-pkg1.run
Post by: Stone.Giant on August 16, 2015, 05:04:45 AM
The long wait is over, NVIDIA-Linux-x86-173.14.39-pkg1 is now an extension. Note: For TC 4.0 kernel 3.0.3 only. Available on the tiny core repo soon.

For those who want to beta test and report some irregularity kindly download the file at  http://s000.tinyupload.com/?file_id=08523192522053129820 (http://s000.tinyupload.com/?file_id=08523192522053129820)

Supported Products:

Quote
GeForce 200 Series:

GeForce GTX 280, GeForce GTX 260
GeForce 9 Series:

GeForce 9800 GX2, GeForce 9800 GTX/GTX+, GeForce 9800 GT, GeForce 9600 GT, GeForce 9600 GSO, GeForce 9500 GT
GeForce 8 Series:

GeForce 8800 Ultra, GeForce 8800 GTX, GeForce 8800 GTS 512, GeForce 8800 GTS, GeForce 8800 GT, GeForce 8800 GS, GeForce 8600 GTS, GeForce 8600 GT, GeForce 8600 GS, GeForce 8500 GT, GeForce 8400 GS, GeForce 8400 SE, GeForce 8400, GeForce 8300 GS, GeForce 8300, GeForce 8200, GeForce 8200 /nForce 730a, GeForce 8100 /nForce 720a
GeForce 7 Series:

GeForce 7025 / NVIDIA nForce 630a, GeForce 7050 PV / NVIDIA nForce 630a, GeForce 7050 / NVIDIA nForce 610i, GeForce 7050 / NVIDIA nForce 630i, GeForce 7100 / NVIDIA nForce 630i, GeForce 7100 / NVIDIA nForce 620i, GeForce 7100 GS, GeForce 7150 / NVIDIA nForce 630i, GeForce 7300 SE / 7200 GS, GeForce 7300 LE, GeForce 7300 GS, GeForce 7300 GT, GeForce 7350 LE, GeForce 7500 LE, GeForce 7550 LE, GeForce 7600 LE, GeForce 7600 GS, GeForce 7600 GT, GeForce 7650 GS, GeForce 7800 GS, GeForce 7800 GTX, GeForce 7800 SLI, GeForce 7900 GS, GeForce 7900 GT/GTO, GeForce 7900 GTX, GeForce 7950 GT, GeForce 7950 GX2
GeForce 6 Series:

GeForce 6100, GeForce 6100 nForce 400, GeForce 6100 nForce 405, GeForce 6100 nForce 420, GeForce 6150, GeForce 6150 LE, GeForce 6150LE / Quadro NVS 210S , GeForce 6150SE nForce 430, GeForce 6200, GeForce 6200 A-LE, GeForce 6200 LE, GeForce 6200 TurboCache(TM), GeForce 6200SE TurboCache(TM), GeForce 6250, GeForce 6500, GeForce 6600, GeForce 6600 GT, GeForce 6600 LE, GeForce 6600 VE, GeForce 6610 XL, GeForce 6700 XL, GeForce 6800, GeForce 6800 GS, GeForce 6800 GS/XT, GeForce 6800 GT, GeForce 6800 LE, GeForce 6800 Ultra, GeForce 6800 XE, GeForce 6800 XT
GeForce 5 FX Series:

GeForce FX 5100, GeForce FX 5200, GeForce FX 5200 Ultra, GeForce FX 5200LE, GeForce FX 5500, GeForce FX 5600, GeForce FX 5600 Ultra, GeForce FX 5600XT, GeForce FX 5700, GeForce FX 5700 Ultra, GeForce FX 5700LE, GeForce FX 5700VE, GeForce FX 5800, GeForce FX 5800 Ultra, GeForce FX 5900, GeForce FX 5900 Ultra, GeForce FX 5900XT, GeForce FX 5900ZT, GeForce FX 5950 Ultra, GeForce PCX 5300, GeForce PCX 5750, GeForce PCX 5900
Quadro FX Series:

Quadro FX 330, Quadro FX 350, Quadro FX 370, Quadro FX 500/FX 600, Quadro FX 540, Quadro FX 550, Quadro FX 560, Quadro FX 570, Quadro FX 700, Quadro FX 1000, Quadro FX 1100, Quadro FX 1300, Quadro FX 1400, Quadro FX 1700, Quadro FX 1500, Quadro FX 2000, Quadro FX 3000, Quadro FX 3400/4400, Quadro FX 3450, Quadro FX 3500, Quadro FX 3700, Quadro FX 4000, Quadro FX 4500, Quadro FX 4500 X2, Quadro FX 4600, Quadro FX 4700 X2, Quadro FX 5500, Quadro FX 5600
Quadro FX Series (Notebooks):

Quadro FX 3600M, Quadro FX 2700M, Quadro FX 1700M, Quadro FX 1600M, Quadro FX 570M, Quadro FX 370M, Quadro FX 360M
Quadro NVS Series:

Quadro NVS 285, Quadro NVS 290, Quadro NVS 440
Quadro Plex Series:

Quadro Plex Model II, Quadro Plex Model IV
Quadro Sync Series:

Quadro G-Sync II, Quadro G-Sync I
Quadro SDI:

Quadro SDI
NVS Series:

Quadro NVS 285, Quadro NVS 290, Quadro NVS 440
C-Class:

Tesla C870


(http://i62.tinypic.com/3589gud.png)
(http://i60.tinypic.com/2epspl4.png)


Admin kindly marked this as SOLVED