nvidia drivers 340.32 installation using chroot debian

Hi everyone,
I’m building a custom debian live distribution which is running from RAM only. It has some access to the network share and some special packages. All this i did using the debirf package. Computers which running this live distro are diskless machines with the Tesla K20m GPU. Using the debirf which uses chroot (i guess) to access the created system I’m able to install the required packages i.e linux-headers, gcc-4.6, make, build-essential even also create the symbolic link for gcc-4.6 which is required for NVIDIA-Linux-x86_64-340.32.run. During the build i get this error

DKMS make.log for nvidia-current-340.32 for kernel 3.2.0-4-amd64 (x86_64)
Sat Nov  1 17:38:33 CET 2014
make: Entering directory `/var/lib/dkms/nvidia-current/340.32/build'
make KBUILD_VERBOSE=1 -C /lib/modules/3.2.0-4-amd64/build M=/var/lib/dkms/nvidi$
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-4-amd64'
make -C /usr/src/linux-headers-3.2.0-4-amd64 \
    KBUILD_SRC=/usr/src/linux-headers-3.2.0-4-common \
    KBUILD_EXTMOD="/var/lib/dkms/nvidia-current/340.32/build" -f /usr/src/l$
    modules
make: file.c:145: enter_file: Assertion `*name != '

DKMS make.log for nvidia-current-340.32 for kernel 3.2.0-4-amd64 (x86_64)
Sat Nov 1 17:38:33 CET 2014
make: Entering directory /var/lib/dkms/nvidia-current/340.32/build' make KBUILD_VERBOSE=1 -C /lib/modules/3.2.0-4-amd64/build M=/var/lib/dkms/nvidi$ make[1]: Entering directory /usr/src/linux-headers-3.2.0-4-amd64’
make -C /usr/src/linux-headers-3.2.0-4-amd64
KBUILD_SRC=/usr/src/linux-headers-3.2.0-4-common
KBUILD_EXTMOD="/var/lib/dkms/nvidia-current/340.32/build" -f /usr/src/l$
modules
make: file.c:145: enter_file: Assertion *name != '\0'' failed. Aborted make[2]: *** [sub-make] Error 134 make[1]: *** [all] Error 2 make[1]: Leaving directory /usr/src/linux-headers-3.2.0-4-amd64’
make: *** [modules] Error 2
make: Leaving directory `/var/lib/dkms/nvidia-current/340.32/build’

'' failed.
Aborted
make[2]: *** [sub-make] Error 134
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64'
make: *** [modules] Error 2
make: Leaving directory `/var/lib/dkms/nvidia-current/340.32/build'

^^^Any ideas about this?^^^

  • The second approach to build the drivers manually inside a running machine was successful. I'm also able to --add-this-kernel and to have already prepared builded drivers. (when i put these pre-build drivers to debirf I got the same error as above appears). After the installation on the headless machines I'm able to run nvidia-detect, nvidia-smi or nvidia-modprobe. the outputs are following:
    nvidia-detect
            No NVIDIA GPU detected.
    
    nvidia-smi
            Unable to determine the device handle for GPU 0000:83:00.0: Unknown Error
    
    nvidia-debugdump -l 
            Found 1 NVIDIA devices
            Error: nvmlDeviceGetHandleByIndex(): Unknown Error
            FAILED to get details on GPU (0x0): Unknown Error
    
    dmesg | grep NVRM
    [ 2400.286037] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.32  Tue Aug  5 20:58:26 PDT 2014
    [ 2405.568003] NVRM: RmInitAdapter failed! (0x26:0xffffffff:1218)
    [ 2405.573892] NVRM: rm_init_adapter failed for device bearing minor number 0
    [ 2405.580824] NVRM: nvidia_frontend_open: minor 0, module->open() failed, error -5
    
    cat /proc/driver/nvidia/gpus/0000\:83\:00.0/information 
    Model:           Tesla K20m
    IRQ:             121
    GPU UUID:        GPU-????????-????-????-????-????????????
    Video BIOS:      ??.??.??.??.??
    Bus Type:        PCIe
    DMA Size:        40 bits
    DMA Mask:        0xffffffffff
    Bus Location:    0000:83:00.0
    
  • Any ideas? Help?

    make: file.c:145: enter_file: Assertion `*name != '\0'' failed.
    Aborted
    

    This looks like a bug in GNU make. I wonder if something about this environment is confusing it.

    Hi Aaron,
    firstly, thanks for the reply. This is the first reply i received on three forums. I received also a reply from nvidia linux bugs, that such installation may be not compatible with the installer. It is a little bit confusing for me, but now I’m focusing on different approach…