Hello, I applied a few more changes since I was asked to produced server images too, and it was not possible without one more fix. I have a question about that. - On noble, I add to change both the config and the hook `03-kernel-metapkg.chroot_early` to add my flavour. I tested it, it worked fine. - On devel the hook file does not exist anymore (mainly from commit dbfe42ad2516728f73afd37413acead8a16a8c03). I assume that it's not required anymore.
Any update on the testing method that we should apply here? Should I put the kernel on a PPA for devel, plucky and oracular? ** Description changed: - [ Impact ] - * In partner engineering, we maintain specific nvidia hardware which require a dedicated optimized kernel. We need to build Desktop images for these machines, on a regular basis, to run the certification suites. + * In partner engineering, we maintain specific nvidia hardware which require a dedicated optimized kernel. We need to build Desktop images for these machines, on a regular basis, to run the certification suites. Right now the kernel we need is `linux-nvidia-hwe-24.04-edge`, but I'm anticipating that it will be `linux-nvidia-hwe-24.04` at some point so this should be possible to configure. - * The resolution involves adding a subarchitecture (SUBARCH) option in + * The resolution involves adding a subarchitecture (SUBARCH) option in Desktop images which, when provided, will behave accordingly. a CHANNEL option can also be provided to add the channel. [ Test Plan ] - 1. Create a Desktop ISO. It will contain the generic kernel. - 2. Create a Desktop ISO with the proposed package. It will contain the generic kernel too. - 3. Create a Desktop ISO after mentioning subarch=nvidia in the metadatas. The kernel should now be nvidia's. - 4. Create a Desktop ISO after mentioning subarch=nvidia in the metadatas. The kernel should now be nvidia's edge. - 5. Build the images from 3, 4, 5 with ubuntu-cdimage and test that they boot correctly and have the right kernel. - Please not that the debian-cd branch to be used it the following merge proposal: https://code.launchpad.net/~antoinelassagne/debian-cd/+git/debian-cd/+merge/485191 + 1. Create a Desktop ISO. It will contain the generic kernel. + 2. Create a Desktop ISO with the proposed package. It will contain the generic kernel too. + 3. Create a Desktop ISO after mentioning subarch=nvidia in the metadatas. The kernel should now be nvidia's. + 4. Create a Desktop ISO after mentioning subarch=nvidia in the metadatas. The kernel should now be nvidia's edge. + 5. Build the images from 3, 4, 5 with ubuntu-cdimage and test that they boot correctly and have the right kernel. + Please not that the debian-cd branch to be used it the following merge proposal: https://code.launchpad.net/~antoinelassagne/debian-cd/+git/debian-cd/+merge/485191 + 6. Redo all these steps with Live Server image [ Where problems could occur ] - * If the bash scripts becomes invalid or go in the wrong branch, the + * If the bash scripts becomes invalid or go in the wrong branch, the image build process could simply stop working, or provide images with the wrong kernel. The test plan reflects this risk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2109822 Title: Add support for building ARM64 images with nvidia kernels in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2109822/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
