[all variants] Known Jaunty Wireless/Ethernet workarounds

[songmaster]

I've had significant difficulties getting my HP Pavillion dv7 laptop (ath9k) to stay associated with my Linksys WRT54G AP under Jaunty [Kubuntu]. My current workaround is to turn off Network Manager and connect manually. Although slightly annoying, at least it works and stays associated for several hours. The AP is not configured to use encryption (WEP, WPA or WPA2) and has essid broadcasts turned off. It also runs a DHCP server which gives me my IP address.

Here's what I do, in case it's useful to anyone else (these instructions are not specific to the ath9k, they may work on other systems with similar problems):

First remove any desktop widgets that connect to NetworkManager, they are likely to die at the first step below.

Then open a terminal window (Konsole on kubuntu) and run the commands shown in bold below (replace the text in bold italic with your AP's SSID). You'll get prompted for your password the first time you run sudo:

dv7$ sudo invoke-rc.d NetworkManager stop
[sudo] password for user:
 * Stopping network connection manager NetworkManager                    [ OK ]
dv7$ sudo iwconfig wlan0 essid 'YOURSSID'
dv7$ sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.1                                  
Copyright 2004-2008 Internet Systems Consortium.                                
All rights reserved.                                                            
For info, please visit http://www.isc.org/sw/dhcp/                              

Listening on LPF/wlan0/00:23:xx:xx:xx:xx
Sending on   LPF/wlan0/00:23:xx:xx:xx:xx
Sending on   Socket/fallback
DHCPREQUEST of 192.168.1.100 on wlan0 to 255.255.255.255 port 67
DHCPREQUEST of 192.168.1.100 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.100 from 192.168.1.1                       
bound to 192.168.1.100 -- renewal in 34171 seconds.
dv7$

The association with the AP doesn't occur until the dhclient runs above. You can check that it has worked using iwconfig — you're connected if you see the Access Point's MAC address on the second line of output (although if it failed, you won't have seen the DHCPACK line in the output above either):

dv7$ iwconfig wlan0
wlan0     IEEE 802.11abgn  ESSID:"<myEssid>"
          Mode:Managed  Frequency:2.422 GHz  Access Point: 00:13:xx:xx:xx:xx
          Bit Rate=54 Mb/s   Tx-Power=20 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B
          Power Management:off
          Link Quality=62/70  Signal level=-48 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
dv7$

- Andrew

[vegesm]

This fix is for the BCM4312 wireless card(maybe works for other BCM43xx cards). If you can join to the AP with SSID broadcast but not with hidden SSID this will help you:
http://worldofxor.blogspot.com/2008/...-wireless.html

[BigCityCat]

I'm posting this as a solution to broadcom 4328 driver issue. I use this on Kubuntu 9.04 with Kde 4.3. It may work on other distros. I don't know.

I am not an expert. I am posting a link from a thread I started where someone helped me fix this. So that the right person gets credit. The link does not have the whole solution. This post will. Only use this if your sure it fits your problem.

http://ubuntuforums.org/showthread.php?t=1238421

My dv 9700 laptop did not recognize any wireless. Ndiswrapper could not use any drivers that would work for my system. If you have ndiswrapper you need to purge it before you do this. The broadcom driver for my system does not support Linux as far as I know.

to purge ndiswrapper

sudo apt-get remove --purge ndis*

here is the next step.

sudo rmmod wl ssb

Sudo modprobe wl

iwconfig

lsmod | grep b43

lsmod | grep wl

Sudo ifup wlan0

sudo cat /var/log/messages | grep wl

sudo lshw -c networks

sudo kate /etc/modules

add the following

wl

at the end of the file in kate, and proof read save

sudo kate /etc/modprobe.d/blacklist.conf

add the following lines to the end of the file, proof read and save

blacklist ssb blacklist rmmod wl ssl blacklist b43legacy blacklist b43

sudo rmmod wl ssb

sudo modprobe wl

sudo kate /etc/rc.local

add the following lines at the end of the file but before "exit 0" proof read and save.

rmmod wl ssb sleep 3 modprobe wl

restart and see

Now that worked for me. Like I said Chili555 is the one who solved this for me.

[chili555]

There are one or two misleading things here. Purge ndiswrapper as he said. Then sudo kate /etc/modules to add a new line:

wl

Not Kate, but kate and not WL, but wl.

His blacklist.conf is correct.

Evidently, the module ssb loads even if it's blacklisted (go figure), so we must sudo kate /etc/rc.local to add:

rmmod wl ssb
sleep 3
modprobe wl

Add it right above 'exit 0' As always, proofread carefully, save and close kate. After a reboot, your wireless should work correctly.

NB!!! This works, as far as I know, for the Broadcom 4328 only.

[BigCityCat]

Originally Posted by chili555 There are one or two misleading things here. Purge ndiswrapper as he said. Then sudo kate /etc/modules to add a new line: wl Not Kate, but kate and not WL, but wl. His blacklist.conf is correct. Evidently, the module ssb loads even if it's blacklisted (go figure), so we must sudo kate /etc/rc.local to add: rmmod wl ssb sleep 3 modprobe wl Add it right above 'exit 0' As always, proofread carefully, save and close kate. After a reboot, your wireless should work correctly. NB!!! This works, as far as I know, for the Broadcom 4328 only.

Fixed and as always, thanks.

[BigCityCat]

I noticed there is a small issue with the modules blacklisted in blacklist.conf

blacklist rmmod wl ssl

should read

blacklist rmmod wl ssb

but I actually copied and pasted my file into this solution so that is how it is on my system and it is working. I have no intention on changing it for now.

[rtrdom]

Using both Thinkpad R61i with Intel PRO Wireless 4965 AG or AGN wireless adapter, and a Compaq X1030US with Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04). I tried several hours to find the problem
with the computers which both would access a NETGEAR Model WPN802 V2 while in Windows (both computers are dual boot because I teach basic Windows to old folk) but would see and NOT access in UBUNTU. Finally solved problem.... I took both computers to other open networks and they
both worked flawlessly in either OS. Took both computers to my encrypted
(WPA2 static IP) network and they worked flawlessly without any adjustment. Problem.... WPN802 V2 is/has going/gone bad. It
has quit working (accepting) from my Ubuntu 9.04 but works with Windows XP.
Another item. An early model of WRE54G was not "syncing" with the access
point, even when reset by directions.
Hope this helps someone else.

[Feareilo]

Output of lsusb:

Bus 002 Device 012: ID 03eb:7614 Atmel Corp. AT76c505a Wireless Adapter
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 049f:000e Compaq Computer Corp. Internet Keyboard
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I don't know what this all means but I'm using an SMC EZ Connect Wireless USB adapter. Model number: SMC2662W.

Problem: In Ubuntu 8.04 (Hardy Heron) I couldn't connect through the Network Manager so I used to type this in a terminal:

sudo ifconfig wlan0 down
sudo dhclient -r wlan0
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid "Networ-name"
sudo iwconfig wlan0 key open PASSWORD
sudo dhclient wlan0

However, this didn't work in Ubuntu 9.04 (Jaunty Jackalope).

My wireless card is connected via USB and it has two leds: a red one and a green one. I always use the Internet so I don't see any point in disconnecting it, even when the computer is off. Whenever I turned on the computer, both leds used to turn on in my USB card. That changed with Jaunty. Now only the red one turns on and I can't connect with neither the Network Manager nor the thing I typed in the terminal.

Partial Solution: Disconnect the card and reconnect it until the green led turns on too. This way, I now can connect to the Internet using the Network Manager.
If anyone knows a better solution please tell me.

EDIT: By the way, I'm dual booting Ubuntu 9.04 and UbuntuStudio 8.04 and this problem only happens with Jaunty.

[jbrice]

Dell Inspiron 1525 - with standard Intel Pro Wireless card 3945ABG - connects to our WPA-secured Netgear router reliably and quickly on system boot. However on resume from suspend, it seems to take a random period of time before it tries to re-connect (which it always succeeds in doing - eventually). This can be almost instantaneous (hurrah!), minutes (oh hurry up!), or lots of minutes (aargh, should have used WinXP).

This PC uses the standard Jaunty install double-booted with WinXP - the latter always connects quickly and reliably with the same router.

Is this a manifestation of any of the problems listed in this thread, or something different?

James B.

[uylug]

Wireless connection has a high packet loss rate using a TrendNet 424UB v3 on Jaunty using the rtl8187 built in module.

Solution:

Run this command after connecting to WiFi

sudo iwconfig <interface> retry <high_value>

Like

sudo iwconfig wlan0 retry 999999