AndiH

Hello,
 
I did again some testing with the actual Nightly builds on an Odroid HC1, and detected an issue - the DNS name resolution doesn't work properly.

Reason is that the configuration file "/etc/NetworkManager/NetworkManager.conf" now contains a line "dns=None".  After just deleting this line from NetworkManager.conf, it works fine - and NetworkManager is updating "/etc/resolv.conf" accordingly.

(Note: with "dns=none", the DHCP client ("dhclient" resp. "dhclient-script" would have to take care of the "resolv.conf" update - but that script gets never called, as "dhclient" is started with the -sf option, and will instead invoke the NetworkManage "nm-dhcp-helper" component).

I found the issue trying the following images:
5.46.180602_Odroidxu4_Debian_stretch_next_4.9.103
5.46.180602_Odroidxu4_Debian_stretch_dev_4.14.47
5.46.180530_Odroidxu4_Debian_stretch_dev_4.14.44
 
It was fine (i.e. "NetworkManager.conf" does not contain the "dns=none" line) in:
5.44.180506_Odroidxu4_Debian_stretch_next_4.14.39
5.45_Odroidxu4_Debian_stretch_next_4.9.99 
 
So must happened somewhere in between ...
 
Andi.
 

Hello,
 
I did some testing with the Nightly Build Image for the Odroid HC1 / XU4, and made 2 observations:
 
First a nice one:  Seems the idle power consumption with the Nightly Build is even lower than with the current Stable Version (measured with an "ELV Energy Master", and very same Hardware for HC1 / SD Card / HDD in standby):
4.0 - 4.1 Watts with 5.43.180423 nightly, Debian stretch, kernel 4.14.35-odroidxu4 4.3 Watts with 5.41 stable, Debian jessie, 4.9.86-odroidxu4 During the boot process however there seems to be some 12 seconds delay on the Odroid HC1, which does not occur on a XU4.  Seems the Kernel is running into some timeout?  (Perhaps because the HC1 is headless and has no HDMI?)
 
Here the "dmesg" output on the HC1 (with ARMBIAN 5.43.180423 nightly):
[ 2.269968] exynos-gsc 13e00000.video-scaler: Linked as a consumer to 13e80000.sysmmu [ 2.270023] iommu: Adding device 13e00000.video-scaler to group 6 [ 2.271205] exynos-gsc 13e10000.video-scaler: Linked as a consumer to 13e90000.sysmmu [ 2.271263] iommu: Adding device 13e10000.video-scaler to group 7 [ 14.599003] device-mapper: uevent: version 1.0.3 [ 14.599314] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com And here the same on the XU4 (used exactly same SD Card): 
[ 2.265929] exynos-gsc 13e00000.video-scaler: Linked as a consumer to 13e80000.sysmmu [ 2.265984] iommu: Adding device 13e00000.video-scaler to group 6 [ 2.267160] exynos-gsc 13e10000.video-scaler: Linked as a consumer to 13e90000.sysmmu [ 2.267219] iommu: Adding device 13e10000.video-scaler to group 7 [ 2.291153] device-mapper: uevent: version 1.0.3 [ 2.291472] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com Up to this point, the messages in "dmesg" match line-by-line on HC1 and XU4 (of course, the timestamps vary slightly).
 
The Odroid HC1 with the current stable build image (5.41, kernel 4.9.86) doesn't not show such a delay in the boot process.
 
Not a big deal, but I thought to report it here ...

Hello,
 
I did some testing with the Nightly Build Image for the Odroid HC1 / XU4, and made 2 observations:
 
First a nice one:  Seems the idle power consumption with the Nightly Build is even lower than with the current Stable Version (measured with an "ELV Energy Master", and very same Hardware for HC1 / SD Card / HDD in standby):
4.0 - 4.1 Watts with 5.43.180423 nightly, Debian stretch, kernel 4.14.35-odroidxu4 4.3 Watts with 5.41 stable, Debian jessie, 4.9.86-odroidxu4 During the boot process however there seems to be some 12 seconds delay on the Odroid HC1, which does not occur on a XU4.  Seems the Kernel is running into some timeout?  (Perhaps because the HC1 is headless and has no HDMI?)
 
Here the "dmesg" output on the HC1 (with ARMBIAN 5.43.180423 nightly):
[ 2.269968] exynos-gsc 13e00000.video-scaler: Linked as a consumer to 13e80000.sysmmu [ 2.270023] iommu: Adding device 13e00000.video-scaler to group 6 [ 2.271205] exynos-gsc 13e10000.video-scaler: Linked as a consumer to 13e90000.sysmmu [ 2.271263] iommu: Adding device 13e10000.video-scaler to group 7 [ 14.599003] device-mapper: uevent: version 1.0.3 [ 14.599314] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com And here the same on the XU4 (used exactly same SD Card): 
[ 2.265929] exynos-gsc 13e00000.video-scaler: Linked as a consumer to 13e80000.sysmmu [ 2.265984] iommu: Adding device 13e00000.video-scaler to group 6 [ 2.267160] exynos-gsc 13e10000.video-scaler: Linked as a consumer to 13e90000.sysmmu [ 2.267219] iommu: Adding device 13e10000.video-scaler to group 7 [ 2.291153] device-mapper: uevent: version 1.0.3 [ 2.291472] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com Up to this point, the messages in "dmesg" match line-by-line on HC1 and XU4 (of course, the timestamps vary slightly).
 
The Odroid HC1 with the current stable build image (5.41, kernel 4.9.86) doesn't not show such a delay in the boot process.
 
Not a big deal, but I thought to report it here ...