search

google-coral / edgetpu

Coral issue tracker (and legacy Edge TPU API source)
https://coral.ai
Apache License 2.0
422 stars 124 forks source link

Problem to install these two Libraries: gasket-dkms libedgetpu1-std #478

Open ghost opened 3 years ago

ghost commented 3 years ago

Good morning, I have problems installing the two libraries on my ARM64 computer because the software searches for the "aarch64" infrastructure according to "uname -machine" instead of the "arm64" propagated by the Ubuntu 21.04 operating system.

The command: lspci -nn | grep 089a brings the correct information regarding the hardware:

01:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]

Are there any drivers that do NOT have this problem? I would be very happy if someone can help me here, because I would like to use this card in my small LABOR cluster on TPU /GPU server under SLURM.

The background for this is that I would like to use it very much for the project "Human Brain /Human Robotics" and use it on the different robots.

It is really important for me because there is a lot of research behind this. Many thanks in advance.....

Z. Matthias

manoj7410 commented 3 years ago

@Zhexue-M Do you see any error ? Can you paste the error here ?

ghost commented 3 years ago

Yes, I see the Error-Message:

DKMS make.log for gasket-1.0 for kernel 5.13.0-1007-raspi (aarch64) Wed Sep 29 01:17:36 PM UTC 2021 make: Entering directory '/usr/src/linux-headers-5.13.0-1007-raspi' Makefile:710: arch//Makefile: No such file or directory make: *** No rule to make target 'arch//Makefile'. Stop. make: Leaving directory '/usr/src/linux-headers-5.13.0-1007-raspi'

And this is, if I want to install it:

Get:1 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 dkms all 2.8.4-4ubuntu1 [69.6 kB] Fetched 69.6 kB in 1s (130 kB/s) Selecting previously unselected package dctrl-tools. (Reading database ... 139791 files and directories currently installed.) Preparing to unpack .../dctrl-tools_2.24-3_arm64.deb ... Unpacking dctrl-tools (2.24-3) ... Selecting previously unselected package dkms. Preparing to unpack .../dkms_2.8.4-4ubuntu1_all.deb ... Unpacking dkms (2.8.4-4ubuntu1) ... Selecting previously unselected package gasket-dkms. Preparing to unpack .../gasket-dkms_1.0-17_all.deb ... Unpacking gasket-dkms (1.0-17) ... Selecting previously unselected package libedgetpu1-std:arm64. Preparing to unpack .../libedgetpu1-std_16.0_arm64.deb ... Unpacking libedgetpu1-std:arm64 (16.0) ... Setting up libedgetpu1-std:arm64 (16.0) ... Setting up dctrl-tools (2.24-3) ... Setting up dkms (2.8.4-4ubuntu1) ... Setting up gasket-dkms (1.0-17) ... Loading new gasket-1.0 DKMS files... Building for 5.13.0-1007-raspi Building initial module for 5.13.0-1007-raspi ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gasket-dkms.0.crash' Error! Bad return status for module build on kernel: 5.13.0-1007-raspi (aarch64) Consult /var/lib/dkms/gasket/1.0/build/make.log for more information. dpkg: error processing package gasket-dkms (--configure): installed gasket-dkms package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.9.4-2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Errors were encountered while processing: gasket-dkms needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1)

manoj7410 commented 3 years ago

@Zhexue-M Are there any steps to reproduce this ? Which hardware are you working with?

magic-blue-smoke commented 3 years ago

Yes, I see the Error-Message:

DKMS make.log for gasket-1.0 for kernel 5.13.0-1007-raspi (aarch64) Wed Sep 29 01:17:36 PM UTC 2021 make: Entering directory '/usr/src/linux-headers-5.13.0-1007-raspi' Makefile:710: arch//Makefile: No such file or directory make: *** No rule to make target 'arch//Makefile'. Stop. make: Leaving directory '/usr/src/linux-headers-5.13.0-1007-raspi'

Currently Raspberry Pi CM4 and Coral TPU are not working together on PCIe

ghost commented 3 years ago

Hello together, sorry for my delay, but I had so many Presentation about AI, etc. and there was no time to write back so far.

So, that is NOT my problem. I had it on several machine, like RADXA RockPI4, Raspberry PI include CM4 with M.2 and with the USB - Card. The Reason is, that all the system said, that they are an "AARCH64" - Infrastrucutre they had, but on LINUX-Distribution it's call as ARM64...... That is the IMPORTANT Point, not that is not working on..... I want to habe driver, system where no installation problems are coming out.

Is this possible to do or to show, what kind of problem that here is? Best regards

Z. Matthias

ghost commented 3 years ago

In Addition of my Message. Please make a look on my Message about the Error - Message. On Line 1 "Get 1 ...." you see, that your software seem, that is is an ARM64 - System.... Later you see, that your system want to build it for aarch64. This is the point, that I had on several systems....

magic-blue-smoke commented 3 years ago

@Zhexue-M This is the issue for RPi CM4 and m.2 card: https://github.com/google-coral/edgetpu/issues/280

As for other cases (including USB accelerator and other platforms), it should work, but I didn’t try that to tell for sure

ghost commented 3 years ago

Hey, that is not true. On my RockPI - System is this the same. The big reason is, that ARM64 and AARCH64 doesn't match so far and that is the point.... Sorry..