Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Prepare 12.4 #3422

Merged
merged 28 commits into from
Jun 18, 2024
Merged

Prepare 12.4 #3422

merged 28 commits into from
Jun 18, 2024

Conversation

sairon
Copy link
Member

@sairon sairon commented Jun 18, 2024

sairon and others added 28 commits April 26, 2024 11:59
@sairon
Bump OS to development version 12.4.dev0
21fd9e6
@sairon
Enable KVM for running tests in GH Actions (#3329)
4e44b10 
It was not possible on free runners previously, but it should be now:
actions/runner-images#7191 (comment)
@sairon
Enable kernel userspace crypto API interface for all platforms (#3330)
67315f8 
Enable libkcapi in generic kernel config. The bloat is minimal and the
options are enabled on most distributions. These modules are also needed
for Bluetooth Mesh and adding them fixes compatibility with some HCI USB
adapters.

Fixes #3322
@sairon
Linux: Update kernel to 6.6.29 (#3334)
65f35c6 
* https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.29
@sairon
Fix incorrect mapping of DT overlays on RPi 5 (#3335)
fce19b7 
RPi 5 config uses BR2_LINUX_KERNEL_INSTALL_INTREE_OVERLAYS which builds
the device tree overlays from the Linux tree when building the kernel.
The overlays directory also contains overlay_map.dtb which is necessary
to correctly map overlays without RPi version suffix to the
platform-specific ones. Without this, some peripherals may not work
correctly on Pi 5 without any obvious error messages in the kernel log
because an incorrect (Pi 4) overlay is used as the default.

Fixes #3321

* buildroot cc0481f40e...0a64bfe8f1 (1):
  > Install overlay_map.dtb when using in-tree DT overlays
@sairon
RaspberryPi: Update kernel to 6.6.28 - stable_20240423 (#3336)
9fa9537 
* RaspberryPi: Update kernel to 6.6.28 - stable_20240423

* Bump buildroot to update rpi-firmware

* buildroot 0a64bfe8f1...e8948ce36e (1):
  > package/rpi-firmware: bump to version 1.20240424 for kernel 6.6.28
@agners
Enable grep context feature (#3339)
2c266c5 
Add context feature to Busybox grep configuration. Context is really useful
when checking host logs directly on the OS shell.
@sairon
Linux: Update kernel to 6.6.30 (#3342)
ca71774 
* https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.30
@sairon
Merge branch 'main' into dev
229cc7e
@sairon
Bump buildroot to update openvmtools to 12.3.0 (again) (#3370)
dd96b50 
Cherry-picked downstream-only patch lost in Buildroot 2024.02 bump.

* buildroot 34e790c5da...9af2384782 (1):
  > package/openvmtools: bump version to 12.3.0

Fixes #3366
@sairon
Use U-Boot tarball for all boards (#3361)
8aa9869 
ODROID M1, M1S and Green historically used git repo as the source. Now
that we use the same version for all boards, use always use distribution
tarball for consistency and more efficient caching.
@sairon
Linux: Update kernel to 6.6.31 (#3384)
8dbc03c 
* Linux: Update kernel to 6.6.31

* https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.31

* Update patch workarounding Z-Wave.me USB issues

Linux commit 480c3abbba36628dab063b9ca218bb28090e5b46 changed code that
is reverted by the patch. Use a version-specific patch directory again
for upstream Linux patches before RPi kernel is updated to 6.6.31+.
@sairon
Reintroduce IPv6 reachability probe patch for RPi lost after refactor…
2c725d9 
…ing (#3389)

* Reintroduce IPv6 reachability probe patch for RPi lost after refactoring

In #3384 we moved the patches around, which results in version-specific
patches not applied for RPi linux-custom build. Copy the missing IPv6
reachability probe patch to the RPi patches directory.

* Only copy IPv6 reachability probe patch to top-level linux patches

Instead of copying the patch to RPi directory and renumbering the
patches, only copy it upper level so it's applied for all linux versions
other than 6.6.31.
@sairon
Linux: Update kernel to 6.6.32 (#3394)
682d594 
* https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.32
@dependabot
Bump docker/login-action from 3.1.0 to 3.2.0 (#3399)
5ed9057 
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@sairon
RaspberryPi: Update kernel to 6.6.31 - stable_20240529 (#3400)
bd7474f 
* RaspberryPi: Update kernel to 6.6.31 - stable_20240529

* Unify Linux patches after RPi update to non-conflicting 6.6.31

* Bump buildroot to update rpi-firmware

* buildroot 9af2384782...691077e577 (1):
  > package/rpi-firmware: bump to version 1.20240529 for kernel 6.6.31
@sairon
Set tty0 in cmdline as the default preferred console (#3402)
22b63ae 
The preferred console (which is used for printing the systemd boot log)
is the last one specified in the cmdline boot arguments. Make sure it is
always tty0, i.e. the first graphical console.

In some places tty1 was used - change it to tty0 which is commonly used,
and in HAOS points to tty1 anyway.

The only exception is the Yellow, which doesn't have an HDMI port, so
the serial console is used as the preferred one instead.

For ASUS Tinker, use a versioned cmdline.txt file instead of in-place
generating it in the post-build hook.
@sairon
Use Genimage for declarative image layout (#3388)
6135ecd 
* Use Genimage for declarative image layout instead of s[fg]disk and dd

* Change partition type to hybrid for M1, M1S and Green

This is what it really is, so just make sure only one "fix" function is
called.

* Change efi BOOT_SYS to gpt

There is no reason to have separate efi and boot sys, since all boards
that use efi also use grub as the loader.

* Change BOOT_SYS to more explanatory PARTITION_TABLE_TYPE

* Add units to DISK_SIZE

* Add forced-primary patch and use it in MBR images

* Avoid disabling SC2155, remove old comments
@dependabot
Bump docker/build-push-action from 5.3.0 to 5.4.0 (#3405)
ae588b7 
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@sairon
Update Buildroot to 2024.02.3 (#3406)
542f69e 
* Bump buildroot to 2024.02.3

* buildroot 691077e577...770f939463 (1):
  > Merge tag '2024.02.3' into 2024.02.x-haos

* package/hassio: update dind to version 26.0 used in current buildroot
@sairon
Fix linux-firmware compression after BR 2024.02.3 merge (#3407)
26f0b5a 
The compression is necessary for successful generic-x86-64 build.

* buildroot 770f939463...b9520eedc6 (1):
  > package/linux-firmware: fix compression after bad merge
@sairon
Temporary revert ODROID-N2 U-Boot to 2023.01 to fix eMMC issues (#3409)
6d77355 
As we don't have proper solution for #3319 and #3351 yet, revert to
previous U-Boot which was proven working. This is intended as a
workaround but as there's nothing in the latest U-Boot that will be
really missed on N2, we can stay on the older version for the time
being.

This also means reverting the "40 MHz hack" back to the 24 MHz one.
Since this patch only applies to N2 (meson gx), it can stay along the
common hardkernel uboot patches.
@sairon
Fix writing to eMMC in U-Boot on Green (#3412)
8953375 
When Green starts, there is an error indicating the MMC write failed when
saving the bootstate:

  storing env...

  MMC write: dev # 0, block # 1214464, count 64 ... mmc write failed 0 blocks written: ERROR

This results in the boot count not being updated properly if the boot fails.

Seems to be a known issue for this platform, disabling the DDR52 mode (which is
the same what upstream does for other RK356x boards [1]) fixes the issues and
the bootstate is updated correctly.

[1] https://patchwork.ozlabs.org/project/uboot/patch/20240204205312.2342868-2-jonas@kwiboo.se/
@sairon
Add hardware details to bug issue template (#3413)
d847b98 
Very often we have to ask for further details about the hardware that HAOS is
running on. Add a required field that asks for these details - in the end it
should't complicate the form a lot and might result in faster turnaround of
resolving the issues.

Also adjust the question about the upgrade and swap the order (people often
don't care and keep the pre-selected value).
@sairon
Bump Docker to v26.1.4 (#3411)
6c2d5b5 
* buildroot b9520eedc6...ad5e711bc1 (4):
  > package/containerd: bump to v1.7.17
  > package/docker-cli: bump version to v26.1.4
  > package/docker-engine: bump version to v26.1.4
  > .github: remove upstream's PR template discouraging GH usage
@sairon
Linux: Update kernel to 6.6.33 (#3415)
27bc730 
* https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.33
@sairon
Bump OS to pre-release version 12.4.rc1
0e9e8ca
@sairon
Bump OS to release version 12.4
a70ed7e
@sairon sairon requested a review from agners June 18, 2024 10:28
@sairon sairon merged commit a70ed7e into main Jun 18, 2024
2 checks passed
@sairon sairon deleted the prepare-12.4 branch June 18, 2024 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@agners agners agners approved these changes

Assignees
No one assigned
Labels
cla-signed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@sairon @agners