[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017738
Bug still present on saucy. Ubuntu network manager policy is not user friendly
-
Precise connected fairly quickly after power up to wireless WPA encrypted
network.
Nook connects immediately on power up to wireless WPA encrypted network.
Chromebook connects immediately on power up to wireless
** Tags added: needs-bisect saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017738
Title:
NM fails to connect Wi-Fi; dhclient works -- Intel Centrino Wireless-N
1000 iwlwifi
To manage
jerrylamos, 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
This bug is still present on latest Saucy Salamander 3.11.0-3.
On the same WPA encrypted network:
Precise on the same hardware boots up and connects automatically.
Nook HD+ boots up and connects autmatically even faster.
Asus Transformer TF101 boots up and connects automatically.
Samsung Galaxy
Workaround since this bug is even worse with 3.7.0-3:
Startup Applications
Add
Title: Connect
command: ~/wl
where wl is
#!/bin/bash
sudo iwconfig wlan0 essid LAUREL
sudo dhclient wlan0
exit 0
Has worked O.K. for three boots so far.
Why can't Ubuntu issue the iwconfig??
--
You received this
Raring booted up, had already been updated to Nov 15.
Hidden wireless WPA security did not connect automatically although it is
marked to do so.
Sysetems Settings Network keyed the network name on the entry area. Nothing
shows in the Network Name area.
Four minutes later! finally the
Raring Regression vs. Quantal..
On quantal, nm disconnects as described above, I could do sudo dhclient and
wait 5 seconds, Ctrl-c, connect. Does not work on Raring.
Raring much worse. I have to crawl thru systems settings network takes
minutes on end staring at un-responive drop down
Boot today with Raring NM all kinds of thrash with system settings
network to finally get connected. Attached is syslog showing network
manager complaining about all kinds of problems which really don't exist
since everything is all ready set saved and connects immediately once
network manager
Syslog from Precise connected fine when desktop booted up.
Why can't Raring do the same thing?
** Attachment added: Ending part of syslog showing wlan0 connected O.K.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1017738/+attachment/3424647/+files/syslog_precise_autoconnect
--
You
Real thrash getting NM to finally (!) connect to wireless WPA security
today.
sudo dhclient wlan0 no luck at all.
nm applet edit connections no luck at all.
systems settings nm drop down window cannot enter name of the network
for over a minute. At 1.5 MB/S what on earth is nm waiting for?
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017738
Title:
NM fails to connect Wi-Fi; dhclient works -- Intel Centrino Wireless-N
What you could try is to boot on a Quantal live cd image to verify that
it is not something strange in your installation.
Also it would be interesting to know if a 3.5/3.6/3.7 mainline kernels
work better. There are packages available. Read more here:
Network Applet Edit Connections Wireless Security tab should ask for
authorization to set/change password. It does not. That's a bug.
I assume this is a user connection then. For editing system connections,
a sudo prompt should pop up.
--
You received this bug notification because you are a
Marius, I've tried upstream Debian kernel. Same problem.
Analysis from upstream was when the authentication was presented to the kernel,
the kernel connected no problem right away.
This is evident in the syuslogs where the syslog shows once the authentication
request gets around to being
I put raring ubuntu-bug data into bug #1073907. External results are
the same, there is some difference in the syslog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017738
Title:
NM fails to
Since this bug's expired I'll open a new one for Raring since the
problem still exists on my two notebooks. On this Acer Aspire 1 netbook
nearly always fails to connect to security WPA. On Acer Aspire 5253
wide screen notebook fairly erratic on connecting.
--
You received this bug
You can just set the status of this report back to New.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017738
Title:
NM fails to connect Wi-Fi; dhclient works -- Intel Centrino Wireless-N
1000
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017738
@jerrylamos: Does it help if you create a file /etc/modprobe.d/iwlwifi-
disable11n.conf with the contents
options iwlwifi 11n_disable=1
and then reboot?
** Summary changed:
- NM fails to connect Wi-Fi -- Intel Centrino Wireless-N 1000 iwlwifi
+ NM fails to connect Wi-Fi; dhclient works --
Most likely a driver problem
** Package changed: network-manager (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017738
Title:
NM fails to connect Wi-Fi; dhclient works --
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.6 kernel[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
Also, it would be helpful to know the results of the test requested in
comment #21.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017738
Title:
NM fails to connect Wi-Fi; dhclient works -- Intel
I have tested the upstream kernel before. Their analysis as soon as
their kernel got the authienticate or connect or whatever the proper
term is from quantal they connected right away. That is very evident in
the dmesg and syslogs.
I can try the upstream kernel again. Is there any way to tell
With comment #21, once connected O.K. once did not connect, but sudo
dhclient and it did. Most tries it does not connect automatically and I
do a sudo dhclient wlan0, Ctrl-c. Here's an excerpt from a dmesg
showing link is not ready at the bottom. I wonder if there's a race
condition between
Just tried 3.6.0-030600rc3-generic same behavior. Note the suggestion for
comment #21 is still in.
Last time I tried Cebian upstream kernel same behavior too, though that was
probably Alpha 1 time.
[ 23.094874] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N
1000 BGN,
26 matches
Mail list logo
