Opened 2 years ago

Last modified 22 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)

syslog (362.7 KB ) - added by yann64 2 years ago.
screenshot-haiku.png (46.3 KB ) - added by yann64 2 years ago.
screenshot-linux.png (28.1 KB ) - added by yann64 2 years ago.
syslog.2 (388.9 KB ) - added by yann64 2 years ago.
syslog following reboot
syslog-23-01-04.zip (58.3 KB ) - added by vercu 23 months ago.
syslog vercu 2023-01-04
syslog.new.SSID.connects.to.previously.selected.network (349.3 KB ) - added by yann64 23 months ago.
Syslog: "normal" wifi connect fails, entering new network with different SSID/Password ignores the new network but allows connecting to previoulsy "unconnectable" network

Download all attachments as: .zip

Change History (25)

by yann64, 2 years ago

Attachment: syslog added

by yann64, 2 years ago

Attachment: screenshot-haiku.png added

by yann64, 2 years ago

Attachment: screenshot-linux.png added

comment:1 by yann64, 2 years ago

Check the differences of what is detected in Haiku hrev56588 vs Ubuntu 22.10 (see attached screen shots)

  • Far fewer networks are detected on Haiku.
  • For those detected, signal intensity is lower on Haiku.
  • One of the few detected networks on Haiku does not have any SSID displayed. There are no network with hidden SSID in my vicinity.
  • It is impossible to connect to any network on Haiku, (so I have to use wired connection). I tried using
    ipconfig [adapter] join [SSID]
    
    but it fails on all networks.
Last edited 2 years ago by yann64 (previous) (diff)

comment:2 by korli, 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 yann64, 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 humdinger, 2 years ago

FWIW, my "device 088e: Centrino Advanced-N 6235" still works with the iprowifi4965 driver.

comment:5 by waddlesplash, 2 years ago

Please try to narrow down exactly when things broke, i.e. between what hrevs.

comment:6 by quentinsk, 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)
Last edited 2 years ago by korli (previous) (diff)

comment:7 by yann64, 2 years ago

Away from home this week. Will try to bisect the faulty hrev next week.

comment:8 by quentinsk, 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 yann64, 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.

Ticket can probably be closed unless something strange detected in the latest syslog.

Last edited 2 years ago by yann64 (previous) (diff)

by yann64, 2 years ago

Attachment: syslog.2 added

syslog following reboot

comment:10 by vercu, 23 months 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 waddlesplash, 23 months ago

Component: Network & Internet/WirelessDrivers/Network/iprowifi4965
Owner: changed from mmlr to waddlesplash
Platform: x86-64All

comment:12 by waddlesplash, 23 months 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 vercu, 23 months 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.

by vercu, 23 months ago

Attachment: syslog-23-01-04.zip added

syslog vercu 2023-01-04

in reply to:  10 comment:14 by kim1963, 23 months 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.

Last edited 23 months ago by kim1963 (previous) (diff)

comment:15 by yann64, 23 months 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 yann64, 23 months ago

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 mikafei, 22 months 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 quentinsk, 22 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.

Last edited 22 months ago by quentinsk (previous) (diff)

comment:18 by vercu, 22 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 yann64, 22 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.

Note: See TracTickets for help on using tickets.