Thanks for the note.
I haven't been able to find much out about my
kernel: usb 1-2: control timeout on ep0in
problem, other than it may happen if the device is
underpowered (seems unlikely since it works from the Win2K
side of this dual-boot box) or that 2.6 kernels don't always
do USB right on older motherboards (the computer was new
five years ago). I gotta wonder since the USB jump drive
On Wed, 23 Mar 2005, Adrian Irving-Beer wrote:
> On Wed, Mar 23, 2005 at 12:29:51PM -0600, James Shatto wrote:
> > > Also, is there supposed to be something in
> > > /etc/network/interfaces?
> > /etc/network/interfaces is to setup your wireless configuration at
> > boot. If you don't need it automatically setup at boot you probably
> > don't need to touch it. But it's there and there's several howto's
> > and examples of it out on the web.
> Forgot to mention -- it only does it at boot if you say 'auto wlan0'
> in the file.
> It's actually handy to store static configuration data about your
> devices. Then when you actually want them, you just load the
> ndiswrapper drivers, run 'ifup wlan0', and it's ready to go.
> You can even store multiple configs for the same device. For example,
> you can have interface definitions for 'wlan0-home' and
> 'wlan0-office', and when you want to pick your home config, run 'ifup
> wlan0=wlan0-home'. This is what I do.
> There are other things you can do with this, too, such as running
> scripts on activation or deactivation (before or after). And you can
> also define a script that decides for you which config to use; once
> upon a time, I had a script that did a scan, picked out any APs it
> knew, and used the corresponding config.
> That being said, /etc/network/interfaces is not required to get the
> device working manually, and is only for when you've got it working
> and want to commit your settings to a more convenient form.