Black screen on boot, turns off immediately with a power button

technicap · 2023-08-22 17:15:32

Hi, as I said in subject I have a problem during boot whre I can't even go to diffrent tty and without holding a power button it turns off . I tried chrooting into system and reinstalling kernel, and reinstalling nvidia drivers, propiatery.
Here is output of

 journalctl -b-1

http://ix.io/4Eg0
Thank you for your help

Last edited by technicap (2023-08-22 17:15:56)

zpg443 · 2023-08-22 17:26:45

You are using the nemesis kernel which is not supported.

technicap · 2023-08-22 17:32:51

I use kernel installed by pacman if it is not supported should I revert it or something?

headkase · 2023-08-22 17:36:27

zpg443 wrote:

You are using the nemesis kernel which is not supported.

technicap wrote:

I use kernel installed by pacman if it is not supported should I revert it or something?

nemesis is the hostname for your machine, you are using the standard kernel Arch ships.

seth · 2023-08-22 19:30:10

Aug 22 16:00:04 nemesis systemd-logind[604]: Power key pressed short.

The system powered down because of a signal from the power button - not sure about your OP, are you suggesting you did *NOT* push the power button or that you "had" to do that because otherwise the system was unresponsive?

Aug 22 15:59:56 nemesis kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
Aug 22 15:59:56 nemesis kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

Get rid of that: https://wiki.archlinux.org/title/NVIDIA … de_setting

If that doesn't fix it:

Aug 22 15:59:58 nemesis kernel: i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
Aug 22 15:59:58 nemesis kernel: i915 0000:00:02.0: [drm] [ENCODER:118:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
Aug 22 15:59:58 nemesis kernel: i915 0000:00:02.0: [drm] [ENCODER:125:DDI D/PHY D] is disabled/in DSI mode with an ungated DDI clock, gate it
Aug 22 15:59:59 nemesis kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to probe lspcon
Aug 22 15:59:59 nemesis kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 1
Aug 22 15:59:59 nemesis python3[641]: [82] INFO: Available modules: ['nouveau', 'bbswitch', 'nvidia', 'nvidia_drm', 'nvidia_modeset', 'nvidia_uvm']
Aug 22 15:59:59 nemesis python3[641]: [82] INFO: Unloading modules ['nvidia_drm', 'nvidia_modeset', 'nvidia_uvm', 'nvidia'] (if loaded)
Aug 22 15:59:59 nemesis kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Aug 22 16:00:01 nemesis kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Aug 22 16:00:01 nemesis kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes

There doesn't seem to be any output connected to the intel chip and the nvidia chip is apparently disabled by optimus-manager.

The result is

Aug 22 15:59:59 nemesis sddm[726]: Adding new display...
Aug 22 15:59:59 nemesis sddm[726]: Loaded empty theme configuration
Aug 22 15:59:59 nemesis sddm[726]: Xauthority path: "/run/sddm/xauth_LIaJcG"
Aug 22 15:59:59 nemesis sddm[726]: Using VT 2
Aug 22 15:59:59 nemesis sddm[726]: Display server starting...
Aug 22 15:59:59 nemesis sddm[726]: Writing cookie to "/run/sddm/xauth_LIaJcG"
Aug 22 15:59:59 nemesis sddm[726]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_LIaJcG -noreset -displayfd 16
Aug 22 15:59:59 nemesis sddm[726]: Failed to read display number from pipe
Aug 22 15:59:59 nemesis sddm[726]: Display server stopping...
Aug 22 15:59:59 nemesis sddm[726]: Attempt 1 starting the Display server on vt 2 failed
Aug 22 15:59:59 nemesis dbus-daemon[598]: [system] Would reject message, 3 matched rules; type="method_call", sender=":1.11" (uid=0 pid=726 comm="/usr/bin/sddm") interface="org.freedesktop.DBus" member="RequestName" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)
Aug 22 16:00:01 nemesis sddm[726]: Display server starting...
Aug 22 16:00:01 nemesis sddm[726]: Writing cookie to "/run/sddm/xauth_LIaJcG"
Aug 22 16:00:01 nemesis sddm[726]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_LIaJcG -noreset -displayfd 16
Aug 22 16:00:01 nemesis sddm[726]: Failed to read display number from pipe
Aug 22 16:00:01 nemesis sddm[726]: Display server stopping...
Aug 22 16:00:01 nemesis sddm[726]: Attempt 2 starting the Display server on vt 2 failed
Aug 22 16:00:03 nemesis sddm[726]: Display server starting...
Aug 22 16:00:03 nemesis sddm[726]: Writing cookie to "/run/sddm/xauth_LIaJcG"
Aug 22 16:00:03 nemesis sddm[726]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_LIaJcG -noreset -displayfd 16
Aug 22 16:00:03 nemesis sddm[726]: Failed to read display number from pipe
Aug 22 16:00:03 nemesis sddm[726]: Display server stopping...
Aug 22 16:00:03 nemesis sddm[726]: Attempt 3 starting the Display server on vt 2 failed
Aug 22 16:00:03 nemesis sddm[726]: Could not start Display server on vt 2
Aug 22 16:00:04 nemesis sddm[726]: Signal received: SIGTERM

