-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Unlocking radios on RPI with a dedicated service #8210
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
Conversation
WalkthroughTwo new functions were added to the bcm2711 family configuration. The first function clones a Raspberry Pi firmware repository into the target root filesystem under Suggested labels
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
config/sources/families/bcm2711.conf (1)
258-276
: Implementation looks good with a simple and effective approach.This is a clean solution to unblock rfkill devices without requiring the rfkill binary. The systemd service is well-structured with appropriate timing (after multi-user.target) and type (oneshot with RemainAfterExit=true).
Consider adding a brief comment at the top of the function explaining the specific issue this addresses (rfblock enabled by default on boot for certain RPI models like Zero 2 W), which would help future maintainers understand the rationale.
function pre_install_distribution_specific__unblock_rfkill() { + # Raspberry Pi Zero 2 W and potentially other models have rfkill block enabled + # by default at boot, which prevents wireless functionality from working # Create a systemd service to unblock rfkill cat > "${SDCARD}/etc/systemd/system/unblock-rfkill.service" <<- EOT
Tested twice, working. |
Description
While doing last prerelease testing I tried booting on Zero2W, which only has wireless connection. I could not enable connection because rfblock comes up enabled, thus nothing wireless wise works.
Adding a systemd service that ublock it without adding additional dependency rfkill.
Does it make sense to make this OS wide?
Checklist: