#9479 closed bug (invalid)
No wireless connection with Intel Pro/Wireless 4965 AG (iprowifi4965 driver)
Reported by: | kostas | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Drivers/Network/iprowifi4965 | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
As stated above and on User Support Forum (Forum thread started by kostas on Sat, 2013-02-09 10:19), I have no wireless connection. My hardware (Intel Pro/Wireless 4965 AG) is recognised on all releases (Haiku R1 Alpha 4.1 and latest x86 GCC 2 Hybrid hrev45318), iprowifi4965 driver is loaded, but no wireless networks are detected.
Attachments (6)
Change History (16)
by , 12 years ago
Attachment: | syslog.txt added |
---|
by , 12 years ago
Attachment: | listdev.txt added |
---|
by , 12 years ago
Attachment: | listimage_grep_drivers.txt added |
---|
by , 12 years ago
Attachment: | listusb.txt added |
---|
comment:1 by , 12 years ago
Component: | - General → Network & Internet |
---|
(Changing component to Network & Internet for now, as I'm not sure if it's a network/dhcp issue or an issue with iprowifi4965.)
Looking at the syslog, the marvell_yukon fails continues to timeout on the DHCP request while the iprowifi4965 is attempting it as well. Does unplugging the wired connection improve the situation at all?
comment:2 by , 12 years ago
Wired connection works fine. Unplugging it does not improve things. Please note that following another suggestion to remove /boot/common/settings/network/interfaces and move marvel_yukon driver to Desktop, did not give better results either.
comment:3 by , 11 years ago
The driver has panicked because what is read from the EEPROM is invalid. I find this weird though. This could be a timing issue. Could you please try with a current nightly? Thanks!
KERN: iprowifi4965: init_driver(0x814799a0) KERN: [iprowifi4965] (iwn) bus_alloc_resource(3, [16], 0x0, 0xffffffff, 0x1,0x2) KERN: add_memory_type_range(3571, 0xf0700000, 0x20000, 0) KERN: set MTRRs to: KERN: mtrr: 0: base: 0x90000, size: 0x10000, type: 0 KERN: mtrr: 1: base: 0xa0000, size: 0x20000, type: 0 KERN: mtrr: 2: base: 0xc0000, size: 0x40000, type: 0 KERN: mtrr: 3: base: 0x7fed0000, size: 0x10000, type: 0 KERN: mtrr: 4: base: 0xe0000000, size: 0x20000000, type: 0 KERN: mtrr: 5: base: 0x80000000, size: 0x80000000, type: 1 KERN: allocate_io_interrupt_vectors: allocated 1 vectors starting from 24 KERN: msi_allocate_vectors: allocated 1 vectors starting from 24 KERN: [iprowifi4965] (iwn) bus_alloc_resource(1, [1], 0x0, 0xffffffff, 0x1,0x6) KERN: [iprowifi4965] (iwn) timeout reading ROM at 0x45 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0x48 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0x15 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0x60 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0x63 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0x72 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0x80 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0x8d KERN: [iprowifi4965] (iwn) timeout reading ROM at 0x99 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0xa0 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0xa8 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0xe8 KERN: [iprowifi4965] (iwn) timeout reading ROM at 0xea KERN: [iprowifi4965] (iwn) timeout reading ROM at 0xe9 KERN: [iprowifi4965] (iwn) MIMO 2T3R, , address %D KERN: if_initname(0x8242f000, iwn, 3) KERN: [iprowifi4965] iprowifi4965: /dev/net/iprowifi4965/0 KERN: PANIC: ieee80211_get_ratetable: no rate table for channel; freq 0 flags 0x0 KERN: KERN: Welcome to Kernel Debugging Land... KERN: Thread 92 "net_server" running on CPU 1 KERN: stack trace for thread 92 "net_server" KERN: kernel stack: 0x816d6000 to 0x816da000 KERN: user stack: 0x7efef000 to 0x7ffef000 KERN: frame caller <image>:function + offset KERN: 0 816d9888 (+ 32) 8013129e <kernel_x86> arch_debug_stack_trace + 0x12 KERN: 1 816d98a8 (+ 16) 8009270f <kernel_x86> stack_trace_trampoline(NULL) + 0x0b KERN: 2 816d98b8 (+ 12) 80123f32 <kernel_x86> arch_debug_call_with_fault_handler + 0x1b KERN: 3 816d98c4 (+ 48) 800941b2 <kernel_x86> debug_call_with_fault_handler + 0x5e KERN: 4 816d98f4 (+ 64) 8009292f <kernel_x86> kernel_debugger_loop([34m0x801700f7[0m [36m"PANIC: "[0m, [34m0x8146fb00[0m [36m"%s: no rate table for channel; freq %u flags 0x%x KERN: "[0m, [34m0x816d99a0[0m [36m"ËúF"[0m, int32: [34m1[0m) + 0x21b KERN: 5 816d9934 (+ 48) 80092c93 <kernel_x86> kernel_debugger_internal([34m0x801700f7[0m [36m"PANIC: "[0m, [34m0x8146fb00[0m [36m"%s: no rate table for channel; freq %u flags 0x%x KERN: "[0m, [34m0x816d99a0[0m [36m"ËúF"[0m, int32: [34m1[0m) + 0x53 KERN: 6 816d9964 (+ 48) 8009453e <kernel_x86> panic + 0x36 KERN: 7 816d9994 (+ 48) 81446631 </boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965> ieee80211_get_ratetable + 0xf9 KERN: 8 816d99c4 (+ 64) 8142b293 </boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965> ieee80211_chan_init + 0x23f KERN: 9 816d9a04 (+ 64) 8142cc8b </boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965> ieee80211_media_init + 0x3b KERN: 10 816d9a44 (+ 64) 8142b6af </boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965> ieee80211_ifattach + 0x97 KERN: 11 816d9a84 (+ 64) 8141c5ce </boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965> iwn_attach + 0x5ba KERN: 12 816d9ac4 (+ 48) 8145dd34 </boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965> device_attach + 0x3c KERN: 13 816d9af4 (+ 64) 8145f102 </boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965> _fbsd_init_drivers + 0x16a KERN: 14 816d9b34 (+ 48) 8142ae6d </boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965> __haiku_handle_fbsd_drivers_list + 0x31 KERN: 15 816d9b64 (+ 48) 8142aec2 </boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965> init_driver + 0x22
by , 9 years ago
comment:5 by , 9 years ago
Component: | Network & Internet → Drivers/Network/iprowifi4965 |
---|---|
Keywords: | Intel Pro/Wireless 4965 AG removed |
Version: | R1/alpha4.1 → R1/Development |
comment:9 by , 6 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
No reply in 6 months, closing as invalid.
comment:10 by , 5 years ago
Milestone: | R1 |
---|
Remove milestone for tickets with status = closed and resolution != fixed
/var/log/syslog