[Prism54-users] What could cause the this card not to respond?

[david]

On my pc (PCI) only one order of the "iwconfigs" runs ok. Any other order s=
ets=20
my card on 5.2Ghz, or null ssid, or AP  00:00:00:00:00:00.

This is my startup script:

MODE=3D"master"
ESSID=3D"Habitacion WIFI"
CHANNEL=3D6
IPADDR=3D"192.168.0.2"
IWCONFIG=3D"/usr/local/sbin/iwconfig"
MODPROBE=3D/sbin/modprobe
IFCONFIG=3D"/sbin/ifconfig"
IF2=3Deth1

$MODPROBE prism54
sleep 5
$IWCONFIG $IF2 mode $MODE
$IWCONFIG $IF2 essid "$ESSID"
$IWCONFIG $IF2 channel $CHANNEL


This is the ONLY order of settings wich works for me.


El Mi=E9rcoles, 12 de Noviembre de 2003 22:59, Klaas Jan Wierenga escribi=
=F3:
> Hi Ronald,
>
> I've got exactly the same laptop and the same problem. I'm currently
> attempting to get it to work on the 2.6.0-test9 kernel, but no result so
> far. I get exactly the same behaviour you're describing. Have you made
> any progress yet?
>
> Cheers,
> Klaas Jan Wierenga
>
> >>> Ronald <ronaldvandermeer@wanadoo.nl> 11/12/03 12:11 AM >>>
>
> Hi everyone,
>
> I'm trying to get the build-in miniPCI wireless device in my Medion
> MD40100 laptop to work.
>
> I tried several snapshot kernelpatches on the 2.4.23-pre9 kernel, all
> with the same result, dmesg shows:
>
> Loaded prism54 driver, version 1.0.2.2
> eth1: resetting device...
> eth1: uploading firmware...
> eth1: firmware upload & reset successful!
>
> and later on..
>
> eth1: prism54_mib_init()
> TRAP: oid 0xff020003, device 3, flags 0x0 length 4
> eth1: done with prism54_mib_init()!
>
> iwconfig shows:
>
> eth1      PRISM Duette  Mode:Auto  Frequency:5.2GHz
>           Access Point: 00:00:00:00:00:00  Bit Rate:0kb/s
> Sensitivity=3D20/0
>           Retry min limit:8   RTS thr:2347 B   Fragment thr:2346 B
>           Encryption key:off
>           Link Quality:0  Signal level:0  Noise level:216
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
> I can do the following with no errors and no extra dmesg output:
> iwconfig eth1 channel 6
> iwconfig eth1 essid myap
> iwconfig eth1 mode managed
>
> But the output of iwconfig won't change.
>
> lcpci -vvv -n shows  the following :
>
> 03:06.0 Class 0280: 1260:3890 (rev 01)
>         Subsystem: 17cf:0014
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
> ParErr- Stepping- SERR+ FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 80 (2500ns min, 7000ns max), cache line size 08
>         Interrupt: pin A routed to IRQ 11
>         Region 0: Memory at d2004000 (32-bit, non-prefetchable)
> [size=3D8K]
>         Capabilities: [dc] Power Management version 1
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=3D0mA
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=3D0 DScale=3D0 PME-
>
> I noticed the power management capabilities. Could it be that this
> device doesn't repond bacause it is in some sort of powersafe state by
> default? This behavior would make sense in environments that require
> little battery-power consumption, like in laptops.
>
> This laptop also has a wireless button and led, which are very simular
> to the buttons and leds found on some Acer laptops. In windows pushing
> this button turns on wireless and the led will turn on. Could this
> somehow be related to my problems?
>
> Needless to say I stuck here, so any suggestion are welcome.
>
> I'm also interested in other stories of experiences with simular miniPCI
> devices in laptops.
>
> Ronald
>
> _______________________________________________
> Prism54-users mailing list
> Prism54-users@prism54.org
> http://prism54.org/mailman/listinfo/prism54-users
>
> _______________________________________________
> Prism54-users mailing list
> Prism54-users@prism54.org
> http://prism54.org/mailman/listinfo/prism54-users