Problem With Smc Ez Connect 2642w

[jackschmidt]

Hi,

I've not been able to use my EZ Connect wireless CF card on my Zaurus from day one though I know it worked when my friend gave it to me (he has no idea about my problem).  I've been trying to find the drivers that make this device work but have not had much luck in it.

Originally, I use Watapon 1.6.1 rom and I checked what driver it used, which is prism2_cs.  But it does not yield any wireless extensions so my research lead me to use hostap drivers.  That gave me wireless extensions but did nothing when I went to a hotspot.  It found nothing and left me completely baffled.

Since I saw on the Sharp Zaurus website that such a device was being sold for the Zaurus, I figured I'd go back to the Sharp ROM available on their website. 1.32.

Now I've spent much of today flashing and bringing back my configuration so I can be happy with my Z again.  Then I tried the CF card and voila... nothing.

It still uses the prism2_cs driver and there isn't any wireless extensions AGAIN.

Someone please help me on this problem of mine.

[Greg2]

The prism2_cs is the correct module for your card using the old Sharp Linux kernel. You won't have much luck using that kernels hostap module for your card.

Many of those cards were shipped with old v1.3.6 station firmware. They did not work very well with the Sharp rom unless you upgraded the firmware to at least v1.7.4. You can see what firmware your card has by inserting it in your Z and then checking the dmesg output. If it's older then 1.7.4, I would suggest you upgrade your card's firmware. I've upgraded mine from 1.3.6 to 1.8.2 and it works great with the 2.6.17 kernel using the hostap module, but I use OpenZaurus.

If you want to upgrade the firmware, here's the instructions and links to primary and station firmware: Flashing Intersil Prism Chipsets

[jackschmidt]

The prism2_cs is the correct module for your card using the old Sharp Linux kernel. You won't have much luck using that kernels hostap module for your card.

Many of those cards were shipped with old v1.3.6 station firmware. They did not work very well with the Sharp rom unless you upgraded the firmware to at least v1.7.4. You can see what firmware your card has by inserting it in your Z and then checking the dmesg output. If it's older then 1.7.4, I would suggest you upgrade your card's firmware. I've upgraded mine from 1.3.6 to 1.8.2 and it works great with the 2.6.17 kernel using the hostap module, but I use OpenZaurus.

If you want to upgrade the firmware, here's the instructions and links to primary and station firmware: Flashing Intersil Prism Chipsets
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167813\"][{POST_SNAPBACK}][/a][/div]

Thanks for the explanation.  Just checked mine through dmesg.

This is what is written on mine:
ident: nic h/w: id=0x800c 1.0.0
ident: pri f/w: id=0x15 1.0.7
ident: sta f/w: id=1.3.5

I guess this means I should upgrade the firmware then.  My Linux kernel is 2.4.18-rmk7-pxa3-embedix.

EDIT:
Over at Tyrannozaurus a user shows he has exactly the same firmware as mine but his works out of the box for sl-5500 and sl c1000 sharp rom.  Now I'm not sure what the problem is.

[jackschmidt]

I've configured syslog to show me kernel logs.

Code: [Select]

Sep 27 07:29:55 localhost syslogd 1.4.1: restart.
Sep 27 07:29:55 localhost syslog: syslogd startup succeeded
Sep 27 07:29:55 localhost syslog: klogd startup succeeded
Sep 27 07:29:55 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started.
Sep 27 07:29:55 localhost kernel: ts: pxyp=89(4060/0,1903/0)1
Sep 27 07:29:55 localhost kernel: pxa_pcmcia_init(0)
Sep 27 07:29:55 localhost kernel: prism2_cs.o: 0.1.12-shp Unloaded
Sep 27 07:29:55 localhost kernel: p80211.o: 0.1.12-shp Unloaded
Sep 26 23:30:24 localhost cardmgr[134]: initializing socket 0
Sep 26 23:30:24 localhost cardmgr[134]: socket 0: D-Link DCF-660W  11Mbps 802.11b WLAN Card
Sep 26 23:30:24 localhost cardmgr[134]: executing: 'modprobe prism2_cs'
Sep 26 23:30:24 localhost cardmgr[134]: executing: './wlan-ng start eth0'
Sep 27 07:30:24 localhost kernel: init_module: prism2_cs.o: 0.1.12-shp Loaded
Sep 27 07:30:24 localhost kernel: init_module: dev_info is: prism2_cs
Sep 27 07:30:24 localhost kernel: prism2_cs: index 0x01: Vcc 3.3, irq 39, io 0xf6000000-0xf600003f
Sep 26 23:30:24 localhost /etc/hotplug/net.agent: register event for eth0 not handled
Sep 27 07:30:24 localhost kernel: hfa384x_corereset: hfa384x_corereset not supported on pcmcia. Use driver services COR access function instead
Sep 27 07:30:24 localhost kernel: ident: nic h/w: id=0x800c 1.0.0
Sep 27 07:30:24 localhost kernel: ident: pri f/w: id=0x15 1.0.7
Sep 27 07:30:24 localhost kernel: ident: sta f/w: id=0x1f 1.3.5
Sep 27 07:30:24 localhost kernel: MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
Sep 27 07:30:24 localhost kernel: CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
Sep 27 07:30:24 localhost kernel: PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=4/4
Sep 27 07:30:24 localhost kernel: STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/9
Sep 27 07:30:24 localhost kernel: PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
Sep 27 07:30:24 localhost kernel: STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
Sep 27 07:30:24 localhost kernel: STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Sep 27 07:30:25 localhost kernel: Prism2 card SN: (serial number omitted)
Sep 27 07:30:25 localhost kernel: pxa_pcmcia_suspend(0)
Sep 26 23:30:25 localhost cardmgr[134]: executing: './wlan-ng suspend eth0'
Sep 27 07:30:47 localhost kernel: Kernel logging (proc) stopped.
Sep 27 07:30:47 localhost kernel: Kernel log daemon terminating.
Sep 27 07:30:48 localhost syslog: klogd shutdown succeeded
Sep 27 07:30:48 localhost exiting on signal 15
I'm still on the fence on flashing firmware.  Can someone explain to me what this means?

[jackschmidt]

I read this thread from OESF which seems to have gotten me further.

https://www.oesf.org/forum/index.php?showto...a384x_corereset

Nothing to worry about - no need to ship it back.

The clue is (as always) in the error message

initmac

Which means (I think) that it is failing to IINITiate the Media Access Control layer.

I have a Netgear prism2 card using the wlan_ng drivers and had the same problem with the added bonus of the card going into suspend mode at the end of it.

All that is happening is that your card is unable to attach to a network.

Try setting up the following

Goto the network setup application and add a new connection

In the Account tab call it Test

In the Config tab unceck the Non Spec ESS-ID

Wntr an ESS-ID of Test and change network type to Ad-Hoc

Now goto the TCP/IP tab and set the IP Address to 1.1.1.2, the Subnet Mask to 255.255.255.252 and the Gateway to 1.1.1.1

This connection will be useful if you ever want to run Kismet as well as for testing your card

Now OK that and select your new connection and hit the connect button

You should see the Link light on the card come up and a connection will form

From here its just a case of troubleshooting your Wifi connection - ie we have proved it works smile.gif

Nothing like how I expexted the card to work, but have been messing around with this card (and a bluetooth one) for about a week now (since I got my Z) and think I pretty much worked out the wrinkles

My CF card lights up but I can't tell for sure if that means the card is working.  I know it's setup as static IP and there's a green light indeed that flashes.  Does this mean the card works?