I’m trying to get my Dell Latitude work with wifi speed >54Mbit/s, and up to now without any success. The router is a Dlink DIR-635, it has ‘n’ enabled and working (got an apple laptop connecting at 130Mbit/s, can’t test the actual throughput though, since it’s the only high-speed device).
Here’s the device data:
0c:00.0 Network controller: Intel Corporation WiFi Link 5100
Subsystem: Intel Corporation WiFi Link 5100 AGN
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f1ffe000 (64-bit, non-prefetchable) [size=8]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-24-d6-ff-ff-8e-01-28
Kernel driver in use: iwlagn
I’m running 11.4, added the compat-wireless recently to be able to run the newes firmware (iwlwifi-5000-5.ucode , firmware version 8.83.5.1 build 33692), but still all I get is 54Mbit/s. I’d like to know if ANYONE ever got the 802.11n speed on linux, and in particular with these intel cards.
Its interesting you have had success here with the 5100 AGN. A number of users have reported constant drop outs (requiring a reboot each time) with the 5100/5300 AGNs. I experienced same with 11.4 KDE liveCD with a 5300AGN, but I did not have problems with an 11.4 Gnome liveCD with same 5300 AGN.
May I ask what desktop you are using ? Gnome ? KDE4 ?
I’m also wondering if this is related to the “firmware version 8.83.5.1 build 33692” that you noted in your post. May I ask where you obtained that firmware from ? ( oldcpu being hopeful that the final long awaited firmware update to fix the drop outs that many have experienced has finally arrived ).
It’s KDE4, the official 4.6 coming with 11.4 (I stopped using Gnome few years ago, when after each upgrade the whole desktop was getting messed up).
I downloaded the firmware from http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-5000-ucode-8.83.5.1-1.tgz
To load it I had to install the compat-wireless* packages from driver:wireless repository.
In fact I can’t say yet that I have no dropouts since I managed to make the 11n speeds working only last night and don’t have enough experience yet. What I can say for sure is that at 11g (54Mbit/s) speed things worked fine, very rarely I had problems with knetworkmanager, and had to switch to Gnome nm-applet instead (which stopped working for me since last update). Frankly speaking, all the development in network manager applets sucks, it only got worse and worse since kde3. But this is an offtop probably
I’m not at a Linux PC currently. When I get home I will have to download that tarball and see if there is a release note inside which explains the changes.
There’s no changelog, unfortunately, only a useless readme and license…
BTW, I seem to have the dropouts, too. But for a short time only, no reboot required. Once I had to run rcnetwork restart to get things back…
For example this quote from that Bug 16691 report:
I’m fortunate I don’t have the Intel WiFi drop out problem on openSUSE-11.3 KDE, but because I did experience the drop out problem on openSUSE-11.4 KDE (on my Dell Studio 1537 laptop with the Intel WiFi 5300AGN) during liveCD testing, I have not installed 11.4 on that laptop.
From my read now, it appears I can’t expect 8.83.5.1 to solve the connection problems (although I’m also not convinced the 11.4 KDE connection problems were the Wifi device - as I had no such problems with 11.4 Gnome liveCD - and ergo 11-4 Gnome is an option for me to install on this laptop to replace 11.3 KDE if this problem is not fixed within 8-months or so (when openSUSE-11.3 support stops)).
15 minutes?! I’m having dropout problems perhaps once in a week! With the 11n upgrade I’ll have to see though, but I surely run hours without problems…
Just to re-iterate, bug https://bugzilla.novell.com/show_bug.cgi?id=675433 was written on openSUSE-11.4 drop outs with the Intel WiFi Link 5100. I noted on the bug report that with the Gnome liveCD for openSUSE-11.4 that I obtained no drop outs with Gnome, but I did experience drop outs with KDE liveCD for openSUSE-11.4.
I believe my own issue was related to the kernel-firmware package.
I removed the package and used the ralink-firmware in the wireless repo and I believe it is ok.
I haven’t had the time to test it enough to say for certain, but by reinstalling the kernel-firmware the problem did reoccur immediately.
Maybe you could check if the said package is installed in the live kde / live gnome
I believe there is no extra firmware package for the intel card as it’s supposed to be included in the kernel since 2.6.24
This bug has nothing to do with firmware or channel neither mode abg or N
This is definitely an OpenSuse issue, wifi can’t work neither with ifup nor networkmanager (gnome).
Just write your own wpa_supplicant.conf file by hand, and start wpa_supplicant -i wlan0 -c wpa_supplicant.conf and it will works like a charm.
I think there is a series of bugs :
the generation of wpa_supplicant.conf file by yast and networkmanager
the bad use of wpa_supplicant with dbus (-u)
Since then; no problem with wifi N, no drops.
This is my first use of opensuse, just to have a try, the debian way of network configuration cause far less problems.
dhcp client under opensuse don’t handle all informations of the lease the server gave, such as nameserver or gateway, this is another story, but definitely Opensuse has lots of problems with networking.
On 07/26/2011 05:06 PM, gorpux wrote:
>
> Got the same problem with iwlwifi (intel 5100).
>
> This bug has nothing to do with firmware or channel neither mode abg or
> N
>
> This is definitely an OpenSuse issue, wifi can’t work neither with ifup
> nor networkmanager (gnome).
>
> Just write your own wpa_supplicant.conf file by hand, and start
> wpa_supplicant -i wlan0 -c wpa_supplicant.conf and it will works like a
> charm.
> I think there is a series of bugs :
> - the generation of wpa_supplicant.conf file by yast and
> networkmanager
> - the bad use of wpa_supplicant with dbus (-u)
>
> Since then; no problem with wifi N, no drops.
>
> This is my first use of opensuse, just to have a try, the debian way of
> network configuration cause far less problems.
> dhcp client under opensuse don’t handle all informations of the lease
> the server gave, such as nameserver or gateway, this is another story,
> but definitely Opensuse has lots of problems with networking.
Maybe, but for me NetworkManager works just as well as ifup.
Link 5100 - Opensuse 11.2 64 bit
What confuses me are the many different kinds off misbehaving reported. In my case there is a connect-disconnect cycle with dmesg output:
209.240051] wlan0: authenticate with 00:02:61:34:55:46 (try 1)
209.241785] wlan0: authenticated
209.243064] wlan0: associate with 00:02:61:34:55:46 (try 1)
209.248916] wlan0: RX ReassocResp from 00:02:61:34:55:46 (capab=0x451 status=0 aid=1)
209.248922] wlan0: associated
209.266840] bridge-wlan0: device is wireless, enabling SMAC
209.266846] bridge-wlan0: up
209.266850] bridge-wlan0: attached
385.773784] wlan0: deauthenticated from 00:02:61:34:55:46 (Reason: 1)
385.775556] bridge-wlan0: disabling the bridge
385.791180] bridge-wlan0: down
385.791191] bridge-wlan0: detached
In other words the device works intermittently.
I made a test with Ubuntu 11.10 32 bit: the card works perfectly on both desktops, gnome and kde. I tested with a radio sender connected continuously during 12 hours.
Other driver, other fw or other configuration? Hard to say, anyway, if somebody would like more information, I keep that installation. I can also perform freely every check on Suse because I keep always 2 copies of the installation and I need only 15 minutes for restoring.
On 03/02/2012 03:16 AM, Capodastro wrote:
>
> Link 5100 - Opensuse 11.2 64 bit
> What confuses me are the many different kinds off misbehaving reported.
> In my case there is a connect-disconnect cycle with dmesg output:
> 209.240051] wlan0: authenticate with 00:02:61:34:55:46 (try 1)
> 209.241785] wlan0: authenticated
> 209.243064] wlan0: associate with 00:02:61:34:55:46 (try 1)
> 209.248916] wlan0: RX ReassocResp from 00:02:61:34:55:46
> (capab=0x451 status=0 aid=1)
> 209.248922] wlan0: associated
> 209.266840] bridge-wlan0: device is wireless, enabling SMAC
> 209.266846] bridge-wlan0: up
> 209.266850] bridge-wlan0: attached
> 385.773784] wlan0: deauthenticated from 00:02:61:34:55:46 (Reason:
> 1)
> 385.775556] bridge-wlan0: disabling the bridge
> 385.791180] bridge-wlan0: down
> 385.791191] bridge-wlan0: detached
> In other words the device works intermittently.
>
> I made a test with Ubuntu 11.10 32 bit: the card works perfectly on
> both desktops, gnome and kde. I tested with a radio sender connected
> continuously during 12 hours.
> Other driver, other fw or other configuration? Hard to say, anyway, if
> somebody would like more information, I keep that installation. I can
> also perform freely every check on Suse because I keep always 2 copies
> of the installation and I need only 15 minutes for restoring.
I think tou are seeing the improvements between kernel 2.6.31 (openSUSE 11.2)
and 3.1(?) (Ubuntu 11.10) in that driver. What happens if you download the
source for a bleeding-edge compat-wireless and build that? As 11.2 is EOL and
out of support, you will not find a pre-built package.
Are you aware that security updates are no longer being applied to your system?
Hi Flux,
I have a path for understanding the reason of this problem. I am collecting further evidences, but until now there is just one explanation. I am investigating together with a good friend, a lady who is computer and network administrator, I know just about programming. She uses my installation on her laptop. We believe on a DoS attack which arises by running Skype. In this case “you right”, congratulation. Now I am busy, I will post again in the afternoon. But just one observation, what about that, by Skype not started?:
msi_user@linux-v9wc:~> dmesg | grep wlan
14.368796] ADDRCONF(NETDEV_UP): wlan0: link is not ready
41.652504] wlan0: authenticate with 00:02:61:34:55:46 (try 1)
41.654214] wlan0: authenticated
41.658335] wlan0: associate with 00:02:61:34:55:46 (try 1)
41.663823] wlan0: RX AssocResp from 00:02:61:34:55:46 (capab=0x451 status=0 aid=1)
41.663827] wlan0: associated
41.667559] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
41.683376] bridge-wlan0: device is wireless, enabling SMAC
41.683380] bridge-wlan0: up
41.683384] bridge-wlan0: attached
52.101053] wlan0: no IPv6 routers present
msi_user@linux-v9wc:~>
bye
Here a link describing in plane words what could be plausible in my case: http://www.utdallas.edu/~neerajm/publications/conferences/attacks.pdf
the deauthentications start always a few minutes after login. However, I know 2 laptops, one running suse, the second one on ubu, whose wlan connections are not disrupted.
On 03/03/2012 07:36 AM, Capodastro wrote:
>
> Here a link describing in plane words what could be plausible in my
> case:
> http://www.utdallas.edu/~neerajm/publications/conferences/attacks.pdf
> the deauthentications start always a few minutes after login. However,
> I know 2 laptops, one running suse, the second one on ubu, whose wlan
> connections are not disrupted.
The probability of that kind of attack being the cause for deauthentication is
extremely close to zero. You cannot get that attack over the network - it has to
be local. In addition, it would affect all connections, not just the openSUSE one.
Please post the output of ‘uname -r’ for the two systems. Of course, if you want
to believe the DoS attack theory, then I won’t have to worry about this any more.
