OESF Portables Forum

Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: tunemx on July 06, 2004, 08:35:42 am

Title: tkcROM and WCF12
Post by: tunemx on July 06, 2004, 08:35:42 am: Hello!

I will get my first ever WLAN card, a Linksys WCF12. I have tkcROM installed on a SL-5500. What will I have to do after inserted the card? Just launch Network Settings, and choose Wireless? Or will I have to edit some files too?

Thanks for any information.
Title: tkcROM and WCF12
Post by: tunemx on July 07, 2004, 03:43:20 pm: OK it was easy. Card connected, setting up SSID, and WEP, saying connect to the network connection subapp, and good to go.
However I have a problem. The card is really hot, even it is not used heavily, just connected and consuming energy. It makes even the Zaurus hot so it shuts down after an hour or so.

Is it happening to other WCF12 users too, or mine defected?
Title: tkcROM and WCF12
Post by: stupkid on July 07, 2004, 06:38:41 pm: Mine gets pretty toasty after about an hour. I thought it was a problem with CF Wifi in general, but I've never used any other cards to verify that theory. Perhaps that is why the WCF12 is so cheap!
Title: tkcROM and WCF12
Post by: dz on July 07, 2004, 07:11:11 pm: Mine used to do the same thing. My AmbiCom didn't get as hot, but it also got hot as well.
Title: tkcROM and WCF12
Post by: tunemx on July 08, 2004, 03:43:12 am: But this one is so hot it really bothers the Z so much, it just blanks the LCD and stops working after a good 20 minutes of Wifi use. I think it's pretty abnormal. I can only revive the unit when it is connected to AC again...
Title: tkcROM and WCF12
Post by: tunemx on July 16, 2004, 04:54:48 pm: When I set WCF12 on tkcROM iwconfig shows nothing. Why is that? The WLAN is working OK, but it seems like there is a wrapper around it, and it is not coming down to the system level. This way I can't even use it to run Kismet, or Wellenreiter, because these programs are not recognizing it as a valid device.

I am ssh'ing in into the Zaurus via WLAN connection, and then issueing "iwconfig". Here is the result. What's wrong?

Code: [Select]
[root@zaurus ~]# iwconfig lo no wireless extensions. irlan0 no wireless extensions. irda0 no wireless extensions. eth0 no wireless extensions.
And then "ifconfig"

Code: [Select]
[root@zaurus ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:0C:41:0B:01:25 inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:269 errors:0 dropped:0 overruns:0 frame:0 TX packets:282 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:19441 (18.9 Kb) TX bytes:15352 (14.9 Kb) Interrupt:35 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)