[gentoo-user] text output from the kernel during boot is not showing

Discussion:

(too old to reply)

t***@sys-concept.com

2023-04-22 19:00:01 UTC

Permalink

I upgraded to kernel 6.1.19 and nvidia-525.105.17

But during boot text is not showing up/scrolling

--
Thelma

David Souza

2023-04-23 06:30:01 UTC

Permalink

Did you change something in your kernel config? I had the same problem
once, because I forgot to enable these kernel options:
(From the AMD64 Handbook)

Device Drivers
Firmware Drivers --->
EFI (Extensible Firmware Interface) Support --->
<*> EFI Variable Support via sysfs
Graphics support --->
Frame buffer Devices --->
<*> Support for frame buffer devices --->
[*] EFI-based Framebuffer Support

Regards,
David

Post by t***@sys-concept.com
I upgraded to kernel 6.1.19 and nvidia-525.105.17
But during boot text is not showing up/scrolling
--
Thelma

t***@sys-concept.com

2023-04-23 20:40:01 UTC

Permalink

No, I did not change anything, during kernel upgrade only run: make oldconfig

but nvidia-drivers-525.105.17 compiled with a note:
WARN: setup
Detected potential configuration issues with used kernel:
CONFIG_FB_SIMPLE: is set, recommended to disable and switch to FB_EFI or
FB_VESA as it currently may be broken with >=kernel-5.18.13 + NVIDIA:
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341
(feel free to ignore this if it works for you)

Though, I got same note compiling nvidia-drivers-470.182.03 and kernel boot normally showing text.

WARN: setup
Detected potential configuration issues with used kernel:
CONFIG_FB_SIMPLE: is set, recommended to disable and switch to FB_EFI or
FB_VESA as it currently may be broken with >=kernel-5.18.13 + NVIDIA:
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341
(feel free to ignore this if it works for you)

I don't use EFI on these systems.
So make me wonder if has all to do with the nvidia-driver.

Post by David Souza
(From the AMD64 Handbook)
Device Drivers
Firmware Drivers --->
EFI (Extensible Firmware Interface) Support --->
<*> EFI Variable Support via sysfs
Graphics support --->
Frame buffer Devices --->
<*> Support for frame buffer devices --->
[*] EFI-based Framebuffer Support
Regards,
David
I upgraded to kernel 6.1.19 and nvidia-525.105.17
But during boot text is not showing up/scrolling
--
Thelma

David Souza

2023-04-24 00:10:01 UTC

Permalink

Is your framebuffer device showing in /dev? It should be called
/dev/fb0,1,2..... If yes could you post the output of
$ dmesg | grep fb0

Post by t***@sys-concept.com
No, I did not change anything, during kernel upgrade only run: make oldconfig
WARN: setup
CONFIG_FB_SIMPLE: is set, recommended to disable and switch to FB_EFI or
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341
(feel free to ignore this if it works for you)
Though, I got same note compiling nvidia-drivers-470.182.03 and kernel
boot normally showing text.
WARN: setup
CONFIG_FB_SIMPLE: is set, recommended to disable and switch to FB_EFI or
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341
(feel free to ignore this if it works for you)
I don't use EFI on these systems.
So make me wonder if has all to do with the nvidia-driver.

Post by David Souza
Did you change something in your kernel config? I had the same problem
(From the AMD64 Handbook)
Device Drivers
Firmware Drivers --->
EFI (Extensible Firmware Interface) Support --->
<*> EFI Variable Support via sysfs
Graphics support --->
Frame buffer Devices --->
<*> Support for frame buffer devices --->
[*] EFI-based Framebuffer Support
Regards,
David
I upgraded to kernel 6.1.19 and nvidia-525.105.17
But during boot text is not showing up/scrolling
--
Thelma

t***@sys-concept.com

2023-04-24 17:10:01 UTC

Permalink

On output of: $ dmesg | grep fb0
on a box that doesn't show kernel text during boot:

[ 0.004012] ACPI: Reserving PCCT table memory at [mem 0xd8b68fb0-0xd8b6901d]

