I think I managed to clarify #2 further and added a few notes on why the workarounds are needed and when we can drop them.
** Description changed: [Availability] Currently in universe [Rationale] Very much like we did with the Lenovo Thinkpad X13s for 24.10 [1] I would like to add support for some of the new Snapdragon X Elite laptops in our coming release. Because arm64 is a bit special we need to ship a settings package containing tweaks and configs that make the installer "just work". This is based on the work I did for our Snapdragon Ubuntu concept image [2]. [Security] I don't expect any security impact. The package is mostly config files and should only affect this specific hardware. [Quality assurance] For now we will have to test manually. There are multiple developers who have access to hardware so that should not get in the way. [UI standards] [Dependencies] [Standards compliance] [Maintenance/Owner] Owned by the Foundations team. [Background information] The package provides 3 binary packages. - hwe-qcom-x1e-meta: This is picked up by "ubuntu-drivers --recommended" in subiquity and pulls in ubuntu-x1e-settings - ubuntu-x1e-settings: A full set of configs needed to make a installation work. This includes statically configured kernel command line parameters that would regress other devices - ubuntu-x1e-settings-nogrub: A safe subset of ubuntu-x1e-settings without the kernel command line. On our live media we want those to be set at runtime depending on which device we boot on to prevent regressions > please explain and give rationale for the "snap channels" in > debian/ubuntu-x1e-settings.postinst, as this seems to be swapping out the > whole stacks of GNOME/Mesa, which might lead to a different experience than > stock Ubuntu. > => snap refresh --channel adreno/stable --no-wait gnome-42-2204 > => snap refresh --channel beta/kisak --no-wait mesa-2404 - Since this is pretty new hardware we are facing problems with the dependency bundling model in snaps. Mesa in particular is problematic because it is closely tied to the hardware and kernel. - The hardware this package enables is not supported in mesa prior to 24.10, so the "default experience" would be that nothing works. We work around this by switching the main mesa provider snaps to channels built against a working mesa version. + Since this is pretty new hardware we are facing problems with the + dependency bundling model in snaps. Mesa in particular is problematic + because it is closely tied to the hardware and kernel. - Since 24.04 there is a dedicated mesa snap to handle those kinds of - situations, for 22.04 we have to hijack the gnome snap which also - bundles mesa. + The hardware this package enables is not supported in mesa prior to + 24.10, so the "default experience" would be that nothing works. We work + around this by switching the main mesa provider snaps to channels built + against a working mesa version. + + Since core24 there is a dedicated mesa snap to handle those kinds of situations, for core22 we have to hijack the gnome snap which supplies mesa for some core + apps like the snap store or firefox. + + This "workaround" will have to remain until those snaps switch to a base + that is new enough to support the hardware out of the box (core26) or + until we have a way to support newer hardware in older snap base + versions (e.g. use system mesa). [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-x13s-settings/+bug/2074078 [2] https://discourse.ubuntu.com/t/ubuntu-24-10-concept-snapdragon-x-elite/48800 ** Description changed: [Availability] Currently in universe [Rationale] Very much like we did with the Lenovo Thinkpad X13s for 24.10 [1] I would like to add support for some of the new Snapdragon X Elite laptops in our coming release. Because arm64 is a bit special we need to ship a settings package containing tweaks and configs that make the installer "just work". This is based on the work I did for our Snapdragon Ubuntu concept image [2]. [Security] I don't expect any security impact. The package is mostly config files and should only affect this specific hardware. [Quality assurance] For now we will have to test manually. There are multiple developers who have access to hardware so that should not get in the way. [UI standards] [Dependencies] [Standards compliance] [Maintenance/Owner] Owned by the Foundations team. [Background information] The package provides 3 binary packages. - hwe-qcom-x1e-meta: This is picked up by "ubuntu-drivers --recommended" in subiquity and pulls in ubuntu-x1e-settings - ubuntu-x1e-settings: A full set of configs needed to make a installation work. This includes statically configured kernel command line parameters that would regress other devices - ubuntu-x1e-settings-nogrub: A safe subset of ubuntu-x1e-settings without the kernel command line. On our live media we want those to be set at runtime depending on which device we boot on to prevent regressions > please explain and give rationale for the "snap channels" in > debian/ubuntu-x1e-settings.postinst, as this seems to be swapping out the > whole stacks of GNOME/Mesa, which might lead to a different experience than > stock Ubuntu. > => snap refresh --channel adreno/stable --no-wait gnome-42-2204 > => snap refresh --channel beta/kisak --no-wait mesa-2404 Since this is pretty new hardware we are facing problems with the dependency bundling model in snaps. Mesa in particular is problematic because it is closely tied to the hardware and kernel. The hardware this package enables is not supported in mesa prior to 24.10, so the "default experience" would be that nothing works. We work around this by switching the main mesa provider snaps to channels built against a working mesa version. Since core24 there is a dedicated mesa snap to handle those kinds of situations, for core22 we have to hijack the gnome snap which supplies mesa for some core - apps like the snap store or firefox. + apps like the snap store or firefox (which segfault otherwise). This "workaround" will have to remain until those snaps switch to a base that is new enough to support the hardware out of the box (core26) or until we have a way to support newer hardware in older snap base - versions (e.g. use system mesa). + versions (e.g. use system mesa). Once core24 is widely in use we can + drop the workaround for core22. [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-x13s-settings/+bug/2074078 [2] https://discourse.ubuntu.com/t/ubuntu-24-10-concept-snapdragon-x-elite/48800 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095536 Title: [MIR] ubuntu-x1e-settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-x1e-settings/+bug/2095536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
