Hi novski
I try with UEFI Firmware 1.34, 1.33, 1.32. I copy the Firmware manually without the card maker script as the script did run into errors on my Ubuntu 22.04.1. but that should not mattter as the rpi4b (as well as my cm4) start into UEFI Firmware and afterwards start into pxe boot. If i select the architecture armhf for machine configuration, pxe throws me to “error: invalid magic number” and “error: you need to load the kernel first”. If i select the architecture arm64, pxe trhows me to just the grub shell "grub> " Thx for the additional github link, see that already but didnt help as the process is failing already at the very begining.
Hi
I was able to commission a rPi4 and an CM4 successfully in MAAS (to device status “ready”) but what is strange is that at the same time the display of the CM4 shows different errors. So I will have to test the deployment of software before i can tell more.
What I found is that while armhf gave me the error you wrote (magic number) and does not commission successfully, an arm64 has a different error on screen but commissions successfully.
It looked like this:
EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot serivces...
Looks like you get the same errors as me except your rpis goes to “device status ready” and my rpis stuck at “PXE booting…” Did you use a specific Firmware and kernel and maas version or just the most recent ones ? Did you create the Firmware sd-card manually or with the script provided in the tutorial ?
@ troyanov: thanks for the hint. i try with Grub 2.06 and at least can get to the same state as novski (Commisioning went thru). Machines -> configuration -> armhf/generic (armhf, arm64/xgene leads to the “invalid magic number” error ). I will try to deploy a vm and report back if it works…
@billwear: sorry if me previous answer was confusing, just to be clear: i am able to PXE boot my cm4 and rpi4 (as per troyanovs hint to use the release candidate) so pxe in general works. Thanks for the link to pxe tutorial. Provisoned cm4 shows “ready” in the maas console now but deploy ubuntu hangs… but that is probably just me, don´t know how to deploy properly. I need to read thru the maas documentation.
Thanks for the fix and thanks for this great Software. I can confirm that it currently works with the CM4. I can comission, deploy ubuntu and create and run an LXD.
There is a big caveat (at least with the DeskPi-Super-6C-cluster-board):
The only possible Storage option is USB 2.0 . Even the internal eMMC does not work for deployment.
Flash the rpi UEFI Firmware to internal eMCC
Plug in a USB-storage
Start commision and chose the USB-storage as target.
This was the only way i could figure out to successfully deploy.
I tried with nvme ssd, m.2 USB3.0 controller and m.2 Sata controller. They show up in UEFI Setup and the attached drives are accessible in ubuntu server and Raspberry pi OS but they don´t show up in the maas machine storage configuration and therefore can´t be used for deployment (sata drives only show up in Raspberry pi OS as the drivers where not loaded per default in ubuntu server from the raspberry pi imager).
Another thing to take into consideration before buy the Deskpi-Super-6C board as a learning platform for maas:
There is no individual power-controll for the CM4s. Each CM4 Slot has a jumper that can be used to reset the CM4 but that is not enogh. m.2 usb and sata controllers do not re-initialize themselfes with cm4 reset. They need a power off, power on cycle to work properly. This leads to the next problem: Power off the board also powers off the cm4 with the maas controller.
Of course this applies to all Client/Server based Software and is not specifically related to MAAS but i thogh i should mention it if someone consider to buy this board to use it to learn maas.
What is your experience with MAAS and CM4 ?
Happy weekend everyone
It was just there. 1. Flash rpiUEFI to the onBoard EMMC. 2. Insert USB-Storage to USB 2.0 Port and PXE boot. Then the USB Stick was there under “available drives” in the maas comissioning console. I did not figure out yet how to integrate other storage drivers such as usb3, nmve or sata. I guess it depends on the USB-controller chip. If it is the same as on the rpi4 it should work. Usb-Storage: Flash Voyager GTX