Thanks Greg, The connection still fails over an open network. The only difference is that the "SIOCSIFFLAGS: Unknown error 132" error does not occur with "/sbin/ifconfig wlan0 up", viz: [root@slinux sluser]# `/sbin/ifconfig wlan0 down; /sbin/modprobe -r ath9k` [root@slinux sluser]# /sbin/modprobe ath9k; /sbin/ifconfig wlan0 up [root@slinux sluser]# exit Thanks for the suggestions Greg, but I can't tinker with the machine, given that it's a wrong specification and I expect it to be swapped for what was originally requested. Unfortunately, I now have to make do as everything is taking forever ... William. --- On Tue, 8/31/10, Greg Heilers <[log in to unmask]> wrote: > From: Greg Heilers <[log in to unmask]> > Subject: Re: Fw: 9825 wireless card auto disconnects! > To: "William Shu" <[log in to unmask]> > Date: Tuesday, August 31, 2010, 5:32 AM > I had trouble with the Atheros cards > when I installed Ubuntu on a friend's > Toshiba Laptop. On my own Dell laptop, the stock > Broadcom card gave > me trouble...so I simply bought an Intel card for about > $25.00, and it > works perfectly (running Slackware and Debian). I > have also often noticed > a great difference in performance of the wireless cards, > between a "Live DVD" > environment, and a full-blown hard-drive-installed > environment. > > Does it connect successfully to a "free and open" network, > such as at the library? > > My suggestion - see if you can find a cheap Intel card that > is compatible > with your Compaq. > > > > On Mon, 30 Aug 2010 08:59:31 -0700 (PDT) > William Shu <[log in to unmask]> > wrote: > > > Dear All, > > I forwarded this mail back in July buy got no reply. > So I can use the machine, does anyone have a workaround that > avoids changing/recompiling stock SL software/kernel? > (Googling seems to suggest there is a fundamental problem; I > lack the needed networking skills.) > > > > Many thanks > > > > William. > > > > --- On Wed, 7/21/10, William Shu <[log in to unmask]> > wrote: > > > > > From: William Shu <[log in to unmask]> > > > Subject: 9825 wireless card auto disconnects! > > > To: [log in to unmask] > > > Cc: "William S. Shu" <[log in to unmask]> > > > Date: Wednesday, July 21, 2010, 7:54 PM > > > Dear all, > > > I have an atheros 9825 wireless card (on a > compaq > > > CQ60-615DX) which is detected, but somehow fails > to connect > > > to -- or rather immediately disconnects > immediately from -- > > > the network when the password is given. I am > running it > > > using linux 5.5 livedvd, but the same device > connects > > > successfully under Windows7. > > > > > > It seems this issue was discussed sometime > before, but I do > > > not seem to find it. Any help appreciated. Below > are details > > > from wpa_supplicant.log and dmesg that I guess > are helpful. > > > > > > William. > > > > > > $ uname -a > > > Linux slinux 2.6.18-194.3.1.el5 #1 SMP Fri May 7 > 01:52:57 > > > EDT 2010 i686 i686 i386 GNU/Linux > > > > > > $ cat /var/log/wpa_supplicant.log > > > (wext) Device wlan0 kernel driver name: ath9k. > > > Device wlan0 kernel driver name: ath9k. > > > Trying to associate with 00:18:e7:01:64:af > > > (SSID='doit1wlan' freq=2437 MHz) > > > Associated with 00:18:e7:01:64:af > > > WPA: Key negotiation completed with > 00:18:e7:01:64:af > > > [PTK=TKIP GTK=TKIP] > > > CTRL-EVENT-CONNECTED - Connection to > 00:18:e7:01:64:af > > > completed (auth) [id=0 id_str=] > > > CTRL-EVENT-DISCONNECTED - Disconnect event - > remove keys > > > > > > > > > $ dmesg |tail -35 > > > r8169: eth0: link down > > > ADDRCONF(NETDEV_UP): eth0: link is not ready > > > ADDRCONF(NETDEV_UP): wlan0: link is not ready > > > ACPI: PCI interrupt for device 0000:00:1b.0 > disabled > > > PCI: Enabling device 0000:00:1b.0 (0000 -> > 0002) > > > ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 > (level, > > > low) -> IRQ 58 > > > PCI: Setting latency timer of device 0000:00:1b.0 > to 64 > > > hfs: unable to find HFS+ superblock > > > ACPI: PCI interrupt for device 0000:00:1b.0 > disabled > > > PCI: Enabling device 0000:00:1b.0 (0000 -> > 0002) > > > ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 > (level, > > > low) -> IRQ 58 > > > PCI: Setting latency timer of device 0000:00:1b.0 > to 64 > > > [drm] Initialized drm 1.0.1 20051102 > > > ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 > (level, > > > low) -> IRQ 74 > > > [drm] Initialized i915 1.8.0 20060929 on minor 0 > > > set status page addr 0x03fff000 > > > wlan0: direct probe to AP 00:18:e7:01:64:af (try > 1) > > > wlan0: deauthenticating from 00:18:e7:01:64:af by > local > > > choice (reason=3) > > > wlan0: direct probe to AP 00:18:e7:01:64:af (try > 1) > > > wlan0: direct probe responded > > > wlan0: authenticate with AP 00:18:e7:01:64:af > (try 1) > > > wlan0: authenticated > > > wlan0: associate with AP 00:18:e7:01:64:af (try > 1) > > > wlan0: RX AssocResp from 00:18:e7:01:64:af > (capab=0x431 > > > status=0 aid=1) > > > wlan0: associated > > > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes > ready > > > wlan0: no IPv6 routers present > > > wlan0: deauthenticating from 00:18:e7:01:64:af by > local > > > choice (reason=3) > > > > > > > > > > > > > > > > > > -- > > Greg Heilers > Registered Linux user #328317 > Slackware 12.2 (2.6.27.7) > Debian Lenny (2.6.27.7) > AUS > > For two incredible email programs: > http://sylpheed.sraoss.jp/en/ > http://www.mutt.org > > ..... > > > [after burying Gus by the stream in Texas] > Well, Gus; there you go. I guess this will teach me > to be more careful about what > I promise people in the future. > > -- Woodrow Call, in > Larry McMurtry's "Lonesome Dove" > >