Ubuntu

Wireless on Toshiba Satellite Pro 4600

Asked by earthforce_1

The wireless interface does not work under gutsy - cannot see any wireless networks at all. The upgrade broke the wireless interface and it hasn't worked since.
This was filed under https://bugs.launchpad.net/ubuntu/+bug/151455

This was working perfectly under feisty, I was told to ask here because they said it was not a actually a bug? Working->Not working = major regression.
Has anybody else got the interface working at all on this laptop?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
earthforce_1
Solved:
Last query:
Last reply:
Revision history for this message
purrcher (jkleinschmidt) said : 		#1

I've had a similar problem with my build in wireless but the restricted driver fixed it. How ever the problem I'm having is that my wireless doesn't have as long of a range as it does in windows. As much as I don't like it.

Revision history for this message
earthforce_1 (earthforce1) said : 		#2

Am doing a complete reinstall from the gutsy CD - I can confirm that the alternate install CD does NOT recognize the wireless interface. One I have finished the reinstall (mirrors are very slow tonight, as the final has just been released) I will see if I can get this working first with the built in drivers, then with restricted drivers as you suggested.

Revision history for this message
earthforce_1 (earthforce1) said : 		#3

Nope, still doesn't work under a fresh install. How did you install the restricted driver? The only one offered in the menu was for the software modem.

Revision history for this message
Vic (vice-yo) said : 		#4

Hi,

Can you tell us which wireless card you have?

Revision history for this message
earthforce_1 (earthforce1) said : 		#5

It was the built in one, and it is finally working, it seems a neighbour started up another 802.11 network on the same channel while I was waiting for the orinoco_cs.ko drivers to be fixed. Moved from channel 1 to 10 and things started working again.

Revision history for this message
earthforce_1 (earthforce1) said : 		#6

BTW, thanks for your help. Sorry this one turned out to be a false alarm.