Search results for query: gasket

Is your lxc priveleged or unpriv? This didn't work for me on kernel 6.8.4

The instructions I posted are for getting TPU passed into the LXC Container, not through to a VM. Both have different steps and methods. I did not need to blacklist my TPUs (Not the USB or the PCI/M.2). The only thing I have blacklisted if the GPU which I pass into another LXC for running...

...the wrong machine. Have I? EDIT: I've gone back over the install notes for doing Frigate in a VM on Proxmox and they do say to just blacklist gasket and apex on Proxmox, pass them through to the Ubuntu VM and then install the drivers in Ubuntu, so I think I've done the right things. Although...

Thank you for the detailed instructions. This worked for me.

...do is pin to 6.5 for now Google coral driver had a fix pushed TODAY as of a couple hours ago. You'll need to pull current master and rebuild gasket driver Previous SR-IOV workaround for igpus with kernel 6.5 does NOT work on 6.8 and likely never will, see here SR-IOV may be supported OTB with...

Yes, Fixed the typo. Went through the steps and it's working again. Thanks man.. apt remove gasket-dkms apt install dkms lsb-release sudo git dh-dkms devscripts pve-headers git clone https://github.com/KyleGospo/gasket-dkms cd gasket-dkms debuild -us -uc -tc -b cd .. dpkg -i...

This procedure worked for me.

Did you mean 8.1.10 and 8.2.2? If not they are pretty old versions. Just follow @LiloBzH step by step post but replacing the git repository with https://github.com/KyleGospo/gasket-dkms.

Did you try @LiloBzH step by step in the VM? They should work as Ubuntu is a Debian based distro.

...have this problem. Running PVE 8.2, with an Ubuntu 22.04 VM and the apex doesn't show up in the VM. Strangely when I do sudo dpkg-reconfigure gasket-dkms both the TPUs show up as apex devices but as soon as I reboot they're gone again. Anyone got any tips for how to build from the KyleGospo...

Thanks man!

Brilliant, thank you!

I updated to kernel 6.8 and had to build from this repo (https://github.com/KyleGospo/gasket-dkms), since it has robertzaage's latest fix.

...or directory I've tried reinstalling the drivers in the VM, but to no avail. I noticed there were a few threads on here talking about problems with gasket since a recent update of Proxmox, Not sure if there's a known issue? Please can anyone help me figure out what the problem may be? Thanks!

apt install pve-headers apt-get install --reinstall gasket-dkms ( this does not work in latest PROXMOX 8 ) GASKET-DKMS installation in Proxmox 8 apt remove gasket-dkms apt install git apt install devscripts apt install dh-dkms In HOME git clone...

On 6.5.13-5-pve, only got as far as. Subbing for solutions in the future. gasket: module verification failed: signature and/or required key missing - tainting kernel

I needed to use this git repo when building on a recent kernel. This is because the interface for eventfd_signal changed in the kernel git@github.com:robertzaage/gasket-driver.git

Interesting, I do have two ethernet ports, one 1G and one 2.5G. I'm currently using the 2.5G, I'll switch to the 1G and see if that makes any difference. Looks like gasket isn't quite ready on 6.8, which I need for a TPU accelerator, so I'll have to wait on the kernel.

...snd_hwdep cec snd_pcm cmdlinepart rc_core snd_timer intel_cstate spi_nor snd drm_kms_helper apex(OE) mei_me wmi_bmof soundcore mtd gasket(OE) cp210x i2c_algo_bit pcspkr ee1004 mei usbserial intel_pch_thermal joydev input_leds acpi_tad acpi_pad mac_hid zfs(PO) spl(O) vhost_net vhost...

I believe I have implemented the fix for both recent kernels: https://github.com/google/gasket-driver/issues/24#issuecomment-2041102866