[Prism54-devel] problems with iwlist scan

[Brian Bothwell]

--Signature=_Thu__18_Dec_2003_16_18_32_-0800_67EESI7aBhSicguu
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Try: iwlist eth0 scanning

On Thu, 18 Dec 2003 20:40:54 +0100
frank-prism54@mattzz.dyndns.org wrote:

> Hello,
> 
> I would like to report some problems with the latest cvs version of
> the driver. I did not have these problems with a driver from end
> november.
> 
> I hope that I have included the relevant information and did not add
> too much unneeded messages. If you need more info please say so.
> 
> 
> I am using:
> 
> A SMC2802W PCI card. I think this is the relevant output of lspci -nv
> 
> 
> 00:0a.0 Class 0280: 1260:3890 (rev 01)
>         Subsystem: 10b8:2802
> 
> 
> 
> # uname -a
> Linux fantasio 2.4.23-rc3 #8 SMP Fri Dec 12 09:54:58 CET 2003 i686 GNU/Linux
> 
> iwlist --version
> iwlist    Version 26
>           Compatible with Wireless Extension v16 or earlier,
>           Currently compiled with Wireless Extension v16.
> 
> Kernel    Currently compiled with Wireless Extension v16.
> 
> eth1      Driver has no Wireless Extension version information.
> 
> ----------------------------------------------------------------------
> Using the driver you get with cvs co -D 2003-11-26 prism54-ng
> 
> $ rmmod prism54
> $ modprobe prism54
> $ ifconfig eth1 up
> $ iwlist eth1 scan
> 
> I see:
> 
> eth1      Scan completed :
>           Cell 01 - Address: 00:04:E2:98:AD:9A
>                     ESSID:"`"
>                     Mode:Master
>                     Encryption key:on
>                     Frequency:2.417GHz
>                     Quality:148/0  Signal level:-46 dBm  Noise level:-194 dBm
> 
> 
> I am able to ping the access point and to configure it via
> http. Everything seems to be ok.
> 
> and the kernel log says:
> 
> Dkernel: Loaded prism54 driver, version 1.0.2.2
> Dkernel: PCI: Enabling device 00:0a.0 (0000 -> 0002)
> Dkernel: eth1: loading firmware early at probe time as temporary workaround for broken device driver
> Dkernel: eth1: uploading firmware...
> Dkernel: eth1: firmware uploaded done, now triggering reset...
> Dkernel: eth1: prism54_mib_init()
> Dkernel: eth1: done with prism54_mib_init()!
> Dkernel: TRAP: oid 0x18000001, device 8, flags 0x0 length 12
> ..
> Dkernel: TRAP: oid 0x18000003, device 8, flags 0x0 length 12
> Dkernel: eth1: islpci_open()
> Dkernel: eth1: resetting device...
> Dkernel: eth1: uploading firmware...
> Dkernel: eth1: firmware uploaded done, now triggering reset...
> Dkernel: eth1: prism54_mib_init()
> Dkernel: eth1: done with prism54_mib_init()!
> Dkernel: TRAP: oid 0x18000001, device 8, flags 0x0 length 12
> ..
> Dkernel: TRAP: oid 0x18000003, device 8, flags 0x0 length 12
> Dkernel: _mgt_get_request(): data length (64!=1452) mismatch for oid=0x1c000043
> Dkernel: TRAP: oid 0x18000001, device 8, flags 0x0 length 12
> 
> 
> ----------------------------------------------------------------------
> 
> Using the cvs version from 18 december the behaviour is the following:
> 
> 
> $ rmmod prism54
> $ modprobe prism54
> $ ifconfig eth1 up
> $ iwlist eth1 scan
> eth1      Failed to read scan data : Invalid argument
> 
> 
> I was not able to connect to my access point afterwards.
> 
> 
> The kernel log says:
> 
> Dec 18 20:19:32 fantasio kernel: Loaded prism54 driver, version 1.0.2.2
> Dec 18 20:19:32 fantasio kernel: PCI: Enabling device 00:0a.0 (0000 -> 0002)
> Dec 18 20:19:32 fantasio kernel: eth1: islpci_open()
> Dec 18 20:19:32 fantasio kernel: eth1: resetting device...
> Dec 18 20:19:32 fantasio kernel: eth1: uploading firmware...
> Dec 18 20:19:32 fantasio kernel: eth1: firmware uploaded done, now triggering reset...
> 
> ----------------------------------------------------------------------
> 
> Do you have an idea what is wrong here?
> 
> 
> best regards
>   Frank
> 
>  
> _______________________________________________
> Prism54-devel mailing list
> Prism54-devel@prism54.org
> http://prism54.org/mailman/listinfo/prism54-devel
> 

--Signature=_Thu__18_Dec_2003_16_18_32_-0800_67EESI7aBhSicguu
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/4kPbXFoaje2SLvERAljHAJ4t7uL+LDS7p67ZpNJo215JdBKT/ACdEnbY
504266uivrUdghPjUWIZh+Q=
=ZgVr
-----END PGP SIGNATURE-----

--Signature=_Thu__18_Dec_2003_16_18_32_-0800_67EESI7aBhSicguu--