Toshiba Satellite Pro 4600 Wireless broken

Bug #151455 reported by earthforce_1
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Running kernel 2.6.22.14-generic;

Wireless does not connect to a 64 bit WEP encrypted LAN - this used to work in Feisty.

Running /etc/init.d/networking restart yields an interesting error message:
wlan0: ERROR while getting interface flags: No such device
Error for wireless request "Set Encode" (8B2A) :
SET failed fpr devoce wlan0; No such device
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; No such device.
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519120
Internet Systems Consrtium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For into, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0

As I recall under Feisty, the wireless looked like another Ethernet port. when I ran ifconfig. I still see eth0 and eth1, but both are unconfigured according to ifconfig. The chip only supports 64 bit encryption, but at least it is better than nothing!

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not have enough information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "lsmod" in your next response.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Please run the command "lsmod > lsmod.log" and attach the resulting file "lsmod.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Revision history for this message
earthforce_1 (earthforce1) wrote :
Revision history for this message
earthforce_1 (earthforce1) wrote :
Revision history for this message
earthforce_1 (earthforce1) wrote :
Revision history for this message
earthforce_1 (earthforce1) wrote :
Revision history for this message
Basilio Kublik (sourcercito) wrote :

why are you trying to connect using wlan0?, the dmesg log shows eth1 as the orinoco wireless card., are you trying to use another card, maybe a usb one?

Revision history for this message
earthforce_1 (earthforce1) wrote :

I believe you are correct - eth1 is the built in wireless interface, and no - I was not trying to use a USB wireless device. In fact, I have to use an external adapter on eth0 to get any connectivity at all. This interface did work perfectly in feisty. It sees the wireless interface is now seen to exist, but reports no signal at all and I cannot connect to my wireless LAN.

Revision history for this message
earthforce_1 (earthforce1) wrote :

Is there any more information you need from me? I assume I still set my WEP code in the wireless settings box under Network settings. Unfortunately, it still doesn't work. This was one of the tested and certified laptops for Feisty.

Revision history for this message
earthforce_1 (earthforce1) wrote :

One more thing - when I run /sbin/etc/init.d/networking restart, it seems to be trying to set the ESSID for wlan0, although as you pointed out, the actual wireless interface is on eth1 - at least it appeared as such under feisty.

The network manager icon shows wireless with empty bars (0%) and no networks available, even though I know there are 2 or 3 within range. I have tried with the wired connection disabled, roaming, and enabled to no avail. I have tried to find the wireless networks both in roaming and manually configured mode. I have all the latest updates as of Oct. 14th evening.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
it seems that the problem is a leftover configuration, could you check if you have a "wlan0" interface configured or mentioned at /etc/network/interfaces, if so, could you please delete it, or change by eth1 and try again.

Revision history for this message
earthforce_1 (earthforce1) wrote :

Done. It seems to know the network is there, but doesn´t have a channel or ESSID associated with it.

There was an old thread at
http://ubuntuforums.org/showthread.php?t=328079 that discussed wireless issues with this same laptop. Surely it is a bug if I cannot set this up properly via the network interface gui? They seemed to get it running at the time with some sudo iwconfig scripts using the same wlan0 you suggested I delete from /etc/network/interfaces.

I hope the following info helps:
$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:00:39:B9:47:3C
          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)

eth1 Link encap:Ethernet HWaddr 00:02:2D:13:12:31
          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:11 Base address:0xd100

eth1:avah Link encap:Ethernet HWaddr 00:02:2D:13:12:31
          inet addr:169.254.1.211 Bcast:169.254.255.255 Mask:255.255.0.0
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          Interrupt:11 Base address:0xd100

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:122 errors:0 dropped:0 overruns:0 frame:0
          TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10628 (10.3 KB) TX bytes:10628 (10.3 KB)

$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11b ESSID:"" Nickname:"HERMES I"
          Mode:Managed Frequency:2.457 GHz Access Point: None
          Bit Rate:2 Mb/s Sensitivity:1/3
          Retry limit:4 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=0/92 Signal level=134/153 Noise level=134/153
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

gary@Lennier:~$

Revision history for this message
earthforce_1 (earthforce1) wrote :

