Problems with Toshiba C655-S5049 and Atheros AR9285 wireless controller
I've installed Ubuntu 10.4 on a Toshiba Satellite C655-S5049 laptop and cannot get the laptop to connect via WiFi.
It has an Atheros AR9285 Wireless Network Adapter (PCI-Express), which does *say* that it is connected (while at Starbucks), but I can't get any throughput (via FireFox, ping, etc).
This was while I was trying to connect to the free WiFi at Starbucks, and the guy at the next table over was having no problems whatsoever. So it isn't a Starbucks problem...
I then took the laptop to work and tried to connect it to the WiFi there. This isn't an open network, so I had to configure it with not only the SSID, the password, the wireless security, and IP settings as well. I have a work laptop which is running Ubuntu 10.4 (which is what I am using at the moment), so I was able to copy the settings from that laptop.
Trying to connect to the work network eventually gives me a timeout and a request for the password (which I have quadruple-checked to make sure that it is correct).
I am currently connected to a wired network where I am doing a network install of OpenSuSE in the hopes that it has a better driver for this card.
I have the same wireless device on my netbook, which I am using now.
I am using SuSE 10.3. I think you may need to upgrade to SuSE 10.2 or newer for this wireless device to be detected. It uses the same ath9k kernel module, but, IIRC, your kernel's ath9k module may not support this model.
I think that I had upgraded to a newer kernel back when I bought this netbook and was using 10.1.
/sbin/lspci will list the devices. Note the pci address for the atheros device. Then run /sbin/lscpi -n to list the manufacturer code. If you have your kernel source installed, scan through the
/lib/modules/$(uname -r)/source/drivers/net/wireless/ath/hw.h file.
Okay, I just now did a "serious" install of OpenSuSE 10.3 on my friends' laptop (one with the partitions setup the way that I wanted them, and the packages I thought that he could use). I executed the commands that you suggested and found the controller at: 03:00.0. And running /sbin/lspci -n gives me: "03:00.0 0280: 168c:002b (rev 01)". This will now be the distro that he uses. ;>
Digging through the sources does not come up with a "hw.h" file in the location you pointed me to, but it does show up in .../wireless/ath/ath9k/hw.h. And inside this file it does include the #define statement that you listed (#define AR9285_DEVID_PCIE 0x002b).
Running dmesg | grep 9285 comes up with this:
[ 11.910086] phy0: Atheros AR9285 Rev:2 mem=0xf9080000, irq=11
So the system "sees" it okay, but judging by all of the irq faults in dmesg, the kernel seems to be having some problems setting irq's. I found this using dmesg:
[ 11.550124] ath9k 0000:03:00.0: can't find IRQ for PCI INT A: probably buggy MP table
I just rebooted the PC with acpi=off, and while the blasted thing booted up better, and quicker, it still won't connect. However, the "Scan" feature on the Wireless setup tool found our two networks here at work, and the applet shows the relative strength of the signal. This is weird...
Thanks for the help!
BTW, I like your little tip in your sig "man -Tps <topic> | okular -" Handy :)
There are less drastic acpi kernel boot options then noacpi. I find often that nolapic will fix hardware boot problems. It sounds like you have a very buggy bios. You might want to see if there is a firmware update available on the toshiba website.
I found this link:
http://forums.opensuse.org/english/g...-problems.html (post #2)
Which led me to the patched kernel (to fix the Toshiba BIOS problems). I installed it, and Yast created the kernel, etc, but didn't follow through with running grub-install so that I could boot it up with the new kernel. Trying to run Yast's Boot Manager within Yast, would cause the Boot Manager to hang at 33% completion. Trying to run grub manually didn't work (I forget what the error was, but it amounted to not being able to locate the drive in the BIOS).
Sooo, I noticed that Ubuntu 10.10 beta is out, and it has the kernel that I needed, so (after about six tries - they don't call it beta for nothing), I managed to get that installed.
Still no WiFi, but it does connect to eth0, which is way better than nothing.
I'm going to try connecting to WiFi using the traditional manner next (ifup) to see if I can work around whatever bugs are left with the WiFi controller.
But right now, it's off to bed. 13 hours in front of a POS Toshiba is enough for anyone. :)
I'll look at the acpi options (tomorrow?) and see if I can be more selective as to what I'm man-handling.
Thanks again for all of your help. :)
|All times are GMT -5. The time now is 12:15 PM.|