Pop!_os added an unknown display that cannot be deleted #3257
Comments
|
I wonder if this is related to some of the other display issues we saw with the 6.8.0 update. If you boot the previous kernel, does it act normally again? Also, can you describe your hardware? |
|
I'm pretty sure I do not have an old enough kernel to change things as I reinstalled my OS (I totally screwed it up trying all the fixes I could look up). Here's what I have. I've never reverted to an old kernel before and after screwing with my system all weekend I'm kind of soured on doing anything else for awhile. I've had other problems crop up and after a few months and some updates they are usually fixed so I'm hoping this will be the case here too. rick@pop-os:~$ find /boot/vmli* Here's my system info (short) rick@pop-os:~$ sudo lshw -short
|
|
I'm experiencing the same issue here. |
|
@RikardtheCard I managed to temporarily fix the issue (until the next boot) by just running |
|
Thanxs vanrohan, I'll give that a try. I wonder if I opened up grub as an admin whether (GRUB_CMDLINE_LINUX=--output None-2-1 --off) would turn off the display forever? I don't know enough about linux to know if that would work. |
|
sudo xrandr thing didn't work for me. This is what I got back- (Error of failed request: BadMatch (invalid parameter attributes) |
|
I'm also experiencing this behavior. Feel free to ping me if you need any debugging :) |
|
Ha on me! I didn't even think of looking at the nvidia settings. I can't figure out how to use it to delete or disable the unknown display. It's marked as prime display so I can't change it with nvidia settings. I tried setting my real display as the prime but had a popup tell me it couldn't save the file. Pop!_os is wayland but it tried to save as x11. Weird. I wish I understood this stuff more; as it is, I'm just lost and expect to just have to put up with it until (maybe) a fix is in the works. |
|
I can't figure out why this will not work for me.........xrandr --output None-1-1 --off |
|
I used the system settings to change the primary display, and the nvidia one to posisition them since the system dialog just wouldn't set their positions correctly |
|
Here's the idiotic thing here. All I can do at this point is laugh because it makes no sense att all!
|
|
Oddly, my stuck display is 1024*768. I ended up covering it with my ultrawide display, since it was the only thing that wanted to work
|
|
Well, it's been entertaining at least. My cursor goes past the edge of my screen at the top where the other screen is supposed to be so at least it's better than before I reinstalled my OS. Prior to that I had 2 27" monitors side by side and had to scroll a whole screen over to reach the other side! With your 1024x768 screen off to the side does your cursor move over to it or does the cursor follow the edge of your Acer? Anyways, I'm going off the computer so, have a good one! |
|
I booted into my last available kernel Linux version 6.6.10-76060610-generic and the phantom display is gone. |
|
the only other one I have is 6.2.6-76060206-generic. can I run (sudo update-initramfs -u -k 6.2.6-76060206-generic)? I've never done this before so I'm not sure. Running 6.8.0-76060800daily20240311-generic right now. |
I used this command without sudo being my ghost screen None-1-1. It worked, the ghost display is still present in settings but it doesn't seem to mess anymore with my system. It still works after a reboot. Thank you for the temporal fix! |
I started experiencing this with the 6.8.x kernel update. I do think it is related. I attempted to go back to 6.6.10 to test when I first experienced this, but for whatever reason, it wouldn't load. I never got a login screen, just a cursor. I had to get into recovery, chroot and get my kernel reset to the 6.8.x kernel to get the boot to work and be able to log back in. |
|
Oh boy, sad didnt find this place before! Wellcome to linux world I guess... I wasted all the weekend trying to figure out how to fix this issue. Currently pressing spacebar on boot to load old kernel: This kernel was causing me to not be able to mirror my screen (cos of that phantom-unknown screen): Seems it only happens when I boot with the monitor on attached to the nvidia gpu, if I turn off that monitor and boot with the monitor on that is attached to the amd gpu the unknown screen is gone. UPDATE: creating and configuring a xorg.conf file solved the problem for me, which I had to do it anyways sometime for undervolting the gpu and extra the x server screen for the surround sound output to the avr. Everything seems fine now <3 |
|
Hey guys, wanted to let you know that |
|
This seems really likely to be an upstream kernel/nvidia driver issue. I'm not sure when it happened, but at some point a "PRIME" display started showing up for me. It definitely wasn't there a year ago. |
I'm glad my temporal solution worked. Did you also have glitches on the decrypt and login screen? Relating to your question, I guess it's related somehow to the nvidia drm and the kernel change. Probably Pop devs have a better explanation. |
Writing in to confirm this resolved my issue as well. A recent update caused my tablet to become offset pretty bad within Krita and I couldn't for the life of me figure out what happened. After seeing the small phantom display hidden away, along with my spanned desktop background being shifted a similar distance, I got suspicious and found this thread. |
|
@Nuxmin hey there, didn't set up encryption so can't say for sure, but login screen seems normal to be |
|
I'm not sure... But I believe they've done something in recent updates. The display still appears but no longer seems to be interfering with my system. |
|
FWIW, here's my report in the chat with some details. |
Permanently get rid of 'Unknown Display' from Settings application and eliminate mouse cursor from exiting screen:1. Find the name of the offending displayOpen a terminal and type: ~$ In my case, the display was listed as "None-2-1". 2. Create an Xorg Configuration FileCreate a file CTRL+S, then CTRL+X to save and exit. This file tells Xorg to completely ignore the "None-2-1" display at the next login. 3. Restart computer (or log out and back in, apparently) and the ghost display should be gone!edit: I was informed a complete restart isn't necessary. |
|
Thank you, this was very helpful. It worked for me, although only if I put the config file in |
|
I have an XP-Pen Artist 12 display tablet that I use along side my main Monitor. I was having issue recently with my Display Tablet, was unable to mirror the screens. The solution provided by @KeithDobbelaere works. Now my Unkown display (None-1-1) is gone, I am able to work with both my screens now. 😄
|
|
Thank you, @KeithDobbelaere, that worked for me too. Also logging out and in was sufficient to apply changes. |
|
For me, Anyone able to weight in? |
|
I tried the xorg.conf trick but it didn't work for me. I put it in etc and in usr x11...neither worked. Drats! (knackstedt, what does sudo kernelstub -a "nvidia_drm.fbdev=1 do?) Well, at least I'm learning stuff. I just learned how to create a conf file, so, that's something. |
|
@RikardtheCard, was the problem display listed when you queried X Resize and Rotate(xrandr)? It might not be "None-2-1" in your case. |
|
@KeithDobbelaere I changed it... mine was "None1-1" |
|
I am so new here I don't even know how to reply to someone properly. There's no reply button on anyone's comment. Is it just as simple as typing @ and then their username? Because that's what I've been doing. Anyways I've gotten used to making sure my cursor doesn't go over the top right of my screen because it gets lost in neverneverland. I suppose someone will get a fix at some point. knackstedt came up with this but I am wary of trying it because I don't know what it does "sudo kernelstub -a "nvidia_drm.fbdev=1" I just don't want to crash my system again. I'm no expert I'm just flying by the seat of my pants when it comes to problems like this. |
You can click the 3 horizontal buttons on the comment and "Quote Reply". It won't specifically link the message though IIRC That setting enables DRM on the kernel, which seems to be a regression in the latest version of the kernel (Frustrating that nobody caught this) It was originally documented from the Arch linux wiki from what I can tell, but it's relevant for debian as far as the kernel setting goes |
This resolved it for me, where trying to run |
I tried "sudo kernelstub -a "nvidia_drm.fbdev=1" it said kernelstub was not found |
|
Well, thanx everyone for all your input. I've at least leaned some linux stuff and had my first experience on github. |
|
Well I appreciate everyone on github. It's nice to know I wasn't the only one having the problem. I read everything everyone wrote and tried the stuff I could sort of understand. I'm sorry if you feel slighted by me in any way. In the beginning I thanked people because there wasn't many writing on the issue. I didn't try the kernelstub thing a try for awhile because I was a bit scared about what could happen to my system. By the time I got around to it (it didn't work) there were many more entries and I had pretty much given up fixing the problem. In the future I will try to acknowledge all the help I get. Thank-you for your help Nuxmin.
[Rick_Face_small.png]
Sent with [Proton Mail](https://proton.me/) secure email.
…On Thursday, April 18th, 2024 at 6:48 PM, Nuxmin ***@***.***> wrote:
Well... I tried my best to help because at the end the first solution I got from a kind person didn't work for me. As I find most people didn't even read my long post trying to help. Not only that, it also led to people saying people who just reposted what I did try to help came with that temporal fix.
A bit appreciation would be welcome. Or at least made me know it didn't work instead of ignoring the post completely.
—
Reply to this email directly, [view it on GitHub](#3257 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BHOXAUL2WHAZEYPMMJ7Q47DY6BZXTAVCNFSM6AAAAABFPXZM6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGYYDIMZXGE).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
I am finding this comment system confusing. I reply to an email and find it posted here (and there it is...my email...for all to see). There is no reply button; instead after inquiring another member lets me know I have to use the "Quote Reply". I'm just finding this counterintuitive. As this display issue has not been addressed am I now supposed to close the issue? or just leave it open? Thanx everyone for participating. |
|
Having the exact problem all of a sudden. Here's my
|
|
@RikardtheCard don't worry, github is still kind of a dev platform, and yes please leave this issue open for further discussion :) |
Thanks. It was interesting for me and I learned a few things along the way. |
Thanks for the help! This solved my issue completely. In my case, the display was listed as "None-1-1". |
Well, you know, MrLekkim, I've tried this twice before and for some reason I decided to try again after reading your post. Wonders never cease to surprise! It actually worked this time for me. I have no idea why it didn't work before; the only thing I did different this time was I did it from the command line instead of going in the folder and creating it (it didn't exist when I looked). So, a thank-you to all who listed that as the fix. |
|
Hey guys, I have a small update: After hopping back to Pop, I randomly noticed today that the fbdev fix made my boot much longer, which now takes about a minute. After putting in the decryption passphrase, the monitor would change mode (goes black for half a sec), and when it reactivates, the screen is still the output of cryptsetup, and only after half a minute, the screen would go to GDM, and after logging in, the screen would again show cryptsetup output for 10 seconds, and then to GNOME. Everything else seems fine... What do we do now? Thanks! Edit: Will be using the xorg config file fix for now... Next GPU will probably be AMD :P |
|
This only happens when manually restarting the shell. I've tried the I've tried settings my display mode as |
|
I found creating the Xorg configuration file removed my "Unknown Display" on Pop!_os, and that was great until I realized it had other side effects, my streaming application "Sunshine" now just gives me a black screen, and I get other monitor errors when trying to specify the single monitor I have. Removing this configuration file restores functionality, but the "Unknown Display" returns. |
|
If this is still a problem for anyone - this worked for me: and on the end of options need to add DO NOT add PS: this solution above also fixed weird screen flickering when entering boot screen. |
|
I'm on Fedora now, there isn't this ghost monitor bug but has anyone tried adding the nvidia modules to the initramfs? It fixed the broken decryption screen for me on Fedora a while ago, and combined with nvidia_drm.modeset=1 this might be a good workaround |
|
are you guys sure that creating will not cause any issues when actually connecting an additional display? |
|
Disabling with xorg.conf.d worked for me. But also disabling with kernel parameter worked for me on Ubunt 24.04: To undo the change: |
|
I have updated my kernel to |
Same here : ) |
|
(I just finally rebooted my desktop going from a 6.5.x to 6.8.x kernel on my Ubuntu 22.04 system). Just an FYI, the nvidia-settings program indicates the second screen is for Nvidia Prime. (I wondered why my remote desktop had become extra-wide 8-) .) I'm using a Nvidia GTX1650, and the monitor is hooked up to there (nothing hooked up to the onboard video.) But the BIOS doesn't disable the on board Coffee Lake GPU. So presumably with the 6.8 kernel something in the driver stack decides I want to run hybrid graphics. Not that it effects the fix for it or anything, but I thought it's nice to have some insight into WHY it's doing what it's doing. Have a good one! |
and others
Pop!_os 22.04 I am a Linux novice and this is my first time using Github so let me know how I could have improved this post.
Unknown Display
I now have an Unknown Display showing up and cursor is not constrained within screen border
suddenly showed up after OS update on March 29th 2024
tried getting rid of the unknown display but couldn't; ended up totally messing up system; reinstalled Pop!_os 22.04 and after update unknown display showed up and cursor is restrained within display top, bottom and left side but, on the right it is confined within display on the bottom but cursor will move off the display area at the top right
I am sure the problem is caused by the Unknown Display showing up under display settings. The display settings indicate I am using a single display but cursor behavior suggests otherwise.
I tried xrandr --query and here is the output (it looks like None-1-1 was added but, not by me)
Screen 0: minimum 8 x 8, current 2560 x 1080, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
1920x1080 60.00*+ 59.94 50.00
1680x1050 59.95
1440x900 59.89
1280x1024 75.02 60.02
1280x960 60.00
1280x800 59.81
1280x720 60.00 59.94 50.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 75.00 72.81 59.94 59.93
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
None-1-1 connected (normal left inverted right x axis y axis)
640x480 60.00 +
The text was updated successfully, but these errors were encountered: