Re: Airport stops working.
On Fri, 2005-10-21 at 16:44 +0200, Enric Nadal wrote:
> El Viernes, 21 de Octubre de 2005 00:07, Benjamin Herrenschmidt escribió:
> > You mean that occasionally, when you boot, it doesn't work ?
> No, when i boot the computer, the card works ok, but from time to time, it
> stops working. Ifdowning ang ifuping again doesn't solve the problem, and
> neither does rmmoding airport, hermes...
That is weird since rmmod is supposedly turning it off (as ifconfig down
in fact iirc, unless I broke something). So the card is fully reset.
With an rmmod/insmod cycle, the driver itself is fully recycled too.
> I seems more an issue of
> eth1: New link status: Connected (0001)
> eth1: New link status: Disconnected (0002)
> as Wojciech says in his message.
> But i don't know how to trace the problem better or reproduce.
> For that is what I need help, so I could be more precise.
> Regards,
> Enric
>
> PD: It happened again while I was typing this message. Looking at logs, I've
> found this, perhaps its useful:
> Oct 21 16:19:00 fourier kernel: eth0: Hardware identity 0005:0001:0001:0002
> Oct 21 16:19:00 fourier kernel: eth0: Station identity 001f:0001:0008:0046
> Oct 21 16:19:00 fourier kernel: eth0: Firmware determined as Lucent/Agere 8.70
> Oct 21 16:19:00 fourier kernel: eth0: Ad-hoc demo mode supported
> Oct 21 16:19:00 fourier kernel: eth0: IEEE standard IBSS ad-hoc mode supported
> Oct 21 16:19:00 fourier kernel: eth0: WEP supported, 104-bit key
> Oct 21 16:19:00 fourier kernel: eth0: MAC address 00:30:65:26:FF:7C
> Oct 21 16:19:00 fourier kernel: eth0: Station name "HERMES I"
> Oct 21 16:19:00 fourier kernel: eth0: ready
> Oct 21 16:19:00 fourier kernel: airport: Card registered for interface eth0
> Oct 21 16:19:00 fourier kernel: eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet
> 00:0a:95:71:d1:a8
> Oct 21 16:19:00 fourier kernel: eth0: Found BCM5221 PHY
> Oct 21 16:19:00 fourier kernel: eth1: New link status: Connected (0001)
>
> It's really messed with eth0 and eth1, and iwconfig says eth0 has no wireless
> extensions.
Hrm... something messed with your interface names and your airport
suddenly became eth1 ... I'm not sure what's up here, do you have some
dodgy ifrename scripts in userland that are doing that ?
Ben.
Reply to: