January 2021 - openSUSE Kernel - openSUSE Mailing Lists

KMP for openSUSE Leap on OBS may need to include openSUSE key
by joeyli 24 Feb '21

24 Feb '21

Hi all, In a discussion with Max Lin, he has mentioned that the KMP on OBS (e.g. virtual box) can not be loaded by closing-gap kernel. That makes sense because the kernel binary is from SLE. For those KMP from SLE repo, the driver be signed by SLE key. It doesn't have problem to work with closing-gap kernel. But for those drivers from openSUSE Leap repo, they are signed by openSUSE key. The closing-gap kernel doesn't embed Leap kernel. Maybe the openSUSE Leap pubic key must be included in all KMPs in Leap repo? or at least all KMPs in Leap repo must depend on a openSUSE Leap sign key RPM. After KMP be installed and reboot, user can follow MOK manager's UI to enroll openSUSE Leap key. Any idea? Thanks a lot! Joey Lee

3 8

Leap 15.2 kernel-default-5.3.18-lp152.60.1.x86_64 problem with AMD Turks graphics
by Andreas Vetter 21 Jan '21

21 Jan '21

Hi, the update from kernel-default-5.3.18-lp152.57.1.x86_64 to kernel-default-5.3.18-lp152.60.1.x86_64 results in dark screens after smooth tock-tock-sound when I would expect switch of resolution on my 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] The system is running fine, so I can ssh to it and reboot and start with the old kernel where everything is fine. Is this a known problem (I had this already in 2019 or 2020, where it was solved by the next kernel update before I was able to report)? If not, I'll open a bug report. What information is needed for debugging this problem? -- Mit freundlichen Gruessen, Andreas Vetter

2 2

[opensuse-kernel] kernel lockdown and signed modules
by Giacomo Comes 18 Jan '21

18 Jan '21

Hi, I recently needed to rebuild one kmp package to add some changes. I did that and I have been using it without trouble. However, when I try to load such module on a UEFI system with secure boon enabled I get: modprobe: ERROR: could not insert '<module>': Operation not permitted and dmesg shows: Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 After some googling I found that I need to sign the module I build myself in order to make it load on a kernel with lockdown. I followed the instructions in: https://documentation.suse.com/sbp/all/html/SBP-KMP-Manual/index.html 8.2 Signing Module Object Files (UEFI Secure Boot) I created a key and certificate (8.2.1) I signed my KMP rpm (8.2.2) using modsign-repackage I installed the rpm: <name>-kmp-<flavor> together with <name>-ueficert then I imported the certificate installed by <name>-ueficert using mokutil mokutil --import /etc/uefi/certs/<file>.crt After reboot I enrolled the new certificate. Now the command: mokutil --list-enrolled shows two certificates: the 'openSUSE Secure Boot CA' and the one I have enrolled. However when I try to load my (now signed) kernel module I still get: Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 (but the command modsign-verify <module> gives: good signature) Am I doing something wrong? Is the documentation I'm following outdated? Is there a bug somewhere? I don't think the problem is with the UEFI bios as I get the same results on real hardware and in qemu. Any help is appreciated. Thanks. Giacomo

4 7

kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by Manfred Hollstein 06 Jan '21

06 Jan '21

Hi there, this is more like a heads up for everyone. I installed kernel 5.10.4 when it became available in Kernel:stable, so around 12:00 hrs CET at Jan 1st. I have since then had issues with three of my systems which never occured to me so far. The issue is, that there is no display anymore after some time (>= 20 minutes) (i.e. switching to another vtty doesn't work), and the network also doesn't work. Interestingly, one system (a Dell Latitude 5500 with an Intel Core(TM) i5-8365U CPU) still works OK. Common to all systems is the following: - openSUSE Leap 15.2 with all updates - builtin Intel graphics, no external graphics card - builtin Intel network card What's different is the graphics connector: - HDMI on two systems - DisplayPort on one system The Dell laptop - which works OK - is using its builtin display, so no HDMI or DisplayPort. I can only use the usual Ctrl-Alt-Print-... sequences to get them cleanly shut down and reboot. This never happened with any kernel from Kernel:stable up to 5.10.3! I'll be off for two days, but thought this might be interesting for other users/developers here. Cheers. l8er manfred

2 4