{"id":351,"date":"2014-06-24T12:34:47","date_gmt":"2014-06-24T12:34:47","guid":{"rendered":"https:\/\/digitalchild.info\/?p=351"},"modified":"2014-06-24T12:34:47","modified_gmt":"2014-06-24T12:34:47","slug":"raspberry-pi-asus-n10-wireless","status":"publish","type":"post","link":"https:\/\/randomadult.local\/raspberry-pi-asus-n10-wireless\/","title":{"rendered":"Raspberry Pi + Asus N10 wireless"},"content":{"rendered":"
I’ve finally got some time to do some work on my time-lapse project when I hit a brick wall straight off the bat. My $15 tiny wireless adaptor from Asus wasn’t working so I did some digging to try to work out what was going on.\u00a0I first tried to use the GUI WiFi Config and it was able to detect the wireless AP but I was unable to connect. I did some digging and worked out what I needed to do to get it working.<\/p>\n
I’m using the official Raspbian<\/a> image from the raspberry pi website. The good folks over at Element14 have a page that outlines their wireless adaptor testing<\/a> and list the N10 as a working adaptor\u00a0with the right kernel module loaded.<\/p>\n It uses a Realtek RTL8188u chipset with the r8712u kernel module that is available in staging on wheezy.<\/p>\n This is what you have to do to get the Raspberry Pi + Asus N10 wireless adaptor working. I have the wireless adaptor plugged into a powered USB hub along with a Dell keyboard and mouse.<\/p>\n Load the module for your current terminal session<\/p>\n Check that the module is loaded<\/p>\n This should output a bunch of other stuff but I’ve cut if off. If you see the r8712u in the list, then its loaded. If it does, you’re all good. If not make sure that you’re using the correct version of Raspbian.<\/p>\n Next you will want this to load on every boot so the easiest way to do that is to add it to the modules for boot.<\/p>\n Next I had to remove the wpa_supplicant configuration that was in my network interfaces file after the GUI WiFi\u00a0config\u00a0failed.<\/p>\n Your \/etc\/network\/interfaces<\/strong> file should look like this. Use sudo vi<\/strong> to open the file and edit as required.<\/p>\n Next you’ll need to take the interface down and back up again<\/p>\n Once this has completed you’ll be\u00a0connected to your wireless network and it will output the IP for you once the DHCP lease is active. It should look something like the following.<\/p>\n I’ve finally got some time to do some work on my time-lapse project when I hit a brick wall straight off the bat. My $15 tiny wireless adaptor from Asus wasn’t working so I did some digging to try to work out what was going on.\u00a0I first tried to use …<\/p>\n\n\nsudo mod_probe r8712u\n\n<\/pre>\n
\n\nsudo lsmod\n\nModule\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Size\u00a0 Used by\nr8712u\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 168753\u00a0 0\nsnd_bcm2835\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 16165\u00a0 0\nsnd_soc_bcm2708_i2s \u00a0 \u00a0 5474\u00a0 0\nregmap_mmio \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 2806\u00a0 1 snd_soc_bcm2708_i2s\n.....\n<\/pre>\n
\n\necho "r8712u" | sudo tee -a \/etc\/modules\n\n<\/pre>\n
\nauto lo\niface lo inet loopback\niface eth0 inet dhcp\n\nallow-hotplug wlan0\nauto wlan0\niface wlan0 inet dhcp\nwpa-ssid\u00a0YourSSID\nwpa-psk\u00a0YourPassword\n<\/pre>\n
\nsudo ifdown wlan0; sudo ifup wlan0;\n<\/pre>\n
\nListening on LPF\/wlan0\/bc:ee:7b:e4:e2:41\nSending on \u00a0 LPF\/wlan0\/bc:ee:7b:e4:e2:41\nSending on \u00a0 Socket\/fallback\nDHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5\nDHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7\nDHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12\nDHCPREQUEST on wlan0 to 255.255.255.255 port 67\nDHCPOFFER from 192.168.1.1\nDHCPACK from 192.168.1.1\nbound to 192.168.1.113 -- renewal in 40150 seconds.\n<\/pre>\n","protected":false},"excerpt":{"rendered":"