Page MenuHomeSolus
Create Task
Maniphest T10452

Linux 6.1
Closed, ResolvedPublic
Actions

Description

Disclaimer: This guide is intended for advanced and expert users only. Please only follow if you know how to change your kernel at boot time, edit kernel boot parameters, and how to boot your system from a rescue USB and fix it. You should already know what addon kernel modules you need. Do not attempt if this is your only device. We're not responsible if this renders your device or data unusable. You need to be on the unstable repo for this guide.

Still feel like trying it? Great.

To start with, you should know what graphics driver your system uses. If your system uses AMD or Intel graphics you're in luck because your install will be a bit simpler. For Nvidia users you'll need to check your current driver to see if you are using the 520 driver (nvidia-glx-driver), the 470 driver (nvidia-470-glx-driver), or the 390 driver (nvidia-390-glx-driver). If you are unsure of which of those you are using and unable to figure it out this guide is probably not for you.

Intel/AMD graphics:

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/linux-next-6.1.0-22-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/linux-next-headers-6.1.0-22-1-x86_64.eopkg

Nvidia 520 driver (nvidia-glx-driver):

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/linux-next-6.1.0-22-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/linux-next-headers-6.1.0-22-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-glx-driver-32bit-520.56.06-444-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-glx-driver-common-520.56.06-444-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-glx-driver-modaliases-520.56.06-444-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-glx-driver-next-520.56.06-444-1-x86_64.eopkg

Nvidia 470 driver (nvidia-470-glx-driver):

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/linux-next-6.1.0-22-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/linux-next-headers-6.1.0-22-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-470-glx-driver-32bit-470.161.03-15-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-470-glx-driver-common-470.161.03-15-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-470-glx-driver-modaliases-470.161.03-15-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-470-glx-driver-next-470.161.03-15-1-x86_64.eopkg

Nvidia 390 driver (nvidia-390-glx-driver):

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/linux-next-6.1.0-22-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/linux-next-headers-6.1.0-22-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-390-glx-driver-32bit-390.157-145-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-390-glx-driver-common-390.157-145-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-390-glx-driver-modaliases-390.157-145-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/nvidia-390-glx-driver-next-390.157-145-1-x86_64.eopkg

Don't reboot yet

If you use any additional kernel modules these are the rebuilt packages for them. Run the command listed for each kernel module you need:

bbswitch:

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/bbswitch-next-0.8-275-1-x86_64.eopkg

broadcom-sta:

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/broadcom-sta-common-6.30.223.271-340-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/broadcom-sta-modaliases-6.30.223.271-340-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/broadcom-sta-next-6.30.223.271-340-1-x86_64.eopkg

openrazer:

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/openrazer-common-3.4.0-258-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/openrazer-modaliases-3.4.0-258-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/openrazer-next-3.4.0-258-1-x86_64.eopkg

v4l2loopback:

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/v4l2loopback-common-0.12.7-237-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/v4l2loopback-next-0.12.7-237-1-x86_64.eopkg

vhba-module:

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/vhba-module-common-20211218-198-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/vhba-module-next-20211218-198-1-x86_64.eopkg

virtualbox:

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/virtualbox-common-6.1.40-245-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/virtualbox-next-6.1.40-245-1-x86_64.eopkg

xone:

sudo eopkg it https://solus.reillybrogan.com:8443/T10452/xone-common-0.3-4-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10452/xone-next-0.3-4-1-x86_64.eopkg

Now you can reboot into the new kernel.

Major Changes:

  • Usual 6.1 hardware enablement
  • NTFS3 enabled
  • MGLRU enabled
  • Some Zen patches cherry-picked:
    • Set default mglru TTL to 1 second (improves system responsiveness)
    • Use BFQ by default for single queue devices (usually spinning hard drives)
    • Use Kyber by default for multiqueue devices (flash-based devices like NVME SSDs)
    • Disable work queue for dm-crypt (improves responsiveness of encrypted devices)

Event Timeline

ReillyBrogan claimed this task.Dec 12 2022, 5:44 PM
ReillyBrogan triaged this task as Normal priority.
ReillyBrogan created this task.
ReillyBrogan updated the task description. (Show Details)Dec 12 2022, 6:30 PM
ReillyBrogan updated the task description. (Show Details)Dec 12 2022, 6:33 PM
algent added a subscriber: algent.Dec 12 2022, 7:21 PM

Booted successfully to kernel 6.1 and virtualbox working without any issue.
And so far no issues with snaps and flatpaks.

Host: CELSIUS W530 
Kernel: 6.1.0-22.next 
Shell: bash 5.1.16 
Resolution: 1920x1080 
DE: Budgie 10.6.4 
WM: Mutter(Budgie) 
CPU: Intel Xeon E3-1271 v3 (8) @ 4.000GHz 
GPU: NVIDIA Quadro 2000 
Memory: 5124MiB / 15925MiB
Staudey added a subscriber: Staudey.EditedDec 12 2022, 11:53 PM

