All Activity

Moved the post to the correct sub-forum.

@SteeMan Do you mean moving to TV Box Wi-Fi folder?

Today I did also the hardware fix for the 2.5Gbit Port & I can confirm nothing changed concerning the speed: Helios64 -> client around 200Mbit/s Client -> Helios64 2.35Gbit/s but unstable connection compared to 1Gbit Port, the transfer drops The switch monitoring indicates now 1 error. My Conclusion for 2.5Gbit Port: Not usable at all!

@Nick A The fact that the kernel is old, interferes with finding a driver for wifi ?

No problem. Good luck with the exams. And thank you for the interesting link. I remember there was a hype about fuzzy logic, when I was young and in college😀.

It was already mentioned that bluetooth is not working on boxes with AIC8800D40. Maybe is the bug describe here: https://github.com/radxa-pkg/aic8800/issues/14 responsible for that.

Hi @Ed van den Enden, After checking your provided information: [ 1.019881] sun6i-rtc 1f00000.rtc: registered as rtc0 [ 1.019937] sun6i-rtc 1f00000.rtc: setting system clock to 2025-04-22T10:04:37 UTC (1745316277) This actually shows the SoC provided RTC, not the i2c one. I cannot see any other RTC being picked up by the kernel, so it seems something is not working well with the overlay. Can you list the contents of /boot/overlay* and /boot/overlay-user ? And also, can you share the contents of the dt overlay "i2c-rtc,ds1307" ? (Not sure if that is supposed to be seperated by whitespace or a comma.) (Also not sure if 'dtoverlay=' is the correct keyword here, please check https://docs.armbian.com/User-Guide_Armbian_overlays/#armbianenvtxt-entries-reference to make sure you added the overlay correctly.) While you are at it, any possibility to get the U-Boot output? That will show if the overlay can be found or not. Groetjes, PS Check the topic below for how the same RTC can be made working on an OrangePi 0, which uses the same SoC as the BananaPi M2 0. There are two dt overlay files mentioned there that should add the i2c RTC (and name it rtc0) and one that will 'rename' the SoC RTC to rtc1.

@guenter I'm in the middle of exams at college, I'll be back to this board soon, I have other work waiting here for it too

Hi @Ed van den Enden, the blob shown was a device tree overlay. The device tree is the non-PCI variant of PCI config spaces. It specifies which hardware is located where and on what bus and so on. There are default device tree overlays for adding an 'external' RTC to the board, the one I shared is based on this, but just to make sure the 'external' will be 'found' first (and therefore updated by kernel). Edit: to be clear - if you choose to use a device tree overlay where the RTC is listed as the first RTC in your system, you do not need to use the script. If you do not use the device tree overlay to put your external RTC first in line, you can try if the script suits your needs. The scrip attached, you can just put on your system, somewhere in /usr/local/sbin/ would be my advice. To make it work, you have to trigger it during boot and on interval basis. I think I have it triggered from /etc/rc.local (not the best spot, but it works). Set proper ownership (root as owner and anyone in the adm group can execute): sudo chown root:adm /usr/local/sbin/rtc-sync sudo chmod 0750 /usr/local/sbin/rtc-sync Add to /etc/rc.local: /usr/local/sbin/rtc-sync -A start (Create and) Add to /etc/cron.d/rtc-sync: */22 * * * * root /usr/local/sbin/rtc-sync -A update The cron job will start rtc-sync 'update' every 22 minutes, which checks if the wallclock is synchronized by ntp. If so, if will update the 'freerunning' clocks with the wallclock. 'freerunning' means "not updated by ntpd" in this case. For all this to work, you do need to install and configure ntp. The ntp daemon will update the wallclock and the kernel will set the first RTC it sees (/dev/rtc0) with the adjusted wallclock it keeps. The kernel will not update any other RTC than the first one -> this is where the rtc-sync script will help. This update will happen every 11 minutes and is hardcoded in the kernel somewhere. (See https://unix.stackexchange.com/questions/285129/switch-off-11-minute-kernel-mode for some more info.) Hope this all helps, Groetjes, PS I forgot why I added the link to the topic about the NTP server with external GPS receiver... I guess I sometimes get a little bit distra

Take apart your tv box. Take pictures of all the components inside. Looking for your exact part number of your wifi module - mine was AP6330. Then I googled and found this person solved it on their tv box. But the procedure might work for other wifi chipsets. Just have a look in /lib/firmware/brcm and you will see plenty of them. Plus I believe that is the broadcom designs. Going up one level there are even more. WARNING - Not an expert... but this trick worked for me. Good Luck.

@sdavides You're welcome. I am glad you recovered your tv box 😀. Thanks for the link to your firmware file. But the link with "/file" did not work. I removed "/file" and this link works https://www.mediafire.com/file/6ndvrg9ze0v6eww/X3-9.0-2GB4GB-6330-0720-191119_1.img I will download the firmware file and make a backup of it on Archive.org web site. Please upload a photo 📷 of your tv TMAX 95 China tv box. Thanks. Cheers matey.

Description Enable video console on amd64 cloud images - for remote console access Enable video console on aarch64 cloud images - for remote console access Add additional packages to cloud images How Has This Been Tested? [x] Tested on aarch64 netcup cloud Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Maybe have a look again: The NanoPi-R6S has 2x 2.5Gb eth and 1x 1Gb eth and soldered eMMC and a openWRT variant pre-installed. Can be ordered with all metal fanless case. I ordered the C variant as I wanted an M.2 M-key for my already Samsung 970plus 500GB NVMe SSD. Idle is about 1.5 Watt with Armbian vendor kernel but it runs various other distros as well with a Armbian rockchip64 kernel. As indicated, I use mine as a generic compact computing box currently, but I can imagin people use the S variant as router as is.

I see that u-boot 2025.04 has applied some fixes to DRAM detection a month ago https://github.com/u-boot/u-boot/commits/master/arch/arm/mach-sunxi/dram_sun50i_h616.c so if the new u-boot 2025.04 via apt upgrade will be available in armbian for Orange Pi Zero 3, there is hope that the problem of incorrect detection of RAM size will be solved

@djurny I believe the first code you show me is in "C" and is a ds3231 driver. The missing driver in the today kernel. (Kernel: 6.12.23-current-sunxi) This driver would work for me but I have no clue how to compile. The rtc-sync program, makes sense to me but how can I make it to run?

For my complete log and Banana pi M2 Zero data, see: https://paste.armbian.com/yusewapuzi Kernel: 6.12.23-current-sunxi RTC module ds3231, connected to pin 3 and 5 (i2c0) 3.3V from 1 and 9 overlays=sun8i-h3-i2c0 dtoverlay=i2c-rtc,ds1307

First problem was fixed in predicted way. There is no more firmware warnings on upgrade / kernel install. New package is getting to the stable repository in a couple of hours, while it is already present in beta. Agree. While testing kernel, I installed Ubuntu Noble based image and ERROR: Unsupported initramfs version does not manifest there! I suspect this problem is caused by some script that is coming from RaspberryPi OS - on Debian based Armbian, we use userspace and Rpi related firmware packages from RPi OS (which is Bookworm based, so we have great / full packages compatibility). I will try to get to the bottom of this when possible. Basic problem is that in open source and especially in packages assemblies, there are always (tens of) thousands of potentially irritating issues. You noticed this one, we already have a list of many others that needs attention and there is endless list that well always be somewhere ...

Ver 20250423-edge kernel 6.15

Moved

Thanks maka for replying. Issue is resolved and Ethernet is working now. I did not read the first email from Maxio tech properly and I was sent files for MAE0621A-Q3C rather than the MAE0621A-Q2C which I have. Maxio tech kindly sent me files for MAE0621A-Q2C yesterday and I managed to compile it into the current kernel 6.12.24

I don't use my Clearfog Base as a filer or anything, but I much prefer to have some snappy storage on systems that I access frequently - and since this system is my firewall, I end up working on it often enough. When I'm not at home it's often where I push files - so running off an SD card is right out. For years now I've been using an m.2 SATA drive which has been fine, but it's got a minipcie slot just sitting there that I've never used... it's not particularly fast (PCIe gen 1 x1) but with one of these and an m.2 NVMe drive (the older the better...), you can get much better perf than SATA. You can't boot off it (at least I don't know how to make that happen) but it's easy enough to do that via an SD card or SATA and use one of these for the root filesystem or /home, etc.

Thanks for those that answered. I was hoping someone would bring up a board targeted at networking (router / firewall) that was well supported by modern software, but nothing is really jumping out. Here are some more random thoughts on the matter... since my previous experience was with SolidRun Clearfog Base (and with Armbian it was quite positive!) I am interested in their newer Clearfog CN9130 Base but it's a bit expensive and I'm hesitant to use anything not supported by Armbian due to poor experience with vendor images. But it looks cool! MACCHIATObin double shot isn't new, and doesn't have the best support either from what I can gather - but it also is attractive. And lastly, Honeycomb LX2 is pretty boss as well - but it also is a bit dated now, isn't cheap, and seems to have not caught on well so doesn't have great software support. All of those seem like nice hardware but I don't expect the software experience to warrant buying one. I had an impulse to buy when I saw the new dual 2.5gbe HAT from Radxa as I have a Rock 4a that claims to support it. I've had that little box in use as a container host running simple services like DNS, DHCP, Unifi controller, etc for a long time now and it's been nothing but reliable - though I do need to evacuate it so I can try bringing it up running Bookworm (it's on Bullseye still - but it's stable!). But I just noticed that maybe its own software support is rotting... it's community supported and the last Armbian image for it is quite old, so maybe I shouldn't put any more money or effort into it and let it do its thing. Dunno. But yeah, a tiny system that is quite low power which supports 2 x 2.5gbe and 1gbe along with NVMe sounds pretty nice especially since I already own the SBC... I suppose what I should really do is continue to ride my existing router until it dies. Considering I locked the kernel and firmware I expect it will work for a long while at this point, though I don't figure it to be able to upgrade to the next major Debian release once it's available. Maybe by then the support for Rock 5 ITX will be solid and I can start using it for this. If anyone else runs Armbian systems as their firewall, please chime in with thoughts and experiences!

Off-topic, but related to "trixie / sid" on RPi4 On a freshly written 64-bit raspberrypi os bookworm (Lite) image, replaced word "bookworm" by "trixie" in following two files: "/etc/apt/sources.list" and "/etc/apt/sources.list.d/raspi.list" . After above modifications, ran following commands: sudo apt update sudo apt full-upgrade sudo apt autoremove sudo apt autoclean sudo reboot The upgrade command took about half an hour to complete, and upgraded 470 packages. No issues during & after upgrade. Everything is OK.

Hi, anybory know The STV-2000 Aquário tvbox? It's brazilian make, It a gxl-s905w-p281board, this old product, but can install armbian in interna memory? Thanks

TV Box Name: Sunvell T95Z plus Octagon shaped box (Beware – apparently a lot of variants) CPU Amlogics S912 Armbian build file name: Armbian_community_25.5.0-trunk.370_Aml-s9xx-box_noble_current_6.12.23 DTB file used: meson-gxm-vega-s96.dtb (but several seem to work… none with wifi out of the box) Kernel Version: 6.12.24 Distribution Installed (focal, buster, etc): Noble Working Ethernet (Yes/No): Yes Max Ethernet Speed that works (100/1000): Not sure how to determine... Does wifi work (Yes/No): YES *** See Below Does bluetooth work (Yes/No): Not tested Does HDMI audio work (Yes/No): Yes Additional Comments (provide any additional information you feel is important): Tested many files. Ubuntu (noble) seemed much more usable than Debian (bookworm) Also tested Armbian_community_25.5.0-trunk.334_Aml-s9xx-box_bookworm_current_6.12.21 _gnome_desktop.img.xz Armbian_community_25.5.0-trunk.334_Aml-s9xx-box_noble_current_6.12.21 _gnome_desktop.img.xz Armbian_community_25.5.0-trunk.334_Aml-s9xx-box_oracular_edge_6.14.0 _gnome_desktop.img.xz Armbian_community_25.5.0-trunk.334_Aml-s9xx-box_oracular_edge_6.14.0.img.xz Since I am trying to learn server/media center/adguard or pihole stuff – chose the server headless install eventually. Learning has started. **** Thank you thank you to @ZuiMelanieForno and their post here: But basically looks like the easy way is to create a soft link of the ap6330 driver file as the brcm4330 file that must be loaded by default. sudo mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old sudo ln -s /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt Not sure of this solution will survive update. (UPDATE: Confirmed - it does not survive update - but doing the commands again and a reboot seemed to work.) I have installed pihole and had it running. I had jellyfin running. Rebuilt from 0 again and am trying to do inside of docker containers. Dockers seems running but still some learning to go. If I write my sd to my eMMC – can reset to 0 again by booting from an sd card … and when ready burn that to eMMC? Or should I keep the writes to the eMMC as few as possible? I own two of these boxes – Identical on the outside but the newer one (bought probably 1 year later) does NOT have an eMMC. It has the dreaded NAND chip(BiWIN 16GB)… Also a different wifi module I think…. (LTM8830) Oh and – can I just say I love pulling this thing out of retirement and having a tiny low cost media server in the house. Thanks @balbes150 and @SteeMan and Everyone for their hard work! This is amazing... until I blow it up again...