lfam

As you can see here [1], it should be included in upstream Debian, eventually. I'm not sure if that will get in to Jessie or if we will have to wait for Stretch. Also, I can forgot to mention before that this is a "minimal" installation of Debian — no X. Just some more information. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803184

The great people on #debian-systemd told me this requires libpam-systemd, which is not included by default in minimal Jessie. I rebooted to enable it, but you may only have to relogin and / or restart systemd-logind.service.

I just installed Armbian 4.2 and then upgraded it to Armbian 4.6 using the Armbian APT repositories. I am running Debian Jessie with the sunxi kernel 3.4.109 on a Cubieboard 2. My issue is that systemd user sessions don't work out of the box. When I try to check the status of my user session, this is what happens: $ systemctl --user status Failed to get D-Bus connection: Connection refused $ systemd --version systemd 215 +PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR Any ideas? Any other information I can provide? This used to work on a pre-Armbian image from Igor. That installation became unstable and I messed up the upgrade so I reinstalled from scratch, starting at 4.2 because I want systemd (recent images disable it).

I found it: http://mirror.igorpecovnik.com/

Are the old releases of Armbian available anywhere? I can't find them.

I've been having these sorts of problems on my Cubieboard2 running Debian Jessie on the sunxi kernel in the past few months also. The older wheezy images were stable. I'm not sure when the issue started. I won't have physical access to the machine for a couple days, so I can't give very detailed information at the moment, but I will report back then. I'd like to move to the mainline kernel but I am waiting for audio support. I believe this will be in 4.4 based on the sunxi wiki [1] although I haven't noticed it on the RC kernel changelogs published by Torvalds. What are the major changes between Armbian releases? Is there a downgrade process or do I have to reinstall the OS? What is the full list of information I can give that may help diagnose the issue? For example, should anything be added to this list? Kernel version Contents of /etc/armbian.txt u-boot build date? How can I check that? Should I provide a hash of something? Description of power supply Connected peripherals Results of a memtest? What provides this on ARM? Anything else? I'm willing to spend some time running tests and providing information. [1] http://linux-sunxi.org/Linux_mainlining_effort#Merged_into_4.4

It also writes to the sysfs, setting the block IO scheduler. Anyways, I'm going to dig in. Where should I submit my patch, if I produce one?

The script /etc/init.d/armhwinfo is executed on boot and gathers information about the machine's capabilities to tweak some settings. On my Cubieboard2 running Debian Jessie, it sometimes takes up to 20 seconds to execute. For example, last boot: $ systemd-analyze critical-chain multi-user.target @30.700s └─armhwinfo.service @12.831s +17.867s └─basic.target @12.155s └─timers.target @12.130s └─systemd-tmpfiles-clean.timer @12.130s └─sysinit.target @12.097s └─networking.service @4.315s +7.732s └─systemd-random-seed.service @3.979s +112ms └─systemd-remount-fs.service @3.672s +286ms └─keyboard-setup.service @2.272s +1.379s └─systemd-udevd.service @2.175s +35ms └─systemd-tmpfiles-setup-dev.service @2.012s +75ms └─kmod-static-nodes.service @1.732s +186ms └─system.slice @1.290s └─-.slice @1.033s I'd like to improve this situation. My first question: is the script idempotent? By which I mean, is there any harm in running it over and over again while I figure out which steps are taking soooooo long?