Kulp K8-B intermittent no network on boot

[timdt74]

Hello all,

Looking for a little help. I shut down all my Pi's and kulp every night and then cut power. I then power up everything 15 minutes before my show starts.

My Kulp K8-B boots with "No Network" about 20% of the time with the other 80% connecting just fine.

I have a dedicated network for my show that only includes the following. Nothing else is on the network.

Router with built in 4 port switch
F16V3 (ethernet to switch) 192.168.1.2
Pi with Matrix hat (wireless) 192.168.1.3 FFP5.3
Kulp K8-B (ethernet to switch) 192.168.1.4 FFP6.2
Pi with Matrix hat (ethernet to switch) 192.168.1.5 FFP6.2
Pi player (ethernet to switch) 192.168.1.6 FFP6.2


I have been experiencing this since last years show when I was running FFP 5.0-5.3. I upgraded to 6.2 this year with a fresh install but I am still experiencing the same issue.

Trouble shooting...
I have changed the ethernet cable multiple times along with changing switch ports.

I have never had an issue with any of the Pi's or F16V3 connecting

[Poporacer]

I shut down all my Pi's and kulp every night and then cut power.

Are you shutting down the Router as well? If so, your FPP is probably trying to obtain a connection before your Router is ready, there is a boot delay option that was implemented for this exact scenario.

[timdt74]

I shut down all my Pi's and kulp every night and then cut power.

Are you shutting down the Router as well? If so, your FPP is probably trying to obtain a connection before your Router is ready, there is a boot delay option that was implemented for this exact scenario.

I am not shutting down the router, only the pi's, kulp and F16

[Kensington Graves]

Like Popo said, add a few seconds boot delay under the FPP Settings - System tab.  It will most likely fix your problem.

[fauxton]

There is a documented problem with a certain revision of the BBB that has a problem where the ethernet phy chip does not come cleanly out of reset and has this behavior.  If you post a good picture of the bottom of the BBB, I can identify it for you.

I dealt with this problem on a large system and it drove us nuts.