Arch Linux

sabowski

Member

Registered: 2009-12-01

Posts: 2

WG511 only works when laptop started on AC power

Here is what is basically going on: I have a WG511 wireless card that will only properly load it's firmware when the laptop is started on AC power. If I start it up and plug it into AC power after it's loaded, that still won't allow the firmware to load.

Wireless card: Netgear WG511. Back of the card says "v3.0" and "MADE IN CHINA". According to lspci -k:

02:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)
    Subsystem: Netgear WG511 Wireless Adapter
    Kernel modules: p54pci, prism54

(module p54pci is used, prism54 is blacklisted in rc.conf)

The laptop is an IBM ThinkPad T22, running the latest version of the BIOS.

When I start up the laptop without AC power plugged in, this is what I get:

pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
pci 0000:02:00.0: reg 10 32bit mmio: [0x000000-0x001fff]
pci 0000:02:00.0: supports D1 D2
pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:02:00.0: PME# disabled
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
    (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
p54pci 0000:02:00.0: enabling device (0000 -> 0002)
p54pci 0000:02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
p54pci 0000:02:00.0: setting latency timer to 64
p54pci 0000:02:00.0: firmware: requesting isl3886pci
phy0: p54 detected a LM86 firmware
p54: rx_mtu reduced from 3240 to 2376
phy0: FW rev 2.13.1.0 - Softmac protocol 5.5
phy0: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES
phy0: Cannot boot firmware!
p54pci 0000:02:00.0: PCI INT A disabled
p54pci: probe of 0000:02:00.0 failed with error -110

it also looks like there's some issues with hal as well. I haven't quite been able to pin down exactly what makes this error come up, as it doesn't seem tied to the AC power issue:

ACPI Exception: AE_NOT_ACQUIRED, Could not release Global Lock 20090521 exutils-310
INFO: task kacpid:10 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kacpid        D 00000000     0    10      2 0x00000000
 cf83a520 00000046 00000000 00000000 00000001 00000000 00000008 cf867d30
 00000000 cf283a80 00000020 c1489140 c1489140 cf83a6c8 c1484744 d179759a
 00000020 cf83a6c8 c1489140 c1489140 cf867d30 00000000 0ffeffc8 0ffeffc9
Call Trace:
 [<c1306545>] ? schedule_timeout+0x195/0x210
 [<c1036331>] ? update_curr+0x1e1/0x1f0
 [<c1307b30>] ? __down_timeout+0x60/0xa0
 [<c106857b>] ? down_timeout+0x6b/0x70
 [<c11dd333>] ? acpi_os_wait_semaphore+0x46/0x64
 [<c11f296a>] ? acpi_ex_system_wait_mutex+0x40/0x62
 [<c11eceff>] ? acpi_ev_acquire_global_lock+0x4f/0xd1
 [<c11f48e7>] ? acpi_ex_acquire_mutex_object+0x3e/0x75
 [<c11f44d9>] ? acpi_ex_acquire_global_lock+0x2a/0x59
 [<c11ef9d4>] ? acpi_ex_read_data_from_field+0x10b/0x153
 [<c11f4e61>] ? acpi_ex_resolve_node_to_value+0x159/0x1e0
 [<c11f03cf>] ? acpi_ex_resolve_to_value+0x1bc/0x1d9
 [<c11ea469>] ? acpi_ds_evaluate_name_path+0x77/0xf9
 [<c11e9116>] ? acpi_ds_exec_end_op+0x82/0x36c
 [<c11fb18e>] ? acpi_ps_parse_loop+0x5ff/0x76d
 [<c11fa51c>] ? acpi_ps_parse_aml+0x8b/0x28f
 [<c11fbae6>] ? acpi_ps_execute_method+0x1a0/0x266
 [<c11f78da>] ? acpi_ns_evaluate+0xce/0x190
 [<c11f7347>] ? acpi_evaluate_object+0x180/0x27b
 [<c11e20c3>] ? acpi_ec_gpe_query+0x8d/0xd7
 [<c11dd390>] ? acpi_os_execute_deferred+0x0/0x54
 [<c11dd3c7>] ? acpi_os_execute_deferred+0x37/0x54
 [<c105cfdf>] ? worker_thread+0x11f/0x280
 [<c1062d40>] ? autoremove_wake_function+0x0/0x60
 [<c105cec0>] ? worker_thread+0x0/0x280
 [<c10628ec>] ? kthread+0x8c/0xa0
 [<c1062860>] ? kthread+0x0/0xa0
 [<c10048e7>] ? kernel_thread_helper+0x7/0x10
INFO: task hald:2970 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
hald          D 093fc0d0     0  2970      1 0x00000000
 cf1454a0 00000082 00000000 093fc0d0 cfa65c14 cfa65f94 00000001 cfa65c20
 c13115c0 cf283a80 56811831 c1489140 c1489140 cf145648 c1484744 00000000
 cf1454a0 cf145648 c1489140 c1489140 ffff4e72 00000000 00000000 cf1454a0
Call Trace:
 [<c1104f80>] ? pollwake+0x0/0x80
 [<c1306545>] ? schedule_timeout+0x195/0x210
 [<c1104f80>] ? pollwake+0x0/0x80
 [<c1104f80>] ? pollwake+0x0/0x80
 [<c1307b30>] ? __down_timeout+0x60/0xa0
 [<c106857b>] ? down_timeout+0x6b/0x70
 [<c11dd333>] ? acpi_os_wait_semaphore+0x46/0x64
 [<c11f296a>] ? acpi_ex_system_wait_mutex+0x40/0x62
 [<c11eceff>] ? acpi_ev_acquire_global_lock+0x4f/0xd1
 [<c11f48e7>] ? acpi_ex_acquire_mutex_object+0x3e/0x75
 [<c11f44d9>] ? acpi_ex_acquire_global_lock+0x2a/0x59
 [<c11ef897>] ? acpi_ex_write_data_to_field+0x15b/0x18d
 [<c11f3fbd>] ? acpi_ex_store_object_to_node+0x91/0xdb
 [<c11f417e>] ? acpi_ex_store+0xaa/0x208
 [<c11f1d71>] ? acpi_ex_opcode_1A_1T_1R+0x3f9/0x544
 [<c11f257a>] ? acpi_ex_resolve_operands+0x188/0x416
 [<c11e9167>] ? acpi_ds_exec_end_op+0xd3/0x36c
 [<c11fb18e>] ? acpi_ps_parse_loop+0x5ff/0x76d
 [<c11e9985>] ? acpi_ds_call_control_method+0x159/0x1c4
 [<c11fa51c>] ? acpi_ps_parse_aml+0x8b/0x28f
 [<c11fbae6>] ? acpi_ps_execute_method+0x1a0/0x266
 [<c11f78da>] ? acpi_ns_evaluate+0xce/0x190
 [<c11f7347>] ? acpi_evaluate_object+0x180/0x27b
 [<d0b86314>] ? acpi_battery_get_state+0x69/0xdb [battery]
 [<d0b8670d>] ? acpi_battery_get_property+0x29/0x1ab [battery]
 [<c1248bb6>] ? power_supply_show_property+0x46/0x160
 [<c1306e44>] ? __mutex_lock_slowpath+0x1f4/0x2e0
 [<c1248b70>] ? power_supply_show_property+0x0/0x160
 [<c1230ad0>] ? dev_attr_show+0x30/0x70
 [<c114fc15>] ? sysfs_read_file+0xa5/0x160
 [<c116663b>] ? security_file_permission+0x1b/0x40
 [<c10f35f5>] ? vfs_read+0xc5/0x1b0
 [<c114fb70>] ? sysfs_read_file+0x0/0x160
 [<c10f37ff>] ? sys_read+0x5f/0xb0
 [<c1003cb3>] ? sysenter_do_call+0x12/0x28
INFO: task kacpid:10 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kacpid        D 00000000     0    10      2 0x00000000
 cf83a520 00000046 00000000 00000000 00000001 00000000 00000008 cf867d30
 00000000 cf283a80 00000020 c1489140 c1489140 cf83a6c8 c1484744 d179759a
 00000020 cf83a6c8 c1489140 c1489140 cf867d30 00000000 0ffeffc8 0ffeffc9
Call Trace:
 [<c1306545>] ? schedule_timeout+0x195/0x210
 [<c1036331>] ? update_curr+0x1e1/0x1f0
 [<c1307b30>] ? __down_timeout+0x60/0xa0
 [<c106857b>] ? down_timeout+0x6b/0x70
 [<c11dd333>] ? acpi_os_wait_semaphore+0x46/0x64
 [<c11f296a>] ? acpi_ex_system_wait_mutex+0x40/0x62
 [<c11eceff>] ? acpi_ev_acquire_global_lock+0x4f/0xd1
 [<c11f48e7>] ? acpi_ex_acquire_mutex_object+0x3e/0x75
 [<c11f44d9>] ? acpi_ex_acquire_global_lock+0x2a/0x59
 [<c11ef9d4>] ? acpi_ex_read_data_from_field+0x10b/0x153
 [<c11f4e61>] ? acpi_ex_resolve_node_to_value+0x159/0x1e0
 [<c11f03cf>] ? acpi_ex_resolve_to_value+0x1bc/0x1d9
 [<c11ea469>] ? acpi_ds_evaluate_name_path+0x77/0xf9
 [<c11e9116>] ? acpi_ds_exec_end_op+0x82/0x36c
 [<c11fb18e>] ? acpi_ps_parse_loop+0x5ff/0x76d
 [<c11fa51c>] ? acpi_ps_parse_aml+0x8b/0x28f
 [<c11fbae6>] ? acpi_ps_execute_method+0x1a0/0x266
 [<c11f78da>] ? acpi_ns_evaluate+0xce/0x190
 [<c11f7347>] ? acpi_evaluate_object+0x180/0x27b
 [<c11e20c3>] ? acpi_ec_gpe_query+0x8d/0xd7
 [<c11dd390>] ? acpi_os_execute_deferred+0x0/0x54
 [<c11dd3c7>] ? acpi_os_execute_deferred+0x37/0x54
 [<c105cfdf>] ? worker_thread+0x11f/0x280
 [<c1062d40>] ? autoremove_wake_function+0x0/0x60
 [<c105cec0>] ? worker_thread+0x0/0x280
 [<c10628ec>] ? kthread+0x8c/0xa0
 [<c1062860>] ? kthread+0x0/0xa0
 [<c10048e7>] ? kernel_thread_helper+0x7/0x10
INFO: task hald:2970 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
hald          D 093fc0d0     0  2970      1 0x00000000
 cf1454a0 00000082 00000000 093fc0d0 cfa65c14 cfa65f94 00000001 cfa65c20
 c13115c0 cf283a80 56811831 c1489140 c1489140 cf145648 c1484744 00000000
 cf1454a0 cf145648 c1489140 c1489140 ffff4e72 00000000 00000000 cf1454a0
Call Trace:
 [<c1104f80>] ? pollwake+0x0/0x80
 [<c1306545>] ? schedule_timeout+0x195/0x210
 [<c1104f80>] ? pollwake+0x0/0x80
 [<c1104f80>] ? pollwake+0x0/0x80
 [<c1307b30>] ? __down_timeout+0x60/0xa0
 [<c106857b>] ? down_timeout+0x6b/0x70
 [<c11dd333>] ? acpi_os_wait_semaphore+0x46/0x64
 [<c11f296a>] ? acpi_ex_system_wait_mutex+0x40/0x62
 [<c11eceff>] ? acpi_ev_acquire_global_lock+0x4f/0xd1
 [<c11f48e7>] ? acpi_ex_acquire_mutex_object+0x3e/0x75
 [<c11f44d9>] ? acpi_ex_acquire_global_lock+0x2a/0x59
 [<c11ef897>] ? acpi_ex_write_data_to_field+0x15b/0x18d
 [<c11f3fbd>] ? acpi_ex_store_object_to_node+0x91/0xdb
 [<c11f417e>] ? acpi_ex_store+0xaa/0x208
 [<c11f1d71>] ? acpi_ex_opcode_1A_1T_1R+0x3f9/0x544
 [<c11f257a>] ? acpi_ex_resolve_operands+0x188/0x416
 [<c11e9167>] ? acpi_ds_exec_end_op+0xd3/0x36c
 [<c11fb18e>] ? acpi_ps_parse_loop+0x5ff/0x76d
 [<c11e9985>] ? acpi_ds_call_control_method+0x159/0x1c4
 [<c11fa51c>] ? acpi_ps_parse_aml+0x8b/0x28f
 [<c11fbae6>] ? acpi_ps_execute_method+0x1a0/0x266
 [<c11f78da>] ? acpi_ns_evaluate+0xce/0x190
 [<c11f7347>] ? acpi_evaluate_object+0x180/0x27b
 [<d0b86314>] ? acpi_battery_get_state+0x69/0xdb [battery]
 [<d0b8670d>] ? acpi_battery_get_property+0x29/0x1ab [battery]
 [<c1248bb6>] ? power_supply_show_property+0x46/0x160
 [<c1306e44>] ? __mutex_lock_slowpath+0x1f4/0x2e0
 [<c1248b70>] ? power_supply_show_property+0x0/0x160
 [<c1230ad0>] ? dev_attr_show+0x30/0x70
 [<c114fc15>] ? sysfs_read_file+0xa5/0x160
 [<c116663b>] ? security_file_permission+0x1b/0x40
 [<c10f35f5>] ? vfs_read+0xc5/0x1b0
 [<c114fb70>] ? sysfs_read_file+0x0/0x160
 [<c10f37ff>] ? sys_read+0x5f/0xb0
 [<c1003cb3>] ? sysenter_do_call+0x12/0x28
INFO: task kacpid:10 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kacpid        D 00000000     0    10      2 0x00000000
 cf83a520 00000046 00000000 00000000 00000001 00000000 00000008 cf867d30
 00000000 cf283a80 00000020 c1489140 c1489140 cf83a6c8 c1484744 d179759a
 00000020 cf83a6c8 c1489140 c1489140 cf867d30 00000000 0ffeffc8 0ffeffc9
Call Trace:
 [<c1306545>] ? schedule_timeout+0x195/0x210
 [<c1036331>] ? update_curr+0x1e1/0x1f0
 [<c1307b30>] ? __down_timeout+0x60/0xa0
 [<c106857b>] ? down_timeout+0x6b/0x70
 [<c11dd333>] ? acpi_os_wait_semaphore+0x46/0x64
 [<c11f296a>] ? acpi_ex_system_wait_mutex+0x40/0x62
 [<c11eceff>] ? acpi_ev_acquire_global_lock+0x4f/0xd1
 [<c11f48e7>] ? acpi_ex_acquire_mutex_object+0x3e/0x75
 [<c11f44d9>] ? acpi_ex_acquire_global_lock+0x2a/0x59
 [<c11ef9d4>] ? acpi_ex_read_data_from_field+0x10b/0x153
 [<c11f4e61>] ? acpi_ex_resolve_node_to_value+0x159/0x1e0
 [<c11f03cf>] ? acpi_ex_resolve_to_value+0x1bc/0x1d9
 [<c11ea469>] ? acpi_ds_evaluate_name_path+0x77/0xf9
 [<c11e9116>] ? acpi_ds_exec_end_op+0x82/0x36c
 [<c11fb18e>] ? acpi_ps_parse_loop+0x5ff/0x76d
 [<c11fa51c>] ? acpi_ps_parse_aml+0x8b/0x28f
 [<c11fbae6>] ? acpi_ps_execute_method+0x1a0/0x266
 [<c11f78da>] ? acpi_ns_evaluate+0xce/0x190
 [<c11f7347>] ? acpi_evaluate_object+0x180/0x27b
 [<c11e20c3>] ? acpi_ec_gpe_query+0x8d/0xd7
 [<c11dd390>] ? acpi_os_execute_deferred+0x0/0x54
 [<c11dd3c7>] ? acpi_os_execute_deferred+0x37/0x54
 [<c105cfdf>] ? worker_thread+0x11f/0x280
 [<c1062d40>] ? autoremove_wake_function+0x0/0x60
 [<c105cec0>] ? worker_thread+0x0/0x280
 [<c10628ec>] ? kthread+0x8c/0xa0
 [<c1062860>] ? kthread+0x0/0xa0
 [<c10048e7>] ? kernel_thread_helper+0x7/0x10
INFO: task hald:2970 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
hald          D 093fc0d0     0  2970      1 0x00000000
 cf1454a0 00000082 00000000 093fc0d0 cfa65c14 cfa65f94 00000001 cfa65c20
 c13115c0 cf283a80 56811831 c1489140 c1489140 cf145648 c1484744 00000000
 cf1454a0 cf145648 c1489140 c1489140 ffff4e72 00000000 00000000 cf1454a0
Call Trace:
 [<c1104f80>] ? pollwake+0x0/0x80
 [<c1306545>] ? schedule_timeout+0x195/0x210
 [<c1104f80>] ? pollwake+0x0/0x80
 [<c1104f80>] ? pollwake+0x0/0x80
 [<c1307b30>] ? __down_timeout+0x60/0xa0
 [<c106857b>] ? down_timeout+0x6b/0x70
 [<c11dd333>] ? acpi_os_wait_semaphore+0x46/0x64
 [<c11f296a>] ? acpi_ex_system_wait_mutex+0x40/0x62
 [<c11eceff>] ? acpi_ev_acquire_global_lock+0x4f/0xd1
 [<c11f48e7>] ? acpi_ex_acquire_mutex_object+0x3e/0x75
 [<c11f44d9>] ? acpi_ex_acquire_global_lock+0x2a/0x59
 [<c11ef897>] ? acpi_ex_write_data_to_field+0x15b/0x18d
 [<c11f3fbd>] ? acpi_ex_store_object_to_node+0x91/0xdb
 [<c11f417e>] ? acpi_ex_store+0xaa/0x208
 [<c11f1d71>] ? acpi_ex_opcode_1A_1T_1R+0x3f9/0x544
 [<c11f257a>] ? acpi_ex_resolve_operands+0x188/0x416
 [<c11e9167>] ? acpi_ds_exec_end_op+0xd3/0x36c
 [<c11fb18e>] ? acpi_ps_parse_loop+0x5ff/0x76d
 [<c11e9985>] ? acpi_ds_call_control_method+0x159/0x1c4
 [<c11fa51c>] ? acpi_ps_parse_aml+0x8b/0x28f
 [<c11fbae6>] ? acpi_ps_execute_method+0x1a0/0x266
 [<c11f78da>] ? acpi_ns_evaluate+0xce/0x190
 [<c11f7347>] ? acpi_evaluate_object+0x180/0x27b
 [<d0b86314>] ? acpi_battery_get_state+0x69/0xdb [battery]
 [<d0b8670d>] ? acpi_battery_get_property+0x29/0x1ab [battery]
 [<c1248bb6>] ? power_supply_show_property+0x46/0x160
 [<c1306e44>] ? __mutex_lock_slowpath+0x1f4/0x2e0
 [<c1248b70>] ? power_supply_show_property+0x0/0x160
 [<c1230ad0>] ? dev_attr_show+0x30/0x70
 [<c114fc15>] ? sysfs_read_file+0xa5/0x160
 [<c116663b>] ? security_file_permission+0x1b/0x40
 [<c10f35f5>] ? vfs_read+0xc5/0x1b0
 [<c114fb70>] ? sysfs_read_file+0x0/0x160
 [<c10f37ff>] ? sys_read+0x5f/0xb0
 [<c1003cb3>] ? sysenter_do_call+0x12/0x28

When I get these messages, restarting the hal daemon fails, I have to reboot the laptop to get hal running right again. But I don't really know if this is related to the wireless card issue, because those hal messages don't appear every time the wireless card firmware won't load.

So has anyone seen this before and know what's going on? And if not, where should I be digging to perhaps find an answer?

miau

Member

Registered: 2009-05-06

Posts: 202

Re: WG511 only works when laptop started on AC power

Maybe you have a broken dsdt table? You could check fo errors using this guide: http://en.gentoo-wiki.com/wiki/ACPI/Fix_common_problems

The WG511 uses different chipsets reagrding which version of the WG511 you have. Have you checked which one its uses or which version you have? Not all versions are supported by prism54. Have you tried Ndiswrapper?

Last edited by miau (2009-12-01 10:14:03)