Addendum: I can set the ESSID with the network interface applet, (shows up in ESSID and encryption key field of eth1, but no change in any other field. In roaming mode, I cannot see any other wireless network in the area, and I could find 3 to 5 networks (some encrypted, some not) using the same laptop under feisty when I enable roaming mode.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
This actually doesn't seem to be a bug, and it make more sense to raise a question at the support tracker https://answers.launchpad.net/ubuntu, so everyone with this issue could benefit from the response.
I'm closing this bug report as invalid, please do ask your question at the support tracker so you can solve this issue. Thanks again for taking the time to report this issue and help to make Ubuntu better. Feel free to continue to report any other bugs you may find.

Revision history for this message
earthforce_1 (earthforce1) wrote :

Update:
I did a complete wipe and reinstall using the gutsy alternate CD and can confirm that the built in wireless inteface does NOT work when network setup is prompted by the debian installer, and did work out of the box with feisty. See https://wiki.ubuntu.com/LaptopTestingTeam/ToshibaSatellitePro4600 It is not a misconfiguration, and I expect my results will be perfectly reproducible if the tests on this page are repeated.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
Thanks for the update, i'm re-open this bug regarding your last comment, could you please update the wiki with your finds in gutsy?, if you can test with the Gutsy Gibbon livecd also would be great.
Could you include your syslog as attachment for now?, hopefully after you try to associate to the network a couple of times. Are you using network-manager to join the network or are you doing so via commands?.

Thanks in advance.

description: updated
Revision history for this message
earthforce_1 (earthforce1) wrote :

Thanks for taking a look at this, as it is a serious regression for me and/or anybody else with similar laptops. (I am posting this from the laptop in question with a wired link to gain network access) I have updated the wiki, (They did not have an column for gutsy, so I had to add it, hope I did it right) and have attached what few tests I have done so far in gutsy. My syslog file is attached to this entry.
As I mentioned, the network configuration option of the alternate install CD failed to detect and/or connect to the wireless network. (I have 64 bit WEP enabled, which is the strongest encryption supported by this model)
After installation in roaming mode I don´t see any networks reported, even though my signal should be fairly strong. (Mixed B/G enabled)

I am indeed using the network-manager to set up my connection - I am familiar with iwconfig and tried it before the reinstall without success. Once I manually enter my ESSID and WEP key it seems to see the network, and shows 4 blue bars instead of the network icon which should be a good sign, (hovering the cursor over it indicates connected at 87% strength) but there is not connection. After submitting the file you requested, I will try again with the wired connection disabled, and if I can with the live CD.

Revision history for this message
earthforce_1 (earthforce1) wrote :

Ok, posting from another machine because the wired link is now disabled on the laptop. Roaming mode did not immediately identify any networks selectable, (I could usually see 2 or 3 with feisty) so I manually entered my ESSID and WEP key. I see the 4 blue bars in the network manager icon, but when I click on it it it shows my network with a shield icon and no horizontal bars. (all white) ifconfig reports no connection, iwconfig reports Link Quality 8/92 Signal level 134/153 and Noise level 134/153 Bit Rate 2 Mb/s and Frequency 2.412 GHz which is correct. (My network uses channel 1) Sensitivity 1/3 Access Point: None

I know the network signal and base station setup is good, I have another gutsy desktop with a linksys wireless 802.11b USB adaptor located much further from the base station with no problems connecting.
Live 7.10 CD hangs on startup with corrupted screen, so it was impossible to test. Looks like 256M of RAM doesn't cut it. Noted on wiki page. I tried to recheck if the wireless worked directly from the 7.04 live CD, but this also hung on startup - I installed this from the alternate install CD as well.

Revision history for this message
earthforce_1 (earthforce1) wrote :

A bit more info:
Turning all security off doesn't help. It seems to know the signal is there, and reads as 4 bars (87%) in the network-manager toolbar icon, but the network shows as 0 bars in the pull down menu when I click on it. I tried switching channels from 1 to 10 and tried changing between Open and Shared Key. ifconfig shows that it does not obtain a dhcp address.

I have Win 98/ME/NT/2000 Toshiba drivers from one of the disks that came with the thing, and tried to install them with ndiswrapper. In each case, ndiswrapper claimed the .inf file was invalid for some reason.

Revision history for this message
earthforce_1 (earthforce1) wrote :

Finally was able to get it working - I think it was interference from a conflicting network that had started broadcasting nearby, during the time the orricono driver was broken and mising so it still looked broken even after the driver was fixed. (Because it had been working before, and other wireless PCs using 802.11g were less affected.) Switched from channel 1 to channel 10 and ensured CTS protection mode was enabled in my WL router.

Revision history for this message
earthforce_1 (earthforce1) wrote :

Well also update the Wiki page...

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Glade to know you solve your problem, and thanks for updating the information at the wiki. Feel free to report any future bugs you might find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.