Intel(R) I211 Gigabit does't work

[pragmavalue]

hrev52359.

My network card does't work with Haiku.

[korli]

Please post a syslog, indicate hrev and architecture. see https://dev.haiku-os.org/wiki/ReportingBugs

[diver]

Does it work in FreeBSD? The attached syslog doesn't contain any information about your NIC. Please attach listdev output.

[waddlesplash]

Added in hrev52442.

[taos]

As you've probably read in #14999, it doesn't work for me with hrev53047 64bit. The Intel I211-AT is recognized as /dev/net/ipro1000/0 but is indefinitely stuck at "configuring" and won't get an IP address per DHCP (manually assigning an IP didn't work either).

In case there are different I211 chips around, mine is:

device Network controller (Ethernet controller) [2|0|0]
  vendor 8086: Intel Corporation
  device 1539: I211 Gigabit Network Connection

It works under a FreeBSD 12.0 Release LiveCD (recognized as igb0, DHCP with dhclient).

[pragmavalue]

Still don't work. I don't have a FreeBSD and don't check.

[waddlesplash]

Did it work on hrev52442 or a hrev near there? I did some major refactors since then which may have broken it.

[taos]

Seems I can't check with the Ryzen 5 system from #14999 since it's going straight to KDL with hrev52443 anyboot. Does it make sense to extract the ipro1000 driver from that revision and put it into non-packaged to see what happens?

[waddlesplash]

Yes.

[bga]

Is it possible this is related to the ipro1000 issues I am seeing? https://dev.haiku-os.org/ticket/15016

[waddlesplash]

Possibly, but as this card seems to initialize and then just fails to send traffic, perhaps not.

[bga]

I am pretty sure my card initializes to. But then it deadlocks somewhere.

I will do a guarded heap build later today and see if I can find something in any case.

[taos]

Put the ipro1000 from hrev52443 in /non-packaged/add-ons/kernel/drivers/bin/, rebooted -> ipro1000 stuck at "Configuring...". Rebooted again with blacklisted ipro1000 -> no ipro1000 found.

[waddlesplash]

You have to reboot and then copy the driver into non packaged. You can't copy it in before rebooting with the blacklist.

[taos]

Rebooting with blacklisted ipro1000 -> no ipro1000 -> moving ipro1000 out of non-packaged, moving it back -> ipro1000 appears, listimage shows that the driver in non-packaged is used -> ipro1000 stuck at "Configuring ..."

[pragmavalue]

Thanks!

in hrev53106 NIC work fine. Please close

[taos]

Unfortunately, it still doesn't work for me with hrev53106 anyboot.

[taos]

Replying to pragmavalue:

Thanks!

in hrev53106 NIC work fine. Please close

How did you get it to work? Are you using gcc2 hybrid or 64 bit?

[taos]

Ah, it works if "Enable UEFI Network Stack" is activated in UEFI BIOS (this option is only there to make it possible to boot from PXE). So far (3 Linux distributions, Windows, FreeBSD), Haiku seems the only operating system in need of this option for a working LAN connection.

[waddlesplash]

That probably means that EFI initializes the chip in some way that we are missing. As it works on FreeBSD, this probably implies something at the PCI level or the like, I'd guess.

[waddlesplash]

hrev53174 probably fixes that bug.

[taos]

Checked with hrev53176 64bit. Unfortunately, without activated "Enable UEFI Network Stack" ipro1000 is still stuck at "Configuring ...".

[taos]

syslog from hrev53176 with "Enable UEFI Network Stack" activated in UEFI BIOS

[taos]

syslog excerpt relevant to igb from hrev53176 with "Enable UEFI Network Stack"

[taos]

syslog excerpt relevant to igb from hrev53176 without "Enable UEFI Network Stack"

[taos]

syslog from hrev53176 without "Enable UEFI Network Stack" activated in UEFI BIOS

[taos]

After the update from hrev53379 to hrev53523, I'm greeted with a KDL during boot if ipro1000 is not blacklisted. I'll probably have to open a new ticket for this regression.

[waddlesplash]

Yes, please do.

[taos]

I opened ticket #15402 for this.

[nielx]

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone