I was able to fix the /sbin/init issue, which was separate. I got
./m5term going and that helped me resolve the issue (such a useful tool—I’m
glad I know about it now). Thank you!
On Mon, Oct 18, 2021 at 3:25 PM Reiko Matsuda-dunn <
reiko.matsudad...@colorado.edu> wrote:
> Thanks Jason! I'm
Thanks Jason! I'm trying ./m5term and running the following build command:
$build/ARM/gem5.opt --outdir=run/pop2_s configs/fs_ARM.py
--checkpoint-dir=checkpoint/pop2_s -r 1
--disk-image=../m5_binaries/disks/gem5.img
--kernel=../m5_binaries/binaries/vmlinux.arm64 --mem-size=4GB
Hi Reiko,
I would guess that it's a permission issue as well. Maybe, by default, when
booting the image it logs in as a regular user?
What I would do is not pass the rcS script and log in interactively with
the m5term (see util/term). Then, run the commands in the rcS file one at a
time manually
