Bug 2346240 - KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Summary: KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 41
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-18 10:41 UTC by Fxzx micah
Modified: 2025-02-20 14:05 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fxzx micah 2025-02-18 10:41:45 UTC
1. Please describe the problem:

This issue occurs when I use wayvnc in nspawn.
"wayvnc -g -r -f 60"

2. What is the Version-Release number of the kernel:

kernel-6.12.13-200.fc41.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

The last kernel version that did not have this problem was kernel-6.12.11-200.fc41.x86_64.
Sorry I skipped kernel-6.12.12-200.fc41.x86_64 so I don't know if it works on kernel-6.12.12-200.fc41.x86_64.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

*Run wayvnc in an nspawn container with hyprland installed.*

Sorry, I don't know if wayvnc will come back to normal if I don't run it inside a container, because my host system's DE is Gnome and wayvnc doesn't support Gnome.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

I don't know, please let me know if it is necessary for me to perform this step.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Please let me know if this step is also necessary, as I actually checked the kernel logs and found no exception related to the problem.

Reproducible: Always

Comment 1 Fxzx micah 2025-02-20 14:05:25 UTC
Sorry, but I dug deeper into the issue and found that if I install the nvidia proprietary driver, the error reported becomes as follows:

[drm:nv_kthread_q_stop [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Cannot create sg_table for NvKmsKapiMemory 0x00000000206e8d05

And this error is no longer output by wayvnc but appears in the kernel error log.

That is, this is not a single kernel bug but is related to both the kernel and the nvidia kernel module.

Yes, I'm using a common dual graphics laptop.


Note You need to log in before you can comment on or make changes to this bug.