What Edge TPU Works with What Hardware/Software

Each Coral product has been tested with specific hardware and software versions.

These development systems must be connected to a host computer:

Product
Host Operating System

USB Accelerator
Ubuntu 18.04 20.04, Debian 10 Buster, Win10 64-bit, Mac 10.15 Catalina

Dev Board
Ubuntu 18.04 20.04, Debian 10 Buster

Dev Board Mini
Ubuntu 18.04 20.04, Debian 10 Buster

These embedded products are connected through an operating system

Product
Embedded Operating System

M.2
Debian 10 Buster, Win10 64-bit

mPCIe
Debian 10 Buster, Win10 64-bit

M.2 dual
Debian 10 Buster, Win10 64-bit

Dev Board
Mendel 5 Eagle (based on Debian 10 Buster)

Dev Board Mini
Mendel 5 Eagle (based on Debian 10 Buster)

Embedded motherboards vary widely in what they are compatible with.   Some M.2 slots could work with more peripheral cards, but have been tailored for a specific purpose.  These systems are known to work with these products:

Product
Tested in Hardware

USB Accelerator
Raspberry Pi 4, 4B  /  Coral Dev Board

M.2 and mPCIe
Asus PE100A /  Nexcom nROK 6222-GCIOT /  Nexcom VTC 7251-GCIoT, Jetson Nano

mPCIe
tested mPCIe to PCIe adapter

M.2 dual
tested nexcom

Thanks @usbguru!!!

Hi @usbguru, are you 100% sure the tested Nexcom NDiS B537 M.2 E-Key slot reported to be compatible with the M.2 Accelerator with Dual Edge TPU has two instances of PCIe x1 lanes?
FWIW, I've plugged a M.2 Accelerator with Dual Edge TPU in a M.2 E-Key to PCIe x1 adapter and obviously, only one TPU device is working:
# lspci | grep Coral
02:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU

Hi, got confirmation from Nexcom that the NDiS B537 M.2 E-Key slot has 2 x PCIe Gen. 3 lanes.

Are there any adapters that work with  M.2 Accelerator with Dual Edge TPU to get use of both TPU's ?

Are there any PCIe adapters that work with M.2 Accelerator with Dual Edge TPU to get use of both TPU's ?

Did not find such an adapter on the market after a somewhat extensive search.
For now, I've collected the following list of devices with explicit M.2 E-Key 2x PCIe support (in addition to the Nexcom NDiS B537 device mentioned above).
Motherboards:

Premio CT-MCL01 (MicroATX LGA-1151) (alternative link)
Supermicro (SuperServer proprietary form factor): X11SDS-8C / X11SDS-12C /  X11SDS-14C /  X11SDS-16C

Computers:

Premio VCO-6131E-4M2 (LGA-1151) (alternative link)
Premio RCO-6120-2060S (alternative link)

Note: Nexcom also manufactures devices with explicit Coral support but they do not mention what model:

Coral From Google Edge TPU processor for AI applications

Through PCI-e accelerator

PS: I will update the list if I find additional devices.

@pdecat
Im going to try this combo. Ill report back and let you know if it works. Im trying to put this in an existing server/pc I have via PCIe..
https://www.amazon.com/gp/product/B07G8N8Y9J?ref=ppx_pt2_dt_b_prod_image + https://www.amazon.com/gp/product/B079NB8J3B/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

@pdecat confirmed adapters work. 1x TPU, but better than nothing.

@pdecat confirmed adapters work. 1x TPU, but better than nothing.

@mitchross
I have a similar experience as you do with the M.2 dual TPU. Only one is visible, but better than 0. Anyone have any ideas/workarounds to expose both TPUs?
 Only one is visible, but better than 0. Anyone have any ideas/workarounds to expose both TPUs?
M.2 adapter https://www.amazon.com/gp/product/B079NB8J3B/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
mated with
SeedStudio Odyssey Blue J4105 https://www.amazon.com/Mini-Odyssey-Blue-J4105-Bluetooth5-0/dp/B08FD3QHQC
running Ubuntu 20.10
ls /dev/apex*
/dev/apex_0
anand@odyssey3:~/IOTstack$ lspci
00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03)
00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 03)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03)
00:0c.0 Network controller: Intel Corporation Device 31dc (rev 03)
00:0e.0 Audio device: Intel Corporation Celeron/Pentium Silver Processor High Definition Audio (rev 03)
00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 03)
00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03)
00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3)
00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3)
00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f3)
00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03)
00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03)
00:17.1 Signal processing controller: Intel Corporation Device 31b6 (rev 03)
00:17.2 Signal processing controller: Intel Corporation Device 31b8 (rev 03)
00:18.0 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Serial IO UART Host Controller (rev 03)
00:18.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Serial IO UART Host Controller (rev 03)
00:18.2 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Serial IO UART Host Controller (rev 03)
00:18.3 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Serial IO UART Host Controller (rev 03)
00:19.0 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Serial IO SPI Host Controller (rev 03)
00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver Processor SDA Standard Compliant SD Host Controller (rev 03)
00:1e.0 SD Host controller: Intel Corporation Device 31d0 (rev 03)
00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03)
00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 03)
01:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU
02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
anand@odyssey3:~/IOTstack$

@mitchross
Here is another person with similar results as us
https://community.home-assistant.io/t/local-realtime-person-detection-for-rtsp-cameras/103107/2243
and he sued this adapter
https://www.amazon.com/dp/B07SN3QYR9

@mitchross
Here is another person with similar results as us
https://community.home-assistant.io/t/local-realtime-person-detection-for-rtsp-cameras/103107/2243
and he sued this adapter
https://www.amazon.com/dp/B07SN3QYR9

Hi,
Does anyone managed to use M.2 Accelerator on Raspberry Pi 4?
I tried to buy USB Accelerator but it is out of stock everywhere.
So I was wondering if I can use the M.2

Hi,
Does anyone managed to use M.2 Accelerator on Raspberry Pi 4?
I tried to buy USB Accelerator but it is out of stock everywhere.
So I was wondering if I can use the M.2

Google's Coral hardware ecosystem is grossly under-tested, it's unfortunate the hardware does not have the same support as their software!
Not working with the Jetson Nano nor the Bananapi M4.

Google's Coral hardware ecosystem is grossly under-tested, it's unfortunate the hardware does not have the same support as their software!
Not working with the Jetson Nano nor the Bananapi M4.

https://github.com/google-coral/edgetpu/issues/96#issuecomment-616566015

@mitchross Jetson Nano should works, what issue do you have with it?
I believe the banana pi doesn't have msi-x support

@mitchross I believe the banana pi doesn't have msi-x support
how is this verified? As the device is listed with correct hardware address with lspci

@mitchross Jetson Nano should works, what issue do you have with it?
I believe the banana pi doesn't have msi-x support

Jetson nanon doesnt work out of the box without applying your fix.
@rdejana Hi, although I haven't seen these issue before, we have had success stories from jetson nano users. There is one thing that you can try:
Could you add pcie_aspm=off to your kernel command arguments?
You can do with by opening this file:
$ cat /boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet
Change "APPEND ${cbootargs} quiet" to "APPEND ${cbootargs} quiet pcie_aspm=off"
Then reboot your board, let me know if this fixes your issue!

Hi folks,
Confirmed working Dual Edge TPU with this adapter.
Running in an Asus Z390I-G Mini-itx with i9 - 9900k on Unraid OS (bit of a faff compiling gasket and apex)
As mentioned only a single TPU at time of writing.
The mobo as an M key slot, so using the mentioned adapter is the easiest solution, BUT.....
Has anyone tried 2 adapters:
M2 M Key > PCIe
PCIe > E Key
Curious as that should preserve x4 and make the 2nd of the TPU modules available?
Any thoughts?

Requires a dual bus PCIe:
https://developers.googleblog.com/2020/09/doubling-down-on-edge-with-corals-new.html

HI , i try to run Dual Edge TPU whit a Dell optiflex 3060 Micro Form Factor
the mainboard have a M.2 E-key interface, unfortunaly the spec indicate for wireless card non for storage... very generic spec...
I had test varius OS ( Debian / ubuntu ) dont see it; also the bios seems not to see it, in the summary screen it shows empty slot.
Any suggestion? or can suggest me any adapter to try M.2 pcie

@moscheIT Can you share the output of 'lscpu', 'uname -a' and 'dmesg' ?

@manoj7410 certainly there are no problems! here are the required outputs:
the installation operations have already been performed on the system
https://coral.ai/docs/m2/get-started/#2-install-the-pcie-driver-and-edge-tpu-runtime
lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
Address sizes:       39 bits physical, 48 bits virtual
CPU(s):              6
On-line CPU(s) list: 0-5
Thread(s) per core:  1
Core(s) per socket:  6
Socket(s):           1
NUMA node(s):        1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               158
Model name:          Intel(R) Core(TM) i5-8500T CPU @ 2.10GHz
Stepping:            10
CPU MHz:             800.206
CPU max MHz:         3500,0000
CPU min MHz:         800,0000
BogoMIPS:            4224.00
Virtualization:      VT-x
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
L3 cache:            9216K
NUMA node0 CPU(s):   0-5
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d

uname -a
Linux home 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux
cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

dmesg
[    0.000000] Linux version 4.19.0-14-amd64<EMAIL_ADDRESS>(gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.171-2 (2021-01-30)
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-14-amd64 root=UUID=74d19b83-0831-4109-8639-72025dadfac5 ro quiet pcie_aspm=off
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[    0.000000] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[    0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000a2bc8fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000a2bc9000-0x00000000a2bc9fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000a2bca000-0x00000000a2bcafff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000a2bcb000-0x00000000b67cafff] usable
[    0.000000] BIOS-e820: [mem 0x00000000b67cb000-0x00000000b9b0dfff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000b9b0e000-0x00000000b9b8afff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000b9b8b000-0x00000000ba047fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000ba048000-0x00000000bab14fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bab15000-0x00000000bacfefff] type 20
[    0.000000] BIOS-e820: [mem 0x00000000bacff000-0x00000000bacfffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bad00000-0x00000000bf7fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000013e7fffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] efi: EFI v2.70 by American Megatrends
[    0.000000] efi:  ACPI 2.0=0xb9b27000  ACPI=0xb9b27000  SMBIOS=0xf0000  SMBIOS 3.0=0xf0020  ESRT=0xba826018  MEMATTR=0xb28f7018
[    0.000000] secureboot: Secure boot could not be determined (mode 0)
[    0.000000] SMBIOS 3.1.1 present.
[    0.000000] DMI: Dell Inc. OptiPlex 3060/03KWTV, BIOS 1.9.1 12/11/2020
[    0.000000] tsc: Detected 2100.000 MHz processor
[    0.004337] tsc: Detected 2112.000 MHz TSC
[    0.004337] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.004339] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.004347] last_pfn = 0x13e800 max_arch_pfn = 0x400000000
[    0.004354] MTRR default type: write-back
[    0.004355] MTRR fixed ranges enabled:
[    0.004356]   00000-9FFFF write-back
[    0.004357]   A0000-BFFFF uncachable
[    0.004358]   C0000-FFFFF write-protect
[    0.004359] MTRR variable ranges enabled:
[    0.004361]   0 base 00C0000000 mask 7FC0000000 uncachable
[    0.004362]   1 base 00BE000000 mask 7FFE000000 uncachable
[    0.004363]   2 base 00BD000000 mask 7FFF000000 uncachable
[    0.004363]   3 disabled
[    0.004364]   4 disabled
[    0.004364]   5 disabled
[    0.004365]   6 disabled
[    0.004365]   7 disabled
[    0.004366]   8 disabled
[    0.004366]   9 disabled
[    0.006477] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
[    0.006617] last_pfn = 0xbad00 max_arch_pfn = 0x400000000
[    0.016875] esrt: Reserving ESRT space from 0x00000000ba826018 to 0x00000000ba826050.
[    0.016887] Using GB pages for direct mapping
[    0.017363] RAMDISK: [mem 0x34bf3000-0x365f0fff]
[    0.017372] ACPI: Early table checksum verification disabled
[    0.017375] ACPI: RSDP 0x00000000B9B27000 000024 (v02 DELL  )
[    0.017379] ACPI: XSDT 0x00000000B9B270A8 0000D4 (v01 DELL   CBX3     01072009 AMI  00010013)
[    0.017385] ACPI: FACP 0x00000000B9B68590 000114 (v06 DELL   CBX3     01072009 AMI  00010013)
[    0.017390] ACPI: DSDT 0x00000000B9B27210 04137E (v02 DELL   CBX3     01072009 INTL 20160527)
[    0.017393] ACPI: FACS 0x00000000BA046080 000040
[    0.017396] ACPI: APIC 0x00000000B9B686A8 0000A0 (v04 DELL   CBX3     01072009 AMI  00010013)
[    0.017399] ACPI: FPDT 0x00000000B9B68748 000044 (v01 DELL   CBX3     01072009 AMI  00010013)
[    0.017401] ACPI: FIDT 0x00000000B9B68790 00009C (v01 DELL   CBX3     01072009 AMI  00010013)
[    0.017404] ACPI: MCFG 0x00000000B9B68830 00003C (v01 DELL   CBX3     01072009 MSFT 00000097)
[    0.017407] ACPI: SSDT 0x00000000B9B68870 0017DF (v02 CpuRef CpuSsdt  00003000 INTL 20160527)
[    0.017410] ACPI: BOOT 0x00000000B9B6A050 000028 (v01 DELL   CBX3     01072009 AMI  00010013)
[    0.017412] ACPI: SSDT 0x00000000B9B6A078 0031C8 (v02 SaSsdt SaSsdt   00003000 INTL 20160527)
[    0.017415] ACPI: HPET 0x00000000B9B6D240 000038 (v01 INTEL  CBX3     00000002      01000013)
[    0.017418] ACPI: SSDT 0x00000000B9B6D278 000E82 (v02 INTEL  Ther_Rvp 00001000 INTL 20160527)
[    0.017421] ACPI: SSDT 0x00000000B9B6E100 0008D1 (v02 INTEL  DELL_MFF 00000000 INTL 20160527)
[    0.017424] ACPI: UEFI 0x00000000B9B6E9D8 000048 (v01 DELL\x CBX3     00000002      01000013)
[    0.017426] ACPI: LPIT 0x00000000B9B6EA20 00005C (v01 INTEL  CBX3     00000002      01000013)
[    0.017429] ACPI: SSDT 0x00000000B9B6EA80 0027DE (v02 INTEL  PtidDevc 00001000 INTL 20160527)
[    0.017432] ACPI: SSDT 0x00000000B9B71260 0014E2 (v02 INTEL  TbtTypeC 00000000 INTL 20160527)
[    0.017434] ACPI: DBGP 0x00000000B9B72748 000034 (v01 DELL\x CBX3     00000002      01000013)
[    0.017437] ACPI: DBG2 0x00000000B9B72780 000054 (v00 DELL\x CBX3     00000002      01000013)
[    0.017440] ACPI: MSDM 0x00000000B9B727D8 000055 (v03 DELL   CBX3     06222004 AMI  00010013)
[    0.017442] ACPI: SLIC 0x00000000B9B72830 000176 (v03 DELL   CBX3     01072009 MSFT 00010013)
[    0.017445] ACPI: SSDT 0x00000000B9B729A8 000144 (v02 Intel  ADebTabl 00001000 INTL 20160527)
[    0.017448] ACPI: DMAR 0x00000000B9B72AF0 0000A8 (v01 INTEL  EDK2     00000002      01000013)
[    0.017451] ACPI: TPM2 0x00000000B9B72B98 000034 (v04 DELL\x CBX3     00000001 AMI  00000000)
[    0.017460] ACPI: Local APIC address 0xfee00000
[    0.017947] No NUMA configuration found
[    0.017949] Faking a node at [mem 0x0000000000000000-0x000000013e7fffff]
[    0.017953] NODE_DATA(0) allocated [mem 0x13e7fb000-0x13e7fffff]
[    0.017977] Zone ranges:
[    0.017978]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.017979]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.017980]   Normal   [mem 0x0000000100000000-0x000000013e7fffff]
[    0.017981]   Device   empty
[    0.017982] Movable zone start for each node
[    0.017983] Early memory node ranges
[    0.017984]   node   0: [mem 0x0000000000001000-0x000000000009efff]
[    0.017985]   node   0: [mem 0x0000000000100000-0x00000000a2bc8fff]
[    0.017986]   node   0: [mem 0x00000000a2bcb000-0x00000000b67cafff]
[    0.017986]   node   0: [mem 0x00000000bacff000-0x00000000bacfffff]
[    0.017987]   node   0: [mem 0x0000000100000000-0x000000013e7fffff]
[    0.018809] Zeroed struct page in unavailable ranges: 45208 pages
[    0.018811] Initmem setup node 0 [mem 0x0000000000001000-0x000000013e7fffff]
[    0.018812] On node 0 totalpages: 1003368
[    0.018814]   DMA zone: 64 pages used for memmap
[    0.018814]   DMA zone: 22 pages reserved
[    0.018815]   DMA zone: 3998 pages, LIFO batch:0
[    0.018927]   DMA32 zone: 11616 pages used for memmap
[    0.018928]   DMA32 zone: 743370 pages, LIFO batch:63
[    0.041113]   Normal zone: 4000 pages used for memmap
[    0.041114]   Normal zone: 256000 pages, LIFO batch:63
[    0.047934] Reserving Intel graphics memory at [mem 0xbd800000-0xbf7fffff]
[    0.048325] ACPI: PM-Timer IO Port: 0x1808
[    0.048326] ACPI: Local APIC address 0xfee00000
[    0.048332] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.048333] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.048334] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.048334] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    0.048335] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[    0.048336] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[    0.048398] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
[    0.048400] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.048402] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.048403] ACPI: IRQ0 used by override.
[    0.048404] ACPI: IRQ9 used by override.
[    0.048406] Using ACPI (MADT) for SMP configuration information
[    0.048407] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.048411] TSC deadline timer available
[    0.048412] smpboot: Allowing 6 CPUs, 0 hotplug CPUs
[    0.048431] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.048433] PM: Registered nosave memory: [mem 0x0009f000-0x000fffff]
[    0.048434] PM: Registered nosave memory: [mem 0xa2bc9000-0xa2bc9fff]
[    0.048435] PM: Registered nosave memory: [mem 0xa2bca000-0xa2bcafff]
[    0.048436] PM: Registered nosave memory: [mem 0xb67cb000-0xb9b0dfff]
[    0.048437] PM: Registered nosave memory: [mem 0xb9b0e000-0xb9b8afff]
[    0.048437] PM: Registered nosave memory: [mem 0xb9b8b000-0xba047fff]
[    0.048438] PM: Registered nosave memory: [mem 0xba048000-0xbab14fff]
[    0.048439] PM: Registered nosave memory: [mem 0xbab15000-0xbacfefff]
[    0.048440] PM: Registered nosave memory: [mem 0xbad00000-0xbf7fffff]
[    0.048441] PM: Registered nosave memory: [mem 0xbf800000-0xf7ffffff]
[    0.048441] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
[    0.048442] PM: Registered nosave memory: [mem 0xfc000000-0xfdffffff]
[    0.048442] PM: Registered nosave memory: [mem 0xfe000000-0xfe010fff]
[    0.048443] PM: Registered nosave memory: [mem 0xfe011000-0xfebfffff]
[    0.048444] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[    0.048444] PM: Registered nosave memory: [mem 0xfec01000-0xfedfffff]
[    0.048445] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[    0.048445] PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
[    0.048446] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
[    0.048448] [mem 0xbf800000-0xf7ffffff] available for PCI devices
[    0.048449] Booting paravirtualized kernel on bare hardware
[    0.048452] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>211568 ns
[    0.168696] random: get_random_bytes called from start_kernel+0x93/0x52a with crng_init=0
[    0.168706] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:6 nr_node_ids:1
[    0.168908] percpu: Embedded 45 pages/cpu s144536 r8192 d31592 u262144
[    0.168915] pcpu-alloc: s144536 r8192 d31592 u262144 alloc=1*2097152
[    0.168916] pcpu-alloc: [0] 0 1 2 3 4 5 - -
[    0.168938] Built 1 zonelists, mobility grouping on.  Total pages: 987666
[    0.168939] Policy zone: Normal
[    0.168941] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-14-amd64 root=UUID=74d19b83-0831-4109-8639-72025dadfac5 ro quiet pcie_aspm=off
[    0.169004] PCIe ASPM is disabled
[    0.173500] Calgary: detecting Calgary via BIOS EBDA area
[    0.173502] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[    0.184715] Memory: 3788220K/4013472K available (10252K kernel code, 1242K rwdata, 3324K rodata, 1600K init, 2260K bss, 225252K reserved, 0K cma-reserved)
[    0.184826] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
[    0.184834] Kernel/User page tables isolation: enabled
[    0.184888] ftrace: allocating 31973 entries in 125 pages
[    0.200378] rcu: Hierarchical RCU implementation.
[    0.200379] rcu: 	RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=6.
[    0.200380] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6
[    0.203684] NR_IRQS: 33024, nr_irqs: 1536, preallocated irqs: 16
[    0.204207] Console: colour dummy device 80x25
[    0.204210] console [tty0] enabled
[    0.204228] ACPI: Core revision 20180810
[    0.204803] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>5 ns
[    0.204875] hpet clockevent registered
[    0.204949] APIC: Switch to symmetric I/O mode setup
[    0.204951] DMAR: Host address width 39
[    0.204952] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.204958] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e
[    0.204959] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.204962] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[    0.204963] DMAR: RMRR base: 0x000000ba5dc000 end: 0x000000ba825fff
[    0.204964] DMAR: RMRR base: 0x000000bd000000 end: 0x000000bf7fffff
[    0.204966] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.204967] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.204968] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[    0.208216] DMAR-IR: Enabled IRQ remapping in x2apic mode
[    0.208217] x2apic enabled
[    0.208249] Switched APIC routing to cluster x2apic.
[    0.217605] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.236899] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x1e71785e5dd, max_idle_ns:<PHONE_NUMBER>14 ns
[    0.236913] Calibrating delay loop (skipped), value calculated using timer frequency.. 4224.00 BogoMIPS (lpj=8448000)
[    0.236916] pid_max: default: 32768 minimum: 301
[    0.238354] Security Framework initialized
[    0.238355] Yama: disabled by default; enable with sysctl kernel.yama.*
[    0.238376] AppArmor: AppArmor initialized
[    0.238941] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.239208] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.239225] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
[    0.239234] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[    0.239452] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.239452] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[    0.239488] CPU0: Thermal monitoring enabled (TM1)
[    0.239519] process: using mwait in idle threads
[    0.239522] Last level iTLB entries: 4KB 128, 2MB 8, 4MB 8
[    0.239523] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[    0.239524] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.239526] Spectre V2 : Mitigation: Full generic retpoline
[    0.239526] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.239527] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.239534] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.239535] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.239564] TAA: Mitigation: Clear CPU buffers
[    0.239568] SRBDS: Mitigation: Microcode
[    0.239569] MDS: Mitigation: Clear CPU buffers
[    0.239875] Freeing SMP alternatives memory: 24K
[    0.243527] smpboot: CPU0: Intel(R) Core(TM) i5-8500T CPU @ 2.10GHz (family: 0x6, model: 0x9e, stepping: 0xa)
[    0.243619] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
[    0.243657] ... version:                4
[    0.243657] ... bit width:              48
[    0.243658] ... generic registers:      8
[    0.243659] ... value mask:             0000ffffffffffff
[    0.243660] ... max period:             00007fffffffffff
[    0.243660] ... fixed-purpose events:   3
[    0.243661] ... event mask:<PHONE_NUMBER>0000ff
[    0.243707] rcu: Hierarchical SRCU implementation.
[    0.244363] random: crng done (trusting CPU's manufacturer)
[    0.244857] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[    0.244901] smp: Bringing up secondary CPUs ...
[    0.244901] x86: Booting SMP configuration:
[    0.244901] .... node  #0, CPUs:      #1 #2 #3 #4 #5
[    0.245549] smp: Brought up 1 node, 6 CPUs
[    0.245549] smpboot: Max logical packages: 1
[    0.245549] smpboot: Total of 6 processors activated (25344.00 BogoMIPS)
[    0.249110] devtmpfs: initialized
[    0.249110] x86/mm: Memory block size: 128MB
[    0.249368] PM: Registering ACPI NVS region [mem 0xa2bc9000-0xa2bc9fff] (4096 bytes)
[    0.249368] PM: Registering ACPI NVS region [mem 0xb9b8b000-0xba047fff] (4968448 bytes)
[    0.249368] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>100000 ns
[    0.249368] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.249368] pinctrl core: initialized pinctrl subsystem
[    0.249368] NET: Registered protocol family 16
[    0.249368] audit: initializing netlink subsys (disabled)
[    0.249368] audit: type=2000 audit(1615188410.036:1): state=initialized audit_enabled=0 res=1
[    0.249368] cpuidle: using governor ladder
[    0.249368] cpuidle: using governor menu
[    0.249368] Simple Boot Flag at 0x47 set to 0x80
[    0.249368] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.249368] ACPI: bus type PCI registered
[    0.249368] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.249368] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[    0.249368] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[    0.249368] PCI: Using configuration type 1 for base access
[    0.249699] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.249699] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.249699] ACPI: Added _OSI(Module Device)
[    0.249699] ACPI: Added _OSI(Processor Device)
[    0.249699] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.249699] ACPI: Added _OSI(Processor Aggregator Device)
[    0.249699] ACPI: Added _OSI(Linux-Dell-Video)
[    0.249699] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.303217] ACPI: 8 ACPI AML tables successfully acquired and loaded
[    0.316837] ACPI: Dynamic OEM Table Load:
[    0.316843] ACPI: SSDT 0xFFFF88B0B8D3B000 00057C (v02 PmRef  Cpu0Ist  00003000 INTL 20160527)
[    0.317430] ACPI: \_SB_.PR00: _OSC native thermal LVT Acked
[    0.319141] ACPI: Dynamic OEM Table Load:
[    0.319146] ACPI: SSDT 0xFFFF88B0B884F800 000400 (v02 PmRef  Cpu0Cst  00003001 INTL 20160527)
[    0.319697] ACPI: Dynamic OEM Table Load:
[    0.319700] ACPI: SSDT 0xFFFF88B0B88CD000 00011B (v02 PmRef  Cpu0Hwp  00003000 INTL 20160527)
[    0.320160] ACPI: Dynamic OEM Table Load:
[    0.320165] ACPI: SSDT 0xFFFF88B0B8D3D800 000724 (v02 PmRef  HwpLvt   00003000 INTL 20160527)
[    0.321043] ACPI: Dynamic OEM Table Load:
[    0.321051] ACPI: SSDT 0xFFFF88B0B8D89000 000EF1 (v02 PmRef  ApIst    00003000 INTL 20160527)
[    0.322301] ACPI: Dynamic OEM Table Load:
[    0.322305] ACPI: SSDT 0xFFFF88B0B884F000 000317 (v02 PmRef  ApHwp    00003000 INTL 20160527)
[    0.322874] ACPI: Dynamic OEM Table Load:
[    0.322878] ACPI: SSDT 0xFFFF88B0B884E000 00030A (v02 PmRef  ApCst    00003000 INTL 20160527)
[    0.327124] ACPI: Interpreter enabled
[    0.327177] ACPI: (supports S0 S3 S4 S5)
[    0.327179] ACPI: Using IOAPIC for interrupt routing
[    0.327227] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.328519] ACPI: Enabled 7 GPEs in block 00 to 7F
[    0.344673] ACPI: Power Resource [USBC] (on)
[    0.348582] ACPI: Power Resource [V0PR] (on)
[    0.349100] ACPI: Power Resource [V1PR] (on)
[    0.349601] ACPI: Power Resource [V2PR] (on)
[    0.361374] ACPI: Power Resource [WRST] (on)
[    0.366921] ACPI: Power Resource [FN00] (off)
[    0.367013] ACPI: Power Resource [FN01] (off)
[    0.367102] ACPI: Power Resource [FN02] (off)
[    0.367191] ACPI: Power Resource [FN03] (off)
[    0.367279] ACPI: Power Resource [FN04] (off)
[    0.368073] ACPI: Power Resource [PIN] (off)
[    0.368528] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[    0.368533] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig Segments MSI]
[    0.368637] acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI]
[    0.369559] PCI host bridge to bus 0000:00
[    0.369561] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.369563] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    0.369564] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    0.369565] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window]
[    0.369566] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window]
[    0.369567] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window]
[    0.369568] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff window]
[    0.369569] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window]
[    0.369571] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
[    0.369572] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
[    0.369573] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
[    0.369575] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window]
[    0.369576] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff window]
[    0.369578] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff window]
[    0.369579] pci_bus 0000:00: root bus resource [mem 0xbf800000-0xf7ffffff window]
[    0.369580] pci_bus 0000:00: root bus resource [mem 0xfc800000-0xfe7fffff window]
[    0.369582] pci_bus 0000:00: root bus resource [bus 00-3e]
[    0.369592] pci 0000:00:00.0: [8086:3ec2] type 00 class 0x060000
[    0.370036] pci 0000:00:02.0: [8086:3e92] type 00 class 0x030000
[    0.370049] pci 0000:00:02.0: reg 0x10: [mem 0xd0000000-0xd0ffffff 64bit]
[    0.370056] pci 0000:00:02.0: reg 0x18: [mem 0xc0000000-0xcfffffff 64bit pref]
[    0.370060] pci 0000:00:02.0: reg 0x20: [io  0x4000-0x403f]
[    0.370271] pci 0000:00:08.0: [8086:1911] type 00 class 0x088000
[    0.370284] pci 0000:00:08.0: reg 0x10: [mem 0xd121e000-0xd121efff 64bit]
[    0.370525] pci 0000:00:12.0: [8086:a379] type 00 class 0x118000
[    0.370575] pci 0000:00:12.0: reg 0x10: [mem 0xd121d000-0xd121dfff 64bit]
[    0.370919] pci 0000:00:14.0: [8086:a36d] type 00 class 0x0c0330
[    0.370967] pci 0000:00:14.0: reg 0x10: [mem 0xd1200000-0xd120ffff 64bit]
[    0.371115] pci 0000:00:14.0: PME# supported from D3hot D3cold
[    0.371650] pci 0000:00:14.2: [8086:a36f] type 00 class 0x050000
[    0.371690] pci 0000:00:14.2: reg 0x10: [mem 0xd1216000-0xd1217fff 64bit]
[    0.371710] pci 0000:00:14.2: reg 0x18: [mem 0xd121c000-0xd121cfff 64bit]
[    0.371964] pci 0000:00:16.0: [8086:a360] type 00 class 0x078000
[    0.372009] pci 0000:00:16.0: reg 0x10: [mem 0xd121b000-0xd121bfff 64bit]
[    0.372135] pci 0000:00:16.0: PME# supported from D3hot
[    0.372437] pci 0000:00:17.0: [8086:a352] type 00 class 0x010601
[    0.372478] pci 0000:00:17.0: reg 0x10: [mem 0xd1214000-0xd1215fff]
[    0.372494] pci 0000:00:17.0: reg 0x14: [mem 0xd121a000-0xd121a0ff]
[    0.372510] pci 0000:00:17.0: reg 0x18: [io  0x4090-0x4097]
[    0.372526] pci 0000:00:17.0: reg 0x1c: [io  0x4080-0x4083]
[    0.372542] pci 0000:00:17.0: reg 0x20: [io  0x4060-0x407f]
[    0.372558] pci 0000:00:17.0: reg 0x24: [mem 0xd1219000-0xd12197ff]
[    0.372647] pci 0000:00:17.0: PME# supported from D3hot
[    0.372931] pci 0000:00:1c.0: [8086:a33c] type 01 class 0x060400
[    0.373157] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    0.373204] pci 0000:00:1c.0: PTM enabled (root), 4ns granularity
[    0.373518] pci 0000:00:1f.0: [8086:a304] type 00 class 0x060100
[    0.373947] pci 0000:00:1f.3: [8086:a348] type 00 class 0x040300
[    0.374026] pci 0000:00:1f.3: reg 0x10: [mem 0xd1210000-0xd1213fff 64bit]
[    0.374100] pci 0000:00:1f.3: reg 0x20: [mem 0xd1000000-0xd10fffff 64bit]
[    0.374252] pci 0000:00:1f.3: PME# supported from D3hot D3cold
[    0.375197] pci 0000:00:1f.4: [8086:a323] type 00 class 0x0c0500
[    0.375389] pci 0000:00:1f.4: reg 0x10: [mem 0xd1218000-0xd12180ff 64bit]
[    0.375603] pci 0000:00:1f.4: reg 0x20: [io  0xefa0-0xefbf]
[    0.376000] pci 0000:00:1f.5: [8086:a324] type 00 class 0x0c8000
[    0.376030] pci 0000:00:1f.5: reg 0x10: [mem 0xfe010000-0xfe010fff]
[    0.376381] pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000
[    0.376427] pci 0000:01:00.0: reg 0x10: [io  0x3000-0x30ff]
[    0.376467] pci 0000:01:00.0: reg 0x18: [mem 0xd1104000-0xd1104fff 64bit]
[    0.376492] pci 0000:01:00.0: reg 0x20: [mem 0xd1100000-0xd1103fff 64bit]
[    0.376641] pci 0000:01:00.0: supports D1 D2
[    0.376642] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    0.376766] pci 0000:00:1c.0: PCI bridge to [bus 01]
[    0.376776] pci 0000:00:1c.0:   bridge window [io  0x3000-0x3fff]
[    0.376781] pci 0000:00:1c.0:   bridge window [mem 0xd1100000-0xd11fffff]
[    0.378402] ACPI: PCI Interrupt Link [LNKA] (IRQs) *0
[    0.378443] ACPI: PCI Interrupt Link [LNKB] (IRQs) *1
[    0.378481] ACPI: PCI Interrupt Link [LNKC] (IRQs) *0
[    0.378519] ACPI: PCI Interrupt Link [LNKD] (IRQs) *0
[    0.378556] ACPI: PCI Interrupt Link [LNKE] (IRQs) *1
[    0.378594] ACPI: PCI Interrupt Link [LNKF] (IRQs) *0
[    0.378632] ACPI: PCI Interrupt Link [LNKG] (IRQs) *1
[    0.378669] ACPI: PCI Interrupt Link [LNKH] (IRQs) *1
[    0.379527] pci 0000:00:02.0: vgaarb: setting as boot VGA device
[    0.379527] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[    0.379527] pci 0000:00:02.0: vgaarb: bridge control possible
[    0.379527] vgaarb: loaded
[    0.379527] pps_core: LinuxPPS API ver. 1 registered
[    0.379527] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    0.379527] PTP clock support registered
[    0.379527] EDAC MC: Ver: 3.0.0
[    0.379527] Registered efivars operations
[    0.379527] PCI: Using ACPI for IRQ routing
[    0.400965] PCI: pci_cache_line_size set to 64 bytes
[    0.401062] e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
[    0.401064] e820: reserve RAM buffer [mem 0xa2bc9000-0xa3ffffff]
[    0.401065] e820: reserve RAM buffer [mem 0xb67cb000-0xb7ffffff]
[    0.401066] e820: reserve RAM buffer [mem 0xbad00000-0xbbffffff]
[    0.401067] e820: reserve RAM buffer [mem 0x13e800000-0x13fffffff]
[    0.401174] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[    0.401174] hpet0: 8 comparators, 64-bit 24.000000 MHz counter
[    0.403118] clocksource: Switched to clocksource tsc-early
[    0.410275] VFS: Disk quotas dquot_6.6.0
[    0.410289] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.410385] AppArmor: AppArmor Filesystem Enabled
[    0.410397] pnp: PnP ACPI init
[    0.410729] system 00:00: [io  0x0a00-0x0a3f] has been reserved
[    0.410730] system 00:00: [io  0x0a40-0x0a7f] has been reserved
[    0.410735] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.411739] pnp 00:01: [dma 0 disabled]
[    0.411782] pnp 00:01: Plug and Play ACPI device, IDs PNP0501 (active)
[    0.411967] system 00:02: [io  0x0680-0x069f] has been reserved
[    0.411969] system 00:02: [io  0x164e-0x164f] has been reserved
[    0.411972] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.411992] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.412100] system 00:04: [io  0x1854-0x1857] has been reserved
[    0.412103] system 00:04: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[    0.412232] system 00:05: [mem 0xfed10000-0xfed17fff] has been reserved
[    0.412233] system 00:05: [mem 0xfed18000-0xfed18fff] has been reserved
[    0.412234] system 00:05: [mem 0xfed19000-0xfed19fff] has been reserved
[    0.412236] system 00:05: [mem 0xf8000000-0xfbffffff] has been reserved
[    0.412237] system 00:05: [mem 0xfed20000-0xfed3ffff] has been reserved
[    0.412239] system 00:05: [mem 0xfed90000-0xfed93fff] could not be reserved
[    0.412240] system 00:05: [mem 0xfed45000-0xfed8ffff] has been reserved
[    0.412241] system 00:05: [mem 0xfee00000-0xfeefffff] could not be reserved
[    0.412244] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.412519] system 00:06: [io  0x1800-0x18fe] could not be reserved
[    0.412520] system 00:06: [mem 0xfd000000-0xfd69ffff] has been reserved
[    0.412522] system 00:06: [mem 0xfd6c0000-0xfd6cffff] has been reserved
[    0.412523] system 00:06: [mem 0xfd6f0000-0xfdffffff] has been reserved
[    0.412524] system 00:06: [mem 0xfe000000-0xfe01ffff] could not be reserved
[    0.412526] system 00:06: [mem 0xfe200000-0xfe7fffff] has been reserved
[    0.412527] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
[    0.412530] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.412900] system 00:07: [io  0x2000-0x20fe] has been reserved
[    0.412907] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.414322] system 00:08: [mem 0xfd6e0000-0xfd6effff] has been reserved
[    0.414323] system 00:08: [mem 0xfd6d0000-0xfd6dffff] has been reserved
[    0.414325] system 00:08: [mem 0xfd6b0000-0xfd6bffff] has been reserved
[    0.414326] system 00:08: [mem 0xfd6a0000-0xfd6affff] has been reserved
[    0.414329] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.415193] pnp: PnP ACPI: found 9 devices
[    0.420965] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns:<PHONE_NUMBER> ns
[    0.420974] pci 0000:00:1c.0: PCI bridge to [bus 01]
[    0.420982] pci 0000:00:1c.0:   bridge window [io  0x3000-0x3fff]
[    0.420990] pci 0000:00:1c.0:   bridge window [mem 0xd1100000-0xd11fffff]
[    0.421005] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    0.421007] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    0.421008] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[    0.421009] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff window]
[    0.421010] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff window]
[    0.421011] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff window]
[    0.421012] pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff window]
[    0.421013] pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff window]
[    0.421014] pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff window]
[    0.421016] pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff window]
[    0.421017] pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff window]
[    0.421018] pci_bus 0000:00: resource 15 [mem 0x000e4000-0x000e7fff window]
[    0.421019] pci_bus 0000:00: resource 16 [mem 0x000e8000-0x000ebfff window]
[    0.421020] pci_bus 0000:00: resource 17 [mem 0x000ec000-0x000effff window]
[    0.421021] pci_bus 0000:00: resource 18 [mem 0xbf800000-0xf7ffffff window]
[    0.421022] pci_bus 0000:00: resource 19 [mem 0xfc800000-0xfe7fffff window]
[    0.421024] pci_bus 0000:01: resource 0 [io  0x3000-0x3fff]
[    0.421025] pci_bus 0000:01: resource 1 [mem 0xd1100000-0xd11fffff]
[    0.421195] NET: Registered protocol family 2
[    0.421344] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes)
[    0.421359] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
[    0.421415] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
[    0.421482] TCP: Hash tables configured (established 32768 bind 32768)
[    0.421508] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[    0.421519] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[    0.421565] NET: Registered protocol family 1
[    0.421569] NET: Registered protocol family 44
[    0.421579] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    0.421938] PCI: CLS 64 bytes, default 64
[    0.421968] Unpacking initramfs...
[    0.989217] Freeing initrd memory: 26616K
[    1.012930] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    1.012934] software IO TLB: mapped [mem 0xae8f7000-0xb28f7000] (64MB)
[    1.012982] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1e71785e5dd, max_idle_ns:<PHONE_NUMBER>14 ns
[    1.012996] clocksource: Switched to clocksource tsc
[    1.013714] Initialise system trusted keyrings
[    1.013734] Key type blacklist registered
[    1.013783] workingset: timestamp_bits=40 max_order=20 bucket_order=0
[    1.014974] zbud: loaded
[    1.181715] Key type asymmetric registered
[    1.181716] Asymmetric key parser 'x509' registered
[    1.181730] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    1.181757] io scheduler noop registered
[    1.181758] io scheduler deadline registered
[    1.181795] io scheduler cfq registered (default)
[    1.181796] io scheduler mq-deadline registered
[    1.182270] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    1.182286] intel_idle: MWAIT substates: 0x11142120
[    1.182287] intel_idle: v0.4.1 model 0x9E
[    1.182596] intel_idle: lapic_timer_reliable_states 0xffffffff
[    1.183646] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.205697] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[    1.206492] Linux agpgart interface v0.103
[    1.206541] AMD IOMMUv2 driver by Joerg Roedel<EMAIL_ADDRESS>[    1.206542] AMD IOMMUv2 functionality not available on this system
[    1.207077] i8042: PNP: No PS/2 controller found.
[    1.207206] mousedev: PS/2 mouse device common for all mice
[    1.207245] rtc_cmos 00:03: RTC can wake from S4
[    1.208339] rtc_cmos 00:03: registered as rtc0
[    1.208353] rtc_cmos 00:03: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[    1.208361] intel_pstate: Intel P-state driver initializing
[    1.208409] intel_pstate: Disabling energy efficiency optimization
[    1.208871] intel_pstate: HWP enabled
[    1.208910] ledtrig-cpu: registered to indicate activity on CPUs
[    1.209313] NET: Registered protocol family 10
[    1.215822] Segment Routing with IPv6
[    1.215839] mip6: Mobile IPv6
[    1.215840] NET: Registered protocol family 17
[    1.215928] mpls_gso: MPLS GSO support
[    1.216380] mce: Using 12 MCE banks
[    1.216411] microcode: sig=0x906ea, pf=0x2, revision=0xde
[    1.216610] microcode: Microcode Update Driver: v2.2.
[    1.216624] sched_clock: Marking stable<PHONE_NUMBER>, 8717589)->(1225524263, -8918327)
[    1.216812] registered taskstats version 1
[    1.216812] Loading compiled-in X.509 certificates
[    1.241121] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1'
[    1.241133] Loaded X.509 cert 'Debian Secure Boot Signer 2020: 00b55eb3b9'
[    1.242348] Loaded UEFI:db cert 'Dell Inc. UEFI DB: 5ddb772dc880660055ba0bc131886bb630a639e7' linked to secondary sys keyring
[    1.242365] Loaded UEFI:db cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' linked to secondary sys keyring
[    1.242383] Loaded UEFI:db cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' linked to secondary sys keyring
[    1.243583] zswap: loaded using pool lzo/zbud
[    1.243800] AppArmor: AppArmor sha1 policy hashing enabled
[    1.245451] rtc_cmos 00:03: setting system clock to 2021-03-08 07:26:51 UTC<PHONE_NUMBER>)
[    1.246514] Freeing unused kernel image memory: 1600K
[    1.281164] Write protecting the kernel read-only data: 16384k
[    1.281796] Freeing unused kernel image memory: 2028K
[    1.282039] Freeing unused kernel image memory: 772K
[    1.289532] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    1.289533] x86/mm: Checking user space page tables
[    1.295007] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    1.295008] Run /init as init process
[    1.353746] i801_smbus 0000:00:1f.4: SPD Write Disable is set
[    1.353812] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
[    1.356941] cryptd: max_cpu_qlen set to 1000
[    1.360145] SCSI subsystem initialized
[    1.362545] ACPI: bus type USB registered
[    1.362559] usbcore: registered new interface driver usbfs
[    1.362563] usbcore: registered new interface driver hub
[    1.362569] usbcore: registered new device driver usb
[    1.366209] AVX2 version of gcm_enc/dec engaged.
[    1.366209] AES CTR mode by8 optimization enabled
[    1.369935] libata version 3.00 loaded.
[    1.371349] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    1.371353] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[    1.372518] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810
[    1.372526] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[    1.372794] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    1.372795] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.372796] usb usb1: Product: xHCI Host Controller
[    1.372796] usb usb1: Manufacturer: Linux 4.19.0-14-amd64 xhci-hcd
[    1.372797] usb usb1: SerialNumber: 0000:00:14.0
[    1.372845] thermal LNXTHERM:00: registered as thermal_zone0
[    1.372846] ACPI: Thermal Zone [TZ00] (28 C)
[    1.372893] hub 1-0:1.0: USB hub found
[    1.372919] hub 1-0:1.0: 16 ports detected
[    1.374008] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    1.374028] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[    1.374030] xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
[    1.374074] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[    1.374075] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.374075] usb usb2: Product: xHCI Host Controller
[    1.374076] usb usb2: Manufacturer: Linux 4.19.0-14-amd64 xhci-hcd
[    1.374077] usb usb2: SerialNumber: 0000:00:14.0
[    1.374153] hub 2-0:1.0: USB hub found
[    1.374164] hub 2-0:1.0: 8 ports detected
[    1.374544] ahci 0000:00:17.0: version 3.0
[    1.374555] usb: port power management may be unreliable
[    1.374806] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1 impl SATA mode
[    1.374807] ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part ems deso sadm sds apst
[    1.375155] scsi host0: ahci
[    1.375231] scsi host1: ahci
[    1.375299] scsi host2: ahci
[    1.375354] scsi host3: ahci
[    1.375408] scsi host4: ahci
[    1.375447] ata1: SATA max UDMA/133 abar m2048@0xd1219000 port 0xd1219100 irq 124
[    1.375447] ata2: DUMMY
[    1.375448] ata3: DUMMY
[    1.375448] ata4: DUMMY
[    1.375449] ata5: DUMMY
[    1.376802] libphy: r8169: probed
[    1.377155] r8169 0000:01:00.0 eth0: RTL8168h/8111h, 54:bf:64:95:ec:24, XID 54100800, IRQ 123
[    1.377156] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[    1.383160] r8169 0000:01:00.0 enp1s0: renamed from eth0
[    1.685924] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.688584] ata1.00: supports DRM functions and may not be fully accessible
[    1.689833] ata1.00: ATA-11: Samsung SSD 860 QVO 1TB, RVQ01B6Q, max UDMA/133
[    1.689838] ata1.00:<PHONE_NUMBER> sectors, multi 1: LBA48 NCQ (depth 32), AA
[    1.693197] ata1.00: supports DRM functions and may not be fully accessible
[    1.697105] ata1.00: configured for UDMA/133
[    1.697384] scsi 0:0:0:0: Direct-Access     ATA      Samsung SSD 860  1B6Q PQ: 0 ANSI: 5
[    1.706737] ata1.00: Enabling discard_zeroes_data
[    1.706750] sd 0:0:0:0: [sda]<PHONE_NUMBER> 512-byte logical blocks: (1.00 TB/932 GiB)
[    1.706753] sd 0:0:0:0: [sda] Write Protect is off
[    1.706754] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.706758] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.706923] ata1.00: Enabling discard_zeroes_data
[    1.708267]  sda: sda1 sda2 sda3
[    1.708509] ata1.00: Enabling discard_zeroes_data
[    1.709398] sd 0:0:0:0: [sda] supports TCG Opal
[    1.709399] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.712913] usb 1-7: new high-speed USB device number 2 using xhci_hcd
[    1.750636] PM: Image not found (code -22)
[    1.878347] usb 1-7: New USB device found, idVendor=1737, idProduct=0077, bcdDevice= 1.01
[    1.878351] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.878353] usb 1-7: Product: 802.11 g WLAN
[    1.878355] usb 1-7: Manufacturer: Ralink
[    1.878356] usb 1-7: SerialNumber: 1.0
[    1.932125] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[    2.151025] systemd[1]: Inserted module 'autofs4'
[    2.286158] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    2.305240] systemd[1]: Detected architecture x86-64.
[    2.308167] systemd[1]: Set hostname to <home>.
[    2.427613] systemd[1]: Listening on udev Kernel Socket.
[    2.427826] systemd[1]: Listening on udev Control Socket.
[    2.428027] systemd[1]: Listening on Journal Audit Socket.
[    2.428120] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    2.428247] systemd[1]: Listening on Syslog Socket.
[    2.430491] systemd[1]: Created slice User and Session Slice.
[    2.430763] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    2.444513] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
[    2.514311] systemd-journald[279]: Received request to flush runtime journal from PID 1
[    2.526735] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
[    2.526743] ACPI: Sleep Button [SLPB]
[    2.526778] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[    2.526781] ACPI: Power Button [PWRB]
[    2.526824] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[    2.526830] ACPI: Power Button [PWRF]
[    2.567933] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    2.567975] wmi_bus wmi_bus-PNP0C14:02: WQBC data block query control method not found
[    2.567976] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    2.569725] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    2.572533] acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    2.592227] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFC, rev-id 1)
[    2.605801] input: PC Speaker as /devices/platform/pcspkr/input/input3
[    2.605802] iTCO_vendor_support: vendor-support=0
[    2.605808] EFI Variables Facility v0.08 2004-May-17
[    2.606240] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    2.607696] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
[    2.607697] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[    2.607697] RAPL PMU: hw unit of domain package 2^-14 Joules
[    2.607697] RAPL PMU: hw unit of domain dram 2^-14 Joules
[    2.607698] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[    2.607698] RAPL PMU: hw unit of domain psys 2^-14 Joules
[    2.609469] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[    2.609909] iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff]
[    2.609915] iTCO_wdt: probe of iTCO_wdt failed with error -16
[    2.613317] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[    2.673365] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[    2.686113] pstore: Using compression: deflate
[    2.686131] pstore: Registered efi as persistent store backend
[    2.705832] Adding 8853500k swap on /dev/sda3.  Priority:-2 extents:1 across:8853500k SSFS
[    2.745167] snd_hda_intel 0000:00:1f.3: enabling device (0100 -> 0102)
[    2.765461] [drm] Replacing VGA console driver
[    2.767512] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[    2.783807] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.783808] [drm] Driver supports precise vblank timestamp query.
[    2.784462] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    2.796624] i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[    2.796983] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[    2.797640] input: Dell WMI hotkeys as /devices/platform/PNP0C14:02/wmi_bus/wmi_bus-PNP0C14:02/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input4
[    2.833624] audit: type=1400 audit(1615188413.084:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=367 comm="apparmor_parser"
[    2.833627] audit: type=1400 audit(1615188413.084:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=367 comm="apparmor_parser"
[    2.834160] audit: type=1400 audit(1615188413.084:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=366 comm="apparmor_parser"
[    2.834161] audit: type=1400 audit(1615188413.084:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=366 comm="apparmor_parser"
[    2.834163] audit: type=1400 audit(1615188413.084:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=366 comm="apparmor_parser"
[    2.923098] intel_rapl: Found RAPL domain package
[    2.923099] intel_rapl: Found RAPL domain core
[    2.923100] intel_rapl: Found RAPL domain uncore
[    2.923100] intel_rapl: Found RAPL domain dram
[    2.953165] usb 1-7: reset high-speed USB device number 2 using xhci_hcd
[    3.064187] [drm] failed to retrieve link info, disabling eDP
[    3.117051] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 detected
[    3.128014] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0006 detected
[    3.158699] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[    3.158915] usbcore: registered new interface driver rt2800usb
[    3.163423] rt2800usb 1-7:1.0 wlx00259c700734: renamed from wlan0
[    3.295541] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[    3.295632] r8169 0000:01:00.0: firmware: failed to load rtl_nic/rtl8168h-2.fw (-2)
[    3.295637] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[    3.295639] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168h-2.fw failed with error -2
[    3.295641] r8169 0000:01:00.0 enp1s0: unable to load firmware patch rtl_nic/rtl8168h-2.fw (-2)
[    3.295862] Generic PHY r8169-100:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-100:00, irq=IGNORE)
[    3.395947] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[    3.401484] IPv6: ADDRCONF(NETDEV_UP): wlx00259c700734: link is not ready
[    3.401520] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[    3.403122] rt2800usb 1-7:1.0: firmware: direct-loading firmware rt2870.bin
[    3.403124] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
[    3.619482] IPv6: ADDRCONF(NETDEV_UP): wlx00259c700734: link is not ready
[    3.628417] [drm] Initialized i915 1.6.0 20180719 for 0000:00:02.0 on minor 0
[    3.630212] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    3.630474] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
[    3.630662] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    3.666706] [drm] Cannot find any crtc or sizes
[    3.701620] [drm] Cannot find any crtc or sizes
[    3.733503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3234: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line
[    3.733505] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=1 (0x14/0x0/0x0/0x0/0x0)
[    3.733506] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[    3.733506] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[    3.733507] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[    3.733508] snd_hda_codec_realtek hdaudioC0D0:      Headset Mic=0x19
[    3.733508] snd_hda_codec_realtek hdaudioC0D0:      Headphone Mic=0x1a
[    3.733902] [drm] Cannot find any crtc or sizes
[    3.789978] snd_hda_codec_realtek hdaudioC0D0: Failed to find dell wmi symbol dell_micmute_led_set
[    3.859960] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1f.3/sound/card0/input6
[    3.862219] input: HDA Intel PCH Headphone Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input7
[    3.862346] input: HDA Intel PCH Front Line Out as /devices/pci0000:00/0000:00:1f.3/sound/card0/input8
[    3.862449] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input9
[    3.862626] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input10
[    3.862783] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
[    3.869319] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
[    3.869540] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
[    3.876580] IPv6: ADDRCONF(NETDEV_UP): wlx00259c700734: link is not ready
[    3.944682] IPv6: ADDRCONF(NETDEV_UP): wlx00259c700734: link is not ready
[    8.467405] IPv6: ADDRCONF(NETDEV_UP): wlx00259c700734: link is not ready

i kwon, I have a issue whit wireless firmware but isn't a problem for a moment, i fix it later

Please share the output of below commands too:

lspci
modinfo gasket
ls /dev/apex*

lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port (rev f0)
00:1f.0 ISA bridge: Intel Corporation H370 Chipset LPC/eSPI Controller (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

** modinfo gasket **
filename:       /lib/modules/4.19.0-14-amd64/updates/dkms/gasket.ko
author:         Rob Springer<EMAIL_ADDRESS>license:        GPL v2
version:        1.1.3
description:    Google Gasket driver framework
srcversion:     EE63B2D1E7E5BEBAF51CEE1
depends:
retpoline:      Y
name:           gasket
vermagic:       4.19.0-14-amd64 SMP mod_unload modversions
parm:           dma_bit_mask:int

*ls /dev/apex **
ls cannot access '/dev/apex*' no such file or directory

Please also share the output of : lsmod | grep apex
Also confirm if you have followed the instructions given at : https://coral.ai/docs/m2/get-started/#2a-on-linux
We should see an entry like "03:00.0 System peripheral: Device 1ac1:089a" once the PCIe device is connected to your machine.

Yes I confirm that I have followed the instructions in the guide, in any case i dont't see the coral
unfortunately at the moment I have no other hardware available to evaluate if the mainboard or the coral, to make a double check in case they  have electrical problems.
lsmod | grep apex
dont report anything
~# lsmod | grep apex
~#

@moscheIT I assume that you are working with a Native installation of Ubuntu and not a VM or Virtual Box or WSL. Please correct me if my assumption is wrong.

@manoj7410 yes you are correct I am working with a "native version", in this case of debian 10 buster.
as noted at the top of the therad debian 10 is supported on all devices

@moscheIT Can you also share the output of:
sudo lspci -vvv

@manoj7410 of course there are no problems
here it is:
# lspci -vvv
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
	Subsystem: Dell 8th Gen Core Processor Host Bridge/DRAM Registers
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information: Len=10 <?>
	Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop) (prog-if 00 [VGA controller])
	Subsystem: Dell UHD Graphics 630 (Desktop)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 126
	Region 0: Memory at d0000000 (64-bit, non-prefetchable) [size=16M]
	Region 2: Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 4000 [size=64]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [40] Vendor Specific Information: Len=0c <?>
	Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
	Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee00018  Data: 0000
	Capabilities: [d0] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Process Address Space ID (PASID)
		PASIDCap: Exec- Priv-, Max PASID Width: 14
		PASIDCtl: Enable- Exec- Priv-
	Capabilities: [200 v1] Address Translation Service (ATS)
		ATSCap:	Invalidate Queue Depth: 00
		ATSCtl:	Enable-, Smallest Translation Unit: 00
	Capabilities: [300 v1] Page Request Interface (PRI)
		PRICtl: Enable- Reset-
		PRISta: RF- UPRGI- Stopped+
		Page Request Capacity: 00008000, Page Request Allocation: 00000000
	Kernel driver in use: i915
	Kernel modules: i915

00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
	Subsystem: Dell Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 255
	Region 0: Memory at d121e000 (64-bit, non-prefetchable) [disabled] [size=4K]
	Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [f0] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-

00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
	Subsystem: Dell Cannon Lake PCH Thermal Controller
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 17
	Region 0: Memory at d121d000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Kernel driver in use: intel_pch_thermal
	Kernel modules: intel_pch_thermal

00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) (prog-if 30 [XHCI])
	Subsystem: Dell Cannon Lake PCH USB 3.1 xHCI Host Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 123
	Region 0: Memory at d1200000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
		Address: 00000000fee00298  Data: 0000
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
	Subsystem: Intel Corporation Cannon Lake PCH Shared SRAM
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at d1216000 (64-bit, non-prefetchable) [disabled] [size=8K]
	Region 2: Memory at d121c000 (64-bit, non-prefetchable) [disabled] [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-

00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
	Subsystem: Dell Cannon Lake PCH HECI Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 125
	Region 0: Memory at d121b000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee002f8  Data: 0000
	Capabilities: [a4] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) (prog-if 01 [AHCI 1.0])
	Subsystem: Dell Cannon Lake PCH SATA AHCI Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 122
	Region 0: Memory at d1214000 (32-bit, non-prefetchable) [size=8K]
	Region 1: Memory at d121a000 (32-bit, non-prefetchable) [size=256]
	Region 2: I/O ports at 4090 [size=8]
	Region 3: I/O ports at 4080 [size=4]
	Region 4: I/O ports at 4060 [size=32]
	Region 5: Memory at d1219000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee00278  Data: 0000
	Capabilities: [70] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port (rev f0) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: d1100000-d11fffff
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #5, Speed 5GT/s, Width x1, ASPM not supported, Exit Latency L0s <1us, L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #8, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState+
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [90] Subsystem: Dell Cannon Lake PCH PCI Express Root Port
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
	Capabilities: [140 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd- EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [150 v1] Precision Time Measurement
		PTMCap: Requester:- Responder:+ Root:+
		PTMClockGranularity: 4ns
		PTMControl: Enabled:+ RootSelected:+
		PTMEffectiveGranularity: Unknown
	Capabilities: [200 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=40us PortTPowerOnTime=44us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=150us LTR1.2_Threshold=81920ns
		L1SubCtl2: T_PwrOn=150us
	Capabilities: [250 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:1f.0 ISA bridge: Intel Corporation H370 Chipset LPC/eSPI Controller (rev 10)
	Subsystem: Dell H370 Chipset LPC/eSPI Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
	Subsystem: Dell Cannon Lake PCH cAVS
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 127
	Region 0: Memory at d1210000 (64-bit, non-prefetchable) [size=16K]
	Region 4: Memory at d1000000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] Vendor Specific Information: Len=14 <?>
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee00318  Data: 0000
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
	Subsystem: Dell Cannon Lake PCH SMBus Controller
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 21
	Region 0: Memory at d1218000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at efa0 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
	Subsystem: Dell Cannon Lake PCH SPI Controller
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at fe010000 (32-bit, non-prefetchable) [size=4K]

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
	Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at 3000 [size=256]
	Region 2: Memory at d1104000 (64-bit, non-prefetchable) [size=4K]
	Region 4: Memory at d1100000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address:<PHONE_NUMBER>000000  Data: 0000
	Capabilities: [70] Express (v2) Endpoint, MSI 01
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 4096 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Via message/WAKE#
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
		Vector table: BAR=4 offset=00000000
		PBA: BAR=4 offset=00000800
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
	Capabilities: [140 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [160 v1] Device Serial Number 01-00-00-00-68-4c-e0-00
	Capabilities: [170 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [178 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=150us PortTPowerOnTime=150us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=81920ns
		L1SubCtl2: T_PwrOn=150us
	Kernel driver in use: r8169
	Kernel modules: r8169

Has anyone gotten the dual TPU edge working on a normal pcie slot yet? Looks like everyone is only getting one core out of it no matter the adapter used.

Hi, has anyone tested the ASRock Ultra Quad M.2 Card with the M.2 Accelerator B+M key successfully?
Looks like an alternative to the rare E-Key to get multiple TPUs on a system. But it's designed for NVM-E SSDs, so I'm not exactly certain that it will actually work.

Confirmed working: Rock Pi 4C SBC with M.2 B+M TPU. Ubuntu 20.04 and Debian 9.
Seeed's "M.2 Extend Board" accessory holds the module securely in place, but it's a bit wonky - the inference speed slowed to a half when using the extender, from ~2ms to ~4ms. Appears to be caused by electrical interference on the cable/connector/lines.
This is v1.6 with a rather unusual FFC, maybe someone who has this combo with v1.4 or v1.2 of the extender board can comment on any decrease in speed with the older, more common style of FFC.

HI , i try to run Dual Edge TPU whit a Dell optiflex 3060 Micro Form Factor
the mainboard have a M.2 E-key interface, unfortunaly the spec indicate for wireless card non for storage... very generic spec...
I had test varius OS ( Debian / ubuntu ) dont see it; also the bios seems not to see it, in the summary screen it shows empty slot.
Any suggestion? or can suggest me any adapter to try M.2 pcie

I am trying to do the same with a Dell Optiplex 9020 Micro.  I have a 1TB NVMe drive in the M.2 22x80 slot, and the Coral in the M.2 22x30 slot.  The BIOS doesnt seem to detect the coral.  Did you have any luck? or come up with any workarounds?
Or alternatively have you found anywhere that has the usb version in stock?

I've managed to get 1 TPU out of 2 running on Jetson Nano 4GB
The Harware specs of Jetson Nano state that it has an M.2 E-key - 1 x4 (PCIe Gen2)
More hardware specs here - https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra Linux Driver Package Development Guide/software_features_jetson_nano.html#wwpID0E0IB0HA
The problem is that Coral Dual TPU explicetly asks for M.2 E-key - with two PCIe Gen2 x1 lanes
Unless there's a M.2 E-key adapter that would convert  1 x4 M.2 E-key into a 2 x2... x1 M.2 E-key, and provided there will still be enough space under the Jetson SOC - I don't see the Dual TPU working on Jetson Nano anytime soon.

@F0rged I'm sorry but I have not found solutions, currently I havn't try any workarounds

Confirmed working: Rock Pi 4C SBC with M.2 B+M TPU. Ubuntu 20.04 and Debian 9.
Seeed's "M.2 Extend Board" accessory holds the module securely in place, but it's a bit wonky - the inference speed slowed to a half when using the extender, from ~2ms to ~4ms. Appears to be caused by electrical interference on the cable/connector/lines.
This is v1.6 with a rather unusual FFC, maybe someone who has this combo with v1.4 or v1.2 of the extender board can comment on any decrease in speed with the older, more common style of FFC.

Hi!
@blazczak  What model has been used for speed test? I want to compare this numbers to Raspberry Pi4 with<EMAIL_ADDRESS>so it will be nice if you could provided more information on benchmark. Thanks!

@marcin-kamionowski this is with the mobilenet_v2_1.0_224_inat_bird_quant_edgetpu.tflite model from the hello parrot example in "Get Started" section (https://coral.ai/docs/m2/get-started/#4-run-a-model-on-the-edge-tpu).
I can get low 2ms inference times consistently on the Rock Pi 4C
$ python3 examples/classify_image.py --model test_data/mobilenet_v2_1.0_224_inat_bird_quant_edgetpu.tflite --labels test_data/inat_bird_labels.txt --input test_data/parrot.jpg
----INFERENCE TIME----
Note: The first inference on Edge TPU is slow because it includes loading the model into Edge TPU memory.
12.3ms
2.4ms
2.4ms
2.3ms
2.3ms
-------RESULTS--------
Ara macao (Scarlet Macaw): 0.75781

Pozdrawiam 😃

Update on the M.2 extend board for Rock Pi 4: it appears the slow down might have been caused by the CSI camera (IMX219) attached, once I disconnected the cam the inference times were again comparable to the M.2 module attached directly to the Rock Pi.

@mitchross Jetson Nano should works, what issue do you have with it?
I believe the banana pi doesn't have msi-x support

Jetson nanon doesnt work out of the box without applying your fix.
@rdejana Hi, although I haven't seen these issue before, we have had success stories from jetson nano users. There is one thing that you can try:
Could you add pcie_aspm=off to your kernel command arguments?
You can do with by opening this file:
$ cat /boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet
Change "APPEND ${cbootargs} quiet" to "APPEND ${cbootargs} quiet pcie_aspm=off"
Then reboot your board, let me know if this fixes your issue!

Hi, I'm curious why I'm still getting the
ValueError: Failed to load delegate from libedgetpu.so.1

after applying the fix and reboot. Does anyone have the same issue?
I use single core M.2. edgetpu on jetson nano, and the edgetpu is visible.

@jk78346 how do you define "the edgetpu is visible" in your case? I would see this delegate error when there is an issue with PCIe connectivity or the TPU driver (compiled with mismatched headers or compiled with errors).
lspci -nn | grep 089a and ls /dev/apex_0 show output? What do modinfo gasket and modinfo apex return.

Hello @blazczak, is it possible to run M.2 module with dual edge tpu with Rock Pi 4+ b or did you only test it with single edge tpu module ?

Hi @pdecat @mitchross @saket424 @jaburges @mattncsu @retrospectsecurity @F0rged @DeepDubbed
I'm developing adapters for Dual Edge TPU to use both cores on systems with single m.2 PCIe
Currently I soldered AE key adapter and have bare PCBs for BM
Could you please take a look at logs and suggest further tests to see if my design any good?
magic-blue-smoke/Dual-Edge-TPU-Adapter/issues/1

Logs look great, you may want to test Frigate NVR on this setup: https://github.com/blakeblackshear/frigate
Do you plan to publish the design of your adapter or sell some adapters?

@pdecat thanks. If models are there, I'll try it
I plan to sell these adapters and can send prototypes for testing. Let me know if you're interested

@magic-blue-smoke
I certainly would be interested in testing your part. Let us know when and how I go about procuring it

I'd also be interested in testing one. Currently using a USB TPU to do inference on multiple cameras and have wanted to try out the dual edge tpu since it came out.
@pdecat- frigate looks awesome. I have a homegrown solution I developed in python a year ago to do "smart" ai detection but that seems 100x better!

@magic-blue-smoke I am interested in trying. Your logs look perfectly fine. There is nothing wrong with the output.

For anyone else that can't get their hands on a USB Coral - I was able to get a Mini PCIe Coral TPU working with the Low Profile HP WN7004 PCIe WLAN Card (716869-001).  ProxMox passes it through successfully and is working fine in a docker container running Frigate.

Getting a single core Edge TPU working in a PCIe/mini PCIe port with only a 1x PCIe lane working is not an issue to be honest.
The real challenge here is getting both cores of the Dual Edge TPU working.
Not sure how @magic-blue-smoke's adapter design makes that possible, but I'd be glad to try it too.

Getting a single core Edge TPU working in a PCIe/mini PCIe port with only a 1x PCIe lane working is not an issue to be honest.
The real challenge here is getting both cores of the Dual Edge TPU working.
Not sure how @magic-blue-smoke's adapter design makes that possible, but I'd be glad to try it too.

I partially agree - in my search there were numerous reports of the single core mini PCIe cards not working with some mini PCIe adapter boards, so I wanted to report back of a known working solution.  Bonus points for it working on recycled hardware that has very little (other) useful life left.
An adapter for the dual TPU would've been a clear winner when I was looking for a non-usb solution (but it didn't/doesn't exist), so alternatives are needed until something workable is available.

For those of you who missed it, there's now the ultimate adapter card from Asus that supports 8 Dual Edge TPUs. But it's not exactly cheap.
And also for anyone who might be interested, this adapter card has worked for me to get the Mini PCIe module working a PCIe slot.

@saket424 @mattncsu @mitchross @pdecat and everyone interested in testing, please sign up here:
magic-blue-smoke/Dual-Edge-TPU-Adapter/issues/2

Does anyone know if the B+M key version will work with a SATA adapter like this one or does it require more from the M.2 slot?

Does anyone know if the B+M key version will work with a SATA adapter like this one or does it require more from the M.2 slot?

It will not work. Module expects PCIe, not SATA.

Does M.2 Accelerator with Dual Edge TPU work with RPI 4  with the adapter?

Does M.2 Accelerator with Dual Edge TPU work with RPI 4 with the adapter?

@manju-rn none of PCIe Coral TPUs are known to work with Raspberry Pi CM4 due to compatibility issue: /issues/280
My adapter only makes two cores available for Dual Edge TPU on a systems with one PCIe bus on m.2 connector (ie where one core is visible and working)

Thanks @magic-blue-smoke .  So in order to use in PI 4 the USB accelerator is the only option? I thought internally the USB uses the same chip / setup

Does anybody uses the Mini PCIe Accelerator in combination with a Synology DS1621+ it has a PCIe slot.
I would like to use that slot  for the coral Mini PCIe Accelerator

@pirazor I've tested the single TPU module with Rock Pi 4 C; 4+ B is newer so I can't comment on that model. The rockpi.org tech specs posted online are unfortunately incomplete, they don't list the actual type of key for their M.2 socket, but in the case of 4 C it's M key. I would imagine 4+ B is also M key; the dual TPU model is E-key so right off the bat you'd need an adapter.
The RK3399 SoC on both models should support multiple (4) PCIe lanes but even if you get a working adapter E->M there may be Rockpi specific hardware and software configurations ("features") that could still prevent it from working with the dual TPU module. Let me know if you get it to work with the dual TPU.

@blazczak @pirazor
For second core to work on Dual Edge TPU, system has to have second PCIe interface routed to m.2 connector, which is rare. Important: Dual Edge TPU exposes two independent PCIe buses, ie times two PCIe x1 interfaces, and not PCIe x2
PCIe m.2 specification defines second PCIe bus for E-key as optional, this is why on most system only one core is visible.
Keys B and M have one PCIe x4, ie multiple lanes, but not multiple buses. In addition to this, B and M key must be NVMe (not SATA) for Single Core TPUs to work.
Some examples for m.2 Dual Edge TPU:
If system has m.2 B or M key NVMe connector, Dual Edge TPU second core won't work with passive adapter
If system has m.2 E key connector, Dual Edge TPU second core might work if designers routed second PCIe interface
If system has m.2 A key, there is a chance it might work with passive adapter
To solve these issues I'm developing adapters for Dual Edge TPUs to be fitted to any A/B/E/M and desktop PCIe slots: https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter

My motherboard doesn't have any spare m.2 slots, and doesn't have mini PCIe.
I do have a spare PCIe x1 slot, so am looking for a reliable, tested PCIe x1 adaptor to use with either the Coral M.2 B/M or Coral M.2 A/E card.  These are both in stock locally for me, but the mini PCIe version is not, and the USB version seems unavailable everywhere.
It seems weird to me that they wouldn't just release a full sized PCIe version in the first place since it's by far the most commonly available slot, but here we are!
Any suggestions?

My motherboard doesn't have any spare m.2 slots, and doesn't have mini PCIe.
I do have a spare PCIe x1 slot, so am looking for a reliable, tested PCIe x1 adaptor to use with either the Coral M.2 B/M or Coral M.2 A/E card. These are both in stock locally for me, but the mini PCIe version is not, and the USB version seems unavailable everywhere.
It seems weird to me that they wouldn't just release a full sized PCIe version in the first place since it's by far the most commonly available slot, but here we are!
Any suggestions?
edit: I do also have an available x16 slot but I was saving it for a future video card. So that is an option if no x1 card is available, but I'd definitely prefer to use the x1 if possible.

@bjammin you have several options depending on your enthusiasm:

"easiest and cheapest": get Coral m.2 B+M key and m.2 NVMe to PCIe x4 adapter and use it in x16 slot
"trust me, I'm engineer": same as above, but dremel off PCIe pads that won't fit x1 slot and use in x1 slot. If not detected after mod, you'd need to short "card present" pins on PCIe edge connector by soldering a wire.
"I'm lucky": there are m.2 E-key to PCIe x1 adapters for m.2 WiFi cards. Make sure that it has PCIe routed to m.2 slot by identifying differential pair on pins B14 and B15 (in very rare cases only USB might be passed to m.2 connector from external USB connector)

Everything above only relates to single core TPU cards

My motherboard doesn't have any spare m.2 slots, and doesn't have mini PCIe.
I do have a spare PCIe x1 slot, so am looking for a reliable, tested PCIe x1 adaptor to use with either the Coral M.2 B/M or Coral M.2 A/E card. These are both in stock locally for me, but the mini PCIe version is not, and the USB version seems unavailable everywhere.
It seems weird to me that they wouldn't just release a full sized PCIe version in the first place since it's by far the most commonly available slot, but here we are!
Any suggestions?
edit: I do also have an available x16 slot but I was saving it for a future video card. So that is an option if no x1 card is available, but I'd definitely prefer to use the x1 if possible.

I think getting a Wi-Fi PCIe x1 card (where you can replace the A/E key wi-fi module) is your best bet.
Early on in the thread, one confirmed model was: Low Profile HP WN7004 PCIe WLAN Card (716869-001).

I just ordered one of these along with some single Coral B+M key Accelerators.
https://www.aliexpress.com/item/32898293772.html?spm=a2g0s.90423<IP_ADDRESS>424c4ddmpyYF
I'm hoping that it will work as it was the cheapest option ($4 shipped to me). Granted it will be a few weeks before I get it and can report back :) In my case I needed the pcie 1x as it is the only slot I had.

That's certainly a nice cheap option!  Please do report back and let us know how you go.
There's also this one which is also PCIE x1 and has a slot bracket (it's the same as one of the Amazon ones I linked).  I might order one of those and see how it goes.
https://www.aliexpress.com/item/4000221883956.html

Sooo is there any option to connect the dual TPU card to a RasPi 4B, like with a Hat or an USB3-Adapter?

Sooo is there any option to connect the dual TPU card to a RasPi 4B, like with a Hat or an USB3-Adapter?

@RubenKelevra
For Dual Edge card there are no options to interface to Raspberry Pi4 or CM4:

they are not compatible on PCIe interface
there are no off the shelf converters for USB to PCIe m.2

Sooo is there any option to connect the dual TPU card to a RasPi 4B, like with a Hat or an USB3-Adapter?

@RubenKelevra
For Dual Edge card there are no options to interface to Raspberry Pi4 or CM4:

they are not compatible on PCIe interface
there are no off the shelf converters for USB to PCIe m.2

Ah sad. So I have to get two USB ones. Thanks for the help! :)

Sooo is there any option to connect the dual TPU card to a RasPi 4B, like with a Hat or an USB3-Adapter?

@RubenKelevra
For Dual Edge card there are no options to interface to Raspberry Pi4 or CM4:

they are not compatible on PCIe interface
there are no off the shelf converters for USB to PCIe m.2

What about  https://pipci.jeffgeerling.com/

Sooo is there any option to connect the dual TPU card to a RasPi 4B, like with a Hat or an USB3-Adapter?

@RubenKelevra
For Dual Edge card there are no options to interface to Raspberry Pi4 or CM4:

they are not compatible on PCIe interface
there are no off the shelf converters for USB to PCIe m.2

What about  https://pipci.jeffgeerling.com/

Well, while might be interesting for a CM4 built like the new Home Assistant Amber, I have already a RasPi 4B. I don't really think I like to replace it.
Additionally it would only run a single TPU board, as there's no secondary PCIe lane (as far as I understand).

Well, while might be interesting for a CM4 built like the new Home Assistant Amber, I have already a RasPi 4B. I don't really think I like to replace it.
Additionally it would only run a single TPU board, as there's no secondary PCIe lane (as far as I understand).

@RubenKelevra
Raspberry Pi CM4 and current Coral TPUs are not compatible, nor single, nor dual: https://github.com/google-coral/edgetpu/issues/280
If you already have Pi4B and have no intentions to change SBC, then USB TPU is the only option

Well, while might be interesting for a CM4 built like the new Home Assistant Amber, I have already a RasPi 4B. I don't really think I like to replace it.
Additionally it would only run a single TPU board, as there's no secondary PCIe lane (as far as I understand).

@RubenKelevra
Raspberry Pi CM4 and current Coral TPUs are not compatible, nor single, nor dual: https://github.com/google-coral/edgetpu/issues/280
If you already have Pi4B and have no intentions to change SBC, then USB TPU is the only option

Yeah I know. But technically it should be possible to fixed for single TPUs, right? 🤔
And there's a hacky option to add PCIe to the RasPi
... just for the sake of completion :)
https://hackaday.com/2020/07/01/adding-pcie-to-your-raspberry-pi-4-the-easier-way/

Could someone take a look at the post here: https://github.com/google-coral/edgetpu/issues/431#issuecomment-922826985 and give me some advice on what is needed to get this working?  I'm unclear what I'm missing.

Could someone take a look at the post here: #431 (comment) and give me some advice on what is needed to get this working? I'm unclear what I'm missing.

Did you run thru the linux install instructions slowy? You have to disable apex drivers. Its super important to follow that guide super closely. https://coral.ai/docs/m2/get-started/

Could someone take a look at the post here: #431 (comment) and give me some advice on what is needed to get this working? I'm unclear what I'm missing.

Did you run thru the linux install instructions slowy? You have to disable apex drivers. Its super important to follow that guide super closely. https://coral.ai/docs/m2/get-started/

Yep.  Several times.  Not once have I seen the apex drivers loaded (prebuilt or others).  I also went through the troubleshooting steps which included blacklisting the apex drivers and gasket drivers just to make sure the proper things were disable.

Whats output of lspci ?

Whats output of lspci ?

   I disabled secure boot and it worked great!   I'll see about putting in a PR to change the docs to potentially save some others the same headache.
https://github.com/google-coral/edgetpu/issues/431#issuecomment-925345105

I just ordered one of these along with some single Coral B+M key Accelerators.
https://www.aliexpress.com/item/32898293772.html?spm=a2g0s.90423<IP_ADDRESS>424c4ddmpyYF
I'm hoping that it will work as it was the cheapest option ($4 shipped to me). Granted it will be a few weeks before I get it and can report back :) In my case I needed the pcie 1x as it is the only slot I had.

That's certainly a nice cheap option! Please do report back and let us know how you go.
There's also this one which is also PCIE x1 and has a slot bracket (it's the same as one of the Amazon ones I linked). I might order one of those and see how it goes.
https://www.aliexpress.com/item/4000221883956.html

I just got everything setup on my ubuntu machine with the m2 coral and a pcie1x adapter. I didn't really have any problems and it seems to be working well!

I finally received my PCIe to m2 adaptor.  I got it from ebay but it's the same as this one:
https://www.amazon.com/MZHOU-Controller-Expansion-Supports-Profile/dp/B082D6RF6S/
The model number is PCENVME-N01 VER006S V3.0
There's not much to it, it's pretty much connecting m2 lanes to PCIe lanes.
It works fine with the Coral m2 B+M TPU in a PCIe x1 slot in my MSI C236A motherboard.
My inference speeds in Frigate dropped from 280 to 7!

Are you using it in a Synology DS or something else?

"I'm lucky": there are m.2 E-key to PCIe x1 adapters for m.2 WiFi cards. Make sure that it has PCIe routed to m.2 slot by identifying differential pair on pins B14 and B15 (in very rare cases only USB might be passed to m.2 connector from external USB connector)
Unfortunately m.2 E-key was only available option at the moment and I was able to get it working with this adapter: https://www.ebay.com/itm/174362088680
Only one TPU but better than nothing.

I just tried to use this exact card for my dual edge TPU but my motherboard isn't recognizing it.  What hardware are you using?  Anything special you did to have it recognized?

I just tried to use this exact card for my dual edge TPU but my motherboard isn't recognizing it. What hardware are you using? Anything special you did to have it recognized?
It didn't work in PCIeX1 but does in a regular PCIe slot (X16). I'm using pretty old PC with ASUS P8Z68-V PRO motherboard.

Just share mine,
my dual edge TPU m.2 is working (only 1 TPU is running) on Nano Jetson 4Gb version and Gigabyte brix GB-BRi3H-10110.
So if two edge is running I should see apex0 and apex1 right?

I have bought the 2GB version of the Jetson Nano and the Dual Edge TPU but obviously this version of the Jetson Nano does not have an M.2 slot.

@Matssa56
I'm looking at HP EliteDesk 800 G4 i5-8500T specs here: https://support.hp.com/us-en/document/c06045012 and what I can tell is:

When checking the specs, the first M.2 2280/2230 combo (I'm guessing M key?) seems to be used by the SSD NVMe and is PCIe 3.0 4x and the
This one sounds promising. PCIe on m.2 slot is what you need for Coral TPU

second one is a M.2 2230 (dunno which key that is) PCIe x1 for WLAN.

I'd be cautious here. Specs point out "Intel 9560 802.11ac 2x2 Wi-Fi with Bluetooth M.2 Combo Card" and Intel specs https://www.intel.com/content/www/us/en/products/sku/99446/intel-wirelessac-9560/specifications.html tell it has CNVio interface, which is not compatible with Coral TPU.
However there is also "Intel 7265 802.11ac 2x2 Wi-Fi with Bluetooth M.2 Combo Card non-vPro (Brazil)" and 7265 is PCIe/USB card.
So I'd scratch my head if I were in Brazil and wouldn't rely on this option if anywhere else in the world

If I want to use the M.2 SSD slot for the Coral, seems like I need to go SATA with a SSD instead right?

Yes, looks like you have to use m.2 NVMe slot for Coral TPU and SATA for drive, unless "(2) M.2 PCIe x4 2280/2230 combo (for storage)" means there are two identical m.2 NVMe slots, then you can use one for Coral and another for NVMe SSD

@Matssa56
I'm looking at HP EliteDesk 800 G4 i5-8500T specs here: https://support.hp.com/us-en/document/c06045012 and what I can tell is:

When checking the specs, the first M.2 2280/2230 combo (I'm guessing M key?) seems to be used by the SSD NVMe and is PCIe 3.0 4x and the

This one sounds promising. PCIe on m.2 slot is what you need for Coral TPU

second one is a M.2 2230 (dunno which key that is) PCIe x1 for WLAN.

I'd be cautious here. Specs point out "Intel 9560 802.11ac 2x2 Wi-Fi with Bluetooth M.2 Combo Card" and Intel specs https://www.intel.com/content/www/us/en/products/sku/99446/intel-wirelessac-9560/specifications.html tell it has CNVio interface, which is not compatible with Coral TPU. However there is also "Intel 7265 802.11ac 2x2 Wi-Fi with Bluetooth M.2 Combo Card non-vPro (Brazil)" and 7265 is PCIe/USB card. So I'd scratch my head if I were in Brazil and wouldn't rely on this option if anywhere else in the world

If I want to use the M.2 SSD slot for the Coral, seems like I need to go SATA with a SSD instead right?

Yes, looks like you have to use m.2 NVMe slot for Coral TPU and SATA for drive, unless "(2) M.2 PCIe x4 2280/2230 combo (for storage)" means there are two identical m.2 NVMe slots, then you can use one for Coral and another for NVMe SSD

Ah perfect thanks for your help, I'm in France so not going with the Brasil stuff hehe.
For the NVMe, I watched the website https://www.servethehome.com/hp-elitedesk-800-g4-mini-tinyminimicro-guide-review/ and it seems like there are indeed 2 NVMes so I can use one for coral and another one for NVMe.
Next thing I need to do now is manage to buy a Coral A+M key but seems like out of stock EVERYWHERE ^^'
Thanks for your help!! Still new to this M.2 slot and PCIe... Cheers!

So, all this m.2 key stuff is very confusing to me. I have a Dell Optiplex MT 7040 with an m.2 slot. The only thing I can find on the slot is SSD | M.2 22x80 socket3. Would love to use the dual tpu google coral if possible. Any hints on the best google coral to purchase would be greatly appreciated.

I have a 7040 Micro. I got 1 pci channel of the dual TPU m.2 a+e recognized in the m.2 NVME slot using an adapter. The WIFI adapter is keyed all wrong for the coral, even though it's the right dimensions. I'm waiting for magic-blue-smoke's dual m.2 b+m adapter to take advantage of both accelerators. Supposedly going on sale real soon now.
https://www.amazon.com/gp/product/B07WBXP632/ is the adapter I used/

going to try a dual TPU with Sintech NGFF M.2 (Key-A+E/Key-E) to Mini PCI-E Express Adapter Card...

I can confirm that this E-key to M-key adaptor works: https://www.aliexpress.com/item/1005001274922542.html?spm=a2g0s.90423<IP_ADDRESS>fb44c4dbvMX3F
Obviously, only connects 1 of the 2 TPU's.

I can confirm that this E-key to M-key adaptor works: https://www.aliexpress.com/item/1005001274922542.html?spm=a2g0s.90423<IP_ADDRESS>fb44c4dbvMX3F
Obviously, only connects 1 of the 2 TPU's.

Did you have to connect the USB header too?

No, worked without the usb
Get Outlook for iOShttps://aka.ms/o0ukef

From: PenguinPaws @.>
Sent: Thursday, November 11, 2021 4:52:10 AM
To: google-coral/edgetpu @.>
Cc: ps-nl @.>; Comment @.>
Subject: Re: [google-coral/edgetpu] What Edge TPU Works with What Hardware/Software (#256)
I can confirm that this E-key to M-key adaptor works: https://www.aliexpress.com/item/1005001274922542.html?spm=a2g0s.90423<IP_ADDRESS>fb44c4dbvMX3F
Obviously, only connects 1 of the 2 TPU's.
Did you have to connect the USB header too?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/google-coral/edgetpu/issues/256#issuecomment-965964470, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEBZMFMQ7IRQ5KS3INJL4NLULM4WVANCNFSM4TZERNJQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

No, worked without the usb Get Outlook for iOShttps://aka.ms/o0ukef
…
________________________________ From: PenguinPaws @.> Sent: Thursday, November 11, 2021 4:52:10 AM To: google-coral/edgetpu @.> Cc: ps-nl @.>; Comment @.> Subject: Re: [google-coral/edgetpu] What Edge TPU Works with What Hardware/Software (#256) I can confirm that this E-key to M-key adaptor works: https://www.aliexpress.com/item/1005001274922542.html?spm=a2g0s.90423<IP_ADDRESS>fb44c4dbvMX3F Obviously, only connects 1 of the 2 TPU's. Did you have to connect the USB header too? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#256 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEBZMFMQ7IRQ5KS3INJL4NLULM4WVANCNFSM4TZERNJQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Awesome. Thank you! I'll probably give it a shot then.

I can confirm that tekit M.2 NGFF Key E Card to mPCIe (PCIe+USB) works with the Dual TPU (with 1 TPU working) plugged into a Ableconn PEX-MP117 Mini PCI-E to PCI-E Adapter Card (previously mentioned)...
https://www.amazon.com.au/gp/product/B07JK3VTZQ/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&th=1
https://www.amazon.com/dp/B07JBCL1CJ?psc=1&ref=ppx_yo2_dt_b_product_details

I just bought a Dual edge TPU and I got to connect it to a x1 PCIE. Do you have any Aliexpress (or europe amazon) adapter that works to do the job to get one TPU working? (until I can get the MBS adapter)

dont think its possible

Just share mine, my dual edge TPU m.2 is working (only 1 TPU is running) on Nano Jetson 4Gb version and Gigabyte brix GB-BRi3H-10110. So if two edge is running I should see apex0 and apex1 right?

Hi @willertan, just one simple question: did you place the Dual Edge TPU in the M.2 SSD slot (PCI-e x4 /SATA) of the Gigabyte Brix or did you replace the WiFi+BT card? In my case I have a Gigabyte Brix J5005 model and I would like to know if I can replace the WiFi card with the Dual Edge TPU (with a single TPU active, for sure), without sacrificing the M.2/SSD drive.
What's your experience? Would you mind sharing this details with me/us?
Many thanks for your help and best regards!

Hello all, I finally got my hands on a Coral, but it's the dev board variant. I realize that this is probably a long shot, but I was wondering if it's possible to use dev board to emulate the USB accelerator (as it's only the 1gb model, so I worry running NVR software on it will have the memory packed to the brim), so that I could simply plug the dev board into a device running Frigate and have it use the dev board as an accelerator via USB connection?
Thanks,
-MH

Ok, so what are options 'out of box' to get both TPUs working? Adapters are not available, i've got my coral dual tpu in hands, been using it with 1 chip for ages.
I was hoping to see devices here saing 'this' motherboard and cpu works with both chips, but so far cant see a single device here?

Adapters are not available...

Coming soon... https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter

Yeah I've seen that info. I could change my hardware too, I'm not too bothered, but so far I'm unable to find compatible device.
Also I've seen those adapters are 'switching' PCIE devices, but I don't understand how it works. Is it affecting any timing or its not affecting any efficiency of dual tpu?

Hi @usbguru, are you 100% sure the tested Nexcom NDiS B537 M.2 E-Key slot reported to be compatible with the M.2 Accelerator with Dual Edge TPU has two instances of PCIe x1 lanes?
FWIW, I've plugged a M.2 Accelerator with Dual Edge TPU in a M.2 E-Key to PCIe x1 adapter and obviously, only one TPU device is working:
# lspci | grep Coral
02:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU

Same here

Also I've seen those adapters are 'switching' PCIE devices, but I don't understand how it works. Is it affecting any timing or its not affecting any efficiency of dual tpu?

@fryc88 PCIe bus is more like Ethernet network (including routed data packets), rather than "bus". Imagine PCIe switch as network switch with downstream port and aggregated upstream port. My current adapters use PCIe Gen 2 switch with one upstream lane. This means that two TPUs are sharing same bandwidth of upstream port, but both working in parallel. It adds some latency: https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter/issues/3#issuecomment-885925888
However for new adapters I do plan to use more upstream lanes

Plus I think my dell Wyse 5070 got a+e slot and I can't see adapter for it or I'm blind(I've seen picture but not shop link or waiting list for this one)

a+e slot can be CNVio instead of PCIe, thus non-compatible
Most of radio cards are 2230, this leaves no space for TPU card. So I only have a prototype in 2242 size

1. a+e slot can be CNVio instead of PCIe, thus non-compatible

Dual Edge TPU works in my 5070 as 1 chip visible, so i'm assuming it is PCIe?

2. Most of radio cards are 2230, this leaves no space for TPU card. So I only have a prototype in 2242 size

There is no room for 2280 indeed, however after moving 1 cap i would be able to install longer card easily, or possibly after moving two caps install 2280. Problem would be only with mounting hole :)

Also, there is Wyse 5070 with PCIe slot i think x1? But it's really difficult to find it for normal amount of money (usually price for it is unbelievably higher than standard 5070. According to pictures, there is ONLY slot not soldered, other components around seems to be soldered, also it is visible (and i'm assuming functional) in BIOS. That's a hardcore mod, but using pinout i could simply solder PCIe card out there or try to install socket, but i would have to obtain 2nd wyse to not disturb my main system. It does not matter at this moment, i mainly want to get 2nd chip working in easiest possible way. As i said, i could even replace that wyse to something different, but i don't know to what other system with similiar specs (it's 24/7 runner, mainly for Home Assistant, but got some other stuff working on it as well, so don't need supercomputer, but similiar performance and power consumption would be lovely)

So I have 2 Dual TPU cards and fully realize that I will only get one TPU per card. I am looking for a card to go into a desktop PCIe slot and be able to run both adapters.
I have read through MANY threads and they always seem to talk about on board M.2 slots and not much about full PCIe adapter cards.
What actually works. I will even settle for an adapter which will only work with a single dual TPU card at this point.

So I have 2 Dual TPU cards and fully realize that I will only get one TPU per card. I am looking for a card to go into a desktop PCIe slot and be able to run both adapters. I have read through MANY threads and they always seem to talk about on board M.2 slots and not much about full PCIe adapter cards.
What actually works. I will even settle for an adapter which will only work with a single dual TPU card at this point.

These work for dual tpu- https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter

So I have 2 Dual TPU cards and fully realize that I will only get one TPU per card. I am looking for a card to go into a desktop PCIe slot and be able to run both adapters. I have read through MANY threads and they always seem to talk about on board M.2 slots and not much about full PCIe adapter cards.
What actually works. I will even settle for an adapter which will only work with a single dual TPU card at this point.

These work for dual tpu- https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter

I know about those but they are not shipping and no idea when any will ship. I am on the waiting list.
What I asked for was a standard PCIe adapter for a normal workstation which will allow one of the 2 TPU's to be used. If the card has two M.2 E key slots would be great because I could use my two coral dual TPU and make use of one TPU on each card.
My question was what PCIe adapter can I use in a standard PCIe slot to get one of the TPU's on a dual TPU card working. Everyone talks about what works using a mPCIe/M.2 slot, but noone, that I have found, has posted a working standard PCIe slot adapter.

You could try https://www.newegg.com/riitop-model-dul-m2tpce4x-pci-express-controller-card/p/17Z-0061-00056?Description=dual M.2 PCIe adapter card&cm_re=dual_M.2 PCIe adapter card--17Z-0061-00056--Product&quicklink=true

https://www.newegg.com/riitop-dul-nvtpce8x-pci-express-controller-card/p/17Z-0061-00097?Description=dual nvme PCIe adapter&cm_re=dual_nvme PCIe adapter-_-9SIARE9F592947-_-Product&quicklink=true this might work. It has the ASM2812 PCIe switch on it. No idea if it'll work, but it might be worth a try.

So I have 2 Dual TPU cards and fully realize that I will only get one TPU per card. I am looking for a card to go into a desktop PCIe slot and be able to run both adapters. I have read through MANY threads and they always seem to talk about on board M.2 slots and not much about full PCIe adapter cards.
What actually works. I will even settle for an adapter which will only work with a single dual TPU card at this point.

These work for dual tpu- https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter

I know about those but they are not shipping and no idea when any will ship. I am on the waiting list.
What I asked for was a standard PCIe adapter for a normal workstation which will allow one of the 2 TPU's to be used. If the card has two M.2 E key slots would be great because I could use my two coral dual TPU and make use of one TPU on each card.
My question was what PCIe adapter can I use in a standard PCIe slot to get one of the TPU's on a dual TPU card working. Everyone talks about what works using a mPCIe/M.2 slot, but noone, that I have found, has posted a working standard PCIe slot adapter.

This is what worked for me.  Connect the Dual TPU to this M.2 to mini PCIe converter, then use the mini PCIe converter to this Mini PCI-E to PCI-E Adapter Card.  It's not the most elegant or efficient solution, but my motherboard wouldn't recognize the dual tpu if I plugged it straight into the m.2 e-key slot that was used for wifi, and it also wouldn't recognize it when I plugged it into an m.2 e-key to PCI-E adapter card.

I would appreciate to get some tip how to Process next to get duad TPU visible
I'm using B+M adapter https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter in HP eliteDesk 800 G3 micro and I can see card PCI bridge, but no Coral

I know that @magic-blue-smoke was developing something to allow the Dual Coral Edge TPU to use both chips, but since he's in Moscow and under brutal tech sanctions, I'm willing to bet that he won't be getting the parts to make more for a few years at least, and he might not even have internet access anymore.
So the question is this:  Is anyone else working on an m.2 M-key to E-key adapter that uses two PCIe lanes?

Cool.  I'll keep watching and hopefully China won't try to invade Taiwan.  That would be really inconvenient.  :-)

Hi, would the below motherboard work with the dual edge tpu? I can’t tell if it is has two PCI lanes for the m.2 e key. If it doesn’t, what apparels have people been successful with?
https://www.msi.com/Motherboard/H510M-A-PRO

Cool. I'll keep watching and hopefully China won't try to invade Taiwan. That would be really inconvenient. :-)

@DougLorenz PCIe version is available now: https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter/issues/8#issuecomment-1181686907
m.2 version will be available late August-September

Thanks!  I've got one on order.

A downside having to order from China right now…
Destination
Origin - Sync Time: 2022-07-17 10:55:58 (GMT-04:00)
2022-07-17 21:29
杭州萧山国际操作中心, During epidemic period, resources are significantly restricted and we don’t promise any transit time. We are trying our best to coordinate the resources to arrange export.
From: magic-blue-smoke @.>
Sent: Tuesday, July 12, 2022 6:41 PM
To: google-coral/edgetpu @.>
Cc: Robert Webb @.>; Comment @.>
Subject: Re: [google-coral/edgetpu] What Edge TPU Works with What Hardware/Software (#256)
Cool. I'll keep watching and hopefully China won't try to invade Taiwan. That would be really inconvenient. :-)
@DougLorenzhttps://github.com/DougLorenz PCIe version is available now: magic-blue-smoke/Dual-Edge-TPU-Adapter#8 (comment)https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter/issues/8#issuecomment-1181686907
m.2 version will be available late August-September
—
Reply to this email directly, view it on GitHubhttps://github.com/google-coral/edgetpu/issues/256#issuecomment-1182562603, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC4G2Q7PAX4WLHBNXDD62M3VTXX7BANCNFSM4TZERNJQ.
You are receiving this because you commented.Message ID: @.***>

apologies, I did review this whole thread....I just received my dual edge TPU 2 days back.
I have previously bought a miniPCIe to M.2 e-key adapter. so far, so good.
Will a miniPCIe to PCIe x1 adapter work, as in will both TPUs be visible to the system. My Debian based system has a PCIe 3.0 x4 slot.
...or is the only viable solution to use both CPUs of the dual-edge to use https://www.makerfabs.com/dual-edge-tpu-adapter.html
any pointers will be helpful.

I just received my dual edge TPU 2 days back.

Can I ask where from? Do you know of someone who has stock at the moment?

I just received my dual edge TPU 2 days back.

Can I ask where from? Do you know of someone who has stock at the moment?

mouser just shipped what appears to be a large number of orders on the dual coral

I just received my dual edge TPU 2 days back.

Can I ask where from? Do you know of someone who has stock at the moment?

mouser, my order was delivered finally.

apologies, I did review this whole thread....I just received my dual edge TPU 2 days back.
I have previously bought a miniPCIe to M.2 e-key adapter. so far, so good.
Will a miniPCIe to PCIe x1 adapter work, as in will both TPUs be visible to the system. My Debian based system has a PCIe 3.0 x4 slot.
...or is the only viable solution to use both CPUs of the dual-edge to use https://www.makerfabs.com/dual-edge-tpu-adapter.html
any pointers will be helpful.

anyone...?
A pci to mini-pci adapter, and a mini-pci to m.2 e key adapter, connected to a dual edge coral ...would that work, has it worked for anyone please ?
or is my only option the makerfabs adapter?

anyone...?
A pci to mini-pci adapter, and a mini-pci to m.2 e key adapter, connected to a dual edge coral ...would that work, has it worked for anyone please ?
or is my only option the makerfabs adapter?

Hi @eagle239 Dual Edge TPU card has two identical TPUs at the same board with two independent PCIe interfaces. Only m.2 E-key slot implemented to full specs has two PCIe interfaces. This means that with passive adapters to any mPCIe/PCIe/m.2 you'll get only one TPU visible. Second TPU will not be connected via PCIe and won't be visible.
I've designed adapter you're mentioning, it's using PCIe switch to split one PCIe interface for two TPUs

anyone...?
A pci to mini-pci adapter, and a mini-pci to m.2 e key adapter, connected to a dual edge coral ...would that work, has it worked for anyone please ?
or is my only option the makerfabs adapter?

Hi @eagle239 Dual Edge TPU card has two identical TPUs at the same board with two independent PCIe interfaces. Only m.2 E-key slot implemented to full specs has two PCIe interfaces. This means that with passive adapters to any mPCIe/PCIe/m.2 you'll get only one TPU visible. Second TPU will not be connected via PCIe and won't be visible.
I've designed adapter you're mentioning, it's using PCIe switch to split one PCIe interface for two TPUs

Thanks, I didnt realize you designed it @magic-blue-smoke Thank you for explaining again !! I have placed the order for my adapter, and will update here, once received.

very basic question: how do I find out that my DualEdge TPU card is dead on arrival.
I also want to find out just in case if I'm doing anything wrong.
I am on a TrueNAS SCALE Debian based NAS platform, A2SDi-H-TP4F SuperMicro motherboard, with an onboard PCI 3.0 x4.
I tried two options, added the right packages, rebooted , lspci...nothing new:

dualedge M.2 e-key-->M.2 ekey to miniPCI adapter-->motherboard PCI 3.0 x4 slot
dualedge M.2 e-key-->@magic-blue-smoke's PCI x1 adapter-->motherboard PCI 3.0 x4 slot

There are no error messages, grep on dmesg or syslog comes back empty for coral or tpu.

@magic-blue-smoke  Is there a way to use your adapter with some PCIe converter to USB to be used in RPI?

very basic question: how do I find out that my DualEdge TPU card is dead on arrival. I also want to find out just in case if I'm doing anything wrong.
I am on a TrueNAS SCALE Debian based NAS platform, A2SDi-H-TP4F SuperMicro motherboard, with an onboard PCI 3.0 x4.