<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-build.git/scripts/package-build/linux-kernel/config, branch rolling</title>
<subtitle>VyOS image build scripts (mirror of https://github.com/vyos/vyos-build.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-build.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-build.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/'/>
<updated>2026-10-01T18:43:17+00:00</updated>
<entry>
<title>Kernel: T9014: enable VIRTIO_IOMMU on arm64</title>
<updated>2026-10-01T18:43:17+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-10-01T16:25:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=312893b89351bbf2cc683eb6ebbac7f0a789da32'/>
<id>urn:sha1:312893b89351bbf2cc683eb6ebbac7f0a789da32</id>
<content type='text'>
Smoketest test_kernel_options.py::test_hypervisor_virtio fails on arm64.
The test is not architecture gated and checks fifteen virtio options, of
which VIRTIO_IOMMU was the only one not enabled on arm64 - amd64 has it
as a module already.

The driver is available here, it is "depends on VIRTIO &amp;&amp; (ARM64 || X86)",
and it is what QEMU virt machines use, so build it as a module to match
amd64.

ACPI_VIOT comes along because VIRTIO_IOMMU selects it.
</content>
</entry>
<entry>
<title>Kernel: T9014: regenerate arm64 base config against Linux 6.18</title>
<updated>2026-10-01T18:43:14+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-10-01T16:25:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=73d9d2d6750e50649c1c1cf0bf3e8df7ac9e7fcb'/>
<id>urn:sha1:73d9d2d6750e50649c1c1cf0bf3e8df7ac9e7fcb</id>
<content type='text'>
The arm64 base config was still the dump of a 6.6.15 configuration. It had
only ever been hand edited per feature, never regenerated, so building
6.18.x produced 91 warnings from merge_config.sh:

  Value requested for CONFIG_AS_HAS_LSE_ATOMICS not in final .config
  Requested value:  CONFIG_AS_HAS_LSE_ATOMICS=y
  Actual value:
</content>
</entry>
<entry>
<title>Kernel: T9014: keep architecture specific options out of shared snippets</title>
<updated>2026-10-01T18:43:07+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-10-01T16:24:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=4f5a9a7b09f7b5cf330d47884c0501d5883a53d7'/>
<id>urn:sha1:4f5a9a7b09f7b5cf330d47884c0501d5883a53d7</id>
<content type='text'>
The config/*.config snippets are merged on every architecture, so an option
that only exists on one of them is reported as a mismatch on the others:

  Value requested for CONFIG_NETLABEL not in final .config
  Requested value:  # CONFIG_NETLABEL is not set
  Actual value:

Three options are only available on amd64 and were sitting in the shared
snippets. Move them to the amd64 base config, each next to the symbol that
gates it:

  * XFRM_USER_COMPAT needs COMPAT_FOR_U64_ALIGNMENT
  * HUGETLB_PAGE_OPTIMIZE_VMEMMAP_DEFAULT_ON needs
    ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP
  * NETLABEL depends on SECURITY, which arm64 does not enable
</content>
</entry>
<entry>
<title>Kernel: T9014: build WWAN drivers in on arm64, completing T8938</title>
<updated>2026-10-01T18:43:00+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-10-01T16:23:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=c6d478cce58f26be1a25fc5c09f31a7c23b9845b'/>
<id>urn:sha1:c6d478cce58f26be1a25fc5c09f31a7c23b9845b</id>
<content type='text'>
T8938 consolidated the WWAN build time options into config/12-wwan.config
and requested the USB WWAN drivers as built-in. That only ever took effect
on amd64. On arm64 all of them silently ended up as modules, because a
tristate can never exceed the value of what it depends on and the arm64
base config had USB_USBNET=m and USB_SERIAL=m, while amd64 had both =y.
Pull the two parents into the snippet so the requested =y is reachable on
every architecture - this is a no-op on amd64 where they were already =y.
</content>
</entry>
<entry>
<title>kernel: T9197: enable CONFIG_IWLMLD</title>
<updated>2026-08-11T16:16:17+00:00</updated>
<author>
<name>Stephen Nothnagel</name>
<email>srnoth@users.noreply.github.com</email>
</author>
<published>2026-08-11T16:16:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=8d1583caaabe5ecb3b5d8c384bf05a565ab978ca'/>
<id>urn:sha1:8d1583caaabe5ecb3b5d8c384bf05a565ab978ca</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>kernel: T9138: enable support for Microsoft MANA NIC driver</title>
<updated>2026-07-28T12:27:24+00:00</updated>
<author>
<name>Daniil Baturin</name>
<email>daniil@baturin.org</email>
</author>
<published>2026-07-28T12:27:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=caa1f3f9c406a4afd5554708afac1952bf57eb7c'/>
<id>urn:sha1:caa1f3f9c406a4afd5554708afac1952bf57eb7c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge pull request #1243 from alexandr-san4ez/T8868-rolling</title>
<updated>2026-07-17T05:55:51+00:00</updated>
<author>
<name>Viacheslav Hletenko</name>
<email>v.gletenko@vyos.io</email>
</author>
<published>2026-07-17T05:55:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=802f45df53f21e41a5062a1e4d1bf376f90f7cc6'/>
<id>urn:sha1:802f45df53f21e41a5062a1e4d1bf376f90f7cc6</id>
<content type='text'>
Kernel: T8868: Enable crash dump (kdump) and debug info in config</content>
</entry>
<entry>
<title>Merge pull request #1239 from c-po/compress-kernel-modules</title>
<updated>2026-07-15T15:26:39+00:00</updated>
<author>
<name>Viacheslav Hletenko</name>
<email>v.gletenko@vyos.io</email>
</author>
<published>2026-07-15T15:26:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=fbd036a36e4bd1fa8f15638f79bc554db2cac9fb'/>
<id>urn:sha1:fbd036a36e4bd1fa8f15638f79bc554db2cac9fb</id>
<content type='text'>
Kernel: T5641: enable module compression to save disk space</content>
</entry>
<entry>
<title>Kernel: T8868: Enable crash dump (kdump) and debug info in config</title>
<updated>2026-07-10T07:35:30+00:00</updated>
<author>
<name>Oleksandr Kuchmystyi</name>
<email>o.kuchmystyi@vyos.io</email>
</author>
<published>2026-07-06T07:59:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=446e1205432968b8a44e33084af40ac9016d3759'/>
<id>urn:sha1:446e1205432968b8a44e33084af40ac9016d3759</id>
<content type='text'>
Enabling the following options allows us to use `kdump-tools`:
  - `CONFIG_CRASH_DUMP`
  - `CONFIG_DEBUG_INFO`
  - `CONFIG_PROC_VMCORE`
</content>
</entry>
<entry>
<title>Kernel: T5641: enable module compression to save disk space</title>
<updated>2026-07-08T18:45:13+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-07-08T18:45:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-build.git/commit/?id=21c7e66112d3ec360a9902037d086fdb15e4ebeb'/>
<id>urn:sha1:21c7e66112d3ec360a9902037d086fdb15e4ebeb</id>
<content type='text'>
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.
</content>
</entry>
</feed>
