CryBaby

I got mine booting again. The /boot/Image link hadn't been updated. Nor the links in / but I'm not sure they are necessary anyway. I have a desktop and network but ssh won't let me in for some reason. I'll have to get a keyboard and mouse attached. On the upside the fan is working 🙂 While I was rummaging around I noticed I have a dtb overlay for the fan. I thought I had disabled it. It was based on the one here but IIRC I cut it down somewhat. I can look into it more if you still have issues.

I am using zfs so I have to lag behind a bit. Also I have uboot not EFI. I actually tried to downgrade to current last night... and it wouldn't boot. I'm running from SD so I'll stick it in my laptop tonight to see what's what. Might try EFI if I have to start again.

I feel I should mention that 6.19.6 has problems for me (one core is constantly pegged for no apparent reason, some processes hang and can't be killed) so you might want to try current first (6.18.2?). It may not be optimized fanwise but it should still work.

It works for me on an edge kernel (I have 6.19.6). I think current kernels will work too. You can change them using armbian-config. Not sure if you will lose anything, the newer kernels are pretty feature-complete for RK3588.

You aren't telling us much, like what software you are using. I would expect you to need to give it something like smb://10.10.2.101/NAME_OF_SHARE/ or sftp://10.10.2.101:/path/to/folder You will also need to give it a username and password somehow. But first; have you checked you can reach it on the network?

What does that mean? What did you do?

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.

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.

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.

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

You can remove packages in Discover.

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.

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

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"; }; }; };

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.

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.

Will it cook my breakfast too?

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

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.

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.

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?

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.

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

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.

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.