Hmm, while the (self-compiled) RC kernel worked fine for me, with this version (plus nvidia-glx-driver) I can't use mouse or keyboard, and journalctl shows me the following error several times during boot.
Dez 13 00:45:55 solus-pc kernel: hid: exports duplicate symbol hid_bus_type (owned by kernel)

Will look into it more tomorrow, it's getting pretty late.
Full journal log for reference in the meantime: https://dev.getsol.us/P30

Jacek awarded a token.Dec 13 2022, 12:07 PM
Jacek added a subscriber: Jacek.Dec 13 2022, 12:09 PM

What do you thing of also including this change? https://www.phoronix.com/news/Linux-Splitlock-Hurts-Gaming Or just wait for 6.2?
Also, thank you so much for such quick kernel update, and including those additional patches!

ReillyBrogan added a comment.Dec 13 2022, 5:30 PM
In T10452#199552, @Jacek wrote:

What do you thing of also including this change? https://www.phoronix.com/news/Linux-Splitlock-Hurts-Gaming Or just wait for 6.2?

Given that it's already been merged into 6.2 and there's already a valid workaround (use the kernel parameter) my inclination is to wait.

In T10452#199548, @Staudey wrote:

Hmm, while the (self-compiled) RC kernel worked fine for me, with this version (plus nvidia-glx-driver) I can't use mouse or keyboard, and journalctl shows me the following error several times during boot.

I'm pretty sure I know which change I made broke this so I'm re-building the kernel with the change reverted now.

ReillyBrogan added a comment.Dec 13 2022, 6:07 PM

@Staudey I just uploaded a new kernel build. Re-run the command under "Intel/AMD graphics" to install it. None of the kernel modules should need re-building (probably).

If anyone else already has 6.1 installed and has not experienced the same issue then there's no need for you to install the fixed kernel. Just keep using the kernel you were already using.

Staudey added a comment.EditedDec 13 2022, 6:18 PM

@ReillyBrogan: Works fine now, thanks!

Host: Pentino Mini G530 
Kernel: 6.1.0-22.next 
Packages: 2032 (eopkg), 6 (flatpak) 
Shell: zsh 5.9 
Resolution: 1920x1080 
DE: Budgie 10.6.4 
WM: Mutter(Budgie) 
CPU: Intel i7-2600K (8) @ 3.800GHz 
GPU: NVIDIA GeForce GTX 1060 6GB 
Memory: 1956MiB / 7909MiB

(the RC also worked fine on an Intel i5-3550P Nvidia GTX 1050 Ti system, but that one is borked now (for unrelated reasons))

silke added a subscriber: silke.Dec 14 2022, 3:50 PM

The kernel broke MST on my desktop (log attached). The issue has been reported here already. Specs:

Host: B450 AORUS M 
Kernel: 6.1.0-22.next 
Uptime: 3 mins 
Packages: 1928 (eopkg), 7 (flatpak), 22 (snap) 
Shell: fish 3.5.1 
Resolution: 2560x1440 
Terminal: /dev/pts/0 
CPU: AMD Ryzen 5 2600X (12) @ 3.600GHz 
GPU: AMD ATI Radeon RX 6800/6800 XT / 6900 XT 
Memory: 1597MiB / 32027MiB

Working fine on my notebook:

Host: 20N3S3DN00 ThinkPad T490 
Kernel: 6.1.0-22.next 
Uptime: 4 mins 
Packages: 1777 (eopkg), 15 (snap) 
Shell: fish 3.5.1 
Resolution: 2560x1440 
Terminal: /dev/pts/1 
CPU: Intel i5-8265U (8) @ 3.900GHz 
GPU: Intel WhiskeyLake-U GT2 [UHD Graphics 620] 
Memory: 1985MiB / 23704MiB

trace.log5 KBDownload

ReillyBrogan added a comment.Dec 14 2022, 6:24 PM
In T10452#199569, @silke wrote:

The kernel broke MST on my desktop (log attached). The issue has been reported here already. Specs:

Thank you for the report and also for find the linked issue. I did some more research on the Freedesktop gitlab and I think the main issue is this one. Once it seems like there's a valid solution in place I'll pull the fix patches into 6.1

GPU: AMD ATI Radeon RX 6800/6800 XT / 6900 XT

I'm confused by this output, which GPU do you have exactly?

silke added a comment.Dec 14 2022, 7:41 PM
In T10452#199570, @ReillyBrogan wrote:

GPU: AMD ATI Radeon RX 6800/6800 XT / 6900 XT

I'm confused by this output, which GPU do you have exactly?

