OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: tavasti on November 23, 2005, 11:42:45 am
-
Looks like my D-link DCF-660W is not working with cacko 1.23. I'm not sure, but with original ROM I got my C1000 if might been working. At least wireless monitor was showing some values, now with cacko, nothing. Here is what dmesg says when I plug card in:
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.3.7 - 2005-02-12 (Jouni Malinen <jkmaline@cc.hut.fi>)
hostap_crypt: registered algorithm 'WEP'
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 3.3, irq 135, io 0xf6000000-0xf600003f
prism2_hw_init: initialized in 210 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4
wifi0: registered netdevice wlan0
prism2: wlan0: operating mode changed 3 -> 2
hostap_cs: CS_EVENT_PM_SUSPEND
hostap_cs: CS_EVENT_RESET_PHYSICAL
pxa_pcmcia_suspend(0)
wifi0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wifi0: hfa384x_cmd_issue - timeout - reg=0x8888
wifi0: hfa384x_cmd: entry still in list? (entry=c24be520, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
wifi0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wifi0: hfa384x_cmd_issue - timeout - reg=0x8888
wifi0: hfa384x_cmd: entry still in list? (entry=c24be5e0, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
This continues forever. Ideas what to do?
-Tavasti
-
Looks like many of have wlan problems with cacko 1.23. I entered this bug to http://bryandeluca.com/cacko/bugs/query.php (http://bryandeluca.com/cacko/bugs/query.php) also
-
Firmware update. Use the last firmware. Worked for me.
-
Looks like many of have wlan problems with cacko 1.23. I entered this bug to http://bryandeluca.com/cacko/bugs/query.php (http://bryandeluca.com/cacko/bugs/query.php) also
[div align=\"right\"][a href=\"index.php?act=findpost&pid=104807\"][{POST_SNAPBACK}][/a][/div]
I use the latest version of this card without any problems on my C860. For me wlan in version 1.23 works just fine.
-
Firmware update. Use the last firmware. Worked for me.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=104823\"][{POST_SNAPBACK}][/a][/div]
Hmm, url for firmware update? Is it from dlink on somewhere else?
Edit: I cannot find any firmware from Dlink pages, only Windows driver. I emailed dlink and asked.
-
Hmm, url for firmware update? Is it from dlink on somewhere else?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=104840\")
Ok, I got links:
[a href=\"http://linux.junsun.net/intersil-prism/]http://linux.junsun.net/intersil-prism/[/url]
http://www.red-bean.com/~proski/firmware/ (http://www.red-bean.com/~proski/firmware/)
Unfortunately doesn't help, since prism2_srec says:
ioctl: connection timed out
Missing wlan component info
Could not read wlan RIDs
So I would need more recent FW to update FW. :-(
-
Hey Anton,
Would you know why his card would work with the sharp rom and not the latest cacko rom?
-
Hey, now I got it working:
http://bryandeluca.com/cacko/bugs/bug.php?...&bugid=67&pos=0 (http://bryandeluca.com/cacko/bugs/bug.php?op=show&bugid=67&pos=0)
Posted By: my-zaurus at narod dot ru
Date: 7:39 AM 11-25-2005
Make sure the card is not suspnded - type "cardctl scheme qpewlan0; cardctl reset" before trying to update the firmware
And that did the trick. After it, I could update firmware, and it works!
-
very cool
-
tavasti: you upgraded to FW 1.8.4? can you show me your dmesg log?
Thanks,
-
Hey Anton,
Would you know why his card would work with the sharp rom and not the latest cacko rom?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=104957\"][{POST_SNAPBACK}][/a][/div]
Totaly different wireless drivers.
-
Hi all -
I am having this same prob with a Dlink 660 card with Cacko 1.23. Trying to preform the flash, but prism2_srec told me:
ioctl[PRISM2_IOCTL_HOSTAPD]: connection timed out
Missing wlan component info
Could not read wlan RIDs
I have also tried making sure the card isn't suspended with the "cardctl scheme qpewlan0; cardctl reset" command as suggested above, but that was also returning an error message. After quite a few clock cycles, I realized that the card needs to have a driver loaded before prism2_srec works. In other words, make sure you have some sort of network connection enabled so that prism2_srec can talk to the card properly.
Then the flash worked fine!
Just double-checked via a "hostap_diag wlan0" and all looks good.
FWIW,
Charles
-
Looks like my D-link DCF-660W is not working with cacko 1.23. I'm not sure, but with original ROM I got my C1000 if might been working. At least wireless monitor was showing some values, now with cacko, nothing. Here is what dmesg says when I plug card in:
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.3.7 - 2005-02-12 (Jouni Malinen <jkmaline@cc.hut.fi>)
hostap_crypt: registered algorithm 'WEP'
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 3.3, irq 135, io 0xf6000000-0xf600003f
prism2_hw_init: initialized in 210 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4
wifi0: registered netdevice wlan0
prism2: wlan0: operating mode changed 3 -> 2
hostap_cs: CS_EVENT_PM_SUSPEND
hostap_cs: CS_EVENT_RESET_PHYSICAL
pxa_pcmcia_suspend(0)
wifi0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wifi0: hfa384x_cmd_issue - timeout - reg=0x8888
wifi0: hfa384x_cmd: entry still in list? (entry=c24be520, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
wifi0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wifi0: hfa384x_cmd_issue - timeout - reg=0x8888
wifi0: hfa384x_cmd: entry still in list? (entry=c24be5e0, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
This continues forever. Ideas what to do?
-Tavasti
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=104691\")
Did you get this resolved? I have a similar problem, ref [a href=\"https://www.oesf.org/forums/index.php?showtopic=20772]https://www.oesf.org/forums/index.php?showtopic=20772[/url]
Reflashing has not helped. My DCF660W is now running F/W 1.8.4. The WiFi card runs connects to 2 different 802.11b networks , works fine then after a few minutes drops packets and hostap tries to reset it, turning my SLC-860 into a kind of network paperweight, all but useless.
Not sure what else to try...
TIA
-
Did you get this resolved? I have a similar problem, ref https://www.oesf.org/forums/index.php?showtopic=20772 (https://www.oesf.org/forums/index.php?showtopic=20772)
I also had problems with a card being suspended 1 second after insertion (pxa_pcmcia_suspend(0) in dmesg).
I traced the problem: the pcmcia subsys wants to stop the card, and then wants to start it. But that's too late, it's stucked in suspend.
So the suspend must be disabled: after adding SCHEME="" in /etc/pcmcia/wireless.opts , my card worked perfectly ! (a zcom / ellink xi 815).
Cheers,
Ludovic