OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

Profile
Personal Photo
Options
Options
Personal Statement
gooseman doesn't have a personal statement currently.
Personal Info
gooseman
Age Unknown
Gender Not Set
Location Unknown
Birthday Unknown
Interests
No Information
Statistics
Joined: 7-July 04
Profile Views: 87*
Last Seen: 4th January 2005 - 09:23 AM
Local Time: Aug 22 2014, 03:38 PM
9 posts (0 per day)
Contact Information
AIM No Information
Yahoo No Information
ICQ No Information
MSN No Information
* Profile views updated each hour

gooseman

Members


Topics
Posts
Comments
Friends
My Content
12 Jul 2004
I have two problems regarding WiFi on the Zaurus SL 5500 OZ3.2.

1. I have an SMC2642W 802.11b CF card that I'm trying to get to work with a D-link 614+ WAP. If I leave the WAP in "Open System" mode, I get a good connection, when the 3.2 OZ release sees this card as a Zocomm or something if it sees the card as supported at all, (see question 2). If I set the WEP HEX key and switch the Z to Shared Key...I still work, but in "open system " mode, I suspect. If I set the Z to Shared Key and the WAP to shared key the Z never sees the access point. Access point has the " All 4's " HW address from output of IWCONFIG. I see the WAP but never get the primary key exchange, or that is what I suspect. I've tried making the settings via IWCONFIG and the Opie applet, but while both seem to work as far as changing the config file, neither make the connection. The DMESG output just shows the attempt and the failure to authenticate against 44:44:44 etc etc. IS this common to many cards or just the SMC card type or just my particular SMC card. now on to the second question...

2. The SMC2642W shows up spottily as a supported card, if it does recongnize the device it never sees it as the card it really is. I suppose I could edit the file with a new entry for that card, but since it would call the same driver as it does now, why bother, unless it would change the fact that more often than not the damn thing shows up as UNSUPPORTED CARD, and the no amount of tweaking/restarting/physically reseating will get it to be otherwise. when it gets like that, the cardctl idnet output shows a zero function, the identification string is "SMC2642W" rather than the much longer (paraphrased here) "SMC2642W wireless ethernet card" and the MANUID info is zeroes. I also see from CARDCTL STATUS that I get a a Battery low warning. The device will be working off of the Wall wart directly or in the USB cradle at the time. so does the card have a battery in it or something? Why won't the damn thing recognize the card either all the time or none of the time?

What am I missing here? This is not hard stuff....I'm loathe to even ask for help, but if I don't get this squared away I'm going to pack this guy up with my old Visor, my pair of Cybikos, etc etc and chalk it up to "nice toy" because I'll lose interest. And my interest is basically turning this 5500 into a network admin tool kit/ basic PIM (calendar and phone numbers...handy) and then being able to duplicate it to my various remote sites for my team to use.

Info, I finally got the USDB0 up and working although periodically it "goes to sleep" when connected to the WINXP machine; nuisance at best. The TrendNET 10/100 ethernet card works like a champ. Im no guru, but I am usually pretty profecient in most Linux distros, including Debian Woody which was my distro of choice for my home server, until I decided to move it to FreeBSD. It's going back to debian to double as a dev platform for my Zaurus distro. I can provide any outputs from commands if needed and specified. HELP!

Thanks in advance...just trying to ramp up the learning curve fast
12 Jul 2004
I have two problems regarding WiFi on the Zaurus SL 5500 OZ3.2.

1. I have an SMC2642W 802.11b CF card that I'm trying to get to work with a D-link 614+ WAP. If I leave the WAP in "Open System" mode, I get a good connection, when the 3.2 OZ release sees this card as a Zocomm or something if it sees the card as supported at all, (see question 2). If I set the WEP HEX key and switch the Z to Shared Key...I still work, but in "open system " mode, I suspect. If I set the Z to Shared Key and the WAP to shared key the Z never sees the access point. Access point has the " All 4's " HW address from output of IWCONFIG. I see the WAP but never get the primary key exchange, or that is what I suspect. I've tried making the settings via IWCONFIG and the Opie applet, but while both seem to work as far as changing the config file, neither make the connection. The DMESG output just shows the attempt and the failure to authenticate against 44:44:44 etc etc. IS this common to many cards or just the SMC card type or just my particular SMC card. now on to the second question...

2. The SMC2642W shows up spottily as a supported card, if it does recongnize the device it never sees it as the card it really is. I suppose I could edit the file with a new entry for that card, but since it would call the same driver as it does now, why bother, unless it would change the fact that more often than not the damn thing shows up as UNSUPPORTED CARD, and the no amount of tweaking/restarting/physically reseating will get it to be otherwise. when it gets like that, the cardctl idnet output shows a zero function, the identification string is "SMC2642W" rather than the much longer (paraphrased here) "SMC2642W wireless ethernet card" and the MANUID info is zeroes. I also see from CARDCTL STATUS that I get a a Battery low warning. The device will be working off of the Wall wart directly or in the USB cradle at the time. so does the card have a battery in it or something? Why won't the damn thing recognize the card either all the time or none of the time?

What am I missing here? This is not hard stuff....I'm loathe to even ask for help, but if I don't get this squared away I'm going to pack this guy up with my old Visor, my pair of Cybikos, etc etc and chalk it up to "nice toy" because I'll lose interest. And my interest is basically turning this 5500 into a network admin tool kit/ basic PIM (nessus, kismet,ethereal nmap etc and then calendar and phone numbers...handy) and then being able to duplicate it to my various remote sites for my team to use.

Info, I finally got the USDB0 up and working although periodically it "goes to sleep" when connected to the WINXP machine; nuisance at best. The TrendNET 10/100 ethernet card works like a champ. Im no guru, but I am usually pretty profecient in most Linux distros, including Debian Woody which was my distro of choice for my home server, until I decided to move it to FreeBSD. It's goingto go back to Debian to double as a dev platform for my Zaurus distro. I can provide any outputs from commands if needed and specified.

Oh and by the way is there any elegant way to do a totally clean install of the OS besides rm -rf * at the root prompt, then flash with the C and D key process? If anyone is interested in my net admin idea, and has more experience with the Z than me, I'd ike to discuss the pros and cons of a SD based ROM vs a Hybrid, with the base OS and swap on the Z with the "packages" on the SD card.

Thanks in advance...just trying to ramp up the learning curve fast

Goose
Last Visitors
gooseman has no visitors to display.

Comments
Other users have left no comments for gooseman.

Friends
There are no friends to display.
RSS Lo-Fi Version Time is now: 22nd August 2014 - 03:38 PM