Re: Troubleshooting 802.11b wireless
On Wed, 2004-03-10 at 00:48, Joe Carey wrote:
> It's the wrong driver. You're using the driver for an
> Agere/Proxim/Orinoco card, i.e. "Hermes" on a card built with the
> Prism2.5 chipset. You probably want the linux-wlan-ng drivers.
>
> Check these links:
> http://packages.debian.org/testing/admin/linux-wlan-ng
> http://www.linux-wlan.com/linux-wlan/
>
> Have fun!
>
> joe
That doesn't quite make sense to me. If the driver is wrong than why
does it report that it detected an "Orinoco/Prism2 PCI device" and then
gets information from it like the MAC address and firmware revision?
This fellow http://members.iinet.net.au/~mtriggs/wireless.html got his
card to work with the orinoco_pci driver.
Unfortunately, the latest release of linux-wlan-ng doesn't work with
2.6, although that support is coming down the pipe in the next release
according to the CHANGELOG at linux-wlan.com. I attempted to build the
module from their source tree for 0.2.1-pre20, but it expects a file
[kernel-source-root]/.tmp_versions to be present, which is not shipped
with kernel-headers-2.6.3-1-686 (or its dependency). So, without
actually building my own kernel, what would it take to get a kernel
source tree that matched the one used to build the stock Debian kernel
verbatim?
Thanks,
Jonathan Brandmeyer
> Jonathan Brandmeyer wrote:
>
> >I'm trying to get a brand new Prism 2.5 based 802.11b wireless ethernet
> >card to work with Linux 2.6.3 (Netgear MA311) on Sid.
> >
> >The wireless-tools package installed.
> >
> >When I insert the required drivers into the kernel (orinoco_pci,
> >orinoco, and hermes), I get these messages:
> >
> >orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
> >orinoco_pci.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> & Jean
> >Tourrilhes <jt@hpl.hp.com>)
> >PCI: Found IRQ 11 for device 0000:02:0b.0
> >Detected Orinoco/Prism2 PCI device at 0000:02:0b.0, mem:0xF47FF000 to
> >0xF47FFFFF -> 0xe080d000, irq:11
> >Reset done..<7>orinoco_lock() called with hw_unavailable (dev=d2f03800)
> >.............<7>orinoco_lock() called with hw_unavailable (dev=d2f03800)
> >(repeated 17 more times)
> >
> >Clear Reset.....<7>orinoco_lock() called with hw_unavailable
> >(dev=d2f03800)
> >.............<7>orinoco_lock() called with hw_unavailable (dev=d2f03800)
> >(repeated 20-something more times)
> >.;
> >pci_cor : reg = 0x0 - 75286D9 - 75284E5
> >orinoco_lock() called with hw_unavailable (dev=d2f03800)
> >(repeated 13 more times)
> >
> >eth1: Station identity 001f:0006:0001:0003
> >eth1: Looks like an Intersil firmware version 1.3.6
> >eth1: Ad-hoc demo mode supported
> >eth1: IEEE standard IBSS ad-hoc mode supported
> >eth1: WEP supported, 104-bit key
> >eth1: MAC address 00:09:5B:67:95:0D
> >eth1: Station name "Prism I"
> >orinoco_lock() called with hw_unavailable (dev=d2f03800)
> >eth1: ready
> >
> >
> >With /etc/network/interfaces set up thus:
> >iface eth1 inet dhcp
> >name Wireless Ethernet LAN Card
> > wireless_essid 203cfr
> > wireless_mode managed
> > wireless_channel 6
> > wireless_ap auto
> >
> >ifup eth1 gives me this output:
> >Error for wireless request "Set Frequency" (8B04) :
> > SET failed on device eth1 ; Operation not supported.
> >Internet Software Consortium DHCP Client 2.0pl5
> >Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
> >All rights reserved.
> >
> >Please contribute if you find this software useful.
> >For info, please visit http://www.isc.org/dhcp-contrib.html
> >
> >sit0: unknown hardware address type 776
> >sit0: unknown hardware address type 776
> >Listening on LPF/eth1/00:09:5b:67:95:0d
> >Sending on LPF/eth1/00:09:5b:67:95:0d
> >Sending on Socket/fallback/fallback-net
> >DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
> >
> >DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
> >DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
> >DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19
> >DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
> >No DHCPOFFERS received.
> >No working leases in persistent database.
> >
> >Sleeping.
> >
> >After rebooting and trying again, I got several of this error instead:
> >hermes @ MEM 0xe090a000: Error -16 issuing command.
> >hermes @ MEM 0xe090a000: Error -16 issuing command.
> >hermes @ MEM 0xe090a000: Error -16 issuing command.
> >which repeated until I ran `modprobe -r orinoco_pci`
> >
> >So, can anyone help me debug this problem? The card works fine under
> >Windows XP on the same machine.
> >
> >Thanks,
> >Jonathan Brandmeyer
> >
> >
> >
> >
>
>
Reply to: