Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
WiFi Realtek usb
#1
Does the board support any Wifi via USB yet? 

I cannot get my Edimax EW-7612UAn or my other wifi usb dongles with any of the following drivers to start: r8188eu or 8192cu or cfg80211 or rtl8192cu

Lsmod only shows one lonely driver, I have tried the following:

$ lsmod
Module                  Size  Used by
8723bs               1245184  0 

$ dmesg
[    2.306543] usb 1-1.4: New USB device found, idVendor=7392, idProduct=7822
[    2.306591] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.306641] usb 1-1.4: Product: 802.11n WLAN Adapter
[    2.306674] usb 1-1.4: Manufacturer: Realtek
[    2.306706] usb 1-1.4: SerialNumber: 00e04c000001

I have installed the packages:
firmware-ralink for Ralink devices (RT5370/RT3070/etc.)

firmware-realtek for Realtek devices (RTL8188CUS/etc.)

I rebooted the board.

wlan0 the internal wifi chip works well.

ifconfig nor iwconfig shows wlan1

How can i get Edimax or Realtek wifi usb devices running?
Reply
#2
(04-03-2017, 12:03 AM)hblanken Wrote: Does the board support any Wifi via USB yet? 
How can i get Edimax or Realtek wifi usb devices running?

Not possible (for TinkerOS), kernel driver is not compiled as module or built-in, firmware is insufficient.

Code:
# egrep 'r8188eu|rtl8192cu' /lib/modules/$(uname -r)/modules.builtin
# find /lib/modules/$(uname -r)/kernel | egrep 'r8188eu|rtl8192cu'
# gunzip -c /proc/config.gz |  egrep -i 'r8188eu|rtl8192cu'
   # CONFIG_RTL8192CU is not set  
   # CONFIG_R8188EU is not set

I do not know where the sources for kernel are.

Code:
# ls -l /lib/modules/$(uname -r)/source
   lrwxrwxrwx 1 root root 50 Feb 23 10:00 /lib/modules/4.4.16/source -> /home/leslie_yu/ASUS/source/linux4.4-rk3288/kernel

ASUS "leslie_yu" forget to distribute kernel sources  Angry (not part of debian packages) to change config and recompile kernel with requested drivers (maybe https://github.com/rockchip-linux/kernel or https://github.com/rockchip-linux/kernel/tree/release-20160818-miniarm (miniarm was previous name for TinkerBoard) or https://github.com/Kwiboo/linux-rockchip (Kwiboo from Sweden?)).

M.C>
Reply
#3
(04-04-2017, 07:04 PM)mcerveny Wrote: ASUS "leslie_yu" forget to distribute kernel sources  Angry (not part of debian packages) to change config and recompile kernel with requested drivers (maybe https://github.com/rockchip-linux/kernel or https://github.com/rockchip-linux/kernel/tree/release-20160818-miniarm (miniarm was previous name for TinkerBoard) or https://github.com/Kwiboo/linux-rockchip (Kwiboo from Sweden?)).

M.C>

And 4 ASUS "leslie_yu" this is why Asus Tinker Board will fail....Grrrrh!!! get the distribution kernel sources out there! this isn't a closed loop system...share the love.....not hide the magic..wrong platform 4 that!!!!
Reply
#4
The last days I have now tried many things on this new board. I had high hopes and was really excited when I received the board.

I have many, many Pi2, Pi3 Pi0, C2 and want to give this board a shot.

I read many posts about how this is still 'beta' and we need to give Asus time. While I agree, a) I also notice that some of the essentials for making a great linux board are not in place (yet), b) and Asus is moving too slow. The first boards were shipped in Jan - it is April now.

A week into testing, I notice several areas to immediately improve on:
-Better linux command level support and explanations - there is so little, no FAQs, no tutorials, no clear examples. Try this: Work with leading bloggers, hackers, makers to create tutorials. Take a leaf out of how other companies do it well, Pi Foundation, Google, Amazon, Intel, etc.
-Really delivering on the promise of GPU integration for any sort of video encoding and decoding, full integration with the most widely used packages such as gst, ffmpeg, opencv, etc. I would prefer Linux command and script level, less screen and GUI level.
-Making sure accessories, HATs, kits work easily. Several suggestions: a) Integrate drivers into kernel (see thread above) to make it seamless b) work with the most prolific manufacturers, Cameras, usb devices such as Wifi Edimax/Realtek, Screens c) Test the most common Pi HATs for compatibility, publish lists of kits. Look at this - nice -: http://elinux.org/RPi_USB_Wi-Fi_Adapters
-Make sure you make as much as possible compatible with Pi to build on the Foundations strength, don't try to build another silo

