Am 17.07.2015 um 08:29 schrieb Andreas Färber:

Hello,

After upgrading 13.2 from kernel-lpae-3.16.7-7 to -11/-21 (why is it installing two new kernels btw?) I no longer have network.

Diagnosing this is difficult because, as reported previously, the kernel does not provide any serial output to ttyS0. The LED lights up, which is done by my boot.local script, so it is coming up to some degree, just not far enough to login via ssh, and it's not reachable by ping either.

I doubt this is just the dtb getting out of sync again?

Originally it was a U-Boot 2014.10, but same with 2015.07 (and still working with a downgraded kernel/initrd).

Upgrading to Factory (kernel-lpae-4.0.5-3), ssh login works again, but still no serial output. There are systemd messages and a graphical login on HDMI now, but no kernel messages either. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op woensdag 5 augustus 2015 21:35:35 schreef Andreas Färber:

Am 17.07.2015 um 11:50 schrieb Andreas Färber:

...

Upgrading to Factory (kernel-lpae-4.0.5-3), ssh login works again, but still no serial output. There are systemd messages and a graphical login on HDMI now, but no kernel messages either.

You may find /dev/tty10 or /dev/xconsole in /etc/rsyslog.conf Changing /dev/tty10 in /dev/tty1 may get your kernel messages logged on your screen. It did for me on a Raspberry Pi 2B. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org