Espressobin Debian testing

tom_i · July 22, 2018

14 hours ago, tkaiser said:

Boots even from SATA disks behind a crappy SATA PM.

Ok thx, fortunatelly my board works pretty well

Anyway, my network manager doesn't work as I switched from 4.4. kernel to the next 4.17.5.

It shows me just:

sudo journalctl -u systemd-networkd-wait-online.service - 
[sudo] password for nashome: 
-- Logs begin at Sat 2018-07-21 09:50:37 UTC, end at Sat 2018-07-21 09:57:12 UTC
Jul 21 09:50:40 espressobin systemd[1]: Starting Wait for Network to be Configur
Jul 21 09:52:40 espressobin systemd-networkd-wait-online[566]: Event loop failed
Jul 21 09:52:40 espressobin systemd[1]: systemd-networkd-wait-online.service: Ma
Jul 21 09:52:40 espressobin systemd[1]: systemd-networkd-wait-online.service: Fa
Jul 21 09:52:40 espressobin systemd[1]: Failed to start Wait for Network to be C

Because I'm connected it through "screen" so it looks that it break lines of that log :-/

ebin-dev · July 22, 2018

24 minutes ago, tom_i said:

my network manager doesn't work as I switched from 4.4. kernel to the next 4.17.5.

I am on Debian stretch- mainline/stable (4.17.5) (Armbian 5.44) - and it works just fine ...

Welcome to ARMBIAN 5.44 user-built Debian GNU/Linux 9 (stretch) 4.17.5-mvebu64 

# cat /proc/version
Linux version 4.17.5-mvebu64 (root@armbian) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #34 SMP PREEMPT Mon Jul 9 16:32:32 UTC 2018
# journalctl -u systemd-networkd-wait-online.service
-- No entries --
# systemd --v
systemd 232
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

@Igor Is there a problem with systemd-networkd in Ubuntu ?

Igor · July 22, 2018

Just now, ebin-dev said:

Is there a problem with systemd-networkd in Ubuntu ?

Ubuntu Bionic? It has plenty of (upstream) bugs and that is the reason we don't support it.

tom_i · July 22, 2018

Hi @ebin-dev I'm on Debian too:

Linux version 4.17.5-mvebu64 (root@nightly) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #87 SMP PREEMPT Sun Jul 8 19:16:19 UTC 2018

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux testing (buster)
Release:        testing
Codename:       buster

It shows me some messages about eth0:

[ 2868.894331] mvneta d0030000.ethernet eth0: could not attach PHY: -19
[ 2868.898077] mvneta d0030000.ethernet eth0: cannot probe MDIO bus

Is there any way, how to debug this?

I've tried to define eth0 with DHCP in "/etc/network/interfaces", or run "sudo dhclient eth0".

Both with no luck

ebin-dev · July 22, 2018

5 minutes ago, tom_i said:

Is there any way, how to debug this?

You should not change the content of /etc/network/interfaces if you use systemd-networkd. If it is of some help for you - see my configuration below:

#  cat /etc/network/interfaces

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

# cd /etc/systemd/network
# ls

10-br0.netdev  10-br0.network  10-eth0.network	10-lan0.network  10-lan1.network  10-wan.network

# cat *
[NetDev]
Name=br0
Kind=bridge
MACAddress=XX:XX:XX:XX:XX:XX
[Match]
Name=br0

[Network]
DHCP=ipv4
[Match]
Name=eth0

[Network]
DHCP=ipv4 
[Match]
Name=lan0

[Network]
Bridge=br0
[Match]
Name=lan1

[Network]
Bridge=br0
[Match]
Name=wan 

[Network]
Bridge=br0

Igor · July 22, 2018

8 minutes ago, tom_i said:

Description: Debian GNU/Linux testing (buster)

We only support Armbian builds here.

Smurfix · July 22, 2018

There is no physical interface named "eth0" you could talk on.

There are interfaces named "lan1", "lan0" and "wan". However, eth0 is what the CPU uses to multiplex these, so you need to set that to "up" too.

I do it with this simple systemd-networkd rule:

# cat /etc/systemd/network/49-switch.network
[Match]
Name=eth0

[Network]
DHCP=no

Then you can access the three real interfaces normally.

ebin-dev · July 22, 2018

35 minutes ago, Smurfix said:

I do it with this simple systemd-networkd rule

I have changed the configuration in 10-eth0.network to DHCP=no. It is working, but networkctl reports it failed.

# networkctl
IDX LINK             TYPE               OPERATIONAL SETUP     
  1 lo               loopback           carrier     unmanaged 
  2 bond0            ether              off         unmanaged 
  3 dummy0           ether              off         unmanaged 
  4 eth0             ether              carrier     configuring
  5 wan              ether              carrier     failed    
  6 lan0             ether              no-carrier  failed    
  7 lan1             ether              no-carrier  failed    
  8 br0              ether              routable    configured

8 links listed.

tom_i · July 22, 2018

53 minutes ago, ebin-dev said:

You should not change the content of /etc/network/interfaces if you use systemd-networkd. If it is of some help for you - see my configuration below:


#  cat /etc/network/interfaces

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

# cd /etc/systemd/network
# ls

10-br0.netdev  10-br0.network  10-eth0.network	10-lan0.network  10-lan1.network  10-wan.network

# cat *
[NetDev]
Name=br0
Kind=bridge
MACAddress=XX:XX:XX:XX:XX:XX
[Match]
Name=br0

[Network]
DHCP=ipv4
[Match]
Name=eth0

[Network]
DHCP=ipv4 
[Match]
Name=lan0

[Network]
Bridge=br0
[Match]
Name=lan1

[Network]
Bridge=br0
[Match]
Name=wan 

[Network]
Bridge=br0

Same for me man.

My ip addr show:

nashome@espressobin:/etc/systemd/network$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 532
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
5: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 532
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
6: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff

So no lan0, lan1 are up, so maybe that's the reason it doesn't work.

ebin-dev · July 22, 2018

8 minutes ago, tom_i said:

So no lan0, lan1 are up, so maybe that's the reason it doesn't work.

You are on Debian buster testing - that causes your problem.

Is there a reason why you are not using Debian stretch mainline/stable ? The interfaces are up and running:

#  ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
5: wan@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
6: lan0@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 state LOWERLAYERDOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
7: lan1@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 state LOWERLAYERDOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
8: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    inet 192.168.xx.yy/24 brd 192.168.xx.255 scope global dynamic br0
       valid_lft 861638sec preferred_lft 861638sec
    inet6 2a02:810d:1500:7c44:f2ad:4eff:xxxx:yyyy/64 scope global mngtmpaddr noprefixroute dynamic 
       valid_lft 5214sec preferred_lft 2514sec
    inet6 fe80::f2ad:4eff:xxxx:yyyy/64 scope link 
       valid_lft forever preferred_lft forever

y52 · July 22, 2018

54 minutes ago, ebin-dev said:

I have changed the configuration in 10-eth0.network to DHCP=no.

It should be

[Network]
DHCP=ipv4

tom_i · July 22, 2018

43 minutes ago, ebin-dev said:

You are on Debian buster testing - that causes your problem.

Is there a reason why you are not using Debian stretch mainline/stable ? The interfaces are up and running:


#  ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
5: wan@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
6: lan0@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 state LOWERLAYERDOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
7: lan1@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 state LOWERLAYERDOWN group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
8: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    inet 192.168.xx.yy/24 brd 192.168.xx.255 scope global dynamic br0
       valid_lft 861638sec preferred_lft 861638sec
    inet6 2a02:810d:1500:7c44:f2ad:4eff:xxxx:yyyy/64 scope global mngtmpaddr noprefixroute dynamic 
       valid_lft 5214sec preferred_lft 2514sec
    inet6 fe80::f2ad:4eff:xxxx:yyyy/64 scope link 
       valid_lft forever preferred_lft forever

I've seen that 4.17.X kernel has more features for EspressoBin so I wanted to switch to the NEXT. Ddebian Stretch has 4.4. right?

Igor · July 22, 2018

Debian testing is not supported. We have enough problems without that. You are welcome to discuss this further in the general area.

tom_i · July 22, 2018

15 minutes ago, Igor said:

Debian testing is not supported. We have enough problems without that. You are welcome to discuss this further in the general area.

Aha.. ok. Thx

Sign In

Espressobin Debian testing

Recommended Posts

tom_i

ebin-dev

Igor

tom_i

ebin-dev

Igor

Smurfix

ebin-dev

tom_i

ebin-dev

y52

tom_i

Igor

tom_i

Forums

My Activity Streams

Download

Store

Important Information