Opened 4 years ago

Closed 8 months ago

#16238 closed bug (invalid)

Could not power ON adapter: wimax/wifi 5150

Reported by: Bambr Owned by: waddlesplash
Priority: normal Milestone: Unscheduled
Component: Drivers/Network/iprowifi4965 Version: R1/beta2
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by Bambr)

Hello. Device is detected correctly in syslog, but iprowifi4965 says like:

(iwn) iwn_read_eeprom: could not power ON adapter, error -2147483639
(iwn) could not read EEPROM, error -2147483639

So, there is no such device in /dev/net/ and wifi is missing.

I remember that when there was linux on this laptop, I used rfkill command to turn on/off this wifi device. May be there is any similar tool under haiku?

Thanks.

Attachments (2)

syslog1 (143.7 KB ) - added by Bambr 4 years ago.
syslog.2021-09-24 (136.0 KB ) - added by Bambr 3 years ago.
Full syslog from the latest nightly build is attached. Thank you!

Download all attachments as: .zip

Change History (16)

comment:1 by Bambr, 4 years ago

Description: modified (diff)

comment:2 by waddlesplash, 4 years ago

Platform: x86-64All

Can you post your whole syslog, or at least the PCI: lines for the network device and any lines with "iwn" or "iprowifi" in them?

by Bambr, 4 years ago

Attachment: syslog1 added

comment:3 by Bambr, 4 years ago

Done.

comment:4 by waddlesplash, 4 years ago

This actually looks very similar to #14265, but that's for a much older generation of Intel hardware. Maybe they have a common cause somehow?

comment:5 by Bambr, 4 years ago

No idea :( Please tell me if I can check something else. Probably I will be AFK till Sunday, but then I will try to give you all the information you need.

comment:6 by waddlesplash, 4 years ago

Can you test on a FreeBSD desktop? Not sure what the best distribution to use at this point is...

comment:7 by Bambr, 4 years ago

Hello, I'm back again. Checked with FreeBSD 12, it works.

comment:8 by Bambr, 4 years ago

Hi. Can this issue be fixed or it is too strange/uncommon to be fixed? Just tell me if you need any assistance from me, I will try. Anyway, thank you for your work!

comment:9 by waddlesplash, 4 years ago

I have no great ideas about what causes this. I can ask the FreeBSD developers but I think I asked before for the older ticket and did not get much enlightenment. So as I don't have any way to investigate this easily, unless you want to try and fix it yourself, it may stay in limbo for some time...

comment:10 by diver, 4 years ago

Is this in UEFI mode or BIOS?

comment:11 by Bambr, 4 years ago

BIOS. Laptop is too old to have UEFI

comment:12 by korli, 3 years ago

Could you attach the pci part of the syslog with the wireless device?

by Bambr, 3 years ago

Attachment: syslog.2021-09-24 added

Full syslog from the latest nightly build is attached. Thank you!

comment:13 by waddlesplash, 3 years ago

Please retest after hrev55890; it may help with this.

comment:14 by waddlesplash, 8 months ago

Resolution: invalid
Status: newclosed

No reply.

Note: See TracTickets for help on using tickets.