uninvitedguest

After a little tinkering, I found that holding back the following packages during an ` apt update` allowed for recognition of the nvme ssd: linux-dtb-current-rockchip64 linux-image-current-rockchip64 linux-u-boot-rockpi-4cplus-current I'm going to test further to see if it narrows down to one package.

Hey, thank you for this! I went straight to a new install of Armbian on my 4C+ and used the Github linked releases - a build of 24.5 - and found that the nvme ssd was not showing up at all under lsblk or df. Without your post I wouldn't have thought to try the archived versions!

As per the title: Using the image Armbian_22.11.2_Rock-5b_bullseye_legacy_5.10.110 Formatting an nvme ssd partition as BTRFS and running the armbian-install utility, install using SPI to boot, targeting ththe btrfs partition, and selecting BTRFS in the prompt results in a failure to boot. Reformatting that same partition as EXT4 and rerunning armbian-install (and making no changes to the data loaded to /de/mtdblock0) targeting the EXT4 partition, and the device boots using the SPI loader.

As a fun new quirk, after having my board offline for a number of days, I've booted it up and the device mac address has changed - resulting in the DHCP server on my router assigning it a random IP address, even though armbian-config had been set to static as well.

Okay, at one point I was able to run armbianmonitor -u, but I wasn't able to post due to the daily post limit here. Now, when I attempt to run it I receive the following: rock-5b:user:# armbianmonitor -u System diagnosis information will now be uploaded to https://paste.armbian.com/ https://paste.armbian.com/ https://paste.armbian.com/ https://paste.armbian.com/ https://paste.armbian.com/ https://paste.armbian.com/ https://paste.armbian.com/ Please post the URL in the forum where you've been asked for. Luckily, the link was in my browser history. Here's the output: https://paste.armbian.com/alayababaf

Hey all. Running the Dec 9th build of Armbian 22.11.2 Debian Bullseye CLI, and I've been running in to issues with consistently remotely connecting to the board. While ssh and other direct connections (IP:Port for services like Nextcloud, etc) work for a bit after a recent reboot, after some unknown amount of uptime I'm unable to connect to the board through any new remote connections. Attempting an SSH session provides me the error ssh: connect to host 192.168.50.5 port 22: No route to host When connected via the serial console, I am able to verify that the board has internet access while it is refusing these remote connections on the local network. When I restart the board it starts accepting remote connections again. Not sure what to do to troubleshoot this or if anyone else is dealing with the issue.