Stuart F. Biggar wrote: >>Does your A21p's bottom slot start to work after the >>top slot has been used at least once? >> >>That is: plug into top slot, check that ath1 is >>detected, >>unplumb wlan nic and modunlod wlan driver module, >>move wlan cardbus card from top to bottom slot? >> >> > >No, that doesn't work. > > > This problem is different from Jurgen's.
>Try to connect with an already defined profile: > >[a21p:/]# wificonfig -i ath1 connect tobeornottobe >wificonfig: connecting to tobeornottobe failed, try later > > > What is the output of "wificonfig -i ath1 scan" ? If "scan" doesn't work, then nothing works. >The radio lights are blinking (3 quick blinks on one, then the other, >repeated ...) > >[a21p:/]# wificonfig -i ath1 showstatus > linkstatus: not connected > >Well, that didn't work too well so try to switch slots: > >[a21p:/]# ifconfig ath1 unplumb >[a21p:/]# ifconfig -a >lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 >index 1 > inet 127.0.0.1 netmask ff000000 >iprb0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 4 > inet 192.168.1.101 netmask ffffff00 broadcast 192.168.1.255 > ether 0:10:a4:92:ad:dc >[a21p:/]# modinfo | grep ath > 92 f9cdb000 28920 194 1 ath (ath driver 1.1) >[a21p:/]# modunload -i 92 >[a21p:/]# modinfo | grep ath >[a21p:/]# > >However, the lights are still blinking so sync the >filesystem before a hot unplug ... > >After putting in the bottom slot (no lights on yet) >prtconf -D shows: > > pci1014,130, instance #0 (driver name: pcic) > pcs, instance #0 (driver name: pcs) > ethernet, instance #1 (driver name: ath) > pci1014,130, instance #1 (driver name: pcic) > pcs, instance #1 (driver name: pcs) > >Well, the output of prtconf didn't change :-( > > > This is a different problem. What are the messages when you switch the slot? (please enable debugging)
