On the topic of which packages to pull for WiFi support in our images, I've checked seeds and images for jammy; Raspi defines all packages in seeds alone; in the foundational platform seeds, we have:
- netplan.io always installed through the minimal seed - wpasupplicant installed in desktop-common and raspi-common seed In Ubuntu seeds: - (network-manager) as recommends in the desktop-minimal seed - wireless-tools in the desktop-common seed - systemd-networkd is always there because it's part of the main systemd package (NB: wireless-regdb is typically a linux kernel dependency, and is not directly listed in seeds.) So I'm assuming that for our headless IoT images much like the Raspi ones, we should: - assume netplan, systemd-networkd to always be there - we should install wpasupplicant through a new tegra-common seed that we'd use from our tegra server images; in the meantime, we would list this package directly in the image definition ** Description changed: Hi, Canonical maintains a set of kernels and images for NVIDIA Tegra Orin based systems for Ubuntu 22.04/jammy in collaboration with NVIDIA, with intentions to also support 24.04 and probably other series in the future. The image definition for Tegra images is fairly simple: https://git.launchpad.net/ubuntu-images/tree/ubuntu-server-tegra-igx.yaml?h=jammy but has to manually pull a number of packages such as: - nvidia-tegra-defaults (currently just ships a GRUB config to expand the console= parameters to include the specific Tegra serial console) - grub + shim as to have a path to update these boot artifacts on installed systems Contrast this to RPi images which just refer to seeds https://git.launchpad.net/ubuntu-images/tree/ubuntu-server-pi-arm64.yaml this is because there are RPi specific seeds pulling in the bootloader – flash-kernel (ubuntu-seeds/platform/raspi-common) – and raspi specific packages – rpi-eeprom (same seed) Similary, the Tegra images don't currently include a WiFi stack, but just like RPi, they should as the Tegra system-on-modules come with a WiFi chip that we want to enable out of the box in Ubuntu. Here again, this is achieved in Raspberry Pi images by listing wpasupplicant in the raspi-common seed used in both desktop and server images. Hence, I think we need to add tegra seeds similar to the raspi ones, and similar metapackages. In the future, probably the bootloader bits should be selected through some more scalable mechanism somewhere between ubuntu-image and seeds. Wireless support should perhaps be in some kind of Ubuntu for IoT seed or similar, as to not clutter server, but share a common definition of how we expect to deliver WiFi in RPi like embedded systems. + We also want to have Tegra seeds to have a mean to pull packages into + main, such as nvidia-tegra-defaults. + Best, ** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2083775 Title: Seeds and metapackages for Tegra Status in ubuntu-meta package in Ubuntu: New Bug description: Hi, Canonical maintains a set of kernels and images for NVIDIA Tegra Orin based systems for Ubuntu 22.04/jammy in collaboration with NVIDIA, with intentions to also support 24.04 and probably other series in the future. The image definition for Tegra images is fairly simple: https://git.launchpad.net/ubuntu-images/tree/ubuntu-server-tegra-igx.yaml?h=jammy but has to manually pull a number of packages such as: - nvidia-tegra-defaults (currently just ships a GRUB config to expand the console= parameters to include the specific Tegra serial console) - grub + shim as to have a path to update these boot artifacts on installed systems Contrast this to RPi images which just refer to seeds https://git.launchpad.net/ubuntu-images/tree/ubuntu-server-pi-arm64.yaml this is because there are RPi specific seeds pulling in the bootloader – flash-kernel (ubuntu-seeds/platform/raspi-common) – and raspi specific packages – rpi-eeprom (same seed) Similary, the Tegra images don't currently include a WiFi stack, but just like RPi, they should as the Tegra system-on-modules come with a WiFi chip that we want to enable out of the box in Ubuntu. Here again, this is achieved in Raspberry Pi images by listing wpasupplicant in the raspi-common seed used in both desktop and server images. Hence, I think we need to add tegra seeds similar to the raspi ones, and similar metapackages. In the future, probably the bootloader bits should be selected through some more scalable mechanism somewhere between ubuntu-image and seeds. Wireless support should perhaps be in some kind of Ubuntu for IoT seed or similar, as to not clutter server, but share a common definition of how we expect to deliver WiFi in RPi like embedded systems. We also want to have Tegra seeds to have a mean to pull packages into main, such as nvidia-tegra-defaults. Best, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2083775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
