Bug#414557: fails to create ath1 if ath0 is not present
Uwe Kleine-König
ukleinek at informatik.uni-freiburg.de
Tue Nov 20 20:58:36 UTC 2007
Hello,
Uwe Kleine-König wrote:
> Hello,
>
> Kel Modderman wrote:
> > On Tue, 13 Mar 2007 12:11:40 am Uwe Kleine-König wrote:
> > > Package: madwifi-tools
> > > Version: 1:0.9.2+dfsg-1
> > > Severity: normal
> > >
> > > Hello,
> > >
> > > I'm not sure if that's a problem with madwifi-tools or the kernel
> > > driver. FWIW, I using version 0.9.2+r1842.20061207-2 of the kernel
> > > driver.
> > >
> > > root at cepheus:~# ifconfig -a | grep ath
> > > root at cepheus:~# wlanconfig ath1 create wlandev wifi0 wlanmode sta
> > > ath1
> > > root at cepheus:~# ifconfig -a | grep ath
> > > ath0 Link encap:Ethernet HWaddr 00:11:xx:xx:xx:xx
> > >
> > > So ath0 is created instead of ath1. This happens to jumble ifupdown.
> >
> > I think this may be udev rules, check:
> >
> > /etc/udev/rules.d/z25_persistent-net.rules
> >
> > for rules with athX.
> Currently I have:
>
> # PCI device 0x168c:0x0013 (ath_pci)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:11:95:bb:42:d6", ATTRS{type}=="1", NAME="ath0"
>
> # PCI device 0x168c:0x0013 (ath_pci)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="06:11:95:bb:42:d6", ATTRS{type}=="1", NAME="ath1"
>
> # PCI device 0x168c:0x0013 (ath_pci)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="0a:11:95:bb:42:d6", ATTRS{type}=="1", NAME="ath2"
>
> # PCI device 0x168c:0x0013 (ath_pci)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:04:0e:c4:82:3b", ATTRS{type}=="1", NAME="ath3"
>
> But I cannot do further tests now, because I currently access the
> machine via this device. For now I cannot even say if these lines where
> already there when I reported the bug.
>
> If your guess is right, do you have a suggestion how to fix the problem?
> Is it an udev bug?
>
> I will look into this issue later when I have physical access to the
> machine again. Thanks for now.
OK, finally I found the time to look into this issue again, sorry that
it took so long.
udevmonitor reports:
UEVENT[1195591531.029634] add@/class/net/ath1
UDEV [1195591531.030523] add@/class/net/ath0
That is your guess that udev is involved is correct.
Best regards
Uwe
--
Uwe Kleine-König
http://www.google.com/search?q=0+degree+Celsius+in+kelvin
More information about the Pkg-madwifi-maintainers
mailing list