Closed geerlingguy closed 4 months ago
Moved to Linux repo because quirks for PCIe switches would be a kernel change.
This should be fixed by dtoverlay=pciex1-compat-pi5,no-mip
.
See https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L3544
@P33M - Indeed, if I add just that overlay, the device is enabled and firmware loads successfully.
In future the pcie*-compat*
overlay(s) are going to be the way that users can flip switches until they get something that works with their particular bus topology.
Enquiring minds want to know: what's the output of sudo lspci -v
in this case?
Describe the bug
When I boot my Pi with the Hailo-8L plugged into any PCI Express switch (e.g. a Dual-NVMe HAT board), I get the following errors when the Hailo driver tries initializing the driver:
(Note: I'm testing a configuration with two Hailo-8 series chips behind a bridge, that's how this came up...)
See below 'additional context' for a fix.
To reproduce
Plug a Hailo-8L M.2 Accelerator into any PCI Express switch/bridge, and plug that into the Pi 5. Boot the Pi, follow the Getting Started instructions for the AI Kit, and check
dmesg
or runhailortcli fw-control identify
and observe the results.Expected behaviour
The Hailo-8L should work as normal, and be usable by applications like
rpicam-apps
.Actual behaviour
The Hailo-8L is not usable, and you get the errors as stated above.
System Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:
cat /etc/rpi-issue
)?vcgencmd version
)?uname -a
)?Logs
See above.
Additional context
If I add the following overlay to
/boot/firmware/config.txt
:...and then reboot, the Hailo-8L initializes properly, shows up using
identify
, and can be used for inference by applications on the Pi. Additionally, multiple Hailo-8L can be used this way too :)Related: https://github.com/raspberrypi/linux/pull/6126