[Buildroot] Plug/unplug ethernet connector does not detected on Raspberry PI3 B+

[Buildroot] Plug/unplug ethernet connector does not detected on Raspberry PI3 B+

[Oscar Gomez Fuente]

Hi everyone,

I'm using the HW: Raspberry Pi 3B+ and buildroot-2018.02.5 (with
LINUX_KERNEL_CUSTOM_REPO_VERSION="865ddc1393f558198e7e7ce70928ff2e49c4f7f6")
and I have the following problem.

I've started the system with the ethernet unplugged. After the system has
initiated completely, I log in using the uart console, and I plug the
ethernet cable, but I'm not able to up eth0 without executing ifup eth0
command.

This is my /etc/network/interface:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual
        pre-up /etc/network/wait_iface $IFACE 20
        pre-up /sbin/ip link set $IFACE up
        pre-up /etc/network/nfs_check
        pre-up /sbin/udhcpc -R -b -p /var/run/udhcpc.${IFACE}.pid -i $IFACE
        post-down /bin/kill -9 $(cat /var/run/udhcpc.${IFACE}.pid)
        post-down /sbin/ip link set $IFACE down

I would like that the ifup eth0 was executed automatically when the plug
ethernet cable is detected, but it seems to be when I plug/unplug the
ethernet cable the kernel isn't detect it.

I've check the same buildroot-2018.02.5 version in the Raspberry pi 3B
(instead of 3B+) and it works fine, so I think it's something related with
the driver associated to the phy LAN7515
The raspberry pi has the LAN9514.

Does anyone know if there is a problem with the driver associated with the
LAN9515 (Raspberry Pi 3B+)?

Best regards.

Oscar Gomez Fuente
TST Sistemas
www.tst-sistemas.es
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181003/0e29c87b/attachment.html>

[Buildroot] Plug/unplug ethernet connector does not detected on Raspberry PI3 B+

[Arnout Vandecappelle]

On 03/10/2018 08:02, Oscar Gomez Fuente wrote:
> Hi everyone,
> 
> I'm using the HW: Raspberry Pi 3B+ and buildroot-2018.02.5 (with
> LINUX_KERNEL_CUSTOM_REPO_VERSION="865ddc1393f558198e7e7ce70928ff2e49c4f7f6") and
> I have the following problem.
> 
> I've started the system with the ethernet unplugged. After the system has
> initiated completely, I log in using the uart console, and I plug the ethernet
> cable, but I'm not able to up eth0 without executing ifup eth0 command.

 You probably want ifplugd.

 Regards,
 Arnout

> 
> This is my /etc/network/interface:
> 
> auto lo
> iface lo inet loopback
> 
> auto eth0
> iface eth0 inet manual
> ? ? ? ? pre-up /etc/network/wait_iface $IFACE 20
> ? ? ? ? pre-up /sbin/ip link set $IFACE up
> ? ? ? ? pre-up /etc/network/nfs_check
> ? ? ? ? pre-up /sbin/udhcpc -R -b -p /var/run/udhcpc.${IFACE}.pid -i $IFACE
> ? ? ? ? post-down /bin/kill -9 $(cat /var/run/udhcpc.${IFACE}.pid)
> ? ? ? ? post-down /sbin/ip link set $IFACE down
> 
> I would like that the ifup eth0 was executed automatically when the plug
> ethernet cable is detected, but it seems to be when I plug/unplug the ethernet
> cable the kernel isn't detect it.
> 
> I've check the same buildroot-2018.02.5 version in the Raspberry pi 3B (instead
> of 3B+) and it works fine, so I think it's something related with the driver
> associated to the phy LAN7515
> The raspberry pi has the LAN9514.
> 
> Does anyone know if there is a problem with the driver associated with the
> LAN9515 (Raspberry Pi 3B+)?
> 
> Best regards.
> 
> Oscar Gomez Fuente
> TST Sistemas
> www.tst-sistemas.es <http://www.tst-sistemas.es>
> ? ?
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] Plug/unplug ethernet connector does not detected on Raspberry PI3 B+

[Oscar Gomez Fuente]

Hi Arnout,

>  You probably want ifplugd.

Yes, I was checking this one, but it didn't work properly (Sometimes works
and sometimes not).

I don't understand because If I am using the same defconfig file than in
the Raspberry Pi 3B (changing the config.txt file and changing the device
tree bcm2710-rpi-3-b-plus.dtb for bcm2710-rpi-3-b.dtb) everything works
fine without installing the ifplugd.

So, this is the reason I think there is something wrong with the driver
LAN9515 (Raspberry Pi 3B+).

It is not normal that with the same image, in the raspberry pi 3B, I can
see kernel messages of the plug/unplug events:

[   81.006823] smsc95xx 1-1.1:1.0 eth0: link down
[   83.455586] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa
0xC5E1
[   84.454778] smsc95xx 1-1.1:1.0 eth0: link down
[   87.080069] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa
0xC5E1

And with the Raspberry Pi 3B+, I cannot see this messages, so I think the
driver is not detecting these events and then the Raspberrypi is not able
to execute ifup/ifdown automatically.

Does anyone have any suggestion? I am stuck.

Oscar Gomez Fuente
TST Sistemas
www.tst-sistemas.es
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181004/f26c3ee3/attachment.html>

[Buildroot] Plug/unplug ethernet connector does not detected on Raspberry PI3 B+

[Peter Seiderer]

Hello Oscar,

On Thu, 4 Oct 2018 08:12:06 +0200, Oscar Gomez Fuente <oscargomezf@gmail.com> wrote:

> Hi Arnout,
> 
> >  You probably want ifplugd.
> 
> Yes, I was checking this one, but it didn't work properly (Sometimes works
> and sometimes not).
> 
> I don't understand because If I am using the same defconfig file than in
> the Raspberry Pi 3B (changing the config.txt file and changing the device
> tree bcm2710-rpi-3-b-plus.dtb for bcm2710-rpi-3-b.dtb) everything works
> fine without installing the ifplugd.
> 
> So, this is the reason I think there is something wrong with the driver
> LAN9515 (Raspberry Pi 3B+).
> 
> It is not normal that with the same image, in the raspberry pi 3B, I can
> see kernel messages of the plug/unplug events:
> 
> [   81.006823] smsc95xx 1-1.1:1.0 eth0: link down
> [   83.455586] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa
> 0xC5E1
> [   84.454778] smsc95xx 1-1.1:1.0 eth0: link down
> [   87.080069] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa
> 0xC5E1
> 
> And with the Raspberry Pi 3B+, I cannot see this messages, so I think the
> driver is not detecting these events and then the Raspberrypi is not able
> to execute ifup/ifdown automatically.
> 
> Does anyone have any suggestion? I am stuck.

Same suggestions as for thee BT Problem ([1]), try out original Raspbian, try out
with buildroot bumped rpi packages to latest versions ([2])....

Regards,
Peter

[1] http://lists.busybox.net/pipermail/buildroot/2018-October/233141.html
[2] http://lists.busybox.net/pipermail/buildroot/2018-October/233136.html

> 
> Oscar Gomez Fuente
> TST Sistemas
> www.tst-sistemas.es