[MLB-WIRELESS] Kernel panic

[Toliman]

At 08:55 PM 8/08/2002, sanbar wrote:
>Ey all,
>I have a WL200 running under Linux. It fires up okay, and I can raise set
>the card in full Master mode, but after a short while it suffers from a
>kernel panic, seemingly at random. I no understand.
>Output from uname, iwconfig and dmesg is after the sig. Apologies for the
>size of this message, but it's relevant to wireless. OS is Red Hat 7.3.
>Please snip before you reply :/

ahh redhat. i promise nothing ... but advice.

>[root at wlan root]# iwconfig wlan0
>Warning : Device wlan0 has been compiled with version 12
>of Wireless Extension, while we are using version 11.
>Some things may be broken...

unpack the kernel into /usr/src/linux, and install pcmcia-cs-3.2.0 and 
patch/install over with orinoco-0.12b.tar.gz from source, or from whatever 
distribution package you have. i.e. thats the latest version for me, pick 
the latest version of pcmcia-cs for your distribution..  (the order to 
install, versions & incompatibilities of all the various wavelan / orinoco 
drivers is one of those 'linux' things you get used to)

then
cp /usr/src/linux/include/linux/wireless.h /usr/include/linux

to get rid of the "device has been compiled with version ..." error. you 
will also need to recompile the wireless-tools package to get rid of the 
above message. wireless extensions v14 comes with a few new devices and 
behaviours, your problems might be solved or made worse.

>hostap_cs: hostap_cs.c 0.0.0 2002-05-19 (SSH Communications Security Corp,
>Jouni Malinen)
>hostap_cs: (c) SSH Communications Security Corp <jkm at ssh.com>
>hostap_cs: setting Vcc=33 (constant)
>hostap_cs: CS_EVENT_CARD_INSERTION
>prism2_config()
>hostap_cs: setting Vcc=33 (from config)
>CISTPL_MANFID: 0x0138, 0x0002
>Checking CFTABLE_ENTRY 0x01 (default 0x01)
>Config has no IRQ info, but trying to enable IRQ anyway..
>IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
>io->flags = 0x0046, io.base=0x0000, len=64
>cs: IO port probe 0x0100-0x04ff: excluding 0x3c0-0x3df
>cs: IO port probe 0x03e0-0x04ff: clean.
>cs: IO port probe 0x0a00-0x0aff: clean.
>cs: IO port probe 0x0c00-0x0cff: clean.
>hostap_cs: index 0x01: Vcc 3.3, irq 11, io 0x0100-0x013f
>hostap_cs: Registered netdevice wlan0
>prism2_hw_init()
>prism2_hw_config: initialized in 9449 iterations
>wlan0: NIC: id=0x8002 v1.0.1
>wlan0: PRI: id=0x15 v0.3.0
>wlan0: STA: id=0x1f v0.8.0
>Using data::nullfunc ACK workaround - firmware upgrade recommended

hmm. check that out, see what the author asks for/requires in terms of 
firmware versions.
it might also modify the behaviour as seen below.

>spurious 8259A interrupt: IRQ7.
>prism2: wlan0: operating mode changed 3 -> 2
>wlan0: INFO - fid=0x01f8 - len=2 type=0xf200
>   LinkStatus=2 (Disconnected)
>wlan0: INFO - fid=0x01f9 - len=2 type=0xf200
>   LinkStatus=2 (Disconnected)
>wlan0: INFO - fid=0x01fa - len=2 type=0xf200
>   LinkStatus=2 (Disconnected)
>wlan0: INFO - fid=0x01fb - len=2 type=0xf200
>   LinkStatus=2 (Disconnected)
>wlan0: prism2_open
>wlan0: INFO - fid=0x0289 - len=2 type=0xf200
>   LinkStatus=2 (Disconnected)
>wlan0: INFO - fid=0x028a - len=2 type=0xf200
>   LinkStatus=2 (Disconnected)
>prism2: wlan0: operating mode changed 2 -> 3
>wlan0: INFO - fid=0x028b - len=2 type=0xf200
>   LinkStatus=2 (Disconnected)


To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message