[SOLVED] Nonexistent Unknown display causing issues on GNOME

segfaultenjoyer · 2024-08-13 14:56:36

After updating my system, I noticed my system suspend wasn't working for some reason. When I closed my laptop lid my system did not suspend, and I was not logged out. I figured out that it was because of this nonexistent monitor showing up in my Displays tab. I figured out if I select "Join" and then toggle the nonexistent monitor off, then my system suspend will work properly. However, I still seem to get some issues with my wallpaper and it seems to turn itself back on every once in a while. Therefore, I'd like to get this unknown display to stop being recognized. I read online some people were having a very similar issue apparently caused by nvidia drivers. However, I don't have a dedicated gpu in my system as it's a work laptop. My processor is an Intel i5-1340P, and my system is currently updated at the time of writing running kernel 6.10.4-arch2-1 and GNOME 46.4. Any help with this issue would be greatly apprecieated.

screenshot

EDIT:

Adding this to my kernel parameters fixed the issue for me. Thanks to V1del for the help

initcall_blacklist=simpledrm_platform_driver_init

Last edited by segfaultenjoyer (2024-08-15 23:37:05)

V1del · 2024-08-13 19:40:56

Potentially lol simpledrm. Try adding

initcall_blacklist=simpledrm_platform_driver_init

to your kernel parameters

segfaultenjoyer · 2024-08-14 00:10:41

V1del wrote:

Potentially lol simpledrm. Try adding
initcall_blacklist=simpledrm_platform_driver_init
to your kernel parameters

Thank you so much! This seems to work for me. Will keeping this in my kernel parameters cause any problems for me? Also, is this something that will be fixed in an update or will I need to keep this in my kernel parameters permanently? Thanks again.

Last edited by segfaultenjoyer (2024-08-14 00:11:15)

seth · 2024-08-14 07:57:47

That's the simpledrm device, it's supposed to be removed/replaced by the actual drm devicewhen it shows up, check your journal whether there're more related errors.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

segfaultenjoyer · 2024-08-16 23:47:35

seth wrote:

That's the simpledrm device, it's supposed to be removed/replaced by the actual drm devicewhen it shows up, check your journal whether there're more related errors.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Thanks for the heads up, I just edited it. I'm still a little confused about my previous two questions though. Will keeping this in my kernel parameters cause any problems for me? Will an update fix this issue and allow me to remove it from my kernel parameters again? Thanks for the help

seth · 2024-08-17 07:02:51

Will keeping this in my kernel parameters cause any problems for me?

No.
It's a fallback device to allow a wayland GUI when your graphics drivers are broken but
1. that just also masks the error
2. if you can't fix the system w/o a GUI, you're using the wrong distro

However and as mentioned: it's supposed to get replaced during the boot and you want to check the journal why that's not the case. "sudo journalctl -b 2" will show the journal of the second to last boot, so no need to restore the broken behavior in order to inspect the problem.

segfaultenjoyer · 2024-08-17 18:57:13

Thanks so much for the info seth! It was very helpful. My graphics seem to be working perfectly fine, so I think I'm just going to ignore the issue for now as everything seems to be working(also because I'm not sure what I should be looking for in my journal). Thank you again for all your help

ouille · 2024-10-10 00:20:19

I'm also seeing this issue, but nothing is popping out at me as an obvious problem in the journal. Here are some things related to simpledrm and some errors, though:

The following sequence of logs appears twice since last boot, about 10 seconds apart (at 16:35:30 and 16:35:40; including only the latter sequence because they looks the same). Looks pretty innocuous, but it's the only place where "simpledrm" appears in the logs:

Oct 09 16:35:40 quomp gnome-shell[1758]: Made thread 'KMS thread' realtime scheduled
Oct 09 16:35:40 quomp gnome-shell[1758]: Device '/dev/dri/card1' prefers shadow buffer
Oct 09 16:35:40 quomp gnome-shell[1758]: Added device '/dev/dri/card1' (i915) using atomic mode setting.
Oct 09 16:35:40 quomp gnome-shell[1758]: Added device '/dev/dri/card0' (simpledrm) using atomic mode setting.
Oct 09 16:35:40 quomp gnome-shell[1758]: Created gbm renderer for '/dev/dri/card1'
Oct 09 16:35:40 quomp gnome-shell[1758]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated
Oct 09 16:35:40 quomp gnome-shell[1758]: Created gbm renderer for '/dev/dri/card0'
Oct 09 16:35:40 quomp gnome-shell[1758]: Boot VGA GPU /dev/dri/card1 selected as primary
Oct 09 16:35:40 quomp gnome-shell[1758]: Obtained a high priority EGL context
Oct 09 16:35:40 quomp gnome-shell[1758]: Obtained a high priority EGL context

These logs from the gdm stream look slightly more relevant, but does not mention simpledrm directly:

Oct 09 16:35:14 quomp gdm[778346]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Oct 09 16:35:14 quomp gdm[778346]: Gdm: Freeing conversation 'gdm-password' with active job
Oct 09 16:35:39 quomp gdm[981]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Oct 09 16:35:42 quomp gdm[981]: Gdm: Child process -1061 was already dead.
Oct 09 16:35:42 quomp gdm[981]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed

Does this look relevant?

seth · 2024-10-10 06:56:39

https://bbs.archlinux.org/viewtopic.php … 7#p2189767

You're not supposed to have the simplydumb device around by the time gnome/gdm starts at all - but there's somthing more rotten about the framebuffer handling since 6.11
In doubt please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Arch Linux

#1 2024-08-13 14:56:36

[SOLVED] Nonexistent Unknown display causing issues on GNOME

#2 2024-08-13 19:40:56

Re: [SOLVED] Nonexistent Unknown display causing issues on GNOME

#3 2024-08-14 00:10:41

Re: [SOLVED] Nonexistent Unknown display causing issues on GNOME

#4 2024-08-14 07:57:47

Re: [SOLVED] Nonexistent Unknown display causing issues on GNOME

#5 2024-08-16 23:47:35

Re: [SOLVED] Nonexistent Unknown display causing issues on GNOME

#6 2024-08-17 07:02:51

Re: [SOLVED] Nonexistent Unknown display causing issues on GNOME

#7 2024-08-17 18:57:13

Re: [SOLVED] Nonexistent Unknown display causing issues on GNOME

#8 2024-10-10 00:20:19

Re: [SOLVED] Nonexistent Unknown display causing issues on GNOME

#9 2024-10-10 06:56:39

Re: [SOLVED] Nonexistent Unknown display causing issues on GNOME

Board footer