• Pop!_Planet is still very much under development. Data for the wiki is being sourced from the Arch Linux and Ubuntu wikis, along with a bunch of completely unique content specific to Pop!_OS, and sourcing, converting and updating that content takes time; please be patient. If you can't find what you're looking for here, check the Arch Linux and Ubuntu wikis.
  • Welcome!

    I'll get straight to the point.

    When I started Pop!_Planet, I launched it because I saw a need for a centralized community for Pop!_OS. To be frank, I never expected the level of popularity it has achieved. Over the last year, we have gone from under 50 users, to almost 400 users. That's awesome! However... it also comes with a downside. We are rapidly running out of disk space on our server, and the bandwidth costs go up every month.

    Pop!_Planet is not affiliated with System76 in any way, and is funded completely out of pocket. From day one, I said that I'd never use on-site ads (I hate them as much as you do), so the only monetization we get is through donations. Right now, the donations we receive don't even cover our overhead.

    I know that most users will ignore this message, and that's ok. However, if even a few of our users are willing and able to donate a few dollars to help offset our expenses, it would be greatly appreciated.

    Support Pop!_Planet

    Thank you for your time,

    Dan Griffiths
    Pop!_Planet Founder

Thinkpad X1E docked display issues


New member
Apr 7, 2020
Hi all,

I am running Pop_OS 20.04 on my Thinkpad X1E (Gen 1) and I am using a Thinkpad Thunderbolt Workstation Dock (Gen 2) (40ANY230).

I have the BIOS set to use nVidia graphics only, Thunderbolt assist is turned on, and Thunderbolt security is set to off (I know this is not ideal, but trying to just get things working).

Everything is working fine with the dock except booting the laptop with the lid closed. I have what seem to be two independent problems:

- the laptop immediately going to sleep after LVM decryption (despite my /etc/systemd/logind.conf having "HandleLidSwitchDocked=ignore" in logind.conf)
- if I keep the lid open at boot (to stop the autosleep) then after I log into the desktop, all internal and external screens go black

If I plug in the dock after booting to the desktop, I can shut the lid of the laptop and work on the external screens fine, but I really want to just boot without opening the laptop when I'm at my desk.

I have detailed my testing in the table below, any help on the matter would be very much appreciated!

Side note, in dmesg I get lots of:

"nvidia-modeset: WARNING: GPU:0: AU Optronics Corporation (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible."

is that anything to do with the issues I am seeing?

Lid closed at bootLid open at boot
Laptop docked at boot- Laptop bootscreen shows on external displays
- LVM decryption prompt shows on the primary external display
- After inputting decryption pw the laptop immediately goes to sleep
- Waking the laptop using the power button on the dock wakes up the laptop (fan starts) and the external screens (backlight comes on) BUT no image is ever output to the screens, they remain black
- It seems like that Pop is at the user login screen, just not displaying it
- Laptop bootscreen shows on internal + external displays
- LVM decryption prompt shows on the primary external display
- User login screen shows on primary external dispaly
- After user login pw submitted all screens (internal and external) go black
- Disconnecting the dock results in the desktop showing on the internal display
- Reconnecting the dock after this shows the desktop across all internal and external displays
- I can then shut the laptop lid and work on just the external displays

Laptop docked after user loginN/A- Works fine, desktop shows up on external displays
- Laptop lid can then be closed and desktop still shows on external displays


New member
Apr 7, 2020
Hi again,

So I now think this is a Nvidia driver issue. I managed to SSH into my laptop after all screens had gone black and have found these lines from dmesg:

[   71.451396] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.

[  242.718494] INFO: task nvidia-modeset/:992 blocked for more than 120 seconds.
[  242.718502]       Tainted: P           OE     5.4.0-7642-generic #46~1598628707~20.04~040157c-Ubuntu
[  242.718505] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  242.718508] nvidia-modeset/ D    0   992      2 0x80004000
[  242.718513] Call Trace:
[  242.718526]  __schedule+0x2e3/0x740
[  242.718530]  schedule+0x42/0xb0
[  242.718537]  schedule_timeout+0x203/0x2f0
[  242.718541]  ? schedule_timeout+0x203/0x2f0
[  242.718548]  ? ttwu_do_activate+0x5b/0x70
[  242.718553]  __down+0x82/0xd0
[  242.718559]  down+0x47/0x60
[  242.718598]  nvkms_kthread_q_callback+0x66/0xe0 [nvidia_modeset]
[  242.718633]  _main_loop+0x8c/0x140 [nvidia_modeset]
[  242.718638]  kthread+0x104/0x140
[  242.718672]  ? _raw_q_schedule+0x70/0x70 [nvidia_modeset]
[  242.718676]  ? kthread_park+0x90/0x90
[  242.718682]  ret_from_fork+0x35/0x40

Does anyone have any pointers they can give me on this? I am running the latest nvidia driver (455.28) but with this error Pop is essentially a no go for me, I really don't to have to revert to using Windows full time (which I dualboot for games only currently and it works flawlessly with the dock/monitors).

The odd thing is my setup has worked perfectly fine in the past, though >1 year ago now. It seems this Arch forum post is referring to a similar issue and seem to have resolvedit by using older kernels / drivers?



Trusted User
Founding Member
Nov 23, 2018
It seems this Arch forum post is referring to a similar issue and seem to have resolvedit by using older kernels / drivers?
I was going to suggest you try that, seeing as Pop recently updated the NVIDIA driver. If you hit the space bar during boot can you select "old kern" and boot that?

Members online

Latest posts

Latest projects

Forum statistics

Latest member