-
Notifications
You must be signed in to change notification settings - Fork 972
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
Prepare 12.3.rc1 #3327
Merged
Merged
Prepare 12.3.rc1 #3327
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Booting from a ADATA SD600Q fails when connected to a USB 3.0 port on RPi4. Adding it to the quirks list resolves the issue.
Bump DinD version used for creating data partition after Docker bump in #3271.
CP15 barrier instruction emulation only exists on arm64 architecture. Avoid sysctl writing an error to the journal when the setting doesn't exist by prepending a dash.
This should have been included in #3288.
* Only run HA CLI interactively if stdout is a terminal Flags for running HA CLI commands in an interactive shell added in #3238 cause the command to fail if the process is not running in a terminal. This is needed for example for the fsfreeze hook, otherwise the command fails, as seen in this trace when the hook is executed: ----------- + '[' thaw '=' freeze ] + '[' thaw '=' thaw ] + echo 'File system thaw requested, thawing Home Assistant' File system thaw requested, thawing Home Assistant + ha backups thaw the input device is not a TTY ------------ However, for example on Proxmox this message is not logged anywhere and the hook just fails silently (i.e. it doesn't cause the backup to fail). Fixes #3251 * Use -i also when not running in a terminal
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 3.2.0 to 3.3.0. - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](docker/setup-buildx-action@v3.2.0...v3.3.0) --- updated-dependencies: - dependency-name: docker/setup-buildx-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* RaspberryPi: Update kernel to 6.6.20 - 6f16847710cc0502450788b9f12f0a14d3429668 Used version specified in RPi OS release notes [1]. [1] https://downloads.raspberrypi.org/raspios_arm64/release_notes.txt * Update RPi Buildroot defconfigs for v6.6.y kernel * Update RPi kernel patches for v6.6.y kernel * Amended old patches to accomodate for new DTS paths * Removed 6.6.25 patches -> moved to the common folder * Added patch to fix Yellow DTS compilation * Bump buildroot to update rpi-firmware * buildroot b45d671fe3...9f5750121a (1): > package/rpi-firmware: bump to version for (untagged) kernel v6.6.20 * Remove kernel v6.1.y config fragments, as they're not needed anymore
BT_HS has been removed in e7b02296fb400ee64822fbdd81a0718449066333 and backported to stable branches - remove it from our configs to avoid warnings.
Make sure all Raspberry Pi devices using the BCM2837 SoC (or the SiP version RP3A0 of it) are deployed. This especially makes sure that we only deploy the downstream device trees (named bcm2710*) and deploy device trees for the CM3 as well as the Zero 2 and Zero 2 W consistently for 32-bit and 64-bit.
It seems that forcing 24MHz clocks is problematic for newer 32GB Kingston based eMMC modules on ODROID-N2(+). Use what downstream U-Boot is using as f_max, which is 40MHz. Fixes: #3227
) GRUB 2.12 release contains a change of the loader [1] used for loading the kernel on x86_64 platform. This change was identified to cause boot failure on some old Intel Atom boards with the NM10 chipset, and possibly some others. Revert this patch before we get a more proper fix for the issue. [1] https://git.savannah.gnu.org/cgit/grub.git/commit/?id=cfbfae1aef0694b416aa199291cfef7596cdfc20 Fixes #3305
This fixes "Warning: your password will expire in 0 days." message shown on tty login since Buildroot bump in HAOS 12.2. * buildroot 9f5750121a...d29893dd98 (1): > package/linux-pam: bump to version 1.6.1
* buildroot 9a506c0e75...cc0481f40e (1): > package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.75
agners
approved these changes
Apr 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.