[Prism54-users] Re: Prism54-users digest, Vol 1 #93 - 11 msgs

[Jens Maurer]

Peter Leinen wrote:
> 	iwconfig eth1 essid "XXX" channel 10 ap "00:0D:54:9C:8C:56" commit 
> iwevent show somthing like
> 	eth1	ESSID:"XXX"
> 	eth1	Channel:10
> 	eth1	Mode:Managed

Those are the messages TO the device.
You should see something like this in the kernel log

Jan  6 01:02:03 localhost kernel: TRAP: oid 0x18000001, device 3, flags 0x0 length 12
Jan  6 01:02:03 localhost kernel: TRAP: oid 0x18000003, device 3, flags 0x0 length 12
Jan  6 01:02:03 localhost kernel: TRAP: oid 0x1, device 3, flags 0x0 length 4

when the link to an AP has been established.

>         pe kernel: Loaded prism54 driver, version 1.0.2.2

Ok so far.

>         pe kernel: divert: allocating divert_blk for eth1

That's fishy, I don't get this.  The message comes from net/core/dv.c
in 2.4.23.  Ah, with this, you can somehow "grab" packets not meant for
you (on the Ethernet level).

>         pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x17000
[...]

Hm... Someone wants to get information from the device, and it appears to fail
(it gets only 1 byte when 4 are expected).
(The oid=... values are truncated. Can we see the full log, please?)

>         pe kernel: eth1: islpci_open()

And there is the "ifconfig eth1 up".

Could you please reboot (if it's a CardBus card, the card NOT inserted),
then insert the card into the slot, then do
     cardctl insert
     ifconfig eth1 up
     iwconfig eth1 essid XXX
     (wait 5 sec)
     iwconfig     (without arguments, should show the AP address)

And NOTHING else (no "commit", no "channel", no "ap" ID)?
Your syslog should show the lspci_open() BEFORE all the
_mgt_get_request() stuff, if any, otherwise *something* else
is issuing requests to the card.

Jens Maurer