On Tue, 25 Sep 2007 14:27:44 -0400 Dan Williams <dcbw@xxxxxxxxxx> wrote: > On Thu, 2007-09-20 at 18:50 +0300, Faidon Liambotis wrote: > > [CCing networkmanager mailing list] > > Michael Buesch wrote: > > > On Thursday 20 September 2007, Luis R. Rodriguez wrote: > > >> On 9/20/07, Stephen Hemminger <shemminger-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@xxxxxxxxxxxxxxxx> wrote: > > >>> Network manager doesn't seem to detect ath5k. Perhaps it is because > > >>> it is name "ath0". I think device should follow the convention of using > > >>> name "wifi0" rather than BSD convention of putting driver name in device name. > > >> I couldn't agree anymore. But my ath5k kicks out a wlan%d name as with > > >> any other mac80211 driver. Is yours coming out to ath%d ? > > > > > > Probably udev renames it. > > IMHO, NetworkManager should cope with whatever name is assigned to a device. > > AFAIK, device names are only "suggestions" by the drivers; the user may > > rename the device name (either by "ip link set name", with ifrename or > > with udev rules) to his liking, e.g. home. > > 0.7 svn trunk uses device indexes internally already. > > > Granted, seems a bit of an overkill to rename a device on a machine > > where NetworkManager is in charge of the device but still, there is no > > reason why it shouldn't be allowed. > > No reason why you shouldn't be able to do this with NM. > > Dan > Actually, NM sees the card. The problem is that scanning appears to be broken. It seems to be related to the card type (PCI-E). -- Stephen Hemminger <shemminger@xxxxxxxxxxxxxxxxxxxx> - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
