One of my computers, currently connected to the network by cable, may have to be moved to another room where connecting by cable is not practical. I do have a wireless access point so can anyone recommend a PCI wireless network card that will work with Linux (Debian Etch/Testing) without a lot of messing about. I don't want to use the software, the name escapes me, that uses Windows drivers as I've had problems using that in the past. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
On Fri, 11 Aug 2006, Barry Samuels wrote:
One of my computers, currently connected to the network by cable, may have to be moved to another room where connecting by cable is not practical.
I do have a wireless access point so can anyone recommend a PCI wireless network card that will work with Linux (Debian Etch/Testing) without a lot of messing about.
I don't want to use the software, the name escapes me, that uses Windows drivers as I've had problems using that in the past.
Atheros based cards work well. You'll need to install the madwifi-ng drivers for it. emerge madwifi-ng on Gentoo :-) For a list of cards with this chipset see here http://customerproducts.atheros.com/customerproducts/ HTH Chris -- Chris ---------------------------------- E Mail: chris@glovercc.plus.com SIP: 84411389@voiptalk.org IAXTEL: 17003366726
On Fri, 2006-08-11 at 17:08 +0100, Barry Samuels wrote:
I do have a wireless access point so can anyone recommend a PCI wireless network card that will work with Linux (Debian Etch/Testing) without a lot of messing about.
One of my old machines had a Netgear WG311 v2 which just worked, in fact Ubuntu detected it during installation and prompted for keys etc. Sorry not sure what chipset as that machine has gone now.
I don't want to use the software, the name escapes me, that uses Windows drivers as I've had problems using that in the past.
ndiswrapper ? Yes good plan, ndiswrapper is handy when you already have the wrong hardware and for whatever reason can't/won't change it. But if you are purchasing new hardware then going for stuff that is compatible with native drivers is a far better plan.
On 11/08/06 22:32:23, Chris Glover wrote:
Atheros based cards work well. You'll need to install the madwifi-ng drivers for it. emerge madwifi-ng on Gentoo :-)
For a list of cards with this chipset see here http://customerproducts.atheros.com/customerproducts/
It doesn't give me much confidence when they list the Netgear WG311 which according to the Atheros compatability list now doesn't work because the chip has been changed. On 11/08/06 22:32:23, Wayne Stallwood wrote:
One of my old machines had a Netgear WG311 v2 which just worked, in fact Ubuntu detected it during installation and prompted for keys etc.
See above
I don't want to use the software, the name escapes me, that uses Windows drivers as I've had problems using that in the past.
ndiswrapper ?
Yes it was ndsiwrapper. I've downloaded and compiled the madwifi-ng source and while everything seemed to go swimmingly depmod -a produces a 'Unresolved symbols in /lib/modules/2.4.27/net/wlan.o'. I've tried loading the modules, although I don't have a wireless card yet, and they fail to load possibly because of the above. Any helpful hints? Many thanks for the help so far. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
On Sat, 12 Aug 2006, Barry Samuels wrote:
On 11/08/06 22:32:23, Chris Glover wrote:
Atheros based cards work well. You'll need to install the madwifi-ng drivers for it. emerge madwifi-ng on Gentoo :-)
For a list of cards with this chipset see here http://customerproducts.atheros.com/customerproducts/
It doesn't give me much confidence when they list the Netgear WG311 which according to the Atheros compatability list now doesn't work because the chip has been changed.
I've got a WG511T which works perfectly, don't know about the 311, never sued one. Sorry.
ndiswrapper ?
Yes it was ndsiwrapper.
I've downloaded and compiled the madwifi-ng source and while everything seemed to go swimmingly depmod -a produces a 'Unresolved symbols in /lib/modules/2.4.27/net/wlan.o'.
I've tried loading the modules, although I don't have a wireless card yet, and they fail to load possibly because of the above.
Why are you using such an ancient kernel? Try building against a 2.6 kernel. Chris -- Chris ---------------------------------- E Mail: chris@glovercc.plus.com SIP: 84411389@voiptalk.org IAXTEL: 17003366726
Hi Barry On Saturday 12 August 2006 15:01, Barry Samuels wrote:
I've downloaded and compiled the madwifi-ng source and while everything seemed to go swimmingly depmod -a produces a 'Unresolved symbols in /lib/modules/2.4.27/net/wlan.o'.
A list of unresolved symbols would help in diagnosing the problem.... You could try loading aes first although it should be loaded automatically when using `modprobe ath_pci` Regards, Paul.
On 12/08/06 15:41:03, Paul wrote:
Hi Barry
On Saturday 12 August 2006 15:01, Barry Samuels wrote:
I've downloaded and compiled the madwifi-ng source and while everything seemed to go swimmingly depmod -a produces a 'Unresolved symbols in /lib/modules/2.4.27/net/wlan.o'.
A list of unresolved symbols would help in diagnosing the problem....
depmod: *** Unresolved symbols in /lib/modules/2.4.27/net/wlan.o depmod: wireless_send_event
You could try loading aes first although it should be loaded automatically when using `modprobe ath_pci`
I don't have an aes module just ath_something or wlan_something -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Hi Barry On Saturday 12 August 2006 16:39, Barry Samuels wrote:
depmod: *** Unresolved symbols in /lib/modules/2.4.27/net/wlan.o depmod: wireless_send_event
OK - In a 2.4.27 kernel, this symbol is found in wireless.c and exported via netsyms.c - But only if CONFIG_NET_RADIO or CONFIG_NET_PCMCIA_RADIO is defined in the kernel config. Check to see if either of these (along with CONFIG_NET_WIRELESS) are enabled. Regards, Paul.
On 12/08/06 17:52:25, Paul wrote:
Hi Barry
On Saturday 12 August 2006 16:39, Barry Samuels wrote:
depmod: *** Unresolved symbols in /lib/modules/2.4.27/net/wlan.o depmod: wireless_send_event
OK - In a 2.4.27 kernel, this symbol is found in wireless.c and exported via netsyms.c - But only if CONFIG_NET_RADIO or CONFIG_NET_PCMCIA_RADIO is
defined in the kernel config. Check to see if either of these (along with CONFIG_NET_WIRELESS) are enabled.
Regards, Paul.
I would love to be able to say that one or the other was not enabled as that may have been a quick fix but both are enabled. # Wireless LAN (non-hamradio) # CONFIG_NET_RADIO=y # CONFIG_STRIP is not set # CONFIG_WAVELAN is not set # CONFIG_ARLAN is not set # CONFIG_AIRONET4500 is not set # CONFIG_AIRO is not set # CONFIG_HERMES is not set CONFIG_NET_WIRELESS=y -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Hi Barry On Saturday 12 August 2006 20:32, Barry Samuels wrote:
I would love to be able to say that one or the other was not enabled as that may have been a quick fix but both are enabled.
CONFIG_NET_RADIO=y CONFIG_NET_WIRELESS=y
OK - That should mean wireless_send_event is compiled in.. Try `grep wireless_send_event /proc/ksyms` - It *should* report back an address in memory where the function is located. Not that this will help in loading the madwifi driver. In the end I suspect your only real answer is to grab the latest kernel sources and build your own using the 2.4.33 tarball. Regards, Paul.
On 12/08/06 21:53:25, Paul wrote:
Hi Barry
On Saturday 12 August 2006 20:32, Barry Samuels wrote:
I would love to be able to say that one or the other was not enabled as that may have been a quick fix but both are enabled.
CONFIG_NET_RADIO=y CONFIG_NET_WIRELESS=y
OK - That should mean wireless_send_event is compiled in.. Try `grep wireless_send_event /proc/ksyms` - It *should* report back an address in memory where the function is located.
grep wireless_send_event /proc/ksyms gives: c01e2560 wireless_send_event_R__ver_wireless_send_event
Not that this will help in loading the madwifi driver. In the end I suspect your only real answer is to grab the latest kernel sources and build your own using the 2.4.33 tarball.
Regards, Paul.
-- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
On Sat, 2006-08-12 at 15:01 +0100, Barry Samuels wrote:
It doesn't give me much confidence when they list the Netgear WG311 which according to the Atheros compatability list now doesn't work because the chip has been changed.
Ahh That happens sometimes, it's a right pain too. Netgear at least seem to now change the version number when they do that (in the past there have been plenty of D-Link and Netgear products that have changed chipset without there being any external indication) In that case it is probably best to work backwards from the compatibility list and find a card where the current version is Atheros, the chances of finding a WG311 v2 when a v3 has been out for some time may be quite slim.
On 12/08/06 15:13:43, Chris Glover wrote:
It doesn't give me much confidence when they list the Netgear WG311 which according to the Atheros compatability list now doesn't work because the chip has been changed.
I've got a WG511T which works perfectly, don't know about the 311, never sued one. Sorry.
Yes but that isn't PCI is it? Cardbus I believe.
I've downloaded and compiled the madwifi-ng source and while everything seemed to go swimmingly depmod -a produces a 'Unresolved symbols in /lib/modules/2.4.27/net/wlan.o'.
I've tried loading the modules, although I don't have a wireless card yet, and they fail to load possibly because of the above.
Why are you using such an ancient kernel? Try building against a 2.6 kernel.
Chris
Because if I use a 2.6 kernel I have to sit and wait for around 5 minutes before my machine starts to boot. It doesn't do that with a 2.4. Some time ago I saw a number of people report the same problem but never saw a remedy. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
On Sat, 12 Aug 2006, Barry Samuels wrote:
On 12/08/06 15:13:43, Chris Glover wrote:
It doesn't give me much confidence when they list the Netgear WG311 which according to the Atheros compatability list now doesn't work because the chip has been changed.
I've got a WG511T which works perfectly, don't know about the 311, never sued one. Sorry.
Yes but that isn't PCI is it? Cardbus I believe.
You're right, it is Cardbus... which is PCI in a PCMCIA slot, so technically it's PCI :-)
Why are you using such an ancient kernel? Try building against a 2.6 kernel.
Because if I use a 2.6 kernel I have to sit and wait for around 5 minutes before my machine starts to boot. It doesn't do that with a 2.4.
Some time ago I saw a number of people report the same problem but never saw a remedy.
I've never heard of this problem before. I'm using 2.6.17.7 on my machines with no problems. Good luck in your hunt for an Atheros based card Chris -- Chris ---------------------------------- E Mail: chris@glovercc.plus.com SIP: 84411389@voiptalk.org IAXTEL: 17003366726
I downloaded the source for 2.4.33 as Paul suggested, compiled and installed and the 'unresolved symbol' error message has gone away. The wlan module now loads - hooray. End of part 1. Now the difficult bit - I've got to get a card that works with the Atheros drivers. The Atheros site lists this as one of two: AirPlus Xtreme G 108Mbps PCI Adapter DWL-G520 PCI 802.11b/g AR5002G Super G This is available at the moment for only £20.00 plus carriage at http://www.pixmania.co.uk/uk/uk/92365/art/d-link/dwl-g520-pci-wireless-net.h... The picture on this site matches the label shown on the D-Link site shown as DWL-G520 Revision B Does anyone have any experience of these? Atheros doesn't mention any revisions so does the Rev. B still have an Atheros chipset? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Does anyone have any experience of these? Atheros doesn't mention any revisions so does the Rev. B still have an Atheros chipset?
To be honest it doesn't look good, if you look on D-Link's site there are revision A and B's listed. Both these have completely different driver packages and versions and therefore I assume they are different chipsets.
On 14/08/06 20:28:03, Wayne Stallwood wrote:
Does anyone have any experience of these? Atheros doesn't mention any revisions so does the Rev. B still have an Atheros chipset?
To be honest it doesn't look good, if you look on D-Link's site there are revision A and B's listed. Both these have completely different driver packages and versions and therefore I assume they are different chipsets.
After a lot of searching on the Internet it seems to be the consensus that the D-Link Revision B is the one with the Atheros chipset. There's only one way to find out so I've ordered two. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
participants (4)
-
Barry Samuels -
Chris Glover -
Paul -
Wayne Stallwood