| 2008-09-12 04:04:51 |
Everett Guerny |
bug |
|
|
added bug |
| 2008-09-12 08:59:56 |
Alexander Sack |
network-manager: status |
New |
Incomplete |
|
| 2008-09-12 08:59:56 |
Alexander Sack |
network-manager: statusexplanation |
|
please reproduce and attach your complete syslog taken _after_ reproducing. Thanks! |
|
| 2008-09-15 12:44:04 |
matejcik |
description |
Binary package hint: network-manager
I'm using a Fujitsu T2010 laptop currently running Intrepid Alpha 5.
condition 1: If I boot into the LiveCD with the hardware wireless switch enabled (wireless on) from the beginning, WiFi works as expected.
condition 2: If I boot into the LiveCD with the hardware wireless switch disabled (wireless off) and then switch it on, network-manager does not detect any nearby wireless networks, and manually entering a known working one does not result in a connection being established. I've also waited a number of minutes after enabling wireless, as I know that it sometimes takes a few minutes for wireless networks to appear in the network-manager-applet.
From my dmesg (condition 2):
[ 97.650227] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
[ 97.650233] iwlagn: Copyright(c) 2003-2008 Intel Corporation
[ 97.651622] iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
So it looks like the wireless card is detected and whatnot, so I'm guessing it might be a network-manager problem.
I'm not familiar with managing wireless connections from the command line to troubleshoot this outside of the scope of network-manager, but if necessary, please let me know if there's any further information I can provide to help better diagnose this problem.
By the way, this hardware works without difficulty in Hardy. |
I'm using a Fujitsu T2010 laptop currently running Intrepid Alpha 5.
condition 1: If I boot into the LiveCD with the hardware wireless switch enabled (wireless on) from the beginning, WiFi works as expected.
condition 2: If I boot into the LiveCD with the hardware wireless switch disabled (wireless off) and then switch it on, network-manager does not detect any nearby wireless networks, and manually entering a known working one does not result in a connection being established. I've also waited a number of minutes after enabling wireless, as I know that it sometimes takes a few minutes for wireless networks to appear in the network-manager-applet.
From my dmesg (condition 2):
[ 97.650227] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
[ 97.650233] iwlagn: Copyright(c) 2003-2008 Intel Corporation
[ 97.651622] iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
So it looks like the wireless card is detected and whatnot, so I'm guessing it might be a network-manager problem.
I'm not familiar with managing wireless connections from the command line to troubleshoot this outside of the scope of network-manager, but if necessary, please let me know if there's any further information I can provide to help better diagnose this problem.
By the way, this hardware works without difficulty in Hardy. |
|
| 2008-09-15 12:44:04 |
matejcik |
title |
Intel 4965AGN wireless only works in Intrepid if hardware switch is enabled on boot |
rfkill switch on Intel 4965AGN wireless does not work in intrepid |
|
| 2008-09-15 12:46:01 |
matejcik |
network-manager: status |
Incomplete |
Invalid |
|
| 2008-09-15 12:46:01 |
matejcik |
network-manager: statusexplanation |
please reproduce and attach your complete syslog taken _after_ reproducing. Thanks! |
|
|
| 2008-09-17 20:44:40 |
matejcik |
bug |
|
|
assigned to linux (Ubuntu) |
| 2008-09-18 19:15:15 |
Leann Ogasawara |
linux: status |
New |
Incomplete |
|
| 2008-09-18 19:15:15 |
Leann Ogasawara |
linux: statusexplanation |
|
@matejcik - care to test using the latest Intrepid Alpha LiveCD - http://www.ubuntu.com/testing
@Everett - can you do the following:
1) as you describe in condition 2, boot with wireless off
2) open a terminal and do 'tail -n0 -f /var/log/syslog > syslog.log'
3) enable wireless (ie flip your kill switch)
4) capture the dmesg output by doing 'dmesg > dmesg.log'
5) attach both dmesg.log and syslog.log to this report
Thanks. |
|
| 2008-09-19 03:50:26 |
Everett Guerny |
bug |
|
|
added attachment 'syslog.log' (syslog.log) |
| 2008-09-19 03:51:08 |
Everett Guerny |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2008-09-29 13:31:14 |
Fernando Miguel |
linux: status |
Incomplete |
New |
|
| 2008-09-29 13:31:14 |
Fernando Miguel |
linux: assignee |
|
kernel-team |
|
| 2008-09-29 13:31:14 |
Fernando Miguel |
linux: statusexplanation |
@matejcik - care to test using the latest Intrepid Alpha LiveCD - http://www.ubuntu.com/testing
@Everett - can you do the following:
1) as you describe in condition 2, boot with wireless off
2) open a terminal and do 'tail -n0 -f /var/log/syslog > syslog.log'
3) enable wireless (ie flip your kill switch)
4) capture the dmesg output by doing 'dmesg > dmesg.log'
5) attach both dmesg.log and syslog.log to this report
Thanks. |
|
|
| 2008-09-29 13:32:09 |
Fernando Miguel |
bug |
|
|
added attachment 'dmesg' (dmesg) |
| 2008-09-29 13:32:22 |
Fernando Miguel |
bug |
|
|
added attachment 'syslog' (syslog) |
| 2008-09-29 21:18:29 |
Brian Murray |
linux: assignee |
kernel-team |
ubuntu-kernel-team |
|
| 2008-09-29 22:27:31 |
Brian Murray |
linux: status |
New |
Confirmed |
|
| 2008-09-29 22:27:31 |
Brian Murray |
linux: importance |
Undecided |
Medium |
|
| 2008-09-29 22:27:31 |
Brian Murray |
linux: statusexplanation |
|
Possibly related to bug 193970 if the different drivers share code. |
|
| 2008-11-26 09:48:57 |
Andy Whitcroft |
marked as duplicate |
|
193970 |
|
| 2009-04-08 16:39:24 |
matejcik |
removed subscriber matejcik |
|
|
|
