Hi, i got two HP Prodesk 600 G3 Mini. When i connect them to RJ45, its recognized as 10mbit, the red LED on the hp is flashing every few seconds. I can also not connect. Anyone an idea whats going on? The same device worked on another router (was at a friends location). I changed ports and cables, no help, still the same. Could this be some kind of incompatibility between HP and the BPI-R4?
You have to at least post ethtool output to show supported/advertised modes of both sides.
1 Like
will try to gather that later - will be a PITA because i have no connection from router->prodesk, maybe i can connect a screen to the prodesk and take a picture or so
from the router (i used the port where the voip phone was on, thats why there is so much traffic listed):
wan Link encap:Ethernet HWaddr 36:A9:D6:BC:EE:E0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:336800 errors:0 dropped:19924 overruns:0 frame:0
TX packets:1808768 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:86174634 (82.1 MiB) TX bytes:767199922 (731.6 MiB)
root@OpenWrt:~# ethtool wan
Settings for wan:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 10Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: external
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: d
Wake-on: d
Link detected: yes
from one of the incompatible mini pcs:
root@xxx:~# ethtool eno1
Settings for eno1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: no
somehow r4 only sees 10Mbit advertised from your HP-Box, on HP-Box it seems good…afair you can enable dynamic debug (if enabled in kernel) to see the advertising-bits but based on output 1000baseT/Full is the highest supported mode from both sides and should be choosen…but on HP i miss the “Link-Partner advertised” block…maybe debugging on hp is easier and look if you get any advertisement from r4
its getting wierd now. i turned on debugging in the kernel options and now it gives me this:
root@OpenWrt:~# ethtool wan
Settings for wan:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: external
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: d
Wake-on: d
Link detected: yes
on the mini pc it shows:
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether f4:39:09:2c:2a:3d brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
altname enxf439092c2a3d
inet6 fd39:306b:5312:0:f639:9ff:fe2c:2a3d/64 scope global dynamic mngtmpaddr proto kernel_ra
valid_lft 5395sec preferred_lft 2695sec
inet6 2a02:168:859e:0:f639:9ff:fe2c:2a3d/64 scope global dynamic mngtmpaddr proto kernel_ra
valid_lft 3529sec preferred_lft 2529sec
inet6 fe80::f639:9ff:fe2c:2a3d/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
but i see no ipv4 and also the ethernet port of the mini pc is red blinking every x seconds
How does hp-clients ethtool looks like now? Ip address is next step (of course needs dhcp server on lan, and no conflicting dhcp server) when ethernet layer is up
Both sides now support dynamic debug? Maybe you have flapping interface or sonething like this? Check dmesg and stats (ethtool/ip)
Blinking leds are vendor specific 