Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I was reading the installation wiki at sourceforge again, and thought I'd try brining up the interface using "dhclient wlan0" and got:
Listening on LPF/wlan0/00:xx:xx:xx:xx:d5
Sending on LPF/wlan0/00:xx:xx:xx:xx:d5
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
I can't understand what the problem with DHCP is. Don't know if that will help anybody at all, but hey, it's more info, so why not.
I have posted here also, and offered guru a card to work on.
Static ip address did not seem to work either.
just for the record I have also tried the Netgear mimo pre-n Drivers which use the same chip, as they are slightly newer, like so
wnihdd50.sys 126.96.36.199 vs 188.8.131.52
wnihdd51.sys 184.108.40.206 vs 220.127.116.11
Thanks for the link, looks like we're not alone. Doesn't look like anybody's been able to get it to work yet either. Hopefully Airgo will make good on their promise to release an open source driver. If you ever do get it working or find out more, post it here, these threads turn up on google when people search, and so far this is the most helpful info on the subject I've found.
I have nothing to add to this except my complete attention. I've had Pre-N on my laptop and desktop, and they work great, just what I needed, except when I need to get online with Linux, in which case I hafta swap out my card and make do. Is that right, Airgo says they're going to release an open source driver?
I've temporarily abandoned trying to get this working, since I recently got a new laptop, but when I contacted Airgo they said they had plans to release an open source driver, but gave no specific date. However, D-Link has a USB adapter that supports 108 MBPS that is listed as working under ndiswrapper. From the wiki:
# Card: D-Link DWL-G132 Airplus XtremeG (word)
* Chipset: Atheros? double... H/W ver.:A2 F/W ver.:1.02
* Other: needs both athfmwdl.inf and NETA5AGU.inf to run.
* Chipset: Atheros
* Driver: neta5agu.inf 1.01.41 from D-Link's site. Need to compile utils/load_fw_ar5523 and use it to load firmware that ships w/ driver (ar5523.bin) before loading ndiswrapper.
* Other: Working w/ ndiswrapper-1.6rc1. Full step-by-step posted in forum .
* Other: With ndiswrapper version 1.7 (and later), load_fw_ar5523 is not used; instead, install both neta5agu and athfmwdl drivers. With that, ndiswrapper will load the firmware when necessary.
Awesome man! As soon as I get my desktop back up and running, I can finally run linux (I seem to have fried my board when I had to uninstall and re-install it like 6 times into my new case because the liquid cooling system that came with the case didn't work ). I still wonder if Airgo will ever release that driver they promised us. In the meantime, at least we have this!
this looks like excellent news, but I can't find the windows driver for the netgear WPNT511 !! I can only find the firmware posted to the Netgear web. Is the windows driver included in the firmware download? It looks as though the WPNT511 is a newer card than the date listed: 06/30/2005 . Do you have a link to the windows driver software file?
Why wouldn't we use the Belkin 8010 windows driver?
I'm pretty sure that the driver is in the firmware download. Netgear's always been like that, making things just a tad confusing. As I understand it, the Belkin drivers are a bit dodgy because they're some of the first of this pre-N generation to come out, and are just a bit buggy. I couldn't get the Belkin pre-N card to maintain a connection on my desktop, but have been doing fine with Linksys's drivers. I haven't had time to go back and attempt this hack (did once, failed), but I say give it a try with the Netgear gear, and tell us the results.
Finally got my pre-N card working on a Dell Dimension 5100. Thought I'd recap some of the issues I faced.
1) Discovery of the card: At first lscpi could see the CardBus Controller but not the Wireless card. This turned out to be an issue with PCI bus configuration of my machine. In a nutshell, the
Bus that the card was on could not be detected. The fix was to add
to the boot parameters of my kernel (easily done a boot using grub's interface, or via grub.conf permanently). This resulted in the following lspci:
2) I then made the mistake of loading the drivers that came with my card. the ndiswrapper doc warns against this (for good reason), but I did it anyway. Seems the Belkin supplied driver is, possibly, a tad old.
-r-xr-xr-x 1 ben ben 37943 Aug 13 2004 NetAni.inf
-r-xr-xr-x 1 ben ben 753664 Aug 13 2004 wnihdd51.sys
-r-xr-xr-x 1 ben ben 6838 Aug 13 2004 wni6000.bin
If you download the Netgear WPNT511 driver (the firmware download) you'd find the timestamp is newer (for what that's worth) and that the sizes are different:
-rw-r--r-- 1 root root 36496 Nov 10 21:35 NETANI.INF
-rw-r--r-- 1 root root 6426 Nov 10 21:35 wni6000.bin
-rw-r--r-- 1 root root 845312 Nov 10 21:35 WniHdd51.sys
After installing the Belkin version, I had a number of errors on loading, here's an example:
I followed the above notes and successfully configured my pre-N card with encryption, wep. The problem I'm having is the pci card interferes with the graphics display. My X desktop fails to come up.
I have 2 systems running Suse 10. One is a dfi lanparty ultra using a pci express graphics subsystem. The other is an Asus agp 8x graphics subsystem. The same thing happens with both systems.
They boot up successfully. However, instead of having the graphics login panel come up, I get a black text based login console. The pre-N pci card must be in conflict with the graphics subsystem. When I remove the card, the system comes up fine.
Also, the kernel parameter above, is it incorrectly spelled? pci=assign-busses.
I tried entering this command in the grub boot loader but it seemed to have no affect.
I'd be greatful if anyone could suggest a direction to pursue.