Linux 5.15 Testing Report

SuperJC710e

I know this task is closed, but there is some testing going on somewhere. I was finally able to get my Solus laptop back connected (unfortunately I couldn't test earlier because work sent me a laptop, with expectation that I use it, and that disrupted my usual setup). I installed the latest set from the temporary testing repository just to try it out on this legacy optimus machine with shared ntfs drives. My system boots and runs great. Switching to the new ntfs mount of the shared drives (triple boot with Windows and another testing linux) was seamless as well. I do not have the IgnoreABI option set currently.

Installation:

sudo eopkg install \
https://joshuastrobl.com/5.15-testing/linux-current-5.15.5-207-1-x86_64.eopkg \
https://joshuastrobl.com/5.15-testing/linux-current-headers-5.15.5-207-1-x86_64.eopkg \
https://joshuastrobl.com/5.15-testing/bbswitch-current-0.8-257-1-x86_64.eopkg \
https://joshuastrobl.com/5.15-testing/nvidia-390-glx-driver-32bit-390.144-122-1-x86_64.eopkg \
https://joshuastrobl.com/5.15-testing/nvidia-390-glx-driver-common-390.144-122-1-x86_64.eopkg \
https://joshuastrobl.com/5.15-testing/nvidia-390-glx-driver-current-390.144-122-1-x86_64.eopkg \
https://joshuastrobl.com/5.15-testing/nvidia-390-glx-driver-modaliases-390.144-122-1-x86_64.eopkg \
https://joshuastrobl.com/5.15-testing/v4l2loopback-common-0.12.5-220-1-x86_64.eopkg \
https://joshuastrobl.com/5.15-testing/v4l2loopback-current-0.12.5-220-1-x86_64.eopkg \
https://joshuastrobl.com/5.15-testing/virtualbox-common-6.1.28-220-1-x86_64.eopkg \
https://joshuastrobl.com/5.15-testing/virtualbox-current-6.1.28-220-1-x86_64.eopkg

System Info:

System:    Kernel: 5.15.5-207.current x86_64 bits: 64 Console: pty pts/0 Distro: Solus 4.3
Machine:   Type: Laptop System: LENOVO product: 243852U v: ThinkPad W530 serial: <filter>
           Mobo: LENOVO model: 243852U v: Win8 Pro DPK TPG serial: <filter> UEFI: LENOVO v: G5ETB3WW (2.73 ) date: 11/28/2018
Battery:   ID-1: BAT0 charge: 63.7 Wh (94.5%) condition: 67.4/85.9 Wh (78.5%)
CPU:       Info: Quad Core model: Intel Core i7-3740QM bits: 64 type: MT MCP cache: L2: 1024 KiB
           Speed: 2287 MHz min/max: 1200/3700 MHz Core speeds (MHz): 1: 2287 2: 1924 3: 2694 4: 2694 5: 2694 6: 2694 7: 2654
           8: 2694
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel
           Device-2: NVIDIA GK107GLM [Quadro K1000M] driver: nvidia v: 390.144
           Device-3: Acer ThinkPad Integrated Camera type: USB driver: uvcvideo
           Display: server: X.Org 1.20.13 driver: loaded: modesetting,nvidia resolution: 1920x1080~60Hz
           OpenGL: renderer: Quadro K1000M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.144
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel
           Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel
           Sound Server-1: ALSA v: k5.15.5-207.current running: yes
           Sound Server-2: PipeWire v: 0.3.40 running: yes
Network:   Device-1: Intel 82579LM Gigabit Network driver: e1000e
           IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi
           IF: wlp3s0 state: up mac: <filter>
Bluetooth: Device-1: Broadcom BCM20702 Bluetooth 4.0 [ThinkPad] type: USB driver: btusb
           Report: rfkill ID: hci0 state: up address: see --recommends
Drives:    Local Storage: total: 1.82 TiB used: 1.11 TiB (61.2%)
           ID-1: /dev/sda vendor: Seagate model: ST1000LX001-1EM164 size: 931.51 GiB
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
Partition: ID-1: / size: 228.1 GiB used: 204.18 GiB (89.5%) fs: ext4 dev: /dev/sdb5
Swap:      ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) file: /8GB.swap
Sensors:   System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 46 C
           Fan Speeds (RPM): fan-1: 2720
