laibsch

Just came across this and thought maybe it can help you guys in getting better board support. No idea ;-)

Compiling your own image is actually quite easy. https://docs.armbian.com/Developer-Guide_Building-with-Docker/ https://evilolaf.github.io/docupreview/Developer-Guide_Build-Preparation/ https://www.youtube.com/watch?v=kQcEFsXEJEE The name of your board is "rock-5t" and you will want to try out the vendor kernel, try something like "./compile.sh BOARD=rock-5t BRANCH=vendor RELEASE=noble BUILD_MINIMAL=yes KERNEL_BTF=no SHARE_LOG=yes". You will then share your logs and you can paste a link here if the build fails. "qmicli: command not found" means you do not have the package installed that provides the command. So, you need to find out what package that is and then install it. I suggest you install "sudo apt install command-not-found" first and then this information will come up automatically in the future. # from my computer $ qmicli Command 'qmicli' not found, but can be installed with: sudo apt install libqmi-utils This situation will be a learning experience for you, it is not very likely somebody will come out here and fix your situation for you (unless they have the same problem and want to fix it for themselves and then change something in Armbian for everyone's benefit). People are very willing to help and guide you, but you will essentially need to fix this for yourself and then hopefully share what you did so that others will benefit from your work. That is the power of open source.

Thank you for sharing your logs. Have a look through my post where you can find lots and lots of commands I used for troubleshooting my bluetooth situation. Go ahead and share some of that information yourself and people might be able to spot the issue and guide you in the right direction.

Hello @swthpk32 The Radxa Rock 5T in Armbian is maintained by @meco, maybe he will have something to say. I don't have the board, so I will only be of limited help. Have you tried some of the commands given in the thread you linked and what was the result? Can you confirm that your modem shows up for a second and then disappears? Can you compile your own image with a vendor kernel? nmcli -m 0 sudo dmesg | grep usb

we need full logs of your compilation. Run like "./compile.sh [...] SHARE_LOG=yes"

@djzort just posted his success story including information on how to get around the issues he ran into. Check it out, @bsammon

Lovely @djzort, thank you for sharing. Do you think you can come up with a list of things that need fixing in Armbian to improve the user experience? Would you be interested to join as Maintainer for the Pinebook Pro in Armbian alongside @rpardini?

worked fine for me. sorry to hear that. what specific issues did you run into? It should be fairly straight-forward to compile armbian. git clone https://github.com/armbian/build cd build ./compile.sh

That's all it really means to be a maintainer in Armbian, though. People can look up in the board config that you have the machine and are - time permitting on a best-effort basis - willing to check for and verify devivce-specific issues. Nobody in Armbian knows everything about the project and its boards or even a single board and nobody expects you to. What I have seen from you is more than enough to join @chainsx in his effort to improve support for the board. Again, at the very minimal your commitment can kind of go as low as being willing to try and reproduce/WFM device-specific issues, your time permitting. In this thread you've already done way, way more than that. I'd really like to welcome you to the official Armbian maintainer pool. If ever you have a question, don't hesitate to ask me personally or in our discord server. BTW, on the topic of missing firmware which started this thread, maybe it needs to be added to armbian-firmware, something I've also only discovered yesterday, thanks to @c0rnelius.

Absolutely, and I believe that @tabrisnet could be a great addition to the team of supporters. In case he wants to do that. He certainly seems to have a good skill set and required curiosity.

Thank you for your continued work on this. Would you be interested to step up as official maintainer for the board, @tabrisnet? @chainsx, what do you think?

The Orange Pi Zero+ is community maintained. That means, there is no guarantee that the device even gets boot-tested. Going through git log I don't see much activity related to this board for the last two years, so quite possibly this is very stale. Current maintainer is @schwar3kat. Maybe he can tell us more if he can reproduce your issue. If you are able to test this board and fix issues to improve support for it in Armbian, your contributions are more than welcome. I do not have the board and am not aware of anyone who owns it.

If I were you, I would first try to get headless working, log in via ssh and fix things from there.

@Eng.ahmedflash Sounds to me like you are mistaking this volunteer effort with support from your vendor. I suggest you redirect your request to whoever you purchased your board from.

@Piotr Kędzia Have we found ourselves a future Orange Pi 3b Armbian Maintainer? ;-)

@Piotr Kędzia Please try one of the Armbian images from https://www.armbian.com/orangepi3b/

I don't see any images for download from Armbian for the Turing RK1. But the turing-rk1 board definition exists. Your best bet is to compile your own image.

"docker container ls" will show you the right ports.

Another report of this issue. Went away on a second build attempt according to the user @uablrek.

an orangepi5-plus compilation succeeded just fine now, so this error is not deterministic

split off the issue from the original into a separate thread Essentially the problem here is that one of the mirrors is apparently redirecting from https to http. This has been a problem in the past and was supposedly fixed, in fact more than once. Obviously, it's never been fixed properly for all cases or there was a regression.

You fail to mention which OS and which release you are running. https://packages.ubuntu.com/noble-updates/torbrowser-launcher is not working for you? Frankly, I don't find 5 and a half hours of compilation time unbearable, but you could also look into using a Launchpad PPA to offload the compilation effort.

merged

I can confirm: https://paste.armbian.de/oxupahozud

Not sure if the target board makes a difference. But FWIW, my compilations for rockpi-4b and orangepi5-plus exhibited the issue while the one for bananapim2plus did not.