Setting up WiFi in MK 802 II

Everybody would’ve experienced the d’uh moment of truth, at which you realise that you spent hours looking for a solution that was right in front of you.

In this instance, while setting up the MK 802 II, I failed to notice that the WiFi chip inside MK 802 II is slightly different than MK 802. Another fact which made it even more difficult was that the 8188 chip inside MK 802 II (  MK 802 has 8192 based chip ) is a specific variant 8188eu. If it was a plain 8188, then the 8192cu module (which holds the driver for the MK 802’s WiFi chip )would’ve worked.  Should’ve looked carefully at the description behind the package-box of the device  when I the unpacked it I guess.
 However as I found out, device identifier for the 8188eu chip was not present inside the 8192cu driver which i was force loading through /etc/modules . P.S: you can find out the device identifiers supported through a driver module using : modinfo module_name.ko
miniand@miniand:~$ modinfo 8188eu
filename: /lib/modules/3.0.36-t1+/kernel/drivers/net/wireless/rtl8188eu/8188eu.ko
version: v4.1.2_4787.20120803
author: Realtek Semiconductor Corp.
description: Realtek Wireless Lan Driver
license: GPL
srcversion: E54AFC4145D0A7E7121B00D
alias: usb:v0BDAp8179d*dc*dsc*dp*ic*isc*ip*
depends:
vermagic: 3.0.36-t3+ preempt mod_unload modversions ARMv7
For finding the actual drivers, all you need is the ability to cross compile the kernel with the relevant code segments. Or else, a plain simple ability to google for the particular version.
The latter way needs some luck as well. To begin the quest, we will need to find out the exact information about the device. Plug in the device and follow these steps:
  1.  Open terminal  & run lsusb .  Through this you can find out the device identifiers of various devices connected to your linux box.
    miniand@miniand:~$ lsusb
    Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 002: ID 0bda:8179 Realtek Semiconductor Corp.
  2.  Note down the identifier for the device you are trying to install drivers for.
  3.  Google it 😉 .
8188eu modules for MK 802 II –
Rtl8188eu
Rtl8188eu
rtl8188eu.zip

276.0 KiB
349 Downloads
Details…

 After finding out the module required for the particular device to work( should be for your chipset – arm,x86,x64 etc and kernel version ). You can follow these steps to put it for the test.

  1. Check for the identifier inside the module using modinfo module_name.ko
  2. Copy the module file into the relevant module file folder. If it’s for the 8188eu , then it should go to the /lib/modules/~kernel_version~/kernel/drivers/net/wireless .
  3. After putting it there, run  depmod -a  as sudo/root.
  4. Run a modprobe 8188eu to check if its loaded correctly.
  5. Reboot your box.

To check if the wireless chip driver for 8188eu been loaded correctly and is working, you can run iwconfig .

miniand@miniand:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

tunl0 no wireless extensions.

wlan2 IEEE 802.11bgn ESSID:"NFi" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:2.422 GHz Access Point:
 But if it is not, may be the device identifier is not exactly correct. You can force load a module by adding its name to /etc/modules file.
8188eu
mali
mail_drm
ump
nand
usbserial vendor=0x1c9e product=0x9e00
option
# /etc/modules: kernel modules to load at boot time.

 My module file looks like the above picture ( in my MK 802 II) since my device requires modules such as Mali (which are not mandatory hence ubuntu won’t load them by default ) :         So I’ve explained these informations in this article :

  • How do you find out the modules for devices without driver in your linux box.
  • How to install the module and make it work once you have the module file with you.
  • How to force load a driver module to make certain hardware work.

Leave a Reply