orinoco_plx 0.08a - no IRQs

[Ulf Buermeyer]

Dear list-subscribers,

i'm using orinoco-0.08a on a Netgear NA301/401, thus with the
orinoco_plx module. The latter finally found the NA301 PCI adaptor after
some nights of typing - I "just" had to compile it with the PCI id from
lspci and cat /proc/pci at the end of orinoco_plx.c. Now all the
initialisation seems to work fine:

Nov  3 12:00:07 bubu kernel: hermes.c: 3 Oct 2001 David Gibson
<hermes at gibson.dropbear.id.au>
Nov  3 12:00:30 bubu kernel: orinoco.c 0.08a (David Gibson
<hermes at gibson.dropbear.id.au> and others
Nov  3 12:04:42 bubu kernel: PCI: Assigned IRQ 9 for device 00:0c.0
Nov  3 12:04:42 bubu kernel: Detected Orinoco/Prism2 PCI device at
00:0c.0, mem:0xc58f1000, irq:9, i
Nov  3 12:04:42 bubu kernel: eth1: Station identity 001f:0003:0000:0008
Nov  3 12:04:42 bubu kernel: eth1: Looks like an Intersil firmware
version 0.08
Nov  3 12:04:42 bubu kernel: eth1: Ad-hoc demo mode supported.
Nov  3 12:04:42 bubu kernel: eth1: IEEE standard IBSS ad-hoc mode
supported.
Nov  3 12:04:42 bubu kernel: eth1: WEP supported, "128"-bit key.
Nov  3 12:04:42 bubu kernel: eth1: MAC address 00:30:AB:0B:83:BE
Nov  3 12:04:42 bubu kernel: eth1: Station name "Prism  I"
Nov  3 12:04:42 bubu kernel: eth1: ready

# iwconfig eth1 (after some manual initialisation)

eth1      IEEE 802.11-DS  ESSID:"rauscher"  Nickname:"rauscher"
          Mode:Ad-Hoc  Frequency:2.422GHz  Cell: 00:00:00:00:00:00
          Bit Rate:2Mb/s   Tx-Power=15 dBm   Sensitivity:1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  invalid crypt:0  invalid misc:0


# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:30:AB:0B:83:BE  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::230:abff:fe0b:83be/10 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:74 dropped:0 overruns:0 carrier:0
          collisions:0 
          RX bytes:0 (0.0 b)  TX bytes:15079 (14.7 Kb)


# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) from 192.168.1.1 : 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=7.168 msec
64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=300 usec
64 bytes from 192.168.1.1: icmp_seq=3 ttl=255 time=296 usec
64 bytes from 192.168.1.1: icmp_seq=4 ttl=255 time=294 usec
64 bytes from 192.168.1.1: icmp_seq=5 ttl=255 time=298 usec


So far - so fine, but what didn't work is setting up a communication
frequency:

# iwconfig eth1 channel 2

seems to work, but there is no change in the *output* from iwconfig.

No communication is possible over the air, no frames are received:

# cat /proc/net/wireless 
Inter-| sta-|   Quality        |   Discarded packets
 face | tus | link level noise |  nwid  crypt   misc
  eth1: 0000    0     0     0        0      0      0


IRQ statistics are discouraging:

# cat /proc/interrupts 
  9:          0          XT-PIC  eth1

thus a big fat zero. Syslog shows how the driver is suffering:

Nov  3 13:16:30 bubu kernel: eth1: Error -110 setting multicast list.
Nov  3 13:16:30 bubu last message repeated 3 times
Nov  3 13:16:32 bubu kernel: NETDEV WATCHDOG: eth1: transmit timed out
Nov  3 13:16:32 bubu kernel: eth1: Tx timeout! Resetting card.
Nov  3 13:16:32 bubu kernel: eth1: Error -110 writing packet header to
BAP<3>eth1:Error -110 writing packet header to BAP
Nov  3 13:16:34 bubu kernel: NETDEV WATCHDOG: eth1: transmit timed out
Nov  3 13:16:34 bubu kernel: eth1: Tx timeout! Resetting card.
Nov  3 13:16:36 bubu kernel: eth1: Error -110 writing packet header to
BAP
Nov  3 13:16:36 bubu last message repeated 4 times
Nov  3 13:16:37 bubu kernel: NETDEV WATCHDOG: eth1: transmit timed out
Nov  3 13:16:37 bubu kernel: eth1: Tx timeout! Resetting card.
Nov  3 13:16:40 bubu kernel: NETDEV WATCHDOG: eth1: transmit timed out
Nov  3 13:16:40 bubu kernel: eth1: Tx timeout! Resetting card.

and so on.

It seems to me like there is a IRQ problem - but how can I get IRQs to
the driver? PCI IRQ assignment during boot is as follows:

# dmesg | grep PCI
PCI: Assigned IRQ 9 for device 00:0c.0

I'd greatly appreciate any ideas !

THNX in advance,

Ulf.

P.S. using the linux-wlan-ng driver symptoms are the same - all seems to
work but no IRQs and no communication :-/