[Bug 183796] Re: iwl4965 unusable: packet loss, slow network

Christopher M. Penalver christopher.m.penalver at gmail.com
Thu Aug 15 13:41:49 CEST 2013


Kim Nguyễn, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** This bug is no longer a duplicate of bug 621265
   Slow Wireless Connection in Intel 3945abg

** Tags added: needs-kernel-logs needs-upstream-testing

** Changed in: linux (Ubuntu)
       Status: Triaged => Incomplete

-- 
You received this bug notification because you are subscribed to PLD
Linux.
https://bugs.launchpad.net/bugs/183796

Title:
  iwl4965 unusable: packet loss, slow network

Status in The Linux Kernel:
  Invalid
Status in “linux” package in Ubuntu:
  Incomplete
Status in PLD Linux Distribution:
  Confirmed

Bug description:
  Binary package hint: linux-image-2.6.24-4-generic

  On my sony vaio TZ, the intel wireless adapter is correctly detected but performances are horrible when using a 802.11b access point.
  This *does'nt seem* to affect 802.11g access points but I only tested with one. (While I tested 2 b access points, both perfectly working
  with other laptops (Linux/Windows Vista, intel cards,...)).
  I am testing with hardy amd64:

  # uname -a
  Linux carciofo 2.6.24-4-generic #1 SMP Mon Jan 14 18:19:11 UTC 2008 x86_64 GNU/Linux

  Behaviour is the following:
  modprobe iwl4965 works properly.
  network-manager associate with the acess point (WEP authentication),
  route/dns is setup correctly.

  ping 192.168.0.1 (the acess point) show over 10% packet loss and half the packet duplicated (DUP!),
  with the laptop only a few meters from the AP.
  Downloading a file with wget shows poor performances (around 10kb/s max) while connecting the laptop to the AP with ethernet gives around
  1Mb/s in download speed.

  This is with linux-image-2.6.24-4 from Hardy but the following
  kernel/driver combinations give the same behaviour:

  - linux-image-2.6.22 from gutsy
  - stock 2.6.23.13 kernel with latest mac80211 (10.0.0.4), latest iwlwifi (1.2.23) and latest firmware.
  - stock 2.6.24-rc7 and -rc8 with in-tree mac80211 and iwlwifi (1.2.23 fails to compile due to a change of wext_handle_ioctl and such).

  - also tried associating manually with iwconfig instead of network-manager, same result. 
  - also tried without wep.
  - also tried with various module parameters (antenna=1,2, disable_hw_scan=1, ...)

  I will attach output of iwconfig, lspci -v, dmesg, and ping.
  Let me know if I can do some more testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/183796/+subscriptions


More information about the pld-bugs mailing list