NSA 325 v2 network problem after pacman -Syu

[Jutzi]

I just installed ARCH Linux to a brand new Zyxel NSA325-V2. Everything went fine but after upgrade (pacman -Syu) network is lost. Or actually network is connected again after 2-10 reboots. No logic how many reboots are needed. After re-installing the rootfs (ArchLinuxARM-kirkwood-latest.tar.gz) to the second partition, everything works nicely again and problem is back after upgrade.

Problem could be related to this: viewtopic.php?f=27&t=3851&start=10

Last lines from the log of a the last boot with failing network (journalctl -b -1):

Feb 21 17:44:40 nsa325-v2 systemd-networkd[131]: eth0 : gained carrier
Feb 21 17:44:40 nsa325-v2 kernel: mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
Feb 21 17:44:40 nsa325-v2 systemd-networkd[131]: eth0 : could not start IPv6 router discovery
Feb 21 17:45:31 nsa325-v2 kernel: mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
Feb 21 17:45:31 nsa325-v2 systemd-networkd[131]: eth0 : lost carrier
Feb 21 17:45:41 nsa325-v2 systemd-networkd[131]: eth0 : gained carrier
Feb 21 17:45:41 nsa325-v2 kernel: mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
Feb 21 17:45:41 nsa325-v2 systemd-networkd[131]: eth0 : could not start IPv6 router discovery

I do not yet have the serial connection so my debugging possibilities are limited.

Any help would be appreciated.

[Socaltom]

Did you update your fstab to include the following?
$this->bbcode_second_pass_code('', '/dev/sda1 /boot ext2 noatime, 0 0
')

If not, then what happened is that the kernel in /boot does not match the kernel in /dev/sda1 which is used to boot the system.
Tom

[Jutzi]

I did now

Seems to be pretty standard Linux setting but I think this should be mentioned in the installation instructions. In my system fstab was empty. Any other settings needed in the fstab?

I have to wait a few hours to check after my working day.

[Socaltom]

I like to put the mount points for my standard directories. ( i.e. /homes /Video). Keep in mind if you have a mount point in the fstab, and it can't find the drive your system won't boot to the network.
Tom

[Jutzi]

Thanks a lot.

Some problems still. After adding the line to fstab the system boots mostly ok. Feels a little unreliable, though.

I removed the eth0 script and after that the system did no boot at all. This is what I have in the eth0 script:

Description='A basic dhcp ethernet connection'
TimeoutDAD=60
Interface=eth0
Connection=ethernet
IP=dhcp

I enabled that again using (after rebuilding the rootfs and upgrading):

netctl enable eth0

And after that system boots in most cases. I don't understand why this is needed after upgrade. Original rootfs does not need this.

Another thing: reboot does not work at all. Reboot causes the system to shut down but leaves the power on and nothing happens. Normal boot with the power button goes like this:
- blue power light on
- after a second blue power light turns off for a second
- after around 30 seconds of no action, the green light turns on
- after a few seconds hd lights start blinking and the system gets ready, blue and green lights remain lit

Is there a setting available enabling reboot? Or power off using the power button?

[Jutzi]

More problems.

Mount.cifs gives error saying cifs is not supported. Googling the issue leads to a thread indicating kernel version differences which I should not have after the fstab addition.

But:

[root@alarm jussi]# uname -r
3.18.5-1-ARCH
[root@alarm jussi]# ls /usr/lib/modules
3.19.0-1-ARCH extramodules-3.19--kirkwood

What is wrong with this ? And why is cifs not working? I have installed samba.

[WarheadsSE]

mount /boot , re-install linux-kirkwood package.

Add line item to your fstab

[Socaltom]

$this->bbcode_second_pass_quote('Jutzi', 'T')hanks a lot.

Some problems still. After adding the line to fstab the system boots mostly ok. Feels a little unreliable, though.

I removed the eth0 script and after that the system did no boot at all. This is what I have in the eth0 script:

Description='A basic dhcp ethernet connection'
TimeoutDAD=60
Interface=eth0
Connection=ethernet
IP=dhcp

I enabled that again using (after rebuilding the rootfs and upgrading):

netctl enable eth0

And after that system boots in most cases. I don't understand why this is needed after upgrade. Original rootfs does not need this.

Another thing: reboot does not work at all. Reboot causes the system to shut down but leaves the power on and nothing happens. Normal boot with the power button goes like this:
- blue power light on
- after a second blue power light turns off for a second
- after around 30 seconds of no action, the green light turns on
- after a few seconds hd lights start blinking and the system gets ready, blue and green lights remain lit

Is there a setting available enabling reboot? Or power off using the power button?

[Jutzi]

$this->bbcode_second_pass_quote('WarheadsSE', 'm')ount /boot , re-install linux-kirkwood package.

Add line item to your fstab

[moonman]

What is the output of 'mount' and 'fdisk -l' ? did you reboot after you did update? The kernel running obviously doesn't match what you have installed.
2 reasons:
1. Partition containing the kernel is not mounted under /boot so when you do pacman -Syu kernel image doesn't go to where it can be picked up by bootloader
2. You didn't reboot for new kernel to be loaded.

Now this should be simple for you to figure out...