WE NEED !YOUR! HELP

Tido · June 17, 2018

Hi,

Thank you for your interest, you won't be disappointed. You have probably read that the developer want to do some changes - and some of this changes are now ready to get tested in the BETA's of armbian.

Do not test with your 'production' SDcard unless you have done a backup ;-)

Once done that, please go to 'armbian-config' System switch to BETA (Nightly), do an update/upgrade, reboot, check if your system still performs as before.

If it does work like before - please let us know and post your 'armbianmonitor -u' link
If it doesn't work, please try a reboot, check if the problem is reproduceable and if so explain the steps to reproduce it and post your 'armbianmonitor -u' link

If you like to know what has changed or is changing:

Kernel upgrade for Allwinner boards. NEXT is 4.17.y and it's getting daily updates. (LIB_TAG="sunxi-4.18" in our build system)

https://forum.armbian.com/topic/7398-bsp-scripts-rfc/

https://forum.armbian.com/topic/5565-zram-vs-swap/

https://forum.armbian.com/topic/6444-varlog-file-fills-up-to-100-using-pihole/

This is not all, see details on GitHub look at the shell code - which makes this happen - more eyes less errors :thumbup:

And if you want to try a fresh install, look for the nightly created 17. June https://dl.armbian.com/

Thank you in advance for your support

Tido · June 17, 2018

Hi, I just ran some tests with fresh install on my tinker board

Spoiler


Welcome to ARMBIAN 5.46.180616 nightly Ubuntu 18.04 LTS 4.14.50-rockchip   
System load:   1.26 1.26 0.67  	Up time:       15 min		
Memory usage:  9 % of 2005MB 	IP:            192.168.9.5
CPU temp:      50°C           	
Usage of /:    4% of 30G    	


root@tinkerboard:~# zramctl 
NAME       ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram4 lz4         250.7M   4K   63B    4K       4 [SWAP]
/dev/zram3 lz4         250.7M   4K   63B    4K       4 [SWAP]
/dev/zram2 lz4         250.7M   4K   63B    4K       4 [SWAP]
/dev/zram1 lz4         250.7M   4K   63B    4K       4 [SWAP]
/dev/zram0 lz4            40M   0B    0B    0B       4 


root@tinkerboard:~# swapon --show
NAME       TYPE        SIZE USED PRIO
/dev/zram1 partition 250.7M   0B    5
/dev/zram2 partition 250.7M   0B    5
/dev/zram3 partition 250.7M   0B    5
/dev/zram4 partition 250.7M   0B    5

root@tinkerboard:~# sysctl vm.swappiness
vm.swappiness = 60

root@tinkerboard:~# LANG=en free -h
              total        used        free      shared  buff/cache   available
Mem:           2.0G        173M        1.1G         16M        676M        1.7G
Swap:          1.0G          0B        1.0G

The keyboard-setting seem to stick now and I have installed via armbian-config Transmission and the minimal desktop. After that the Memory footprint in htop went from 70MB to 186MB. File Manager Thunar starts in this release much quicker than with Xenial. The display resolution still perfect on 4.14.

root@tinkerboard:~# armbianmonitor -u
System diagnosis information will now be uploaded to http://ix.io/1dIr

Well done

mpmc · June 17, 2018

~~Not sure what I'm looking for, I've not even noticed any difference. I'm sure there is, but I can't see it. And this is a good thing!~~

~~I originally did it on my Orange Pi Zero & didn't notice ANYTHING different so did it on my PC and couldn't notice it there either!~~

Update: OK I've found the change to zram on the PC but not the Zero, even after an update!

Orange Pi Zero -> http://ix.io/1dIO [Updated] http://ix.io/1dJ3

Orange Pi PC -> http://ix.io/1dIA

~~/me has no idea what to look for.~~

I hope this helps though!

rusatch · June 18, 2018

Works OK.

http://ix.io/1dL9

Igor · June 18, 2018

8 hours ago, mpmc said:

Update: OK I've found the change to zram on the PC but not the Zero, even after an update!

This bug will hopefully be fixed with today update ... which I am still fixing for other problems. It would be best to try with not updated image yet or some older image updated to nightly.

Thank you for your help!

Edit: Please pay attention to log rotation service. If that works properly. Starting with today update, current is broken.

Tido · June 18, 2018

Shall I stress more the update path to test?

2 hours ago, Igor said:

Starting with today update

Shall I add in the first post to do: sudo apt update && upgrade for fresh-install to get your latest bugfix?

Tido · June 18, 2018

I just ran an update on : Armbian_5.38_Tinkerboard_Ubuntu_xenial_next_4.14.xx_desktop.img 'armbian-config' System switch to Nightly (BETA).

My keyboard was now and then in USA-mode instead of Switzerland, so I have started armbian-config. I think this armbian-config (after the upgrade) is different to my fresh install of last night.

It starts now faster just like the fresh install (by the way) I went to PERSONAL, LOCALES, de_CH.UTF-8 & en_US.UTF-8, wanted to stay on english (it is easier to copy text to the forum) BUT change to my keyboard - the keyboard change option did not show up. While I am sure it did on the fresh install - or am I wrong.. it was late.

Igor · June 18, 2018

37 minutes ago, Tido said:

Shall I add in the first post to do: sudo apt update && upgrade for fresh-install to get your latest bugfix?

Today's update will include more fixes ... but even with it, some leftovers shell be manually cleaned from the previous update. I didn't make a script for that.

To do minor, manual clean up:

sudo nano /etc/logrotate.conf

