| Age | Commit message (Collapse) | Author |
|
Kernel 6.18 moved Intel BE200/BE-series (Wi-Fi 7) devices to the new
iwlmld op-mode driver: their dev_info entries in iwlwifi's pcie/drv.c
are guarded by IS_ENABLED(CONFIG_IWLMLD). The VyOS kernel config enables
IWLWIFI/IWLDVM/IWLMVM but not IWLMLD, so BE-series support is compiled
out and probing fails with error -22 (no wlan interface is created).
Enable IWLMLD as a module on x86 and arm64, matching the existing
IWLDVM/IWLMVM op-modes. The firmware these devices need is already
shipped by the linux-firmware package.
|
|
Update the accel-ppp-ng version to 9654bb6
Includes fixes for T8391
(Bonding interface permission errors with custom ethernet MTU)
|
|
Convert build-nat-rtsp.sh, build-ipt-netflow.sh, build-intel-nic.sh,
build-intel-qat.sh and build-linux-firmware.sh from fpm to debmake +
debuild, matching the jool/realtek packaging style.
|
|
build-kernel.sh parsed kernel_flavor out of defaults.toml itself via a
brittle awk one-liner, even though build.py already has that value from
its own defaults.toml read.
Pass kernel_flavor down as an env var instead, so defaults.toml is read
in exactly one place (build.py's main) and everything downstream flows
through kernel-vars or explicit parameters.
|
|
Rewrite build-jool.py, build-realtek-r8126.py and build-realtek-r8152.py
as build-*.sh, matching the Bash convention already used by every other
sub-dependency script in this directory (kernel-vars sourcing, debmake +
debuild packaging).
|
|
Accel-PPP-ng only links against a few VPP libraries, but the build triggered
a full VPP package rebuild (make pkg-deb) on every run, with no caching.
Skip that step when the required VPP libraries already exist from a
previous run.
Delete them to force a rebuild.
|
|
Commit 21c7e661 ("Kernel: T5641: enable module compression to save disk
space") which enabled module compression using XZ missed that when we search
modules for firmware inclusion, the pattern was hardcoded to *.ko instead of
*.ko* - this has been fixed.
|
|
Package update required in lockstep mode to add support for renaming podman
macvlan interfaces.
|
|
T9147: Bump accel-ppp-ng version to 9874ea3
|
|
Upgrade rolling release Kernel version.
Changelogs:
* 6.18.41 https://lwn.net/Articles/1086227/
* 6.18.40 https://lwn.net/Articles/1084923/
* 6.18.39 https://lwn.net/Articles/1083464/
|
|
This version includes a fix for
T8391: Bonding interface permission errors with custom Ethernet MTU
|
|
|
|
|
|
Kernel: T9103: fix arm64 syscalltbl path breaking linux-perf package build
|
|
Building linux-perf-* on a native arm64 build host failed with "No rule to
make target '.../unistd_64.h'" because arch/arm64/kernel/Makefile.syscalls
overrides syscalltbl with a path relative to the kernel root, but
tools/lib/perf/Makefile invokes the header generator from tools/lib/perf/
instead. Make the override absolute, matching the srctree-prefixed default.
|
|
Kernel: T8868: Enable crash dump (kdump) and debug info in config
|
|
openssl: T9083: fix APT detected package downgrade despite identical versions
|
|
VyOS rolling APT repo (packages.vyos.net/repositories/rolling) publishing its
own openssl/libssl3 packages, pinned at priority 600 (higher than Debian's 500)
causes a "poisoning" of the APT cache policy inside the chroot:
openssl:
Installed: 3.0.20-1~deb12u2
Candidate: 3.0.20-1~deb12u2
Version table:
* 3.0.20-1~deb12u2 500 <- debian bookworm + bookworm-security
* 3.0.20-1~deb12u2 600 <- packages.vyos.net rolling (same version string, higher pin)
* 3.0.17-1~deb12u2 500 <- bookworm-updates
This results in APT seeing a version-string tie between Debian's build and the
VyOS repo build of the same package and, because of the pin-priority swap,
classifies switching to the VyOS repo copy as a "downgrade".
This is fixed by appending a clear VyOS related marked to the package version,
preventing any possible downgrade detection.
Signed-off-by: Date Huang <tjjh89017@hotmail.com>
Co-authored-by: Christian Breunig <christian@breunig.cc>
|
|
Kernel: T5641: enable module compression to save disk space
|
|
Enabling the following options allows us to use `kdump-tools`:
- `CONFIG_CRASH_DUMP`
- `CONFIG_DEBUG_INFO`
- `CONFIG_PROC_VMCORE`
|
|
Kernel: T9067: Update Linux Kernel to 6.18.38
|
|
Option useful during development to not automatically clean the Linux Kernel
source folder of all its intermediate files.
|
|
After signing the Linux Kernel modules with the ephemeral key, proceed
by compressing the Kernel modules with xz to reduce the final ISO image
size.
Initial tests have shown a size reduction by 60MiB.
|
|
|
|
|
|
|
|
|
|
T9040: Build FIPS-provider OpenSSL version
|
|
Build FIPS-compatible OpenSSL binaries
The FIPS provider does not get built and installed automatically.
To enable it, you need to configure OpenSSL using the `enable-fips` option.
|
|
for the fix for legacy hash algorithm loading
to make MS-CHAP work correctly again
|
|
podman: T9024: package upgrade from v4.9.5 to v5.8.4
|
|
This updates the used Podman version from 4.9.5 to 5.8.4 which is a major bump.
For this update to work on Vyos we also do need to switch from crun to runc, as
the Debian Bookworm provided version of crun is not working with podman 5.8.4.
Building crun from Debian trixie package sources does not work due to missing
build time dependencies.
|
|
Kernel: T8914: add support for 2.5G pluggables on BCM57810S
|
|
Kernel: T8605: net/l2tp: allow unmanaged tunnel setup without route to peer
|
|
Add the well-known JAMESMTL kernel module patch for bnx2x to advertise 2.5Gbit/s
capabilities on Broadcom NetXtreme2-X cards with BCM57810S chipset.
This is useful for ISP GPON access networks that use 2.5Gbit/s pluggables and
need the NIC to negotiate beyond 1000baseT/Full, avoiding the 940Mbit/s
practical cap on overprovisioned 1G services.
References:
* https://hack-gpon.org/broadcom-57810s/
* https://github.com/JAMESMTL/snippets/blob/dceb2fee74d80c66d/bnx2x/patches/bnx2x_warpcore_8727_2_5g_sgmii_txfault.patch
|
|
|
|
T9013: Add FRR patch to fix BMP connect source-interface deletion
|
|
T9010: Update Linux Kernel to 6.18.36 and re-fresh Intel OOT driver versions
|
|
|
|
T8599: Make source packages required and fix them
|
|
|
|
Update versions:
* igb v5.20.28
* ixgbe v6.4.4
* ixgbevf v5.3.36
* i40e v2.30.18
* ice v2.6.6
* iavf v4.13.35
|
|
T8099: Update strongswan to 6.0.6
|
|
1.0 source format version needs tarball without '.orig' suffix as described in https://www.man7.org/linux/man-pages/man1/dpkg-source.1.html.
Only if debian/source/format exists and contains 3.0, use '.orig'
|
|
Patch modifies debian/control and debian/rules, there is no easy way to
fix source package creation in such case. As quick solution disable
source package build for this package (previously it failed silently)
|
|
Exit with error for other failures:
* Creating/installing dependency package should be error: e.g. debugging
why strongswan cannot find systemd could be easier if build.py failed
when it couldn't install systemd and not when `configure` couldn't
find it.
* Creating tarball
* pre_hook run
|
|
A lot of packages failed to build source package.
Stop ignoring source package build errors and fix it.
To fix source packages:
* Use <source_package>_<upstream_version>.orig.tar.gz naming for source
archive.
* Get `source_package` and `upstream_version` from changelog using
dpkg-parsechangelog utility
* Clean build-deps after usage or dpkg-source sees these files as
changes relative to upstream.
* Add '.github' to --diff-ignore source option
|
|
|
|
|
|
salt: T8973: remove package build due to feature removal
|