8000 Not working with kernel 6.12.20-amd64? · Issue #278 · strongtz/i915-sriov-dkms · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Not working with kernel 6.12.20-amd64? #278

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
derzwen opened this issue Mar 29, 2025 · 4 comments
Open

Not working with kernel 6.12.20-amd64? #278

derzwen opened this issue Mar 29, 2025 · 4 comments

Comments

@derzwen
Copy link
derzwen commented Mar 29, 2025 •
edited
Loading

Hi, did a fresh debian testing installation today in a Proxmox VM. In the past I had no problems getting SR-IOV working on other debian stable VMs. But with this kernel in testing it does work. DKMS module is installed but somehow not loaded.

cat /proc/cmdline 

BOOT_IMAGE=/vmlinuz-6.12.20-amd64 root=/dev/mapper/testing--vg-root ro quiet i915.enable_guc=3 module_blacklist=xe
uname -a

Linux testing 6.12.20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.20-1 (2025-03-23) x86_64 GNU/Linux
dkms status

i915-sriov-dkms/2025.03.27, 6.12.20-amd64, x86_64: installed (Original modules exist)
dmesg | grep -E "i915|xe|VGA|Display"

[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-6.12.20-amd64 root=/dev/mapper/testing--vg-root ro quiet i915.enable_guc=3 module_blacklist=xe console=tty0 console=ttyS0,115200
[    0.000000] NX (Execute Disable) protection: active
[    0.000097] MTRR map: 4 entries (2 fixed + 2 variable; max 18), built from 8 variable MTRRs
[    0.010004] PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xefffffff]
[    0.014025] Kernel command line: BOOT_IMAGE=/vmlinuz-6.12.20-amd64 root=/dev/mapper/testing--vg-root ro quiet i915.enable_guc=3 module_blacklist=xe console=tty0 console=ttyS0,115200
[    0.111451] PCI: ECAM [mem 0xe0000000-0xefffffff] (base 0xe0000000) for domain 0000 [bus 00-ff]
[    0.416756] pci 0000:00:01.0: vgaarb: setting as boot VGA device
[    0.416756] pci 0000:00:01.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[    0.416756] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
[    0.419733] system 00:04: [mem 0xe0000000-0xefffffff window] has been reserved
[    0.716793] fb0: EFI VGA frame buffer device
[   10.590381] systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
[   10.896354] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[   10.925372] Module xe is blacklisted
lspci | grep UHD

01:00.0 VGA compatible controller: Intel Corporation Alder Lake-S GT1 [UHD Graphics 730] (rev 0c)

What am I missing?
@bbaa-bbaa
Copy link
Contributor

Try modprobe i915 and upload latest dmesg here.
The result of modinfo i915 is also useful.

@derzwen
Copy link
Author
derzwen commented Mar 29, 2025 •
edited
Loading

Figured it out 🤦‍♂️ modprobe i915 gave the hint. Quick googling revealed the underlaying problem. Secure boot was enabled in that VM.

modprobe i915

modprobe: ERROR: could not insert 'i915': Key was rejected by service

Is this a know issue that the module does not work with secure boot enabled? If yes, I didn't find anything in the docs. Maybe add a hint there?

Thanks for the quick help anyway 💪👌 BTW: I'm very glad that this module exists and very well works!

@bbaa-bbaa
Copy link
Contributor
bbaa-bbaa commented Mar 29, 2025 •
edited
Loading

The simplest way is to disable Secure Boot.
If you need Secure Boot, you will need to maintain your own Secure Boot keys and use the correct private key to sign the module.
More information can be found here: https://github.com/dell/dkms?tab=readme-ov-file#module-signing
https://wiki.debian.org/SecureBoot#DKMS_and_Secure_Boot

@derzwen
Copy link
Author
derzwen commented Mar 29, 2025

Yeah, I don't need it so I just disabled it. Issue can be closed 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@derzwen @bbaa-bbaa
0