sudo nano /etc/logrotate.d/*

Removing those lines:

# compress

su root syslog

Edited June 18, 2018 by Tido
changed, took me a bit to understand

Tido · June 18, 2018

5 minutes ago, Tido said:

It starts now faster just like the fresh install (by the way) I went to PERSONAL, LOCALES, de_CH.UTF-8 & en_US.UTF-8, wanted to stay on english (it is easier to copy text to the forum) BUT change to my keyboard - the keyboard change option did not show up. While I am sure it did on the fresh install - or am I wrong.. it was late.

just ran sudo apt update && upgrade and an update for armbian-config came through

UPDATE: in the new armbian-config the keyboard is available.

Maybe a stupid question, why didn't it come when I switched to Nightly ?

Edited June 18, 2018 by Tido
keyboard available

Tido · June 18, 2018

10 minutes ago, Igor said:

/etc/logrotate.d/*

my output shows only this files, what is to do ?

/etc/logrotate.d/
apt armhwinfo rsyslog
aptitude cups-daemon unattended-upgrades
armbian-hardware-monitor dpkg

11 minutes ago, Igor said:

# compress

su root syslog

Wouldn't it be enough to 'comment' these lines, well #compress already is - like this ?

# compress

#su root syslog

Igor · June 18, 2018

1 hour ago, Tido said:

Wouldn't it be enough to 'comment' these lines

https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-hardware-optimization#L45-L56

Actually compress can stay. "su root syslog" part might do some troubles. BTW. Still compiling today's build.

Igor · June 18, 2018

Today's updates are made. I only had to purge zram-config to make our zram logging running ...

apt purge zram-config

Tido · June 18, 2018

1 hour ago, Igor said:

I only had to purge zram-config to make our zram logging running

that said, does this mean this is obsolete:

12 hours ago, Igor said:

To do minor, manual clean up:

sudo nano /etc/logrotate.conf

sudo nano /etc/logrotate.d/*

Removing those lines:

# compress

su root syslog

Tido · June 18, 2018

I have done the same checks for zram like yesterday. It is one dev less and lzo versus lz4.

Spoiler


Welcome to ARMBIAN 5.46.180617 nightly Ubuntu 16.04.4 LTS 4.14.50-rockchip   
System load:   0.61 0.20 0.07  	Up time:       0 min		
Memory usage:  7 % of 2005MB 	IP:            192.168.9.9
CPU temp:      42°C           	
Usage of /:    75% of 3.0G   	


root@tinkerboard:~# zramctl
NAME       ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 lzo         250.7M   4K   78B   12K       4 [SWAP]
/dev/zram1 lzo         250.7M   4K   78B   12K       4 [SWAP]
/dev/zram2 lzo         250.7M   4K   78B   12K       4 [SWAP]
/dev/zram3 lzo         250.7M   4K   78B   12K       4 [SWAP]


root@tinkerboard:~# swapon --show
NAME       TYPE        SIZE USED PRIO
/dev/zram0 partition 250.7M   0B    5
/dev/zram1 partition 250.7M   0B    5
/dev/zram2 partition 250.7M   0B    5
/dev/zram3 partition 250.7M   0B    5


root@tinkerboard:~# sysctl vm.swappiness
vm.swappiness = 60


root@tinkerboard:~# LANG=en free -h
              total        used        free      shared  buff/cache   available
Mem:           2.0G        148M        1.6G         25M        243M        1.7G
Swap:          1.0G          0B        1.0G

hmmm, since I did: apt purge zram-config reboot lz4 and the dev came back :-)

Spoiler


root@tinkerboard:~# zramctl
NAME       ALGORITHM DISKSIZE  DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 lz4            40M 12.3M  4.4M    5M       4 /var/log
/dev/zram1 lz4         250.7M    4K   63B    4K       4 [SWAP]
/dev/zram2 lz4         250.7M    4K   63B    4K       4 [SWAP]
/dev/zram3 lz4         250.7M    4K   63B    4K       4 [SWAP]
/dev/zram4 lz4         250.7M    4K   63B    4K       4 [SWAP]


root@tinkerboard:~# swapon --show
NAME       TYPE        SIZE USED PRIO
/dev/zram1 partition 250.7M   0B    5
/dev/zram2 partition 250.7M   0B    5
/dev/zram3 partition 250.7M   0B    5
/dev/zram4 partition 250.7M   0B    5


root@tinkerboard:~# sysctl vm.swappiness
vm.swappiness = 60


root@tinkerboard:~# LANG=en free -h
              total        used        free      shared  buff/cache   available
Mem:           2.0G        152M        1.6G         13M        245M        1.7G
Swap:          1.0G          0B        1.0G

What else can be tested, reported for example log2RAM ?

Edited June 18, 2018 by Tido
forgot - apt purge zram-config

lampra · June 18, 2018

Espressobin

Spoiler


Welcome to ARMBIAN 5.46.180617 nightly Debian GNU/Linux 9 (stretch) 4.14.50-mvebu64   
System load:   0.06 0.06 0.05  	Up time:       22 min		
Memory usage:  6 % of 993MB  	IP:            192.168.100.9
CPU temp:      36°C           	
Usage of /:    9% of 15G 

root@espressobin:/# zramctl 
NAME       ALGORITHM DISKSIZE  DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 lz4            50M  5,6M  1,1M  1,5M       2 /var/log
/dev/zram1 lz4         248,3M    4K   63B    4K       2 [SWAP]
/dev/zram2 lz4         248,3M    4K   63B    4K       2 [SWAP]

root@espressobin:/# swapon --show
NAME       TYPE        SIZE USED PRIO
/var/swap  file        128M   0B   -2
/dev/zram1 partition 248,3M   0B    5
/dev/zram2 partition 248,3M   0B    5

root@espressobin:/# free -h
              total        used        free      shared  buff/cache   available
Mem:           993M         67M        734M        2,9M        191M        857M
Swap:          624M          0B        624M

root@espressobin:/# apt purge zram-config
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package zram-config

Igor · June 19, 2018

5 hours ago, lampra said:

apt purge zram-config

That's ok. A package is not present in Debian.

Next thing to test is ... logrotate. It check's every 15 minutes if we are over 75%. Then it save logs, rotate them and truncate/zero logs on the /var/log ... this is theory and I hope reality as well. We need to test random, common and extreme situations of logging to see if default settings are O.K. for most cases. Then somewhere must be written how to configure this system.

tkaiser · June 19, 2018

1 hour ago, Igor said:

A package is not present in Debian

Just for the record: this package (a simple script in reality) installs and works pretty well in Debian too so it should be purged anywhere as part of an upgrade mechanism.

Igor · June 19, 2018

6 hours ago, tkaiser said:

so it should be purged anywhere as part of an upgrade mechanism

This should do, so we can actually remove the checking part as well.

https://github.com/armbian/build/commit/bd2aeb8d8f71027522ec2c5333c191deb1cce82d

Found troubles on Bionic builds, ZRAM service timeouts.

Tido · June 20, 2018

17 hours ago, Igor said:

ZRAM service timeouts

Can you be more specific, how you found that bug?
What can be done to analyse this behavior ?
Is it on both upgrade and fresh install ?

Are the Google results any helpful or is it armbian specific ?

Igor · June 20, 2018

1 hour ago, Tido said:

Can you be more specific, how you found that bug?
What can be done to analyse this behavior ?

I was testing freshly made Odroid C2 DEV build with Bionic ... I haven't narrowed down the problem. It can be a kernel or some other service related. ATM I don't know if it's our or general problem.

TonyMac32 · June 24, 2018

On 6/19/2018 at 9:34 AM, Igor said:

Found troubles on Bionic builds, ZRAM service timeouts.

I found the same on Alwwiner H5-based board with Bionic:

[FAILED] Failed to start Armbian ZRAM config.
See 'systemctl status armbian-zram-config.service' for details.

That results in a 2 minute boot delay. It seems to succeed in the end though, or eventually:

tony@tritium:~$ sudo systemctl status armbian-zram-config.service
● armbian-zram-config.service - Armbian ZRAM config
   Loaded: loaded (/lib/systemd/system/armbian-zram-config.service; enabled; ven
   Active: active (exited) since Sun 2018-06-24 18:53:02 UTC; 6min ago
  Process: 576 ExecStart=/usr/lib/armbian/armbian-zram-config start (code=exited
 Main PID: 576 (code=exited, status=0/SUCCESS)

Jun 24 18:53:02 tritium armbian-zram-config[576]: no label, UUID=d4c99662-9d44-4
Jun 24 18:53:02 tritium armbian-zram-config[576]: Setting up swapspace version 1
Jun 24 18:53:02 tritium armbian-zram-config[576]: no label, UUID=5b252a9a-1cdf-4
Jun 24 18:53:02 tritium armbian-zram-config[576]: mke2fs 1.44.1 (24-Mar-2018)
Jun 24 18:53:02 tritium armbian-zram-config[576]: [74B blob data]
Jun 24 18:53:02 tritium armbian-zram-config[576]: Creating filesystem with 12800
Jun 24 18:53:02 tritium armbian-zram-config[576]: [41B blob data]
Jun 24 18:53:02 tritium armbian-zram-config[576]: [38B blob data]
Jun 24 18:53:02 tritium armbian-zram-config[576]: [75B blob data]
Jun 24 18:53:02 tritium systemd[1]: Started Armbian ZRAM config.

http://ix.io/1eFg

Igor · June 24, 2018

8 minutes ago, TonyMac32 said:

That results in a 2 minute boot delay. It seems to succeed in the end though, or eventually:

Yes, it succeeds, but why, for what is waiting? Dependency issues?

guidol · June 25, 2018

On 6/20/2018 at 10:59 AM, Igor said:

I was testing freshly made Odroid C2 DEV build with Bionic ... I haven't narrowed down the problem. It can be a kernel or some other service related. ATM I don't know if it's our or general problem.

I did boot Armbian_5.48.180624_Odroidc2_Ubuntu_bionic_dev_4.17.2 today...

I do get a heartbeat at the blue LED, but no sign of life at the ethernet port (green is going up and down, but orange never comes on) ....and I wonder even with a USB-Ethernet device there is no DHCP request.

At this time I didnt got a serial port attached

guidol · June 26, 2018

On 6/25/2018 at 11:28 AM, guidol said:

I did boot Armbian_5.48.180624_Odroidc2_Ubuntu_bionic_dev_4.17.2 today...

I do get a heartbeat at the blue LED, but no sign of life at the ethernet port (green is going up and down, but orange never comes on) ....and I wonder even with a USB-Ethernet device there is no DHCP request.

@Igor today I got the same effect (no usb-ethernet) at the OPi Zero Plus2 H5 with

Armbian_5.48.180624_Orangepizeroplus2-h5_Ubuntu_bionic_dev_4.17.2

On my User-Build Kernel (with LED-Support and HDMI-disable for proper reboot) the USB-Ethernet does work.

But at the nightly I do get the following error-messages (for orientation some good messages before the errors) via the serial port:


Loading Environment from EXT4... ** File not found /boot/boot.env **
** Unable to read "/boot/boot.env" from mmc0:1 **
Failed (-5)
Loading Environment from FAT... Unable to use mmc 1:1... Failed (-5)

[  OK  ] Started Create list of required sta…vice nodes for the current kernel.
[  OK  ] Started Remount Root and Kernel File Systems.
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
...
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
         Starting Update UTMP about System Boot/Shutdown...
         Starting Load Kernel Modules...
         Starting Network Time Synchronization...
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.


[    5.041850] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    5.169329] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    5.169439] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.clm_blob failed with error -2

Maybe these are the "same" as on the Odroid C2, because there is also no onboard/USB-Ethernet.
Here as hidden the serial Boot-Log from the first boot (my normal user-build system/kernel is on emmc and this is the sdcard boot):

Spoiler

U-Boot 2018.03-armbian (Jun 24 2018 - 19:54:11 +0000) Allwinner Technology

CPU: Allwinner H5 (SUN50I)
Model: OrangePi Zero Plus2
DRAM: 512 MiB
MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
Failed (-5)
Loading Environment from FAT... Unable to use mmc 1:1... Failed (-5)
In: serial
Out: serial
Err: serial
Net: No ethernet found.
230454 bytes read in 139 ms (1.6 MiB/s)
starting USB...
No controllers found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3090 bytes read in 195 ms (14.6 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
192 bytes read in 157 ms (1000 Bytes/s)
22802 bytes read in 334 ms (66.4 KiB/s)
385 bytes read in 532 ms (0 Bytes/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
385 bytes read in 539 ms (0 Bytes/s)
Applying kernel provided DT overlay sun50i-h5-usbhost3.dtbo
4179 bytes read in 416 ms (9.8 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 44000000
7978052 bytes read in 668 ms (11.4 MiB/s)
13262856 bytes read in 920 ms (13.7 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 7977988 Bytes = 7.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
Booting using the fdt blob at 0x4fa00000
Loading Ramdisk to 49864000, end 49fffc04 ... OK
reserving fdt memory region: addr=4fa00000 size=6b000
Loading Device Tree to 00000000497f6000, end 0000000049863fff ... OK

Starting kernel ...

Loading, please wait...
starting version 237
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.31.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: recovering journal
/dev/mmcblk0p1: clean, 34623/962880 files, 266379/3849616 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Ubuntu 18.04 LTS!

[ OK ] Set up automount Arbitrary Executab…rmats File System Automount Point.
[ OK ] Reached target System Time Synchronized.
[ OK ] Reached target Remote File Systems.
[ OK ] Reached target Swap.
[ OK ] Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Started ntp-systemd-netif.path.
[ OK ] Created slice System Slice.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ OK ] Listening on udev Control Socket.
[ OK ] Listening on Journal Audit Socket.
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Listening on Journal Socket.
Starting Nameserver information manager...
Mounting Huge Pages File System...
Mounting POSIX Message Queue File System...
[ OK ] Listening on Syslog Socket.
Starting Set the console keyboard layout...
Mounting Kernel Debug File System...
Starting Restore / save the current clock...
[ OK ] Listening on fsck to fsckd communication Socket.
Starting Create list of required st…ce nodes for the current kernel...
[ OK ] Listening on udev Kernel Socket.
Starting udev Coldplug all Devices...
[ OK ] Started Forward Password Requests to Wall Directory Watch.
[ OK ] Reached target Local Encrypted Volumes.
[ OK ] Created slice User and Session Slice.
[ OK ] Reached target Slices.
Starting Load Kernel Modules...
Starting Remount Root and Kernel File Systems...
[ OK ] Mounted Huge Pages File System.
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Mounted Kernel Debug File System.
[ OK ] Started Restore / save the current clock.
[ OK ] Started Create list of required sta…vice nodes for the current kernel.
[ OK ] Started Remount Root and Kernel File Systems.
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[ OK ] Started Nameserver information manager.
[ OK ] Reached target Network (Pre).
Starting Apply Kernel Variables...
Mounting Kernel Configuration File System...
Starting Load/Save Random Seed...
Starting Create Static Device Nodes in /dev...
[ OK ] Started udev Coldplug all Devices.
[ OK ] Mounted Kernel Configuration File System.
[ OK ] Started Set the console keyboard layout.
[ OK ] Started Apply Kernel Variables.
[ OK ] Started Load/Save Random Seed.
[ OK ] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager...
[ OK ] Reached target Local File Systems (Pre).
Mounting /tmp...
[ OK ] Mounted /tmp.
[ OK ] Reached target Local File Systems.
Starting Armbian ZRAM config...
Starting Raise network interfaces...
Starting Set console font and keymap...
[ OK ] Started udev Kernel Device Manager.
[ OK ] Started Set console font and keymap.
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Starting Load/Save RF Kill Switch Status...
[ OK ] Found device /dev/ttyS0.
[ OK ] Started Load/Save RF Kill Switch Status.
[ OK ] Started Armbian ZRAM config.
Starting Armbian memory supported logging...
[ OK ] Started Raise network interfaces.
[ OK ] Started Armbian memory supported logging.
Starting Journal Service...
[ OK ] Started Journal Service.
Starting Flush Journal to Persistent Storage...
[ OK ] Started Flush Journal to Persistent Storage.
Starting Create Volatile Files and Directories...
[ OK ] Started Create Volatile Files and Directories.
Starting Network Name Resolution...
[ OK ] Started Entropy daemon using the HAVEGE algorithm.
Starting Update UTMP about System Boot/Shutdown...
Starting Load Kernel Modules...
Starting Network Time Synchronization...
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Started Network Name Resolution.
[ OK ] Reached target Host and Network Name Lookups.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Initialization.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Started Message of the Day.
[ OK ] Started Discard unused blocks once a week.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Started resolvconf-pull-resolved.path.
[ OK ] Reached target Paths.
Starting Armbian hardware monitoring...
Starting Armbian hardware optimization...
[ OK ] Started Daily apt download activities.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Reached target Timers.
[ OK ] Started Armbian hardware optimization.
[ OK ] Started Armbian hardware monitoring.
[ OK ] Reached target Basic System.
[ OK ] Started Set the CPU Frequency Scaling governor.
Starting LSB: Patch firmware for ap6212 adapter...
Starting Login Service...
[ OK ] Started Regular background program processing daemon.
[ OK ] Started Armbian first run tasks.
Starting Dispatcher daemon for systemd-networkd...
Starting LSB: Load kernel modules needed to enable cpufreq scaling...
[ OK ] Started ntp-systemd-netif.service.
Starting System Logging Service...
[ OK ] Started D-Bus System Message Bus.
[ OK ] Started Login Service.
Starting WPA supplicant...
Starting Network Manager...
Starting resolvconf-pull-resolved.service...
Starting Resets System Activity Data Collector...
[ OK ] Started System Logging Service.
[ OK ] Started LSB: Patch firmware for ap6212 adapter.
[ OK ] Started Resets System Activity Data Collector.
[ OK ] Started resolvconf-pull-resolved.service.
[ OK ] Started WPA supplicant.
[ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
Starting LSB: set CPUFreq kernel parameters...
[ OK ] Started LSB: set CPUFreq kernel parameters.
Starting LSB: Set sysfs variables from /etc/sysfs.conf...
[ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
Starting Hostname Service...
[ OK ] Started Hostname Service.
[ OK ] Started Network Manager.
Starting Network Manager Script Dispatcher Service...
Starting Network Manager Wait Online...
[ OK ] Reached target Network.
[ OK ] Started Unattended Upgrades Shutdown.
Starting Permit User Sessions...
Starting OpenBSD Secure Shell server...
[ OK ] Started Permit User Sessions.
[ OK ] Started Network Manager Script Dispatcher Service.
Starting Set console scheme...
[ OK ] Started Set console scheme.
[ OK ] Created slice system-getty.slice.
[ OK ] Started OpenBSD Secure Shell server.
[ OK ] Started Dispatcher daemon for systemd-networkd.
Starting Authorization Manager...
[ OK ] Started Authorization Manager.
[ OK ] Started Network Manager Wait Online.
[ OK ] Reached target Network is Online.
Starting LSB: Advanced IEEE 802.11 management daemon...
Starting /etc/rc.local Compatibility...
[ OK ] Started LSB: Advanced IEEE 802.11 management daemon.
[ OK ] Started /etc/rc.local Compatibility.
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Started Getty on tty1.
Starting resolvconf-pull-resolved.service...
[ OK ] Started resolvconf-pull-resolved.service.

Ubuntu 18.04 LTS orangepizeroplus2 ttyS0

orangepizeroplus2 login: root
Password: Starting resolvconf-pull-resolved.service...
[ OK ] Started resolvconf-pull-resolved.service.
Starting resolvconf-pull-resolved.service...
[ OK ] Started resolvconf-pull-resolved.service.
Stopping OpenBSD Secure Shell server...
[ OK ] Stopped OpenBSD Secure Shell server.
Starting OpenBSD Secure Shell server...
[ OK ] Started OpenBSD Secure Shell server.
Stopping OpenBSD Secure Shell server...
[ OK ] Stopped OpenBSD Secure Shell server.
Starting OpenBSD Secure Shell server...
[ OK ] Started OpenBSD Secure Shell server.
Starting resolvconf-pull-resolved.service...
[ OK ] Started resolvconf-pull-resolved.service.

Login incorrect
orangepizeroplus2 login: root
Password:
You are required to change your password immediately (root enforced)
Changing password for root.
(current) UNIX password:
Enter new UNIX password:
Retype new UNIX password:
___ ____ _ _____ ____ _ ____
/ _ \| _ \(_) |__ /___ _ __ ___ | _ \| |_ _ ___ |___ \
| | | | |_) | | / // _ \ '__/ _ \ | |_) | | | | / __| __) |
| |_| | __/| | / /| __/ | | (_) | | __/| | |_| \__ \ / __/
\___/|_| |_| /____\___|_| \___/ |_| |_|\__,_|___/ |_____|

Welcome to ARMBIAN 5.48.180624 nightly Ubuntu 18.04 LTS 4.17.2-sunxi64
System load: 0.23 0.07 0.02 Up time: 0 min
Memory usage: 12 % of 482MB IP:
Usage of /: 6% of 15G

New to Armbian? Check the documentation first: https://docs.armbian.com
[ OK ] Created slice User Slice of root.
Starting User Manager for UID 0...
[ OK ] Started Session 1 of user root.
[ OK ] Started User Manager for UID 0.

You are using an Armbian nightly build meant only for developers to provide
constructive feedback to improve build system, OS settings or user experience.
If this does not apply to you, STOP NOW!. Especially don't use this image for
daily work since things might not work as expected or at all and may break
anytime with next update. YOU HAVE BEEN WARNED!

This image is provided AS IS with NO WARRANTY and NO END USER SUPPORT!.

Creating a new user account. Press <Ctrl-C> to abort

Igor · June 26, 2018

22 minutes ago, guidol said:

the USB-Ethernet does work.

As expected. 4.17.y don't have overlay support there ... and USB ports are disabled by default on this board. DEV is experimental/preparation build and many things might be broken.

26 minutes ago, guidol said:

Maybe these are the "same" as on the Odroid C2

Unfortunately no. USB on C2 is much more problematic. It's enabled but sometimes doesn't work. Here at least we know why it doesn't

We seek ZRAM related issues at this point. That is planned to go into stable builds - when it's working as expected or at least if we know what prevents that, while 4.17-18 is months away.

guidol · June 26, 2018

45 minutes ago, Igor said:

As expected. 4.17.y don't have overlay support there ... and USB ports are disabled by default on this board.
DEV is experimental/preparation build and many things might be broken.

Ahh - I didnt know that overlay support is disabled - that do clarify some things

I know DEV is a experimental/preparation build, but on the most SBCs here it do work quite well!
Now I know that mostly more the onboard/original hardware should work.

Igor · June 26, 2018

2 minutes ago, guidol said:

Now I know that mostly more the onboard/original hardware should work.

Our target for Allwinner is to get 4.18.y operational and 4.17.y servers only to prepare patches, as a temporal version.

Arglebargle · June 28, 2018

Can someone answer a naive question about the new zram implementation? I think I've found something important that's been overlooked.

# Use half of the real memory by default --> 1/${ram_divisor}
	ram_divisor=2
	mem_info=$(LC_ALL=C free -w 2>/dev/null | grep "^Mem" || LC_ALL=C free | grep "^Mem")
	memory_total=$(awk '{printf("%d",$2*1024)}' <<<${mem_info})
	mem_per_zram_device=$(( ${memory_total} / ${zram_devices} / ${ram_divisor} ))

	for (( i=1; i<=zram_devices; i++ )); do
		[[ -f /sys/block/zram${i}/comp_algorithm ]] && echo lz4 >/sys/block/zram${i}/comp_algorithm 2>/dev/null
		echo -n ${mem_per_zram_device} > /sys/block/zram${i}/disksize
		mkswap /dev/zram${i}
		swapon -p 5 /dev/zram${i}
	done
	echo -e "\n### Activated ${zram_devices} zram swap devices with ${mem_per_zram_device} MB each\n" >>${Log}

Is the intent here to devote half of real memory to zram and take advantage of compression to multiply that chunk of memory, or is the intent to provide some small swap space without hitting swap on flash storage?

Right now the script is doing the latter, not the former. The current implementation makes swap space equal in size to half of ram, which is then compressed (usually at 2:1 or 3:1, most often at 3:1) and stored in memory. This means that, on average, the amount of actual ram used by zram hovers between 25% and ~17% rather than the apparently intended 50%.

I spent quite a bit of time researching and profiling something similar for my own use and I've settled on the following to allocate 50% of real memory to zram:

mem_per_zram_device=$(( 3 * ${memory_total} / ${zram_devices} / ${ram_divisor} ))

Coincidentally this is the same zram allocation that Google makes on ChromeOS.

I've seen the same mistake made in almost every single zram script that I can find via Google so this definitely isn't an Armbian thing. It looks like someone made the original logic error at some point a long time ago and it's been copy-pasted into every zram setup script for the last 7 or 8 years.

For what it's worth setting /sys/block/zramN/mem_limit does what everyone seems to be expecting and limits the amount of ram that the zram device can use. Unfortunately there is no way to adaptively vary /sys/block/zramN/disksize according to the actual compression ratio so the currently accepted best practice seems to be assuming 3:1 and punting (this is what Google does on ChromeOS.)

Edited June 28, 2018 by Arglebargle
clarification

Flávio Becker · June 29, 2018

Hi, I just installed the 5.49 nightly build (4.17.3) on my OrangePI Prime.

It's running quite well and I had almost no issues until now, except for:

. some errors reported by journald (journal corruption) that ended up filling up all /var/log space.

. sometimes the reboot doesn't work, freezing on a black screen with a cursor blinking in one corner.

The errors reported by journald were probably caused by my need to power off and on to resume after the reboot freezing.

I had to delete the log files though to be able to perform the system settings (language, timezone and so on).

Igor · June 29, 2018

2 minutes ago, Flávio Becker said:

The errors reported by journald were probably caused by my need to power off and on to resume after the reboot freezing.

Not sure. I also noticed this (only?) on Bionic version which has some other problems and it's still in testing/fixing phase.

Thank you for the report. Next time supply logs with:

armbianmonitor -u

This way we can see more.

Sign In

WE NEED !YOUR! HELP

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Important Information