Wow, that is sharp!

We are currently testing the Banana Pi CM4 board. We hope to have results soon.

Did you get out email?

It looks like you ordered an Interceptor Carrier Board and a 5 HDD case from us, but not a CM4.

Yes it can. It doesn't have to, but we like to install our OS for testing purposes.

So, I cannot test this here because I don't have a CM4 Lite, but you should be able to install the OS to SSD/HDD, but you would still have to boot from USB because the bootloader is there. When you boot with our OS on a USB thumb drive, you should be able to select install, then install to your SSD/HDD and go through the installation process. Let me know if this is not the case. At the very least, you can boot from the USB thumb drive in "Live Mode".

Yes, if you are using our OS, you will have to setup the mounts manually. There is no automation to do that for you. For sda1, is that a partition on your 2TB ssd? Is sda2 another partition on that SSD or a different drive? I don't know how you created them, so it's hard to say why it won't mount. There are no restrictions for mounting drives, so this should work.

We'll get back to you today.

Ok, you'll be testing specifically the +3.3V rail. Start testing before you switch the power on and then follow it while it's powered on and booting. As soon as it's powered on it needs to stay near +3.3V. The FAQ has more detail on the issue.

We have not tested that PSU and I'm unfamiliar with the brand. If you have a DMM I can walk you through testing it, or you can look at our FAQ at our list of tested and reliable PSUs.

Hello @Daniel, please execute the following to see the config.txt: sudo mount /dev/mmcblk0p1 /boot/

Hi @Ryan Ayers yes, you can do this via a Raspberry Pi I/O Board. I'm not sure you need to do that yet. I've been thinking about this and wonder what PSU you are using to power your Interceptor Carrier Board. If it doesn't have a reliable +3.3V rail, it will misbehave in various different ways. Looking at your boot order, I think you should be good (I see USB, it's just not getting there). Could you try a different PSU please?

Yes, as noted elsewhere in the forum, for some reason some versions of Windows don't write the image properly. At some point, we'll look into that.

Our recommendation is f215 for the boot order. If you need to change that, you would need a Raspberry Pi I/O board. Can you share what your boot screen looks like right now with the USB flash drive with our OS installer on it? https://www.axzez.com/forum/interceptor-carrier-board/frequently-asked-questions#viewer-7pbl2

What you have on the CM4 eMMC is irrelevant. If you have the boot order set to include USB, you are good to go. Can you send us a screen shot of your boot up? Also, we have had some users who have had issues writing our imager from Windows (you can do a search here and find those discussions).

Our image is not meant to be flashed directly to the CM4. It is meant to be flashed to a USB flash drive. It is itself an installer, so when your system boots from the flash drive, it will ask you if you want to install the OS and walk you through that. You can then either boot from eMMC, eMMC+SATA (OS on HDD or SSD), or in live move (boot from the USB flash drive and run OS from the USB flash drive).

@Tom A. We released an updated OS today that includes the latest firmware and kernel being used by Raspberry Pi. It also includes a fix for the above issue regarding our driver reporting half-duplex for PoE ports even when they are full-duplex. The new kernel is based on 5.15.84 and the firmware is the latest released RaspberryPi firmware 1.20230106 (only updated by our installer if boot order is not what we expect). Downloads here: https://www.axzez.com/software-downloads

We released an updated OS today that includes the latest firmware and kernel being used by Raspberry Pi. It also includes a fix for a driver reporting half-duplex for PoE ports even when they are full-duplex. (see https://www.axzez.com/forum/main/comment/fccb0f68-5d43-4dfc-9927-0bc20db42131?postId=62632d56ed3c900016ce90d2). The new kernel is based on 5.15.84 and the firmware is the latest released RaspberryPi firmware 1.20230106 (only updated if boot order is not what we expect). Downloads here: https://www.axzez.com/software-downloads

@Pieter Geelen besides using a switching PSU it looks like you've done what is possible to reduce power consumption. The CM4 is not especially power conservative (see https://www.etechnophiles.com/compute-module-4-specifications-uses/#power-consumption-of-cm4), so there is not much that can be done here.

This looks like a power issue. When I saw your original message I thought you were going to tell me that you were using an old wired Mac keyboard (the one keyboard that doesn't work). I tested this fully before it went back to you and it was working perfectly, so that tells me that the PSU is most likely failing at some point. Could be under voltage protection (UVP) kicking in and failing to allow a full boot. You can connect up your DMM before starting up and watch to see if you lose power to any of the rails during boot up. https://www.axzez.com/forum/interceptor-carrier-board/frequently-asked-questions#viewer-26j64