Messages

1

Angstrom & OpenZaurus / Oz 3.5.2 Coming Any Minute Now.

« on: December 01, 2004, 05:31:24 am »

Sounds like you aren't waiting long enough at the GPE splash screen.  I thought my SL6000L was hung there as well.  If you leave it for a few minutes, it'll get in.

With regard to wireless, we'll be putting up a wiki page on the exact steps to configure it using /etc/network/interfaces.  Once you set it up in there, you can just call 'ifup wlan0' or 'ifdown wlan0' to bring it up & down.  3.5.2 shipped with a default configuration which is dhcp, Managed wireless mode.  No essid or anything set.

2

Angstrom & OpenZaurus / Repartitioning 5600

« on: November 17, 2004, 12:34:42 am »

/home is the second paritition of the single nand chip.  To answer your question, yes, it can most certainly be repartitioned.
--
Chris "kergoth" Larson

3

Angstrom & OpenZaurus / Wifi under OZ3.5.1/GPE

« on: November 16, 2004, 07:36:54 pm »

Opie's wireless configuration app writes to /etc/network/interfaces, not /etc/pcmcia/wireless.opts.  So, /etc/pcmcia/wireless never actually does anything, and isnt "used" by Opie in any way, shape or form.  

Cardmgr executes that script, but under normal circumstances, it doesn't actually do anything.  Then hotplug is called when the wlan0 interface is created (cardmgr loading the module).  When that happens, /etc/hotplug/net.agent is called, which calls 'ifup wlan0'.  That configures the interface using the wireless_* entries in interfaces, and then brings it up via normal methods (dhcp, static, what have you).

If you write configuration into wireless.opts, then the pcmcia wireless script will indeed do work to setup the interface.  There's no way to easily ascertain whether that will be called before or after the hotplug script that calls ifup on the interface, and doing it this way, while it may function, isn't the supported methodology.
--
Chris "kergoth" Larson

4

Angstrom & OpenZaurus / Muilt WiFi/Wlan profiles

« on: November 16, 2004, 07:32:10 pm »

The most correct means of setting up network and wireless profiles in OpenZaurus would be to use the existing support in /etc/network/interfaces for 'mapping' entries.  Basically, you setup an entry in that file which tells it how to determine which "mapping" it should use when you attempt to bring up an inteface.  For example, i could go to bring up wlan0, and it could call out a script that checks what mac addresses are nearby, and returns either 'work' or 'home' based on that information, and brings up the appropriate one.

There are existing tools to make this easier.  Remember that OZ is debian based.  Google for info on ifupdown-roaming and waproamd.

I do not believe any of the GUIs supports making use of any of this.  Yet.
--
Chris "kergoth" Larson

5

OpenZaurus/Opie/Qtopia / SL 6000 Support

« on: November 16, 2004, 07:27:02 pm »

FYI, I fixed up the OZ wlan-ng handling a bit.  You can now configure it via /etc/network/interfaces, similar to the way one configures the usual wireless-tools interfaces.  Naturally the gui doesn't handle that yet.  I'll write up a page on the wiki describing how this configuration works.

I also adapted the interfaces entry to automatically do the necessary bits (load module, enable the hardware) on up, and the reverse on down.  So, you can now use the GUI network application to bring the interface (wlan0) up and down, and it will properly do so.
--
Chris "kergoth" Larson