@Antony Derham, it is my belief that you have a loose connection with the Realtek IC and it was exposed by the move to the new case. I believe this is a manufacturing defect. We'd like to go ahead and replace this board. We'll get one shipped out to you shortly. We apologize for the inconvenience.

We've just released the official images that contain all of the previously mentioned fixes, plus we've updated to the very latest Linux mainline kernel version 6.6.18: https://www.axzez.com/software-downloads The previous test images are nearly identical to we reviewed, tested, and released this evening, except for the newer kernel, some refinements to the kernel build, and improvements to the self-test.sh script contained in the OS image. We really appreciate the feedback from those of you that shared and hope you'll continue to share suggestions, issues, and improvements we can make to the images. Thank you!

We have new images available here for download and I've verified the docker issue is resolved: https://www.axzez.com/forum/interceptor-carrier-board/os-test-images-available We're still working on them, but these are very close to the end result for our next official OS release.

We feel that Debian packages are signed, so it good and acceptable to get from plain http sources. We will use deb.debian.org/debian instead of the ftp.us url, though. Of course, once you have the OS, you may manipulate source.list however you like.

OMV docker is now fixed. Using the same link as above.

There is an issue with docker on the OMV image. We're investigating.

I've reproduce the "flakiness" for OMV, @Attilio Bonaccorso. No need to elaborate for us. I'll get that resolved ASAP.

@Attilio Bonaccorso Thank you for the feedback. When you say "flaky", would you mind elaborating a bit? We want to get this right. Was it an issue specifically with docker? I'll see what the test results were for it on OMV. Regarding your posts in September and October, we did respond to you with updated and verified images that supported Docker at that time. It was before we switched to the new kernel, I believe. I don't see a reply after our last post there, but perhaps you had given up at that point? We want to get this right, of course. We will keep on it until we get it right. Thank you, Attilio.

We do not support a way of doing this with the Interceptor Carrier Board, unfortunately. We do discuss this in the FAQ: https://www.axzez.com/forum/interceptor-carrier-board/frequently-asked-questions#viewer-7pbl2

@Attilio Bonaccorso We have released multiple images in the last year and several of them had docker support. Only recently when we changed to the mainline kernel was this broken again. We have made available images that we are currently testing (see below) that resolve this, plus provide a whole lot more, while still using the latest mainline Linux kernel. If you are using a CM4 lite, with no eMMC, you would have to know what you are doing to use those images by installing the startup on the USB with the rest of the OS on the SATA. Our images provide this. Others out there have instructions on how to do this if you want to do this yourself. Our latest patches apply just fine. If you encounter any hunk failures or context mismatches due to version differences in the Linux kernel, you might need to apply the patch with a fuzz factor. Use the patch command with the --fuzz option to allow for some discrepancies. If you want to share what your process/steps is/are, we'd be glad to offer help. Others are using this without issue. Our patch is based off of the latest kernel. I am sorry to hear that you feel you've wasted money. We provide the OS as a free service. We really want to help customers get the most out of their hardware and we hope we can work with you to get your board running the way you need it. Many customers are not using our OS at all and are doing their own thing. We will continue to provide updates to the OS as people have requests for new features and new kernels. If you want to try our next OS versions that we hope to be posting soon, the beta versions are here: Desktop RPi with kernel 6.6.17: https://nyc3.digitaloceanspaces.com/axzez-build/image/desktop-interceptor-raspberrypi-cm4-customer_requests.img OMV RPi with kernel 6.6.17: https://nyc3.digitaloceanspaces.com/axzez-build/image/omv-interceptor-raspberrypi-cm4-customer_requests.img

@cvertesi please check out this dev branch build for OMV if you are interested. It should meet every requested change you and others had: https://nyc3.digitaloceanspaces.com/axzez-build/image/omv-interceptor-raspberrypi-cm4-customer_requests.img If my testing is successful and code review is approved, this image will be identical to what we release. Thanks again for your patience.

Excellent! Enjoy!

@cvertesi if you are in the mood to test, this version I just built has every fix that everyone in the forums has requested. The co-founder that usually maintains this is out, so I took a stab at it. I verified your https in apt sources is good, raid is good, nfsd support, add ufw (didn't test it) and that the self test is satisfied. I'm having problems with the OMV build (could be related to the updated kernel or to the k3s updates my colleague made, don't know yet). Anyway, here it is. Latest kernel 6.6.17 too. https://nyc3.digitaloceanspaces.com/axzez-build/image/desktop-interceptor-raspberrypi-cm4-customer_requests.img This is a branch build of the OS. I'll keep working the OMV issues (tomorrow).

Hello @Gordon Gerard, I understand you're looking to enable SSH access on your OpenMediaVault (OMV) system. SSH is disabled by default for security reasons, but you can easily enable it through the OMV web interface. Here's a quick guide to get you started: 1. Log into the OMV Web Interface: Use your admin credentials to access the OMV web dashboard. 2. Navigate to Services: Find the 'SSH' option under the 'Services' section. 3. Enable SSH: There will be an option to enable the SSH service. Make sure to check or toggle this option to 'On'. 4. Configure SSH Settings: You can also configure additional SSH settings here, such as disabling root login, enabling public key authentication, and more, according to your security preferences. 5. Add User to SSH Group: If you haven't already, ensure that your user (in this case, you're using the default 'admin' account) is added to the 'ssh' group within the 'User' settings to allow SSH access. 6. Apply Changes: Don't forget to save and apply your changes. OMV might prompt you to apply pending changes if you navigate away from the page. Please ensure that you're following best practices for SSH security, such as using strong passwords, employing public key authentication, and possibly changing the default SSH port to reduce the risk of unauthorized access. For a more detailed guide and additional SSH configuration options, you might find the OpenMediaVault documentation and community forums helpful. Here are a couple of resources that could assist you further: • OpenMediaVault Official Documentation: SSH Overview and Configuration • Community Guide on Configuring SSH and Rsync in OpenMediaVault: Zen Software Blog If you have any further questions or encounter any issues, please don't hesitate to reach out. We're here to help!

Thank you for your feedback, @cvertesi. We anticipated that the re-post of build 913 would only fix the OMV/Desktop image mixup. For NFS, as noted before, the client is built-in to the kernel, so no modules. NFSD is built as a module with our newest image, but we haven't released it yet. Regarding the delayed release of a new version, our CI/CD infrastructure experienced unexpected failures, complicating our release process. We've been actively working with our CI/CD provider and conducting extensive research and testing to resolve these issues. With our infrastructure now stabilized, we're focusing on ensuring the upcoming release addresses these critical features, including NFS, software RAID, and firewall support. We have some other customers with requests as well. We understand the importance of these features and are committed to providing a robust OS image for OMV, Desktop, and OpenWrt. For users requiring immediate solutions, our website offers patches, and we encourage building a custom OS from our provided resources if our current offering doesn't meet your needs. Several customers have used this option. We're also in the process of developing a legacy OS downloads page for accessing previous released versions of OS. As the OMV image is a relatively new offering, the selection will be limited as you'd expect. I will see if we can't add a note to the OMV download regarding the missing components if we can't get the images out today. I'm sure we can do this. We certainly value your support and understanding as we work through these challenges. Your feedback is crucial in guiding our efforts to improve. As a small team start-up, we will keep doing our best to enhance our products and services, ensuring they meet the needs and expectations of our user community. Thank you for being a part of our journey.

Great news. We're glad you are up and running!

There are a couple reasons you can get that "USB MSD Timed out after 20 seconds" issue. My first guess is that it's the Windows issue that some of our other customers have seen when writing our image from a Windows machine to their USB flash drive (not seen on all Win machines and not seen on Mac/Linux). Another reason could be that the power supply is incompatible (we discuss this in the FAQ). If you don't use the Axzez Interceptor OS, you can certainly follow the instructions of others on the OMV site. If you do this, you will not have access to our add-on boards for PoE, but it sounds like you might not be using that anyway. Do you have someone with a Mac or Linux box or perhaps you have a regular Raspberry Pi or I/O board that you can use to write our image to your USB flash drive? To clarify: "we provide an imager that is a combination of a live boot to our image and an OS (our image) installer" - what I mean here is that this is all of our images. They all have this behavior.

No HDMI on the IO board is certainly telling. A second CM4, as you've ordered, should tell us what we need to know. I personally cannot imagine if your HDMI cable and monitor work elsewhere, that they'll not work here, but I'll do some digging on that. I've used wide screen monitors (DELL) with our Interceptor systems. Since you know it boots, I guess we don't need to go the DMM route and test your PSU output. (just thinking out loud). You don't happen to have another monitor to test with do you? Maybe a friend has one you can borrow?

It is very unlikely the both HDMI ports are bad. They are completely separate from each other and both run directly to the CM4. Even if there were slight issues with the traces running to the ports, you would still get mixed up garbage on your screen rather than nothing at all. We look forward to hearing your restuls. I am also glad that they are in good supply again. What a nightmare that was.

We were finally able to resolve our image build issue, so we'll start crankig out new images soon. We have several requested updates that we have coming. Last week we did make the last stable images downloadable from our site. These images were re-verified.