ath5k and network manager

ath5k and network manager

[Stephen Hemminger]

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.

-- 
Stephen Hemminger <shemminger@linux-foundation.org>

Re: ath5k and network manager

[Luis R. Rodriguez]

On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> 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 ?

ieee80211_register_hw():

        /* add one default STA interface */
        result = ieee80211_if_add(local->mdev, "wlan%d", NULL,
                                  IEEE80211_IF_TYPE_STA);

  Luis

Re: ath5k and network manager

[Michael Buesch]

On Thursday 20 September 2007, Luis R. Rodriguez wrote:
> On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> 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 ?
> 
> ieee80211_register_hw():
> 
>         /* add one default STA interface */
>         result = ieee80211_if_add(local->mdev, "wlan%d", NULL,
>                                   IEEE80211_IF_TYPE_STA);
> 


Probably udev renames it.

Re: ath5k and network manager

[Stephen Hemminger]

On Thu, 20 Sep 2007 15:11:23 +0200
Michael Buesch <mb@bu3sch.de> wrote:

> On Thursday 20 September 2007, Luis R. Rodriguez wrote:
> > On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> 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 ?
> > 
> > ieee80211_register_hw():
> > 
> >         /* add one default STA interface */
> >         result = ieee80211_if_add(local->mdev, "wlan%d", NULL,
> >                                   IEEE80211_IF_TYPE_STA);
> > 
> 
> 
> Probably udev renames it.

It was udev, don't know why Ubuntu was adding a rule for it (and getting wrong)
value.

-- 
Stephen Hemminger <shemminger@linux-foundation.org>

Re: ath5k and network manager

[Luis R. Rodriguez]

On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> On Thu, 20 Sep 2007 15:11:23 +0200
> Michael Buesch <mb@bu3sch.de> wrote:
>
> > On Thursday 20 September 2007, Luis R. Rodriguez wrote:
> > > On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> 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 ?
> > >
> > > ieee80211_register_hw():
> > >
> > >         /* add one default STA interface */
> > >         result = ieee80211_if_add(local->mdev, "wlan%d", NULL,
> > >                                   IEEE80211_IF_TYPE_STA);
> > >
> >
> >
> > Probably udev renames it.
>
> It was udev, don't know why Ubuntu was adding a rule for it (and getting wrong)
> value.
>

CC' TIm

Was it a rule by PCI ID? If so then perhaps its based on the old
madwifi rules of sticking to ath%d notation as well. This can be
removed for ath5k but not too sure how this works.

  Luis

Re: ath5k and network manager

[Stephen Hemminger]

On Thu, 20 Sep 2007 11:34:29 -0400
"Luis R. Rodriguez" <mcgrof@gmail.com> wrote:

> On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> > On Thu, 20 Sep 2007 15:11:23 +0200
> > Michael Buesch <mb@bu3sch.de> wrote:
> >
> > > On Thursday 20 September 2007, Luis R. Rodriguez wrote:
> > > > On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> 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 ?
> > > >
> > > > ieee80211_register_hw():
> > > >
> > > >         /* add one default STA interface */
> > > >         result = ieee80211_if_add(local->mdev, "wlan%d", NULL,
> > > >                                   IEEE80211_IF_TYPE_STA);
> > > >
> > >
> > >
> > > Probably udev renames it.
> >
> > It was udev, don't know why Ubuntu was adding a rule for it (and getting wrong)
> > value.
> >
> 
> CC' TIm
> 
> Was it a rule by PCI ID? If so then perhaps its based on the old
> madwifi rules of sticking to ath%d notation as well. This can be
> removed for ath5k but not too sure how this works.
> 

It was by PCI ID

-- 
Stephen Hemminger <shemminger@linux-foundation.org>

Re: ath5k and network manager

[Luis R. Rodriguez]

On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> On Thu, 20 Sep 2007 11:34:29 -0400
> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>
> > On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> > > On Thu, 20 Sep 2007 15:11:23 +0200
> > > Michael Buesch <mb@bu3sch.de> wrote:
> > >
> > > > On Thursday 20 September 2007, Luis R. Rodriguez wrote:
> > > > > On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> 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 ?
> > > > >
> > > > > ieee80211_register_hw():
> > > > >
> > > > >         /* add one default STA interface */
> > > > >         result = ieee80211_if_add(local->mdev, "wlan%d", NULL,
> > > > >                                   IEEE80211_IF_TYPE_STA);
> > > > >
> > > >
> > > >
> > > > Probably udev renames it.
> > >
> > > It was udev, don't know why Ubuntu was adding a rule for it (and getting wrong)
> > > value.
> > >
> >
> > CC' TIm
> >
> > Was it a rule by PCI ID? If so then perhaps its based on the old
> > madwifi rules of sticking to ath%d notation as well. This can be
> > removed for ath5k but not too sure how this works.
> >
>
> It was by PCI ID

Then I guess that rule should be removed from udev because of ath5k,
if we let the driver pick the name then we'd get ath%d for madwifi
driver and wlan%d for ath5k. Would help with troubleshooting too. Tim?
:-)

  Luis

Re: ath5k and network manager

[Tim Gardner]

Luis R. Rodriguez wrote:
> On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
>> On Thu, 20 Sep 2007 11:34:29 -0400
>> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>>
>>> On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
>>>> On Thu, 20 Sep 2007 15:11:23 +0200
>>>> Michael Buesch <mb@bu3sch.de> wrote:
>>>>
>>>>> On Thursday 20 September 2007, Luis R. Rodriguez wrote:
>>>>>> On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> 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 ?
>>>>>>
>>>>>> ieee80211_register_hw():
>>>>>>
>>>>>>         /* add one default STA interface */
>>>>>>         result = ieee80211_if_add(local->mdev, "wlan%d", NULL,
>>>>>>                                   IEEE80211_IF_TYPE_STA);
>>>>>>
>>>>>
>>>>> Probably udev renames it.
>>>> It was udev, don't know why Ubuntu was adding a rule for it (and getting wrong)
>>>> value.
>>>>
>>> CC' TIm
>>>
>>> Was it a rule by PCI ID? If so then perhaps its based on the old
>>> madwifi rules of sticking to ath%d notation as well. This can be
>>> removed for ath5k but not too sure how this works.
>>>
>> It was by PCI ID
> 
> Then I guess that rule should be removed from udev because of ath5k,
> if we let the driver pick the name then we'd get ath%d for madwifi
> driver and wlan%d for ath5k. Would help with troubleshooting too. Tim?
> :-)
> 
>   Luis

Keeping the names unique makes sense to me, especially in the case where
both drivers are present in the distro, as will likely be the case until
ath5k fully matures.

I'll research the udev rule...

rtg
-- 
Tim Gardner tim.gardner@ubuntu.com

Re: ath5k and network manager

[Faidon Liambotis]

[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@public.gmane.org> 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.

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.

Regards,
Faidon

Re: ath5k and network manager

[Dan Williams]

On Wed, 2007-09-19 at 21:40 -0700, Stephen Hemminger 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.

NM shouldn't care what the device name is as long as the device has the
right tags in HAL and as long as the device doesn't get renamed
underneath NM (0.7 svn already uses device indexes internally instead).

Dan

Re: ath5k and network manager

[Dan Williams]

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@public.gmane.org> 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

> Regards,
> Faidon
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: ath5k and network manager

[Stephen Hemminger]

On Tue, 25 Sep 2007 14:27:44 -0400
Dan Williams <dcbw@redhat.com> 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@public.gmane.org> 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@linux-foundation.org>