Yeah, that's not helpful, sorry. I have an AMD Radeon RX 6800 XT.

GZGavinZhao added a subscriber: GZGavinZhao.EditedDec 16 2022, 7:23 PM

Full AMD system, so far no issues.

            -```````````                  gavinzhao@solus 
          `-+/------------.`              --------------- 
       .---:mNo---------------.           OS: Solus x86_64 
     .-----yMMMy:---------------.         Host: 82NW Legion 5 15ACH6A 
   `------oMMMMMm/----------------`       Kernel: 6.0.11-225.current 
  .------/MMMMMMMN+----------------.      Uptime: 1 hour, 35 mins 
 .------/NMMMMMMMMm-+/--------------.     Packages: 1889 (eopkg), 18 (flatpak) 
`------/NMMMMMMMMMN-:mh/-------------`    Shell: fish 3.5.1 
.-----/NMMMMMMMMMMM:-+MMd//oso/:-----.    Resolution: 1920x1080 
-----/NMMMMMMMMMMMM+--mMMMh::smMmyo:--    DE: Budgie 10.6.4 
----+NMMMMMMMMMMMMMo--yMMMMNo-:yMMMMd/.   WM: Mutter(Budgie) 
.--oMMMMMMMMMMMMMMMy--yMMMMMMh:-yMMMy-`   Theme: Plata-Noir [GTK2/3] 
`-sMMMMMMMMMMMMMMMMh--dMMMMMMMd:/Ny+y.    Icons: Papirus [GTK2/3] 
`-/+osyhhdmmNNMMMMMm-/MMMMMMMmh+/ohm+     Terminal: gnome-terminal 
  .------------:://+-/++++++oshddys:      CPU: AMD Ryzen 7 5800H with Radeon Graphics (16) @ 4.463GHz 
   -hhhhyyyyyyyyyyyhhhhddddhysssso-       GPU: AMD ATI Radeon RX 6600/6600 XT/6600M 
    `:ossssssyysssssssssssssssso:`        Memory: 3459MiB / 15858MiB 
      `:+ssssssssssssssssssss+-
         `-/+ssssssssssso+/-`                                     
              `.-----..`
ReillyBrogan added a comment.Dec 16 2022, 7:25 PM
In T10452#199588, @GZGavinZhao wrote:
`------oMMMMMm/----------------`       Kernel: 6.0.11-225.current

Looks like you may have forgotten to switch the kernel at boot time.

GZGavinZhao added a comment.EditedDec 16 2022, 7:51 PM

Sorry for the confusion. I'm still on the secure boot kernel Joey tested with me, but I have been using 6.1 since you released it till yesterday's secure boot test, and it has been working well. I saw your message on Matrix and just want to repo that the new kernel runs fine with my system info.

infinitymdm added a subscriber: infinitymdm.Dec 17 2022, 12:10 AM

Looking good on my laptop

            -```````````                  marcus@mellor-xps 
          `-+/------------.`              ----------------- 
       .---:mNo---------------.           OS: Solus x86_64 
     .-----yMMMy:---------------.         Host: XPS 15 9560 
   `------oMMMMMm/----------------`       Kernel: 6.1.0-22.next 
  .------/MMMMMMMN+----------------.      Uptime: 5 mins 
 .------/NMMMMMMMMm-+/--------------.     Packages: 824 (eopkg) 
`------/NMMMMMMMMMN-:mh/-------------`    Shell: bash 5.1.16 
.-----/NMMMMMMMMMMM:-+MMd//oso/:-----.    Resolution: 3840x2160 
-----/NMMMMMMMMMMMM+--mMMMh::smMmyo:--    DE: Budgie 10.6.4 
----+NMMMMMMMMMMMMMo--yMMMMNo-:yMMMMd/.   WM: Mutter(Budgie) 
.--oMMMMMMMMMMMMMMMy--yMMMMMMh:-yMMMy-`   Theme: Plata-Noir [GTK2/3] 
`-sMMMMMMMMMMMMMMMMh--dMMMMMMMd:/Ny+y.    Icons: Papirus [GTK2/3] 
`-/+osyhhdmmNNMMMMMm-/MMMMMMMmh+/ohm+     Terminal: gnome-terminal 
  .------------:://+-/++++++oshddys:      CPU: Intel i7-7700HQ (8) @ 3.800GHz 
   -hhhhyyyyyyyyyyyhhhhddddhysssso-       GPU: NVIDIA GeForce GTX 1050 Mobile 
    `:ossssssyysssssssssssssssso:`        GPU: Intel HD Graphics 630 
      `:+ssssssssssssssssssss+-           Memory: 1653MiB / 31959MiB 
         `-/+ssssssssssso+/-`
              `.-----..`
Jacek added a comment.Dec 17 2022, 12:39 AM

