• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Orange Pi Zero virtual wireless devices not working
1 1

11 posts in this topic

Recommended Posts

I've read many posts here and understand the OPi0 wireless chip isn't very well liked. I'm trying to setup hostapd with both client and AP functionality. I can get AP working only if I dedicate wlan0 to it. It seems that virtual devices (eg iw dev wlan0 interface add uap0 type managed; ip link set uap0 up) don't work with the current jessie image, making it impossible to have both AP and client simultaneously.

 

I'm happy to help with testing the driver, but I'm no expert and certainly not knowledgeable enough to code this sort of stuff. If there's any help to be had, I'd be grateful.

Share this post


Link to post
Share on other sites
4 hours ago, chowderhead said:

 

I've read many posts here and understand the OPi0 wireless chip isn't very well liked.

 


Opi Zero is not suitable for such complex setup. Even you manage to patch the driver (for which you need advanced knowledge) and get all this working, performance would be terrible.
 

Consider attaching some proven USB wireless chip or get Opi Zero 2 H3, which have at least a decent wireless chip and where this might be possible to achieve.

Share this post


Link to post
Share on other sites
On 5/29/2017 at 0:53 AM, Igor said:

Opi Zero is not suitable for such complex setup. Even you manage to patch the driver (for which you need advanced knowledge) and get all this working, performance would be terrible.
 

Consider attaching some proven USB wireless chip or get Opi Zero 2 H3, which have at least a decent wireless chip and where this might be possible to achieve.

 

Thanks for the reply, Igor. I would like to challenge your assertion since I presently have a Raspberry Pi Zero Wireless performing this function quite handily; for my purposes, anyway. The OPi0 is more useful given a quad core processor and more io, hence my interest in it. I'll take a look at the H3 version, however.

Share this post


Link to post
Share on other sites
1 minute ago, chowderhead said:

I would like to challenge your assertion since I presently have a Raspberry Pi Zero Wireless performing this function quite handily;

It's not about the board or SoC (processor), it's about the wireless module and its software (driver and firmware) quality.

Share this post


Link to post
Share on other sites

I would also like to get the wireless of the Orange Pi Zero working fully.  Limited bandwidth is not a problem for my use case.  I'm a competent programmer, but normally try to stay away from kernel code.  If this isn't too much work, I'm willing to make an exception.  To know that, and also to get started, I need to know what needs to be done though.  My observations so far:

  1. When the xradio module is loaded, the load average is at least 1.0.  It seems to be busy waiting whenever it's not doing anything useful.  Unloading the module makes the system load reasonable (near 0).
  2. The wifi interface works, but when creating other virtual interfaces (iw dev wlan0 interface add), they show up as if they're working, but no communication is possible with them (they also don't find any networks when scanning).

Please let me know where I should start if I want to fix things, so I can see if it's worth my time.

 

Thanks!

Share this post


Link to post
Share on other sites

So I followed the advise given and purchased an Orange Pi Zero Plus2 H3. No luck. Steps followed:

 

Removed network-manager (doesn't work with hostapd so I don't need it).

 

Permit ipv4 forwarding by uncommenting  net.ipv4.ip_forward=1 in /etc/sysctl.conf.

 

Setup dnsmasq to serve dhcp over wlan0_ap and ignore wlan0.

 

Create virtual device wlan0_ap:

iw dev wlan0 interface add wlan0_ap type managed

 

/etc/network/interfaces:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
        wpa-essid "myssid"
        wpa-psk "mypassphrase"


auto wlan0_ap
iface wlan0_ap inet static
        address 192.168.76.1
        netmask 255.255.255.0  

 

/etc/hostapd/hostapd.conf:

interface=wlan0_ap
ssid=opi0plus2
hw_mode=g
channel=4
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=0123456789
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP

Setup iptables:

iptables -t nat -A POSTROUTING -s 192.168.76.0/24 ! -d 192.168.76.0/24 -j MASQUERADE

Set wlan0_ap up:

ip link set dev wlan0_ap up
ifup wlan0_ap

 

Restart dnsmasq:

service dnsmasq restart

Start hostapd:

hostapd /etc/hostapd/hostapd.conf 
Configuration file: /etc/hostapd/hostapd.conf
nl80211: Could not re-add multicast membership for vendor events: -2 (No such file or directory)
Using interface wlan0_ap with hwaddr 02:00:00:00:00:00 and ssid "opi0plus2"
wlan0_ap: interface state UNINITIALIZED->ENABLED
wlan0_ap: AP-ENABLED 

hostapd seems happy, but there is no opi0plus2 ssid in a scan of the local wireless networks.

 

I've tried the supplied interfaces.hostapd and /etc/hostapd.conf from Armbian, they don't work either.

 

Any help?

 

Oh, and Wijnen offered to work on the POS wireless drive, but radio silence from the Armbian crew. What's up with that?

Share this post


Link to post
Share on other sites

If you get such configuration working on RPi with very similar chip, than one way is to try with mainline kernel, even still development version - build one or try the ones from download section. This way become more but not exactly comparable ... It can be also firmware related and I would double check small print / documentation / ask Broadcomm, do detail compare of both chips.


This is wireless networking, which is yet another big area of expertise and pressing on volunteers to help is a bit out. We already save you a lot of work, but Armbian crew (few people) can not fix all generic Linux problems that emerges. 

 

Edit: if you are using old kernel (legacy 3.4.113) this module must be loaded with op_mode=2 to provide AP mode - only this way you will see AP. I have no idea if you still can run in client mode at the same time ...

Share this post


Link to post
Share on other sites
5 hours ago, chowderhead said:

Oh, and Wijnen offered to work on the POS wireless drive, but radio silence from the Armbian crew. What's up with that?

 

9 minutes ago, chowderhead said:

Wijnen is offering to help, but nobody responded to his request, so you're missing an opportunity

 

We are not missing anything since we don't manufacture or sell any boards, and vendors who are interested in their hardware usually provide documentation and financial support to people who are willing to improve their software.

Orange Pi Zero wireless limitations and problems were already discussed several times in other threads, so I don't see any points in discussing the situation yet another time.

Share this post


Link to post
Share on other sites
On 7/1/2017 at 7:51 PM, zador.blood.stained said:

Orange Pi Zero wireless limitations and problems were already discussed several times in other threads, so I don't see any points in discussing the situation yet another time.

 

I'm sorry for not making myself clear then.  I'm not asking for a discussion.  I'm asking for some pointers so I can see if it's worth my time to try to fix things.  Pointers to other forum threads are fine.  I didn't find anything of use myself, which is why I'm asking for pointers.

 

Thanks,

Bas

Share this post


Link to post
Share on other sites
33 minutes ago, wijnen said:

I'm sorry for not making myself clear then.  I'm not asking for a discussion.  I'm asking for some pointers so I can see if it's worth my time to try to fix things.  Pointers to other forum threads are fine.  I didn't find anything of use myself, which is why I'm asking for pointers.

Repository README: https://github.com/fifteenhex/xradio/blob/master/README.md

Discussion: https://forum.armbian.com/index.php?/topic/3243-orange-pi-zero-wireless-module-status-xradio-st-cw1200/

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

1 1

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.