Opened 2 years ago
Last modified 23 months ago
#18064 new bug
iprowifi4965 not working correctly after update
Reported by: | yann64 | Owned by: | waddlesplash |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Network/iprowifi4965 | Version: | R1/beta3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Decided to update my Dell Latitude e6430 to the latest nightly ( hrev56588 ).
iprowifi4965 wireless adapter used to work properly. Now it cannot connect to wifi anymore (and stangely wifi networks are only partially detected if I compare with what is detected by Ubuntu on the exact same computer, same location)
Attachments (6)
Change History (25)
by , 2 years ago
by , 2 years ago
Attachment: | screenshot-haiku.png added |
---|
by , 2 years ago
Attachment: | screenshot-linux.png added |
---|
comment:2 by , 2 years ago
wpa_supplicant version seems correct: package_daemon: [9456848: 684] active package: "wpa_supplicant-2.10.haiku.2-1-x86_64.hpkg"
comment:3 by , 2 years ago
A bit of context: I did an update a few weeks ago (prior to that, wifi used to be working erratically, connecting was difficult but at least it once connected everything was running smoothly), and with that update wifi was not working anymore. Looking at recent comments on the forum about the wpa_supplicant I did an upgrade to the latest nightly the days of this bug report. No improvement from to his update.
comment:4 by , 2 years ago
FWIW, my "device 088e: Centrino Advanced-N 6235" still works with the iprowifi4965 driver.
comment:5 by , 2 years ago
Please try to narrow down exactly when things broke, i.e. between what hrevs.
comment:6 by , 2 years ago
I have a similar problem on hrev56588. Thinkpad x230 with iprowifi4965 which used to work. Seems can't load the firmware. I don't exactly remember when the problem first occurred, but in my memory seems to happen after the OpenBSD drivers were introduced (don't say that's the reason, just giving a time frame).
KERN: /dev/net/iprowifi4965/0: link down, media 0x20080 quality 1000 speed 0 KERN: [iprowifi4965] (iwn) iwn_read_firmware: ucode rev=0x12a80601 KERN: [iprowifi4965] (iwn) iwn5000_load_firmware: could not load firmware .text section, error -2147483639 KERN: [iprowifi4965] (iwn) iwn_hw_init: could not load firmware, error -2147483639 KERN: [iprowifi4965] (iwn) iwn_init_locked: could not initialize hardware, error -2147483639 KERN: [net/iprowifi4965/0] stop running, 1 vaps running KERN: [net/iprowifi4965/0] ieee80211_new_state_locked: pending INIT → SCAN transition lost KERN: [net/iprowifi4965/0] ieee80211_new_state_locked: INIT → INIT (nrunning 0 nscanning 0) KERN: [net/iprowifi4965/0] down parent KERN: [net/iprowifi4965/0] ieee80211_newstate_cb: INIT → INIT arg -1 KERN: [net/iprowifi4965/0] sta_newstate: INIT → INIT (-1)
comment:8 by , 2 years ago
for my problem, it seems very similar to ticket #16789
I need to add from listdev: vendor:8086 device:0891 Centrino Wirelss-N2200.
Could it be that it is trying to load the iwn5000 firmware instead?
comment:9 by , 2 years ago
Restarted the computer to start testing... and to my surprise it now works properly (did not do any upgrade nor changed any settings). I am still on hrev56588.
I'll attach a syslog, maybe there is a clue as to why it started working? Only difference I can think of with last tests is this time the pc was off for two weeks instead of simply being simply being rebooted.
Forgot to add, machine boots using EFI.
follow-up: 14 comment:10 by , 2 years ago
Please don't close the ticket. I have the same problem as quentinsk describes. Same time frame. Thinkpad X1 with iprowifi4965 Centrino Advanced-N 6205 (Taylor Peak) Beta 4 hrev56578+59
comment:11 by , 2 years ago
Component: | Network & Internet/Wireless → Drivers/Network/iprowifi4965 |
---|---|
Owner: | changed from | to
Platform: | x86-64 → All |
comment:12 by , 2 years ago
Please see if booting cold or warm rebooting affects things, or reboot a few times and see if it "eventually" works.
comment:13 by , 2 years ago
OK, cold start - 2x warm boot - cold start. Unfortunately no joy. Syslog follows. Note: this did work for years. Thought that problem is only temporary during your work with the driver. But it is still broken.
comment:14 by , 2 years ago
Replying to vercu:
Please don't close the ticket. I have the same problem as quentinsk describes. Same time frame. Thinkpad X1 with iprowifi4965 Centrino Advanced-N 6205 (Taylor Peak) Beta 4 hrev56578+59
hrev56578+65 64 bit my "device 088e: Centrino Advanced-N 6235" still works fine with the iprowifi4965 driver.
comment:15 by , 2 years ago
So problem is back on my side. Cold/warm reboot will not change anything. I can see the network I want to connect to but Haiku will not connect to ity (althouh its settings are clearly stored).
Bit it gets really weird: Selecting the network will pop-up the password selection box (with the password stored), re-entering the password does nothing (will not connect). I installed a WiFi repeater (different SSID/Password combination), selected the new SSID in Haiku, entered the password... and Haiku connected to my previsouly "unselectable" network withouyt any issue!
Will add my latest syslog
by , 2 years ago
Attachment: | syslog.new.SSID.connects.to.previously.selected.network added |
---|
Syslog: "normal" wifi connect fails, entering new network with different SSID/Password ignores the new network but allows connecting to previoulsy "unconnectable" network
comment:16 by , 2 years ago
the scan somehow keeps resulting in just a few of the 5GHz networks, despite abundance of 2.4 ones, some from same routers even
comment:17 by , 23 months ago
I've just had an inspiration and discovered my issue is coming from booting with uefi. I changed back to boot with normal bios in legacy mode and everything is working correctly now.
comment:18 by , 23 months ago
I can not confirm this. My notebook runs Haiku with BIOS in legacy mode. Note: the wpa supplicant reports a wrong password. That is not correct. The password did not change and it works with my USB WIFI adapter.
comment:19 by , 23 months ago
Further testing shows on my side that if I keep the computer on long enough, Haiku will eventually connect.
I have not yet managed to time exactly how long is needed for wifi to work correctly again.
Check the differences of what is detected in Haiku hrev56588 vs Ubuntu 22.10 (see attached screen shots)