Didn't work. In fact, it added a new way to lock things up. Lacking some direction from the developers on debugging steps that might help, or information I've failed to provide, I'm going to drop the whole thing and check back in from time for the latest svn.
I'm discouraged, of course, but recognize that the driver is advertised as unstable. As always, I'm grateful and humbled by the efforts that far smarter people than I am put in for the good of us all. On Wed, Feb 22, 2006 at 11:03:55AM -0800, Lan Barnes wrote: > Deke, > > A curious yet somehow compelling thought. When I was experimenting > wildly, the wireless first worked when the cat 5 (eth0) connection was > also running. I didn't want to turn the box into a router back to the > same network (I have no idea what, if anything, that might imply), so I > disabled the eth0 profile before going on. Maybe I need to go back and > try the whole thing with eth0 loaded but not connected. > -trimming- > > On Mon, Feb 20, 2006 at 10:01:02PM -0800, Deke Clinger wrote: > > Lan, > > > > I'll offer you my experience. Take it for what it's worth. :) > > > > I have found that when the wireline interface is initialized as eth0 > > and the wireless as eth1 that disabling/removing eth0 completely > > causes problems when using eth1. I'd suggest you remove the route from > > eth0 as you are doing now but do not shut down the interface and > > unload the drivers. Add the route to ath0 or eth1 and see how that > > goes. > > -- Lan Barnes [EMAIL PROTECTED] Linux Guy, SCM Specialist 858-354-0616 Tcl/Tk Enthusiast -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