But this is a notebook, isn't?
=> Try the behavior w/ the LTS kernel to rule out a regression in the i915 module.
Then remove optimus-manager and try to only boot the multi-user.target (2nd link below)

technicap · 2023-08-22 20:18:39

It is notebook. And I put in kernel parameter to disable that nvidia drm thing. Didn't work so tried a second option but I don't know how to switch to lts kernel. Is it as simple as installing it's package or do I need to do something more?
Edit:
I am in system with lts kernel and Optimus manager removed

Last edited by technicap (2023-08-22 20:27:18)

zpg443 · 2023-08-22 20:27:51

technicap wrote:

It is notebook. And I put in kernel parameter to disable that nvidia drm thing. Didn't work so tried a second option but I don't know how to switch to lts kernel. Is it as simple as installing it's package or do I need to do something more?

Instead of

pacstrap -K /mnt base linux linux-firmware

Use

pacstrap -K /mnt base linux-lts linux-firmware

seth · 2023-08-22 20:31:52

Didn't work so … am in system with lts kernel and Optimus manager removed

Please post an updated system journal.

technicap · 2023-08-22 20:40:30

Here is newest system journal
http://ix.io/4EgF

seth · 2023-08-22 20:45:38

Aug 22 22:34:19 nemesis systemd-modules-load[306]: Failed to find module 'nvidia-uvm'

You forgot to install nvidia-lts

[drm] *ERROR* Failed to probe lspcon

is still there,

[drm] Cannot find any crtc or sizes

is gone, though.
You're also only booting the multi-user.target, do get some output on the monitor?

technicap · 2023-08-22 20:51:45

Yes, I have output on monitor. I have console and I will install nvidia-lts right away

Edit:switching to graphical.target makes system freeze at cockpit boot messege
Edit 2: I didn't try with main kernel

Last edited by technicap (2023-08-22 21:02:40)

seth · 2023-08-22 20:53:25

Try to start the graphical.target afterwards.
If that works but consistently fails w/ the main kernel, this would suggest an i915 bug.

technicap · 2023-08-22 21:14:22

With main kernel it doesn't even get me into console with muli-user.target

seth · 2023-08-22 21:23:46

- Aug 22 22:34:21 nemesis kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
+ Aug 22 15:59:58 nemesis kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])

Is this a recent regression (ie. when updating to 6.4.11-arch2-1) ? What was the last "good" kernel?

technicap · 2023-08-22 21:25:16

Last good was 6.4.2. And yes it happened after updating a system.

seth · 2023-08-23 06:43:52

If you're lucky this is https://gitlab.freedesktop.org/drm/intel/-/issues/9134 - you could try 6.4.9 and maybe ask the reporter what her previous kernel was.
This would however also mean that it's not https://gitlab.freedesktop.org/drm/inte … te_2052458 (which apparently affected 6.4.1 while you were still good on 6.4.2)

