Very low wifi speed

[Paueti]

Ubuntu Maverick updated
The wifi speed is really slow 1 byte/s. Networl manager speed is 54M/s

The wifi controller is
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

iwconfig:

wlan0 IEEE 802.11abg ESSID:off/any
          Mode:Managed Frequency:2.452 GHz Access Point: Not-Associated
          Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off

ifconfig:

wlan0 Link encap:Ethernet HWaddr 01:08:dd:t6:f1:34
          inet6 addr: fe80::218:deff:fe55:d1bc/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:23 errors:0 dropped:0 overruns:0 frame:0
          TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2842 (2.8 KB) TX bytes:6619 (6.6 KB)

Ping is slow and dns resolution too.
---
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 10.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
IpRoute:
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.33 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.1.1 dev eth0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
NonfreeKernelModules: nvidia
Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 LANG=ca_ES.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-19.25-generic 2.6.35.3
Tags: maverick
Uname: Linux 2.6.35-19-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

[papukaija (papukaija)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[papukaija (papukaija)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please run the following command which will attach necessary information:

apport-collect 624870

Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):
First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!

[Paueti (paugonzaleza)]

apport information

[Paueti (paugonzaleza)]

apport information

[Paueti (paugonzaleza)]

apport information

[Paueti (paugonzaleza)]

apport information

[Paueti (paugonzaleza)]

apport information

[Paueti (paugonzaleza)]

apport information

[Paueti (paugonzaleza)]

apport information

[Paueti (paugonzaleza)]

apport information

[Paueti (paugonzaleza)]

apport information

[Paueti (paugonzaleza)]

apport information

[Paueti (paugonzaleza)]

apport information

[papukaija (papukaija)]

Why would this be a bug in NM (since you erote that it works in 54Mb speed) ? The speed is probably decreased by your card's driver which is part of the kernel. Therefore I'm moving this back to the kernel.

[Paueti (paugonzaleza)]

Network manaqer indicates 1 M/s.

[Paueti (paugonzaleza)]

In addition, network manager crashes after connect.
this is the log that I found with this command:
cat /var/log/daemon.log | grep NetworkManager,

[Paueti (paugonzaleza)]

This erros are when connects:

Aug 30 13:09:33 pau-portatil NetworkManager[1278]: <error> [1283166573.95547] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Aug 30 13:09:48 pau-portatil NetworkManager[1278]: <error> [1283166588.998923] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Aug 30 13:09:49 pau-portatil NetworkManager[1278]: <error> [1283166589.24346] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name

[papukaija (papukaija)]

This indeed seems to be a bug in NM. However, I noticed the following error messgae from the NM log:

Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
NetworkManager[1278]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)

Therefore, could you please attach your /etc/network/interfaces file to this bug report? Also, did your wifi eork correctly in Lucid? Thanks in advance!

[papukaija (papukaija)]

*work

[Paueti (paugonzaleza)]

/etc/network/interfaces:

auto lo
iface lo inet loopback

[Paueti (paugonzaleza)]

In lucid wifi works great!

[papukaija (papukaija)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 621265, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[penalvch (penalvch)]

Paueti, 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.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]