<bashintosh>
Has anyone seen these errors on Ubuntu 14.10 (RK3288)?
<bashintosh>
[ 34.125202] systemd-logind[786]: Failed to start unit user@104.service: Unknown unit: user@104.service
<bashintosh>
[ 34.125251] systemd-logind[786]: Failed to start user service: Unknown unit: user@104.service
<bashintosh>
I am using Linuxium Ubuntu 14.10 RFS - custom kernel using eDP - CONFIG_VT=y
<bashintosh>
Booting from SD
naobsd has joined #linux-rockchip
bbelos has quit [Ping timeout: 240 seconds]
ckeepax has joined #linux-rockchip
erc has quit [Ping timeout: 248 seconds]
erc has joined #linux-rockchip
premoboss has quit [Ping timeout: 264 seconds]
naobsd has quit [Quit: naobsd]
bbelos has joined #linux-rockchip
<sjoerd>
bashintosh: that's not a rockchip kernel issue, ask the ubuntu folks ? :)
bbelos has quit [Ping timeout: 245 seconds]
bbelos has joined #linux-rockchip
premoboss has joined #linux-rockchip
amstan has quit [Ping timeout: 248 seconds]
amstan has joined #linux-rockchip
amstan has joined #linux-rockchip
cosm has quit [Quit: Leaving]
cosm has joined #linux-rockchip
<bashintosh>
sjoerd: I thought so to - my setup uses linuxium RFS (https://plus.google.com/+IanMORRISON/posts/22Vxc6Sr5Ei) which is likely well tested and adopted by many RK3288 users and I think cnxsoft also tried it. That error I posted above seems to be common with Ubuntu 14.10 which adopted systemd by default - when digging in detail userland(ish) software like systemd actually deals with the kernel a fair bit
<bashintosh>
so kernel config can be critical for its proper execution (https://galileo.mailstation.de/?p=31). So I thought perhaps someone slammed into the same issue and for some reason the kernel (config?) was to be blamed. Otherwise I struggle to understand how linuxium released a broken RFS... :)
premoboss has quit [Quit: Sto andando via]
naobsd has joined #linux-rockchip
sjoerd has quit [Ping timeout: 250 seconds]
sjoerd has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
cosm has quit [Ping timeout: 272 seconds]
cosm has joined #linux-rockchip
ganbold has quit [Ping timeout: 256 seconds]
em|tue has quit [Ping timeout: 240 seconds]
JohnDoe_71Rus has joined #linux-rockchip
em|tue has joined #linux-rockchip
Astralix has joined #linux-rockchip
ganbold has joined #linux-rockchip
afaerber has quit [Quit: Ex-Chat]
Astralix has left #linux-rockchip [#linux-rockchip]
tyler-baker has quit [Read error: Connection reset by peer]
<Ryhfr>
?bashintosh you have problem with "CONFIG_CGROUPS = is not set "probably is not understand with the kernel then become panic.
Ryhfr has quit [Client Quit]
Apocx has quit [*.net *.split]
mcan has quit [*.net *.split]
mcan has joined #linux-rockchip
tyler-baker has joined #linux-rockchip
ssvb has joined #linux-rockchip
<bashintosh>
CONFIG_CGROUPS is set in my config - here's my complete kernel config (RK 3.10) which is largely derived from the Firefly linux_defconfig -> http://ur1.ca/oi68i
<bashintosh>
Perhaps someone can do a diff with their working (Linux) config and point out if I am missing something critical?
Ryhfr has joined #linux-rockchip
<Ryhfr>
ubuntu pass an -o to tell it what to mount. mount -t cgroup -o memory cgroup_memory /sys/fs/cgroup/memory And that's assuming that /sys/fs/cgroup is mounted at all. mount -t tmpfs cgroup /sys/fs/cgroup
<Ryhfr>
im think than not would be work i have the same problem with new image on rk3188 old work ,after upgrade whole system no more get.
cp-- has joined #linux-rockchip
cp- has quit [Ping timeout: 240 seconds]
<Ryhfr>
systemd is fucking shits
<Ryhfr>
therefere on arm or arm64 why i ned security all is in developing whe wont that shit secure boot secure root ,normal usser use android only 1% use linux and only to experyment im not understand why ubuntu build arm image with full security where break booting
cosm has quit [Quit: Leaving]
<premoboss>
Ryhfr, try devuan, is a fork of debian vithout systemd
<Ryhfr>
premboss with any linux I have no problem, everyone can hack and dispose, the only problem I have is the lack of bootloader for booting from sdcard on rk3368,and this I see that the problem lies in the lack of kexec in the linux kernel for arm64
<Ryhfr>
each toy with arm processors is low on memory for 2 systems, can long guessing but the truth is, therefore, proposes always with the solution The Alliance is ready to adopt the you only need it, but everyone has it in the ass like geekbox
<Ryhfr>
It is a very simple solution to the problem kexec boot. plus petitboot then we have a graphical bootloader gives us possibilities max. none so much as to the present day Chinese Chinese company with arm processors we do not proposed.weating until someone grabs the one who is in your hands is still earn on it.
mrueg has quit [Remote host closed the connection]