[arch-general] Last couple of updates Knocked my Wireless -- OUT (atheros/madwifi/ath_pci)

[David C. Rankin]

On Monday 21 September 2009 09:25:24 am Tom K wrote:
> David C. Rankin wrote:
> > Listmates,
> >
> > 	I'm not sure where to start troubleshooting this problem. For months and
> > months, ever since I installed Arch, my Atheros wifi (through ath0) has
> > always just worked right out of the box.
> 
> <snip>
> 
> > The mywpa.conf file is:
> >
> > CONNECTION="wireless"
> > INTERFACE=wlan0
> > SCAN="yes"
> > SECURITY="wpa"
> > ESSID="skyline"
> > KEY="notmyrealkey"
> > IP="dhcp"
> > TIMEOUT=20
> 
> That profile would never have worked with ath0, as it specifies wlan0 as
> the interface.
> 
> > Now I boot my box and I get nothing but the "lo" interface brought up.
> > What gives?
> 
> Check dmesg and/or your logs for clues.
> 
> > What in the world could have changed in the past week or so that is
> > presenting my wireless from being brought up at boot?
> 
> As already mentioned - until you tell us what you have done to your
> system in the past week or so, you might as well be asking how to build
> one of these:
> http://en.wikipedia.org/wiki/Perpetual_motion
> 
> T.
> 

Sorry guys, I'll get the detail,

But yes this profile DOES work as wlan0 is simply an alias for ath0 under the 
madwifi driver:

[13:48 alchemy:/home/david] # ifconfig
ath0      Link encap:Ethernet  HWaddr 00:1B:9E:7C:F6:E7
          inet addr:192.168.6.102  Bcast:192.168.6.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:378638 errors:0 dropped:0 overruns:0 frame:0
          TX packets:133854 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:429332196 (409.4 Mb)  TX bytes:14984393 (14.2 Mb)

eth0      Link encap:Ethernet  HWaddr 00:1B:38:AF:36:B8
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:252 Base address:0xa000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:499 errors:0 dropped:0 overruns:0 frame:0
          TX packets:499 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:57057 (55.7 Kb)  TX bytes:57057 (55.7 Kb)

wifi0     Link encap:UNSPEC  HWaddr 00-1B-9E-7C-F6-
E7-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:747577 errors:0 dropped:0 overruns:0 frame:32135
          TX packets:155592 errors:2 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:280
          RX bytes:303248952 (289.2 Mb)  TX bytes:21529160 (20.5 Mb)
          Interrupt:19

I'll get the pacman logs and post them. But I suspect the problem is related 
to the other post about wifi problems lately.

-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com