From what I've read whilst searching the net for solutions, the transmit timeout doesn't seem to be indicative of a failure of the card to find another one to talk to; it's something more serious. I guess it could be something to do with the IRQ error near the top, but I've tried using
Anyone here willing to help me debug some wireless networking?
The RJ45 dongle on the NIC in my laptop has finally stopped working
completely, which has given me a sufficent kick up the backside to try
to get the wireless cards I bought a few months ago working.
Anyway, here's my setup. The laptop is W95 (sorry, but it *is* my only
Windoze machine), and the other machine is running SuSE 8.0 Pro. This
is my first foray into wireless networking, so the problem could be at
either end (or more likely, both) - I don't have an existing wireless
network with which to test either machine. Cards are identical Sitecom
PCMCIA models; I believe they use the Prism II chipset. Linux machine
also has a PCI-PCMCIA adaptor, also by Sitecom.
I managed to install the drivers on the laptop, after the usual
pantomime of endless disk swaps, hand-holding and reboots, and it seems
to be reasonably happy. I can't tell that it's working, though, as
the diagnostic tool seems to want to minimise itself all the time, and
will never come back.
Anyway, onto the Linux machine.
I've already updated my pcmcia utilities as per the instructions in the
SuSE FAQ, but something still seems to be going wrong.
Here are the contents of my /var/log/messages, when I start up PCMCIA
services:
Jul 31 19:27:39 4ttgate rcpcmcia: /sbin/insmod /lib/modules/2.4.18-4GB/pcmcia-external/pcmcia_core.o
Jul 31 19:27:41 4ttgate kernel: Linux PCMCIA Card Services 3.1.31
Jul 31 19:27:41 4ttgate kernel: kernel build: 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002
Jul 31 19:27:41 4ttgate kernel: options: [pci] [cardbus] [apm]
Jul 31 19:27:42 4ttgate rcpcmcia: /sbin/insmod /lib/modules/2.4.18-4GB/pcmcia-external/pcmcia_core.o
Jul 31 19:27:42 4ttgate rcpcmcia: /sbin/insmod /lib/modules/2.4.18-4GB/pcmcia-external/i82365.o
Jul 31 19:27:42 4ttgate kernel: Intel ISA/PCI/CardBus PCIC probe:
Jul 31 19:27:42 4ttgate kernel: PCI: No IRQ known for interrupt pin A of device 00:11.0. Please try using pci=biosirq.
Jul 31 19:27:42 4ttgate kernel: Ricoh RL5C475 rev 80 PCI-to-CardBus at slot 00:11, mem 0x10000000
Jul 31 19:27:42 4ttgate kernel: host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat 168/176] [bus 2/5]
Jul 31 19:27:42 4ttgate kernel: ISA irqs (default) = 4,5,7,9,10,12 polling interval = 1000 ms
Jul 31 19:27:43 4ttgate rcpcmcia: /sbin/insmod /lib/modules/2.4.18-4GB/kernel/drivers/pcmcia/pcmcia_core.o
Jul 31 19:27:43 4ttgate rcpcmcia: /sbin/insmod /lib/modules/2.4.18-4GB/pcmcia-external/ds.o
Jul 31 19:27:44 4ttgate cardmgr[29127]: starting, version is 3.1.31
Jul 31 19:27:44 4ttgate cardmgr[29127]: modpath = /lib/modules/2.4.18-4GB/
Jul 31 19:27:44 4ttgate cardmgr[29127]: modsubdir = pcmcia-external
Jul 31 19:27:44 4ttgate cardmgr[29127]: watching 1 sockets
Jul 31 19:27:45 4ttgate cardmgr[29127]: socket 0: ZCOMAX AirRunner/XI-300
Jul 31 19:27:45 4ttgate kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Jul 31 19:27:45 4ttgate cardmgr[29127]: executing: 'insmod -v /lib/modules/2.4.18-4GB//pcmcia-external/hermes.o'
Jul 31 19:27:45 4ttgate kernel: hermes.c: 3 Oct 2001 David Gibson
On Thu, 1 Aug 2002, Dave Smith wrote:
network with which to test either machine. Cards are identical Sitecom PCMCIA models; I believe they use the Prism II chipset. Linux machine also has a PCI-PCMCIA adaptor, also by Sitecom.
/snip/
Jul 31 19:27:45 4ttgate cardmgr[29127]: socket 0: ZCOMAX AirRunner/XI-300 /snip/
I just installed a D-Link DCF-650W on my laptop (SuSE 8.0) with a slightly-hacked CF-PCMCIA adapter. I thought it strange that my card also identified itself to card services as a ZCOM XI-300. I got mine going when I switched from 'kernel' to 'external' PCMCIA support, and added the following to my /etc/pcmcia/config: card "D-Link DCF-650W" #card "Z-Com XI300 11Mb/s 802.11b WLAN Card" manfid 0xd601, 0x0002 bind "wvlan_cs" Try running `cardctl ident` and see what it tells you... I also edited /etc/dhclient.conf and changed 'initial-interval 2' to 'initial-interval 5' when I was failing on initial attempts to negotiate a DHCP IP address. Rick Green
On Thu, Aug 01, 2002 at 10:14:06PM -0400, rtg@mich.com wrote:
On Thu, 1 Aug 2002, Dave Smith wrote:
network with which to test either machine. Cards are identical Sitecom PCMCIA models; I believe they use the Prism II chipset. Linux machine also has a PCI-PCMCIA adaptor, also by Sitecom.
/snip/
Jul 31 19:27:45 4ttgate cardmgr[29127]: socket 0: ZCOMAX AirRunner/XI-300 /snip/
I just installed a D-Link DCF-650W on my laptop (SuSE 8.0) with a slightly-hacked CF-PCMCIA adapter.
I thought it strange that my card also identified itself to card services as a ZCOM XI-300.
I got mine going when I switched from 'kernel' to 'external' PCMCIA support,
Already done this. 'kernel' seems to fall over in an even bigger heap.
and added the following to my /etc/pcmcia/config:
card "D-Link DCF-650W" #card "Z-Com XI300 11Mb/s 802.11b WLAN Card" manfid 0xd601, 0x0002 bind "wvlan_cs"
Hmm, I had assumed that the "card" parameter was just a string to print for the user, and that the "bind" line was the important one. I didn't realise that the card parameter had significance.
Try running `cardctl ident` and see what it tells you...
Will do, when I get home. Thanks.
I also edited /etc/dhclient.conf and changed 'initial-interval 2' to 'initial-interval 5' when I was failing on initial attempts to negotiate a DHCP IP address.
I'm not worried about DHCP at the moment - I'm willing to use fixed IP, at least until I get something working... Thanks for the help. -- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England GPG Key: 0xF13192F2
On Thu, Aug 01, 2002 at 10:14:06PM -0400, rtg@mich.com wrote:
On Thu, 1 Aug 2002, Dave Smith wrote:
network with which to test either machine. Cards are identical Sitecom PCMCIA models; I believe they use the Prism II chipset. Linux machine also has a PCI-PCMCIA adaptor, also by Sitecom.
/snip/
Jul 31 19:27:45 4ttgate cardmgr[29127]: socket 0: ZCOMAX AirRunner/XI-300 /snip/
I just installed a D-Link DCF-650W on my laptop (SuSE 8.0) with a slightly-hacked CF-PCMCIA adapter.
I thought it strange that my card also identified itself to card services as a ZCOM XI-300.
I got mine going when I switched from 'kernel' to 'external' PCMCIA support, and added the following to my /etc/pcmcia/config:
card "D-Link DCF-650W" #card "Z-Com XI300 11Mb/s 802.11b WLAN Card" manfid 0xd601, 0x0002 bind "wvlan_cs"
Hmm, done that, and it's behaving itself a bit more, and when I restart PCMCIA card services, I get (edited): Aug 12 16:04:09 4ttgate kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 5, io 0x0100-0x013f Aug 12 16:04:09 4ttgate kernel: wvlan_cs: Registered netdevice eth2 Aug 12 16:04:09 4ttgate kernel: wvlan_cs: MAC address on eth2 is 00 60 b3 68 b2 34 Aug 12 16:04:09 4ttgate kernel: wvlan_cs: PrismII card, rev 0x8 Aug 12 16:04:09 4ttgate kernel: wvlan_cs: Found firmware 0x8 (vendor 3) - Firmware capabilities : 1-0-0-0-1 Aug 12 16:04:09 4ttgate cardmgr[30332]: + ./network: /var/run/hotplug/net-eth2: No such file or directory Aug 12 16:04:10 4ttgate ifup: No configuration found for eth-pcmcia-0 eth2 However, on trying to configure the card with ifconfig, it seems to run OK, but in /var/log/messages: Aug 12 16:06:11 4ttgate kernel: NETDEV WATCHDOG: eth2: transmit timed out Aug 12 16:06:11 4ttgate kernel: wvlan_cs: eth2 Tx timed out! Resetting card Aug 12 16:06:11 4ttgate kernel: wvlan_cs: MAC address on eth2 is 00 60 b3 68 b2 34 Aug 12 16:06:11 4ttgate kernel: wvlan_cs: PrismII card, rev 0x8 Aug 12 16:06:11 4ttgate kernel: wvlan_cs: Found firmware 0x8 (vendor 3) - Firmware capabilities : 1-0-0-0-1 Aug 12 16:06:14 4ttgate kernel: eth2: no IPv6 routers present Repeated ad infinitum. Anyone any ideas? TIA...
participants (3)
-
Dave Smith -
David Smith -
Rick Green