hrev56140 - NIC doesn't configure/enable anymore

[cocobean]

After doing 'pkgman full-sync' to hrev56140, NIC doesn't auto-configure anymore in OS after reboot Had to manually disable/re-enable it in desktop GUI.

• Vendor - 10ec: Realtek Semiconductor Corp
• Device - 8168: RTL8111/8168/8411 PCIe Gigabit Ethernet Controller

Test:

1. ifconfig - (Result: 0 packets)
2. pkgman full-sync - (Result: Could not resolve host issue)

Note: May work after manually reconfiguring/re-enabling NIC.

[bipolar]

Similar issue, same hardware, except that on some boots network does never works. In others, it gets up and ready without intervention, but... network perfomance is horrendous: ping 1.1.1.1 failures, downloads stalls, Webpositve loads one page, but hangs with the next, etc... until nothing works.

Selecting a previous state on the bootmanager (in my case, booting hrev56112) solves the issue.

Attempting to use hrev56112's rtl81xx driver on hrev56140 (after blacklisting the newer version on boot) sends me to KDL (so much for me trying to be find a workaround :-P)

I'll boot again with hrev56140 to get a "clean" syslog and I'll upload one for hrev56140 and one from hrev56112 (writing this while on the latter).

[bipolar]

Syslog of RTL81xx working on hrev56112

[bipolar]

Syslog of RTL81xx "working" (very poorly, unusable, really) on hrev56140

[cocobean]

See: ​https://git.haiku-os.org/haiku/log/?qt=range&q=hrev56138..hrev56139

I was able to get it working and update to hrev56141. Reading syslog, I saw this note:

hrev56141: KERN: [rtl81xx] (re) No memory for jumbo RX buffers

If you restart net-server, you should see the stall issue during 'Network Configuration' to 'Network Ready' status within the desktop. You can also do 'ifconfig <net device> auto-config up' and see if it works correctly (i.e. 'Network configuring' to 'Network Ready' status) and returns to the command prompt.

[waddlesplash]

Attempting to use hrev56112's rtl81xx driver on hrev56140 (after blacklisting the newer version on boot) sends me to KDL

If you use one from hrev56131+ it should work.

Syslog of RTL81xx "working"

Do you have one of it not working? (Do you see the same error messages cocobean does in any of them?)

[bipolar]

Replying to waddlesplash:

Do you have one of it not working?

I'll attach one (I found it on syslog.old, I split that one into the three different boots logs it contained, will upload the one where it didn't work).

On *this* cold-boot, hrev56140 networking got "Ready" without intervention, and seems to be working so far after browsing a couple of pages at least). Really weird. I'll triple check to see if there's any pattern related to warm vs cold boots.

(Do you see the same error messages cocobean does in any of them?)

I definitively remember seing that KERN: [rtl81xx] (re) No memory for jumbo RX buffers at least once.

And... it is present on the syslog that I'll attach next.

Hope that help. Again, really weird that (for) now seems to be working.

[bipolar]

Syslog of hrev564140 with "no memory for jumbo RX buffers"