-
Notifications
You must be signed in to change notification settings - Fork 39
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
[Request] linux-cachyos-lts #882
Comments
Sadly, I have to choose between two things now: I either build more kernels and stop building the current one's modules, or I don't add new kernels. Currently, building all kernel modules take (more than) twice the time to build the kernels themselves. EDIT: I've added polls to know how to deal with this situation:
EDIT 2: We didn't have votes on Matrix, but on Telegram from 53 views, we had 22 votes, 36% preferred new kernels to current modules, but 64% preferred the opposite. |
How about removing hardened version of the kernel ? :) |
6.12 is around the corner, and it is expected to be the next LTS kernel version, once it's released bleeding edge repos like Arch and Nix will surely update their LTS base to it (no more 6.6). I'd recommend reporting your bug to your distro/kernel mailing lists, if it's really a kernel problem. |
Regressions happen in the kernel all the time. Next time you'll be saying this about 6.18 and 6.12, you know |
Link to the package upstream website/repository
https://github.com/CachyOS/linux-cachyos/tree/master/linux-cachyos-lts
Utility this package has for you
i'd like to use the cachyos patches but newer kernel release introduced multiple annoying regressions for my hardware in 6.9, 6.10 and 6.11
Do you consider the package(s) to be useful for every Chaotic-Nyx user?
YES!
Do you consider the package to be useful for feature testing/preview?
Are you sure the package isn't available upstream already?
Does the package's license allow redistributing it?
YES!
Have you searched the issues to ensure this request is unique?
Have you read the README to ensure this package is not banned?
More information
No response
The text was updated successfully, but these errors were encountered: