in_symathyDo you like the new Raspberry Pi Imager 2? (https://github.com/raspberrypi/rpi-imager)
Yes - it's awesome
No - 1.9.x was better
Haven't tried it yet
Other - comment below
Poll ended at .
cyclical_obsessiveScary - you are pushing the new rpi-imager that is reported to brick SDcards in certain cases on Linux and MacOS.
There is version 2.0.2 due but not available yet, so Linux and MacOS folks should probably stick with 1.9 for a bit longer.
@cyclical_obsessive hey, thanks for sharing. Actually 2.0.2 with fixes for those issues is available on GitHub for all platforms in Releases section. But personally I like 1.9.x workflow much more and I was wondering if it’s just me 🤷🏻♂️
@in_sympathy
> Releases section GitHub
Google found me the releases - thanks.
Interested to see if the headless setup is anymore reliable.
With 1.7-1.9 my headless setups were not always successful the first (or even second) try. I was never able to diagnose the issue, and always had a keyboard, display handy to finish the job (albeit frustrated with the imager).
I saw hints the new imager uses a different setup technique, (vs a run once script)
Chris Burton@in_sympathy IMHO the only reason to try it right now is to configure the latest Trixie release they switched to cloud-init which 1.9.x doesn't support. But using the previous Trixie release with 1.9.x is probably a better option 😇.
Vitex@in_sympathy it was impossible to build my own x86 debian trixie package :( so im using appimage now
Alistair BuxtonThe way it was released was terrible. The switch to cloud init was announced three days after it happened. New images don't work on the old imager and vice versa, even though the release announcement says they are supposed to.
The switch to cloud init itself is very good, but mainly because it means I don't have to use imager at all.
The new UI has the potential to be better but still has too many annoying bugs for me to call it "good".
@ali1234 honestly I just don’t like the new flow - I really appreciated the way 1.9.x allowed me to just immediately jump to the step I wanted to alter without having to make all the previous steps.
Even more so - I now feel that RPi-imager was on the path to become a go-to tool for the masses to flash any images to any flash drives and cards. You still can flash custom images, but it’s way more cumbersome now on 2.0.x sadly
This is true, but the old one was also bad because you had to click the write button before it even showed you the customization workflow.
Also not the first time they've incorrectly determined the device size. I reported the same bug (using stat() on a block device) against the old imager, although it was not harmful at the time: https://github.com/raspberrypi/rpi-imager/issues/902#issuecomment-2272184702
> 2.0.2 rpi-imager (macOS)
Hiding server versions under "Other Raspberry Pi OS" was unexpected but understandable.
Moving customization to the normal flow, (rather than under Edit Configuration) button is good IMO - (hopefully it remembers the answers for the next time through, I don't need to change them all, only the hostname usually.)
I've never tried raspberry connect. The signup and auth key transfer into the running rpi-imager worked great.
No objections, so far, to v2
bls@in_sympathy Use https://github.com/gitbls/sdm ! Fast, does exactly what you ask it to, and nothing more.
@in_sympathy
> Do You Like It better than 1.9?
Maybe, but it just set the hostname to "raspberrypi" when my customization requested "birdpi".
I went back and confirmed, it does save the customizations from the prior run and indeed it is "birdpi", so guess I have to submit an issue (if someone else hasn't beat me to it)