Search the Community
Showing results for tags 'cubox-i'.
Found 4 results
-
Greetings; I have downloaded this https://dl.armbian.com/cubox-i/Noble_current_server and verified that I got what I was supposed to (ASC, SHA). I have used a brand new usbimager to install it on various freshly formatted (brand new SD Formatter) and verified working Samsung Evo 32GB, SanDisk Extreme Plus 16GB, Extreme Plus 32GB. All the formatting, imaging and installation done on an Ubuntu 25.04 laptop. After usbimager is done, if I use the Ubuntu Disks application to look at the drive, the first partion shows as free space, which seems suspicious. When I insert the newly-set up SD cards in the Cubox-i4, I see the bootloader start and then do its handoff to the operating system... and then nothing. No more signal on the HDMI cable, nothing out on ssh, nothing. The Cubox-i4 tries to reboot every few minutes with no more successful outcome. This same Cubox-i4 runs fine with the last SD card system disk I built for it using the previous Debian server image. Does anyone have any ideas? Thanks in advance! -
Looking for Armbian_20.02.7_Cubox-i_bionic_current_5.4.28_desktop.7z – anyone can share a copy -
Greetings to all; For a few hours now, as of today 2025-05-29 1418 North America/Pacific, I have been unable to update apt, receiving the following two error messages: E: Failed to fetch http://beta.armbian.com/dists/bookworm/Contents-armhf File has unexpected size (2085376 != 51213). Mirror sync in progress? [IP: 23.186.113.5 80] E: Failed to fetch http://beta.armbian.com/dists/bookworm/Contents-all File has unexpected size (44878 != 8029). Mirror sync in progress? [IP: 23.186.113.5 80] I suppose it is possible that the "mirror sync" mentioned is taking a very long time, but this seems unlikely to me. Does anyone have any ideas?
-
Hi, when booting Armbian Sid minimal rolling 6.1.11, there is no serial console login. Console output: Found U-Boot script /boot/boot.scr 1993 bytes read in 146 ms (12.7 KiB/s) ## Executing script at 12000000 93 bytes read in 94 ms (0 Bytes/s) 38318 bytes read in 2603 ms (13.7 KiB/s) 33621022 bytes read in 3482 ms (9.2 MiB/s) 11215360 bytes read in 1257 ms (8.5 MiB/s) ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 33620958 Bytes = 32.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800c5ad Starting kernel ... Is there a way to enable console login to use the device headlessly? Thanks
