Search the Community

Just ran `apt-get dist-upgrade` on my Orange Pi Zero LTS with Debian minimal Armbian, and wireless network is gone (not shown in armbian-config). Tried downgrading to legacy kernel without success. I have not yet tested 24.08 from a fresh Armbian image; I'm probably going to restore previous 24.05 from a saved backup image. Just sharing this issue in case others see the same thing. No errors in dmesg ... $ dmesg | grep xradio [ 12.723829] xradio_wlan mmc1:0001:1: Input buffers: 30 x 1632 bytes [ 12.723867] xradio_wlan mmc1:0001:1: Firmware Label:XR_C01.08.52.58 Jul 19 2018 18:53:57 but wlan0 is unavailable ... $ nmcli device status DEVICE TYPE STATE CONNECTION end0 ethernet connected Wired connection 1 lo loopback connected (externally) lo wlan0 wifi unavailable --

Description Moving use of dbeinder's repo to fifteenhex repo for xradio driver as fifteenhex seems to give more consistent speeds. This also allows us to drop all of our xradio patches as we can now build right from fifteenhex code. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Test wifi on Orange Pi Zero Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Bumped legacy, current and edge kernel. Legacy - 5.15.127 -> 5.15.130 Current - 6.1.47 -> 6.1.51 Edge - 6.5 -> 6.5.1 Fixed compilation of xradio and as its working fine, disabled cw1200 driver that I added for edge last week. Refreshed kernel configs. Also uwe5622 patches needed for orange pi 3 lts were not being applied as least kernel version was set to 6.0. Moved it back to 5.15. Not sure if it works though will test next week once I receive my orangepi 3 lts. Also for edge kernel, enabled rtw88 based drivers and disabled their corresponding legacy counterparts. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Tested all images on NanoPi Duo2 (sun8i H3) [X] Tested all images on Orange Pi Prime (sun50i H5) [X] Tested xradio drivers on Orange Pi Zero Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Enabling wireless driver found on many Orange Pi boards. Jira reference number AR-1486 How Has This Been Tested? [ ] Test wireless connection Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description The current xradio patch causes the wifi mac address to randomize after every reboot on kernel 5.13+ Modified it to use the updated of_get_mac_address function on kernel 5.13+ and get a stable mac address How Has This Been Tested? Tested patch with 5.15.85 kernel on 3 aw-h6-tv boards. The wifi mac address is now stable/unique and not randomized after every reboot Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [X] Any dependent changes have been merged and published in downstream modules View the full article

Description switched to most recent upstream source fixed wrong header location For 5.19.y and up there is a lot more work, so this will wait for someone else. Jira reference number AR-1316 How Has This Been Tested? [x] Build sunxi and sunxi64 CURRENT Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

BTW I am working on migrating armbian to 6.7 kernel - https://github.com/armbian/build/pull/6079 Feel free to test and comeback. currently it fails compilation for xradio and some realtek wifi drivers that I will fix today. It can be compiled when building with EXTRAWIFI=no, but that will skip compiling uwe5622 driver. Edit: Compilation issue is now fixed.

Description Bump Allwinner kernels Legacy - 5.15.x -> 6.1.x Current - 6.1.x -> 6.6.x Edge - 6.6.x -> 6.7-rc6 Removed old leftover kernel patch directories. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ ] Edge kernel builds with EXTRAWIFI=no. Some driver harness drivers including xradio, rtl8189es, rtl8189fs, rtl8812au, rtl8192eu and possibly others needs some fixes as compilation fails for the same. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Hello -- bringing in conversation from https://github.com/armbian/build/pull/5726#issuecomment-1817668480 as requested. @viraniac -- I've attached the dmesg output from a fresh flash of the quadra SD image -- which is just armbian checked out at `90c05ba` with this patch applied: https://www.inovato.net/build/quadra.patch . Build instructions from the founder are at https://forum.inovato.com/post/building-armbian-from-source-12449428?pid=1333459893 Curiously the dmesg output almost looks truncated to me -- doesn't start with `Booting Linux on physical`, and I see a few xradio message but no results for 819. I've rebooted and get similar output with `journalctl -b -k`, so I guess this is the full output? Let me know if further info would be helpful, and thank you again for your time and attention. quadra-working-wifi.txt EDIT: The inovato founder says they are not intentionally limiting the dmesg output: https://forum.inovato.com/post/dmesg-output-truncated-missing-beginning-12780349?pid=1336369022

