Installing Arch on TonidoPlug2. DHCP service not starting on

[unsignedzero]

I've been pucked to this board from (https://bbs.archlinux.org/viewtopic.php ... 5#p1463285)

I've followed (http://archlinuxarm.org/platforms/armv5/tonidoplug-2) to install Arch on my Tonido Plug 2.

There was a few changes, like bsdtar not working (http://archlinuxarm.org/forum/viewtopic.php?f=53&t=7758%29) and a warning message from install_envtools.sh specifically the last line mount -o remount,ro / not working right. Everything else went smoothly until I rebooted. From my string output in system.journal in /var/log/journey/(md5hash)/system.journal I see these as my last lines

$this->bbcode_second_pass_code('', '
.@8"
MESSAGE=haveged: cpu: (); data: 16K (D); inst: 16K (D); idx: 8/40; sz: 15248/74244
_SOURCE_REALTIME_TIMESTAMP=1412541749390084
.@8"
MESSAGE=haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 7.99876
_SOURCE_REALTIME_TIMESTAMP=1412541749390277
.@8"
MESSAGE=haveged: fills: 0, generated: 0A
_SOURCE_REALTIME_TIMESTAMP=1412541749390355
.@8"
INTERFACE=eth0
MESSAGE=eth0 : gained carrier
_SOURCE_REALTIME_TIMESTAMP=1412541750601045
77H;#=
PRIORITY=4
CODE_FILE=src/network/networkd-dhcp4.c
CODE_LINE=562
CODE_FUNCTION=dhcp4_handler
MESSAGE=eth0 : DHCP error: client failed: Invalid argument
_SOURCE_REALTIME_TIMESTAMP=1412541750616999
9H9#
77H;#
CODE_LINE=845
CODE_FUNCTION=link_acquire_conf
MESSAGE=eth0 : could not acquire DHCPv4 lease
_SOURCE_REALTIME_TIMESTAMP=1412541750617156
77H;#
CODE_LINE=262
CODE_FUNCTION=link_enter_failed
MESSAGE=eth0 : failed
_SOURCE_REALTIME_TIMESTAMP=1412541750617199
77H;#
YEl8
sxXd
SYSLOG_FACILITY=9
CODE_FILE=src/timesync/timesyncd-manager.c
CODE_LINE=1038
CODE_FUNCTION=manager_network_event_handler
SYSLOG_IDENTIFIER=systemd-timesyncd
MESSAGE=Network configuration changed, trying to establish connection.
_PID=78
_UID=192
_GID=192
_COMM=systemd-timesyn
no@x
_EXE=/usr/lib/systemd/systemd-timesyncd
_CMDLINE=/usr/lib/systemd/systemd-timesyncd
_CAP_EFFECTIVE=2000000
_SYSTEMD_CGROUP=/system.slice/systemd-timesyncd.service
_SYSTEMD_UNIT=systemd-timesyncd.service
_SOURCE_REALTIME_TIMESTAMP=1412541752048229
sxXd
jUH0
no@x(
')

Seems like DHCP is somehow not starting correctly. I haven't used netctl before but it looks like the /etc/netctl has empty directories, aside from the examples directory.

$this->bbcode_second_pass_code('', '
ls -R
.:
examples hooks interfaces

./examples:
bonding macvlan-static vlan-dhcp wireless-wpa-config
bridge mobile_ppp vlan-static wireless-wpa-configsection
ethernet-custom openvswitch wireless-open wireless-wpa-static
ethernet-dhcp pppoe wireless-wep
ethernet-static tunnel-he-ipv6 wireless-wep-string-key
macvlan-dhcp tuntap wireless-wpa

./hooks:

./interfaces:
')

I've tried adding x2ddhcp.service (contents below) into '/etc/systemd/system/multi-user.target.wants/netctl@ethernet\x2ddhcp.service' but this doesn't seem to help at all.

$this->bbcode_second_pass_code('', '
.include /usr/lib/systemd/system/netctl@.service

[Unit]
Description=A basic dhcp ethernet connection
BindsTo=sys-subsystem-net-devices-eth0.device
After=sys-subsystem-net-devices-eth0.device
')

Does anyone have any advice on this problem? Before you answer, remember that this is headless system so I can't directly connect into it live. I have a USB 2.0, Gigabit ethernet and a serial port but I don't have this cable (https://www.adafruit.com/product/70) as well as a hard drive, which Arch is booting from. From an outside point of view, I see the green network light on and the amber light flickering on and off so something is happening. However, I don't see anything on my desktop when running wireshark, at least anything with the Plug's mac address.

I can't ssh or even ping the device. Given that this worked under Debian before this installation, the mac address is correctly converted into the same static IP address so I don't think that is a problem. Since uboot is modified, the original debian underneath the device (firmware) won't run until I get the cable so I have a brick if this fails.

[Socaltom]

What is the date on the logs you are looking at?
I've seen cases where the logs were left over from the tar, and were not an accurate representation of the actual system. I

Did you make any changes to the system prior to rebooting? Like changes to fstab?
Tom

[unsignedzero]

You're right the logs are from when it was imaged. I try running again and seeing if the dates change.

I have not made any other changes, that differed from the instructions listed. The only thing I see different is that I have set my system to have 4 partitions instead of 1 but the first one IS the main arch parition with 128GB. I have a 4GB swap, 256GB (will be home) and the extera as another partition. Would this be my problem?

UPDATE:Logs are not updating at least the system journal isn't. Looking under var/logs I don't see any update except with wtmp but that's given me garbage, see below.

$this->bbcode_second_pass_code('', '
reboot
3.1.10-34-ARCH
ttyS0
tyS0
`1TO
ttyS0
tyS0LOGIN
`1TO
tty1
tty1
`1TJ<
tty1
tty1LOGIN
`1TJ<
reboot
3.1.10-34-ARCH
sj1T
tty1
tty1
j1Tq
tty1
tty1LOGIN
j1Tq
ttyS0
tyS0
j1Tb
ttyS0
tyS0LOGIN
j1Tb
reboot
3.1.10-34-ARCH
tty1
tty1
z1T2
tty1
tty1LOGIN
z1T2
ttyS0
tyS0
z1TA
ttyS0
tyS0LOGIN
z1TA
reboot
3.1.10-34-ARCH
tty1
tty1
tty1
tty1LOGIN
ttyS0
tyS0
ttyS0
tyS0LOGIN
reboot
3.1.10-34-ARCH
tty1
tty1
tty1
tty1LOGIN
ttyS0
tyS0
ttyS0
tyS0LOGIN
reboot
3.1.10-34-ARCH
ttyS0
tyS0
3T~Q
ttyS0
tyS0LOGIN
3T~Q
tty1
tty1
3TC&
tty1
tty1LOGIN
3TC&
')

[WarheadsSE]

Well, first off, it would be in journalctl

[Socaltom]

$this->bbcode_second_pass_quote('', '&')quot;unsignedzero"]
I have not made any other changes, that differed from the instructions listed. The only thing I see different is that I have set my system to have 4 partitions instead of 1 but the first one IS the main arch parition with 128GB. I have a 4GB swap, 256GB (will be home) and the extera as another partition. Would this be my problem?
.

I don't understand why reply is disabled for old posts but I'm guessing this is due to people necroing old posts.

$this->bbcode_second_pass_quote('', '
')Well, first off, it would be in journalctl

[WarheadsSE]

journalctl can be used on another system, to read the offline copy of the journal from a different system.

I would also point out -
https://wiki.archlinux.org/index.php/systemd-networkd

[mpadilla2]

Archlinux has switched over to using systemd-networkd from netctl. Remove whatever you had added to netctl. I'm guessing that netctl is not enabled to start on boot since this is a new installation. If you have the means to move the drive to another working archlinux arm installation you could chroot into the nonworking installation.

Then fix your network setup:
I'm assuming that your device will be eth0 and that you want an ip assigned dynamically by dhcp. Sometimes the ethernet device is named enp2s0 or something similar. So try one of the following configurations:
$this->bbcode_second_pass_code('', 'nano /etc/systemd/network/20-dhcp.network')

Then paste in:
$this->bbcode_second_pass_code('', '[Match]
Name=eth0

[Network]
DHCP=both')

OR
$this->bbcode_second_pass_code('', 'nano /etc/systemd/network/20-dhcp.network')

Then paste in:
$this->bbcode_second_pass_code('', '[Match]
Name=en*

[Network]
DHCP=both')

If you want a static ip address then paste in something like this but edit for your particular setup:
$this->bbcode_second_pass_code('', '[Match]
Name=eth0

[Network]
Address=192.168.1.8/24
Gateway=192.168.1.1
DNS=8.8.8.8
DNS=8.8.4.4')

You will then need to ensure netcl is disabled. To find out what is enabled that is netctl related, run this:
$this->bbcode_second_pass_code('', 'systemctl list-unit-files')

Once you identify all netctl related stuff. Go through and disable all netctl related stuff. You may have more to disable than just the below:
$this->bbcode_second_pass_code('', 'systemctl disable netctl@eth0.service')

You will then need systemd-networkd enabled:
$this->bbcode_second_pass_code('', 'systemctl enable systemd-networkd')

If you cannot chroot into the system you can still fix it, you will just have to manually copy and/or remove the necessary *.service files. Then fix it after boot.

If you cannot chroot but are able to mount the drive in another system, do the following. please still add the 20-dhcp.network as noted in the above steps.

Remove netctl from starting by removing netctl related from:
$this->bbcode_second_pass_code('', '/etc/systemd/system/multi-user.target.wants')

You can then temporarily copy systemd-networkd.service:
$this->bbcode_second_pass_code('', 'cp /usr/lib/systemd/system/systemd-networkd.service /etc/systemd/system/multi-user.target.wants/')

Boot your system. Then remove your systemd-networkd.service file:
$this->bbcode_second_pass_code('', 'rm /etc/systemd/system/multi-user.target.wants/systemd-networkd.service')

Now properly enable it:
$this->bbcode_second_pass_code('', 'systemctl enable systemd-networkd')