For now my Tinkerboard sits on the shelf. The essentials don't work (yet). Cannot use it as my Edimax EW-7612UAn second usb Wifi does not work/no driver in kernel and the Pi camera nor my Auvidea HDMI B101 is recognised. Will try it again once I have regained confidence in support and compatibility.
Reply
#5
You can try following for TinkerOS1.4 (kernel sources available) directly on TinkerOS1.4 (or you can try crossbuild). I tested it for RTL8192CU.
  1. apt-get install build-essential libncurses5-dev #... and many other as needed
  2. tar xzf 20170223-tinker-board-linaro-jessie-alip-kernel-v1.4.tar.gz
  3. cd 20170223-tinker-board-linaro-jessie-alip-kernel-v1.4
  4. make ARCH=arm miniarm-rk3288_defconfig # weird, default is "arm64" and this will not work, use ARCH=arm everywhere or edit Makefile
  5. # check, that config are equivalent # gunzip -c /proc/config.gz > /tmp/config; diff .config /tmp/config
  6. make ARCH=arm menuconfig # enable wifi
  7. diff /tmp/config .config # check that is all as expected
    Code:
    1591c1591,1595
    < # CONFIG_RTL8192CU is not set 
    --- 
    > CONFIG_RTL8192CU=m 
    > CONFIG_RTLWIFI=m 
    > CONFIG_RTLWIFI_USB=m 
    > CONFIG_RTLWIFI_DEBUG=y 
    > CONFIG_RTL8192C_COMMON=m
  8. vi Makefile # CFLAGS_MODULE = -fno-pic # toolchain dependend, I got error in modules "Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)" without this
  9. make ARCH=arm savedefconfig
  10. make -j4 ARCH=arm zImage dtbs modules
  11. # corrects all uncompilable warnings in kernel sources, and repeat previous step until successful
  12. mv /boot/zImage /boot/zImage.old
  13. cp ./arch/arm/boot/zImage /boot/
  14. # check, that dtb is the same, no need to reinstall # md5sum /boot/rk3288-miniarm.dtb ./arch/arm/boot/dts/rk3288-miniarm.dtb
  15. make ARCH=arm modules_install
  16. # check, module tree # find /lib/modules/$(uname -r)/kernel
  17. # if needed # make ARCH=arm firmware_install
  18. # if needed # make ARCH=arm headers_install INSTALL_HDR_PATH=/usr
  19. apt-get install firmware-realtek # firmware
  20. reboot
  21. dmesg
    Code:
    [   31.811602] usb 1-1.2: new high-speed USB device number 5 using dwc2
    [   31.915205] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=8176
    [   31.916209] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [   31.917213] usb 1-1.2: Product: 802.11n WLAN Adapter
    [   31.917960] usb 1-1.2: Manufacturer: Realtek
    [   31.918619] usb 1-1.2: SerialNumber: 00e04c000001
    [   32.250840] rtl8192cu: Chip version 0x10
    [   32.433526] rtl8192cu: MAC address: 00:13:...
    [   32.433837] rtl8192cu: Board Type 0
    [   32.434262] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
    [   32.434733] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
    [   32.440236] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
    [   32.449257] usbcore: registered new interface driver rtl8192cu
    [   32.484121] rtl8192cu 1-1.2:1.0 wlx0013...: renamed from wlan1
    [   32.564418] IPv6: ADDRCONF(NETDEV_UP): wlx0013...: link is not ready
  22. ip link
    Code:
    4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000    link/ether 4a:31:... brd ff:ff:ff:ff:ff:ff5:
    wlx0013...: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000    link/ether 72:34:... brd ff:ff:ff:ff:ff:ff
  23. iwlist wlx0013... scan # and you see WiFi networks
For more help search Internet, happy hacking Wink
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)