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

[Peter Leinen]

On Mon, Jan 05, 2004 at 03:52:49PM -0700, jim feldman wrote:
> Do you know what version of the wireless tools you're using?
I was using wireless-tools version 26.1 and upgraded to version 26.2.
Compilation was done using wireless version 16.

> 
> You're saying "iwconfig eth1 freq 2.457 essid xxx mode Master" commit" 
> won't set the card? odd....
mode Master or managed?

> 
> In other windows, run iwevent and also "dmesg|tail -f" when you first
> install the card and then also when you use iwconfig to set the card. 
> Maybe the kernel modules will tell us more and when they load.  The fact
> that you can do a scan is hopeful
if I execute
	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

but nothing about any AP !?

dmesg will be silent at all. iThe output from syslog is
        pe kernel: Linux Kernel Card Services 3.1.22
        pe kernel:   options:  [pci] [cardbus] [pm]
        pe kernel: PCI: Found IRQ 11 for device 00:0a.0
        pe kernel: PCI: Sharing IRQ 11 with 00:02.0
        pe kernel: Yenta IRQ list 0698, PCI irq11
        pe kernel: Socket status: 30000820
        pe kernel: cs: cb_alloc(bus 2): vendor 0x10b7, device 0x6001
        pe kernel: PCI: Enabling device 02:00.0 (0000 -> 0002)
        pe pci.agent[5517]: /lib/modules/2.4.22-1.2115.nptl/modules.pcimap
        pe cardmgr[5519]: starting, version is 3.1.31
        pe cardmgr[5519]: watching 1 sockets
        pe cardmgr[5519]: Card Services release does not match
        pe kernel: cs: IO port probe 0x0c00-0x0cff: clean.
        pe kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x398-0x39f 0x4d0-0x
        pe kernel: cs: IO port probe 0x0a00-0x0aff: clean.
        pe cardmgr[5519]: socket 0: CardBus hotplug device
        pe pci.agent[5517]: PCI slot 02:00.0
        pe kernel: Loaded prism54 driver, version 1.0.2.2
        pe kernel: divert: allocating divert_blk for eth1
        pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x17000
        pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x17000
        pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x12000
        pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x12000
        pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x12000
        pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x12000
        pe kernel: _mgt_get_request(): data length (1!=34) mismatch for oid=0x1200
        pe kernel: _mgt_get_request(): data length (1!=34) mismatch for oid=0x1000
        pe kernel: _mgt_get_request(): data length (1!=6) mismatch for oid=0x10000
        pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x13000
        pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x13000
        pe kernel: _mgt_get_request(): data length (1!=4) mismatch for oid=0x13000
        pe kernel: eth1: islpci_open()
        pe devlabel: devlabel service started/restarted
        pe kernel: eth1: resetting device...
        pe kernel: eth1: uploading firmware...
        pe kernel: firmware_class.c:call_helper: firmware: /sbin/hotplug firmware
        pe kernel: eth1: firmware uploaded done, now triggering reset...
        pe kernel: eth1: prism54_mib_init()

> 
> I know it's frustrating.  It took me a week to get mine working and
> iwevent or the driver was lying to me about authentication. 
> 

Regards
  Peter