Yes, the file is https://downloads.raspberrypi.com/raspi ... ite.img.xz
I found what that the issues are...
So, I'm modifying both the boot and os partitions using some script so that I can create a fully headless deployment of the devices.
As I've been using this since before custom.toml (and not only with Raspberry OS) some leftovers were simply ignored on previous versions, but seem to be an issue now.
The file "/etc/defaults/keyboard" needs to have a valid configuration on this last release, or it will break several things. I had a know bug there that I had to fix.
The country code for the Wi-Fi network could be empty before, it needs to be set now. I'm using "BR" here, but it should work with most country codes out there.
What really struck me is that if, in your "custom.toml" file, you use something like:
you will get some services to fail on the first boot (Avahi, systemd-logind, and others) and NetworkManager does not start, and if you reboot the device, things get better, and everything starts fine, but you still get "Wi-Fi is currently blocked by rfkill".
I'm sorry, but I didn't have time (yet) to look into the first boot failures. I may be able to do that in the weekend.
As far as I can see, the configuration on this latest version is much more strict, leaving little room for "I'll fix it later".
If you want, I can look further into the issues I had without the Wi-Fi country code, but for my case, I consider the issue fixed.
It would be nice to have some more easily found information on these kind of changes, specially since we don't have semantic versioning on the releases.
I found what that the issues are...
So, I'm modifying both the boot and os partitions using some script so that I can create a fully headless deployment of the devices.
As I've been using this since before custom.toml (and not only with Raspberry OS) some leftovers were simply ignored on previous versions, but seem to be an issue now.
The file "/etc/defaults/keyboard" needs to have a valid configuration on this last release, or it will break several things. I had a know bug there that I had to fix.
The country code for the Wi-Fi network could be empty before, it needs to be set now. I'm using "BR" here, but it should work with most country codes out there.
What really struck me is that if, in your "custom.toml" file, you use something like:
Code:
[wlan]ssid="homenet_24G"password = "CLEAR_PASS"password_encrypted = falsehidden = falsecountry = ""I'm sorry, but I didn't have time (yet) to look into the first boot failures. I may be able to do that in the weekend.
As far as I can see, the configuration on this latest version is much more strict, leaving little room for "I'll fix it later".
If you want, I can look further into the issues I had without the Wi-Fi country code, but for my case, I consider the issue fixed.
It would be nice to have some more easily found information on these kind of changes, specially since we don't have semantic versioning on the releases.
Statistics: Posted by rafasgj — Thu Nov 28, 2024 9:43 pm
