BeagleBone Black loses network connection on restart

[sjp]

I have a BeagleBone Black with a Zyxel NWD2205 that I'm trying to set up and while the initial install is smooth, it appears to lose the network connection on restart in several cases:

configuring avahi-daemon
changing ssh port
configuring wireless

In the case of the latter, from a fresh install, I run

pacman -Syu
pacman -S dialog wpa_supplicant
wifi-menu

after following the steps in wifi-menu, I get a working connection and at this point I can ssh using either the wireless or the wired IP. Happy as Larry, I restart but alas, it is no longer working and "sudo nmap .sn [my ip]/24" from my laptop no longer finds either the wired or wirless MAC address.

Unfortunately, I don't have a micro-HDMI cable, so ssh is my only way in. Since I'm trying to get this to work on the flash drive, I can also boot to an SD-card and have from there tried messing around with chroot and systemd-nspawn. Personally, I got none the wiser but using either of them to find out more could also be an option. I'm happy for any help.

[moonman]

Might be related to the new systemd + older kernel problem. Install "linux-am33x" and then do full update and see if it resolves the problem.

[sjp]

On the contrary, this was enough to cause the problem

booting from SD-card:

wget http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz
mkfs.ext4 /dev/mmcblk1p2
mount /dev/mmcblk1p2 rootmnt
bsdtar -xpf ArchLinuxARM-am33x-latest.tar.gz -C root
umount rootmnt
poweroff

removing SD-card and booting up again:

pacman -Syu
shutdown -r now

then it's gone...

pacman updates the following:

Packages (39) ca-certificates-20150402-1 ca-certificates-utils-20150402-1 cracklib-2.9.4-1
curl-7.42.0-1 dhcpcd-6.8.2-1 dnssec-anchors-20150403-1 gawk-4.1.2-1
gcc-libs-4.9.2-4 glib2-2.44.0-1 glibc-2.21-3 gnupg-2.1.3-3 gnutls-3.4.1-1
gpgme-1.5.4-1 groff-1.22.3-3 libassuan-2.2.0-1 libedit-20150325_3.1-1
libgpg-error-1.19-1 libksba-1.3.3-1 libssh2-1.5.0-1 libsystemd-219-6
libtasn1-4.5-1 libtirpc-0.3.0-1 linux-firmware-20150410.ec89525-1 lz4-128-1
man-pages-4.00-1 nano-2.4.1-1 netctl-1.10-2 nettle-3.1.1-1 npth-1.2-1
pacman-mirrorlist-20150507-1 pciutils-3.3.1-1 pcre-8.37-1 pinentry-0.9.1-1
readline-6.3.008-1 s-nail-14.8.0-1 systemd-219-6 systemd-sysvcompat-219-6
tzdata-2015d-1 vi-1:070224-1

[moonman]

Yes, and my suggestion was

$this->bbcode_second_pass_code('', 'pacman -Sy linux-am33x')

then

$this->bbcode_second_pass_code('', 'pacman -Syu')

then reboot

ArchLinuxARM-am33x-latest.tar.gz comes with linux-am33x-legacy kernel package

linux-am33x-legacy = kernel v3.8.13
linux-am33x = kernel v4.0.1

[sjp]

Ah, I misunderstood your suggestion due to my lack of knowledge. This did work, thank you very much.

[sjp]

So while that fixed the original problem, When trying to get PWM working I found out that there's a good reason for using am33x-legacy. Is there another way around this? Or perhaps some reasonable way to get the pin muxing stuff done with the new kernel that I haven't been able to find? Or should I consider going back to the Ubuntu/Debian world for the sake of my own sanity?