Info:      Processes: 302 Uptime: 10h 29m Memory: 31.18 GiB used: 3.42 GiB (11.0%) Shell: Bash inxi: 3.3.09

I would be happy to do additional testing (as time allows) if newer versions are available.

Additional note: the 2nd linux I have setup for testing/backup usage is currently an archlinux derivative (EndeavourOS w/Plasma), which is running up to the minute linux 5.15 and nvidia 390 without issues. (Nvidia is setup using optimus-switch which appears to run it similarly to the way Solus does.) Of course the boot process is nowhere as smooth or quick as on Solus (well, it's occasionally similar, but it's inconsistent).

brent

SuperJC710e I was in that original testing thread and was, I think, the only one who could not run the 5.15 with the nvidia 390's: no boot. Hopefully an aberration! I'd love to try it again, as well, b/c I'm nervous about the upcoming 5.15!

ReillyBrogan

brent You weren't the only person who encountered that issue. I believe we had one other person who encountered issues but they were mainly in IRC. I think the issue was likely determined to be an incompatibility between the simpledrm/fb changes and the Nvidia driver. Arch Linux disabled simpledrm which is likely why it works on EndeavorOS. There was also an issue with suspend on AMD GPUs that I do not believe has been identified yet.

brent

JoshStrobl but not in a rush to jump to a newer kernel until at least the AMDGPU issues that were identified have been resolved.

great to hear

ReillyBrogan You weren't the only person who encountered that issue... I think the issue was likely determined to be an incompatibility between the simpledrm/fb changes and the Nvidia driver.

equally great! thanks for your caution gents

JoshStrobl

Yea, we're going to be going with just FB_SIMPLE instead of SIMPLEDRM going forward due to there being clear issues with SIMPLEDRM, but not in a rush to jump to a newer kernel until at least the AMDGPU issues that were identified have been resolved.

SuperJC710e

JoshStrobl Thanks for the clear explanation! Unfortunately I do not have any AMD hardware to test on. However, I'd gladly test any future updates on my system to at least check the legacy nvidia 390 compatibility.

Just in case it's helpful, here's some info on the kernel and other packages on that eOS/Arch system:

$ uname -a
Linux node-laptop7 5.15.8-zen1-1-zen #1 ZEN SMP PREEMPT Tue, 14 Dec 2021 12:27:58 +0000 x86_64 GNU/Linux

Zen Kernel

$ grep -e 'SIMPLEDRM' -e 'FB_SIMPLE' /usr/lib/modules/5.15.8-zen1-1-zen/build/.config
# CONFIG_SYSFB_SIMPLEFB is not set
CONFIG_DRM_SIMPLEDRM=y

Arch Kernel

$ grep -e 'SIMPLEDRM' -e 'FB_SIMPLE' /usr/lib/modules/5.15.8-arch1-1/build/.config
# CONFIG_SYSFB_SIMPLEFB is not set
CONFIG_DRM_SIMPLEDRM=y

$ pacman -Qe | grep -v atm | grep -v firmware | grep -e nvidia -e xorg -e linux
lib32-nvidia-390xx-utils 390.144-1
linux 5.15.8.arch1-1
linux-headers 5.15.8.arch1-1
linux-zen 5.15.8.zen1-1
linux-zen-headers 5.15.8.zen1-1
nvidia-390xx-dkms 390.144-3
nvidia-390xx-settings 390.144-1
nvidia-installer-dkms 3.3.11-1
xorg-server 21.1.2-1
xorg-xinit 1.4.1-3
xorg-xinput 1.6.3-2
xorg-xkill 1.0.5-2
xorg-xrandr 1.5.1-2

JoshStrobl

Unfortunately not. What works for other operating systems isn't necessarily reflective of what will work for us, or they may be entirely ignoring these sorts of hardware issues because it works for everyone else.

SuperJC710e

JoshStrobl True enough! Thanks for the response!