XPost: linux.debian.maint.boot, linux.debian.ports.arm

Hi,

This is mostly for information: linux went through a lot of big changes, initially staged in experimental, and uploaded to unstable as of linux
6.6.8-1. These impacted the installer in different ways. This is a
summary of the obvious impacts, there might be some others down the line
(just by glancing at hw-detect's massaging of module list by stripping
the .ko suffix).

- kernel-image-* packages are now shipping /boot/vmlinuz-* (or
/boot/vmlinux-* depending on the arch), instead of just /boot/vmlinuz
(respectively /boot/vmlinux). I didn't dive into all the changes but
I'm not sure whether that was on purpose or a side effect of the big
changes. In any case, on the short term, since the build system was
relying on a single file there, that should be moved out of the way,
I decided to unversion those files to restore the old names. If kernel
maintainers decide to go back to unversioned files, two reverts should
be enough:
https://salsa.debian.org/installer-team/debian-installer/-/commit/c17360e632b6f133d4b43a47461944b6203ed730
https://salsa.debian.org/installer-team/debian-installer/-/commit/865c66e497d8e809872bad04aa2269d2a9f889c8

- Modules are compressed now, so the drm workaround needed an updated to
cope with the extra .xz suffix:
https://salsa.debian.org/installer-team/debian-installer/-/commit/bd0f1106f90756e6f4514108492d71e1f2e695ea

- I'm skipping two commits regarding the new way the ABI is written
down, that's in line with what was announced initially.

- YIL: If you don't see anything move in the graphical installer (no
keyboard, no mouse), if your video is garbled, and if you can't load a
NIC module in the text installer, you might have a totally broken
support for kernel modules in your installer. This required adjusting
src:xz-utils to get a liblzma udeb and src:kmod to enable xz support
in its udebs; “thankfully” the former is NMU-maintained, plus the ftp
team speed-reviewed it from NEW; thankfully Marco ACK'd my NMU-ing
kmod so that we unbreak things ASAP. Everything should be sorted out
in unstable. Plus an extra commit to be extra careful between the
kmod upload and the cronned daily builds (which were going to start
before the 01:52Z dinstall):
https://tracker.debian.org/news/1489255/accepted-xz-utils-545-02-source-amd64-all-into-unstable/
https://tracker.debian.org/news/1489268/accepted-xz-utils-545-03-source-into-unstable/
https://salsa.debian.org/md/kmod/-/merge_requests/13
https://tracker.debian.org/news/1489283/accepted-kmod-3020230601-21-source-into-unstable/
https://salsa.debian.org/installer-team/debian-installer/-/commit/c65bdb8128bc68cb566b302feb46267e5c177eb4

- Finally, the armel build fails because it can't find its kernel. The
marvell flavour seems to have been dropped entirely (at least that's
how I read the linux changelog for 6.6.3-1~exp1:
https://tracker.debian.org/news/1482751/accepted-linux-663-1exp1-source-into-experimental/

I didn't investigate the last point and I'd appreciate it if porters
could double check that we really want to drop marvell at this point,
and maybe submit (or commit) patches to drop it from the installer:
https://salsa.debian.org/installer-team/debian-installer

Various netboot and netboot-gtk checks on amd64 seem very positive
after those changes, but I haven't built a netinst image and checked
on actual hardware with the combination of Secure Boot + firmware
packages + reloading of kernel modules. The latter should primarily work
by using module *names* and firmware *paths* as seen in kernel logs, so
having different module *paths* shouldn't make a difference, but that's
just my gut feeling based on my recollection (so nobody should trust
me on this), and seeing how \.ko$ stripping appears in some other files,
I cannot be certain until it's been actually tested.

Feel free to reply to this thread if you spot other fallouts. Of course,
as usual, the best way to report installer bugs is to file them against
the relevant component, X-Debbugs-Cc-ing this list; but leaving an
explicit reference in this thread wouldn't hurt.


Cheers,
--
Cyril Brulebois ([email protected]) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmWH4A4ACgkQ/5FK8MKz VSCXxRAAssVRz+3PlesbXBddt82TCyF8vzE2mIqotANDSCXBH+BeQ5aV5gYWmGRG oeT1gqEAjdcHsH3nvzzhNRHD6OnfDoI6rIekFuc6ZcmTq3DBf7vunutFf0CLayg9 eUKLePhvBNLKIN9SPJ0TY3cYgDi5ffpguc74bh3i9lkzi+TpdiGLgNpWZ8g9sXrx 5N6YM9QHM+FPMMF+xGUwD8ndaD1H0coL/svlQlx6kTgqqoyqYrtGobFMUj9l0yJE t3VR+VOouX/pMkJVbkrNXUp0lbMkeBSPoBv1qd4cv+RWa25uF0hF+j7ZK4vj6N6A d4ZKK1hOUMiHxwau3Q/eOyzp89d2vq5V9xaWO/aJeEunviGtMjsWShxw75Mw1ccs vvU2PzFmokAu7NdKWSsfpTelHB1SJebdzy5PxCD0CUBOTJHOSDX7b0zv1ZofO+Ht wvT5VcL0fxrNIWCsjhn/ykd3LDUkh2klK5CXmg4rUZRK/5s5oFnsVu9KgOGFVr0k hSqMCTFhN9yM8bhO0GNq4/vXMYq8zcTN/TmoaS1bqSDxandZC8ZO3y6sRbfVWtN/ 5/WXhd9C1JSeA2DTCuWweSK9VPo2Apvf+c0/lln3eGLky7HxmYBxJsaSKp5mW7sY x3iH90z0ckLPl2nUrRs7eFD9WXW0w+t2s2v9Io+CbgwZpKPpHY0=
=7W26
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*

XPost: linux.debian.maint.boot

Cyril Brulebois <[email protected]> (2023-12-24):

Feel free to reply to this thread if you spot other fallouts.

Another FYI: one thing that I spotted early on (before realizing module
support was entirely broken), when I first diffed the list of files
available in the initramfs, building against testing's or unstable's
linux udebs: a bunch of virtio modules disappeared.

Comparing 6.5.0-5-amd64 and 6.6.8-amd64:

usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_balloon.ko
usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_dma_buf.ko
usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_input.ko
-usr/lib/modules/$ABI/kernel/drivers/virtio/virtio.ko
usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_mmio.ko
-usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_pci.ko
-usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_pci_legacy_dev.ko
-usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_pci_modern_dev.ko
-usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_ring.ko

A cursory look in linux.git didn't yield an obvious answer:

git diff debian/6.5.13-1..debian/6.6.8-1 -- debian/installer/

Indeed, that's mostly about kernel-versions's getting dropped, fuse
going away, some Depends field being updated, and some i2c-hid-* now
getting excluded in one place, and added conditionally in another one…

Searching for information about fuse and virtio, I finally noticed this
entry, which probably explains both fuse's “going away” and ditto for
some (but not all) virtio modules:

* Set CONFIG_VIRTIO_FS and its dependencies to builtin, to allow building
images that boot directly to rootfs (skipping the initrd)

as it changes:

-CONFIG_VIRTIO_PCI=m
+CONFIG_VIRTIO_PCI=y
-CONFIG_FUSE_FS=m
+CONFIG_FUSE_FS=y
-CONFIG_VIRTIO_FS=m
+CONFIG_VIRTIO_FS=y

I thought I'd mention the answer by mail since I brought up the topic
earlier (even if only on IRC).


Cheers,
--
Cyril Brulebois ([email protected]) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmWH6MsACgkQ/5FK8MKz VSCHpRAAmmeO5/jd0LVX4oBfjfn+JpCMB5PHB4McyxswgED9XPsfgVxXbYli7aEY 6/aJZHW5OEWmnUGPgxgsMYGl0q/fBexKf5ct79nyezroLXDUbdrgEl8pb5JDMYJy sdK383gExUDCaE/Rdw33ThbKQbi0Vpt0GSHApd9qnlGSi3bVqs8fmwIfZzFq5SRe 48wZZeyTZ6br3IOzqjF1QmYEfpidwYjsGtiY+ZftmYQnmPUknZPRL/HAkejMYmdl orO+KpoBXVStB2WHJwQT1DeNwsdY4c3pyq0Gq2PFURqusEhNWKLiA7GyWaKn7sDD zQdk79UO0UDMEqnMPxJ8qIDsQaEkJ4uTbgo7XTXXWJP6vIQPHmgM7FqrFO4//hXZ CRhXsh0gGpgoPJkXz04U+OmSFmpeEgFPSFrkNqUwKYymq0c0xODqZrHn9UEHbEQK IpxqZgxrFVOupjiBhICAiS3LKGVyTgP6T6kYEGzAeuBjAZl8A4CzKCjbss13AATm 6gNvBBObH9WlXbM5ag3n9lHhf9n+jHHFarMMzUHEey++A8gX0QDRArBTS98+mak/ 9mSFc+4g0IgjKhEFR8PQWTAXWDiZRGOeanM3iAkfFbez+MW39uxolFp4ozfuR/AO YxrCLRmx/Wt4yH57ga4grg78ap0jFXQZXG4NSANSOxAkZohi0Ts=
=7W/W
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*

XPost: linux.debian.maint.boot

24.12.2023 11:16, Cyril Brulebois :
...

Searching for information about fuse and virtio, I finally noticed this entry, which probably explains both fuse's “going away” and ditto for some (but not all) virtio modules:

* Set CONFIG_VIRTIO_FS and its dependencies to builtin, to allow building
images that boot directly to rootfs (skipping the initrd)

as it changes:

-CONFIG_VIRTIO_PCI=m
+CONFIG_VIRTIO_PCI=y
-CONFIG_FUSE_FS=m
+CONFIG_FUSE_FS=y
-CONFIG_VIRTIO_FS=m
+CONFIG_VIRTIO_FS=y

Hm. This same argument can be used to include every storage- and filesystem-related
module into the kernel. Why don't we have ahci and sd_mod built-in? This does look quite a bit strange to me to include this stuff..

(This commit is not about big linux changes but about small debian changes ;)

/mjt

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hm. This same argument can be used to include every storage- and filesystem-related
module into the kernel. Why don't we have ahci and sd_mod built-in?
This does
look quite a bit strange to me to include this stuff..

If you have a block device then there are very little advantages in
terms of workflows, as it's still going through a lot of slow paths.

This on the other hand enables the virtiofsd + qemu direct boot fast
path, which is increasingly popular for fast development cycles, and
changing those kconfigs brings us in line with other distros.

--
Kind regards,
Luca Boccassi

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEErCSqx93EIPGOymuRKGv37813JB4FAmWICCgACgkQKGv37813 JB4zqA//e0gaGCJYpdiYIrznHDsrdlC2hyVKoUEKfnPW4MoJLtE4qBc4LXScX4iH gG/K8J14OH0eayny7BinrVR0Jq82q+SV4GYjR1VUdNWy+MzYxQdhjBKah4Iql6JS qgWYOIXPeQ/Y4cCG3JDf4AJSo4rZ2yyeJYX3Gy49v2jmOpWBakjBseLCYaV95E7U RVs6g+o6WpJGu3XvNMQfxKQTf2ylPby8NJaZp5+usfFrnvpnUchg02aLOxApFHCD KR+rK4oQMr4FkeOc19MEJ3mHHk+u2wSswNl2z131HXPCzvQWwHFhzhJH7PqgiRc4 HHJghMF+xrv1wiRtntqw9YVWlDtDFg486c/1Zp1tg/vgiXPoCekqfi0rAghxx4W0 +9dS33kBkzA6dXySJmEpTp7UsN4zhSSAidlngR5lORqPLvmiTuWUXsra3FR8yrC6 um1QiotnkhXTjHfzgGwQ40Le+grISPxSdPNP/3QjqHgNqXY4TvcMEOysyEn0cwUw yQXqkrgNGhMTnH/zTjmI7rDLyCOG8KW09E/YDQMYE432XUtlqei+PWV8UkTrtYoS C18O5k6FJySO9S7pMIi6d3JVX+vLe+a8+qDBicOGkHoPMExDVzAEToU8KdSf+I8d y6Yh2Kj/JP0mkGXgjPBSBVivD1b3iUajNmcny7YxFDgcIcOlBY8=
=vAmm
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.maint.boot, linux.debian.ports.arm

On Sun, Dec 24, 2023 at 08:38:57AM +0100, Cyril Brulebois wrote:

- kernel-image-* packages are now shipping /boot/vmlinuz-* (or
/boot/vmlinux-* depending on the arch), instead of just /boot/vmlinuz
(respectively /boot/vmlinux).

This was even dependent on architecture. A lot of secondary
architectures already had various suffixes.

- Modules are compressed now, so the drm workaround needed an updated to
cope with the extra .xz suffix:
https://salsa.debian.org/installer-team/debian-installer/-/commit/bd0f1106f90756e6f4514108492d71e1f2e695ea

This now hardcodes .xz. And I'm not really sure what this does and why
this can't be fixed in the kernel packages.

- Finally, the armel build fails because it can't find its kernel. The
marvell flavour seems to have been dropped entirely (at least that's
how I read the linux changelog for 6.6.3-1~exp1:
https://tracker.debian.org/news/1482751/accepted-linux-663-1exp1-source-into-experimental/

Yes, the kermel was broken and the checks for this disabled since quite
some time.

Bastian

--
Extreme feminine beauty is always disturbing.
-- Spock, "The Cloud Minders", stardate 5818.4

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.maint.boot, linux.debian.ports.arm

Bastian Blank <[email protected]> (2023-12-24):

On Sun, Dec 24, 2023 at 08:38:57AM +0100, Cyril Brulebois wrote:

- kernel-image-* packages are now shipping /boot/vmlinuz-* (or
/boot/vmlinux-* depending on the arch), instead of just /boot/vmlinuz
(respectively /boot/vmlinux).

This was even dependent on architecture. A lot of secondary
architectures already had various suffixes.

Looking at kernel-image-* 6.5.13-1 for release archs, I'm only seeing
mips64el (-6.5.0-5-5kc-malta, -6.5.0-5-loongson-3, -6.5.0-5-mips64r2el suffixes), and its build targets didn't hit the codepath I had to patch
for the general case.

Anyway, since you're not reacting with “oops, we didn't mean to”, I'm
going to count this as a deliberate change.

- Modules are compressed now, so the drm workaround needed an updated to
cope with the extra .xz suffix:
https://salsa.debian.org/installer-team/debian-installer/-/commit/bd0f1106f90756e6f4514108492d71e1f2e695ea

This now hardcodes .xz. And I'm not really sure what this does and why
this can't be fixed in the kernel packages.

Because that's a workaround for a problem that's not in the kernel and
that remains to be fully investigated.


Cheers,
--
Cyril Brulebois ([email protected]) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmWIXL8ACgkQ/5FK8MKz VSAzLw/+IIPlq8/06iefe2zXWyak4Za367bZ2vkHBpukUzx/8OlI8okEh0DRmMS+ I6el1/ap+3/Ra1bGQ9Rg/z+DbBTso0Qnl0Qb2lK+g5uB/VicbQsNsqfl9OpbTMk5 To13IO6aRJzzQJ4G/z3s8YTbVmkIdtJj+LloipFbkj4l2sIqNu5gDDxRLwVrqmo0 PY6FzBJbxYG79j/VWvKGChAeMq25EKizfv/R/0GH5uVR5+bMUaUL3JRCwVcmt3Cz N/f7L8ZA6RANB+sZ3zg3FJOhcY12+tM2m1yVfnnz1/taMwQpssV7LvR2r4ZjaJWy 1jNLqtQxgGuIRTpaSbL+ng9M7MWd5YI58nOGMop5Uksnr79D6FIypbDNFfxgYKJ4 WHCgI1PByGuv46627qju5Q/WmHXzvhyVG+dca0ZwESqhcnEHLtbvg/4zHIuYz+f0 taMlcKeHbXul5MeSYqR24x9V+votBksEVvTCBP5367ncyn/Y0GWRkfROl816y/MP SoWTkoUpxY02kep9Zjc/aHVcTE4R4Q/ZUo0pcF1Nai8l/gZ9r+Su67ZL8A4QM/i+ 5eAPhG4D3vIW4Wqsij19UF2BpTr/OaU0U1RWpjTp22BdxZvcHx3xrw/nQ9tY2HRl vPaoD/R9gCprk/Dl/UXDXMRN947So2qYYYvpb2sBI0BaSyMcy/Q=
=EXE0
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*

XPost: linux.debian.maint.boot

Hi Roland,

FYI, you might want to read the full thread! ;)

On Sun, Dec 24, 2023 at 08:38:57AM +0100, Cyril Brulebois wrote:

This is mostly for information: linux went through a lot of big changes, initially staged in experimental, and uploaded to unstable as of linux 6.6.8-1. These impacted the installer in different ways. This is a
summary of the obvious impacts, there might be some others down the line (just by glancing at hw-detect's massaging of module list by stripping
the .ko suffix).

- kernel-image-* packages are now shipping /boot/vmlinuz-* (or
/boot/vmlinux-* depending on the arch), instead of just /boot/vmlinuz
(respectively /boot/vmlinux).

[...]

this change also lead to failing live-builds, for trixie (the unstable live-builds
are of course also affected but fail earlier due to #1058994), this can be
seen in https://jenkins.debian.net/job/reproducible_debian_live_build_xfce_trixie/35/console
which failed with

cp: cannot stat 'chroot/debian-installer/build/dest/cdrom/vmlinuz': No such file or directory


--
cheers,
Holger

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄

Just 100 companies are responsible for 71% of global emissions. https://www.theguardian.com/sustainable-business/2017/jul/10/100-fossil-fuel-companies-investors-responsible-71-global-emissions-cdp-study-climate-change

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmWJas8ACgkQCRq4Vgaa qhyFzhAAoX+bxM/EEmc1u8+b8Al+o0xM7Qxp+XO+YfqEUUkfJIxAqvNkxwwa7TxN daD7/TSNrg/U8xSWeoi5rWpVQdSYft2cy4MNU0Dnb5EpdAwfdjJNIIEaAlaxJOIL y9xzRtqMc/EuKvwPgJdXUxJe/KTRTVcOJfMDgbOK7VQfmMmUhiVJlqyQfTpDWJYs cnJX3FMGy5Z6/BLf51azarTSo10ejgwAfxfTS6bOV+xcGhHn/qPQs85o598vAr8c uR9zVGYajJ84wbvG06aK0uNEI8ZiQybf8aNacKBVXZDabAzz9vTuVnxaogJ+lXsY HfGnShUe9bhUJP2+hLK+RrMUPkcKzMn7SmB7xrivETgFPL6J/4+2y1uiNsjQFTQa 6esH6tuMyldo1hjHPfV+TPz413HEs/x3ZNZ3C4Pyhq+u72FoxwbxKI4wcaDrePI/ HEg6JnvN9oFG8+oK6Waebu6IQV

XPost: linux.debian.maint.boot

On Fri, Dec 29, 2023 at 08:04:19AM +0100, Roland Clobus wrote:

Yesterday I published 3 fixes which got merged really quickly.

[...]

Now Jenkins is running fine for the live sid images again :-)
In the next step, I'll check the trixie live builds.

awesome, thank you!


--
cheers,
Holger

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄

20230709: Today was the warmest day on earth in 125,000 years. Today was also the day with the most planes in the air at one time ever in history. By the time
you read this both of these records have probably been broken.

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmWOqf8ACgkQCRq4Vgaa qhzhvg/8CzpKmAJSdS6pn1DH+QYy8iE1hRVtCGLQepORsOUWP1oLOuo9VJlEG3rE 1uQt1NRESB28/6o9ADlDQNaZvCTc5SxYWewS8Ei1UMs+PkxBq10qlvciz+OrHOMM 1pAaUVyhoeFPStHuaMRJ2WQDntYHljWYZABIsj0m36VRCnWBHvvlvhLhRApmAdLX VWxjmx9pHvjpp4f+vrp8F9ebST3CL/hzw0nB0h0FaNOXacAt/7dvNeiJGW94UMEY O1TuL6AOrn6cCX1isgn/T8Y89hg3ltbMYcTt9h96WeIplGleY7rJnuMula8b3J5L gHNEGCzEHGHqZw5DHbnfq0Ksk17ePk3wd26M0xiGpxYarqvb1d6Dnz7A1teLukE0 VUV2SJ4aDujWZt0RZUmsk/HFtdySgjEUbqq1KB6gdmk0TrRhBuOjmT+ss3VsZK8V 9I+BcmcTcMTwQVjxefKi/