-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Bring back Raspi SD card image build #699
Comments
Hi Maybe when the long-promised cloud-init finally appears, I will come back to this issue, but currently it is only talked about. |
OK, I tested it and the workaround seems to work. https://downloads.raspberrypi.org/raspios_lite_arm64/images/raspios_lite_arm64-2023-05-03/2023-05-03-raspios-bullseye-arm64-lite.img.xz They are based on Debian Bullseye, the old Wi-Fi configuration still works (wpa_supplicant), you can use any image flasher and when building "apt install --only-upgrade udev -y" is performed, so the critical udev bug for serial port devices is gone. |
SD images were included in the latest v20beta2 release |
Feature request
What problem does this feature solve?
Deprecating RaspberryPi OS (SD card image installation) might not be necessary anymore? It seems you can download the image separate from Imager now.
https://www.raspberrypi.com/software/operating-systems/
There's a couple other solutions here for wifi config: https://raspberrypi.stackexchange.com/questions/144850/headless-wi-fi-setup-without-the-rpi-imager-bootfs-wpa-supplicant-conf-not-supp
Though that might not be worth the effort to chase. Perhaps we could just require ethernet at first to SSH and run NetworkManager?
What does the proposed API look like?
n/a
How should this be implemented in your opinion?
I would say try to replicate the old build configs as much as possible, to not waste time.
Are you willing to work on this yourself?
I'd be happy to help with documentation! I'd be more comfortable committing after I've familiarized myself with this project a little more.
The text was updated successfully, but these errors were encountered: