[SOLVED]Black screen on boot.

[JustCauseWhyNot]

Syslog-ng. Although I'm not entirely sure I've setup it up.

[figueroa]

Is it running? Look at the output of rc-update. The configuration files are at /etc/syslog-ng/. I'm running metalog which is quite different, but I think more users are using syslog-ng which should give you the traditional /var/log/messages and /var/log/syslog.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi

[pietinger]

JustCauseWhyNot,

can you try again with new 5.17.2 ?

(its a very huge update; very seldom; see: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.17.y )

[JustCauseWhyNot]

I will give it a shot with the new update.

[JustCauseWhyNot]

I've setup metalog, because I didn't have syslog-ng setup. Here's my 5.17.2 config. I can't find any log of kernel 5.17.2 when it fails to boot. When I try and boot it sticks on black screen. Not even a "warm boot" were I've got some input control.

[NeddySeagoon]

JustCauseWhyNot,

[JustCauseWhyNot]

I've disabled those selftests, except CONFIG_NET_SELFTEST as that required me disabling CONFIG_INET. I had CONFIG_DRM_DEBUG_SELFTEST enabled inorder to turn on CONFIG_DRM_KMS_HELPER, and I didn't need to enable simpledrm which is mutually exclusive with simplefb. And I need simplefb to boot. But I've disabled CONFIG_DRM_DEBUG_SELFTEST, and everything listed in second box.

[pietinger]

JustCauseWhyNot,

I had an intensive look to your kernel config ... AND for me its ok (to boot). Yes, there are some options you dont need all, like these:

[pietinger]

Neddy,

you are right with DEBUG options ... in most cases ... BUT some are needed, AND some will INCREASE Kernel Security, like these:

[JustCauseWhyNot]

It's solved! I disbaled CONFIG_DRM_DEBUG_SELFTEST, and that seems to be the issue. I don't have CONFIG_DRM_KMS_HELPER=Y, but I can boot up to the tty in high resolution. I tested turning on simpledrm, but when the nvidia-drm module loaded I got a graphical error, and it freezes up. I'll share config within a short amount of time, but I need to take a break. Thank you pietinger, and NeddySeagoon.

[JustCauseWhyNot]

I'm able to boot using simplefb. If I try and use simpledrm though I get a graphical error, and the startup log freezes. Here's the kernel config I'm using. I need CONFIG_DRM_FBDEV_EMULATION=Y or I get a glitched black screen without startup log.

[pietinger]

JustCauseWhyNot,

thank you very much for reporting back. Maybe this will help some others in the future.

Many Greetings,
Peter

[JustCauseWhyNot]

I do hope this helps anyone else. But I sent config also to get help. I still can't boot properly while having COMFIG_DRM_KMS_HELPER=Y.

[pietinger]

Sorry for this misunderstanding (I thought it was solved). At the moment I have no ideas, but I know there is actual many changes in kernel for FrameBuffer (AFAIK its not finished right now).

So maybe it is best to boot your old kernel and wait for:
a) new kernel versions, and/or
b) new NVIDIA versions

Sorry for no better service ...

[JustCauseWhyNot]

The core problem is solved. I wasn't able to boot with anything I tried , but I've got a configuration that works properly now. I didn't clarify well enough. The problem was I get an error about CONFIG_DRM_KMS_HELPER not being set when I rebuild nvidia. It's not a huge deal though. For now I'm just going to use simplefb, and hopefully the drivers will get better support in future. Thank you for your help.

[JustCauseWhyNot]

Last post. Here's a 5.17.2 kernel config that doesn't have any issues. I've solved all the issues I've had.

[nxe9]

[pietinger]

[JustCauseWhyNot]

How do I satisfy getting DRM_KMS_HELPER while following the wiki?

[pietinger]

[JustCauseWhyNot]

Thank youl. I'll change my config. So I should be able to use this

[pietinger]

[JustCauseWhyNot]

Alrighty. I'll mess around with it.