Hi PEAK community,
I host some Linux machines on which I have installed the pcan driver. The installation of the driver works very well with the install and uninstall script provided by PEAK, but sometimes when I perform an apt update + upgrade, I notice that the devices in /dev went missing. This bugs me for weeks since I have to reinstall the driver from scratch after every update.
Is there a way to fix this? I also notice that this event could be correlating with a linux kernel update during apt upgrade. Could be this causing the issue since I can assume that the built device (during installation) is bound to the kernel version (and the newer version repels the old built device)?
If so, what can I do to fix that issue?
Thanks in advance!
yes, when using the peak-linux-driver you have to build and install the driver which each kernel update. Do you use the chardev or SocketCAN option of the driver? If you use SocketCAN, simply uninstall the driver again and reboot the system once to have the kernel intergrated SocketCAN driver active again, than you don't have to take care for the kernel upgrades. If you use the chardev driver, you can also use the dkms option, which is available with the latest peak-linux-driver version (since 8.11). To use this feature, build the driver with the “dkms_install” option, to automatically rebuild the driver with each kernel update.
thanks for the great advice! It seems working now (tested on some focal fossa machines - kernel update from Linux 5.4.0-88-generic
to Linux 5.4.0-90-generic) and my installed driver and libs stayed where they should be!
I used the standard procedure of the chardev installation.
Here the installation steps for everyone:
wget https://www.peak-system.com/fileadmin/m ... 3.0.tar.gz
tar -xf peak-linux-driver-8.13.0.tar
sudo make clean all #This will build all
sudo make install #This will install all on your os
sudo make -C driver install dkms_install #This will overwrite the driver with dkms support
sudo reboot now
dkms status #This should list your items which are managed by DKMS
-> you can perform an update, check the kernel version (with uname -a) and test if this has helped you