Active threads

Hey there! @arizonan so.. if your H96 is stock you wont need any of my instructions.. My box got bricked somehow and this was pretty much the "troubleshoot" to get it working again. What you need to do is follow this instructions: HERE

"While it didn't give an solution, " Well actually it gave many solutions, none of which worked! I've learned from this experience never follow an AI bot blindly, without second-guessing it's suggestions; it will lead you down the Garden path till Christmas. Many of its instructions in other aspects of armbian worked first time like a charm whereas this did not. I'll take a break for a week or two and think about it. Thanks for your suggestions......

Do you still have the download link for the ISO file Station M2 Armbian_community_24.11.0-trunk.167_Station-m2_bookworm_current_6.6.52_minimal.img.xz?

You will need to provide a lot more information. What image are you trying to use? What CPU does your box have? There are different generations of this box and from what I can see they all have different cpus.

Hi, First of all, sorry for lengthy post and that I ask a lot of things at once, I am very new to linux and this would be my first real experience. I am trying to set up home automation and home assistant server. As I am just getting started to learn all the ropes, I thought about what could be used for sečrver and I remembered that I have an old T9 android TV box see the attachement, I read through this thread and tried to follow the instructions throughout the posts. I burned the armbian image to sd card, which insterted into the sd slot on the T9 board, however I am unable to get the board to boot from the sd card. The box boots normally into android, when no SD card is insterted. When the card is inserted, nothing happens and the box does not turn on at all. It may be a big ask, but would someone be able and willing to help me find out the next possible steps? I feel a bit overwhemed as I am not very knowledgable in this field and unsure how to follow the instructions, or better said, I am not sure if I am following the instructions right. Thank you!

If you need an own build for some reason, you should be able to debug it as well. Why does it fail, others cannot know that from that screenshot. Also you yourself cannot. You need serial console etc, look into bootprocess of RPi, examine files and logs. In general it is rather simple compared to other SBC's, but still you need to do that yourself. It also might be an (additional) problem with you Pi or some SD-card adaptor etc/ Why can't you not use the standard available image? You can remove/tweak/add from there as well.

Ubuntu I see. That I do not have running, so cannot speak from experience.

Thanks for the feedback. This is welcome 👾 I'm currently fiddling with Wifi for the 6.18 kernel. No good karma: the adapted bcmdhd sdio wifi from the Spacemit kernel 6.6 was removed from 6.18. So I'm using the bcmdhd extension instead, as it's done with OrangePi 5, based on the github/armbian/bcmdhd-dkms repo. That one has ALLWINNER changes under the #ifdef CUSTOMER_HW_RK (probably Rockchip origin). I need to re-add SPACEMIT changes. Also, I need to revert a Wake-on-WLAN change submitted by Spacemit to RFKILL in order to get the necessary Interrupt init called. Bonus: OPi5-edge also uses that extension driver but does not compile b/c a PR for 6.17 on bcmdhd-dkms from October was ignored. Will need time 🤪 LG // Sven-Ola

Hello! I see you installed the 3318 image on the T9 and everything works fine. Congratulations! I'm not a big Linux expert, but I'd like to make a server out of it. I have the same console, but I'm afraid I can't handle it. I couldn't even find the best image for it...could you share your image for it?

I am thinking about getting a Nanopi R3S, which could be a better option, for it has a dedicated designed case for it. The CPU on it is the same one, so computation wise should be feasible.

Found the other partition! Quite surprised that it didn't show up in KDE, but that's on me for blindly trusting a GUI. Thank you

Hello Dear, After flashing *Armsom-cm5-rpi-cm4-io_*, there is one critical problem. onboard USB hub always connects and disconnects 2 times when booting. dmesg outputs: [ 6.190239] hub 1-1:1.0: USB hub found … [ 7.868081] rk-pcie 2a200000.pcie: PCIe Link Fail, LTSSM is 0x3, hw_retries=0 [ 7.868642] usb 1-1: USB disconnect, device number 2 … [ 9.326443] hub 1-1:1.0: USB hub found … [ 11.213062] rk-pcie 2a200000.pcie: PCIe Link Fail, LTSSM is 0x3, hw_retries=1 [ 11.213297] usb 1-1: USB disconnect, device number 4 I have tried with many variations, but the onboard hub is always disconnected. server/desktop community release/ self build several tags from 25.5 to 26.2 CONFIG_USB_ONBOARD_HUB O/X rpi cm4 io board/ Ochin board However, Armsom's official image has no problem with the onboard usb hub. CM4-nano-B has no onboard hub, and has no problem with external hub. So, it seems to be a SW problem. In addition (for information), I tried custom-build without pcie because hub disconnection happens near pcie. Kernel menuconfig disables Rockchip PCIe host cont/ Rockchip DesignWare PCIe cont/ Broadcom Wireless Device Drv. Device Drivers ---> [*] PCI support ---> PCI controller drivers ---> < > Rockchip PCIe host controller DesignWare PCI Core Support ---> < > Rockchip DesignWare PCIe controller ... [*] Network device support ---> [*] Wireless LAN ---> <*> Rockchip Wireless LAN support ---> [ ] Broadcom Wireless Device Driver Support ---> Then, both pcie and onboard-usb-hub disappear in dmesg even though any usb option is not changed. Please review this problem. Thanks.

Dear SteeMan, thank you for your answer. I checked Android info, and it shows 8 GB / 128 GB, Android 15, so the advertisement was not real. I investigate it forther.

@quaSimba: Thanks for your remarks and the link to the guide on Github. Hopefully I'll one day have a RPi to work with so I can support it in my script and tutorial. @fxkl47BF: The completion packages were removed because they can be horribly laggy on low-powered SoCs and I find them annoying in general. They can be easily reinstalled if desired.

I have a question about booting from sd card. While with empty emmc (erase with rkdeveloptool), the board falls back to maskrom mode even the sd card (with working os) is inserted. It can boot armbian into sd card if I flash miniloader and u-boot in to emmc. I wonder how can we get it to boot fully from sd card.

Unfortunately i do not have this board to compile/test on

by the way i can ssh into armbian while it’s stuck on a black screen so i can provide any logs you want

Appreciate the quick replies! Turns out im just an idiot, and completely forgot to freeze the kernel. have a great evening!

moved

ok

You use a Desktop/Xfce installation, and it is for a low-power ARM64 computer. So I would not be surprised if in modern Xfce, the Power Management default to suspends after 30 minutes or so. Last time I used Xfce was when Debian Buster, also then in then I remember in the GUI there should be some system setting where you can configure power settings. So there you can make sure that it never enters suspend state. I do not know how to configure that from command line, but that should also be possible, maybe search internet. You can also look into the journal and see what happened, maybe something is wrong. 7 Watts is way too high for suspend state at least, but maybe things connected on USB still draw power and is it only the CPU that is halted. Other option is not to use a Desktop image/installation, but a CLI for server/IoT variant. Those images should have suspend disabled.

This might help you: https://github.com/nyecov/roobi-config-anyOS It details how install basically any OS via Roobi

Just confirmed. Running bookworm on the same RockPi-S, it "just works". Any suggestions on what happened in Trixie and if there's a fix?

I missed the fact that you have an orange pi zero 2w... I think there's a success experience with that orange pi in this thread or in this Allwinner section. Please share if you have success

That's the version I'm running as well, and I have no issues either. I think replacing the device tree (.dtb) at this point only helps with the onboard flash speed?