Linux 5.18.2

[jackpot51]

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.18.2

Please test the following:

• [x] Bluetooth suspend: https://github.com/pop-os/default-settings/pull/140
• [ ] NVIDIA 470: https://github.com/pop-os/nvidia-graphics-drivers-470/pull/7
• [ ] NVIDIA 510
• [x] VirtualBox: https://github.com/pop-os/virtualbox/pull/5
• [ ] ZFS

[linuxgnuru]

On a lemp9 with master added still isn't suspending if a bluetooth device has been paired. Found that if a bluetooth device is off or on doesn't make any difference. If no bluetooth device is paired or if bluetooth is turned off, then the lemp9 can suspend without any problem or if no device has been paired.

journalctl from suspending with bt mouse paired if it helps: journal.log

[n3m0-22]

Tested on gaze15, orpy4, and darp6 with new bluez from master. None will suspend with a bluetooth device paired, but they will all suspend with bluetooth on and no devices paired. This is the same as before.

[XV-02]

With the current bluez fixes (commit 17ba3e9) suspend fails with bluetooth devices attached. On the galp5-UMA this takes the form of rendering the machine unresponsive, and increasing temperature rapidly (presumably the CPU is pegged in some fashion), as fans start blasting shortly after the screen blanks during the suspend attempt. The machine required powering off.

I'm attaching the dmesg output for the boot immediately after the suspend attempt, in case there are any notable bluetooth configuration issues while things are spinning up. dmesg.txt

I'm also attaching the journalctl record for the session of the suspend attempt. I noted that the system reports suspending, then waking, then reports a last line of kernel: PM: suspend entry (shallow) journalctl.txt

As stated elsewhere, suspend with bluetooth on, but not attached to any devices functions.

I believe the behaviour during the suspend attempt on the galp5-UMA with attached bluetooth device is worse than on the current kernel release, however.

[jackpot51]

For bluetooth please see #148 where I added the two commits from #140

[n3m0-22]

All testing passed on gaze15, orpy4, and darp6 running 22.04 with the exception of the mic in not working. It is picked up by plugging the mic into the headphone jack selecting headset (with mic) but then there is no audio out. All suspend resume tests passed with the new bluetooth fix.

22.04_5.18.02.txt

[n3m0-22]

There is a dependency issue installing virtualbox on 21.10. virtualbox-pop-shop.txt virtualbox-apt-install.txt

[jackpot51]

@n3m0-22 is the same issue present on 22.04?

[jackpot51]

I will see about pulling virtualbox updates.

[n3m0-22]

Suspend on 21.10 with a bluetooth device paired works by adding the pop-default-settings_bluetooth-suspend script.

[jackpot51]

VirtualBox fix in https://github.com/pop-os/virtualbox/pull/5

[n3m0-22]

@jackpot51 Virtualbox was already installed on the machines I tested with 22.04 and ran fine. I just checked on a clean install with the this kernel and had no issue installing it.

[n3m0-22]

Dependency issue with the 470 driver on 22.04 and 21.10. 470-driver.txt

[jackpot51]

@n3m0-22 does https://github.com/pop-os/nvidia-graphics-drivers-470/pull/7 address it?

[n3m0-22]

Yes https://github.com/pop-os/nvidia-graphics-drivers-470/pull/7 tested and working on 21.10 and 22.04. Sorry I missed that.

[n3m0-22]

https://github.com/pop-os/virtualbox/pull/5 fixed the vitrualbox dependency issue.

[leviport]

Dev One has passed testing with this kernel

[n3m0-22]

All testing for 21.10 now passing. 21.10_5.18.02.txt

[n3m0-22]

All tests for 20.04 passed on orpy4, gaze15, and darp6.

Note: Suspend resume with bluetooth device paired required pop-default-settings_bluetooth-suspend script.

[XV-02]

With Pop 22.04, the Galp5 3050 does not reach a user session with 5.18.2 and the 510 nvidia driver (both 510.68.02 and 510.73.05 ) This is true with or without disk encryption.

This is not a problem with the 470 driver (either 470.103.01 or 470.129.06 )

[jackpot51]

@XV-02 is this still a problem with the 515 NVIDIA driver in https://github.com/pop-os/nvidia-graphics-drivers/pull/155?

[XV-02]

@jackpot51 It does persist with that version of the 515 driver as well.

I pulled a journalctl log for one such boot: journalctl515log.txt

[jackpot51]

I have a galp5 so I'll look into it.

[XV-02]

Adding another log for the galp5-3050 problem. It should be the same as previous (largely speaking) but I wanted to make doubly sure I went through the update chain correctly. journalctl515log2.txt

[linuxgnuru]

zfs-dkms fails to build on 5.18.2:

Setting up zfs-dkms (2.1.4-1pop1~1652992529~22.04~2d68e58) ...
Removing old zfs-2.1.4 DKMS files...
Deleting module zfs-2.1.4 completely from the DKMS tree.
Loading new zfs-2.1.4 DKMS files...
Building for 5.18.2-76051802-generic
Building initial module for 5.18.2-76051802-generic
ERROR (dkms apport): kernel package linux-headers-5.18.2-76051802-generic is not supported
Error! Bad return status for module build on kernel: 5.18.2-76051802-generic (x86_64)
Consult /var/lib/dkms/zfs/2.1.4/build/make.log for more information.
dpkg: error processing package zfs-dkms (--configure):
 installed zfs-dkms package post-installation script subprocess returned error exit status 10
Processing triggers for initramfs-tools (0.140ubuntu13) ...
update-initramfs: Generating /boot/initrd.img-5.18.2-76051802-generic
cryptsetup: WARNING: Resume target cryptswap uses a key file
kernelstub.Config    : INFO     Looking for configuration...
kernelstub           : INFO     System information: 

    OS:..................Pop!_OS 22.04
    Root partition:....../dev/dm-1
    Root FS UUID:........5ac2a25d-d037-45bd-9853-56e7e6e5fc18
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme0n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash
    Kernel Image Path:.../boot/vmlinuz-5.18.2-76051802-generic
    Initrd Image Path:.../boot/initrd.img-5.18.2-76051802-generic
    Force-overwrite:.....False

kernelstub.Installer : INFO     Copying Kernel into ESP
kernelstub.Installer : INFO     Copying initrd.img into ESP
kernelstub.Installer : INFO     Setting up loader.conf configuration
kernelstub.Installer : INFO     Making entry file for Pop!_OS
kernelstub.Installer : INFO     Backing up old kernel
kernelstub.Installer : INFO     Making entry file for Pop!_OS
Errors were encountered while processing:
 zfs-dkms

make.log file:

make.log

[XV-02]

Major R2 has passed our tests with this kernel update.

[XV-02]

Potentially barring one issue, Pang11 passed certification with the 5.18.2 kernel. Although not a regression, the Pang11 doesn't wake on integrated keyboard input when suspended with the lid open. The power button (with a slightly long press of ~ half a second) will wake the machine, as will and external keyboard, or closing and reopening the lid. However, once resumed, the keyboard and track pad worked every time, and it reached the suspend state through terminal commands, the power menu, and lid closure, and woke every time.

[jackpot51]

Obsolete, see #154