qemu - no network after systemd update on fresh install

This forum is for supported devices using an ARMv7 Freescale SoC.

qemu - no network after systemd update on fresh install

Postby krisbee » Mon Mar 17, 2014 12:22 pm

I'm an arch/systemd novice. After building a Wandbaord img as per the installion guide I've booted it in qemu with:

$this->bbcode_second_pass_code('', 'qemu-system-arm -m 1024M -M vexpress-a9 -cpu cortex-a9 -kernel zImage3.13 -append "root=/dev/mmcblk0p1 rw rootfstype=ext4 console=ttyAMA0" -drive if=sd,cache=writeback,file=archwand.img -net nic -net tap,ifname=tap0,script=no ')

Using the default network set-up on the image (netctl-ifplugd@eth0.service) I went through the preliminary config of keyboard/locale/hostname/user addition etc. Installed htop without a system update , rebooted a couple of time and all was OK. Then after a pacman -Syu which brings in systemd 210-3 with some message about udev and network device which were not re-named, there is no network connection after a re-boot.
$this->bbcode_second_pass_code('', '
systemctl status netctl-ifplugd@eth0.service
netctl-ifplugd@eth0.service - Automatic wired network connection using netctl profiles
Loaded: loaded (/usr/lib/systemd/system/netctl-ifplugd@.service; enabled)
Active: inactive (dead)
Docs: man:netctl.special(7)

Mar 17 11:37:15 awand systemd[1]: Dependency failed for Automatic wired network connection using netctl profiles.')

The emualted nic is present and recognised:

$this->bbcode_second_pass_code('', 'ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
3: tunl0: <NOARP> mtu 0 qdisc noop state DOWN mode DEFAULT group default
link/ipip 0.0.0.0 brd 0.0.0.0')

I made no changes to the default network settings in the wandboard image. Nothing to confilct that I know of and there are no rules in /etc/udev/rules.d.

A manual "dhcpcd eth0" brings the eth0 interface up

Any ideas why the systemd update should render it non-working?
Last edited by kmihelich on Mon Mar 17, 2014 4:48 pm, edited 1 time in total.
Reason: Changed topic to qemu; qemu != wandboard.
krisbee
 
Posts: 3
Joined: Mon Mar 17, 2014 11:57 am

Re: Wandboard - no network after systemd update on fresh ins

Postby krisbee » Mon Mar 17, 2014 12:43 pm

I should have added that "journalctl -b" shows a time out that was not present before updating systemd.

$this->bbcode_second_pass_code('', ' Mar 17 11:37:15 awand systemd[1]: Job sys-subsystem-net-devices-eth0.device/start timed out.
Mar 17 11:37:15 awand systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eth0.device.
Mar 17 11:37:15 awand systemd[1]: Dependency failed for Automatic wired network connection using netctl profiles.
Mar 17 11:37:15 awand systemd[1]: Job dev-ttyAMA0.device/start timed out.
Mar 17 11:37:15 awand systemd[1]: Timed out waiting for device dev-ttyAMA0.device.
Mar 17 11:37:15 awand systemd[1]: Dependency failed for Serial Getty on ttyAMA0.
Mar 17 11:37:15 awand systemd[1]: Starting Login Prompts.
Mar 17 11:37:15 awand systemd[1]: Reached target Login Prompts.
Mar 17 11:37:15 awand systemd[1]: Starting Multi-User System.
Mar 17 11:37:15 awand systemd[1]: Reached target Multi-User System.
Mar 17 11:37:15 awand systemd[1]: Reached target Graphical Interface.
Mar 17 11:50:53 awand systemd[1]: Starting Cleanup of Temporary Directories...
Mar 17 11:50:53 awand systemd[1]: Started Cleanup of Temporary Directories.
Mar 17 12:10:22 awand dhcpcd[932]: version 6.3.1 starting
Mar 17 12:10:22 awand kernel: smsc911x smsc911x eth0: SMSC911x/921x identified at 0xc0a40000, IRQ: 47')

Do I simply need a udev rule for the emulated smsc911x ?
krisbee
 
Posts: 3
Joined: Mon Mar 17, 2014 11:57 am

Re: Wandboard - no network after systemd update on fresh ins

Postby WarheadsSE » Mon Mar 17, 2014 12:58 pm

qemu is not supported. We're not really sure.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: qemu - no network after systemd update on fresh install

Postby krisbee » Mon Mar 17, 2014 5:21 pm

OK, I have a (naive) fix. After login the interface could be brought be these commands:

$this->bbcode_second_pass_code('', '
systemctl enable netctl-ifplugd@eth0.service
systemctl start netctl-ifplugd@eth0.service
')

So I followed the main ARCH KIWI on - How can I make a script start during the boot process?

Systemd entry:

$this->bbcode_second_pass_code('', '[root@awand system]# cat restarteth0.service
[Unit]
Description=Restart eth0 in QEMU

[Service]
ExecStart=/usr/bin/restarteth0

[Install]
WantedBy=default.target ')

V.simple script ( my level):

$this->bbcode_second_pass_code('', 'cat /usr/bin/restarteth0
#!/bin/sh
systemctl enable netctl-ifplugd@eth0.service
systemctl start netctl-ifplugd@eth0.service')

Now ethO is up and connected by the time you login.

There's a job stop message at shutdown re: Automatic wired network connection using netctl profiles (1min 30s)

What cause this delay?

At least I continue to use QEMU now.
krisbee
 
Posts: 3
Joined: Mon Mar 17, 2014 11:57 am


Return to Freescale

Who is online

Users browsing this forum: No registered users and 9 guests