Quantal A2 failed to automatically connect Centrino Wireless N

Hi, jerrylamos,
I thing that you report against the wrong package. It seems to be not the network manager by itself it is more a problem with the kerneldriver.

I swithc the package to that.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1019083

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

sudo apport-collect 1019083
ERROR: The launchpadlib Python module is not installed. This functionality is not available.
jerry@Aspire-5253:~$ sudo apt-get install launchpadlib
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package launchpadlib

Tried both apport-collect and sudo apport-collect they wouldn't run. What package(s) are needed?

On both netbook and wide screen notebook with wireless WPA almost always have to manually connect to hidden wireless even though wireless is checked enabled, connect is checked automatically, and when I connect manually the menus already have the network name and password.

What do I install to get apport-collect to run?

Thanks, Jerry

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc5-quantal/

Installed latest upstream kernel as in your directions

Distributor ID: Ubuntu
Description: Ubuntu quantal (development branch)
Release: 12.10
Codename: quantal
Linux Aspire1 3.5.0-030500rc5-generic #201206302035 SMP Sun Jul 1 00:43:03 UTC 2012 i686 i686 i686 GNU/Linux

First boot from shutdown, "Disconnected".

Wait 1 minute, nothing

Systems Settings Network response quite sluggish, example on selecting "Connection" takes 30 seconds
Menu already has WPA password, mouse click
16 seconds later "Connect" message.

Shutdown, rebooted, same thing all over again. First thing on boot does "Disconnect" and does not enable wireless and does not connect automatically, and is quite sluggish in responding to menu.

Now I do have partitions with Maverick and Precise as well as a couple Quantal's if they would be useful to try.

My opinion, upstream no better than latest 3.5.0-3 Quantal kernel on wireless WPA
Intel Corporation Centrino Wireless-N 1000 with Intel driver.

Let me see if I can set the tags as you suggest.

Jerry

Turned the "confirmed" tag on, I couldn't find the 'kernel-bug-exists-upstream' tag.

Thanks for your attention.

Jerry

Turned the "confirmed" tag on, I couldn't find the 'kernel-bug-exists-upstream' tag.

Thanks for your attention.

Jerry

BTW, Precise may disconnect when the applet comes on, but seconds later "connects automatically" no manual manus required.

Simple copy paste in the tag line for adding tags. Sometimes there is no auto suggestion.

I have removed "needs-upstream-testing".

Thanks. Quite a contrast having to manually connecting to wireless WPA between the Intel Centrino with Intel driver with Quantal even taking 30 to 40 seconds to respond to "Connection" mouse click

versus automatic connection with Precise same hardware

and versus automatic quick response with Acer Aspire widescreen notebook on Quantal.

Any idea why the "automatic" code is not being evoked or is stuck?

Thanks, Jerry

BTW, I think I saw a comment that Phillinux has a Centrino but I don't know if he's using wireless WPA.

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Upstream bug # Bug 44291 since it also occurs with kernel:

 3.5.0-030500rc5-generic #201206302035 SMP Sun Jul 1 00:43:03 UTC 2012 i686 i686 i686 GNU/Linux

Jerry

Did not automatically connect from cold start today. Attached whole dmesg to bugzilla 44291. Ed of dmesg copied below.

Note 3 minute wait after boot for connect. Gave up at that point and selected "systems settings > network".
What is the "DENIED" message? What is "epollwakup" and if it is what it seesm, why wasn't it issued at boot?
Note also took over a minute for "systems settings > network" menu to finally complete.

[ 52.980620] EXT3-fs (sdb7): mounted filesystem with ordered data mode
[ 53.110534] kjournald starting. Commit interval 5 seconds
[ 53.110645] EXT3-fs (sdb6): warning: maximal mount count reached, running e2fsck is recommended
[ 53.111263] EXT3-fs (sdb6): using internal journal
[ 53.111273] EXT3-fs (sdb6): mounted filesystem with ordered data mode
[ 331.170457] audit_printk_skb: 21 callbacks suppressed
[ 331.170470] type=1400 audit(1341660939.590:21): apparmor="DENIED" operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=833 comm="cupsd" pid=833 comm="cupsd" capability=36 capname="epollwakeup"
[ 456.122669] wlan0: authenticate with 00:0f:b3:b0:d6:3c
[ 456.141133] wlan0: send auth to 00:0f:b3:b0:d6:3c (try 1/3)
[ 456.142805] wlan0: authenticated
[ 456.143280] wlan0: waiting for beacon from 00:0f:b3:b0:d6:3c
[ 456.288093] wlan0: associate with 00:0f:b3:b0:d6:3c (try 1/3)
[ 456.301556] wlan0: RX AssocResp from 00:0f:b3:b0:d6:3c (capab=0x431 status=0 aid=1)
[ 456.301568] wlan0: associated
[ 456.304354] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
(END)

Thanks for any thoughts. Jerry

Jerry could you please copy paste the link from kernel bugtracker here(full). The link from comment 12 only points on launchpad itself.

https://bugzilla.kernel.org/show_bug.cgi?id=44291

I think that's it, copied it from the URL when I was viewing the bug.

Jerry

In principle yes, but when you not post the full URL launchpad link automatically to a launchpad bug of this number.

By the way, I have looked at the kernel bugtracker ticket. You should set back the "Needinfo" entry to "New" when you have provided the needed information.

I have linked the bug from kernel bugtracker here. There will be automatically imports of all comments you are doing there. So, bughandling should be primary on kernel bugtracker.

Please also change in kernel bugtracker the kind of attachmend to text. In moment the dmesg are handeled as bin

Comment #18 - they are text. I have no idea why bugzilla marks them as bin.

I downloaded one by selecting it and did a save file.

I selected the saved file and I could read it fine with the normal Nautilus display.

Jerry

Yes, you have done all correct, it is a known bugzilla issue. And the method you describe work.

In weeks of no "automatic connect" I finally got one. dmesg is attached. It looks a lot different at the end than the other dmesg I have posted.

I'll try later to reproduce the bug or success.

Jerry

Here's the dmesg from an actual auto connect. Looks a lot different on the last few lines:
[ 54.914767] EXT3-fs (sdb7): using internal journal
[ 54.914789] EXT3-fs (sdb7): mounted filesystem with ordered data mode
[ 86.970915] wlan0: authenticate with 00:0f:b3:b0:d6:3c
[ 86.984789] wlan0: send auth to 00:0f:b3:b0:d6:3c (try 1/3)
[ 86.987028] wlan0: authenticated
[ 86.987506] wlan0: waiting for beacon from 00:0f:b3:b0:d6:3c
[ 87.140071] wlan0: associate with 00:0f:b3:b0:d6:3c (try 1/3)
[ 87.143199] wlan0: RX AssocResp from 00:0f:b3:b0:d6:3c (capab=0x431 status=0 aid=1)
[ 87.143210] wlan0: associated
[ 87.145928] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Will try again for success/failure. Takes a shutdown - wait - reboot cycle to do it.

Jerry

Thank you for going further, but bughandling is now primary on the kernel bugtracker and not so anymore here.

And give them time to handle. It may be weeks. No, good info, I know, but it is like it is. No more developers than threre are, are arround.

Can you try again to run:

apport-collect 1019083

I would like to look at the logs

When this happends again:

ERROR: The launchpadlib Python module is not installed. This functionality is not available.

please install synaptic and type in launchpadlib in the search form.

there should be a package

python-launchpadlib

install this and make sure(when it is still not working) that

liblaunchpad-integration * (also search from)

is installed(6 packages shown not all needed)

Please also attach your latest syslog manually. Not the compressed ones.

Took over 2 minutes for an "automatic connection".
dmesg and syslog are attached to:

https://bugzilla.kernel.org/attachment.cgi?bugid=44291

Tried apport-collect. Installed launchpadlib.

I'm running an upstream kernel as suggested earlier in this bug. Apport-collect wants an Ubuntu kernel so I'll reboot.

Jerry

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Whee, this bug report just got flooded from apport-collect. Must take up a lot of space if someone knows what to delete please do so.

Jerry

p.s. Problem still prevalent.

Upstream thinks this is a Ubuntu problem. Once given the authentication request, the kernel goes right ahead and connects with no retries, they see no problem on their end. See below.

So the question is, why does Ubuntu take so long between these next two lines in dmesg? What is Ubuntu waiting for?

[ 54.117720] EXT3-fs (sdb2): mounted filesystem with ordered data mode
[ 185.982020] wlan0: authenticate with 00:0f:b3:b0:d6:3c

In some cases, I've waited 5 minutes for the authentication request from Ubuntu, never came, so I did manual connect.

Excerpt from syslog showing big gap between 14:01:51 and 14:02:29 approximate time as the gap in dmesg with similar messages. Syslog has two additional lines about not being able to open /etc/crypttab and mounting a udisk:

Jul 9 14:01:51 Aspire1 kernel: [ 53.184095] EXT3-fs (sdb7): mounted filesystem with ordered data mode
Jul 9 14:01:51 Aspire1 udisksd[1570]: Error opening /etc/crypttab file: Failed to open file '/etc/crypttab': No such file or d
irectory (g-file-error-quark, 4)
Jul 9 14:01:51 Aspire1 udisksd[1570]: Mounted /dev/sdb7 at /run/media/jerry/LiveB7 on behalf of uid 1000
Jul 9 14:02:05 Aspire1 goa[1719]: goa-daemon version 3.5.3 starting [main.c:112, main()]
Jul 9 14:02:29 Aspire1 NetworkManager[950]: <info> Auto-activating connection 'LAUREL'.
Jul 9 14:02:29 Aspire1 NetworkManager[950]: <info> Activation (wlan0) starting connection 'LAUREL'

