Archlinux on R2

spikerguy · September 30, 2019, 2:45pm

Oh yes. So should i create uEnv.txt file with this? systemd.unit=rescue.target

cioby23 · September 30, 2019, 2:55pm

I think you can also enter u-boot cli mode and run setenv bootargs kernel option. Replace kernel option with that line.

frank-w · September 30, 2019, 3:02pm

frank-w/u-boot/blob/7b21e97f09db4ec813218941cfe2196add66e287/uEnv.txt#L24




kernel419_nodt=uImage_4.19.13-main_nodt
fdt419=4.19.13-main.dtb
dtolist419=bpi-r2-mac.dtb


console=earlyprintk console=tty1 fbcon=map:0 console=ttyS0,115200
root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
bootopts=vmalloc=496M debug=7 initcall_debug=0
graphic=video=1920x1080 drm.debug=0x7


buildargs=setenv bootargs "board=${board} ${console} root=${root} ${bootopts} ${graphic}"


checkenv=test -e ${device} ${partition} ${bpi}/${board}/${service}/${bootenv}
importenv=env import -t ${scriptaddr} ${filesize}
loadbootenv=if fatload ${device} ${partition} ${scriptaddr} ${bpi}/${board}/${service}/${bootenv};then run importenv;else echo "fatload (${bootenv}) failed";fi
resetenv=env default -a;printenv;


checksd=fatinfo ${device} 1:1
selectmmc=if run checksd; then echo Boot from SD ; setenv partition 1:1;else echo Boot from eMMC; setenv partition 0:1 ; fi;


newboot=run buildargs;printenv bootargs;fatload ${device} ${partition} ${loadaddr} ${bpi}/${board}/${service}/${kernel}; bootm

My uboot runs this to build bootargs…

Just add this to your uenv.txt (overwriting my bootargs so add its previous content):

bootopts=vmalloc=496M debug=7 initcall_debug=0 systemd.unit=rescue.target

have you Cli-access with debuguart?

cioby23 · September 30, 2019, 3:11pm

@spikerguy I might have a look today or tommorrow why the logind service is failing if you want to share the Archlinux R2 image.

spikerguy · September 30, 2019, 3:14pm

Sure. Let me make a flashable R2 ready image for you.

Yes.

frank-w · September 30, 2019, 3:29pm

Then you can see uboots menu and choose uboot-console to look if your uenv.txt is read.

spikerguy · September 30, 2019, 4:12pm

Sure. I will test this tonight. As in the log It shows Line 406, as it searches for uEnv.txt file.

Thanks. Will get back to you after trying it.

frank-w · September 30, 2019, 4:17pm

you use old/official uboot? this only loads uenv.txt on selecting the “boot from sd”-entry, not before display the menu

but for testing your case it will be enough

spikerguy · September 30, 2019, 5:09pm

I am using your 1m boot file with your 4.19 kernel boot partition.

spikerguy · September 30, 2019, 5:25pm

I tried this but no luck.

Here is the UART log.

If we read the log, I tried to login with alarm/alarm as well as root/root but Its always Authentication Failure.

frank-w · September 30, 2019, 5:25pm

mhm, afair 1M-file from my wiki/gdrive was created before uboot upstream support

spikerguy · September 30, 2019, 5:26pm

Should I use the 2019 1M file which I have extracted from your latest built? Will that make any difference?

frank-w · September 30, 2019, 5:28pm

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)

spikerguy · September 30, 2019, 5:35pm

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.

frank-w · September 30, 2019, 5:50pm

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"

?

spikerguy · September 30, 2019, 5:53pm

* 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.

frank-w · September 30, 2019, 5:54pm

not more? maybe you have to scroll…

spikerguy · September 30, 2019, 5:56pm

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.

frank-w · September 30, 2019, 5:57pm

scroll a bit to right…it’s cut off

spikerguy · September 30, 2019, 5:58pm

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'.