Problem with 2.6.0-test9, linksys wpc 11 v3

Jon Nelson jnelson-hostap
Mon Nov 17 09:42:05 PST 2003


... and D-Link DI-614+ (Rev A, Firmware 2.20)


This is what I get in the kernel log.

Nov 15 16:07:04 workstation kernel: hostap_crypt: registered algorithm 'NULL'
Nov 15 16:07:04 workstation kernel: hostap_cs: CVS (Jouni Malinen <jkmaline at cc.hut.fi>)
Nov 15 16:07:04 workstation kernel: hostap_cs: setting Vcc=33 (constant)
Nov 15 16:07:04 workstation kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Nov 15 16:07:04 workstation kernel: hostap_cs: setting Vcc=50 (from config)
Nov 15 16:07:04 workstation kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Nov 15 16:07:04 workstation kernel: IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
Nov 15 16:07:04 workstation kernel: io->flags = 0x0046, io.base=0x0000, len=64
Nov 15 16:07:04 workstation kernel: hostap_cs: Registered netdevice wifi0
Nov 15 16:07:04 workstation kernel: hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
Nov 15 16:07:04 workstation kernel: prism2_hw_init: initialized in 200 ms
Nov 15 16:07:04 workstation kernel: wifi0: trying to read PDA from 0x007f0000: OK
Nov 15 16:07:04 workstation kernel: wifi0: NIC: id=0x800c v1.0.0
Nov 15 16:07:04 workstation kernel: wifi0: PRI: id=0x15 v1.1.1
Nov 15 16:07:04 workstation kernel: wifi0: STA: id=0x1f v1.5.6
Nov 15 16:07:04 workstation kernel: wifi0: registered netdevice wlan0
Nov 15 16:07:05 workstation kernel: prism2: wifi0: operating mode changed 3 -> 1
Nov 15 16:07:05 workstation kernel: wifi0: LinkStatus=6 (Association failed)
Nov 15 16:07:05 workstation kernel: wifi0: LinkStatus: BSSID=44:44:44:44:44:44
Nov 15 16:07:06 workstation kernel: wifi0: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
Nov 15 16:07:07 workstation kernel: wifi0: LinkStatus=1 (Connected)
Nov 15 16:07:07 workstation kernel: wifi0: LinkStatus: BSSID=<trimmed>
Nov 15 16:07:07 workstation kernel: wifi0: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)

The last line repeats and repeats and repeats.
I am *not* using WEP (why bother?) and the system had to be set from
shared key to open system (worked fine w/2.4 and hostap driver).

Now, the only driver I've gotten working is the orinoco driver (0.13e),
but only after I edited the dlink's config as above (why did I have to
do that? Grr..)

Short version:
 - hostap driver worked "best" for me under 2.4.x
 - orinoco driver would work "OK" but under heavy load would barf
 - later, updated firmware from "very old" to what you see here,
   never bothered trying other (than hostap) drivers
 - wanted to play with 2.6.0
 - wireless doesn't work. Proceed with 2 day investigation.
 - results: I hate dlink, but hostap driver /did/ work with 2.4,
   appears like it /should/ with 2.6, but doesn't.

I hope this information is helpful. Perhaps somebody can tell me what's
going on here (is it D-Link's fault? is it the firmware? Is it the
driver?)

I /am/ up an running, and since I use a VPN anyway I don't care about
the WEP stuff (despite it being disabled), but the "solution" for me
with the orinoco drivers was to change from "shared key" to "open
system".





More information about the Hostap mailing list