[Edit ArmbianEnv.txt when machine is unable to boot?]

If there is nothing in /boot at all then its content is probably in another partition which gets mounted while booting. You will need to find that partition and mount it in your PC to modify it. 

[Edit ArmbianEnv.txt when machine is unable to boot?]

If the file is not in /boot could you have accidentally deleted it? Maybe try recreating it.

 

In general, if you have boot problems you should attach a serial to USB cable and see what uboot is saying.

[Complete beginner.]

I would check out the boards with Platinum Support. Go to the vendor sites to see if they include or sell a fan for their board.

Look for something with a Rockchip RK3576, plenty of RAM, and EMMC or UFS. RK3588 usually needs a fan.

[Update issue]

Did you do Update All after removing knotes?

If you were running wayland you will probably need to use Ctrl-Alt-F3 as wayland uses F1 and there is an (unusable) X server on F2 for xwayland. Then, after logging in

sudo apt update
sudo apt full-upgrade

If that's not enough try

sudo apt install task-kde-desktop

[Update issue]

You can remove packages in Discover.

[Update issue]

It looks like knotes has been replaced with Marknotes. Remove knotes and, if you like, install marknotes. It is supposed to import your old knotes data.

[Version `25.8.2` of kernel, dtb and/or header package on Armbian Ubuntu Noble break `zfs-dkms`]

What version of the kernel is being installed? As yet ZFS only supports up to 6.16.

[CM3588-NAS HDMI Audio enablement]

The armbian edge image for the FriendlyElec CM3588-NAS is currently on kernel 6.17 but has no HDMI audio despite it having been added in 6.15 (I think). This is simply because it has not been enabled in the device tree for this board. You can enable it with this user overlay:

/dts-v1/;
/plugin/;

/ {
        fragment@0 {
                target-path = "/hdmi0-sound";

                __overlay__ {
                        status = "okay";
                };
        };


        fragment@1 {
                target-path = "/hdmi1-sound";

                __overlay__ {
                        status = "okay";
                };
        };
};

 

[Where to Start]

I would put boot and system on the eMMC. Then it will run with or without the SSD, which I would reserve for data. Things like VMs and containers that get a lot of writes can go on the SSD and be symbolically linked to their system folders.

[Where to Start]

Sounds to me like a bad SD card. If you get a splash screen there must be some sort of bootloader. Another possibility is an inadequate power supply. Try one with more amps.

[[Armbian newsletter] - Armbian Unified Kernel Initiative (AUKI): One Kernel to Power Them All]

Will it cook my breakfast too?

[Cubietruck Bluetooth with mainline kernel]

linux-sunxi@googlegroups.com is where they used to hang out but I don't know if they are still active there.

[Curietruck has only console through HDMI]

https://docs.armbian.com/Developer-Guide_Build-Preparation/

 

Once you have the code installed copy the above-linked patch to build/patch/kernel/archive/sunxi-something/ and do the compile.

[Curietruck has only console through HDMI]

There is a patch. It doesn't appear to have reached mainline yet. Perhaps it could be added to Armbian builds.

 

You probably want to go back to your original, working, kernel.

[cubieboard 3 rtc & nand]

I believe the nand is not supported. This is not a great loss as it is flaky and unreliable.

 

Not sure about the rtc. Do you have a battery?

[Why, when working as root do I still need sudo in front of some commands?]

This is likely a $PATH issue. usermod is in /usr/sbin which is probably not in your user's $PATH. If you su without adding - you do not get root's $PATH but with sudo you do.

[Armbian - what kind of error is this?]

That does look like a bad SD card. If another one works that would tend to confirm it.

[Armbian - what kind of error is this?]

I would guess you have fiddled with /etc/fstab or copied your root partition from elsewhere without fiddling with your /etc/fstab. Or maybe /boot/armbianEnv.txt

 

At any rate, the kernel is looking for a partition with UUID=0b77.... to mount at / but isn't finding it. So you need to either change the UUID it is looking for to the one your root partition has, or change your root partition to have the UUID it is looking for.

[How to program orangepi to auto restart?]

You could set up a cron job to reboot it every so often. Log in with PuTTY and type

sudo crontab -e

This will open the default crontab in an editor, probably nano. At the end of the file add the line

0 * * * * systemctl reboot

to reboot every hour on the hour. It needs to have a newline at the end, ie. a blank line at the bottom of the file.

man 5 crontab

will tell you more.

[Bluetooth on cubietruck doesn't work]

I haven't tried it lately but it didn't work last time I did. It looks like everything is in place but it does't actually work. My conclusion was it is a bug or at least a lack of support for the hardware.

[Problems with Cubietruck]

A better power supply might fix 1 and 2, they can go bad over time. 3 is a bug, sometimes you will get a connection, but mostly no carrier.

[wierd network problem w cubieboard2 allwinner A20]

CONFIG_GMAC_TX_DELAY seems to have been added to uboot in 2015 so the question is is it being set in armbian? I don't know if it can be set in bootEnv.txt or you have to set it at build time. I don't have access to my cubietruck right now...

[wierd network problem w cubieboard2 allwinner A20]

That looks like it is working to me. I have been fiddling with my cubietruck recently and I notice that it doesn't always connect to the network too, so maybe the problem has nothing to do with your carrier board.

[wierd network problem w cubieboard2 allwinner A20]

I have no clue, but maybe you will find one in the system logs.

[Cubieboard2 and armbian 6.1.33..]

I don't believe mainline kernels support the NAND, and aren't likely to as it is flaky.

I would try whatever the current image is and see what you get.