technicap · 2023-08-23 10:07:03

I found 6.4.9 arch kernel.
Also tell me if I am doing something wrong with downgrading my kernel.
1. Downgrading packages of linux and linux-headers with pacman
2. Editing /boot/loader/entries/arch.conf with

 linux /vmlinuz-linux
initrd  /initramfs-linux-fallback.img

at the end of the file
3. Reboot into normal system

Edit: I didn't do the second step and I tried going back to 6.4.2 same behavior as 6.4.11 and 6.4.9 has the same behavior

Last edited by technicap (2023-08-23 10:20:15)

seth · 2023-08-23 11:43:23

You'll also have to downgrade the nvidia packages accordingly, editing the bootloader isn't required since you're replacing the kernel file, you're not renaming it or adding a new one.

How sure are you then about

Last good was 6.4.2.

?

technicap · 2023-08-23 12:04:01

Because it was the newest besides 6.4.11 in my pacman cache
Edit: I checked and I have 6.4.1 as the oldest in cache, but I know it worked too, same as 6.4.2.so I'm checking just to be safe if misremembered somehow
Edit 2: 6.4.1 doesn't work

Edit 3: the system gets to console Only on lts and Only on multi-user.target

Edit 4: 6.3.9 kernel works on graphical target, but I don't have control over backlight (I have keys that usually can do this if you press Fn button). My nvidia gpu is regognized by system as pci device, but it can't communicate with driver, I think. Tried reinstalling it with no luck.

Edit 5: I assumed 6.4.2 was last good because it was newest before 6.4.11 in my cache before installing 6.4.9

Edit: nvidia gpu is recognized. I forgot to downgrade the driver. No back light control and sddm is active, but doesn't drop me to greeter, I think that's what's called.

Edit 6: I have greeter after installing optimus-manager

I'm in my desktop and everything seems to work fine.
Any idea what the heck happened in 6.4.11 that my system didn't want to work? If so is it me or a bug?

Last edited by technicap (2023-08-23 13:53:55)

Arch Linux

#1 2023-08-22 17:15:32

Black screen on boot, turns off immediately with a power button

#2 2023-08-22 17:26:45

Re: Black screen on boot, turns off immediately with a power button

#3 2023-08-22 17:32:51

Re: Black screen on boot, turns off immediately with a power button

#4 2023-08-22 17:36:27

Re: Black screen on boot, turns off immediately with a power button

#5 2023-08-22 19:30:10

Re: Black screen on boot, turns off immediately with a power button

#6 2023-08-22 20:18:39

Re: Black screen on boot, turns off immediately with a power button

#7 2023-08-22 20:27:51

Re: Black screen on boot, turns off immediately with a power button

#8 2023-08-22 20:31:52

Re: Black screen on boot, turns off immediately with a power button

#9 2023-08-22 20:40:30

Re: Black screen on boot, turns off immediately with a power button

#10 2023-08-22 20:45:38

Re: Black screen on boot, turns off immediately with a power button

#11 2023-08-22 20:51:45

Re: Black screen on boot, turns off immediately with a power button

#12 2023-08-22 20:53:25

Re: Black screen on boot, turns off immediately with a power button

#13 2023-08-22 21:14:22

Re: Black screen on boot, turns off immediately with a power button

#14 2023-08-22 21:23:46

Re: Black screen on boot, turns off immediately with a power button

#15 2023-08-22 21:25:16

Re: Black screen on boot, turns off immediately with a power button

#16 2023-08-23 06:43:52

Re: Black screen on boot, turns off immediately with a power button

#17 2023-08-23 10:07:03

Re: Black screen on boot, turns off immediately with a power button

#18 2023-08-23 11:43:23

Re: Black screen on boot, turns off immediately with a power button

#19 2023-08-23 12:04:01

Re: Black screen on boot, turns off immediately with a power button

Board footer