Nice to hear edge worked for you. Apart from the fifteenhex repository used by Inovato, I have also found another Xradio XR819 driver which looks kind of cleaner but also need some work as its tightly coupled to some sunxi bsp drivers. I am going to try bringing that up as well. But it will take some time as there are other boards to support and there is not a lot of interest around xradio anymore.

Its weird that xradio is working for orangepi zero but is not working for Quadra. Waiting for @Tenkawa, to test and comeback on the same.

@SteeManThere is some background context of why he posted here. He is having problem with inovato quadra support in our build framework that I added a couple of months back. I asked him to check once on inovato's official image as I wanted to make sure that the onboard wifi is xradio one as I read somewhere that some Tanix TX6 boxes have different onboard wifi. As Quadra is said to be a rebranded TX6, I wanted to confirm the same. Sorry for causing the confusion

@n8henrieWhat was the kernel used in inovato image? If I remember it correctly, they also have a 5.15 and 6.1 version. Can you check their 6.1 version? See if the wifi works there or do you get same error there as well BTW, I have asked the @Tenkawa to test xradio again on inovato quadra. I personally don't have the box. I live in India and can't get the same so all of the testing was done by Tenkawa. He does say that he get better performance on edge kernel. So try creating an image from edge branch as well and give it a try. That image will have 6.6 kernel

If somebody has a chance to test new firmware blob for XR819 feedback would be appreciated Simply grab the code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } fw_xr819.bin from the PR below, replace your current one and reboot. Check if Wi-Fi still works as expected or ideally even better. The file is located here: code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } /usr/lib/firmware/xr819/ https://github.com/armbian/firmware/commit/aff348fa9eef0fcc97d4f2bb7304f0862baffc20 If in doubt create a backup of your current firmware bin.

Hi all, I have a few orange pi zero's and recently on 2 I had an issue with wifi AP that I am trying to properly understand. I have read some of the discussion regarding the wifi chip on the opi0 and that's not a great chip. I thoroughly agree with people that say that if you pay bottom dollar for a board, don't expect top dollar performance. And especially don't come complaining on a public FOSS forum. The only thing I am trying to do is understand the error and see if there is anything I can do to improve it. I use my orange pi zero's with a basic (custom) armbian image that starts up with a wifi AP briefly, so I can ssh in and do some config. Afterwards I reboot it and either turn wifi off altogether, or just connect as a wifi client using wpa_supplicant/ `/etc/network/interfaces.d`. So no heavy wifi AP usage. This has been working fine so far, but with 2 recent boards I couldn't connect to the wifi, and upon inspection of the logs, it showed these errors: [ 21.667120] random: crng init done [ 21.667157] random: 7 urandom warning(s) missed due to ratelimiting [ 21.692073] xradio AP-WRN: ap restarting! [ 21.731438] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 33.782692] vcc3v0: disabling [ 33.782721] vcc5v0: disabling [ 56.852083] xradio TXRX-WRN: received frame has no key status [ 56.852107] xradio TXRX-WRN: dropped received frame [ 56.852208] xradio TXRX-WRN: received frame has no key status [ 56.852218] xradio TXRX-WRN: dropped received frame [ 56.855392] xradio TXRX-WRN: received frame has no key status [ 56.855413] xradio TXRX-WRN: dropped received frame [ 56.861510] xradio TXRX-WRN: ***skb_queue_tail [ 56.973724] xradio TXRX-WRN: ***skb_queue_tail [ 57.028068] xradio TXRX-WRN: ***skb_queue_tail [ 57.040336] xradio TXRX-WRN: ***skb_queue_tail [ 57.042775] xradio TXRX-WRN: received frame has no key status [ 57.042789] xradio TXRX-WRN: dropped received frame [ 57.198022] xradio TXRX-WRN: ***skb_queue_tail [ 57.198644] xradio TXRX-WRN: received frame has no key status [ 57.198669] xradio TXRX-WRN: dropped received frame [ 57.198740] xradio TXRX-WRN: received frame has no key status [ 57.198752] xradio TXRX-WRN: dropped received frame [ 57.199236] xradio TXRX-WRN: received frame has no key status [ 57.199249] xradio TXRX-WRN: dropped received frame [ 57.199662] xradio TXRX-WRN: received frame has no key status [ 57.199672] xradio TXRX-WRN: dropped received frame [ 57.273269] xradio TXRX-WRN: ***skb_queue_tail [ 57.398636] xradio TXRX-WRN: ***skb_queue_tail Can anybody explain what these errors actually mean? Is this indicative of an actual hardware error on the board? Or could it be caused by something else? I did update my base image recently (using the same `customize_image.sh`), or could it be something locally on my wifi that can cause these errors? ---- EDIT ---- After diving into the driver source (well, at least one of the versions), I found this piece of code that seems to trigger the message: void xradio_rx_cb(struct xradio_vif *priv, struct wsm_rx *arg, struct sk_buff **skb_p) { . . . . . . . if (unlikely(early_data)) { spin_lock_bh(&priv->ps_state_lock); /* Double-check status with lock held */ if (entry->status == XRADIO_LINK_SOFT) { skb_queue_tail(&entry->rx_queue, skb); dev_warn(priv->hw_priv->pdev, "***skb_queue_tail\n"); } else ieee80211_rx_irqsafe(priv->hw, skb); spin_unlock_bh(&priv->ps_state_lock); } else { ieee80211_rx_irqsafe(priv->hw, skb); } *skb_p = NULL; I am not very familiar with the linux networking drivers/stack, but from what I understand, a wifi frame comes in over a socket, causing the rx callback to be called, which does a bunch of stuff, ending with checking some status (on the wifi chip? or on the frame?) concludes that the status is XRADIO_LINK_SOFT, which I guess means it isn't able to do something, and queues the frame back on the receive socket buffer/queue (and warns about it)? So does anyone know what that status means? And if there is anything that could cause it? Cheers, Dolf.

Well, this blog post convinced me that upgrading from bullseye to bookworm didn't have to be nearly as complex as the official Debian documentation made it out to be, so I followed those instructions and completed without error. Initially, I neglected to edit /etc/apt/sources.list.d/armbian.list before executing full-upgrade, but it seems to have worked as a two-step full-upgrade. Welcome to Armbian 23.8.3 Bookworm with Linux 6.1.53-current-sunxi and xradio wifi is working 😀

Now that xradio has been enabled on kernel 6.x, I'm ready to upgrade my Orange Pi Zero that I've been keeping on 23.02 with kernel 5.x. With armbian-config I've unfrozen kernel/firmware updates and after apt upgrade and reboot I am on kernel 6.1.53 and wifi is working! But boot message says I'm still on 23.02, and apt says that armbian-bsp-cli-orangepizero is being kept back. Now trying: $ sudo apt install armbian-bsp-cli-orangepizero [...] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: armbian-bsp-cli-orangepizero-current : Depends: base-files (>= 23.8.3) but 23.8.1-bullseye is to be installed E: Unable to correct problems, you have held broken packages. Do I just need to wait for something to be updated in the repositories so that armbian-bsp-cli-orangepizero will be made available, or have I messed up something on my system that I need to fix?

I have the same issue on the OPi Zero 3. I used the Armbian image in the leeboy/armbian repository and followed the instructions on updating the dtb and bin file for the 4gig variant and it works. however WIFI does not and I can't connect at all. I see that there was an issue that was fixed earlier this week regarding the Orange Pi Wifi drivers and xradio not working. I think if someone was to pull the latest armbian and build the kernel it might work (I'm very new to all this, otherwise I would!).

Great news that the xradio fix has been released 😀! Based on this news I have used armbian-config to unfreeze kernel/firmware updates on my 23.02 installation. After apt upgrade and reboot I am on kernel 6.1.53 and wifi is working. But boot message says I'm still on 23.02, and apt says that armbian-bsp-cli-orangepizero is being held back. sudo apt install armbian-bsp-cli-orangepizero Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: armbian-bsp-cli-orangepizero-current : Depends: base-files (>= 23.8.3) but 23.8.1-bullseye is to be installed E: Unable to correct problems, you have held broken packages.

That was an early attempt to enable xradio in edge kernel. But that actually didn't worked out. The working fix is here - https://github.com/armbian/build/commit/46e756540eb01cbefb31cad744e04afc4282e0e0

Description This brings early support for Linux kernel v6.5 for allwinner boards. Following patches are changed Megous patches: disabled patches.megous/video-fbdev-eInk-display-driver-for-A13-based-PocketBooks.patch to prevent build failure. Will work on re-enabling the same Fixes patches: disabled Fix-depends-only-ARM-eInk-display-FB.patch as it changes code introduce by patch disabled above Armbian patches: disabled drv-clk-sunxi-ng-ccu-sun50i-a64-revert-ccu-Pinebook-A64.patch due to patch application failure. Will check if its still needed. Need help from someone who has a PInebook A64 for the same. removed drv-pmic-add-axp313a.patch as it is upstreamed reworked the overlay support patches to reuse the upstream dtbo support. Due to this rework, overlay patches are updated to use dtso as the file extension Config change: Enabled CW1200 wireless driver as this might bring support for xradio xr819 due to patches from megous kernel How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Build succeeds Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

I am trying to figure out how to compile and load the Xradio drivers onto an orange pi zero LTS. I am having some troubles with the xradio drivers that came with my image and am hoping that https://github.com/fifteenhex/xradio will add some improvements. There does seem to be some code change so I am remaining optimistic. I am able to compile the drivers with the kernel from https://github.com/orangepi-xunlong/orangepi-build but it crashes network manager and a few other modules when I try to modprobe it, I am guessing it is because this kernel is not an armbian kernel. I am trying to get the kernel https://github.com/armbian/build to work, but it doesn't look like that's what I need to do. I am lost as to how to get this compiled and any help would be appreciated.

Actually I want to change course, as many people have said this is a waste of time to attempt to fix the drivers. So I am experiencing issues with this driver that mainly drops the device off the network. When this happens I find a dmesg saying the device issued a deauth, and a xradio dmesg saying it is issuing a deauth. But what catches my attention more is the red text saying xradio WSM-ERR: wsm_generic_confirm failed for request 0x0010. and another message I get but this one is spammed on the dmesg is xradio WRN: BH: missed 1848 consecutive interrupts! Which is an error message. Honestly, the true reason I wanted to compile drivers was to debug what was causing these to happen on my devices. These are just a list of all the dmesg entries I have seen. Some of these I have not seen anywhere else while searching the internet. xradio WSM-ERR: wsm_generic_confirm failed for request 0x0010. xradio WRN: BH: missed 1848 consecutive interrupts! xradio TXRX-WRN: received frame has no key status xradio WSM-WRN: Issue unjoin command(TX). xradio STA-ERR: [CQM] if0 Reporting connection loss.

Looking at the code, the only improvements is that it will (probably) compile and work on K6.0+, while quality will remain the same. Search on this forum for more topic associated with xradio, xr819, wireless on zero ... to understand how much time was already wasted for nothing. If you are not an expert in wireless networking that you will dig deep into the this chip in particular ... rather do something else. Perhaps extend driver we use https://github.com/armbian/build/blob/main/lib/functions/compilation/patch/drivers_network.sh#L229 to be compatible with K6.0+ https://armbian.atlassian.net/browse/AR-1486 which is adding few last commits from fifteenhex repo. Most of those drivers, and especially those that were delivered immature, are maintained with minimum effort. Nobody has months of time, knowledge and equipment to fix everything what is wrong ... (Sorry for being honest) It should work on Armbian for Armbian. Orangepi is using some very old variant of this build system and hasn't been updated since. tl;dr; Armbian is much better then what HW vendors are able to deliver.

My OrangePi Zero is on 23.02 and I intend to stay with it (unless/until xradio wifi works on kernel 6.x). Just ran apt update and it shows these available packages: armbian-config/bullseye,bullseye 23.08.0-trunk--1-SA9048-Baeda all [upgradable from: 23.02.2] armbian-firmware/bullseye,bullseye 23.08.0-trunk--1-SA1251-B226d all [upgradable from: 23.02.2] armbian-zsh/bullseye,bullseye 23.08.0-trunk--1-SAbfee-Baf88 all [upgradable from: 23.02.2] I'm surprised to see anything related to 23.08 seeing as that version hasn't been released yet, so obviously I don't really understand what it means to be seeing this. Should I go ahead and install these even though I don't intend to upgrade to 23.08? Maybe this should be in the "beginners" area; mods please feel free to move if appropriate.