ghostv33 What fix? LTS is quite a bit older than latest at this point. If someone knows an actual patch that fixes it, we can add it, but "it works on LTS" is literally saying "it used to work, years ago". We have a hard enough time fixing regressions between releases in the same kernel series, weeks apart, let alone the thousands of commits between LTS and now.
Let's talk about the LTS kernels
ghostv33 I know, I read the other thread. My point is asking us to include the "fix" is like asking us to sort through a haystack for a single needle without lighting the haystack on fire. And since we can't reproduce it ourselves easily, searching that haystack also means not using magnets. It's probably something odd with the display driver in the linux-current kernel for your machine. That likely will only get fixed by moving us to a newer kernel which is waiting on a stable release of 5.10 at the moment.
ghostv33 I know. I figured you could connect the dots that it's specifically something in the driver that is causing problems with MATE's compositor (marco) and not the compositors/WM on the other editions. Apparently, I should have been more clear. These kinds of bugs happen all the time. They are almost always fixed by a later kernel update. Please be patient.
5 days later
Cooking 5.10-rc3, which will actually fix an issue I've been having with my realtek card on the r8169 driver, so that'll be nice!
JoshStrobl Will your RC builds of the LTS kernel be available in Unstable to test?
I'm hopeful that maybe I can use my 2740p on that without the stability issues I have under Current.
- Edited
Saijin_Naib 5.10 would be our current, not LTS. Our linux-lts is designed for what we consider older, "legacy" hardware that has notable regressions in newer kernels. The RCs aren't available since they're just on an experimental source repo that we have, not something we're going to be supporting more broadly since it'd require additional driver support, build time, etc. Mostly used as a rare playground to test changes or in this case, just get a head start on 5.10 so we can push it to unstable as soon it's released as a proper stable release.
@DataDrake has a fairly clear idea on how he wants to address LTS going forward. My work / testing is limited to future current.
JoshStrobl Thank you for the clarification.
I will see if/how I may help test the future LTS then.
- Edited
Saijin_Naib In further testing against current (5.6) on my HP EliteBook 2740p, I find that the issue with suspend/resume remains, and in addition, I am subject to random hard-freezes during usage/idling. Performance seems better than LTS, and accessory/peripheral functionality is solid.
The freeze seems to occur typically within 30min of boot and leads to the system being entirely unresponsive, requiring a hard reset via the power switch.
Given what I have access to, I'd say that maybe the 4.19 branch might be safer for this vintage hardware, given my issues with 5.6 currently.
a month later
i clicked others ( I want latest kernel supporting latest hardware). I wish Solus team uploads 5.9 kernel soon
dostana I wish Solus team uploads 5.9 kernel soon
It's not going to be 5.9, it'll be 5.10 because that is what fixes NVMe issues, per the many discussions here.
And, it’s probably no secret in this forum, 5.10 is expected to be released this upcoming weekend.
The most fun part of Solus is " It's fast, snappy with latest updates and also sometimes some funny things that doesn't work or sometimes one just need more support" and its all done fine.
Validated 5.10-rc7 locally on both my desktop and laptop, I've already updated our linux-current locally for it (previously was using our internal linux-next builds), went through and patched all the kernel modules where necessary (namely NVIDIA graphics drivers and VirtualBox). 5.10 is expected to come out Sunday U.S. (Monday here in Finland), so assuming that happens as scheduled I'll get it landed in unstable on Monday.
Linux 5.10, as well as updates to firmware, nvidia-390-glx-driver, open-vm-tools, openrazer, and virtualbox are now in the unstable repo. Assuming no blockers, should get landed into the stable repo this Friday. If you use the unstable repo, we encourage you to update and test!
So this new kernel has fsync support ? I read the changelog but I dont understand very much
gsf Reading item 1.2 from https://kernelnewbies.org/LinuxChanges makes it sound like you need to reformat a partition with a particular flag to get this feature.