Black screen on boot!

Earlier today my screen went black after I tried to launch a game. I restarted and got a black screen post-bios, so I got into the TTY2 terminal, refreshed my mirrors, updated everything (only protontricks and firefox needed updating apparently), and rebooted, only to be greeted with the same black screen. Startx also brings me to the same black screen, video output seems to go out until I return to the TTY terminal. Now I’m confused.

I’m running Manjaro 5.10.141-1, with an i7 7700k, an RTX 2070 S, 32gb of ram.

mhwd -li yields video-nvidia 2021.12.18

inxi -G yields nvidia 515.65.01
xserver version 1.21.1.4
(and apparently it cannot find GL data, which I doubt is important)

Anything else I should try? Is my GPU dead?

Going to move to linux515 and redo my drivers to see if that fixes it.

Update: Did not affect problem, am now on linux 5.15.65-1 with the requisite closed-source nvidia drivers.

Also, added the nvidia modelules to mkinitcpio to get them to run before boot, no change.

“If you can’t find anything, open a new thread - remember to include what you have already tried.”
This was the first article I read - any tips?

1 Like

do you have a manjaro usb? it would be better to troubleshoot it from there…
so from manjaro usb, enter chroot:
manjaro-chroot -a
and post output from:
mhwd -l && mhwd -li && mhwd-kernel -li
and logs:
journalctl -b-1 -p4 --no-pager

I can, though I fail to see why the output would be different than getting it from TTY.
I did all that in the TTY and only found harmless bios errors (flashed my bios and fixed them, they disappeared on the next boot), and 2 errors regarding the nvidia drivers complaining that my 2070 super doesn’t have a USB-c port. (known, current, and harmless issue apparently).

I think I’ve already paraphrased the mhwd output in the OP, but I will redo and tell you.

Do you want me to chroot for the sake of ruling out video hardware? I’ll get to finding my USB drive and set up a live install from my laptop.

Edit:
mhwd -l yields:
video nvidia 2021.11.04
video nvidia 470xx 2021.11.04
video linux 2018.05.04
video modesetting 2020.01.14
video vesa 2017.03.12

1 Like

if you can post the outputs from tty, so post them …
we need to see what drivers are available, you mentioned that only video-nvidia is installed, althoug you have intel gpu too, so is intel disabled in bios? …
and are there any logs, when you type startx
and also we need to see the output from logs …
and by using the live usb, and booting with proprietary drivers, you can test if it works there …

1 Like

No output from startx, the video output immediately cuts out.
mhwd -li yields:
video-nvidia 2021.11.04
mhwd-kernel -li (now that I’m on linux515) yields:
5.15.65-1-MANJARO (linux515)
and it’s the only kernel currently as I had read a thread of someone removing their old kernels which had magically solved their nvidia video driver issues.

so you have only nvdia installed, why?
so now after you run startx check logs, what are the last logs?

My bad I had been looking at the p3 logs earlier when I said I had solved everything (had went through a different thread earlier)
after running startx and getting back into TTY there was nothing new in journalctl.
From looking at it, certain things stand out.
“CRITICAL: [ randr_update:0142] Get monitors reported 0 monitors. Falling back to single monitor mode.” (I only use a single monitor, but not 0 monitors…)
both “MDS cpu bug present and SMT on, data leak possible” and “MMIO Stale Data CPU bug present and SMT on, data leak possible” sound both worrying and irrelevant,
“nvidia: module license ‘NVIDIA’ taints kernel.” Well, I am using closed source.
Here’s an interesting one, there are 2 of these exact same ones.
“qt.qpa.xcb: QXcbConnection: XCB error: 148 (Unknown), sequence:193, resource id: 0, major code: 140 (unknown), minor code: 20”

If I’m to export the full text of this, you’re right, I’ll have to chroot. If none of this seems out of the ordinary I’ll chroot tomorrow (it’s very late here) and just copy and paste the full journalctl text.

Thanks for your wisdom so far.

