Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#77151 - [linux-hardened] AMDGPU fails to initialize with linux-hardened 6.1.6.hardened2-1

Attached to Project: Arch Linux
Opened by Voron Ravawynn (daechir) - Monday, 16 January 2023, 05:12 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 17 January 2023, 20:24 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
linux-hardened 6.1.6.hardened2-1 successfully boots to the console for login. When logging in and using startx the kernel omits the below error 3x, without starting Xorg, then fails back to the console login. It's unclear if this is a linux-hardened issue with AMDGPU or an upstream one. Downgrading to linux-hardened 6.0.0-6.0.19 series fixes the issue.

Additional info:
kernel: video: Unknown symbol wmi_evaluate_method (err -2)

Steps to reproduce:
Install linux-hardened 6.1.6.hardened2-1 from the core repository
Or self compile linux-hardened from github
This task depends upon

Closed by  Toolybird (Toolybird)
Tuesday, 17 January 2023, 20:24 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See comments
Comment by Toolybird (Toolybird) - Monday, 16 January 2023, 07:00 GMT
This looks like some kind of module loading screw up. Are you sure you haven't mixed'n'matched modules from different builds? What happens if you try a stock kernel (i.e. non-hardened)?
Comment by Voron Ravawynn (daechir) - Tuesday, 17 January 2023, 18:21 GMT
Hi,

As it turns out your theory was correct. Compared to previous kernel builds the video module now depends on the wmi module. De-blacklisting the wmi module solved the issue and now everythings working.

Loading...