-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix detection of the ck-generic- kernel variants #137
Conversation
@Sacro Can you test this and verify that it works for you? |
I'l need to reboot into the CK kernel, it's currently broken for -zen too though!
|
Why? The output looks sane, doesn't it? Or what is your current Edit: Maybe we should improve the wording a bit? I'll definitely add a few log messages were one can see which package was detected etc. We need to do quite some normalization of the |
Oh sorry, yes it does look sane, Just that running has |
This allows us to keep the logic to detet the kernel variant part of the `uname -r` output simpler, but still handle the ck-generic kernels.
fb0fe96
to
f38842c
Compare
Yeah that's the confusing thing: So in the code we normalize these before comparing them, but the output is the original package version, but a normalized I added some more info messages in #138 which should help debug these issues. Just set
|
|
Thanks looks nice. If you find time to test it with CK kernel it would be appreciated. But if not, I'd just merge it and you could still reopen the issue if problems persist 🙂 |
(Regarding |
Yeah, I've rebooted for you, though I have OS lockups on 6.4.3 for some reason.
|
Nice! Seems to work as expected 🎉 Thanks for testing! |
Fixes #136