nvidia-kernel-dkms 340.65-2~bpo70+1 doesn't build with pve-kernel-2.6.32-43-pve

rubictus

Member
Nov 3, 2015
5
0
21
nvidia-kernel-dkms 340.65-2~bpo70+1 (from wheezy-backport) doesn't build with pve-kernel-2.6.32-43-pve. With pve-kernel-2.6.32-42-pve and below, building module nvidia was always fine.


Packages installed :

Code:
 ii  nvidia-kernel-common                  20120630+3                         amd64        NVIDIA binary kernel module support files
 ii  nvidia-kernel-dkms                    340.65-2~bpo70+1                   amd64        NVIDIA binary kernel module DKMS source
 ii  nvidia-modprobe                       334.16-1~bpo70+1                   amd64        utility to load NVIDIA kernel modules and create device nodes
 ii  pve-firmware                          1.1-4                              all          Binary firmware code for the pve-kernel
 ii  pve-kernel-2.6.32-41-pve              2.6.32-164                         amd64        The Proxmox PVE Kernel Image
 ii  pve-kernel-2.6.32-42-pve              2.6.32-165                         amd64        The Proxmox PVE Kernel Image
 ii  pve-kernel-2.6.32-43-pve              2.6.32-166                         amd64        The Proxmox PVE Kernel Image
 ii  pve-headers-2.6.32-41-pve             2.6.32-164                         amd64        The Proxmox PVE Kernel Headers
 ii  pve-headers-2.6.32-42-pve             2.6.32-165                         amd64        The Proxmox PVE Kernel Headers
 ii  pve-headers-2.6.32-43-pve             2.6.32-166                         amd64        The Proxmox PVE Kernel Headers

'dpkg-reconfigure nvidia-kernel-dkms' fails with the new kernel 2.6.32-43 and says to see /var/lib/dkms/nvidia-current/340.65/build/make.log (Join in attachments View attachment make.log.zip).
But i'm not enough expert to understand what appends.

Thanks for help.
 
Last edited:
I have succeeded to investigate.
Seems to results from changes to the file /usr/src/linux-headers-2.6.32-43-pve/include/linux/string.h. These lines were added in pve-headers-2.6.32-43 :


Code:
/**
 * kbasename - return the last part of a pathname.
 *
 * @path: path to extract the filename from.
 */
static inline const char *kbasename(const char *path)
{
        const char *tail = strrchr(path, '/');
        return tail ? tail + 1 : path;
}

Removing them, nvidia module builds now fine again.


Many files in /usr/src/linux-headers-2.6.32-43-pve/ belongs to user uid 1000, group id 1000. I'm thinking it should be root.


How to report that things to proxmox' team ?


Thanks.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!