Site Loader

Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of service , privacy policy and cookie policy , and that your continued use of the website is subject to these policies. Could this be causing the kernel to be using the wrong driver for the card? I tried the device on two different Ubuntu systems one 32bit and one 64bit and achieved the same results on each. Will not run on Pure “N” but works as “G”. Works out of the box in Breezy via the madwifi linux-restricted-kernel that is included by default. This book contains many real life examples derived from the author’s experience as a Linux system and network administrator, trainer and consultant. Visit the following links:

Uploader: Temuro
Date Added: 8 March 2015
File Size: 46.27 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 61013
Price: Free* [*Free Regsitration Required]

Post as a guest Name.

For details and our forum data attribution, retention and privacy policy, see here. Google on that number with the word linux to find the best driver set for it. Will not run on Pure “N” but works as “G”. I looked at the packaging and at the linx page, and guessed number 2, allowed to finish, and rebooted.

For more advanced trainees it can be a desktop reference, and a collection of the wirreless knowledge needed to proceed with system and network administration. After almost giving up I decided to go to the ” Supported wireless cards list and procedure to get help.


Configuring ndiswrapper the open-source program that uses Windows drivers to make hardware work in LinuxI used the Windows XP, and 98 drivers, all of which worked equally poorly. I was just looking at your post February 6th, 3. Originally Posted by Jeff91 I think I’ve gained some insight into why the Wireless card does not connect properly – for some reason when I do an lsusb it lists the card as an atheros device even though it is a ralink chipset Please add a comment to what you had to do to get it to work if this was possible, as well as a URL to an outstanding Launchpad bug report to address the issues encountered.

When I attach it to my Ubuntu system it is recognized by the network manager and it can see my wifi network – however it is unable to connect. Results 1 to 10 of Be sure to substitute file name below with the version you downloaded.

[SOLVED] AWLL Airlink installation help

Could this be causing the kernel to be using the wrong driver for the card? In my experience, newer wireless adapters are a bitch to get configured in Linux, whereas older adapters like my Orinoco WaveLAN Silver pretty much configure themselves.

For that price, I was willing to take a chance on it. AWLL Airlink installation help After almost giving up I decided to go to the ” Supported wireless cards list and procedure to get help. Solution involves blacklisting certain kernel modules wirlink101 the ra and installing the drivers from ralinktech. Used Linux Ubuntu 2.


en/users/Devices/USB – Linux Wireless

In all cases, I can get the wireless adapter to light up, and I can find a wireless network. The time now linuux Any help would be appreciated. If you’d like to contribute content, let us know. Have you tried setting a static IP address just for the sake of seeing if your adapter can connect with the network?

Giving up on Linux wireless with the Airlink 101 AWLL3028

Ask Ubuntu works best with JavaScript enabled. Kernel panics on initial install, see instructions here for addtional installation steps: I must say it is stronger to connect to my home wifi however it doesn’t see as many access points in the neighborhood as the internal wifi had.

But for my sake of sanity I hit the wifi button on the laptop that is supposed to turn off eireless internal and although the light kept going the internal shut off. Having a problem airkink101 in? It continued detect the wireless network after the reboot, but would never complete the connection.

AWLL Airlink installation help Thanks to ibootindos and everyone for the solution – that worked great! Join our community today! Rebooted same kernel panic!