laibsch

OK That would be called regression and should be analysed for a fix moving forward. Specifically looking for an older release as a "solution" still seems misguided and should only be done to bisect not as a kind of permanent solution.

OK what makes you think you got hacked?

No, Armbian has not become a total nightmare. But your posting all over the place, in several threads here and even Ubuntu ustream trackers with a bunch of unsubstantiated and obviously nonsensical claims IS absolutely a nightmare. PLEASE STOP! You make bogus claims faster than anybody can look into them. What made you think this was related to postgres? What makes you think Ubuntu downgraded their Gnome in Noble? Slow down, take a deep breath and stop being all over the place.

You do have a mmcblk0, why do you think there should be a mmcblk1?

@Igor Is this something that Armbian can add automatically for a board? Maybe that it did in the past?

Thank you for your generous offer, @coroner21. I am interested and would love to use this unit to keep it supported in Armbian Core. My goal would be to help keep it at standard supported status. I was already able to lift the BPi M2+ from community to standard support status. I have sent you a PM.

Thank you for sharing your success story for the benefit of everybody.

I cannot verify your claim that Ubuntu "reverted" to Gnome v44. Noble has v44 indeed. v46 is not anywhere in a Ubuntu release so my guess is you shot yourself in the foot with some random PPA or whatever repo out there. https://launchpad.net/ubuntu/+source/meta-gnome3 There is no shortage of boards out in the wild, nobody would think that. What there is, is a shortage of people willing to fund development, be it users or companies. Big shout out to those who do and to our volunteer devs, thank you!

Thank you for your work and I'm happy you fixed it for your installation. It would be good to have this be incorporated into Armbian itself.

I would not expect an older release to run cooler.

Thank you for confirming, @SteeMan. I had the feeling this was a TV box but could not be 100% certain without your expertise.

Hello Petersonn, hope you will enjoy your Armbian time!

good luck

great, keep us posted and be sure to invite Danubio to post here directly, too!

What is the brand name and model of your "server home assistant"?

I see you already went upstream which is probably the best place to discuss this. OTOH, you identified that this might be GPU driver issue which would likely require us to patch the kernel. May I ask if you got this running on regular Intel-hardware? Might be best to iron out some bugs there before moving on to the arm-challenge. I'd be happy to test this for you, but my SBC is headless, so I guess I am out?

github issue

I believe you are likely going to struggle with that approach. But I think before you ask us maybe you should say first why you chose the platform that you are considering. If it is "that is the cheapest I could find" then you might have heard about the saying "buy cheap, buy twice".

That is a wise thing to do and might be a good default for armbian to adopt.

OK, can you do the following for me, please, to be sure this is properly fixed? Kindly share the console output for me to have a look at. sudo apt reinstall wireless-regdb dpkg -S /lib/firmware/regulatory.db* Then reboot and see if your problem remains fixed. For now, I suggest you keep the wireless-regdb-2025.02.20.tar.xz file around on the NanoPi in case you need it again.

please share more information about the problem you ran into for the sake of the next guy coming to the forum to look for a solution to the same problem. Thank you.

some progress $ sudo rfcomm bind /dev/rfcomm0 41:BB:00:D0:D3:D8 && ls -l /dev/rfcomm* crw-rw---- 1 root dialout 216, 0 Jul 7 22:46 /dev/rfcomm0 but $ sudo hcitool info 41:BB:00:D0:D3:D8 Requesting information ... Can't create connection: Input/output error

please be sure to share whatever learnings you have with us

I'd say, boot from a different medium and then try the dd commands again (use pv for a nice progress bar) to see if you have the same errors again.

Thank you for reporting back. I am happy to hear you were able to find another way to solve the underlying issue without needing the v4l2loopback-dkms package anymore. I see you already have backports enabled but probably with low priority (as you should) by default. You can check "man apt" for information how to install that specific version (or use aptitude like I do). That being said, "sudo apt install v4l2loopback-dkms/bookworm-backports" should probably get you the version you need and hopefully it would install fine.