Yo @dbrenes! Welcome on board!
I’ll ask around about the host platform, but in the meantime maybe there something in here…
… or in here that might help?
And in the background we’ll investigate the PC 
Oh! Also, I think Ubuntu 24.04 needs to run in Docker (22.04 doesn’t, but the latest version does - for now anyway). This might help, if it’s not currently running in Docker: https://support.axelera.ai/hc/en-us/articles/25953148201362-Install-Voyager-SDK-in-a-Docker-Container
Hi @dbrenes ,
Thank you for reaching out.
As @Spanner mentioned, we still do not officially support Ubuntu 24.04 native. We will have this support in the close future. In the meantime, you should follow the following guide (using Docker) if you still want to work on Ubuntu 24.04: https://support.axelera.ai/hc/en-us/articles/25953148201362-Install-Voyager-SDK-in-a-Docker-Container .
Please also make sure the driver is installed.
Saying that, the OS used should not be the reason for which the card is nor enumerated.
Take a look at the different suggestions in our troubleshooting guide in: https://support.axelera.ai/hc/en-us/articles/26261515755538-PCIe-Troubleshooting-Guide.
Please try those suggestions one by one and share with us the details of each outcome. This will help us debug where the possible issue might be.
Final question:
- If you do a reboot, is the Metis card enumerated in lspci?
- Can you share the output of running:
- Can you share a txt with the output from running
sudo dmesg? - Can you share specs and more info about the adapter used?
Thank you beforehand.
Best,
Victor
Hello @Spanner and @Victor Labian, thank you for your prompt help!
Regarding the Ubuntu 24.04 issue, I agree with you that the OS shouldn’t be an impediment for the card to be recognized by the system. Regardless, we’ve set up the Docker container with the Ubuntu 22.04 image following your guide and installed the Voyager SDK too.
I’ve attached lspci, lspci -tv and sudo dmesg results. We are not able to see the Axelera card neither the 1f9d vendor ID when rebooting. Additionally, we’ve confirmed that the Metis driver was installed and loaded during the tests:
$ lsmod | grep metis
metis 90112 0
As for the adapter, this is the information we have:
Dual M.2 SSD to PCI Express 3.0 X4 Adapter Expansion Card for PCIe NVMe SATA M2 NGFF SSD 2230 2242 2260 2280.
We’ll be trying out the steps suggested on your troubleshooting guide and later update you. We’ve also placed an order for other adapters in hopes to also try them in the future.
Thank you
Hello Axelera AI Team!
Just a quick update from our side: we’ve tested the Metis M.2 module using a different PCIe adapter—specifically, this one—but unfortunately, the system still isn’t recognizing the card.
To rule out the adapter as the root cause, we verified it using another M.2 accelerator, which was successfully detected via lspci.
We haven’t gone through the software troubleshooting steps yet, as we plan to try the Metis on a Raspberry Pi first. We’ll follow up with more details once we complete that test, but wanted to keep you posted in the meantime.
Hi @dbrenes ,
Thank you for your update, can you quickly try the following on your host? I think it might help:
Disable IOMMU
In some kernels, the intel_iommu=off or amd_iommu=off kernel parameters should be added at boot.
For example, in Ubuntu, the grub file needs to be modified:
sudo nano /etc/default/grub
where you need to disable IOMMU by adding intel_iommu=off or amd_iommu=off parameter:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=off"
or for AMD:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amd_iommu=off"
Save the file, then run:
sudo update-grub
and to apply the changes:
sudo reboot
------
Please let us know if this helped.
Best,
Victor
