Messages

1

Angstrom & OpenZaurus / Problems With D-link Dcf-660w Wifi-card

« on: August 06, 2006, 06:53:59 am »

What does "cardctl ident" say?

Did you modify your /etc/pcmcia/hostap_cs.conf to correspond with the output of cardctl ident?
You may want to try adding the following to hostap_cs.conf and restart.

  card "D-Link DWL-660 11Mbps WLAN Card"
    version "D-Link", "DCF-660W", ""
    # manfid 0xd601, 0x0005
    bind "hostap_cs"

2

Angstrom & OpenZaurus / Basic Rom Flash Question (root & User Partitions)

« on: August 06, 2006, 06:39:13 am »

Hi all -

I am trying to give OZ a go after several years of using other ROMs.  A basic question:  how much root partition does 3.5.4.1 need on an 860?  Or does it handle that itself when it flashes?

A related question relates to reformatting the user partitiion.  Will OZ do that?  Or is there a good way to do it, in order to wipe all settings away etc for a "fresh" install?

TIA,

C.

3

Security and Networking / Bluetooth Faq Or Howto?

« on: August 03, 2006, 09:45:26 am »

oops ... found what i was looking for...

https://www.oesf.org/index.php?title=Bluetooth

4

Security and Networking / Socket Go Wi-fi! P500

« on: August 03, 2006, 04:55:18 am »

Thx.  I'll give ot a go.  Socket even provide a table of supported products for the Zaurii; always a  good sign.

http://www.socketcom.com/ZaurusSharp.asp

5

Security and Networking / Socket Go Wi-fi! P500

« on: August 02, 2006, 05:54:12 am »

Hi all -

I'm in the market for a new CF WiFi card.  Does anyone have any experience with the Socket Go Wi-Fi! P500?  Will it work in a Zaurus?  I'm using Cacko 1.22 & 1.23.

http://www.socketstore.com/product.asp?sku=2850722

6

Security and Networking / Wifi stupidity: "The signal level is low."

« on: August 02, 2006, 05:24:16 am »

I have a dlink dcf 660W and this happens within minutes of getting online, which is pretty frustrating. At the moment it has locked up my zaurus completely, so I can't even tell you what dmesg says about it.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

I have the same prob.  Ref: [a href=\"https://www.oesf.org/forums/index.php?showtopic=20772]https://www.oesf.org/forums/index.php?showtopic=20772[/url]

There is some dmesg stuff in there.

Still trying to fix it...

7

Sharp ROMs / D-link Dcf-660w Not Working With Cacko 1.23

« on: August 02, 2006, 05:15:51 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
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

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

8

Sharp ROMs / Cacko 1.23 & Wifi Signal Strength

« on: August 02, 2006, 04:22:32 am »

OK the weirdness continues.  Now I can connect fine for about five minutes (blue icon), then get the red icon before dropping packets and the connection downgrades to be unusable.  This is happening on both office and home Wireless Lan networks, virtually like clockwork.

Here is a piece of dmesg:

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=c3b658a0, 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=c3b658a0, 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=c3b658a0, 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=c3b658a0, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
eth0: hfa384x_setup_bap - timeout before
eth0: hfa384x_set_rid (rid=fc0e, len=34) - failed - res=-110
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=c3b658a0, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fc28, len=2)
Could not read current WEP flags.
wifi0: encryption setup failed
eth0: set_encryption failed
hostap_cs: CS_EVENT_PM_RESUME
hostap_cs: CS_EVENT_CARD_RESET
prism2_hw_init: initialized in 190 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
   A1=00:00:00:00:00:00 A2=00:80:c8:2b:7a:f7 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:15:e9:e0:7f:55
eth0 (WE) : Buffer for request 8B1B too small (0<9)



Have you guys seen anything like this before?  Could it be the Dlink 660W card is failing?  

TIA,

C.

9

Sharp ROMs / Cacko 1.23 & Wifi Signal Strength

« on: August 01, 2006, 01:10:46 am »

Well, I tried to downgrade to Cacko 1.22 to eliminate the possibility of something in 1.23 (also had bluetooth issues in 1.23).  However, I am still getting this signal low problem, and dropped packets which is making the Z almost unusable.

Dmesg tells me the following:

eth0 (WE) : Buffer for request 8B1B too small (0<

Does anyone know to what this refers?

TIA,

C.


BTW, I also found a thread on OESF which states the following:

Ok, once again, the signal too low error is a bug in Qtopia/Sharp which doesn't query the driver for the range of expected signal strength values but instead uses a fixed range, which is... wrong.

ref: https://www.oesf.org/forums/lofiversion/index.php?t3287.html

10

Sharp ROMs / Cacko Rom 1.23 Is Released

« on: July 31, 2006, 04:33:59 am »

on a related note, since I don't have Cacko 1.23 running at the moment, can someone please paste the output of the mount command here? I just want to check what the cramfs image on Cacko is mounted as since I cannot remember.

Here is the output from mine:

# mount
/dev/root on / type jffs2 (ro)
/proc on /proc type proc (rw)
/dev/ram1 on /dev type minix (rw)
/dev/loop0 on /usr type squashfs (ro)
/dev/mtdblock3 on /home type jffs2 (rw,noatime)
none on /dev/shm type tmpfs (rw)
none on /dev/pts type devpts (rw)
/dev/mmcda1 on /usr/mnt.rom/card type vfat (rw,noatime)
#

11

Sharp ROMs / Cacko 1.23 & Wifi Signal Strength

« on: July 31, 2006, 02:32:20 am »

Hi -

I have a permanent red network icon in my taskbar, and popup message telling me that "The signal level is low".  The network icon occasionally flashes to blue for a few seconds.  This is despite the fact I am sitting next to the WiFi access point.  Is this "normal"?  I did not see behavior like this in previous cacko releases.

I have an 860 running Cacko 1.23 heavy and a DLink 660 WiFi card.  I recently reflashed and just upgraded the DLink firmware to 1.7.4.  The previous version of firmware, 1.3.x was having probs connecting with Cacko 1.23, thus the upgrade.


# hostap_diag wlan0
Host AP driver diagnostics information for 'wlan0'

NICID: id=0x800c v1.0.0 (PRISM II (2.5) PCMCIA (SST parallel flash))
PRIID: id=0x0015 v1.1.1
STAID: id=0x001f v1.7.4 (station firmware)
#


I have /etc/pcmcia/hostap_cs.conf as the following:


card "D-Link DWL-660 11Mbps WLAN Card"
   version "D-Link", "DCF-660W", ""
#   manfid 0xd601, 0x0005
   bind "hostap_cs"


I have tried enabling the manfid 0xd601, 0x0005; sometimes it connects, other times it can not, so I have gone back to the default and commented that line out.

Now I can connect to a 802.11 network, but the signal strength is always red in the toolbar, and often complaining the signal is "low".



# iwconfig
lo        no wireless extensions.

Warning: Driver for device wifi0 recommend version 18 of Wireless Extension,
but has been compiled with version 16, therefore some driver features
may not be available...

wifi0     IEEE 802.11b  ESSID:"KTHNOKIA"  Nickname:"zaurus"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:15:E9:77:91:70  
          Bit Rate:11 Mb/s   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:6161-6131-3233-3435-3637-3839-31   Security mode:open
          Power Management:off
          Link Quality:51  Signal level:0  Noise level:204
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:2400   Missed beacon:0

wlan0     IEEE 802.11b  ESSID:"KTHNOKIA"  Nickname:"zaurus"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:15:E9:77:91:70  
          Bit Rate:11 Mb/s   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:6161-6131-3233-3435-3637-3839-31   Security mode:open
          Power Management:off
          Link Quality:51  Signal level:0  Noise level:204
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:2400   Missed beacon:0

#



What is strange is that this is happening even while sitting next to the WiFi access point (can reach out & touch it).  I never saw this on previous cacko ROMs (1.22 etc).  Other devices seem to be connecting just fine with 100% signal strength.

Questions:

- Are any of you also experiencing this persistant red signal strength indicator and "signal level low" message in Cacko 1.23?
- Does the app "Wireless LAN Status" never show ESSID?
- Is the "Wireless LAN Status" information reliable?  It does not always seem to correspond with the iwconfig data.  Is iwconfig's information relaible?  In fact, iwconfig always says the "Signal level:0" even thou there is a link.
- Any other hints?

Thanks in advance!

Charles

12

Sharp ROMs / D-link Dcf-660w Not Working With Cacko 1.23

« on: July 31, 2006, 12:20:30 am »

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

13

Sharp ROMs / Recommended Bluetooth Cf Card?

« on: February 22, 2006, 09:28:51 am »

actually I just found it.

oesf.org
[div align=\"right\"][a href=\"index.php?act=findpost&pid=115586\"][{POST_SNAPBACK}][/a][/div]

Perfect, just what I was looking for!

Thanks for the feedback.

C.

14

Sharp ROMs / Recommended Bluetooth Cf Card?

« on: February 21, 2006, 05:07:39 am »

Hi all -

I am looking for a Bluetooth CF card for my 860.  It's running Cacko 1.23.  Can anyone make any recommendations on what to buy?  I've looked thru the forums but nothing jumps out on this topic, but perhaps I've missed an FAQ...

Many thanks in advance,

C.

15

Sharp ROMs / Samba & Cacko1.22

« on: December 28, 2005, 06:54:33 am »

Hello again.

I have found the problem in the samba configuration:

In /etc/samba/smb.conf
 
"interface = usb0 eth0 bnep0 irda0 irda1"

So if I switch of this line
" #  interface = usb0 eth0 bnep0 irda0 irda1"
and restart I can connect my zaurus also by samba.

[div align=\"right\"][a href=\"index.php?act=findpost&pid=94288\"][{POST_SNAPBACK}][/a][/div]

I am seeing the same using Cacko 1.23.  If I leave with the default interfaces config like the following:

interfaces = usbd0 eth0 eth1 wlan0 wlan1 bnep0 irda0 irda1

Then i can not connect from a Mac OS X 10.4.3 box.  In fact, "findsmb" shows the following

charles% findsmb
                                *=DMB
                                +=LMB
IP ADDR         NETBIOS NAME     WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.1.7     ZAURUS        +[        ZAURUS     ]


If, however, I disable the "interfaces = " line with a #, then I can connect fine, and findsmb shows the following:

charles% findsmb

                                *=DMB
                                +=LMB
IP ADDR         NETBIOS NAME     WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.1.7     ZAURUS         [ZAURUS] [Unix] [Samba 2.0.7-ja-2.2]


Interesting how it now dosplays more OS and Samba info.

If, however, I enable the interfaces line with anything beyond 1 interface, then I can not connect any more.

Is anyone else seeing this behavior?  I would like to be able to SMB into my Zaurus using both wlan0 and usbd0, but can not see how that is possible currently.

C.