Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - gooseman

Pages: [1]
1
Angstrom & OpenZaurus / Firefox and OZ 3.5.1
« on: November 05, 2004, 04:11:55 am »
two quick questions.  How did you get rid of all the detrious after the install from the feed (that I obviously did too)?  

Second question.  since I don't have the time, ability (yet), or  machine set up to cross-compile (again, yet), when does anyone think there will  be a "good" ipk of firefox on the feed?

2
General Discussion / Wireless fails to obtain IP
« on: October 01, 2004, 12:00:50 pm »
Quote
My SL5600 with AmbiCom CF wireless card works great when I float around the wifi on my local campus, however, when I try to connect up to my dlink at home I run into some problems.  My home network is setup to use 128bit WEP, MAC filtering, and I have an SSID set.  I have entered my wifi cards mac address into the dlink like I would any other computer, and when I setup the networking options and configure the wireless it actually sees my network.  The problem is the fact that it can't seem to grab an IP address, and that is throwing me off.

If anyone could nudge me in the right direction, I would greatly appreciate it.
I noticed that no matter how I verified my settings, I had to use WEP and Open System.

3
Make sure zImage doesn't have the .bin extension...I made that error and banged my head for a half day on that.

4
Accessories / Zaurus 5500, 802.11b, OZ 3.2 and the SMC2642W
« on: July 15, 2004, 06:40:05 pm »
WAP = Wireless Access Point
WEP = Wired Equivalent Privacy
WPA = Wi-Fi protected access

First one is a hardware definition and the last two are encryption algorithims.

5
Angstrom & OpenZaurus / SL5500, OZ3.2, WiFi and the SMC2642W
« on: July 12, 2004, 01:43:58 pm »
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

6
Accessories / Zaurus 5500, 802.11b, OZ 3.2 and the SMC2642W
« on: July 12, 2004, 01:42:09 pm »
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

7
North Carolina / Welcome, Tar Heels
« on: July 08, 2004, 01:03:47 am »
Charlotte area here...new to the Zaurus but have been working with Unix, various Linux distros, BSD as a hobbyist for several years.

My ultimate goal for my Zaurus is a handy "pocket rocket" tool for network testing and admin, as well as light PIM duty.

8
General Discussion / I need basic vi editor commands
« on: July 07, 2004, 12:26:26 pm »
ooops...I mean't UNIX for Dummies...

And this is a basic basic text and not much more than you could get from reading MAN pages, as was suggested before, and in many cases less than the man page.  The O'reilly book Unix in a Nutshell is also decent, and a good second step into the *nix world

9
General Discussion / I need basic vi editor commands
« on: July 07, 2004, 12:17:49 pm »
The best basic *nix text around  IMHO is "Linux for Dummies" quick reference, YMMV,...and they have a nicely laid out basic  "vi" cheatsheet.  

vi rulez - emacs droolz...LOL...for all the newly minted *nix enthusiasts, the vi versus emacs debate is one of the oldest and dearest flame wars ever.  I suspect it might even be the subject of the first flame war

Pages: [1]