Home» » Linksys Wireless Usb Drivers For Linux

Linksys Wireless Usb Drivers For Linux

0Home
Linksys Wireless Usb Drivers For Linux

Recently purchased a Linksys AE1200 USB wifi dongle to use with my debian box for setting up a wifi AP. Unfortunately it doesnt seem to work out of the box and I cant.

• • • • • • • • The Linksys AE6000 is a nice little wireless AC adapter that you can purchase from places like Fred Meyers or Best Buy. It’s not too expensive for what it offers. The speed is decent too. The problem, once again, comes down to Cisco not offering driver support for Linux. Luckily and linked to some drivers that you can compile. Because I didn’t have internet access when I performed his steps, I decided to skip the git part and simply link to the compressed file. You can download this tar file to a USB drive and copy it to the computer with the AE6000 wifi dongle.

Linksys Wireless Usb Drivers For Linux

Once the file has been copied, extract it to a folder in your user directory and run the following commands to install the driver. Cd mediatek_mt7610u_sta_driver_linux-64bit make clean make sudo make install Now that this is installed, simply connect the AE6000 to a USB port and connect to your wireless network! No one else seems to have encountered this, but the compile fails for me. This is a fresh 16.10 installation for dual boot with Win10, and I am trying to get the excellent AE6000 up and running. I get multiple compile errors, the first of which is an incompatible pointer error. If I fix it, I run into another, and then another, etc. I eventually hit one which can’t be resolved by a simple type modification, or cast.

I have done all steps recommended by the (more involved) AskUbuntu thread, and tried 3 separate sources for the code, and nothing changes. So it seems there are some compiler switches missing, or something. I am a 34yr oldp smart techie that’s new to Linux and trying to learn.

I’ve installed a dual boot Win10/Mint 18. Torrent Copytrans Crack Code. 1. I copied the file to my Download folder and extracted it there. On the mediatek folder I selected: Actions: Open Terminal Here. Then I entered the above commands. The make command gives a ‘fatal error: studio.h: no such file or directory’ I don’t know if this has something to do with me needing owner permissions or if I have placed the folder in the wrong location. When I try to place the folder in the root usr folder, as it mentions in the directions above, i still get the same error. After trying to build the driver using git, which failed with an unresolved reference, I decided to follow your method.

The process seemed to proceed smoothly, until I got a series of compilation error ending in failed make. Here I should mention that I was using Inspiron 1100 which is a 32 bit machine. I hate to ask this but I suck at life when it comes to Linux. I have always been around dos, windows, and apple pcs most of my life more so the microsoft end of things. So I downloaded the archive, and I have tried copping the files in my home directory, and downloads but I have no idea what the terminal codes are in reference to.

I get an error every time. How would I use the above code if say the folder “mediatek_mt7610u_sta_driver_linux-64bit” was placed on my desktop? I am running Ubuntu 17.10 64Bit edition, at least till I go nuts & reinstall Windows 10.

Thanks for the help!

Linux introductions, tips and tutorials. Any distro, any platform! Explicitly noob-friendly. Please don't intimidate people who are coming to learn and get help. If you're posting for help, please include the following details, so that we can help you more efficiently: • your operating system and version • the hardware you're using • a description of the problem • output that was displayed (if any) Questions are encouraged. If you fix the problem yourself, please post your solution, so that others can also learn. There's a great - thanks to SCSweeps.

Other subreddits you may like: Does this sidebar need an addition or correction? I think I've done my due diligence looking around the web at large and this subreddit for answers but haven't found anything yet. I'm hoping you guys could help me. I am a total newb. It's taken me 3 excruciating months just to get a distro installed so I could even start learning what the heck I am doing. So, please, please, dumb down any possible solutions: ( Bottom Line Up Front: Trying to install drivers for LINKSYS WUSB 6300 USB Wifi Adapter on a machine that cant otherwise connect to internet.

• I have an intel core i5 system with an AsRock Z87 mobo with UEFI 'BIOS'. • It has a fresh install of Fedora 21. Nothing is on it other than what the live image from less than a month ago came with. • There is no easy way to connect this box via hardwire to the intenet, so anything I need to get the wifi adapter working, has to be sneakernet'ed over via flash drive • I have verified that while linux sees the USB adapter, there is no driver installed for it I have brought over the latest official linux driver (I think): rtl8812AU_8821AU_linux_v4.2.2_757 I extracted the files and tried to run make on the directory with the makefile that came with the driver package. Received following errors: make[1]: * /lib/modules/3.17.4-301.fc21.x86_64/build: No such file or directory. Makefile:1041: recipe for target 'modules' failed make: * [modules] Error 2 Im at a loss as to what to do. Honestly, even if the make command worked, I wouldnt be sure what to do next.

I cannot find a decent explanation of how driver installation in linux works. Should I try NDISWrapper with the windows driver for the dongle? Id like to try and get the makefile working if possible, if only to learn more about linux.

/lib/modules/3.17.4-301.fc21.x86_64/build It is telling you the file or directory build is not where it expects to find it. /lib is a top level directory on linux. If you run this command, $ cd / You will (change directory) to the very top of your file system.

If you then run this command, $ ls You'll (list directory contents) of all the top level directories like /lib /home /bin /root /boot So back to ls $ cd / $ ls /lib Here ls /lib will list the contents of /lib. If you see modules listed, you can drill down further with, $ ls /lib/modules Dig deeper one level at a time, using the error above untill you get not found. Then you could, $ cd /lib $ cd /lib/modules and so on, actually I suggest you do that (change directory) after each (list directroy) so again, from the start, $ cd / $ ls $ cd lib/ $ ls $ cd modules/ dig down until you can no longer follow the path given in the error message. I don't know how to use the package manager in RedHat, but I'm pretty sure ( not positive) you need to figure out how to search the repos and install the correct kernel headers. Also a package called build-essential or something like that. Actually, I'm more sure about the build-essentials than the kernel headers, but I think you need both. Build-essentials may be called something else in RedHat, and it might pull in the headers automatically.