On Sat, 2006-04-01 at 22:45 -0500, David Cary Hart wrote: > On Sat, 01 Apr 2006 21:33:57 -0500 > Robert Locke <lists@xxxxxxxxx> opined: > > On Sat, 2006-04-01 at 14:29 -0500, David Cary Hart wrote: > > > On Sat, 01 Apr 2006 14:19:31 -0500 > > > "Jeffrey D. Yuille" <jeffy5@xxxxxxxxxxxxx> opined: > > > > I have a Linksys Wireless card, model wpc55ag. I am using a > > > > Dell Inspiron 4000 laptop and have FC5 installed with the Gnome > > > > desktop. This card worked perfectly under FC4, using the > > > > madwifi drivers but I cannot get it recognized in FC5. I would > > > > click on Desktop-System Settings-Network, I would come upon the > > > > Networking Configuration tool. When I click on New-Wireless > > > > Connection, I would only see "other wireless cards". The > > > > system does not even see my card, despite already having > > > > installed the kmod-madwifi drivers. How can I corrct this > > > > problem? Is this a problem for others (or is this a bug?) ? > > > > > > > Do you have the alias (eg alias ath0 ath_pci) in modprobe.conf? > > > > > > > Actually, with the packaging from livna, it is found > > in /etc/modprobe.d/madwifi rather than directly > > in /etc/modprobe.conf... > > > > alias wifi0 ath_pci > > alias ath0 ath_pci > > options ath_pci autocreate=sta > > > > Though I am experiencing the same problem. system-config-network is > > insisting that the wireless is an Ethernet card. So I gave up and > > just wrote a script that I run by hand when not wired.... > > > > iwconfig ath0 essid "yourssidhere" key "yourwepkeyhere" > > iwpriv ath0 authmode 2 > > iwpriv ath0 mode 2 > > ifconfig ath0 up > > dhclient -1 ath0 > > > > I believe this may be related to the madwifi-ng code not being > > properly recognized by system-config-network given the pair of > > layers here with both wifi0 and ath0 being established.... > > > > Yes. I had the same problem. Simple. Add alias ath0 ath_pci to > modprobe.conf and you will have another device identified as > wireless. I believe that I deleted the other references. Yeah, just figured that out (see other message).... Have opened a bugzilla ticket (#187640) on this as external packaging should be creating this (as livna does) in /etc/modprobe.d/ not directly editing /etc/modprobe.conf and we should not have to bridge the gap. system-config-network really should be able to pick up the stuff in /etc/modprobe.d/.... Thanks, --Rob
