mhm, afair 1M-file from my wiki/gdrive was created before uboot upstream support
Should I use the 2019 1M file which I have extracted from your latest built? Will that make any difference?
it has at least redesigned buildin-environment where we can do some things easier in uboot-console
e.g. “run buildargs” manually and see if your option is now in bootargs (printenv bootargs)
I flashed the 2019 1M and that seems to accept the bootarg allowed to login in Rescue mode.
Now I will try to remove the uEnv.txt and try again. Thank You very much. Ah but again It doesnt let me login withlogin password. I am not able to login in rescue mode. @cioby23
Here is the journal log from rescue mode.
Sep 23 23:54:31 alarm systemd-tmpfiles[191]: Failed to open directory 'private'>
Sep 23 23:54:31 alarm systemd-tmpfiles[191]: Failed to create file /var/log/wtm>
Sep 23 23:54:31 alarm systemd-tmpfiles[191]: Failed to create file /var/log/btm>
Sep 23 23:54:31 alarm systemd-tmpfiles[191]: Failed to create file /var/log/las>
looks wrong
what is output of
"systemctl status systemd-logind.service" and "journalctl -xe"
?
* systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vend>
Active: inactive (dead)
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
https://www.freedesktop.org/wiki/Software/systemd/logind
https://www.freedesktop.org/wiki/Software/systemd/multiseat```
[quote="frank-w, post:35, topic:3986"]
"journalctl -xe"
[/quote]
journalctl -xe
Sep 23 23:54:33 alarm systemd[1]: systemd-timesyncd.service: Start request repe>
Sep 23 23:54:33 alarm systemd[1]: systemd-timesyncd.service: Failed with result>
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit systemd-timesyncd.service has entered the 'failed' state with resul>
Sep 23 23:54:33 alarm systemd[1]: Failed to start Network Time Synchronization.
-- Subject: A start job for unit systemd-timesyncd.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit systemd-timesyncd.service has finished with a failure.
--
-- The job identifier is 107 and the job result is failed.
Sep 23 23:54:33 alarm systemd[209]: rescue.service: Executable /bin/plymouth mi>
-- Subject: Process /bin/plymouth could not be executed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /bin/plymouth could not be executed and failed.
--
-- The error number returned by this process is ERRNO.not more? maybe you have to scroll…
I tried to restart the service so I can get logind error.
journalctl -xe
Sep 24 00:08:15 alarm systemd[1]: Failed to start Login Service.
-- Subject: A start job for unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit systemd-logind.service has finished with a failure.
--
-- The job identifier is 395 and the job result is failed.
Sep 24 00:08:23 alarm systemd[1]: systemd-logind.service: Start request repeate>
Sep 24 00:08:23 alarm systemd[1]: systemd-logind.service: Failed with result 'r>
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit systemd-logind.service has entered the 'failed' state with result '>
Sep 24 00:08:23 alarm systemd[1]: Failed to start Login Service.
-- Subject: A start job for unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit systemd-logind.service has finished with a failure.
--
-- The job identifier is 451 and the job result is failed.scroll a bit to right…it’s cut off
result is done.
d-logind.service: Start request repeated too quickly.
d-logind.service: Failed with result 'resources'.
g/mailman/listinfo/systemd-devel
ntered the 'failed' state with result 'resources'.
to start Login Service.
-logind.service has failed
g/mailman/listinfo/systemd-devel
ervice has finished with a failure.
I see this also in journal -xe
-logind.service: Failed to run 'start-pre' task: Read-only file system
d-logind.service: Failed with result 'resources'.ok, you have readonly-rootfs,maybe cause of FS-error
Sep 23 23:54:29 alarm kernel: VFS: Mounted root (ext4 filesystem) readonly on d>
but again cut off
Yes its ext4 in readonly why ?
torun DONE.
mcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
ed root (ext4 filesystem) readonly on device 179:2. <<<<HERE
mounted
used kernel memory: 1024K
init as init process
time before build time, advancing clock.
tered protocol family 10
uting with IPv6
d 243.51-1-arch running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +S>
ed architecture arm.
My fstab is blank, Thats how It is from the Arch Latest rootfs from their official repo.
When I check with lsblk I can see it is not RO.
[root@alarm /]# lsblk -l
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 14.9G 0 disk
mmcblk0p1 179:1 0 256M 0 part
mmcblk0p2 179:2 0 6.7G 0 part /
mmcblk1 179:8 0 7.3G 0 disk
mmcblk1boot0 179:16 0 4M 1 disk
mmcblk1boot1 179:24 0 4M 1 disk
[root@alarm /]# lsblk -m
NAME SIZE OWNER GROUP MODE
mmcblk0 14.9G root disk brw-rw----
|-mmcblk0p1 256M root disk brw-rw----
`-mmcblk0p2 6.7G root disk brw-rw----
mmcblk1 7.3G root disk brw-rw----
mmcblk1boot0 4M root disk brw-rw----
mmcblk1boot1 4M root disk brw-rw----
When I try to create a new text file to test it says read only fs.
Try a remount with readwrite mode
mount / -o remount,rw
And restart login-service
1 Like
This worked. So what do you think is the issue here? Is it from the official rootfs?
systemctl status systemd-logind.service
* systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; ven
d>
Active: active (running) since Tue 2019-09-24 00:14:06 UTC; 6s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
https://www.freedesktop.org/wiki/Software/systemd/logind
https://www.freedesktop.org/wiki/Software/systemd/multiseat
Process: 252 ExecStartPre=/sbin/modprobe -abq drm (code=exited, status=1/FAI
L>
Main PID: 253 (systemd-logind)
Status: "Processing requests..."
Tasks: 1
Memory: 1.6M
CGroup: /system.slice/systemd-logind.service
`-253 /usr/lib/systemd/systemd-logind
Sep 24 00:14:05 alarm systemd[1]: Starting Login Service...
Sep 24 00:14:06 alarm systemd-logind[253]: New seat seat0.
Sep 24 00:14:06 alarm systemd-logind[253]: Watching system buttons on /dev/inp
u>
Sep 24 00:14:06 alarm systemd-logind[253]: Watching system buttons on /dev/inp
u>
Sep 24 00:14:06 alarm systemd-logind[253]: Watching system buttons on /dev/inp
u>
Sep 24 00:14:06 alarm systemd-logind[253]: Watching system buttons on /dev/inp
u>
Sep 24 00:14:06 alarm systemd[1]: Started Login Service.
Finally I was able to login with login and password.
Try to add line in fstab for rootfs like the one i’ve added in my debian-images
Ok thanks dear.
Yes this worked. Thanks so much for your support.
@cioby23 Finally I have a working Arch IMG ready but I am working on making it more clean with OEM Installer on boot. Like Manjaro uses. Will post it in few hours.
@frank-w Thanks for all your effort. I have tried connecting my phone on usb tethering but I don’t think 4.19 have that support?
Please try it and let me know what all works and whats broken, as I have only tested if it boots as I dont have any lan connection at home will test it thoroughly tomorrow in office.
I’m running Arch Linux ARM on my BPI-R2 but I made it “manually” (with @frank-w 5.4 kernel)
I will test with pleasure you guide!
WOW he is already working on 5.4, That’s great.
Would appreciate your feedback. I can get kernel 5.4 working on it too, But I don’t see many users looking for arch, As we also need motivation from users to keep maintaining our builds.
Thanks looking forward for your feedback, If you want me to add other kernel version support then feel free to request.
1 Like
I’m also working on 5.5 (my poweroff series is not completely merged) and future versions (hdmi is missing also some parts) 
1 Like