On Wed, 16 Jan 2019 21:04:02 +0100, Richard Brown wrote:
On Wed, 16 Jan 2019 at 21:00, Takashi Iwai
wrote: BTW, the kernel in OBS Kernel:stable repo has one big disadvantage. It's not signed with the official openSUSE key, thus it won't boot with secure boot. OTOH, if we take the real TW kernel package, it should work with secure boot, too.
But it's not quite straightforward to assign a repo only for fetching the kernel package, as it seems. So usually I've recommended to install Kernel:stable package. But if this scenario (providing TW kernel for Leap) becomes more popular, we should reconsider a better way (e.g. a repo aggregating only the TW kernel package).
Takashi
Most of the not-booting issues I've seen lately with modern hardware seem to be more related to UEFI/shim/Grub issues, causing black-screens of nothingness before the kernel comes into play
I'm not saying this to discourage the idea, but if we're going to invest significant time and effort into a solution for this complex problem, I don't think we should be setting peoples expectations too high - the kernel doesn't solve everything ;)
Yes, fully agreed. It's always good to have a bug report when a Leap doesn't work -- no matter whether the upstream kernel works or not. OTOH, there are known sets of not-well-supported hardware components. Recent AMD GPU is one of them for Leap 15.0, for example. They are indeed hard to support better with a fixed kernel like Leap, and it'd better to provide some level of workaround from the beginning. Overall, I'm not loudly advocating this TW kernel + Leap usage pattern, either. However, interestingly, it's also a combo of many (?) kernel developers actually take, AFAIK. This implies that, if you can bear with the frequent update of kernel (and with possible upstream kernel regressions), it's not too unrealistically bad choice. thanks, Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org