Update Error with Coral TPU Drivers

P

pageb018

New Member
Jun 13, 2022
2
0
1
I am trying to update Promox and I seem to be getting a kernel error due to the Coral PTU gasket driver. I am not exactly sure how to proceed.

Code: 
root@pve01:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up proxmox-kernel-6.5.11-3-pve (6.5.11-3) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.5.11-3-pve /boot/vmlinuz-6.5.11-3-pve
dkms: running auto installation service for kernel 6.5.11-3-pve.
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)
Deprecated feature: REMAKE_INITRD (/etc/dkms/framework.conf)
Sign command: /lib/modules/6.5.11-3-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)

Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.5.11-3-pve -C /lib/modules/6.5.11-3-pve/build M=/var/lib/dkms/gasket/1.0/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.11-3-pve (x86_64)
Consult /var/lib/dkms/gasket/1.0/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.11-3-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.5.11-3-pve.postinst line 20.
dpkg: error processing package proxmox-kernel-6.5.11-3-pve (--configure):
 installed proxmox-kernel-6.5.11-3-pve package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.5:
 proxmox-kernel-6.5 depends on proxmox-kernel-6.5.11-3-pve; however:
  Package proxmox-kernel-6.5.11-3-pve is not configured yet.

dpkg: error processing package proxmox-kernel-6.5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.5; however:
  Package proxmox-kernel-6.5 is not configured yet.

dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-6.5.11-3-pve
 proxmox-kernel-6.5
 proxmox-default-kernel
E: Sub-process /usr/bin/dpkg returned an error code (1)


PVE headers and the TPU driver are all up to to date. Maybe the driver isn't support with the newer kernel?

Any ideas? Thanks!
 
pageb018 said:
...
Consult /var/lib/dkms/gasket/1.0/build/make.log for more information.
...

PVE headers and the TPU driver are all up to to date. Maybe the driver isn't support with the newer kernel?
Click to expand...
Probably. Maybe check /var/lib/dkms/gasket/1.0/build/make.log? And then search the web and check if there is a new driver version available, from the place where you got the previous one.
 
Last edited:
Same exact issue. I had to uninstall the gasket-dkms package to fix the error, preventing me from using Frigate. Hopefully an update to the driver will fix this. It was last updated in March 2022.
 
shehzman said:
Same exact issue. I had to uninstall the gasket-dkms package to fix the error, preventing me from using Frigate. Hopefully an update to the driver will fix this. It was last updated in March 2022.
Click to expand...
Were you able to reinstall after? I have frigate running on this node in an LXC and don’t want to break the Corral TPU.
 
pageb018 said:
Were you able to reinstall after? I have frigate running on this node in an LXC and don’t want to break the Corral TPU.
Click to expand...
I was able to reinstall, but had to get the gasket kernel module from here instead. I cloned the repo, built the module using the command mentioned in the README (you'll need dh-dkms, dkms, and devscripts packages), and installed the deb file generated by the build (it'll be located in the outer directory of where the build was ran). After a reboot, /dev/apex_0 appeared and Frigate in my LXC detected the Coral TPU.
 
Last edited:
  • Like
Reactions: takeokun and LiloBzH
Hello

same probleme here.
A build new module , install with dpkg -i gasket-dkms_1.0-18_all.deb and it's ok now !

T you :)
 
sorry I'm a noob at all of this...do you have a list of steps on how to do this? I'm trying to get frigate back up after updating proxmox versions

Edit:

I figured it out

  1. install dh-dkms, dkms, and devscripts packages using apt install
  2. download the code, unzip, copy to proxmox installation, cd into the folder you just copied, run "debuild -us -uc -tc -b", cd back into root and install the debian package using "dpkg -i gasket-dkms_1.0-18_all.deb"
 
Last edited:
  • Like
Reactions: vaer
Was having exactly the same issue. This worked to resolve the issue. Steps followed as per @LiloBzH and it worked perfectly.

Lesson for me - don't ignore errors when running updates :)
 
  • Like
Reactions: LiloBzH
LiloBzH said:
yeah

apt remove gasket-dkms
apt install git
apt install devscripts
apt install dh-dkms

In HOME

git clone https://github.com/google/gasket-driver.git
cd gasket-driver/
debuild -us -uc -tc -b
cd..
dpkg -i gasket-dkms_1.0-18_all.deb

apt update && apt upgrade

if no error => reboot !
Click to expand...
Just want to add my thanks to @LiloBzH for the idiot proof instructions. Apex had disappeared from /dev after the upgrade, but this fixed it without any other changes needing to be made.
 
  • Like
Reactions: aabbccdd
LiloBzH said:
yeah

apt remove gasket-dkms
apt install git
apt install devscripts
apt install dh-dkms

In HOME

git clone https://github.com/google/gasket-driver.git
cd gasket-driver/
debuild -us -uc -tc -b
cd..
dpkg -i gasket-dkms_1.0-18_all.deb

apt update && apt upgrade

if no error => reboot !
Click to expand...
For any other dummies like myself that have no business using Linux and thus might get confused about a few things:

In HOME = cd /home (not home as in going to debian's home/root directory).
cd.. = This step should be putting you back in /home and needs a space e.g. cd ..
(the latter was the mistake I made; cd.. didn't work and I just went cd which put me back too far, obviously, yet the dpkg command seemed to run fine or else I'm just extremely thick and skipped that step actually yeah that was it never use CLI when sleep-deprived okay shutting up now)
 
  • Like
Reactions: Kentrath, chadcroft and bawjaws
LiloBzH said:
yeah

apt remove gasket-dkms
apt install git
apt install devscripts
apt install dh-dkms

In HOME

git clone https://github.com/google/gasket-driver.git
cd gasket-driver/
debuild -us -uc -tc -b
cd..
dpkg -i gasket-dkms_1.0-18_all.deb

apt update && apt upgrade

if no error => reboot !
Click to expand...

Everything went well here until running the debuild command above and the result was a dependencies error - can anyone help?

Code: 
root@pve03:~# git clone https://github.com/google/gasket-driver.git
Cloning into 'gasket-driver'...
remote: Enumerating objects: 846, done.
remote: Counting objects: 100% (38/38), done.
remote: Compressing objects: 100% (22/22), done.
remote: Total 846 (delta 17), reused 28 (delta 14), pack-reused 808
Receiving objects: 100% (846/846), 316.76 KiB | 3.17 MiB/s, done.
Resolving deltas: 100% (572/572), done.
root@pve03:~# cd gasket-driver/
root@pve03:~/gasket-driver# debuild -us -uc -tc -b
 dpkg-buildpackage -us -uc -ui -tc -b
dpkg-buildpackage: info: source package gasket-dkms
dpkg-buildpackage: info: source version 1.0-18
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Coral <coral-support@google.com>
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-checkbuilddeps: error: Unmet build dependencies: dkms
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -tc -b failed
 
NOTORIOUS VR said:
Everything went well here until running the debuild command above and the result was a dependencies error - can anyone help?

Code: 
root@pve03:~# git clone https://github.com/google/gasket-driver.git
Cloning into 'gasket-driver'...
remote: Enumerating objects: 846, done.
remote: Counting objects: 100% (38/38), done.
remote: Compressing objects: 100% (22/22), done.
remote: Total 846 (delta 17), reused 28 (delta 14), pack-reused 808
Receiving objects: 100% (846/846), 316.76 KiB | 3.17 MiB/s, done.
Resolving deltas: 100% (572/572), done.
root@pve03:~# cd gasket-driver/
root@pve03:~/gasket-driver# debuild -us -uc -tc -b
 dpkg-buildpackage -us -uc -ui -tc -b
dpkg-buildpackage: info: source package gasket-dkms
dpkg-buildpackage: info: source version 1.0-18
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Coral <coral-support@google.com>
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-checkbuilddeps: error: Unmet build dependencies: dkms
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -tc -b failed
Click to expand...
Only thing off the top of my head is that you're running it from wrong directory. Per my previous comment:
In HOME = cd /home (not home as in going to debian's home/root directory).
Click to expand...
So root@pve3:/home rather than root@pve03:~#.

Note I have no business instructing others in using Linux, but that was my takeaway (and, of course, it worked on my machine™).
 
vaer said:
Only thing off the top of my head is that you're running it from wrong directory. Per my previous comment:

So root@pve3:/home rather than root@pve03:~#.

Note I have no business instructing others in using Linux, but that was my takeaway (and, of course, it worked on my machine™).
Click to expand...
good catch - however no bueno, same issue...

Code: 
root@pve03:/home/gasket-driver# ls -lc
total 36
-rw-r--r-- 1 root root  1101 Dec  4 16:30 CONTRIBUTING.md
drwxr-xr-x 2 root root  4096 Dec  4 16:30 debian
-rw-r--r-- 1 root root 18092 Dec  4 16:30 LICENSE
-rw-r--r-- 1 root root   613 Dec  4 16:30 README.md
drwxr-xr-x 2 root root  4096 Dec  4 16:30 src
root@pve03:/home/gasket-driver# debuild -us -uc -tc -b
 dpkg-buildpackage -us -uc -ui -tc -b
dpkg-buildpackage: info: source package gasket-dkms
dpkg-buildpackage: info: source version 1.0-18
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Coral <coral-support@google.com>
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-checkbuilddeps: error: Unmet build dependencies: dkms
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -tc -b failed
 
NOTORIOUS VR said:
good catch - however no bueno, same issue...

Code: 
root@pve03:/home/gasket-driver# ls -lc
total 36
-rw-r--r-- 1 root root  1101 Dec  4 16:30 CONTRIBUTING.md
drwxr-xr-x 2 root root  4096 Dec  4 16:30 debian
-rw-r--r-- 1 root root 18092 Dec  4 16:30 LICENSE
-rw-r--r-- 1 root root   613 Dec  4 16:30 README.md
drwxr-xr-x 2 root root  4096 Dec  4 16:30 src
root@pve03:/home/gasket-driver# debuild -us -uc -tc -b
 dpkg-buildpackage -us -uc -ui -tc -b
dpkg-buildpackage: info: source package gasket-dkms
dpkg-buildpackage: info: source version 1.0-18
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Coral <coral-support@google.com>
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-checkbuilddeps: error: Unmet build dependencies: dkms
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -tc -b failed
Click to expand...
Feels like you might have missed removing gasket-dkms or adding dh-dkms? Unmet build dependencies: dkms
Reckon you should start again from step one, line by line. Easy to skip a line and miss something.
If that ain't it, sorry I couldn't be more help.
 
vaer said:
Feels like you might have missed removing gasket-dkms or adding dh-dkms? Unmet build dependencies: dkms
Reckon you should start again from step one, line by line. Easy to skip a line and miss something.
If that ain't it, sorry I couldn't be more help.
Click to expand...
Yeah I hear ya - unfortunately I don't believe I missed anything....

Code: 
root@pve03:~# apt remove gasket-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package gasket-dkms
root@pve03:~#
root@pve03:~#
root@pve03:~# apt install dh-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
dh-dkms is already the newest version (3.0.10-8+deb12u1).
The following package was automatically installed and is no longer required:
  pve-kernel-6.2.16-4-pve
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 
NOTORIOUS VR said:
good catch - however no bueno, same issue...

Code: 
root@pve03:/home/gasket-driver# ls -lc
total 36
-rw-r--r-- 1 root root  1101 Dec  4 16:30 CONTRIBUTING.md
drwxr-xr-x 2 root root  4096 Dec  4 16:30 debian
-rw-r--r-- 1 root root 18092 Dec  4 16:30 LICENSE
-rw-r--r-- 1 root root   613 Dec  4 16:30 README.md
drwxr-xr-x 2 root root  4096 Dec  4 16:30 src
root@pve03:/home/gasket-driver# debuild -us -uc -tc -b
 dpkg-buildpackage -us -uc -ui -tc -b
dpkg-buildpackage: info: source package gasket-dkms
dpkg-buildpackage: info: source version 1.0-18
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Coral <coral-support@google.com>
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-checkbuilddeps: error: Unmet build dependencies: dkms
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -tc -b failed
Click to expand...
apt install dkms
 
  • Like
Reactions: Jurich and NOTORIOUS VR
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back