0
SaiHou

Linux orangepipc 4.14.18-sunxi #24 - D-Link DWA-131 E1

Recommended Posts

I am trying to install my newly bought D-Link DWA-131 E1 on my Orange Pi PC with theLinux orangepipc 4.14.18-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l GNU/Linux. 

 

I googled from the internet and there are so many guides which will not work for me.

 

I almost messed up my OS and the installation still failed. I already re-flash the microSD card with a new "Linux orangepipc 4.14.18-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l GNU/Linux".

 

I am here looking for help if some one experts here can guide me through out the installation.

 

I really appreciated for your help and thank you in advance.

 

Best regards,

SaiHou

 

 

 

 

Share this post


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

I googled from the internet and there are so many guides which will not work for me.


Try this way - starting with a fresh image:

 

armbian-config


1. Switch to beta repository, update

2. Install headers

 

Then proceed with drive compilation this way:
https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-build-a-wireless-driver (you can skip the part for kernel headers install since you did that from armbian-config)

 

Also, provide logs from armbianmonitor -u ... it might give us some clues why it's not working.

Share this post


Link to post
Share on other sites
9 hours ago, Igor said:


Try this way - starting with a fresh image:

 

armbian-config


1. Switch to beta repository, update

2. Install headers

 

Then proceed with drive compilation this way:
https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-build-a-wireless-driver (you can skip the part for kernel headers install since you did that from armbian-config)

 

Also, provide logs from armbianmonitor -u ... it might give us some clues why it's not working.

 

Hi,

 

Thank you for the quick response.

 

I have just switch to nightly build, and trying to install the headers but can't make it.

root@orangepipc:~# sudo apt-get install linux-headers-$(uname -r)
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-headers-4.14.14-sunxi
E: Couldn't find any package by glob 'linux-headers-4.14.14-sunxi'
E: Couldn't find any package by regex 'linux-headers-4.14.14-sunxi'
root@orangepipc:~#
root@orangepipc:~# aptitude install linux-headers-4.14.14-sunxi
Couldn't find any package whose name or description matched "linux-headers-4.14.14-sunxi"
Unable to apply some actions, aborting
root@orangepipc:~#
root@orangepipc:~# armbianmonitor -u
System diagnosis information will now be uploaded to http://ix.io/1bIP
Please post the URL in the forum where you've been asked for.

This is what I get. Thank you.

Share this post


Link to post
Share on other sites
8 minutes ago, SaiHou said:

I have just switch to nightly build, and trying to install the headers but can't make it.


Follow my advice. Install headers within armbian-config

 

sudo apt-get install linux-headers-$(uname -r)

This is the wrong way of installing headers.

Share this post


Link to post
Share on other sites
Just now, Igor said:


Follow my advice.

 


sudo apt-get install linux-headers-$(uname -r)

This is the wrong way of installing headers.

Hello Igor,

 

Thank you for the advise.

 

I am now trying the advance features.

 

Regards.

SaiHou

Share this post


Link to post
Share on other sites
9 hours ago, Igor said:


Try this way - starting with a fresh image:

 

armbian-config


1. Switch to beta repository, update

2. Install headers

 

Then proceed with drive compilation this way:
https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-build-a-wireless-driver (you can skip the part for kernel headers install since you did that from armbian-config)

 

Also, provide logs from armbianmonitor -u ... it might give us some clues why it's not working.

Hi Igor,

 

This is what I get:-

 

root@orangepipc:~# dir
root@orangepipc:~# cd
root@orangepipc:~# git clone https://github.com/pvaret/rtl8192cu-fixes.git
Cloning into 'rtl8192cu-fixes'...
remote: Counting objects: 637, done.
remote: Total 637 (delta 0), reused 0 (delta 0), pack-reused 637
Receiving objects: 100% (637/637), 1.94 MiB | 669.00 KiB/s, done.
Resolving deltas: 100% (358/358), done.
root@orangepipc:~# cd rtl8192cu-fixes
root@orangepipc:~/rtl8192cu-fixes# make ARCH=arm
make ARCH=arm CROSS_COMPILE= -C /lib/modules/4.14.44-sunxi/build M=/root/rtl8192cu-fixes  modules
make[1]: Entering directory '/usr/src/linux-headers-4.14.44-sunxi'
  CC [M]  /root/rtl8192cu-fixes/core/rtw_cmd.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_security.o
/root/rtl8192cu-fixes/core/rtw_security.c: In function ‘aes_cipher’:
/root/rtl8192cu-fixes/core/rtw_security.c:1504:5: warning: this ‘for’ clause does not guard... [-Wmisleading-indentation]
     for (j = 0; j < 8; j++)
     ^~~
/root/rtl8192cu-fixes/core/rtw_security.c:1507:2: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the ‘for’
  payload_index = hdrlen + 8;
  ^~~~~~~~~~~~~
/root/rtl8192cu-fixes/core/rtw_security.c: In function ‘aes_decipher’:
/root/rtl8192cu-fixes/core/rtw_security.c:1878:5: warning: this ‘for’ clause does not guard... [-Wmisleading-indentation]
     for (j = 0; j < 8; j++)
     ^~~
/root/rtl8192cu-fixes/core/rtw_security.c:1881:2: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the ‘for’
  payload_index = hdrlen + 8;
  ^~~~~~~~~~~~~
  CC [M]  /root/rtl8192cu-fixes/core/rtw_debug.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_io.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_ioctl_query.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_ioctl_set.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_ieee80211.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_mlme.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_mlme_ext.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_wlan_util.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_pwrctrl.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_rf.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_recv.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_sta_mgt.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_ap.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_xmit.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_p2p.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_tdls.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_br_ext.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_iol.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_sreset.o
  CC [M]  /root/rtl8192cu-fixes/core/efuse/rtw_efuse.o
  CC [M]  /root/rtl8192cu-fixes/hal/hal_intf.o
  CC [M]  /root/rtl8192cu-fixes/hal/hal_com.o
  CC [M]  /root/rtl8192cu-fixes/hal/dm.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_hal_init.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_phycfg.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_rf6052.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_dm.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_rxdesc.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_cmd.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/usb_halinit.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/rtl8192cu_led.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/rtl8192cu_xmit.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/rtl8192cu_recv.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/usb_ops_linux.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_sreset.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_xmit.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/Hal8192CUHWImg.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/osdep_service.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/os_intfs.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/usb_intf.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/usb_ops_linux.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/ioctl_linux.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/xmit_linux.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/mlme_linux.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/recv_linux.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/ioctl_cfg80211.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/rtw_android.o
  LD [M]  /root/rtl8192cu-fixes/8192cu.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /root/rtl8192cu-fixes/8192cu.mod.o
  LD [M]  /root/rtl8192cu-fixes/8192cu.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.14.44-sunxi'
root@orangepipc:~/rtl8192cu-fixes# insmod 8192cu.ko
root@orangepipc:~/rtl8192cu-fixes# usbcore: registered new interface driver rtl8192cu
Could not find the database of available applications, run update-command-not-found as root to fix this
usbcore:: command not found
root@orangepipc:~/rtl8192cu-fixes# cd ..
root@orangepipc:~# iwconfig wlan0
wlan0     No such device
root@orangepipc:~# iwconfig
wlx180f76038d53  IEEE 802.11  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off

enx000ec6dec8be  no wireless extensions.

eth0      no wireless extensions.

lo        no wireless extensions.



wlx180f76038d53  IEEE 802.11  ESSID:"MOTOROLA AP"
          Mode:Managed  Frequency:2.462 GHz  Access Point: E0:B9:E5:DF:8D:C3
          Bit Rate=1 Mb/s   Tx-Power=20 dBm
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=26/70  Signal level=-84 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

The signal strength is very low and the connection speed is unacceptable. If I plugged into Windows PC, the signal strength is 5/5 and signal quality is 100%.

 

But in Armbian, seems ...

 

Any solution?

 

Regards,

SaiHou

Share this post


Link to post
Share on other sites
10 minutes ago, SaiHou said:

Hi Igor,

 

This is what I get:-

 


root@orangepipc:~# dir
root@orangepipc:~# cd
root@orangepipc:~# git clone https://github.com/pvaret/rtl8192cu-fixes.git
Cloning into 'rtl8192cu-fixes'...
remote: Counting objects: 637, done.
remote: Total 637 (delta 0), reused 0 (delta 0), pack-reused 637
Receiving objects: 100% (637/637), 1.94 MiB | 669.00 KiB/s, done.
Resolving deltas: 100% (358/358), done.
root@orangepipc:~# cd rtl8192cu-fixes
root@orangepipc:~/rtl8192cu-fixes# make ARCH=arm
make ARCH=arm CROSS_COMPILE= -C /lib/modules/4.14.44-sunxi/build M=/root/rtl8192cu-fixes  modules
make[1]: Entering directory '/usr/src/linux-headers-4.14.44-sunxi'
  CC [M]  /root/rtl8192cu-fixes/core/rtw_cmd.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_security.o