Edit: Went into bios to make sure integrated graphics was disabled, it is disabled.

yes chrooting would be the best … but its suspicious that startx didnt shown any logs… it could be that you run out of space, so in tty run this command:
sudo pacman -Scc and then try again startx , so that we can rule this ‘out of space’ option out

I had seen that in another thread but figured it wouldn’t affect anything as space is one thing I have an abundance of, both ram and memory.

Tried it, no dice, still a dead output with startx.

One thing I forgot to mention is that I use i3 winman, if that’s relevant. (plasma is still around as a backup) Startx i3 yields the same result though.

so when you type startx, there are no logs from it? thats very suspicious…
are you using wayland?
i would reenable the intel gpu tommorow so that we can try booting only with the intel one, to test if it works with it, and thus the issue would be related only to nvidia…

i3 alone actually doesn’t support Wayland! I’ll get the drivers in order for the integrated graphics.

> 0000:01:00.0 (0300:10de:1e84) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
          video-nvidia            2021.11.04               false            PCI
    video-nvidia-470xx            2021.11.04               false            PCI
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
          video-nvidia            2021.11.04               false            PCI


Warning: No installed USB configs!
Currently running: 5.15.60-1-MANJARO (linux515)
The following kernels are installed in your system:
   * linux515
Sep 27 20:00:07 DesktopGame kernel: x86/cpu: SGX disabled by BIOS.
Sep 27 20:00:07 DesktopGame kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Sep 27 20:00:07 DesktopGame kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
Sep 27 20:00:07 DesktopGame kernel:  #5 #6 #7
Sep 27 20:00:07 DesktopGame kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 27 20:00:07 DesktopGame kernel: nvme nvme0: missing or invalid SUBNQN field.
Sep 27 20:00:07 DesktopGame kernel: nvme nvme1: missing or invalid SUBNQN field.
Sep 27 20:00:07 DesktopGame kernel: resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], which spans more than pnp 00:06 [mem 0xfdb00000-0xfdffffff]
Sep 27 20:00:07 DesktopGame kernel: caller pmc_core_probe+0xb7/0x6b0 mapping multiple BARs
Sep 27 20:00:07 DesktopGame kernel: EXT4-fs (nvme1n1p2): warning: mounting fs with errors, running e2fsck is recommended
Sep 27 20:00:07 DesktopGame kernel: vboxdrv: loading out-of-tree module taints kernel.
Sep 27 20:00:07 DesktopGame systemd-journald[276]: File /var/log/journal/b59a5f0c32be4e048d7a5d63a5087de5/system.journal corrupted or uncleanly shut down, renaming and replacing.
Sep 27 20:00:07 DesktopGame kernel: VBoxNetAdp: Successfully started.
Sep 27 20:00:07 DesktopGame kernel: VBoxNetFlt: Successfully started.
Sep 27 20:00:07 DesktopGame systemd-udevd[300]: /etc/udev/rules.d/99-fs2020_joystick.rules:1 Invalid key/value pair, ignoring.
Sep 27 20:00:08 DesktopGame kernel: nvidia: module license 'NVIDIA' taints kernel.
Sep 27 20:00:08 DesktopGame kernel: Disabling lock debugging due to kernel taint
Sep 27 20:00:08 DesktopGame kernel: 
Sep 27 20:00:08 DesktopGame kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 14:00:58 UTC 2022
Sep 27 20:00:08 DesktopGame kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Sep 27 20:00:09 DesktopGame kernel: nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
Sep 27 20:00:09 DesktopGame systemd[879]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Sep 27 20:00:09 DesktopGame kernel: usbhid 5-2:1.3: couldn't find an input interrupt endpoint
Sep 27 20:00:09 DesktopGame kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Sep 27 20:00:09 DesktopGame kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Sep 27 20:00:09 DesktopGame kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Sep 27 20:00:09 DesktopGame kernel: ucsi_ccg: probe of 0-0008 failed with error -110
Sep 27 20:00:10 DesktopGame kernel: Bluetooth: hci0: Reading supported features failed (-16)
Sep 27 20:00:11 DesktopGame kernel: kauditd_printk_skb: 277 callbacks suppressed
Sep 27 20:00:11 DesktopGame sddm-greeter[1195]: QFont::fromString: Invalid description '(empty)'
Sep 27 20:00:11 DesktopGame sddm-greeter[1195]: QObject: Cannot create children for a parent that is in a different thread.
                                                (Parent is QGuiApplication(0x7ffd7484d680), parent's thread is QThread(0x5649ce8da480), current thread is QThread(0x5649ce9b9310)
Sep 27 20:00:11 DesktopGame sddm-greeter[1195]: QObject: Cannot create children for a parent that is in a different thread.
                                                (Parent is QGuiApplication(0x7ffd7484d680), parent's thread is QThread(0x5649ce8da480), current thread is QThread(0x5649ce9b9310)
Sep 27 20:00:11 DesktopGame sddm-greeter[1195]: QObject: Cannot create children for a parent that is in a different thread.
                                                (Parent is QGuiApplication(0x7ffd7484d680), parent's thread is QThread(0x5649ce8da480), current thread is QThread(0x5649ce9b9310)
Sep 27 20:00:11 DesktopGame sddm-greeter[1195]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: file:///usr/share/sddm/themes/breath/components/VirtualKeyboard.qml:11:1: Type InputPanel unavailable
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: qrc:/QtQuick/VirtualKeyboard/content/InputPanel.qml:127:5: Type Keyboard unavailable
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: qrc:/QtQuick/VirtualKeyboard/content/components/Keyboard.qml:38:1: module "QtQuick.VirtualKeyboard.Plugins" is not installed
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: QXcbConnection: XCB error: 148 (Unknown), sequence: 192, resource id: 0, major code: 140 (Unknown), minor code: 20
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.21'
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Sep 27 20:00:12 DesktopGame sddm-greeter[1195]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Sep 27 20:00:19 DesktopGame kernel: kauditd_printk_skb: 14 callbacks suppressed
Sep 27 20:11:10 DesktopGame kernel: kauditd_printk_skb: 44 callbacks suppressed
Sep 27 20:11:44 DesktopGame kernel: kauditd_printk_skb: 100 callbacks suppressed
Sep 27 20:26:52 DesktopGame sddm-helper[1625]: [PAM] authenticate: Authentication failure
Sep 27 20:26:52 DesktopGame sddm[934]: Authentication error: "Authentication failure"
Sep 27 20:26:52 DesktopGame sddm[934]: Auth: sddm-helper exited with 1
Sep 27 23:06:21 DesktopGame sddm[934]: Error from greeter session: "Process crashed"
Sep 27 23:06:21 DesktopGame sddm[934]: Auth: sddm-helper crashed (exit code 15)
Sep 27 23:06:21 DesktopGame sddm[934]: Error from greeter session: "Process crashed"
Sep 27 23:06:21 DesktopGame sddm[934]: Auth: sddm-helper exited with 15
Sep 27 23:06:21 DesktopGame sddm[934]: Signal received: SIGTERM
Sep 27 23:06:31 DesktopGame sddm[934]: QProcess: Destroyed while process ("/usr/bin/X") is still running.
Sep 27 23:06:41 DesktopGame kernel: kauditd_printk_skb: 9 callbacks suppressed

Here’s what I got, took me a while to get around to doing the live-usb schtick.

On another note, the problem isn’t present on the live USB, and I redid my drivers on the main install, leading me to believe that it’s not necessarily an nvidia driver problem.

it shows that you have only nvidia installed even though you have also intel gpu…

it shows that the sddm/greeter crashed…
create a new test user and log with it and see if it works normally

I already threw up my hands and reinstalled and everything works OK now, thanks for the tips though!

1 Like

its always easier to just reinstall everything … glad you fixed everything

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.