Hi. Just to make things clear. My reason for trying this is I am visually impaired.

I am writing some code to run on a pi zero 2. With a small 5 inch screen. IE the code interface is being designed to display very clear large buttons on a small screen.

To set up the OS build, I am trying to create a Qemu emulator on my large screened home desktop. So I can actually read code file system etc in large print. Once I have the OS set up and can install a lite image with very minimal xwindows / tkinter support. I can then use SsH etc to work on the GPIo stuff.

My issue is I have no experience with QEMU. I am having issues finding any online guide using recent versions of QemuEtc (preferably not video as watching code/CLI on YouTube is just undoable with vision issue's.)

If anyone can help with a guide on how to set up qemu_system_aarch64 for raspi2ap

IE what exactly I need to do to provide a -kernal and IMG etc to build a image. I'd be very grateful.

I'm posting here hoping you guys will have some experience. But please let me know if somewhere else would be better.

My desktop is running Debian bookworm with a back ports version of QEMU.

Follow up of my post from earlier this month in case someone needs in the future:

Got myself a Pi5, flashed KonstaKANG's AOSP 16 fork, and installed the "universal" APK of Grayjay.

Tested some 10 or so videos, and so far, been working pretty much the same as on phone, including third party plugins.

Only exception I observed is that it's stuck in landscape mode, and I expect (yet to test) that it stays like that until I use some program to force the screen to rotate.

OC by @shiroininja@lemmy.world

I'm running octopi on an rpi zero 2 w it had been working flawlessly for weeks until I unplugged it to move the printer. Now it won't connect to Wi-Fi sometimes. If I connect a monitor it will connect. If I connect the monitor after booting it has no network IP address just the 127... Local address. I've gotten it to connect one time without a monitor but it was in the wrong location. I thought it might be proximity related, and it still could be, but that doesn't explain why it doesn't always connect near my Wi-Fi access point where it was working before. I've tried multiple other power supplies and with the printer both turned on and disconnected.

I guess using LVM on an old raspberry pi 3B+ was not the smartest idea :/ ! As expected the pi 3b+ can handle qbittorrent and piHole without to much load average...

After switching from LVM+EXT4 to a single EXT4 partition, I can download, check file integrity and resolve DNS at the same time without my dns resolution hanging !

Solution:

• Install piHoleOS on a simpler filesystem without LVM (ext4)
• Take qbittorrent out of docker and install it barebone on the device (qbittorrent-nox)

Hello :))

I'm relatively new to the pi and all the ecosystem (ARM, SBC...) and I'm kinda intrigued on what's happening here if someone has some info to share.

I generally work on debian for my server stuff but found an old never used RPi 3B+ in one of my boxes. Installed RPi OS lite based on debian bookworm and docker with the pihole container as DNS server for my home network.

Works great and does hold all my DNS requests without issues. However, yesterday I migrated my qbittorrent stuff (mostly linux ISO 😅) on the RPi, on an external HDD over USB.

While uploading works fine without issues for +/- 100 torrent files, when downloading OR checking the files integrity the RPi is chocking really hard making the DNS request slowdown and even unresponsive...

I did some search and from my findings the USB is a hard bottleneck for file transfer on the pi 3b+ and qbittorrent in a container adds alot of overheat too, so I checked and moved everything out of the container and installed qbittorrent-nox which does improve the situation but it still makes the DNS request on pihole impossible when downloading or checking file integrity.

I this some kind of bug, known issue? RPi is cool stuff but If it can't hold or stand a medium hungry service, that's kinda a bummer... It's not doing that much of work, It's just resolving DNS and downloading a file over the torrent protocol.

Somone similar issue, observation, insight or solution? Or is the pi not meant to hold a torrenting service?

Does it work on a Pi5 running systems like the Raspbian/Raspberry Pi OS or KonstaKANG's LineageOS?

Don't have the device (yet?), but Grayjay would be one of the main uses for it for me, so concerned I might be wasting money, thus asking if anyone would know.

I have a pile of hard drives sitting around that need to be securely wiped. Does anyone know of something similar to DBAN or ShredOS for ARM that I can use to turn a Pi into a disk wipe station? It doesn't need to be a dedicated OS, just a package that I can run on top of armbian or whatever.