Update docs #2216
Update docs #2216
Conversation
add "Workaround for network related features on bookworm"
harmonize and update description / message
AlvinSchiller
requested review from
pabera and
s-martin
and removed request for
pabera
Co-authored-by: s-martin <[email protected]>
Pull Request Test Coverage Report for Build 7638766854Warning: This coverage report may be inaccurate.We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
💛 - Coveralls |
| <details> | ||
| With Bookworm the network settings have changed. Now "NetworkManager" is used instead of "dhcpcd". | ||
| This breaks breaks network related features like "Static IP", "Wifi Setup" and "Autohotspot". | ||
| Before running the installation, the network config has to be changed via raspi-config, to use the "old" dhcpcd network settings. |
There was a problem hiding this comment.
If we refer to use Bullseye, this is not a problem anymore.
Meanwhile, can't we just automate this instead of describing it here, potentially loosing builders along the way? We could silently change the raspi-config in the installation, most builders won't care. It's a save convention to define.
There was a problem hiding this comment.
We could keep this docs for reference on Bookworm, but it'll be less of a pain for most builders.
There was a problem hiding this comment.
Our current installation instruction dont mention a specific version (the default will be select be RPI Imager), but i think more and more will use the newer Bookworm, and running into this.
A quickfix in the installation is not possible, as a change of the setting will instantly reset the network and the user will lose access to the device, if it has a wifi connection.
I address the problem, with #2184 to have both ways working.
So this is just a temporary documentation apart from the Issue and notes in the Release till the implementation is finished ( in case it will not be ready for 3.5.0 ).
moved to components
documentation/builders/README.md
Outdated
| @@ -19,6 +18,8 @@ | |||
| * [OnOff SHIM for safe power on/off](./components/power/onoff-shim.md) | |||
| * [Soundcards](./components/soundcards/) | |||
| * [HiFiBerry Boards](./components/soundcards/hifiberry.md) | |||
| * [Synchronisation](./components/synchronisation/) | |||
There was a problem hiding this comment.
Is it ok to add all components here, or do we need to split this for hardware and software implementations?
There was a problem hiding this comment.
For better readability, I would split that.
There was a problem hiding this comment.
As soon as this list grows, we can slit it. I like the idea
There was a problem hiding this comment.
How about splitting it now and restructure a bit.
In my opinion its not really clear what the different headers mean (config, components, advanced).
Idea for restructuring:
Additionally i would suggest to add the rfid reader docs for supported readers. Maybe even move to builder space (except mock and template)?
Co-authored-by: s-martin <[email protected]>
Network Settings in Bookworm on future3 #2184
future3 | Install on 64bit not working (Wrong OS type) #2041