Since you cannot trust this EMMC, @magixx256 Here is how to get log2ram up and running, plus a quick way to double-check your storage health. 1. Install log2ram Manually Run these commands to pull the official repository, install it, and get it running: # Download and extract the latest release curl -L https://github.com/azlux/log2ram/archive/master.tar.gz | tar zx # Move into the folder and run the installer cd log2ram-master sudo ./install.sh # Clean up the installer files cd .. && rm -rf log2ram-master Reboot to Activate It For log2ram to properly hijack the logging system and mount it into RAM, you need to reboot the machine: sudo reboot Verify It's Working Once the box boots back up, run your status command again: systemctl status log2ram You should see an active (exited) status (which is normal for this service, as it just runs a script at boot to create the RAM disk). You can also verify it's actively mounting by checking your system disks: df -h | grep log2ram You'll see a line showing /var/log mapped to log2ram with a size of about 40MB or 50MB. 2. A Quick Note on System Stability Since log2ram holds your logs in memory and only writes them to your eMMC/SD card once a day (or right before a clean shutdown), a sudden power pull means you lose the logs from that day.

The kernel 6.18 has the driver i2c-k1x, which is not present in 7.x. There is also i2c-k1, present in both releases. I'm using 6.18 with i2c-k1x, it seems that 10-bit addressing is not supported `i2cdetect -F 4` shows: 10-bit addressing no It seems that the bus is working with 400 kHz frequency, but I don't know why. I was reading driver source and for me if spacemit,i2c-fast-mode or //spacemit,i2c-high-mode is not present, then it shall be 100 kHz. I have no idea how to verify or change the baudrate. I have two sensors, first requires 100 kHz and it is not working, and the second is up to 400 kHz and it seems to be working (I can read some registers, but nothing special). Therefore I assume that bus is operating at 400 kHz.

Please note that ophub is not Armbian. They use the Armbian name without permission, do not contribute to Armbian development nor participate in these forums. Having said that, android TV boxes are a community supported effort under Armbian. It would be appreciated if you took the time to submit a PR to include your efforts into Armbian.

I think what you want to ask is "Can I use u-boot to boot Guix system", and the answer to THAT is probably yes, but that has nothing to do with armbian. What eselarm wrote above is what you have to learn/do and understand. IE, you would need to build Guix system using u-boot, and this forum is not the correct place to ask that question. Maybe ask in the IRC chat here https://guix.gnu.org/en/help/ and see if you can find someone that is willing to help out. Or maybe on the reddit: https://www.reddit.com/r/GUIX/ L1tech forum is pretty popular, maybe ask there: https://forum.level1techs.com/c/software/linux/27

I was searching for WI-FI Drivers for my X96 Mini because I was using my device with Armbian ophub's build. The only-ethernet thing kinda annoyed me so dived in and found there's a fix. A guy named lukas-kuna found a fix for the WI-FI chip (HERE). So I tried the fix and It really worked. So I decided to create a driver myself for Future use and for my fellow users. I used the Driver on Armbian 26.08 Build by ophub and the kernel version is 6.18.37. I created a Github Repo so I could share how I did it and how you could do it too. I Used DKMS to Automate the installation process, theres other ways to do it too. Also the DKMS method ensures driver doesn't disappear when switching to New or Different kernel. Here's the GITHUB REPOSITORY : https://github.com/rayhanorigin/SV6051-SV6051P-WiFi-driver-for-Amlogic-S905W-X96-Mini-with-DKMS-support. I'm Leaving the Driver File here as well. GOOD LUCK! NOTE: I didn't try the driver on openwrt because I have no interest on that thing. You may try because ophub's kernels are compatible with his builds of openwrt as well.