5:32 a.m.
When running RPi3B+, having set up wifi, boot hangs waiting for eth0. I haven't had
the
patience to see if it ever comes up, but it is hanging for minutes at least.
It boots reasonably if my ethernet cable is plugged in.
Regards,
Paul
6:30 a.m.
On Tue, Nov 6, 2018 at 12:22 PM Paul Kennedy <paul(a)the-kennedys.me.uk> wrote:
When running RPi3B+, having set up wifi, boot hangs waiting for eth0. I haven't had
the
patience to see if it ever comes up, but it is hanging for minutes at least.
It boots reasonably if my ethernet cable is plugged in.
At what point in the boot process is this?
7:26 a.m.
About 15 seconds into booting the ostree image:
libphy: lan78xx-mdiobus: probed
usbcore: registered new interface driver lan78xx
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
hmmm - maybe I need to disable ipv6?
8:09 a.m.
On 6 Nov 2018, at 13:26, Paul Kennedy <paul(a)the-kennedys.me.uk>
wrote:
About 15 seconds into booting the ostree image:
libphy: lan78xx-mdiobus: probed
usbcore: registered new interface driver lan78xx
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
hmmm - maybe I need to disable ipv6?
I doubt that IPv6 is an issue. It’s pretty mature, now. Here’s a snippet from a working
pi3:
```
[ 12.835851] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 12.852680] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 12.989948] random: crng init done
[ 13.002686] random: 7 urandom warning(s) missed due to ratelimiting
[ 14.276572] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 14.293706] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
```
That’s using the Oct 27 compose.
tc
_______________________________________________
IoT mailing list -- iot(a)lists.fedoraproject.org
To unsubscribe send an email to iot-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy2SVX...
List Guidelines:
https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy-2FV...
List Archives:
https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy8cAS...
8:42 a.m.
Sorry, I guess I haven't been clear - I want to boot WITHOUT wired ethernet connected.
It
works for me with an ethernet cable plugged in, but won't get past this without.
9:19 a.m.
On Tue, Nov 6, 2018 at 2:17 PM Paul Kennedy <paul(a)the-kennedys.me.uk> wrote:
About 15 seconds into booting the ostree image:
libphy: lan78xx-mdiobus: probed
usbcore: registered new interface driver lan78xx
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
hmmm - maybe I need to disable ipv6?
No, IPv6 should be fine, looking at dracut and the error message
originates from the 35network-legacy which we don't even ship. We'll
need to dig into why that module is even getting put into the initrd.
Peter
6:49 p.m.
I am seeing the same thing on the non-arm version as well. There seems to
be a hang if there is no IP on a detected Ethernet interface. I get to
"Reached target Basic System" and then sit there for ~150 seconds at which
point I get dracut messages. If I plug in an ethernet cable, the system
boots cleanly. When the system does boot correctly, it looks like the box
is doing a double lease:
192.168.1.75 00:01:c0:20:b2:ea 2018/11/11 22:03:44
2018/11/12 00:03:44 online active
192.168.1.74 00:01:c0:20:b2:ea 2018/11/11 22:03:33
2018/11/12 00:03:33 online active
I was able to cross verify this with a virtual instance by disconnecting
the NIC and the same thing happens. I am using the 11/06 build.
Dave
On Wed, Nov 7, 2018 at 10:09 AM Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Tue, Nov 6, 2018 at 2:17 PM Paul Kennedy
<paul(a)the-kennedys.me.uk>
wrote:
>
> About 15 seconds into booting the ostree image:
> libphy: lan78xx-mdiobus: probed
> usbcore: registered new interface driver lan78xx
> IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>
> hmmm - maybe I need to disable ipv6?
No, IPv6 should be fine, looking at dracut and the error message
originates from the 35network-legacy which we don't even ship. We'll
need to dig into why that module is even getting put into the initrd.
Peter
_______________________________________________
IoT mailing list -- iot(a)lists.fedoraproject.org
To unsubscribe send an email to iot-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org
11:46 p.m.
On Mon, Nov 12, 2018 at 1:40 AM Dave Hedge <itswag7(a)gmail.com> wrote:
I am seeing the same thing on the non-arm version as well. There seems to be a hang if
there is no IP on a detected Ethernet interface. I get to "Reached target Basic
System" and then sit there for ~150 seconds at which point I get dracut messages. If
I plug in an ethernet cable, the system boots cleanly. When the system does boot
correctly, it looks like the box is doing a double lease:
192.168.1.75 00:01:c0:20:b2:ea 2018/11/11 22:03:44 2018/11/12
00:03:44 online active
192.168.1.74 00:01:c0:20:b2:ea 2018/11/11 22:03:33 2018/11/12
00:03:33 online active
I was able to cross verify this with a virtual instance by disconnecting the NIC and the
same thing happens. I am using the 11/06 build.
I believe this is a regression in dracut, I've filed the following
upstream bug: https://github.com/dracutdevs/dracut/issues/488
> On Wed, Nov 7, 2018 at 10:09 AM Peter Robinson <pbrobinson(a)gmail.com> wrote:
>>
>> On Tue, Nov 6, 2018 at 2:17 PM Paul Kennedy <paul(a)the-kennedys.me.uk>
wrote:
>> >
>> > About 15 seconds into booting the ostree image:
>> > libphy: lan78xx-mdiobus: probed
>> > usbcore: registered new interface driver lan78xx
>> > IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> >
>> > hmmm - maybe I need to disable ipv6?
>>
>> No, IPv6 should be fine, looking at dracut and the error message
>> originates from the 35network-legacy which we don't even ship. We'll
>> need to dig into why that module is even getting put into the initrd.
>>
>> Peter
>> _______________________________________________
>> IoT mailing list -- iot(a)lists.fedoraproject.org
>> To unsubscribe send an email to iot-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org
>
> _______________________________________________
> IoT mailing list -- iot(a)lists.fedoraproject.org
> To unsubscribe send an email to iot-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org
1997
days inactive
2003
days old
7 comments
4 participants
participants (4)
-
Dave Hedge -
Paul Kennedy -
Peter Robinson -
Tim Coote