Mailing List Archive

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

On Sat, Apr 22, 2023, 20:56 <thelma@sys-concept.com> wrote:

> I upgraded to kernel 6.1.19 and nvidia-525.105.17
>
> But during boot text is not showing up/scrolling
>
> --
> Thelma
>
>

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.

On 4/23/23 00:26, David Souza wrote:
> 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
>
> On Sat, Apr 22, 2023, 20:56 <thelma@sys-concept.com <mailto:thelma@sys-concept.com>> wrote:
>
> I upgraded to kernel 6.1.19 and nvidia-525.105.17
>
> But during boot text is not showing up/scrolling
>
> --
> Thelma
>

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

On Sun, Apr 23, 2023, 22:31 <thelma@sys-concept.com> wrote:

> 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.
>
> On 4/23/23 00:26, David Souza wrote:
> > 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
> >
> > On Sat, Apr 22, 2023, 20:56 <thelma@sys-concept.com <mailto:
> thelma@sys-concept.com>> wrote:
> >
> > I upgraded to kernel 6.1.19 and nvidia-525.105.17
> >
> > But during boot text is not showing up/scrolling
> >
> > --
> > Thelma
> >
>
>

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



On 4/23/23 18:07, David Souza wrote:
> 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
>
> On Sun, Apr 23, 2023, 22:31 <thelma@sys-concept.com <mailto:thelma@sys-concept.com>> wrote:
>
> 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 <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 <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.
>
> On 4/23/23 00:26, David Souza wrote:
> > 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
> >
> > On Sat, Apr 22, 2023, 20:56 <thelma@sys-concept.com <mailto:thelma@sys-concept.com> <mailto:thelma@sys-concept.com <mailto:thelma@sys-concept.com>>> wrote:
> >
> >     I upgraded to kernel 6.1.19 and nvidia-525.105.17
> >
> >     But during boot text is not showing up/scrolling
> >
> >     --
> >     Thelma
> >
>

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.
Can you also print the output of:

$ 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?

Am Mo., 24. Apr. 2023 um 19:08 Uhr schrieb <thelma@sys-concept.com>:

> 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
>
>
>
> On 4/23/23 18:07, David Souza wrote:
> > 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
> >
> > On Sun, Apr 23, 2023, 22:31 <thelma@sys-concept.com <mailto:
> thelma@sys-concept.com>> wrote:
> >
> > 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 <
> 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 <
> 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.
> >
> > On 4/23/23 00:26, David Souza wrote:
> > > 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
> > >
> > > On Sat, Apr 22, 2023, 20:56 <thelma@sys-concept.com <mailto:
> thelma@sys-concept.com> <mailto:thelma@sys-concept.com <mailto:
> thelma@sys-concept.com>>> wrote:
> > >
> > > I upgraded to kernel 6.1.19 and nvidia-525.105.17
> > >
> > > But during boot text is not showing up/scrolling
> > >
> > > --
> > > Thelma
> > >
> >
>
>

On Sat, Apr 22, 2023 at 11:56?AM <thelma@sys-concept.com> wrote:
>
> 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

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
fd@white ~ $
fd@white ~ $ dmesg | grep fbcon

The "dmesg | grep fbcon" show nothing.


On 4/24/23 13:42, David Souza wrote:
> 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.
> Can you also print the output of:
>
> $ 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?
>
> Am Mo., 24. Apr. 2023 um 19:08 Uhr schrieb <thelma@sys-concept.com <mailto:thelma@sys-concept.com>>:
>
> 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
>
>
>
> On 4/23/23 18:07, David Souza wrote:
> > 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
> >
> > On Sun, Apr 23, 2023, 22:31 <thelma@sys-concept.com <mailto:thelma@sys-concept.com> <mailto:thelma@sys-concept.com <mailto:thelma@sys-concept.com>>> wrote:
> >
> >     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 <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
> >     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 <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.
> >
> >     On 4/23/23 00:26, David Souza wrote:
> >      > 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
> >      >
> >      > On Sat, Apr 22, 2023, 20:56 <thelma@sys-concept.com <mailto:thelma@sys-concept.com> <mailto:thelma@sys-concept.com <mailto:thelma@sys-concept.com>> <mailto:thelma@sys-concept.com <mailto:thelma@sys-concept.com> <mailto:thelma@sys-concept.com <mailto:thelma@sys-concept.com>>>> wrote:
> >      >
> >      >     I upgraded to kernel 6.1.19 and nvidia-525.105.17
> >      >
> >      >     But during boot text is not showing up/scrolling
> >      >
> >      >     --
> >      >     Thelma
> >      >
> >
>

On 4/24/23 14:39, Mark Knecht wrote:
>
>
> On Sat, Apr 22, 2023 at 11:56?AM <thelma@sys-concept.com <mailto:thelma@sys-concept.com>> wrote:
> >
> > 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"
------

On Mon, Apr 24, 2023 at 2:31?PM <thelma@sys-concept.com> wrote:
>
> On 4/24/23 14:39, Mark Knecht wrote:
> >
> >
> > On Sat, Apr 22, 2023 at 11:56?AM <thelma@sys-concept.com <mailto:
thelma@sys-concept.com>> wrote:
<SNIP>
> # 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

> # 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

On 4/24/23 15:41, Mark Knecht wrote:
>
>
> On Mon, Apr 24, 2023 at 2:31?PM <thelma@sys-concept.com <mailto:thelma@sys-concept.com>> wrote:
> >
> > On 4/24/23 14:39, Mark Knecht wrote:
> > >
> > >
> > > On Sat, Apr 22, 2023 at 11:56?AM <thelma@sys-concept.com <mailto:thelma@sys-concept.com> <mailto:thelma@sys-concept.com <mailto:thelma@sys-concept.com>>> wrote:
> <SNIP>
> > # 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=""

> > # 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

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

> 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

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.

On Mon, 24 Apr 2023, thelma@sys-concept.com wrote:

> On 4/24/23 15:41, Mark Knecht wrote:
> >
> >
> > On Mon, Apr 24, 2023 at 2:31?PM <thelma@sys-concept.com
> > <mailto:thelma@sys-concept.com>> wrote:
> > >
> > > On 4/24/23 14:39, Mark Knecht wrote:
> > > >
> > > >
> > > > On Sat, Apr 22, 2023 at 11:56?AM <thelma@sys-concept.com
> > > > <mailto:thelma@sys-concept.com> <mailto:thelma@sys-concept.com
> > > > <mailto:thelma@sys-concept.com>>> wrote:
> > <SNIP>
> > > #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=""
>
> > ># 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
>
> 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
>
> > 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
>
>

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


On 4/24/23 16:11, Jude DaShiell wrote:
> 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.
>
> On Mon, 24 Apr 2023, thelma@sys-concept.com wrote:
>
>> On 4/24/23 15:41, Mark Knecht wrote:
>>>
>>>
>>> On Mon, Apr 24, 2023 at 2:31?PM <thelma@sys-concept.com
>>> <mailto:thelma@sys-concept.com>> wrote:
>>> >
>>> > On 4/24/23 14:39, Mark Knecht wrote:
>>> > >
>>> > >
>>> > > On Sat, Apr 22, 2023 at 11:56?AM <thelma@sys-concept.com
>>> > > <mailto:thelma@sys-concept.com> <mailto:thelma@sys-concept.com
>>> > > <mailto:thelma@sys-concept.com>>> wrote:
>>> <SNIP>
>>> > #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=""
>>
>>> ># 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
>>
>> 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
>>
>>> 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
>>
>>
>
>

Okay, that means you had an error free boot without fatals and without
warnings.


-- 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.

On Mon, 24 Apr 2023, thelma@sys-concept.com wrote:

> None of them produce any output:
> - dmesg| grep -i fatal
> - dmesg| grep -i error
> - dmesg| grep -i warn
>
>
> On 4/24/23 16:11, Jude DaShiell wrote:
> > 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.
> >
> > On Mon, 24 Apr 2023, thelma@sys-concept.com wrote:
> >
> >> On 4/24/23 15:41, Mark Knecht wrote:
> >>>
> >>>
> >>> On Mon, Apr 24, 2023 at 2:31?PM <thelma@sys-concept.com
> >>> <mailto:thelma@sys-concept.com>> wrote:
> >>> >
> >>> > On 4/24/23 14:39, Mark Knecht wrote:
> >>> > >
> >>> > >
> >>> > > On Sat, Apr 22, 2023 at 11:56?AM <thelma@sys-concept.com
> >>> > > <mailto:thelma@sys-concept.com> <mailto:thelma@sys-concept.com
> >>> > > <mailto:thelma@sys-concept.com>>> wrote:
> >>> <SNIP>
> >>> > #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=""
> >>
> >>> ># 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
> >>
> >> 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
> >>
> >>> 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
> >>
> >>
> >
> >
>
>

Yes, I know.
But I'm used to see those lines scrolling by during boot. As sometimes you can see error during booting.


On 4/24/23 16:36, Jude DaShiell wrote:
> Okay, that means you had an error free boot without fatals and without
> warnings.
>
>
> -- 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.
>
> On Mon, 24 Apr 2023, thelma@sys-concept.com wrote:
>
>> None of them produce any output:
>> - dmesg| grep -i fatal
>> - dmesg| grep -i error
>> - dmesg| grep -i warn
>>
>>
>> On 4/24/23 16:11, Jude DaShiell wrote:
>>> 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.
>>>
>>> On Mon, 24 Apr 2023, thelma@sys-concept.com wrote:
>>>
>>>> On 4/24/23 15:41, Mark Knecht wrote:
>>>>>
>>>>>
>>>>> On Mon, Apr 24, 2023 at 2:31?PM <thelma@sys-concept.com
>>>>> <mailto:thelma@sys-concept.com>> wrote:
>>>>> >
>>>>> > On 4/24/23 14:39, Mark Knecht wrote:
>>>>> > >
>>>>> > >
>>>>> > > On Sat, Apr 22, 2023 at 11:56?AM <thelma@sys-concept.com
>>>>> > > <mailto:thelma@sys-concept.com> <mailto:thelma@sys-concept.com
>>>>> > > <mailto:thelma@sys-concept.com>>> wrote:
>>>>> <SNIP>
>>>>> > #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=""
>>>>
>>>>> ># 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
>>>>
>>>> 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
>>>>
>>>>> 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
>>>>
>>>>
>>>
>>>
>>
>>
>
>

As a screen reader user, that's a huge amount of material to listen to
scrolling by fast. It is useful to know that a system is talking as it
comes up, but I get more from dmesg after the boot process finishes since
I can do so in an organized fashion.


-- 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.

On Mon, 24 Apr 2023, thelma@sys-concept.com wrote:

> Yes, I know.
> But I'm used to see those lines scrolling by during boot. As sometimes you
> can see error during booting.
>
>
> On 4/24/23 16:36, Jude DaShiell wrote:
> > Okay, that means you had an error free boot without fatals and without
> > warnings.
> >
> >
> > -- 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.
> >
> > On Mon, 24 Apr 2023, thelma@sys-concept.com wrote:
> >
> >> None of them produce any output:
> >> - dmesg| grep -i fatal
> >> - dmesg| grep -i error
> >> - dmesg| grep -i warn
> >>
> >>
> >> On 4/24/23 16:11, Jude DaShiell wrote:
> >>> 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.
> >>>
> >>> On Mon, 24 Apr 2023, thelma@sys-concept.com wrote:
> >>>
> >>>> On 4/24/23 15:41, Mark Knecht wrote:
> >>>>>
> >>>>>
> >>>>> On Mon, Apr 24, 2023 at 2:31?PM <thelma@sys-concept.com
> >>>>> <mailto:thelma@sys-concept.com>> wrote:
> >>>>> >
> >>>>> > On 4/24/23 14:39, Mark Knecht wrote:
> >>>>> > >
> >>>>> > >
> >>>>> > > On Sat, Apr 22, 2023 at 11:56?AM <thelma@sys-concept.com
> >>>>> > > <mailto:thelma@sys-concept.com> <mailto:thelma@sys-concept.com
> >>>>> > > <mailto:thelma@sys-concept.com>>> wrote:
> >>>>> <SNIP>
> >>>>> > #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=""
> >>>>
> >>>>> ># 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
> >>>>
> >>>> 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
> >>>>
> >>>>> 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
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>

On Mon, 24 Apr 2023 16:02:33 -0600, thelma@sys-concept.com wrote:

> > Consider uncommenting this line and running sudo update-grub
>
> Why should I uncommenting this line with an empty parameter?
> GRUB_CMDLINE_LINUX_DEFAULT=""
>
> > > # 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
>
> 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

What setting is the kernel actually being told to use for screen
resolution? What is the output of cat /proc/cmdline.

This sounds like it could be something to do with kernel modesetting.


--
Neil Bothwick

Men who go out with flat chested woman have reasons for feeling down

On 4/25/23 01:27, Neil Bothwick wrote:
> On Mon, 24 Apr 2023 16:02:33 -0600, thelma@sys-concept.com wrote:
>
>>> Consider uncommenting this line and running sudo update-grub
>>
>> Why should I uncommenting this line with an empty parameter?
>> GRUB_CMDLINE_LINUX_DEFAULT=""
>>
>>> > # 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
>>
>> 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
>
> What setting is the kernel actually being told to use for screen
> resolution? What is the output of cat /proc/cmdline.
>
> This sounds like it could be something to do with kernel modesetting.

I'm getting:
cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.1.19-gentoo root=PARTUUID=33fd3594-68f7-e143-842a-cdade6d25e34 ro

Have similar output like on my other systems.

Wold removing from grub : GRUB_GFXMODE=1024x768x32
solve the problem. I think it would go to default mode: 640x480

On Tue, 25 Apr 2023 09:42:55 -0600, thelma@sys-concept.com wrote:

> > What setting is the kernel actually being told to use for screen
> > resolution? What is the output of cat /proc/cmdline.
> >
> > This sounds like it could be something to do with kernel modesetting.
> >
>
> I'm getting:
> cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-6.1.19-gentoo
> root=PARTUUID=33fd3594-68f7-e143-842a-cdade6d25e34 ro
>
> Have similar output like on my other systems.
>
> Wold removing from grub : GRUB_GFXMODE=1024x768x32
> solve the problem. I think it would go to default mode: 640x480

That sets the resolution for the GRUB menu. If you can see that but the
kernel boot messages don't display, you may find adding nomodeset to the
boot options helps. More info at

https://wiki.archlinux.org/title/kernel_mode_setting#Disabling_modesetting


--
Neil Bothwick

If at first you don't suceed, try the switch marked "Power"