@nosuchthingascloud This is the state of things, non-coherence from a user POV as all this is quite scattered and a PITA to manage. For the developers this transactional: They do the part they can (or want to) do, but for the whole thing to work, its usually several stages. In this case: Having a dtb is good. If upstreamed the kernel generally supports init on this hardware. Can boot with the devicetree statement in grub (and some other mechanisms, like UKI). Also having the hwids additionally is good. This goes into dtb-loader and/or stubble. If merged there, stubblle / dtb-loader can detect booting on this hardware and do its magic. Even if both things are achieved, it needs to be in the Ubuntu tree (on both repos) to build a kernel that can boot from this device. And released on a new ISO. My kernels try to achieve at least the kernel part, including stubble. If the data is available, and I have "time", the current dt and hwid will be in my build repos and actually do the trick. Not a new ISO, though.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2093269 Title: [X1E] Support HP EliteBook Ultra G1q 14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-concept/+bug/2093269/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