/root/rtl8192cu-fixes/core/rtw_security.c: In function aes_cipher’:
/root/rtl8192cu-fixes/core/rtw_security.c:1504:5: warning: this for clause does not guard... [-Wmisleading-indentation]
     for (j = 0; j < 8; j++)
     ^~~
/root/rtl8192cu-fixes/core/rtw_security.c:1507:2: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the for
  payload_index = hdrlen + 8;
  ^~~~~~~~~~~~~
/root/rtl8192cu-fixes/core/rtw_security.c: In function aes_decipher’:
/root/rtl8192cu-fixes/core/rtw_security.c:1878:5: warning: this for clause does not guard... [-Wmisleading-indentation]
     for (j = 0; j < 8; j++)
     ^~~
/root/rtl8192cu-fixes/core/rtw_security.c:1881:2: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the for
  payload_index = hdrlen + 8;
  ^~~~~~~~~~~~~
  CC [M]  /root/rtl8192cu-fixes/core/rtw_debug.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_io.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_ioctl_query.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_ioctl_set.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_ieee80211.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_mlme.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_mlme_ext.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_wlan_util.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_pwrctrl.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_rf.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_recv.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_sta_mgt.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_ap.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_xmit.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_p2p.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_tdls.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_br_ext.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_iol.o
  CC [M]  /root/rtl8192cu-fixes/core/rtw_sreset.o
  CC [M]  /root/rtl8192cu-fixes/core/efuse/rtw_efuse.o
  CC [M]  /root/rtl8192cu-fixes/hal/hal_intf.o
  CC [M]  /root/rtl8192cu-fixes/hal/hal_com.o
  CC [M]  /root/rtl8192cu-fixes/hal/dm.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_hal_init.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_phycfg.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_rf6052.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_dm.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_rxdesc.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_cmd.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/usb_halinit.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/rtl8192cu_led.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/rtl8192cu_xmit.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/rtl8192cu_recv.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/usb_ops_linux.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_sreset.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/rtl8192c_xmit.o
  CC [M]  /root/rtl8192cu-fixes/hal/rtl8192c/usb/Hal8192CUHWImg.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/osdep_service.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/os_intfs.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/usb_intf.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/usb_ops_linux.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/ioctl_linux.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/xmit_linux.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/mlme_linux.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/recv_linux.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/ioctl_cfg80211.o
  CC [M]  /root/rtl8192cu-fixes/os_dep/linux/rtw_android.o
  LD [M]  /root/rtl8192cu-fixes/8192cu.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /root/rtl8192cu-fixes/8192cu.mod.o
  LD [M]  /root/rtl8192cu-fixes/8192cu.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.14.44-sunxi'
root@orangepipc:~/rtl8192cu-fixes# insmod 8192cu.ko
root@orangepipc:~/rtl8192cu-fixes# usbcore: registered new interface driver rtl8192cu
Could not find the database of available applications, run update-command-not-found as root to fix this
usbcore:: command not found
root@orangepipc:~/rtl8192cu-fixes# cd ..
root@orangepipc:~# iwconfig wlan0
wlan0     No such device
root@orangepipc:~# iwconfig
wlx180f76038d53  IEEE 802.11  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off

enx000ec6dec8be  no wireless extensions.

eth0      no wireless extensions.

lo        no wireless extensions.



wlx180f76038d53  IEEE 802.11  ESSID:"MOTOROLA AP"
          Mode:Managed  Frequency:2.462 GHz  Access Point: E0:B9:E5:DF:8D:C3
          Bit Rate=1 Mb/s   Tx-Power=20 dBm
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=26/70  Signal level=-84 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

The signal strength is very low and the connection speed is unacceptable. If I plugged into Windows PC, the signal strength is 5/5 and signal quality is 100%.

 

But in Armbian, seems ...

 

Any solution?

 

Regards,

SaiHou

Hi Igor,

 

FYI, after I reboot, the wlan is not connected / activated (view in nmtui), but when check with iwconfig, the wlan is as follow:-

 

wlx180f76038d53  IEEE 802.11  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off

Seems the same issue as before.

 

Anyway, thank you for the reply and advise.

Share this post


Link to post
Share on other sites

 

10 minutes ago, SaiHou said:

The signal strength is very low and the connection speed is unacceptable. If I plugged into Windows PC, the signal strength is 5/5 and signal quality is 100%.

 

But in Armbian, seems ...


Driver quality is certainly not the problem of Armbian. Our supports ends with the possibility to compile the driver. We don't support 3rd party hardware and we are not Microsoft corporation with tens of thousands people but only a few amateurs. If driver sources are bad, there is nothing we can do about. Try another, different one, talk to chip maker, ...

Share this post


Link to post
Share on other sites
11 minutes ago, SaiHou said:

FYI, after I reboot, the wlan is still connected (view in nmtui), but when check with iwconfig, the wlan is as follow:-


You need to add module to the kernel or load it before network goes up ...

Share this post


Link to post
Share on other sites
9 hours ago, Igor said:


You need to add module to the kernel or load it before network goes up ...

Hi Igor,

 

Thanks for the reply. I can't make it work and I just unplugged the USB wifi dongle and the forget about using unsupported "USB hardware" and "hardware drivers".

 

I decide to change to Raspberry Pi 3B(+) board which with good reputation hardware & drivers when compared to unsupported "hardware & hardware drivers".

 

Best regards,

SaiHou

Share this post


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

I decide to change to Raspberry Pi 3B(+) board which with good reputation hardware & drivers when compared to unsupported "hardware & hardware drivers".


Wrong. It is Linux versus Windows. If dongle works well on Rpi it usually works well on other Linux devices, especially in a situation, we have here - modern kernel. If dongle has good support in official Rpi "Linux kernel" then it can be easily ported to official Linux kernel (www.kernel.org), where our sources mostly come from. 

If you can't live with this, you need to switch back to Windows or buy what is recommended. But even then you might have troubles.

Share this post


Link to post
Share on other sites
6 hours ago, Igor said:


Wrong. It is Linux versus Windows. If dongle works well on Rpi it usually works well on other Linux devices, especially in a situation, we have here - modern kernel. If dongle has good support in official Rpi "Linux kernel" then it can be easily ported to official Linux kernel (www.kernel.org), where our sources mostly come from. 

If you can't live with this, you need to switch back to Windows or buy what is recommended. But even then you might have troubles.

I may be wrong. But for sure Raspberry Pi has built-in Wifi and Bluetooth with Raspbian installed, no need to guess which dongle is compatible or not compatible to be used...

 

For other Single Board Computers, their built-in wifi is not as good as Raspberry Pi with the price of US$35++. No need to mention those enpensive SBC which more than US$100-US$200.

 

To me, I only need a simple SBC for my LiveATC / ADSB with wifi support. I have few Rpi 3B for my ADSB and I am trying a low cost SBC which without wifi and I have the D-Link DWA-131 in hand and try to make it work... Unfortunately....

 

Igor, thanks for the previous instruction / reply. At least I learned something but may be I am smart enough to make it work.

 

Best regards,

SaiHou

Share this post


Link to post
Share on other sites
28 minutes ago, SaiHou said:

built-in Wifi


We support wireless adaptors which are on boards, we just don't support 3rd party hardware. That is mission impossible. With exception of OrangePi Zero / Nanopi Duo, which has some bad wifi chip, all works fine.

 

29 minutes ago, SaiHou said:

no need to guess which dongle is compatible or not compatible to be used...


You need to look for some "Linux compatibility lists" and/or buy what is supported. Rpi is popular but that doesn't mean it has an advantage in this area. I have a lot of wireless adaptors for testings and to try to make them work ... Some work fine on Linux, some don't.

Share this post


Link to post
Share on other sites
3 minutes ago, Igor said:


We support wireless adaptors which are on boards, we just don't support 3rd party hardware. That is mission impossible. With exception of OrangePi Zero / Nanopi Duo, which has some bad wifi chip, all works fine.

 


 You need to look for some "Linux compatibility lists" and/or buy what is supported. Rpi is popular but that doesn't mean it has an advantage in this area. I have a lot of wireless adaptors for testings and to try to make them work ... Some work fine on Linux, some don't.

Hi Igor,

 

I got what you mean.

 

Yeah, I saw many forums and feedbacks for the OrangePi Zero, NanoPi Duo etc with BAD Wifi connection.

 

Best regards.

Share this post


Link to post
Share on other sites
0