Neumie Hi, I was just wondering would it be possible to upgrade the kernel to 5.2 in the next update cycle? It has a few quirks added to it to handle the Index VR headset. Thanks, Neumie.
Neumie Ok on second thoughts never mind. It looks like 2 kernel patches are needed for the index. 1 is in 5.2. The other wont be out until 5.3. I'm going to need a plan B to get it to work I think.
Justin Neumie uname -a Linux solus-desktop 5.2.2-122.current #1 SMP PREEMPT Wed Jul 24 01:03:42 UTC 2019 x86_64 GNU/Linux 5.2.2 coming soon to a repo near you.
Neumie Justin Oh thanks very much 😃. Much appreciated. It looks like It needs 5.3 though which i know is way too soon for Solus (i think its only at RC1 at the moment). There are 2 specific patches needed: https://cgit.freedesktop.org/drm/drm/commit/?id=e28ad544f462231d3fd081a7316339359efbb481 https://cgit.freedesktop.org/drm/drm/commit/?id=30d62d4453e49f85dd17b2ba60bbb68b6593dba0. If I can find time I may look into building my own 5.3RC1 Solus kernel or 5.2 with the missing patch (any instructions or links on that?) but my plan B is to quickly switch to ubuntu on a backup drive as valve have a PPA with their own 5.1 kernel for the index. I will be back though as soon as 5.3 is worthy of Solus's awesomeness 🙂.
Justin Neumie https://dev.getsol.us/source/linux-current/ has the build files for the kernel. You'd just bump the release and change the source (and sha256sum). Then build it, may require some tinkering with patches, etc but if you are keen, you can try it. Note: Please backup any data before trying to ensure you don't lose anything important.
Neumie I hate to be a nuisance on this but is it too soon to get kernel 5.2.3 or newer? That second patch for the index was back ported. No worries if it is too soon. I didn't get a chance to figure out building my own. Thanks, Neumie.
JoshStrobl Sorry but it is a bit too late in the cycle for landing new kernels. We typically need to get these done early in the week (or post-sync on the weekend) to meet our expectations on testing. We'll get it landed for the next sync (not today's) though.