Beta 4: network connection is constantly being activated and deactivated

[lelldorin]

My Realtek RTL 8188EU network card is not recognized correctly on 32 bit and 64 bit, because the connection is constantly being connected and then losing the connection again.

On Beta 3 there were no problems at all.

Hrev Beta 4 56578+59 (Update not possible, because instable network)

[waddlesplash]

Syslog please, from both systems.

[lelldorin]

beta 3 syslog

[lelldorin]

beta 4 syslog

[lelldorin]

where can i find the driver for the network card in the beta 3 so i can test if the beta 4 is running without problems with the driver?

[waddlesplash]

Driver ABI changed between beta3 and beta4, you will likely not be able to run the old driver on the new system.

[lelldorin]

Replying to waddlesplash:

Driver ABI changed between beta3 and beta4, you will likely not be able to run the old driver on the new system.

then I'll probably have to wait for the beta 5, which is a pity

[waddlesplash]

The problem appears to be:

KERN: [net/rtl81xx/0] watchdog timeout
KERN: /dev/net/rtl81xx/0: link down, media 0x22 quality 1000 speed 0
KERN: /dev/net/rtl81xx/0: link up, media 0x900030 quality 1000 speed 1000000000

THe device is:

KERN: PCI:   vendor 10ec: Realtek Semiconductor Co., Ltd.
KERN: PCI:   device 8168: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

[waddlesplash]

The changes to this driver between beta3 and beta4 were very insignificant. Perhaps the new MTU changes broke something. You can try setting a lower MTU and see if it stops the timeouts.

[lelldorin]

Replying to waddlesplash:

The changes to this driver between beta3 and beta4 were very insignificant. Perhaps the new MTU changes broke something. You can try setting a lower MTU and see if it stops the timeouts.

???

How to do that?

[waddlesplash]

via ifconfig.

[lelldorin]

Replying to waddlesplash:

via ifconfig.

Please give a answer for a user not for a scripting guy. I do not understand to make ifconfig doing that for me.

[bipolar]

@lelldorin:

I was able to change the MTU from my ipro1000 network interface, from it's original 9004 value, to 1024, like this:

> ifconfig /dev/net/ipro1000/0 mtu 1024

So, try with > ifconfig /dev/net/rtl81xx/0 mtu nnnn (replacing nnnn with the value you want, of course).

Maybe first use ifconfig without parameters to see what it is using by default?

Hope that helps!

[kim1963]

I have the same network card.

device Network controller (Ethernet controller) [2|0|0]

vendor 10ec: Realtek Semiconductor Co., Ltd.

device 8168: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

Haiku 64 bit hrev56578+64

IP addresses of the local network are installed statically. The network works without problems.

~> ifconfig /dev/net/rtl81xx/0

Hardware type: Ethernet, Address: 00:e0:67:20:3f:02 Media type: 1 GBit, 1000BASE-T inet addr: 192.168.1.107, Bcast: 192.168.1.255, Mask: 255.255.255.0 MTU: 9004, Metric: 0, up broadcast link Receive: 6983 packets, 0 errors, 5222413 bytes, 0 mcasts, 0 dropped Transmit: 6213 packets, 0 errors, 1133069 bytes, 0 mcasts, 0 dropped Collisions: 0

[kim1963]

It is possible that the problem with the settings of the router MTU?

[bruno]

syslog 32bit beta4

[bruno]

I have this problems too: device Network controller (Ethernet controller) [2|0|0]

vendor 10ec: Realtek Semiconductor Co., Ltd. device 8139: RTL-8100/8101L/8139 PCI Fast Ethernet Adapter

If I change the MTU to 1024 the network connection seems to get better! In Terminal I typed: ifconfig /dev/net/rtl8139/0 mtu 1504 Works somewhat but not sure if it is the best option.

I used Web+ for upload the syslog... gnome didnt do it°!

What else to do to check this connection out? syslog?

[lelldorin]

Replying to bipolar:

@lelldorin:

I was able to change the MTU from my ipro1000 network interface, from its original 9004 value, to 1024, like this:

> ifconfig /dev/net/ipro1000/0 mtu 1024

So, try with > ifconfig /dev/net/rtl81xx/0 mtu nnnn (replacing nnnn with the value you want, of course).

Maybe first use ifconfig without parameters to see what it is using by default?

Hope that helps!

Thanks but did not solve the problem. I add the network card as unsupported into the hardwarelist.

[bipolar]

Replying to lelldorin:

I add the network card as unsupported into the hardwarelist.

I, as well as kim1963 a few comments above, also have the same card (10ec:8168), and it works for both of us, so... maybe marked as "may or may not work" depending on your motherboard?

Maybe a subsystem_id/subvendor/hw-revision distinction?

Mine is specifically: Vendor=0x10ec Device=0x8168, subsystem_id=0x2307 subsystem_vendor_id=0x1562 Rev=02.

[waddlesplash]

lelldorin: Is there any change on a recent nightly here? If not, did you try and pinpoint when the problem started? Without more information, this won't be getting fixed.

[waddlesplash]

No reply. Moving out of beta5 milestone.

[waddlesplash]

Please retest after hrev57938. The recent changes to bus_dma bouncing may help here.

[roiredxsoto]

Good day,

Same here on hrev58198 x86_64. rtl81xx not transferring data though says it's connected to the network. Can´t connect through DHCP. It connects to the network via Static address then no activity at all.

Will add the logs as soon as I can.

Regards, RR

[pbuyle]

https://dev.haiku-os.org/ticket/19096 has some info.

It seems several of us have to trigger something in the UEFI/BIOS for our network adapter to work. I don't known much about netwrok hardware and drivers, but I suspect somerthing in the EUFI firmware initialize the network adapter when using the boot menu or boot diasgnostic which then allow it to work in Haiku.