On Thu, Jan 02, 2025 at 05:34:57PM -0800, E Shattow wrote: > Tom sorry about sending this reply twice, struggle here is with Thunderbird > mail UI sometimes hiding "Reply All" and it missed the mail list first time > around.
No problem. > On 1/2/25 14:47, Tom Rini wrote: > > On Thu, Jan 02, 2025 at 02:26:06PM -0800, E Shattow wrote: > > > Problem: 'dhcp' must be ran twice when the network cable is plugged into a > > > port other than the first network port. > > > > > > Network cable plugged into bottom (first) Ethernet port: > > > 1. Power on > > > 2. StarFive # dhcp > > > > > > ethernet@16030000 Waiting for PHY auto negotiation to complete....... done > > > DHCP client bound to address 192.168.2.51 (3678 ms) > > > > > > > > > Network cable plugged into top (second) Ethernet port: > > > 1. Power on > > > 2. StarFive # dhcp > > > ethernet@16030000 Waiting for PHY auto negotiation to complete......... > > > TIMEOUT ! > > > phy_startup() failed: -110 > > > FAILED: -110 > > > ethernet@16040000 Waiting for PHY auto negotiation to complete...... done > > > ethernet@16030000 Waiting for PHY auto negotiation to complete......... > > > TIMEOUT ! > > > phy_startup() failed: -110 > > > FAILED: -110 > > > Could not start ethernet@16030000 > > > 3. StarFive # dhcp > > > DHCP client bound to address 192.168.2.77 (31 ms) > > > > What happens when you set ethact to 1 first? > > > > > '1' literal does not seem to do something so I guess it is meant the id of > the first ethernet interface: Yes, I misspoke sorry. > From power-on: > > ... > starfive_7110_pcie pcie@2b000000: Starfive PCIe bus probed. > starfive_7110_pcie pcie@2c000000: Starfive PCIe bus probed. > In: serial@10000000 > Out: serial@10000000 > Err: serial@10000000 > Net: eth0: ethernet@16030000, eth1: ethernet@16040000 > starting USB... > No USB controllers found > Working FDT set to ff700a10 > StarFive # env print ethact > ## Error: "ethact" not defined > StarFive # env set ethact 1 > StarFive # dhcp > ethernet@16030000 Waiting for PHY auto negotiation to complete......... > TIMEOUT ! > phy_startup() failed: -110 > FAILED: -110 > ethernet@16040000 Waiting for PHY auto negotiation to complete...... done > EQOS_DMA_MODE_SWR stuck > FAILED: -110 > Could not start ethernet@16030000 > > Again, from power-on: > > starfive_7110_pcie pcie@2b000000: Starfive PCIe bus probed. > starfive_7110_pcie pcie@2c000000: Starfive PCIe bus probed. > In: serial@10000000 > Out: serial@10000000 > Err: serial@10000000 > Net: eth0: ethernet@16030000, eth1: ethernet@16040000 > starting USB... > No USB controllers found > Working FDT set to ff700a10 > StarFive # env print ethact > ## Error: "ethact" not defined > StarFive # env set ethact ethernet@16040000 > StarFive # dhcp > ethernet@16040000 Waiting for PHY auto negotiation to complete...... done > DHCP client bound to address 192.168.2.77 (149 ms) So then yes, the second interface works when ethact is set to use that directly. This is the same behavior as the legacy stack I believe. -- Tom
signature.asc
Description: PGP signature
