Easy/possible to install driver for RNX-AC600UB in Pogoplug?

The thought occurred to me, I have three of these: http://www.newegg.com/Product/Product.aspx?Item=N82E16833166105
They come with drivers that work in Windows and Mac so far, and a Linux version as well.

This could make sense in either the E02 with more RAM, or Pro as some kind of memory extension could be put into that free pcie slot. Also it makes much more sense in openWRT of course. It won't kill me not to have it working, but that would maybe be neat if it did.

p.s. if you read the reviews they aren't all glowing. Mine work great; dropped connections depend solely on the router they're connected to. AT&T Pace router: bad. Rosewill router: perfect.

=========
-= Cloud 9 =-



Edited 1 time(s). Last edit at 04/22/2015 10:26PM by JoeyPogoPlugE02.

It might be possible. But depending on what the driver looks like. If it's too old, potentially there will be problem compiling. i.e retrofitting will take some or a lot of works. Does the manufacture website provide driver source code?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

That's one place they're terrible - working drivers for Mac came from a 3rd party, but I have one linux driver here, after untarring it's a blank file with no extension. Hey bodhi offhand do you have the code that makes Linux tell the kernel version? I'm making a cheatsheet with my Pogoplug specs and that might be a help if they're all listed like that. Might even help see if one kernel is best. If yer busy don't worry about it, and I hope you don't mind me thinking out loud and getting the idea on "paper" before bedtime here.

=========
-= Cloud 9 =-

Joey,

The command is

uname -a

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Great, thanks for the momentum. This is the uname command on two Pogoplugs here:

E02 wDebian: Linux debian 3.17.0-kirkwood-tld-1 #4 PREEMPT Wed Oct 22 00:55:17 PDT 2014 armv5tel GNU/Linux

E02 wArch:Linux alarm 3.19.3-1-ARCH #1 PREEMPT Fri Mar 27 04:17:26 MDT 2015 armv5tel GNU/Linux

Pogoplug Pro Debian: Linux DebianPlug 3.18.5-oxnas-tld-1 #2 SMP PREEMPT Thu Feb 12 11:17:40 PST 2015 armv6l GNU/Linux


I'll scour for drivers and chipset info next opportunity. Back in a bit..

=========
-= Cloud 9 =-

@joey

post up the results of the following commands from your Pplug when one of these is inserted

lsusb

and

dmesg | tail #when you plug the usb device in and when you remove it.


depending on the windows driver there may be an old school way of using that with ndiswrapper : assuming they have released an XP driver at some point

-update- yes I see XP drivers both 32 and 64-bit. My notes say this wireless USB is also known as RTL8811AU


E02 running Arch on IDE drive connected to Pogo with USB adapter

Okay first command (with it plugged in, Arch Linux on E02 gets this:

Bus 001 Device 004: ID 0bda:0811 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Second command, plugged-in front jack:

[root@alarm ~]# lsusb
Bus 001 Device 004: ID 0bda:0811 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[root@alarm ~]# ^C
[root@alarm ~]# dmesg | tail
[   21.352639] systemd[1]: Started Update is Completed.
[   21.358983] systemd[1]: Started Commit a transient machine-id on disk.
[   21.392075] systemd[1]: Started Journal Service.
[   21.616806] systemd-journald[67]: Received request to flush runtime journal from PID 1
[   28.125227] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   42.466193] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[   42.476079] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 2670.643558] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[ 3242.888991] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 3281.843213] usb 1-1.4: new high-speed USB device number 4 using orion-ehci
[root@alarm ~]#

RTL8811AU unplugged:

[   21.358983] systemd[1]: Started Commit a transient machine-id on disk.
[   21.392075] systemd[1]: Started Journal Service.
[   21.616806] systemd-journald[67]: Received request to flush runtime journal from PID 1
[   28.125227] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   42.466193] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[   42.476079] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 2670.643558] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[ 3242.888991] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 3281.843213] usb 1-1.4: new high-speed USB device number 4 using orion-ehci
[ 3409.097338] usb 1-1.4: USB disconnect, device number 4
[root@alarm ~]#

Pogo Pro w Debian, wireless plugged-in

root@DebianPlug:~# lsusb
-bash: lsusb: command not found
root@DebianPlug:~# dmesg | tail
[   16.644912] EXT3-fs (sda1): using internal journal
[   16.795228] random: nonblocking pool is initialized
[   27.380188] stmmaceth 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[  305.683947] usb 1-1.4: USB disconnect, device number 4
[ 1491.710696] usb 1-1.4: new high-speed USB device number 5 using oxnas-ehci
[ 1491.821583] usb 1-1.4: New USB device found, idVendor=0bda, idProduct=0811
[ 1491.828441] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1491.836172] usb 1-1.4: Product: RNX-AC600UB
[ 1491.840386] usb 1-1.4: Manufacturer: Rosewill Limited
[ 1491.845419] usb 1-1.4: SerialNumber: 00e04c000001

RTL8811AU unplugged:

root@DebianPlug:~# dmesg | tail
[   16.795228] random: nonblocking pool is initialized
[   27.380188] stmmaceth 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[  305.683947] usb 1-1.4: USB disconnect, device number 4
[ 1491.710696] usb 1-1.4: new high-speed USB device number 5 using oxnas-ehci
[ 1491.821583] usb 1-1.4: New USB device found, idVendor=0bda, idProduct=0811
[ 1491.828441] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1491.836172] usb 1-1.4: Product: RNX-AC600UB
[ 1491.840386] usb 1-1.4: Manufacturer: Rosewill Limited
[ 1491.845419] usb 1-1.4: SerialNumber: 00e04c000001
[ 2864.915942] usb 1-1.4: USB disconnect, device number 5

-update 10- PogoplugPro-Debian's dmesg | tail is encouraging where I see things, given specific ID points for that hardware. I went through Webmin and see there's lots of options near figuring a solution but not perfect yet. This actually seems doable.

=========
-= Cloud 9 =-



Edited 11 time(s). Last edit at 04/23/2015 02:19PM by JoeyPogoPlugE02.

There is a driver for this device and you will most likely need to compile it yourself

That chipset is another of the "one used by many"

http://www.linux-hardware-guide.com/uk/2014-09-17-edimax-ew-7811utc-ac600-usb-wifi-dual-band-802-11ac-5ghz-802-11n-2-4ghz

have a look at the link above and it should enable you to do it.

Cheers

Sudo doesn't work but i got the driver, un-tarred it to files, renamed the folder rtl8812au and used WinSCP to copy it to Pogplug Pro's (Debian) /tmp folder. So the "make" file is in there and the other stuff. Trying my luck at various cd and whatnot in PuTTY but aren't having luck yet.

-edited- took a break and came back a while later

root@DebianPlug:~# cd /home/DebianPlug
-bash: cd: /home/DebianPlug: No such file or directory
root@DebianPlug:~#

I'm in there as root, and Qui's tutorial calls this installation DebianPlug. I can see noodling around the Ubuntu-centric instructs, for instance that " apt-get install build-essential" downloaded and i hit the Y prompt, but am hitting snags right were you see it. Any ideas do tell!


-update- hey it's okay if we put this to the back burner - but for people who have headless Linux installs, some of the hows and whys of command line stuff would be a great help. I keep looking at that code and getting clues as to why it works. This part is fun. i have no idea what the interface looks like in Webmin or whatever it displays from.

=========
-= Cloud 9 =-



Edited 4 time(s). Last edit at 04/25/2015 10:59AM by JoeyPogoPlugE02.

Joey,

Quote

but for people who have headless Linux installs, some of the hows and whys of command line stuff would be a great help

It is a little bit hard to know you've posted your progress or stumping block :) since you only updated the post, instead of posting new entry (people only reads the post if the new post red indicator lights up).

Quote

root@DebianPlug:~# cd /home/DebianPlug

You usually do this if there is a user named "DebianPlug". In this case DebianPlug is the host name, not a user name, so there is probably no directory there under that name.

In case you need help compiling please post info where do you get the source code and I'll take a look.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@Bodhi
Your point to Joey is well made, i have asked him in the past to add new entries so we can follow his thought pattern and experiences.

The link to the firmware i found for the the chipset can be located here.
http://www.edimax.com/images/Image/Driver_Utility/Wireless/NIC/EW-7822UAC/EW-7822UAC_linux_v4.2.2_7502.20130517.tar.gz

There's two sources for installation instructions.
First: http://www.linux-hardware-guide.com/uk/2014-09-17-edimax-ew-7811utc-ac600-usb-wifi-dual-band-802-11ac-5ghz-802-11n-2-4ghz

Sudo and Git aren't' recognized in PogoplugPro Debian, so I went with:

Second: the edimax PDF manual (page 18)


Step #3

sudo apt-get install build-essential

I discard the sudo part and enter starting with apt... good and well.. updates

Step #4

Quote

Change to the “Home” directory and type the command below (where
“test” is your login username):

So i enter what they want, replacing "test" with username, devicename, root, swearwords LOL:

cd /home/test

but neither work

So I figure, keep the file names somewhat intact but use any directory that'll have them, in this case, /home

root@DebianPlug:~# cd /home/root
-bash: cd: /home/root: No such file or directory
root@DebianPlug:~# cd /home/DebianPlug
-bash: cd: /home/DebianPlug: No such file or directory
root@DebianPlug:~#

Step 6 from PDF manual: I got that far noodling around and substituted a part of the code to become:

tar  vxf  EW-7822UAC_linux_v4.2.2_7502.20130517.tar.gz

Yeah! So it extracted and

ls

got this result:

root@DebianPlug:/home# ls
.
..
EW-7822UAC_linux_v4.2.2_7502.20130517
EW-7822UAC_linux_v4.2.2_7502.20130517.tar.gz
rtl8812AU_8821AU_linux_v4.2.2_7502.20130517
root@DebianPlug:/home#

So it's time to hit make:

root@DebianPlug:/home# cd EW-7822UAC_linux_v4.2.2_7502.20130517
root@DebianPlug:/home/EW-7822UAC_linux_v4.2.2_7502.20130517# make
make: *** No targets specified and no makefile found.  Stop.
root@DebianPlug:/home/EW-7822UAC_linux_v4.2.2_7502.20130517#

Now i'm a bit confused. But I thought I'd seen a file called Makefile and that didn't run either. Had to try it. Pretty close though and I've made a notepad of the steps that worked, so if there's a next time it'll be a breeze.

=========
-= Cloud 9 =-



Edited 7 time(s). Last edit at 04/26/2015 12:40AM by JoeyPogoPlugE02.

though I have doubts anyone can stand this any longer, let me show where I know it's going wrong:

The driver as downloaded is EW-7822UAC_linux_v4.2.2_7502.20130517.tar.gz

Their instructions are:

1. Ensure that your computer is connected to the Internet.
2. Click on “Dash Home” and then type “terminal”. Click the “terminal” icon.
3. Execute the command below to download the packet which is necessary to 
build the driver.
sudo apt-get install build-essential
Type the password for the administrator, and then type “y” to install the 
gcc packet.
4. Change to the “Home” directory and type the command below (where 
“test” is your login username):
cd /home/test19
5. Extract the driver using the command below:
tar vxf 2011_0427_RT3572_Linux_STA_v.2.5.0.0.DP.bz2
6. Check the extracted file with the command “Is”:
7. Change to the driver folder and execute the command below:
cd rtl8812AU_8821AU_linux_v4.2.0_6952.20130315
8. Build the driver. Execute the command below and then input the password.
sudo make
9. Execute the command below to load the driver.
sudo insmod os/linux/rt3572sta.ko
10. Plug the EW-7811UTC into your computer and restart Ubuntu.20
11. When Ubuntu has restarted, click on “Dash Home” and then type 
“network”. Click on the “network” icon as below.
12. Click on “Wireless” and then click the icon to open the drop-down menu 
labeled “Network Name”. Select the network you wish to connect to and 
enter the necessary security information.21
13. Click on “Wireless” and then click the icon to open the drop-down menu 
labeled “Network Name”. Select the network you wish to connect to and enter the necessary security information

Their own instructions: call the driver by a different name, use sudo commands we don't and god only knows if ARM architecture is supported.

Any ideas?

=========
-= Cloud 9 =-

Joey,

1. No need to use sudo, you are root.

2. The build directory is in the rtl* folder. So just cd into that and start the build:

cd rtl8812AU_8821AU_linux_v4.2.2_7502.20130517
make

The rule of thumb is: whenever you see a directory with a Makefile, it means you can build something by executing make. make will look for the Makefile and use the "target" that you specified (in this case the target is "all", because you did not have any argument for make).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 04/28/2015 06:46PM by bodhi.

It got me further, here's two tries - oh and the wireless isn't plugged-in because I'm pretty sure that gets plugged in if it sticks and reboots:

root@DebianPlug:~# cd /home/
root@DebianPlug:/home# cd rtl8812AU_8821AU_linux_v4.2.2_7502.20130517
root@DebianPlug:/home/rtl8812AU_8821AU_linux_v4.2.2_7502.20130517# make
make ARCH=armv6l CROSS_COMPILE= -C /lib/modules/3.18.5-oxnas-tld-1/build M=/home/rtl8812AU_8821AU_linux_v4.2.2_7502.20130517  modules
make[1]: Entering directory `/usr/src/linux-headers-3.18.5-oxnas-tld-1'
Makefile:610: arch/armv6l/Makefile: No such file or directory
make[1]: *** No rule to make target `arch/armv6l/Makefile'.  Stop.
make[1]: Leaving directory `/usr/src/linux-headers-3.18.5-oxnas-tld-1'
make: *** [modules] Error 2
root@DebianPlug:/home/rtl8812AU_8821AU_linux_v4.2.2_7502.20130517# cd rtl8812AU_8821AU_linux_v4.2.2_7502.20130517
-bash: cd: rtl8812AU_8821AU_linux_v4.2.2_7502.20130517: No such file or directory
root@DebianPlug:/home/rtl8812AU_8821AU_linux_v4.2.2_7502.20130517# make
make ARCH=armv6l CROSS_COMPILE= -C /lib/modules/3.18.5-oxnas-tld-1/build M=/home/rtl8812AU_8821AU_linux_v4.2.2_7502.20130517  modules
make[1]: Entering directory `/usr/src/linux-headers-3.18.5-oxnas-tld-1'
Makefile:610: arch/armv6l/Makefile: No such file or directory
make[1]: *** No rule to make target `arch/armv6l/Makefile'.  Stop.
make[1]: Leaving directory `/usr/src/linux-headers-3.18.5-oxnas-tld-1'
make: *** [modules] Error 2
root@DebianPlug:/home/rtl8812AU_8821AU_linux_v4.2.2_7502.20130517#

I'll noodle around some more. If you see anything, much thanks for telling

=========
-= Cloud 9 =-

Did you try this https://github.com/gnab/rtl8812au ? This should work if you change the CONFIG_PLATFORM section in Makefile i386=y to i386=n and ARM_Rpi=y from ARM_Rpi=n. You need 'git' 'sudo' 'gcc' 'make' 'build-essential' and then the linux-headers for your kernel dpkg'd (edit: looks like you already have it for Oxnas). You modprobe 8812au when the driver is compiled. 'git clone' the provided git address and then cd ~downloaded file name then edit Makefile for processor change and then make, make install and modprobe 8812au.

This worked on a V4, the Oxnas and RPi processors are closer cousins so it probab will work on Pro-Oxnas. Expect moderate speeds due to USB 2.0 limitation. No drivers for chipset in OpenWRT that I could find BTW if that is your future intention.



Edited 2 time(s). Last edit at 04/28/2015 08:08PM by LeggoMyEggo.

I'll try to wrap my head around that - even if I can't, thanks both of you because I learned new things. Eventually this stuff sinks in, and I've got the luck. Leave it to me, a problem where I need to use elements of three instruction sources, two experts and am one line of code further than before this day?

Hey would an Intel Pro b/g mpcie be plug and play? It's not n or ac but i have one in a laptop and am taking it out.

=========
-= Cloud 9 =-

Joey,

> Hey would an Intel Pro b/g mpcie be plug and play?
> It's not n or ac but i have one in a
> laptop and am taking it out.

Why didn't you use the stock wifi card? just want to experiment with another card or because stock wifi card doesn't work?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

If the stock works then cool! Debian and not OpenWRT right? Yeah that still sounds like more fun than i'm having.
If any grownup wants to hold my hand and lead me to how the stock card activates, I don't know. I see it in Webmin...

=========
-= Cloud 9 =-

JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
> If the stock works then cool! Debian and not
> OpenWRT right? Yeah that still sounds like more
> fun than i'm having.

Of course, this is Debian forum :)

> If any grownup wants to hold my hand and lead me
> to how the stock card activates, I don't know. I
> see it in Webmin...

You could start with this and then Leggo or others will jump in the help with the rest:
http://forum.doozan.com/read.php?2,16044,20964#msg-20964

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

That's great news. I tried in Webmin messing around with Networking options and quite frankly am amazed you can already use this as a router.

-update- after changing the apt sources correctly (using WinSCP) I got this:

root@DebianPlug:~# apt-get install firmware-ralink
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package firmware-ralink
root@DebianPlug:~# root@DebianPlug:~# apt-get install firmware-ralink
-bash: root@DebianPlug:~#: command not found
root@DebianPlug:~# Reading package lists... Done
-bash: Reading: command not found
root@DebianPlug:~# Building dependency tree
-bash: Building: command not found
root@DebianPlug:~# Reading state information... Done
-bash: Reading: command not found
root@DebianPlug:~# E: Unable to locate package firmware-ralink
-bash: E:: command not found
root@DebianPlug:~# root@DebianPlug:~#
-bash: root@DebianPlug:~#: command not found
root@DebianPlug:~#

Maybe wireless isn't my forte' - I dunno. Sucks I've got heart disease too because I'd better take a break.

=========
-= Cloud 9 =-



Edited 1 time(s). Last edit at 04/29/2015 01:00AM by JoeyPogoPlugE02.

@Joey
when you change apt sources, you need to do an

apt-get update

then install the package(s)

Got further! I didn't know about that update trick Gravelrash so thanks for that. It updated, then I got to:

root@DebianPlug:~# iwconfig wlan0
-bash: iwconfig: command not found

That's where I'm at.

-update- I'm noodling around in Webmin, and got wlan0 to activate at startup, it's active now but probably missing something. No wireless SSIDs show up as viewed from another computer.

When Linux concepts translate from Windows, that's fun.

=========
-= Cloud 9 =-



Edited 1 time(s). Last edit at 04/29/2015 10:49AM by JoeyPogoPlugE02.

@joey

you need to install the wireless-tools package for iwconfig

apt-get install wireless-tools

@joey while you are at it add yourself teh following too

apt-get install pciutils usbutils

thes will allow you to use lsusb and lspci

(I posted before seeing you'd mention: [apt-get install pciutils usbutils], so I'm doing that now, AFTER what I pasted below)

Great that's a step forward. How's that looking?

root@DebianPlug:~# iwconfig wlan0
wlan0     IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

Gravelrash Wrote:
-------------------------------------------------------
> @joey while you are at it add yourself teh
> following too
>
> apt-get install pciutils usbutils
>
> thes will allow you to use lsusb and
> lspci


Here's the two commands, thanks for the head's up:

root@DebianPlug:~# lsusb
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0781:5575 SanDisk Corp.
root@DebianPlug:~# lspci
00:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
root@DebianPlug:~#

=========
-= Cloud 9 =-



Edited 4 time(s). Last edit at 04/29/2015 12:08PM by JoeyPogoPlugE02.

I tried some command line and this thing was able to result known wireless SSIDs around here.Was pretty happy knowing it was a step forward.
Then I must have entered something wrong in the /etc/network/interfaces file.

-update 1: Pogo wont' boot. Probably having an infinite loop with IP addresses or something.
-update 2: glad i have that Windows app called Ext2 Volume Manager as I plugged in the USB and corrected the entries I'd fudged.

So pogo boots now, but I need to get my /etc/network/interfaces file straightened out.

How does this look? It's the /etc/network/interfaces file

auto lo eth0 wlan0
iface lo inet loopback
iface eth0 inet dhcp

iface wlan0 inet static
        wireless-essid "DebianPro"
	address 192.168.188.1
	netmask 255.255.255.0
	broadcast 192.168.188.255
	network 192.168.188.0

For the time being I thought to call the SSID "DebianPro" for rememberable reasons, but there's stuff I'm missing.
Well it boots over Ethernet and Webmin works. Wireless not yet.

=========
-= Cloud 9 =-



Edited 4 time(s). Last edit at 04/29/2015 02:01PM by JoeyPogoPlugE02.

@Joey

are you trying to hook this into an existing wireless network or are you looking to create your own?

PogoPro-Debian's onboard wireless would just allow m Windows laptop(s) to access Pogo's Webmin, Samba shares and onboard stuff.

=========
-= Cloud 9 =-



Edited 3 time(s). Last edit at 04/29/2015 02:54PM by JoeyPogoPlugE02.

if you are trying to get this card to work as your "access point" here is a good starter for 10.

https://nims11.wordpress.com/2012/04/27/hostapd-the-linux-way-to-create-virtual-wifi-access-point/

however, this card will turn round and bite you in the @rse if you try and use it as a hostapd... unless you are comfortable recompiling the driver and hostapd packages....

to use it as a wireless client you need something like wpa_supplicant another good starter for 10..

http://www.cyberciti.biz/faq/debian-linux-wpa-wpa2-wireless-wifi-networking/

HOWEVER, watch out when you disconnect the ethernet cable.... the networking will stop working on the wifi card.... there is a workaround on this forum.

EDIT : networking will APPEAR to stop working on the wifi card - workarounds here courtesy of DonCharisma and twinclouds http://forum.doozan.com/read.php?2,19949



Edited 1 time(s). Last edit at 04/29/2015 03:04PM by Gravelrash.