| View previous topic :: View next topic |
| Author |
Message |
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 787
|
 Posted: Sat Jan 07, 2023 11:53 pm Post subject: Black screen at boot no output until graphical mode [SOLVED] |
 |
|
Kernel 5.15.80
I have all these set
CONFIG_SYSFB=y
CONFIG_FB=y
CONFIG_FB_EFI=y
CONFIG_SYSFB_SIMPLEFB=y
But when the system boots, there is no output at all, there is only a flashing text-mode underline cursor. The cursor moves by jumping down a few lines, then jumps back up to the top-left of the screen.
There is never any output at all, but after a few seconds, a graphical mouse cursor appears on the black screen, then a few seconds after that, the XDM login screen comes up.
The strangest thing is that it's been like this for a few years. The system runs flawlessly, only there is no info at all during boot.
Sometimes, if I turn the screen off at night, when I open it again in the morning, there will be no signal detected, and I have to CTRL-ALT-F2 to a new virtual-terminal (which is also a black screen with no output at all on it) and then CTRL-ALT-F1 to come back to the main terminal, and everything is exactly where I left things, only KDE warns that there was a graphics-restart.
I'm running the closed-source Nvidia 525.60.13 drivers though, so there might be something going on with that... If Nouveau is really a proper replacement now, I'd switch.
Last edited by Progman3K on Tue Feb 21, 2023 4:54 pm; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54834
Location: 56N 3W
|
| Posted: Sun Jan 08, 2023 12:06 am Post subject: |
|
|
Progman3K,
Put your full dmesg and kernel .config files onto pastebins please.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 787
|
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 2005
|
| Posted: Sun Jan 08, 2023 1:12 am Post subject: |
|
|
Turn FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER off for starters This blocks output at least until the kernel is finished or some other output appears. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2695
|
| Posted: Sun Jan 08, 2023 9:15 am Post subject: |
|
|
SIMPEFB/SIMPLEDRM, those are problematic with NVIDIA binary driver.
You need CONFIG_FB_EFI and CONFIG_FB_VESA (for fallback) enabled and depending on your case possibly CONFIG_SYSFB_SIMPLEFB. Bear in mind the last one is under Device Drivers -> Firmware Drivers.
Add that to grknight's response. Also check if you have quiet parameter passed to your kernel.
However your system should be fast enough to make it impossible for you to follow kernel boot messages and since you have graphical interface enabled, it's all lost from the video buffer when it comes up. It's only accessible through system logs and dmesg.
Best Regards,
Georgi |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54834
Location: 56N 3W
|
| Posted: Sun Jan 08, 2023 10:41 am Post subject: |
|
|
Progman3K,
Please update your firmware. Its not related to your console problem.
| Code: | | [ 0.057137] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later) |
There is no sign of any framebuffer consoles starting in dmesg and thats the only sort there is these days.
Even the 80x24 text console is implemented as a framebuffer.
Do you have some hardware that can use
Its not a problem, just baggage.
Likewise dmesg says you don't have one of those either.
is correct for an EFI system. Its harmless with BIOS booting.
| Code: | | # CONFIG_FB_VESA is not set |
is for BIOS booting and is harmless on EFI systems.
| Code: | | # CONFIG_FB_SIMPLE is not set |
is harmless too. It requires the boot loader to pass its framebuffer to the kernel.
The kernel can draw on this framebuffer but not set it up.
Is only useful if you have the hardware. None was listed in dmesg but its USB.
| Code: | CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_DUMMY_CONSOLE_COLUMNS=80
CONFIG_DUMMY_CONSOLE_ROWS=25
CONFIG_FRAMEBUFFER_CONSOLE=y |
That's the fake VGA text console. Good.
| Code: | | CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y |
may be a bad thing. Its not set here.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 787
|
| Posted: Sun Jan 08, 2023 2:51 pm Post subject: |
|
|
| grknight wrote: | | Turn FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER off for starters This blocks output at least until the kernel is finished or some other output appears. |
Hi grknight,
OK, did that, doesn't change anything, still the same behavior |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 787
|
| Posted: Sun Jan 08, 2023 3:10 pm Post subject: |
|
|
| NeddySeagoon wrote: | is correct for an EFI system. Its harmless with BIOS booting.
| Code: | | # CONFIG_FB_VESA is not set |
is for BIOS booting and is harmless on EFI systems.
|
So which one do I need? I've tried both, then either one, no change.
| NeddySeagoon wrote: | | Code: | | # CONFIG_FB_SIMPLE is not set |
is harmless too. It requires the boot loader to pass its framebuffer to the kernel.
The kernel can draw on this framebuffer but not set it up.
|
OK, I've enabled it, but it makes no apparent difference |
|
| Back to top |
|
|
Banana
Moderator
Joined: 21 May 2004
Posts: 1889
Location: Germany
|
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 787
|
| Posted: Sun Jan 08, 2023 3:17 pm Post subject: |
|
|
| Banana wrote: | | You did boot with the newly compiled kernel and its new settings? |
| Code: | uname -a
Linux spry 5.15.80-gentoo #9 SMP Sun Jan 8 10:00:04 EST 2023 x86_64 Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz GenuineIntel GNU/Linux |
As you can see, the kernel reports it was compiled some 15 minutes ago (my local time) |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54834
Location: 56N 3W
|
| Posted: Sun Jan 08, 2023 4:10 pm Post subject: |
|
|
Progman3K,
Share your new .config and dmesg please, as it is now.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 787
|
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 787
|
| Posted: Sun Jan 08, 2023 5:02 pm Post subject: |
|
|
Is the command line I've baked-in correct?
| Quote: | | [ 0.071205] Kernel command line: root=/dev/sda2 init=/usr/lib/systemd/systemd enable_mtrr_cleanup video=efifb:ywrap,mtrr,1024x768-16@60 |
In any case, I've tried it with the vesa variant, and also with no video parameters, and there never seems to be any difference in the behavior.
One last thing, my video card has three outputs on it, a DVI out and two HDMI outputs. I'm using one of the HDMIs to connect to the display, I've tried either one and it also doesn't seem to make a difference, but I haven't used the DVI output, could it be that the output will only show up on the DVI?
I'm grasping at straws here, of course |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54834
Location: 56N 3W
|
| Posted: Sun Jan 08, 2023 5:59 pm Post subject: |
|
|
Progman3K,
| Code: | [ 0.156473] Console: colour dummy device 80x25
[ 0.156912] printk: console [tty0] enabled |
That's the text console being started.
There is no sign of EFI or VESA though.
The EFI framebuffer console requires the EFI be in use. the VESA framebuffer console requires that BIOS be in use.
Only one can work but its safe to build both.
| Code: | [ 0.166347] MDS: Vulnerable: Clear CPU buffers attempted, no microcode
[ 0.166349] TAA: Vulnerable: Clear CPU buffers attempted, no microcode |
You may want to have the kernel update your CPU microcode.
| Code: | | # CONFIG_FB_VESA is not set |
Thats OK if you use EFI mode.
Your built in command line says | Code: | | video=efifb:ywrap,mtrr,1024x768-16@60" |
Does your display support that video mode?
Its a 4:3 aspect ratio mode.
Do you need a built in command line?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
rab0171610
Guru
Joined: 24 Dec 2022
Posts: 472
|
| Posted: Sun Jan 08, 2023 6:04 pm Post subject: |
|
|
| Quote: | could it be that the output will only show up on the DVI?
I'm grasping at straws here, of course |
Sometimes grasping at straws has led me to the best solution to a problem. There is a possibility that could solve your problem. Example: Nvidia GPU, DVI to HDMI cable, monitor was connected to DVI on GPU out with HDMI end connected to monitor. Worked great. Switched over to a projector, worked fine. Switched to TV and I had the same problem as you. I was able to get grub to show by changing some parameters (resolution if I recall correctly) but no video out until the greeter (SDDM), just a black screen. I could not see kernel/boot messages this way.
Ultimately, after some searching, it was suggested to switch to HDMI and the problem was solved. Whether this would work in reverse, I don't know but it is definitely something to consider. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2695
|
| Posted: Sun Jan 08, 2023 7:08 pm Post subject: |
|
|
| NeddySeagoon wrote: |
| Code: | CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_DUMMY_CONSOLE_COLUMNS=80
CONFIG_DUMMY_CONSOLE_ROWS=25
CONFIG_FRAMEBUFFER_CONSOLE=y |
That's the fake VGA text console. Good.
|
Isn't dummy supposed to be that - dummy? I think it should be disabled. It's not even present in newer kernels.
In the same time in the dmesg I see one line regarding efifb:
| Code: | | [ 0.304093] pci 0000:01:00.0: BAR 3: assigned to efifb |
So it is efifb after all. Just disable that dummy console ans see if it works.
One more thing to consider - have you been playing with boots plash or animation? Have you modified anything in /etc/default/grub?
Best Regards,
Georgi |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 787
|
| Posted: Fri Feb 17, 2023 3:58 pm Post subject: |
|
|
No change, but possibly a clue:
When initially installing this system, it was the first time I dealt with UEFI, and I wasn't very confident about the boot-loading process.
So although I followed the guide and set up Grub, I wasn't able to get the system to boot.
Finally, the method the system uses to boot is the following: It boots the kernel directly.
What this means is that when a new kernel is built, it gets copied to the boot partition like so -
from the linux source folder
| Code: | | ( cp arch/x86/boot/bzImage /boot/EFI/boot/bootx64.efi ) && ( cp arch/x86/boot/bzImage /boot/EFI/boot/bootx64efi.efi ) && ( cp arch/x86/boot/bzImage /boot/EFI/boot/bootx64vesa.efi ) |
The upshot is that when the system boots, it doesn't use the boot-loader, instead the kernel loads directly.
So the video is never prepared by the boot-loader or anything and there is no proper hand-off or the hand-off is not configured properly.
Could this possibly explain why there is no console output at startup? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54834
Location: 56N 3W
|
| Posted: Fri Feb 17, 2023 5:25 pm Post subject: |
|
|
Progman3K,
Can we have your current .config, dmesg and please?
Video handoff between the boot loader and the kernel is required only for Simple Framebuffer.
Its so simple that the kernel only draws on an existing configured framebuffer.
All the rest, it can set up for itself.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 787
|
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 787
|
| Posted: Tue Feb 21, 2023 4:54 pm Post subject: |
|
|
Solved!
Finally, when using the nvidia proprietary video driver, for the setup in question it was important to DISABLE the following kernel config item:
CONFIG_SYSFB_SIMPLEFB
Now, the system boots and displays all kernel messages and then transitions to graphical-mode as expected.
Thank yous to NeddySeagoon, grknight, logrusx, Banana, and rab0171610, for your kind insights. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2695
|
| Posted: Wed Feb 22, 2023 11:45 am Post subject: |
|
|
| Progman3K wrote: | Solved!
Finally, when using the nvidia proprietary video driver, for the setup in question it was important to DISABLE the following kernel config item:
CONFIG_SYSFB_SIMPLEFB
Now, the system boots and displays all kernel messages and then transitions to graphical-mode as expected.
Thank yous to NeddySeagoon, grknight, logrusx, Banana, and rab0171610, for your kind insights. |
Yes, it's broken for nvidia for some time since 5.18, if I remember it correctly. I believe there even was a warning in the nvidia ebuild when it detected it.
Best Regards,
Georgi |
|
| Back to top |
|
|
|
Kernel & Hardware
