Driver Wifi Toshiba Satellite Ubuntu Linux
Toshiba Forum - Satellite L450D - Need Wireless driver for Linux system - Hi, I have a satellite L450D, with a Realtek RTL8191SE wireless card (windows 7). Toshiba Satellite U300-11S. The wireless adapter works with a non free driver. I followed this http://www.itopen.it/2007/11/22/ubuntu-linux-toshiba-satellite.
To all the great ubuntu gods, geeks, gurus, experts, and all around good folks that are found around here. Having a horrible wireless disconnect issue, and after months of dealing with it, days of research, configuring, etc, it STILL goes on. ANY help, suggestions, questions, comments, further reading, etc etc would be GREATLY appreciated. Beyond real solutions, any workarounds, etc, would also be useful. Specifically, ways to reset the hardware without having to reboot would be useful here are the details. Currently on a fresh install of ubuntu 12.04 LTS 64 bit (had same problem with older install of 32 bit version of same) running a toshiba satellite L550. Using an intel Ultimate N WiFi Link 5300 wireless card, driver=iwlwifi driverversion=3.8.0-30-generic previously had in this system RTL8291SE card, replaced with above after similar disconnect problems, assuming the Intel chipset would have less compatibility issues.
What I get, is what seems to be random disconnects, and generally can't get connected again until after a reboot. Wireless will work well for anywhere from a few minutes to a few days, and work well under heavy load. I'm not sure how to trigger it to disconnect. Sometimes, after a disconnect I can connect again by removing & adding the driver using modprobe, but rarely does that work, a reboot is most often required. Doesn't seem to be related to any power management or that type of thing. Looks like it happens when system is idle, or active, on a/c power or on battery. Below is a syslog showing one of these disconnects.
It looks to me, like the card itself is shutting down, then can't be started up again? I'm no expert on this stuff, obviously, so I could be wrong.
Toshiba Wifi Driver Download
I've been assuming all along this is a driver/compatibility type issue. Can anyone confirm this, or suggest otherwise? Hardware problem (bad port/motherboard?
Wireless card?)? Could ubuntu 13.04 maybe help? Will post anything else that might be relevant or might help, please request. THANKS FOR READING! Sep 19 23:59:26 tosh kernel: 211.824248 iwlwifi 0000:06:00.0: fail to flush all tx fifo queuesSep 19 23:59:28 tosh kernel: 213.823426 iwlwifi 0000:06:00.0: Error sending REPLYADDSTA: time out after 2000ms.
Sep 19 23:59:28 tosh kernel: 213.823437 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 188 Sep 19 23:59:28 tosh kernel: 213.823446 wlan0: HW problem - can not stop rx aggregation for tid 0 Sep 19 23:59:30 tosh kernel: 215.826600 iwlwifi 0000:06:00.0: Error sending REPLYADDSTA: time out after 2000ms. Sep 19 23:59:30 tosh kernel: 215.826609 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 191 Sep 19 23:59:30 tosh kernel: 215.826616 wlan0: failed to remove key (0, 00:22:2d:6b:e4:29) from hardware (-110) Sep 19 23:59:32 tosh kernel: 217.829691 iwlwifi 0000:06:00.0: Error sending REPLYQOSPARAM: time out after 2000ms. Sep 19 23:59:32 tosh kernel: 217.829699 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 194 Sep 19 23:59:32 tosh kernel: 217.829703 iwlwifi 0000:06:00.0: Failed to update QoS Sep 19 23:59:34 tosh kernel: 219.828810 iwlwifi 0000:06:00.0: Error sending REPLYRXON: time out after 2000ms. Sep 19 23:59:34 tosh kernel: 219.828821 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 197 Sep 19 23:59:34 tosh kernel: 219.828829 iwlwifi 0000:06:00.0: Error clearing ASSOCMSK on BSS (-110) Sep 19 23:59:36 tosh kernel: 221.828039 iwlwifi 0000:06:00.0: Error sending REPLYRXON: time out after 2000ms.
Sep 19 23:59:36 tosh kernel: 221.828048 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 200 Sep 19 23:59:36 tosh kernel: 221.828053 iwlwifi 0000:06:00.0: Error clearing ASSOCMSK on BSS (-110) Sep 19 23:59:38 tosh kernel: 223.827213 iwlwifi 0000:06:00.0: Error sending REPLYRXON: time out after 2000ms. Sep 19 23:59:38 tosh kernel: 223.827221 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 203 Sep 19 23:59:38 tosh kernel: 223.827226 iwlwifi 0000:06:00.0: Error clearing ASSOCMSK on BSS (-110) Sep 19 23:59:40 tosh kernel: 225.826338 iwlwifi 0000:06:00.0: Error sending REPLYADDSTA: time out after 2000ms. Sep 19 23:59:40 tosh kernel: 225.826349 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 205 Sep 19 23:59:40 tosh kernel: 225.826368 wlan0: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-110) Sep 19 23:59:42 tosh kernel: 227.833434 iwlwifi 0000:06:00.0: fail to flush all tx fifo queues Sep 19 23:59:44 tosh kernel: 229.832567 iwlwifi 0000:06:00.0: Error sending REPLYRXON: time out after 2000ms. Sep 19 23:59:44 tosh kernel: 229.832581 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 206 Sep 19 23:59:44 tosh kernel: 229.832591 iwlwifi 0000:06:00.0: Error clearing ASSOCMSK on BSS (-110) Sep 19 23:59:46 tosh NetworkManager1007: (wlan0): roamed from BSSID 00:22:2D:6B:E4:29 (NETWORK) to (none) ((none)) Sep 19 23:59:46 tosh wpasupplicant1258: CTRL-EVENT-DISCONNECTED bssid=00:22:2d:6b:e4:29 reason=4 Sep 19 23:59:46 tosh kernel: 231.831720 iwlwifi 0000:06:00.0: Error sending REPLYSCANCMD: time out after 2000ms.
Sep 19 23:59:46 tosh kernel: 231.831728 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 207 Sep 19 23:59:46 tosh kernel: 231.831761 cfg80211: Calling CRDA for country: US Sep 19 23:59:46 tosh NetworkManager1007: (wlan0): supplicant interface state: completed - disconnected Sep 19 23:59:48 tosh wpasupplicant1258: Failed to initiate AP scan. Sep 19 23:59:48 tosh kernel: 233.930828 iwlwifi 0000:06:00.0: Error sending REPLYSCANCMD: time out after 2000ms. Sep 19 23:59:48 tosh kernel: 233.930838 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 208 Sep 19 23:59:51 tosh wpasupplicant1258: Failed to initiate AP scan. Sep 19 23:59:51 tosh kernel: 236.929580 iwlwifi 0000:06:00.0: Error sending REPLYSCANCMD: time out after 2000ms. Sep 19 23:59:51 tosh kernel: 236.929594 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 209 Sep 19 23:59:54 tosh wpasupplicant1258: Failed to initiate AP scan. Sep 19 23:59:54 tosh kernel: 239.928333 iwlwifi 0000:06:00.0: Error sending REPLYSCANCMD: time out after 2000ms. Sep 19 23:59:54 tosh kernel: 239.928345 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 210 Sep 19 23:59:57 tosh wpasupplicant1258: Failed to initiate AP scan.
Sep 19 23:59:57 tosh kernel: 242.927087 iwlwifi 0000:06:00.0: Error sending REPLYSCANCMD: time out after 2000ms. Sep 19 23:59:57 tosh kernel: 242.927098 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 211 Sep 20 00:00:00 tosh wpasupplicant1258: Failed to initiate AP scan. Sep 20 00:00:00 tosh kernel: 245.925774 iwlwifi 0000:06:00.0: Error sending REPLYSCANCMD: time out after 2000ms. Sep 20 00:00:00 tosh kernel: 245.925785 iwlwifi 0000:06:00.0: Current CMD queue readptr 182 writeptr 212 Sep 20 00:00:01 tosh wpasupplicant1258: Failed to initiate AP scan. Sep 20 00:00:01 tosh kernel: 246.926939 iwlwifi 0000:06:00.0: No space in command queue Sep 20 00:00:01 tosh kernel: 246.926955 iwlwifi 0000:06:00.0: Restarting adapter queue is full Sep 20 00:00:01 tosh kernel: 246.926975 iwlwifi 0000:06:00.0: Error sending REPLYSCANCMD: enqueuehcmd failed: -28 Sep 20 00:00:02 tosh NetworkManager1007: (wlan0): link timed out. Only mere mortals read these forums, so you will have to accept less than divine advice.
Errors like failed to load firmware would point to a hardware problem. The fact that you have tried 32-bit and 64-bit distros and 2 different wireless cards with similar results. I presume that the wireless card is on a minipci slot under the RAM or harddisk? Perhaps there is dirt, or a bent pin on the slot? Pull the wireless card, blow out any dust, and inspect with a bright light and magnifying glass.
I suspect a bad connector that is causing an intermittent wireless connection. If all of that checks out, then I suspect a poor solder connection of the connector slot to the motherboard, or a flexed/cracked motherboard that affects that circuit.
Does the laptop work OK using a wired connection? Any hard freezes?
Do you get several months of uptime while running linux? Only mere mortals read these forums, so you will have to accept less than divine advice. Errors like failed to load firmware would point to a hardware problem. The fact that you have tried 32-bit and 64-bit distros and 2 different wireless cards with similar results.
I presume that the wireless card is on a minipci slot under the RAM or harddisk? Perhaps there is dirt, or a bent pin on the slot?
Pull the wireless card, blow out any dust, and inspect with a bright light and magnifying glass. I suspect a bad connector that is causing an intermittent wireless connection. If all of that checks out, then I suspect a poor solder connection of the connector slot to the motherboard, or a flexed/cracked motherboard that affects that circuit. Does the laptop work OK using a wired connection? Any hard freezes?
Ubuntu Wifi Drivers Download
Do you get several months of uptime while running linux? Mortal or divine, I'll take any help/suggestions that come my way. Mini pci slot, (actually half size mini pci e), but located under the keyboard up, not with the ram or harddisk. Have inspected it just now, and previously, and see nothing out of the ordinary. Nothing that looks bent or damaged, no dirt/dust. Blew it out with duster anyway, re-installed.
One note, have only tested this one card on 64 bit thus far. The first one, I replaced due to many reports/threads of disconnect & driver issues, so I've not yet brought it back into the testing. Will put it on the list though. No other issues with the system to speak of, no freezes, and while on wired connection, no issues (however 99% of the time I'm having to use wireless, so not tested much). Uptime not measured in months, only because I'm frequently rebooting to get my wireless back.
Generally several reboots/day. Will try to run long enough test on just a wired connection, but will be difficult one thing that I find odd, when you mention the 'failed to load firmware' part, to me, it looks like for some reason it's decided to re-start or disable/enable the hardware at that point, but it just didn't come back up. Or would you think it's failing or not responding before that? Waiting now until it fails again, to move on to next test. The Linux Kernel was written by Gods, and as a result it expects perfect hardware.
Linux Wifi Driver Download
When hardware is not perfect, you get a variety of weird, somewhat reverent, somewhat relevant (to see if you were paying attention), errors that may or may not be related to the hardware fault. So, you have to take the error messages with a grain of salt. Because of the variety of error messages, it appears to be a hardware error. Which is why you want to test for uptime on a wired cable for a few months. That's right, a few months.
If your machine doesn't stay up for a few months at a time, then you might have a motherboard issue that is affecting your wireless connectivity. Wireless chips get hot under use.
Perhaps you can put your finger on it while the keyboard is removed. Use a USB keyboard instead and see if the chip gets hot during use. If it does, then you might have a wireless card problem. Although it would be unusual to have two cards go bad. I have had pcmcia wireless cards go bad, the chip gets hot and acts strange. Only a reboot, or pulling the card (which allows it to cool down) will revive it.
Not a useful way to work. If the keyboard presses against the card, it's possible that flexing of the keyboard has weakened the socket.
Try putting a little pressure on it with your finger and see if behaves differently. 17' laptops tend to flex more than 15' and smaller and tend to develop strange problems as a result. But first do as Hadaka suggests, turn off N mode and see it changes the wireless behavior.