Skip to main content

Feature Request Pipeline

10 Posts

Problem with axdevice --refresh causing NVMe drives to be stopped on a running systemImplemented

Putting this up for folk who may hit a similar issue.If you have a machine which has a single root PCIe device, where the output of lspci -tv looks something like this;alsutton@svr204:~$ lspci -tv-[0000:00]-+-00.0 Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers +-02.0 Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] +-08.0 Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model +-14.0 Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller +-14.2 Intel Corporation Cannon Lake PCH Shared SRAM +-16.0 Intel Corporation Cannon Lake PCH HECI Controller +-1b.0-[01]----00.0 Micron/Crucial Technology P2 [Nick P2] / P3 / P3 Plus NVMe PCIe SSD (DRAM-less) +-1f.0 Intel Corporation B360 Chipset LPC/eSPI Controller +-1f.3 Intel Corporation Cannon Lake PCH cAVS +-1f.4 Intel Corporation Cannon Lake PCH SMBus Controller +-1f.5 Intel Corporation Cannon Lake PCH SPI Controller \-1f.6 Intel Corporation Ethernet Connection (7) I219-VYou need to be very careful running `axdevice --refresh`.I’ve got two machines that, by default, present the pci device tree in this way, and running `axdevice --refresh` triggered the NVMe drive to be disconnected from the system, resulting in filesystem corruption, which put the whole system into a read-only mode.It would be awesome if someone could update the axdevice script to only affect Axelera devices, and yes, this is a machine with the card installed, it just hasn’t been detected.

LattePanda Sigma works with Metis M.2!New

Hi all! I wanted to contribute a little bit about my experience bringing up the Metis M.2 in my LattePanda Sigma. Im an EE who is self taught, I have worked for Harley Davidson, Span.io, Enel X NA, and I’ve done several consulting projects on synthesizers and drum machines. My interest in AI is hobby and curiosity based, not professional. Software engineering is a new skill Im creating.I first tried to run Metis on the Windows 11 operating system that came with LattePanda Sigma, and following the instructions on the git was extremely confusing. I have ADD, and some other learning differences, but that wasn’t the reason installing was so hard on Windows. It’s because there isn’t a single page with coherent instructions telling the user how to bring up the hardware in a simple step by step format. Having the user click between git pages on firmware, installation of drivers, wsl, putting Windows into test mode, using multiple programming environments, etc is painful and makes installing the hardware on Windows a miserable, confusing, and difficult experience.I’ll probably make my own step by step guide for Windows at some point since the instructions on git are confusing.I then tried to do the install on an old version of Ubuntu (support 24.04 please!) and I had much less trouble. I HIGHLY RECOMMEND using Ubuntu 22.04 to run the hardware and software over Windows. The instructions to install the Voyager-SDK on Ubuntu 22.04 actually worked pretty well. I was surprised.I ran into an issue at one point after installing the SDK: I couldn’t detect the Metis M.2 card. I couldn’t really figure out how to install the driver from the instructions for Ubuntu installation, so I had to download the .deb driver and install it similar to the “instructions for installing Voyager-SDK using Docker” to get the driver installed. Once the driver is installed, and the clunky SDK is installed and running, the demos with YOLO worked great, with the Metis M.2 card barely breaking a sweat doing inferences.