AaronNGray

@Igor - Can you have a look at this please. I have retrieved the devicetree's for the radxa Debian release on which the fan works and my Armbian Ubuntu build using dtc -I fs /sys/firmware/devicetree/base uname -a lsb_release -a https://github.com/AaronNGray/radxa-rock-5b-plus The 'pwm-fan' nodes are the same.

Yeah fan working on :- https://github.com/radxa-build/rock-5b-plus/releases/download/rsdk-b2/rock-5b-plus_bookworm_kde_b2.output.img.xz

From the Circuit Schematic it looks like the Radxa Rock 5B+ RK3588 GPIO0-C0 is the fan I/O, GPIO pin 24, if thats correct. I will verify I can access this on the Armbian distro.

I have the default radxa image rock-5b-plus_bookworm_kde_b2 image with the fan working :- https://github.com/radxa-build/rock-5b-plus/releases/download/rsdk-b2/rock-5b-plus_bookworm_kde_b2.output.img.xz I/We need to try and find how this was built and the Linux DTD file the `uname -a` kernel reports as "Linux rock-5b-plus 6.1.84-1-rk2410" kernel. rsetup :- https://docs.radxa.com/en/rock5/rock5b/getting-started/interface-usage/fan https://github.com/radxa-pkg/rsetup

I am using :- [ Ubuntu 24.04 (Noble)](https://dl.armbian.com/rock-5b-plus/Noble_vendor_server) from :- [Radxa Rock 5B Plus - Armbian](https://www.armbian.com/rock-5b-plus/) Trying to turn fan on on Radxa Rock 5B+ selecting the device using armbian-config actually makes it disappear I am getting `line 3: echo: write error:Device or resource busy`

I have not personally modified armbianEnv.txt, I do not know how to. As I say I think the machine has been messed around with, i.e. it has been hacked.As I say I am trying to work out how to reenable /dev/mmcblk1.

Weird its doing it on all distros and builds have tried so far including Debian. I can only think it must be the boards firmware ?

@djurny No, its not a simple as that, its acutally not on the install on NVMe anymore.

The Gnome desktop Power off menu selection and `sudo shutdown now` both reboot rather than powering down.

At the same time as mmcblk1 disappeared someone had changed the ethernet port over to the secondary port as I could not get into the machine and tried the second port which had been configured to the same static IP address as the primary port was on.

>PLEASE STOP! This is both a time and money nightmare for me. I am giving as much information as I can in order to give feedback in order to get support. What I am posting is not all nonsense ! Okay the Gnome downgrade was incorrect and was based on what ifnformation I could get at the time. Why the issue system put up the postgres tag I really don't know I removed it. It is now repeatedly demostratably kernel dependant. On 6.12.32-current-rockchip64 and 6.12.39-current-rockchip64 the display is failing, 6.12.22-current-rockchip64, and 6.12.17-current-rockchip64 the display is working fine. 6.15.1-edge-rockchip64 is also working fine. No sure about 6.15.7 6.16.0-rc3-edge and 6.16.1-edge are not even booting, with BananaPi-M7. I am going to get kernel output using USB UART for all these boots.

mmcblk1 should be the uSDcard it is on Nobel and Bookworm, it was there before I got hacked as well.

Armbian has become a total nightmare. Things keep breaking and theres no way to get a proper build of a past state anymore, so if I loose a copy of the original image I used for a machine then I am stuck again. Stuck with hardware that will not work again. And this hardware costs a lot of money, and its a lot of time too. Why Armbian was not written with this in mind I really don't know ??? The tree kernel lines supported seem to change randomly and are not in alignment with the linux kernel versions or seem to change randomly just at the wrong times.

Same problem when I put `KERNELBRANCH="tag:6.12.22"` in userpatches/lib.config

Its not working on a cleanly installed repo of Armbian/build ! userpatches/config-test.conf ``` EXPERT="yes" DEST_LANG="en_GB.UTF-8" BOARD="bananapim7" BRANCH="current" KERNEL_VERSION_LEVEL="6.12" KERNELBRANCH="tag:6.12.22" ``` https://paste.armbian.com/zoheruvemi