| 2007-04-11 09:19:26 |
Andrea Bravetti |
bug |
|
|
added bug |
| 2007-04-16 14:17:45 |
Andrea Bravetti |
description |
both iwlwifi and ipw3945 are unable to turn off
rf_kill on a Fujitsu Siemens AMILO Pro V3505, so
wifi is unavailable on this notebook (and others...).
Someone (that has the power to do so) should ask
Fujitsu asking for spec...
This is (part of) the output of lspci:
04:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
This is the output of iwconfig:
lo no wireless extensions.
eth0 no wireless extensions.
This is (part of) the output of dmesg using iwlwifi:
[ 24.548000] iwlwifi: Detected Intel PRO/Wireless 3945ABG Network Connection
[ 24.740000] iwlwifi: Radio Frequency Kill Switch is On:
[ 24.740000] Kill switch must be turned off for wireless networking to work.
[ 24.796000] iwlwifi: MAC is in deep sleep!
[ 24.796000] iwlwifi: MAC is in deep sleep!
[ 24.800000] iwlwifi: MAC is in deep sleep!
[ 24.804000] iwlwifi: MAC is in deep sleep!
This is (part of) the output of dmesg using ipw3945:
[ 23.720000] ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0mp
[ 23.720000] ipw3945: Copyright(c) 2003-2006 Intel Corporation
[ 23.720000] ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
... now i'm starting ipw3945d (ipw3945d-2.6.20-14-generic) ...
[ 375.008000] ipw3945: Radio Frequency Kill Switch is On:
[ 375.008000] Kill switch must be turned off for wireless networking to work.
When I try to unload iwlwifi and load ipw3945 I get
a dead keyboard, and I can use only the mouse to reboot...
When I try to turn off rf_kill "manually" I get only
a lot of time out error like this:
[ 565.588000] ipw3945: Error sending CARD_STATE_CMD: time out after 500ms.
When I try to turn on the led "manually" I get:
[ 615.604000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
Now the only way to use this card with linux is:
1. Upgrade the BIOS to version B0E or newer.
2. Boot with Windows (but I don't have it now...).
3. Enable wifi under Windows.
4. Do an hot reboot and enter Linux.
5. Be happy with wifi...
This is a bug, since Linux should be able to turn off
rf_kill without using Windows...
I understand that on Fujitsu Siemens AMILO Pro V3505
there is something strange and it may be also an hardware
or BIOS related problem however it should work...
If someone can get the spec from Fujitsu Siemens I will
be happy to write a patch or utility to do the job.
bye,
Andrea Bravetti |
both iwlwifi and ipw3945 are unable to turn off
rf_kill on a Fujitsu Siemens AMILO Pro V3505, so
wifi is unavailable on this notebook (and others...).
Someone (that has the power to do so) should ask
Fujitsu asking for spec...
This is (part of) the output of lspci:
04:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
This is the output of iwconfig:
lo no wireless extensions.
eth0 no wireless extensions.
This is (part of) the output of dmesg using iwlwifi:
[ 24.548000] iwlwifi: Detected Intel PRO/Wireless 3945ABG Network Connection
[ 24.740000] iwlwifi: Radio Frequency Kill Switch is On:
[ 24.740000] Kill switch must be turned off for wireless networking to work.
[ 24.796000] iwlwifi: MAC is in deep sleep!
[ 24.796000] iwlwifi: MAC is in deep sleep!
[ 24.800000] iwlwifi: MAC is in deep sleep!
[ 24.804000] iwlwifi: MAC is in deep sleep!
This is (part of) the output of dmesg using ipw3945:
[ 23.720000] ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0mp
[ 23.720000] ipw3945: Copyright(c) 2003-2006 Intel Corporation
[ 23.720000] ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
... now i'm starting ipw3945d (ipw3945d-2.6.20-14-generic) ...
[ 375.008000] ipw3945: Radio Frequency Kill Switch is On:
[ 375.008000] Kill switch must be turned off for wireless networking to work.
When I try to unload iwlwifi and load ipw3945 I get
a dead keyboard, and I can use only the mouse to reboot...
When I try to turn off rf_kill "manually" I get only
a lot of time out error like this:
[ 565.588000] ipw3945: Error sending CARD_STATE_CMD: time out after 500ms.
When I try to turn on the led "manually" I get:
[ 615.604000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
Now the only way to use this card with linux is:
1. Upgrade the BIOS to version B0E or newer.
2. Boot with Windows (but I don't have it now...).
3. Enable wifi under Windows.
4. Do an hot reboot and enter Linux.
5. Be happy with wifi...
This is a bug, since Linux should be able to turn off
rf_kill without using Windows...
I understand that on Fujitsu Siemens AMILO Pro V3505
there is something strange and it may be also an hardware
or BIOS related problem however it should work...
bye,
Andrea Bravetti |
|
| 2007-10-23 00:14:54 |
Leann Ogasawara |
linux-source-2.6.20: status |
New |
Incomplete |
|
| 2007-10-23 00:15:11 |
Leann Ogasawara |
marked as duplicate |
|
99585 |
|
| 2007-11-13 18:54:03 |
Leann Ogasawara |
removed duplicate marker |
99585 |
|
|
| 2007-11-17 11:14:29 |
Gioele Barabucci |
linux-source-2.6.20: status |
Incomplete |
Confirmed |
|
| 2007-11-19 16:22:47 |
Leann Ogasawara |
bug |
|
|
assigned to linux-source-2.6.22 (Ubuntu) |
| 2007-11-19 16:30:30 |
Leann Ogasawara |
linux-source-2.6.22: status |
New |
Incomplete |
|
| 2007-11-22 15:55:00 |
Gioele Barabucci |
bug |
|
|
added attachment 'dmidecode.log' (dmidecode.log) |
| 2007-11-22 16:12:36 |
Gioele Barabucci |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci-vvnn.log) |
| 2007-11-22 16:19:10 |
Gioele Barabucci |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2007-12-12 04:42:36 |
Brian Murray |
linux-source-2.6.20: assignee |
|
ubuntu-kernel-team |
|
| 2007-12-19 22:53:31 |
Leann Ogasawara |
bug |
|
|
assigned to linux (Ubuntu) |
| 2007-12-19 22:53:58 |
Leann Ogasawara |
linux: status |
New |
Incomplete |
|
| 2007-12-28 05:41:37 |
Leann Ogasawara |
bug |
|
|
added subscriber l |
| 2008-04-09 17:00:56 |
Leann Ogasawara |
linux-source-2.6.20: status |
Confirmed |
Won't Fix |
|
| 2008-04-09 17:01:15 |
Leann Ogasawara |
linux-ubuntu-modules-2.6.22: status |
Incomplete |
Won't Fix |
|
| 2008-04-09 19:04:21 |
Espen Helgedagsrud |
bug |
|
|
added attachment 'logs.zip' (Archive with all the requested logs) |
| 2008-05-16 13:38:00 |
Leann Ogasawara |
linux: importance |
Undecided |
Medium |
|
| 2008-05-16 13:38:00 |
Leann Ogasawara |
linux: assignee |
|
ubuntu-kernel-team |
|
| 2008-05-16 13:38:00 |
Leann Ogasawara |
linux: status |
Incomplete |
Triaged |
|
| 2008-08-30 16:54:01 |
Fernando Miguel |
linux: status |
Triaged |
New |
|
| 2008-11-24 17:27:56 |
Leann Ogasawara |
linux: status |
New |
Incomplete |
|
| 2008-11-24 17:27:56 |
Leann Ogasawara |
linux: statusexplanation |
|
Hi Andrea,
Can you confirm this is still an issue with the latest 2.6.27-7 Intrepid Ibex kernel? However, I'd also like to point out bug 193970 that might affect your wifi. Thanks. |
|
| 2009-04-29 21:12:27 |
Brad Figg |
linux (Ubuntu): status |
Incomplete |
Won't Fix |
|
| 2019-06-01 19:49:00 |
asdfghjklasdfghjkl |
removed subscriber asdfghjklasdfghjkl |
|
|
|
