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. -Deke On Mon, 20 Feb 2006, Lan Barnes wrote: > On Mon, Feb 20, 2006 at 10:16:52AM +0000, Tom Crummey wrote: > > Lan Barnes wrote: > > >On Sun, Feb 19, 2006 at 09:08:00PM +0000, Tom Crummey wrote: > > >>Lan Barnes wrote: > > >>>Madwifi also installed from rpm's. > > >>> > > >>>madwifi-kmdl-2.6.15-1.1831_FC4-0.9.6.0-18.rhfc4.at > > >>>madwifi-0.9.6.0-18.rhfc4.at > > >>> > > >>>Here is my error message when I insert the driver: > > >>> > > >>> > > >>Hello Lan, > > >> > > >>It would be mich easier to download the tarball of the latest release > > >>and compile that (instead of the kernel). I've got Fedora Core 4 with > > >>the same kernel release as you and I've just downloaded the tarball, > > >>unpacked it, typed make, then make install. THen reboot and it all > > >>works... > > >> > > > > > >I thought that might be a path but couldn't find a tarball for > > >-2.6.15-1.1831_FC4- ... perhaps I didn't look hard enough. > > > > > >I'm going to go do something physical (I've been bashing my head on this > > >for a day and a night) to shake out my head, and then I'll look harder. > > >If you have a location to the tarball that worked for you, I'd be > > >grateful for the pointer. > > > > > >TIA, > > > > > Hello Lan, > > > > Use the SOURCE tarball and compile it on your system. You'll need the > > kernel development RPM as well, but you should have that if you've built > > kernels before? It's much simpler than recompiling the kernel which is > > what you were proposing..... > > > > The tarball is at: > > > > http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r1453-20060220.tar.gz > > > > > > > > OK, following Tom's recommendation, I built madwifi-ng and struggled > with various config files until I got to my present state. I'm sending > this over the wireless, so obviously there has been much progress. Also, > we can rule out HW failure. > > Here is where I am. > > When the laptop boots, all three net interfaces apparently initialize. I > say three because iwconfig is showing ath0 _and_ wifi0, and the RH > network GUI controller shows eth0, eth1 (wireless), and ath0. > > route -n shows both eth0 and ath0 routed to the network with eth0 on the > default route through the firewall/router. To make the wireless card > work, I have to: > > 1. use route del to remove the default route for eth0 > > 2. use the RH GUI network manager (I'm sure I could use an "if-" command > if I knew which and the syntax) to close eth0 > > 3. use route add default gw to add a path through the router for ath0 > > Then I'm on the air, but watch out! -- trying to browse a web site > through Firefox drops the link light on the d-link and locks the > machine. No problem getting to the same web site using lynx. > > BTW, all of the config files in /etc/sysconf/networking/devices are set > to ONBOOT=no. If I set the ath0 to =yes, the machine locks up on boot. > But the interface comes up on anyway. Very puzzling. > > Almost certainly I have something in the RedHat constellation of scripts > misconfigured. Possibly, because of the web site lock up, I also have a > deeper problem. But perhaps even that can be corrected by some magic > option in the /etc/modprobe.conf. > > My thanks to Tom and everyone on both lists who have gotten me this far. > I think I'm close but not quite there. > > -- > 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 > -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
