Hiya. new here. Bought my first rpi on friday. I have spent whole Friday’s evening trying to figure out why it would not connect to the router. Tried diff versions of software, redownloaded the rpi imager and etc… went digging through the router and etc. My pc runs on latest Mint (cinnamon). I even sent the pihole to return and ordered from another vendor. It got delivered on Saturday, around noon. Spent another 3-4 hours digging through random threads online on similar issues and etc. Nothing helped. Then, as a hail marry, I reflashed the sd card on my gf’s win11 pc and rpi connected in under a minute.
There is something clearly wrong with the linux version of the imager.
This is the Pi-hole forum.
Your issue isn't related to Pi-hole, but purely to Raspberry Pi Imager.
You should file your complaints and raise any questions you have with the Raspberry Pi developers, e.g. at GitHub: raspberrypi | rpi-imager.
A fair point and i apologise. but aren’t most piholes running on rpi’s or rockchips? this is not a complaint but a info share about possible issues to any new to this. i know for a fact that this little bit of info would have saved about 7-8 hours of my life, if somebody posted that and i saw it.
Information is of little use if hidden in an unrelated forum.
People looking for help with Raspberry Pi imager are likely to search Raspberry Pi forums, or file an issue with the developers.
And if there indeed would be an issue with the imager, the developers would be the most important people to know about it, as they are quite likely the only ones who can fix it (and you can safely assume they don't scan the Pi-hole forums for issues with their software).
i did drop the bug report on github, too. but, to repeat myself, the 2 are connected. figured i will share a bit of info. remember: searches like google, duck and etc will see this, too. meaning, higher chance somebody having same issues will come across this tidbit. if you want, you can delete this post. no offence meant, bud.
If you'd search the Raspberry Pi fourms and blogs, you'll probably would be aware that RPi Foundation changed their 1stboot configuration to cloud-init.
As a consequence, you must use the most recent RPi Imager 2 to write your SD card with current Trixie RPi OS versions and above.
Older RPi Imager versions would write configuration info that isn't understood by the current images.
Your observation could indicate that you probably used an older version of Raspberry Pi imager with the most current image.
Linux Mint may have contributed to this, if you'd opted to install RPi Imager via Mint's software manager or packet manager, and if those would still pull a pre-2.0 version.
But those details should be discussed with the folks at Raspberry Pi (and perhaps Linux Mint's package maintainers).
It's quite possible that the Raspberry Pi documentation would need an update to contain an explicit and prominent warning regarding Imager versions - and that would be the Raspberry Pi folks job.
well, i did download the imager from RPI website the day the zero2w was delivered to me. well, copy-pasted “sudo apt install rpi-imager” to install the imager and imager, I BELIEVE, will connect to their own or trusted sources.
That method is only recommended for RPi OS:
On Linux Mint, this would indeed have pulled an older version, probably 1.8.5, judging by one of the comments on the Linux Mint software info:
Out of date, the new pi os breaks the custom boot settings on the current version (1.8.5)
That version can't configure the most current RPi OS images correctly.
You should have used the download from Raspberry Pi software.
just double-checked. one i have on linux is 1.8.5
There you go.
So this is more of a Linux Mint issue than an RPi Imager one.
Possibly, Linux Mint software/package maintainers may be aware of it, as the package now seems to have been withdrawn from their repo:
(I'm running LMDE on one of my machines.)
~$ sudo apt-cache policy rpi-imager
N: Unable to locate package rpi-imager
1 Like
oh, sweet! thanks, bud! i guess, it was just wrong time for me to try it, then 
sigh
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.