this the output from a box that everything is working OK:
[ 0.000000] ACPI: Reserving PCCT table memory at [mem 0xd8b68fb0-0xd8b6901d]

I even compare the difference between grub before and after upgrade, and new sys-boot/grub-2.06-r6
inserted line:

# Comment if you don't want GRUB to pass "root=PARTUUID=xxx" parameter to kernel
GRUB_DISABLE_LINUX_PARTUUID=false

but the above two lines are on my other boxes as well afater upgrade and text messages from kernel boot showing OK

David Souza

2023-04-24 19:50:01 UTC

Permalink

Post by t***@sys-concept.com
On output of: $ dmesg | grep fb0
[ 0.004012] ACPI: Reserving PCCT table memory at [mem
0xd8b68fb0-0xd8b6901d]
[ 0.000000] ACPI: Reserving PCCT table memory at [mem
0xd8b68fb0-0xd8b6901d]
I even compare the difference between grub before and after upgrade, and
new sys-boot/grub-2.06-r6
# Comment if you don't want GRUB to pass "root=PARTUUID=xxx" parameter to kernel
GRUB_DISABLE_LINUX_PARTUUID=false
but the above two lines are on my other boxes as well afater upgrade and
text messages from kernel boot showing OK

Post by David Souza
Is your framebuffer device showing in /dev? It should be called

/dev/fb0,1,2..... If yes could you post the output of

Post by David Souza
$ dmesg | grep fb0
No, I did not change anything, during kernel upgrade only run: make

oldconfig

Post by David Souza
WARN: setup
CONFIG_FB_SIMPLE: is set, recommended to disable and switch to

FB_EFI or

Post by David Souza
FB_VESA as it currently may be broken with >=kernel-5.18.13 +
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341 <

https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341>

Post by David Souza
(feel free to ignore this if it works for you)
Though, I got same note compiling nvidia-drivers-470.182.03 and

kernel boot normally showing text.

Post by David Souza
WARN: setup
CONFIG_FB_SIMPLE: is set, recommended to disable and switch to

FB_EFI or

Post by David Souza
FB_VESA as it currently may be broken with >=kernel-5.18.13 +
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341 <

https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341>

Post by David Souza
(feel free to ignore this if it works for you)
I don't use EFI on these systems.
So make me wonder if has all to do with the nvidia-driver.

Post by David Souza
Did you change something in your kernel config? I had the same
(From the AMD64 Handbook)
Device Drivers
Firmware Drivers --->
EFI (Extensible Firmware Interface) Support --->
<*> EFI Variable Support via sysfs
Graphics support --->
Frame buffer Devices --->
<*> Support for frame buffer devices --->
[*] EFI-based Framebuffer Support
Regards,
David
I upgraded to kernel 6.1.19 and nvidia-525.105.17
But during boot text is not showing up/scrolling
--
Thelma

t***@sys-concept.com

2023-04-24 21:30:01 UTC

Permalink

This is the output: dmesg | grep fb
[ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[ 0.004007] ACPI: Reserving WSMT table memory at [mem 0xd8b6fb48-0xd8b6fb6f]
[ 0.004012] ACPI: Reserving PCCT table memory at [mem 0xd8b68fb0-0xd8b6901d]
[ 0.004014] ACPI: Reserving SSDT table memory at [mem 0xd8b6ddf8-0xd8b6fb41]
[ 0.042890] PM: hibernation: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
[ 0.234106] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[ 0.234110] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[ 0.321245] system 00:00: [mem 0xf8000000-0xfbffffff] has been reserved
[ 0.351895] ahci 0000:06:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
[ 0.352470] ahci 0000:07:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
[ 0.352694] ahci 0000:0b:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
[ 0.352896] ahci 0000:0c:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
***@white ~ $
***@white ~ $ dmesg | grep fbcon

The "dmesg | grep fbcon" show nothing.

Interesting, the kernel is not showing anything about the framebuffer device fb0. Could you check if in /dev there is a framebuffer device? There should be a file called fb0 or fb with another number.
$ dmesg | grep fbcon
This would be to check the kernel output if it tries to set a device for outputting kernel messages to a framebuffer device.
I think there is an option missing in your kernelconfig. Did you build your own kernel or are you using a binary or similar?
On output of: $ dmesg | grep fb0
[ 0.004012] ACPI: Reserving PCCT table memory at [mem 0xd8b68fb0-0xd8b6901d]
[ 0.000000] ACPI: Reserving PCCT table memory at [mem 0xd8b68fb0-0xd8b6901d]
I even compare the difference between grub before and after upgrade, and new sys-boot/grub-2.06-r6
# Comment if you don't want GRUB to pass "root=PARTUUID=xxx" parameter to kernel
GRUB_DISABLE_LINUX_PARTUUID=false
but the above two lines are on my other boxes as well afater upgrade and text messages from kernel boot showing OK

Is your framebuffer device showing in /dev? It should be called /dev/fb0,1,2..... If yes could you post the output of
$ dmesg | grep fb0
No, I did not change anything, during kernel upgrade only run: make oldconfig
WARN: setup
CONFIG_FB_SIMPLE: is set, recommended to disable and switch to FB_EFI or
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341 <https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341> <https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341 <https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341>>
(feel free to ignore this if it works for you)
Though, I got same note compiling nvidia-drivers-470.182.03 and kernel boot normally showing text.
WARN: setup
CONFIG_FB_SIMPLE: is set, recommended to disable and switch to FB_EFI or
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341 <https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341> <https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341 <https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341>>
(feel free to ignore this if it works for you)
I don't use EFI on these systems.
So make me wonder if has all to do with the nvidia-driver.
> (From the AMD64 Handbook)
>
> Device Drivers
> Firmware Drivers --->
> EFI (Extensible Firmware Interface) Support --->
> <*> EFI Variable Support via sysfs
> Graphics support --->
> Frame buffer Devices --->
> <*> Support for frame buffer devices --->
> [*] EFI-based Framebuffer Support
>
>
> Regards,
> David
>
>
> I upgraded to kernel 6.1.19 and nvidia-525.105.17
>
> But during boot text is not showing up/scrolling
>
> --
> Thelma
>

Mark Knecht

2023-04-24 20:50:02 UTC

Permalink

Post by t***@sys-concept.com
I upgraded to kernel 6.1.19 and nvidia-525.105.17
But during boot text is not showing up/scrolling
--
Thelma

Is this possibly a grub setting? Check /etc/default/grub or whatever
it might be on your system and look at

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

If that's there then remove the word 'quiet' and
run sudo update-grub or whatever is appropriate
for your system to set up the change.

HTH,
Mark

t***@sys-concept.com

2023-04-24 21:40:01 UTC

Permalink

Post by Mark Knecht

Post by t***@sys-concept.com
I upgraded to kernel 6.1.19 and nvidia-525.105.17
But during boot text is not showing up/scrolling
--
Thelma

Is this possibly a grub setting? Check /etc/default/grub or whatever
it might be on your system and look at
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
If that's there then remove the word 'quiet' and
run sudo update-grub or whatever is appropriate
for your system to set up the change.
HTH,
Mark

I already check "/etc/default/grub" has no entry "quiet" in it.
------------
--GRUB_DISTRIBUTOR="Gentoo"

# Default menu entry
#GRUB_DEFAULT=0

# Boot the default entry this many seconds after the menu is displayed
#GRUB_TIMEOUT=5
#GRUB_TIMEOUT_STYLE=menu

# Append parameters to the linux kernel command line
#GRUB_CMDLINE_LINUX=""
#
# Examples:
#
# Boot with network interface renaming disabled
# GRUB_CMDLINE_LINUX="net.ifnames=0"
#
# Boot with systemd instead of sysvinit (openrc)
# GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd"

# Append parameters to the linux kernel command line for non-recovery entries
#GRUB_CMDLINE_LINUX_DEFAULT=""

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal.
# Note that you can use only modes which your graphic card supports via VBE.
# You can see them in real GRUB with the command `vbeinfo'.
#GRUB_GFXMODE=640x480
GRUB_GFXMODE=1024x768x32

# Set to 'text' to force the Linux kernel to boot in normal text
# mode, 'keep' to preserve the graphics mode set using
# 'GRUB_GFXMODE', 'WIDTHxHEIGHT'['xDEPTH'] to set a particular
# graphics mode, or a sequence of these separated by commas or
# semicolons to try several modes in sequence.
GRUB_GFXPAYLOAD_LINUX=keep

# Path to theme spec txt file.
# The starfield is by default provided with use truetype.
# NOTE: when enabling custom theme, ensure you have required font/etc.
#GRUB_THEME="/boot/grub/themes/starfield/theme.txt"

# Background image used on graphical terminal.
# Can be in various bitmap formats.
#GRUB_BACKGROUND="/boot/grub/mybackground.png"

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to kernel
#GRUB_DISABLE_LINUX_UUID=true

# Comment if you don't want GRUB to pass "root=PARTUUID=xxx" parameter to kernel
GRUB_DISABLE_LINUX_PARTUUID=false

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY=true

# Uncomment to disable generation of the submenu and put all choices on
# the top-level menu.
# Besides the visual affect of no sub menu, this makes navigation of the
# menu easier for a user who can't see the screen.
#GRUB_DISABLE_SUBMENU=y

# Uncomment to play a tone when the main menu is displayed.
# This is useful, for example, to allow users who can't see the screen
# to know when they can make a choice on the menu.
#GRUB_INIT_TUNE="60 800 1"
------

Mark Knecht

2023-04-24 21:50:01 UTC

Permalink

***@sys-concept.com>> wrote:
<SNIP>

Post by t***@sys-concept.com
# Append parameters to the linux kernel command line for non-recovery entries
#GRUB_CMDLINE_LINUX_DEFAULT=""

<SNIP>

Consider uncommenting this line and running sudo update-grub

Post by t***@sys-concept.com
# The resolution used on graphical terminal.
# Note that you can use only modes which your graphic card supports via VBE.
# You can see them in real GRUB with the command `vbeinfo'.
#GRUB_GFXMODE=640x480
GRUB_GFXMODE=1024x768x32

While I understand that you probably didn't change this setting do
you know that 1024x769x32 is ok?

Have you run vbeinfo or verified by some other means?

HTH,
Mark

t***@sys-concept.com

2023-04-24 22:10:01 UTC

Permalink

Post by Mark Knecht
<SNIP>

Post by t***@sys-concept.com
# Append parameters to the linux kernel command line for non-recovery entries
#GRUB_CMDLINE_LINUX_DEFAULT=""

<SNIP>
Consider uncommenting this line and running sudo update-grub

Why should I uncommenting this line with an empty parameter?
GRUB_CMDLINE_LINUX_DEFAULT=""

Post by Mark Knecht

GRUB_GFXMODE=1024x768x32 was there before and it run perfectly find with older kernel: linux-5.10.103-gentoo
Just after upgrading to kernel-6.1.19 it happened

Post by Mark Knecht
While I understand that you probably didn't change this setting do
you know that 1024x769x32 is ok?
Have you run vbeinfo or verified by some other means?

This box is in remote location, so it is hard for me to test with vbeinfo

t***@sys-concept.com

2023-04-24 22:20:01 UTC

Permalink

None of them produce any output:
- dmesg| grep -i fatal
- dmesg| grep -i error
- dmesg| grep -i warn

After a boot,
dmesg| grep -i fatal && dmesg|grep -i error&&dmesg| grep -i warn
may help. If I were doing that for my own uses, I'd include titles and
read statements in the command. All of that could be redirected by means
of non-destructive appends to a file too.
-- Jude <jdashiel at panix dot com> "There are four boxes to be used in
defense of liberty: soap, ballot, jury, and ammo. Please use in that
order." Ed Howdershelt 1940.