Wired network interface does not work

I did some tests at home. From what I can tell, the problem was not solved. Symptoms are the same. Although now I can see to appear the router assigned IP in the Settings / System Info / Network a few times after reboot. (That is when wireless NIC is disabled.)

Vero2 Logs: http://paste.osmc.io/qihaguraxu
Router logs:

Jan  8 11:47:23 dnsmasq-dhcp[2827]: DHCPDISCOVER(br0) 08:61:60:11:26:45 
Jan  8 11:47:23 dnsmasq-dhcp[2827]: DHCPOFFER(br0) 192.168.1.9 08:61:60:11:26:45 
Jan  8 11:47:24 dnsmasq-dhcp[2827]: DHCPREQUEST(br0) 192.168.1.9 08:61:60:11:26:45 
Jan  8 11:47:24 dnsmasq-dhcp[2827]: DHCPACK(br0) 192.168.1.9 08:61:60:11:26:45 vero2
Jan  8 11:47:28 dnsmasq-dhcp[2827]: DHCPREQUEST(br0) 192.168.1.9 08:61:60:11:26:45 
Jan  8 11:47:28 dnsmasq-dhcp[2827]: DHCPACK(br0) 192.168.1.9 08:61:60:11:26:45 vero2

etc.etc.

Yes, the remote seems to work well in the back port. Latency of the wireless keyboard is much better now (in any port) but the buffering problem remains. (Maybe I should have mentioned earlier, that it is not a bluetooth one, but with a custom radio receiver…)

I did some more tests, and found the problem.

Vero2 can’t talk properly with the switch I am using for wall cabling (happens to be Zyxel GS1100-16).

As a workaround, a have patched this one port directly to router. Everything seems to be working now, including getting address via DHCP.

I will try another switch…

Hi Michal

I tried to replicate this here (hence the slow reply) but was unable to do so.

I cannot imagine why this switch may be causing issues, but if you want I can produce a kernel with extremely verbose logging, as well as a couple of patches for the driver. This may give more clues.

Sam

Minor derail: would an update with optional in-depth debugging switch be a worthy ‘feature’ for all builds?

Probably not, as no one seems to have encountered this before

If you want / have nothing better to do, I will try it, why not.

From my point of view I have a working vero2 now, and can live with the workaround.

OK.

We can leave it for now. If it comes up again with other users I will build a new kernel with debugging.

I think Vero2 is misinterpreting power decreasing on the line (green feature of the switch) for line drop.

I can’t think another reason why would 6 EUR switch in between fix the problem. (Which it does, tried it today).

Is this a POE switch? Is it 802.13af compliant?

No, it is not PoE capable.

But according to its datasheet, it should be able to handle:
• IEEE 802.3 10BASE-T Ethernet
• IEEE 802.3u 100BASE-TX Ethernet
• IEEE 802.3ab 1000BASE-T Ethernet
• IEEE 802.3az EEE support
• IEEE 802.3x flow control
• IEEE 802.3z 1000BASE-X
• IEEE 802.1p CoS

I am not sure what the issue is.

I know flow control can sometimes cause issues. Unfortunately because it’s an unmanaged switch you won’t be able to configure this behaviour.