Package Details: gasket-dkms-git r236.5815ee3-1

Git Clone URL: https://aur.archlinux.org/gasket-dkms-git.git (read-only, click to copy)
Package Base: gasket-dkms-git
Description: Google Coral driver for PCIe-based Edge TPU devices, such as the M.2 and Mini PCIe Accelerator, Git version
Upstream URL: https://coral.withgoogle.com/
Licenses: GPL2
Conflicts: gasket
Provides: gasket
Submitter: mjc506
Maintainer: mjc506
Last Packager: mjc506
Votes: 5
Popularity: 1.18
First Submitted: 2023-09-30 19:04 (UTC)
Last Updated: 2024-11-29 21:04 (UTC)

Latest Comments

1 2 3 Next › Last »

daba commented on 2025-01-26 20:28 (UTC) (edited on 2025-01-26 20:29 (UTC) by daba)

I see, thank you.

I was following the AUR wiki (https://wiki.archlinux.org/title/Arch_User_Repository) for installing gasket-dkms-git. It mentions base-devel, but not the kernel headers.

It seems the installation of DKMS kernel modules requires installation of the kernel headers in addition to the dkms package itself. To the unaccustomed that is somewhat intransparent and not obvious. I assume most users intending on installing gasket-dkms-git probably won't be starting on the DKMS wiki page. It would be great if that information was easily discoverable going through the installation process.

It also wasn't obvious that the installation actually failed. The error messages are somewhat hidden among a bunch of other messages. For someone unaccustomed with DKMS modules it may not be obvious that something went wrong or what to do to resolve it. It wasn't for me at first. I went through a series of debugging steps trying to verify the installation (e.g. ls /dev/apex*, lsmod | grep apex, lsmod | grep gasket, dkms status) to recognize that it appears like the modules weren't actually installed correctly (and go back to the build and installation steps to see if anything went wrong there).

Not sure what to do about this either though. I recognize that this is probably outside the scope of the maintenance of this package. Which btw, I am grateful for.

mjc506 commented on 2025-01-26 19:56 (UTC)

Sorry, no. AUR guidelines exclude things like base-devel and kernel headers - see https://wiki.archlinux.org/title/Dynamic_Kernel_Module_Support#Installation noting the requirement to select the headers for your kernel - for example, my server has the LTS kernel, others may have the Zen kernel, etc etc.

daba commented on 2025-01-26 19:43 (UTC)

In addition to installing base-devel, a common requirement for all AUR packages to build, I also had to install linux-headers to be able to install the resulting gasket-dkms package. Would listing linux-headers as a dependency of this package be the right thing to do?

GaaH commented on 2024-11-30 07:30 (UTC)

Thank you so much, it works now.

mjc506 commented on 2024-11-29 21:10 (UTC)

Success, patch applied, seems to be working.

Apologies for the delay.

jynx commented on 2024-11-29 19:20 (UTC)

Also lost the /dev/apex_0 device. Looks like there are some issues:

==> dkms install --no-depmod gasket/r236.5815ee3 -k 6.12.1-arch1-1
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/r236.5815ee3/source/dkms.conf)

Error! Bad return status for module build on kernel: 6.12.1-arch1-1 (x86_64)
Consult /var/lib/dkms/gasket/r236.5815ee3/build/make.log for more information.
==> WARNING: `dkms install --no-depmod gasket/r236.5815ee3 -k 6.12.1-arch1-1' exited 10

DKMS make.log for gasket-r236.5815ee3 for kernel 6.12.1-arch1-1 (x86_64)
make: Entering directory '/usr/lib/modules/6.12.1-arch1-1/build'
  CC [M]  /var/lib/dkms/gasket/r236.5815ee3/build/gasket_core.o
  CC [M]  /var/lib/dkms/gasket/r236.5815ee3/build/gasket_ioctl.o
  CC [M]  /var/lib/dkms/gasket/r236.5815ee3/build/gasket_interrupt.o
  CC [M]  /var/lib/dkms/gasket/r236.5815ee3/build/gasket_page_table.o
  CC [M]  /var/lib/dkms/gasket/r236.5815ee3/build/gasket_sysfs.o
  CC [M]  /var/lib/dkms/gasket/r236.5815ee3/build/apex_driver.o
/var/lib/dkms/gasket/r236.5815ee3/build/gasket_core.c:1376:19: error: ‘no_llseek’ undeclared here (not in a function); did you mean ‘noop_llseek’?
 1376 |         .llseek = no_llseek,
      |                   ^~~~~~~~~
      |                   noop_llseek
make[2]: *** [scripts/Makefile.build:229: /var/lib/dkms/gasket/r236.5815ee3/build/gasket_core.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/usr/lib/modules/6.12.1-arch1-1/build/Makefile:1936: /var/lib/dkms/gasket/r236.5815ee3/build] Error 2
make: *** [Makefile:224: __sub-make] Error 2
make: Leaving directory '/usr/lib/modules/6.12.1-arch1-1/build'

GaaH commented on 2024-11-27 08:06 (UTC)

I lost the /dev/apex_0 device, is there an issue with the latest kernel, or something?

mjc506 commented on 2024-06-25 21:09 (UTC)

Understood, yes, headers for your kernel will be required for many (any?) DKMS packages, but I presume that linux-headers required to not be included as a depends is due to the possibility of installing other kernels, which would require their own headers (and not necessarily linux-headers)

Yes, that warning comes from Upstream, I've not put any effort into investigating to be honest, the less I fiddle, the more reliable things should be! ;-)

Sparticuz commented on 2024-06-24 17:48 (UTC) (edited on 2024-06-24 17:48 (UTC) by Sparticuz)

I did not install linux-headers because of the comment below about it not being required. Installing linux-headers fixes those errors, though now getting

(3/4) Install DKMS modules
==> dkms install --no-depmod gasket/r236.5815ee3 -k 6.9.6-arch1-1
Deprecated feature: REMAKE_INITRD (/usr/src/gasket-r236.5815ee3/dkms.conf)
==> depmod 6.9.6-arch1-1

But that seems to be an upstream issue.

mjc506 commented on 2024-06-24 16:58 (UTC)

Huh weird, it seems to be listing your root dir?

Do you have the kernel headers for your running kernel installed? (optional requirement for dkms, probably linux-headers unless you're running a different kernel)

1 2 3 Next › Last »