-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notes for native-emulation on Arch Linux #118
Comments
@jchidley : Thank you !! That's very useful info. Would you like to create a wiki post on how to emulate rpi-arch / do you mind if I add the posted info in a wiki post ? |
You have my permission to reuse what I wrote in this issue, above. If I were you, I would test the commands to be sure that a syntax error hasn’t crept in. I am glad that you found it helpful. |
Thank you !! I will double check the instructions before publishing it under wiki. |
I was able to use the raw image directly without the limitation by replacing |
Update: I tried to boot the 2022-09-22-bullseye-arm64 image, in my above comment the lite version, now I also tried the regular version with GUI and again, QEMU captures input devices but no input is recognized on the pi |
Thanks for doing this. I had to make some adjustments to get the native emulation to work on Arch Linux.
For Arch, packages
qemu
andqemu-arch-extra
are required.After unzipping the Raspbian download to a img file, I needed to use
fdisk -u sectors -l ../Downloads/2020-08-20-raspios-buster-armhf-lite.img
to work out the correct options to setup a loop device. This showed that the first partition's Start (in sectors) was 8192 and Sectors was 524288. So the offset in bytes will be 8192 * 512 and the sizelimit 524288 * 512Because
qemu-system-aarch64
kept complaining that the image was in the raw format, and I couldn't work how to specify the format for the-sd
option, I converted the raspbian image from a raw format to the qcow2 one usingFinally, my modified command to start the image was:
The text was updated successfully, but these errors were encountered: