Still with wifi connect issues LM17

[bombitmd]

I really, really tried reading and doing all the solutions on this forum and everywhere else on the Internet, but still nothing.

I have the same problem as some: After installing LM17 dual boot with Win7, I can only connect to my home WiFi and my phone hotspot. Anywhere else, I just can't connect. Even if I attach the cable in my clinic, still won't work. (It would show connected, but no data traffic at all.)

I'm currently using an Acer Aspire-M5-481TG, with 04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01).

I'm using my phone's wifi hotspot to post here.

-------------------------
* I. scanning WIFI PCI devices...
-- Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
==> PCI ID = 168c:0034 (rev 01)
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
eth0 no wireless extensions.
inter
lo no wireless extensions.

wlan0 IEEE 802.11abgn ESSID:"bmiss"
Mode:Managed Frequency:2.412 GHz Access Point: 84:38:38:10:D4:2D
Bit Rate=144.4 Mb/s Tx-Power=16 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=70/70 Signal level=-31 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:7 Invalid misc:8 Missed beacon:0

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 04:7d:7b:bc:4b:9d
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:18

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:65536 Metric:1
RX packets:295 errors:0 dropped:0 overruns:0 frame:0
TX packets:295 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:29213 (29.2 KB) TX bytes:29213 (29.2 KB)

wlan0 Link encap:Ethernet HWaddr 08:ed:b9:79:a8:27
inet addr:192.168.43.159 Bcast:192.168.43.255 Mask:255.255.255.0
inet6 addr: fe80::aed:b9ff:fe79:a827/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2937 errors:0 dropped:0 overruns:0 frame:0
TX packets:3354 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1389300 (1.3 MB) TX bytes:569820 (569.8 KB)

-------------------------
* V. querying DHCP...
RTNETLINK answers: File exists
-------------------------
* VI. querying nslookup google.com...
Server: 192.168.43.1
Address: 192.168.43.1#53

Non-authoritative answer:
Name: google.com
Address: 120.28.26.113
Name: google.com
Address: 120.28.26.104
Name: google.com
Address: 120.28.26.118
Name: google.com
Address: 120.28.26.89
Name: google.com
Address: 120.28.26.94
Name: google.com
Address: 120.28.26.109
Name: google.com
Address: 120.28.26.98
Name: google.com
Address: 120.28.26.84
Name: google.com
Address: 120.28.26.114
Name: google.com
Address: 120.28.26.103
Name: google.com
Address: 120.28.26.93
Name: google.com
Address: 120.28.26.99
Name: google.com
Address: 120.28.26.123
Name: google.com
Address: 120.28.26.119
Name: google.com
Address: 120.28.26.108
Name: google.com
Address: 120.28.26.88

[bombitmd]

Here's another diagnostic thingy

[bombitmd]

Ok, so I'm going to try to install the latest Broadcomm driver which I downloaded from their site. The version I have installed is 3.130, their version is 3.136; i'm hoping this might fix it.

My problem is, being an absolute newbie, I don't know how to, even with the given instructions. Am I supposed to install both t he RPM and Tar package? I don't seem to have RPM installed; is it a program? When i type it in the console it doesn't recognize it. If someone can edit the instructions below as to how I'm supposed to type it on the console? And what do they mean when they say "CD"?

many thanks! I also attached the entire README.TXT that came with the drivers

--------------------------------------------------------------------------
Installing Source RPM Package
=============================

The following are general guidelines for installing the driver.
1. Install the source RPM package:

rpm -ivh tg3-<version>.src.rpm

2. CD to the RPM path and build the binary driver for your kernel:

cd /usr/src/{redhat,OpenLinux,turbo,packages,rpm ..}

rpm -bb SPECS/tg3.spec

or

rpmbuild -bb SPECS/tg3.spec (for RPM version 4.x.x)

Note that the RPM path is different for different Linux distributions.

The driver will be compiled for the running kernel by default. To build
the driver for a kernel different than the running one, specify the
kernel by defining it in KVER:

rpmbuild -bb SPECS/tg3.spec --define "KVER <kernel version>"

where <kernel version> in the form of 2.x.y-z is the version of another
kernel that is installed on the system.

3. Install the newly built package (driver and man page):

rpm -ivh RPMS/<arch>/tg3-<version>.<arch>.rpm

<arch> is the architecture of the machine, e.g. i386:

rpm -ivh RPMS/i386/tg3-<version>.i386.rpm

Note that the --force option may be needed on some Linux distributions
if conflicts are reported.

The driver will be installed in the following path:

2.4.x kernels:

/lib/modules/<kernel_version>/kernel/drivers/net/tg3.o

2.6.x/3.x kernels:

/lib/modules/<kernel_version>/kernel/drivers/net/tg3.ko

4. Load the driver:

insmod tg3.o
or
insmod tg3.ko (on 2.6.x/3.x kernels)
or
modprobe tg3

5. To configure network protocol and address, refer to various Linux
documentations.


Building Driver From TAR File
=============================

The following are general guidelines for installing the driver.

1. Create a directory and extract the files:

tar xvzf tg3-<version>.tar.gz

2. Build the driver tg3.o (or tg3.ko) as a loadable module for the
running kernel:

cd src
make

The driver will be compiled for the running kernel by default. To build
the driver for a kernel different than the running one, specify the
kernel by defining it in KVER:

make KVER=<kernel version>

where <kernel version> in the form of 2.x.y-z is the version of another
kernel that is installed on the system.

3. Test the driver by loading it:

insmod tg3.o
or
insmod tg3.ko (on 2.6.x/3.x kernels)
or
insmod tg3

4. Install the driver:

make install

See RPM instructions above for the location of the installed driver.

5. To configure network protocol and address, refer to various Linux
documentations.
-----------------------------------------------------------------------------------

[bombitmd]

Connected!!!

I lost the link to where I read this solution, but here's what I did:

$ sudo gedit /etc/modprobe.d/wlwifi.conf

then added to conf. file
options iwlwifi 11n_disable=1

Hope someone else finds this helpful

[bombitmd]

That was short lived. Now I'm at another wifi area, and I can't connect. Same problem, keeps on asking for password. Damn. Is there no solution to this?!?!

[JeremyB]

You could set the IPv6 to ignore for your connection in Network Manager. One AP(hnharmony) might not work well as it is using a mixed mode encryption instead of strictly WPA2-AES. You can remove the broadcom drivers you installed as your wifi card is a Qualcomm Atheros AR9462 and the 11n_disable parameter only works for intel wifi but one parameter that might help with the Atheros card is

Code: Select all

echo "options ath9k nohwcrypt=1" | sudo tee /etc/modprobe.d/ath9k.conf

Code: Select all

sudo modprobe -r ath9k

Code: Select all

sudo modprobe ath9k

[bombitmd]

Thanks JeremyB for the reply. Unfortunately, still nothing. Right now I'm connected to my phone's hotspot. I tried to connect directly via cable earlier; also nothing. Only home wifi and phone hotspot seems to work. I haven't tried at Starbucks or anything; probably will endup the same.

[Koli14]

I tried all the solutions, nothing helped.
I always installed the newest kernel, but not helped until now.
I installed the newest kernel through 'Update Manager' -> View -> Linux kernels (3.16.0-33), and that's solved my issue.
After installing you need to rebuild the grub:

Code: Select all

sudo update-grub

.
Hope it's help.
Kolos