Looking good for me too. I mean it is exactly as buggy as it was on the previous kernel, it is just a problematic laptop.

            -```````````                  jacek@chujwijacka 
          `-+/------------.`              ----------------- 
       .---:mNo---------------.           OS: Solus x86_64 
     .-----yMMMy:---------------.         Host: MiniBook X 
   `------oMMMMMm/----------------`       Kernel: 6.1.0-22.next 
  .------/MMMMMMMN+----------------.      Uptime: 3 hours, 43 mins 
 .------/NMMMMMMMMm-+/--------------.     Packages: 1129 (eopkg), 7 (snap) 
`------/NMMMMMMMMMN-:mh/-------------`    Shell: fish 3.5.1 
.-----/NMMMMMMMMMMM:-+MMd//oso/:-----.    Resolution: 1600x2560 
-----/NMMMMMMMMMMMM+--mMMMh::smMmyo:--    DE: Plasma 5.26.4 
----+NMMMMMMMMMMMMMo--yMMMMNo-:yMMMMd/.   WM: kwin 
.--oMMMMMMMMMMMMMMMy--yMMMMMMh:-yMMMy-`   Theme: Solus Dark [Plasma], Breeze [GTK3] 
`-sMMMMMMMMMMMMMMMMh--dMMMMMMMd:/Ny+y.    Icons: Papirus-Dark [Plasma], Papirus-Dark [GTK2/3] 
`-/+osyhhdmmNNMMMMMm-/MMMMMMMmh+/ohm+     Terminal: yakuake 
  .------------:://+-/++++++oshddys:      CPU: Intel Celeron N5100 (4) @ 2.800GHz 
   -hhhhyyyyyyyyyyyhhhhddddhysssso-       GPU: Intel JasperLake [UHD Graphics] 
    `:ossssssyysssssssssssssssso:`        Memory: 3301MiB / 11712MiB 
      `:+ssssssssssssssssssss+-
         `-/+ssssssssssso+/-`                                     
              `.-----..`
TClark77 added a subscriber: TClark77.Dec 17 2022, 10:29 PM

Looks good here. No more or less bugs on the XPS than before ;) Things work like they did on 5.15 and 6.0.
nVidia glx-driver-common 520.56.06.444

flatpaks updated successfully

            -```````````                  tracey@tlc-xps17-solus 
          `-+/------------.`              ---------------------- 
       .---:mNo---------------.           OS: Solus x86_64 
     .-----yMMMy:---------------.         Host: XPS 17 9710 
   `------oMMMMMm/----------------`       Kernel: 6.1.0-22.next 
  .------/MMMMMMMN+----------------.      Uptime: 13 mins 
 .------/NMMMMMMMMm-+/--------------.     Packages: 1790 (eopkg), 37 (flatpak) 
`------/NMMMMMMMMMN-:mh/-------------`    Shell: fish 3.5.1 
.-----/NMMMMMMMMMMM:-+MMd//oso/:-----.    Resolution: 2560x1600, 3440x1440 
-----/NMMMMMMMMMMMM+--mMMMh::smMmyo:--    DE: Plasma 5.26.4 
----+NMMMMMMMMMMMMMo--yMMMMNo-:yMMMMd/.   WM: KWin 
.--oMMMMMMMMMMMMMMMy--yMMMMMMh:-yMMMy-`   Theme: Solus Dark [Plasma], Mild-Gradient-GTK [GTK3] 
`-sMMMMMMMMMMMMMMMMh--dMMMMMMMd:/Ny+y.    Icons: [Plasma], breeze-dark [GTK2/3] 
`-/+osyhhdmmNNMMMMMm-/MMMMMMMmh+/ohm+     Terminal: konsole 
  .------------:://+-/++++++oshddys:      CPU: 11th Gen Intel i7-11800H (16) @ 4.600GHz 
   -hhhhyyyyyyyyyyyhhhhddddhysssso-       GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q 
    `:ossssssyysssssssssssssssso:`        GPU: Intel TigerLake-H GT1 [UHD Graphics] 
      `:+ssssssssssssssssssss+-           Memory: 3683MiB / 64047MiB 
         `-/+ssssssssssso+/-`
              `.-----..`
ReillyBrogan added a comment.Dec 28 2022, 3:40 AM

The test for this has ended. You can now uninstall all of the -next packages and switch your boot back to -current.

ReillyBrogan closed this task as Resolved.Dec 28 2022, 3:40 AM
ReillyBrogan added a comment.Dec 29 2022, 8:40 PM

Apologies, it has come to my attention that you should boot into the linux-current kernel BEFORE uninstalling linux-next.

Copyright © 2015-2021 Solus Project. The Solus logo is Copyright © 2016-2021 Solus Project. All Rights Reserved.