Upstream's comment:

--- Comment #10 from John W. Linville <email address hidden> 2012-07-09
17:37:49 ---
I'm sorry, but I don't see any evidence of a kernel problem here.

The kernel has no concept of an "automatic connection". Something in userland
(probably NetworkManager in your case) has to tell the kernel what AP to use.
In every case above, the authentication happens on the first try, followed
immediately by the association on the first try. I don't see any significant
delay being introduced by the kernel, and there are not even any retries. At
worst, the kernel could be taking a while to scan -- but I don't see any
evidence of an abnormally long scan either.

Thanks for any ideas.

Jerry

Tried copying in Pangolin's /etc/crypttab. That got rid of the message about not being able to open it. No help.

Still no automatic connect. On restart, notice the syslog time lapse between 16:31 and 18:56 where I gave up waiting and manually selected "Connect to hidden wireless network" which took about a minute more.
.....
Jul 9 15:16:31 Aspire1 <U+FEFF>AptDaemon.Worker: INFO: Finished transaction /org/debian/apt/transaction/8a62d909e0ac412f91638bb342708a6a
Jul 9 15:17:01 Aspire1 CRON[1841]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 9 15:18:56 Aspire1 NetworkManager[775]: <info> Activation (wlan0) starting connection 'LAUREL'
.....

I'm out of ideas for the moment.

Jerry

Well, maybe it's designated invalid, it's still giving me fits. Not a showstopper. An anklebiter. We'll see if other people hit it.

I'm not a developer. Looking at it from a "black box" standpoint seems that the "script" is delaying issuing "authenticate" from seconds to minutes....I've no clue what it is waiting for...

Thanks for your attention anyway.

Jerry

Hi Jerry,

do net hesitate. kernel developers are sometimes are a bit unpatient. Give me some days to find time to look at your files.

------------------------------------------------

Jerry, it is not necessary to write so much over one bug. We have over 98.000 open bugs here and someone must read all that what you write if you write. This needs time that we do not have in common. So, lesser is most more here. When you write less and more specific you increase the probalility that someone look at.

Alpha 3 still does not automatically connect, even after waiting minuts. Manually select system settings , drop down menu after drop down mneu, wait 40 seconDs Ubuntu finally issues authenticate kernel connects.
3.5.0-9-generic #9-Ubuntu SMP Thu Aug 9 13:55:19 UTC 2012 i686 i686 i686 GNU/Linux
Workaround. boot, wait a little, no connect, then do:
sudo dhclient wlan0
wait 5 seconds, do Ctrl-c connects O.K. Much faster with less manual entry than usung Ubuntu menus. Dmesg excerpt below shows no activity from time 56 to time 112 when the Ctrl-c was issued then authenticate issued right away. Stll no clue why Ubuntu doesn't automatically issue authenticate to kernel at time 56, or why Ctrl-c causes authenticate to issue.

[ 56.298728] EXT3-fs (sdb2): mounted filesystem with ordered data mode
[ 112.089686] wlan0: authenticate with 00:0f:b3:b0:d6:3c
[ 112.114162] wlan0: send auth to 00:0f:b3:b0:d6:3c (try 1/3)
[ 112.115764] wlan0: authenticated

Acer Aspire 5253 wide screen notebook also has automatic disconnect. This instance it connected again shortly. Here's an excerpt from syslog:

Log shows wlan0 ready
then disconnected??

Sep 28 17:13:24 Aspire-5253 NetworkManager[786]: <info> (wlan0): supplicant interface state: starting -> ready
Sep 28 17:13:24 Aspire-5253 NetworkManager[786]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Sep 28 17:13:24 Aspire-5253 NetworkManager[786]: <warn> Trying to remove a non-existant call id.
Sep 28 17:13:24 Aspire-5253 NetworkManager[786]: <info> (wlan0): supplicant interface state: ready -> inactive
......
some lines later connected??
......
Sep 28 17:13:52 Aspire-5253 wpa_supplicant[990]: wlan0: WPA: Key negotiation completed with 00:0f:b3:b0:d6:3c [PTK=TKIP GTK=TKIP]
Sep 28 17:13:52 Aspire-5253 wpa_supplicant[990]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:0f:b3:b0:d6:3c completed (auth) [id=0 id_str=]

Whole syslog attached

Since I found similar problems with disconnect on QQ Beta2 on Acer Aspire 1 and Aspire 5253 should I start another launchpad bug?

For bug investigation I'd like to try Precise Network Manager on QQ. Is that feasible?

Thanks.

Interesting. Asus transformesr 10.1" tablet running Android connects to same hiidden wireless WPA network instantly.

jerrylamos, as per http://us.acer.com/ac/en/US/content/drivers an update is available for your BIOS (3.16). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.