F36 shows black screen on Lenovo T470p


I fresh-installed F35 on Lenovo T470p. Later upgraded to F36 successfully. But after couple of updates, can’t login to UI as it just shows black screen. I did search the threads here, although there were a few threads describing the symptoms, but not sure if any of them matches what I am seeing, hence those resoultions may not be applicable as I am NOT running proprietary nvdidia drivers.

Here are the details :slight_smile:

[[user@F36 ~]$  inxi -Fzx
  Kernel: 5.19.14-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-36.fc36 Desktop: GNOME v: 42.5 Distro: Fedora release 36 (Thirty
  Type: Laptop System: LENOVO product: 20J7S0FA00 v: ThinkPad T470p
    serial: <superuser required>
  Mobo: LENOVO model: 20J7S0FA00 serial: <superuser required> UEFI: LENOVO
    v: R0FET55W (1.35 ) date: 08/10/2021
  ID-1: BAT0 charge: 31.5 Wh (100.0%) condition: 31.5/47.5 Wh (66.3%)
    volts: 12.3 min: 10.8 model: SANYO 45N1767 status: full
  Info: quad core model: Intel Core i7-7820HQ bits: 64 type: MT MCP
    arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 2400 high: 2900 min/max: 800/3900 cores: 1: 2900 2: 900
    3: 2900 4: 2900 5: 2900 6: 2900 7: 2900 8: 900 bogomips: 46398
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Device-1: Intel HD Graphics 630 vendor: Lenovo driver: i915 v: kernel
    arch: Gen-9.5 bus-ID: 00:02.0
  Device-2: NVIDIA GM108M [GeForce 940MX] vendor: Lenovo driver: nouveau
    v: kernel arch: Maxwell bus-ID: 02:00.0
  Device-3: Realtek Integrated Camera type: USB driver: uvcvideo
    bus-ID: 1-8:4
  Display: x11 server: X.Org v: 1.20.11 with: Xwayland v: 22.1.3 driver: X:
    loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution:
    1: 1920x1080~60Hz 2: N/A
  OpenGL: renderer: llvmpipe (LLVM 14.0.0 256 bits) v: 4.5 Mesa 22.1.7
    direct render: Yes
  Device-1: Intel CM238 HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3
  Sound Server-1: ALSA v: k5.19.14-200.fc36.x86_64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.59 running: yes
  Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel
    bus-ID: 03:00.0
  IF: wlp3s0 state: up mac: <filter>
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-7:3
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
  Local Storage: total: 476.94 GiB used: 8.5 GiB (1.8%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000L7
    size: 476.94 GiB temp: 33.9 C
  ID-1: / size: 415 GiB used: 8.23 GiB (2.0%) fs: btrfs dev: /dev/nvme0n1p6
  ID-2: /boot size: 9.75 GiB used: 264.1 MiB (2.6%) fs: ext4
    dev: /dev/nvme0n1p4
  ID-3: /boot/efi size: 3.99 GiB used: 13.9 MiB (0.3%) fs: vfat
    dev: /dev/nvme0n1p3
  ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p5
  ID-2: swap-2 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
  System Temperatures: cpu: 36.0 C pch: 40.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 65535 fan-1: 0
  Processes: 310 Uptime: 1h 4m Memory: 31.21 GiB used: 1.94 GiB (6.2%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.2.1 Packages: 3
  note: see --rpm Shell: Bash v: 5.2.2 inxi: 3.3.21

[user@F36 ~]$ 

[user@F36 ~]$ lspci | grep -i --color 'vga\|3d\|2d'
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
02:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2)

I can access the console (via ctrl-alt-Fn4), and login, and the system is on network, but after logging into the UI, just shows black screen.

Will appreciate if anyone has experienced the same issue and know of a resolution. Can post more logs and info if needed.


1 Like

What happens if after you log in to the console you use startx ?

Thanks Jeff. Yes, “startx” lets me in the UI. But the qn is if I reboot, again will land into the same issue. So how do I fix it ?

Let me search my crystal ball!
Nope, the answer is not available!
You will have to try and see. I cannot guess for you.

Once we know then we can work on whatever is still going wrong, but no one can work on what if?

Can you look at your logs please and see if there are errors on boot, near when the login manager, gdm should be running?