#9263 closed bug (not reproducible)
Random iprowifi4965 failure on Intel 6230 wireless
Reported by: | kallisti5 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Network/iprowifi4965 | Version: | R1/Development |
Keywords: | iprowifi4965 | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
hrev44854 gcc4 iprowifi4965 driver
device Network controller [2|80|0] vendor 8086: Intel Corporation device 0089: Centrino Advanced-N + WiMAX 6250 [Kilmer Peak]
Generally the following happens on my laptop.
- Reboot - wireless networks found
- Reboot - no wireless networks found
- Reboot - no wireless networks found
- Reboot - wireless networks found
I've recorded a clean syslog from each situation.
Attachments (7)
Change History (29)
by , 12 years ago
Attachment: | 1-yes-syslog added |
---|
by , 12 years ago
Attachment: | 2-no-syslog added |
---|
by , 12 years ago
Attachment: | 3-no-syslog added |
---|
by , 12 years ago
Attachment: | 4-yes-syslog added |
---|
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Nice catch diver! Given the amount of spam from the wireless drivers I never picked up on that error :)
comment:3 by , 12 years ago
Component: | Network & Internet/Wireless → Drivers/Network/iprowifi4965 |
---|---|
Description: | modified (diff) |
Keywords: | iprowifi4965 added |
Owner: | changed from | to
Summary: | Erratic wireless network behaviour → Random iprowifi4965 failure on Intel 6230 wireless |
seems related: http://openbsd.7691.n7.nabble.com/Centrino-Advanced-N-6230-crystal-calibration-failed-td190575.html
Definitely a driver issue... renaming ticket.
by , 11 years ago
Attachment: | iprowifi4965_syslog added |
---|
Section of syslog when iprowifi4965 failed to appear in network
comment:4 by , 11 years ago
I assume my experience is related. I just got an iprowifi4965 card installed in my laptop, understanding it was compatible, but when I booted up it failed to appear in the Network Prefs (or in ifconfig's list). Rebooting (several times) didn't change things.
On Stefano's suggestion (via mailing list), I just did 'ifconfig /dev/net/iprowifi4965/0 up' and -- gosh! -- I now have wifi! If that's supposed to be needed this is not documented anywhere. Anyhow, we'll see if it stays up.
In any case, for completeness, I've attached the section of syslog for the wifi from the boot before I got it working.
comment:5 by , 11 years ago
I'm still seeing this issue as of hrev46224
Attaching complete logs. I tried doing a scan, and get no wireless networks. I tried doing a join, and it wouldn't connect.
I'll try an ifconfig up next time I boot the laptop. Wonder if some initilization step is failing and trying the up fixes it?
comment:6 by , 11 years ago
My Device:
device Network controller [2|80|0] vendor 8086: Intel Corporation device 0089: Centrino Advanced-N + WiMAX 6250 [Kilmer Peak]
by , 11 years ago
Attachment: | ifconfig-nowifi.txt added |
---|
by , 11 years ago
Attachment: | syslog-nowifif.txt added |
---|
follow-up: 14 comment:7 by , 11 years ago
I wonder if you actually might have a hardware problem? My 4965 seems to be behaving itself with the patch (I haven't updated the system in a while -- just applied the patch to the driver.) However, I see in your syslog these lines:
KERN: [iprowifi4965] (iwn) iwn5000_post_alive: crystal calibration failed, error -2147483637 KERN: [iprowifi4965] (iwn) iwn_init_locked: could not initialize hardware, error -2147483637
I've never seen this in my logs. Sounds suspicious...
follow-up: 9 comment:8 by , 11 years ago
hm.. looks like an ongoing issue in the BSD driver:
http://gnats.netbsd.org/45899
The card works fine under Linux.
comment:9 by , 11 years ago
Replying to kallisti5:
hm.. looks like an ongoing issue in the BSD driver:
The error in that certainly looks familiar...!
I notice that my hardware is actually slightly different, apparently. My device listing is just:
device Network controller [2|80|0] vendor 8086: Intel Corporation device 008a: Centrino Wireless-N 1030
so I guess it's not subject to the glitch.
comment:10 by , 11 years ago
I've ordered a replacement PCIe card for this laptop (BCM4322). Assuming that the replacement works in my machine, i'm offering this PCIe card free to any developer who wants to try and fix the BSD driver. Contact me for more information kallisti5 :A.T: unixzen.com
comment:11 by , 10 years ago
Milestone: | R1/beta1 → Unscheduled |
---|
As this is due to an upstream issue, i'm moving this to unscheduled as the only solution for this one is time (waiting on BSD to fix the issue)
comment:12 by , 10 years ago
comment:13 by , 7 years ago
I found the same issue with iprowifi2200 (on a Sony Vaio).
EDIT: ifconfig up after boot doesn't help.
follow-up: 15 comment:14 by , 7 years ago
Replying to Pete Goodeve:
just applied the patch to the driver
There is a patch for this driver, somewhere?
My WiFi adapter is reported as:
device Network controller [2|80|0] vendor 8086: Intel Corporation device 4220: PRO/Wireless 2200BG [Calexico2] Network Connection
Driver: /boot/system/add-ons/kernel/drivers/dev/net/iprowifi2200
And as I've said, I encounter the same issue as described in this ticket.
follow-up: 16 comment:15 by , 7 years ago
Replying to Giova84:
Replying to Pete Goodeve:
just applied the patch to the driver
There is a patch for this driver, somewhere?
Heh. Sorry -- I don't remember the details of that at all! I think I may have been referring to the suggestion to do an 'ifconfig up'. If so, I mis-spoke terribly! In any case, I'm sure any patch must have been applied long ago, as I now run the supplied driver without any patches. The only thing I do in the bootscript is "ifconfig /dev/net/iprowifi4965/0 -ht", but it doesn't seem to make much difference whether I do or not. I still seem to often lose WiFi after 1/2 hour or so.
comment:16 by , 7 years ago
Replying to Pete Goodeve:
I still seem to often lose WiFi after 1/2 hour or so.
To me happens exactly what Alexander reported: after a batch of reboots (or shutdown-power on), my wifi adapter is no longer able to find any network; I notice that I need three reboot to make it able again to find wifi networks.
By looking at the other comments, seems an issue from FreeBSD? So, after five years hasn't beed resolved yet? :-[
comment:17 by , 7 years ago
Sorry for the noise. I noticed that after about three hours, ths issue will back. If I do
ifconfig /dev/net/iprowifi2200/o up
and then I do a wifi scan, the adapter will find again all available wifi networks, but If I attemtp to join (doesn't matter if I join using command line or GUI), nothing will happen - I mean that it doesn't connect - and then the adapter loose again the ability to find networks; I can re-do ifconfig /dev/net/iprowifi2200/o up
to discover again wifi networks, but again it cannot connect.
Maybe there is a way to reload the driver? If I reload net_server, doesn't help.
comment:18 by , 7 years ago
Had the same symptomes today with a Intel Corporation Centrino Advanced-N 6235 [8086:088f] Subsystem: Device 6052:8680
I did found that the current Haiku driver doesn't list this PCIID, only the 088e one, so i patched the sources, built it, and got the well known messages:
KERN: [iprowifi4965] (iwn) iwn5000_post_alive: crystal calibration failed, error -2147483637 KERN: [iprowifi4965] (iwn) iwn_init_locked: could not initialize hardware, error -2147483637
I read a bit about it, and tought maybe the firmware should be updated, but Haiku have the latest firmware for this card-family (diffed the actual firmwares).
Then i noticed, the souce code checks for some kind of "pid" values, and depending their value it loads this or that firmware. I patched the source to load always the "iwn6000g2bfw" firmware.
After rebooting my wlan card works, i type this message trough wlan.
comment:19 by , 7 years ago
Please attach a diff (no need for a proper patch since this will probably need a rework). It will make it easier to see what you did and turn it into a more proper patch.
comment:22 by , 6 years ago
Resolution: | → not reproducible |
---|---|
Status: | new → closed |
From the first syslog:
Same place in the second syslog: