Idualwifi7260 failed to initialise

Feedback Hardware
1

The system can recognise the device but the wireless options does not appear in the network manager.
I’ve just upgraded to the latest nightly, still not working

Here is the result from listdev:

device Network controller [2|80|0]
vendor 8086: Intel Corporation
device 08b1: Wireless 7260

Thanks in advance

UPDATE1:
I did some furthur investigation I found the following errors appeared in the syslog:

~> cat /boot/system/var/log/syslog | grep 7260
KERN: pci_reserve_device(3, 0, 0, idualwifi7260)
KERN: [idualwifi7260] (iwm) bus_alloc_resource(3, [16], 0x0, 0xffffffffffffffff, 0x1,0x2)
KERN: [idualwifi7260] (iwm) bus_alloc_resource(1, [1], 0x0, 0xffffffffffffffff, 0x1,0x2)
KERN: package_daemon [9272600: 549] active package: “becjk-1.0.1-3-x86_64.hpkg”
KERN: package_daemon [9272602: 549] active package: “kcompletion-5.50.0-1-x86_64.hpkg”
KERN: package_daemon [9272603: 549] active package: “attica-5.50.0-1-x86_64.hpkg”
KERN: package_daemon [9272604: 549] active package: “scons-2.5.1-3-x86_64.hpkg”
KERN: package_daemon [9272606: 549] active package: “less-542-1-x86_64.hpkg”
KERN: package_daemon [9272607: 549] active package: “lpsolve-5.5.2.5-3-x86_64.hpkg”
KERN: package_daemon [9272608: 549] active package: “haiku_userguide_sv_se-r1~beta1_hrev52791-1-any.hpkg”
KERN: [idualwifi7260] (iwm) fw chunk addr 0x800000 len 81920 failed to load
KERN: [idualwifi7260] (iwm) iwm_pcie_load_section: Could not load the [0] uCode section
KERN: [idualwifi7260] (iwm) iwm_start_fw: failed -2147483639
KERN: [idualwifi7260] (iwm) Failed to start INIT ucode: -2147483639
KERN: pci_unreserve_device(3, 0, 0, idualwifi7260)

Is this relates to my hardware? Or a driver bug?

2

We’ll have to try after hrev52792, according to Waddlesplash. Right now it’s at hrev72791 (for x64).

3

I am already at 52792, still not working :frowning:

4

Did you build your own 52792?

5

No, I upgrade through pkgman

6

Oh! Okay. I’ll have to give it a whirl and see if it works on mine (I’m guessing it won’t).

But if it does, then I can go through the joys of opening up the case and re-attaching those microscopic antenna leads.

7

I have reopened the ticket for this https://dev.haiku-os.org/ticket/14298
Maybe I will try to compile the driver by myself to see if this really works :smile:

1 Like
8

Can confirm. I just went up to hrev52796 and I’m getting the same thing with no Wi-Fi adapters.

9

No, compiling it yourself won’t change anything. Unless you know how to write driver code and can attempt a fix…

I’ll try talking to the FreeBSD developers and see if they have any ideas.

2 Likes
10

I am sure it’s a bug in FreeBSD 12, tested just now :slight_smile:

11

Has anyone tried FreeBSD 13?

12

There are no changes in FreeBSD trunk to iwm that I have not already merged into Haiku. (You can follow the log here.)

13

12 was just released. I don’t think there’s anything useful yet as far as 13.

14

FreeBSD “trunk” is 13 and there have been some pretty substantial changes to iwm there already…

1 Like
15

Okay. That makes sense. I might have to that a whirl to help test any differences. I just put together a new box with 8 cores and 32gb ram. It screams through builds compared to my other systems.

16

@MrEntropy, @masaol: There was a bug in the firmware load routine that I’ve fixed in hrev52798. @axeld already tested this and said it didn’t help there, so don’t expect much, but it might be worth re-testing anyway.

17

Groovy. I’ll give it a whack when I get home!

18

I did give this a whirl, and it did not change anything. As predicted.

19

This problem still exists in the latest version. I am thinking maybe try fresh MBR installation?

20

After reinstalled haiku with MBR, problem solved. It’s kinda weird :confused: