I upgraded to kernel 6.1.19 and nvidia-525.105.17

But during boot text is not showing up/scrolling

--
Thelma

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

<div dir="auto"><div>Did you change something in your kernel config? I had the same problem once, because I forgot to enable these kernel options:</div><div dir="auto">(From the AMD64 Handbook)</div><div dir="auto"><br></div><div dir="auto">Device
Drivers</div><div dir="auto">    Firmware Drivers ---&gt;</div><div dir="auto">        EFI (Extensible Firmware Interface) Support ---&gt;</div><div dir="auto">            &lt;*&gt; EFI Variable Support via sysfs</div><div dir="auto">   
Graphics support ---&gt;</div><div dir="auto">        Frame buffer Devices ---&gt;</div><div dir="auto">            &lt;*&gt; Support for frame buffer devices ---&gt;</div><div dir="auto">                [*] EFI-based Framebuffer
Support<br><br><br>Regards,</div><div dir="auto">David <br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Sat, Apr 22, 2023, 20:56 &lt;<a href="mailto:thelma@sys-concept.com" target="_blank" rel="noreferrer">thelma@sys-
concept.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I upgraded to kernel 6.1.19 and nvidia-525.105.17<br>

But during boot text is not showing up/scrolling<br>

-- <br>
Thelma<br>

</blockquote></div></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

<div dir="auto"><div>Is your framebuffer device showing in /dev? It should be called /dev/fb0,1,2..... If yes could you post the output of </div><div dir="auto">$ dmesg | grep fb0</div><div dir="auto"><br><div class="gmail_quote" dir="auto"><div dir="
ltr" class="gmail_attr">On Sun, Apr 23, 2023, 22:31 &lt;<a href="mailto:thelma@sys-concept.com">thelma@sys-concept.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">No, I
did not change anything, during kernel upgrade only run: make oldconfig<br>

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

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

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

I don&#39;t use EFI on these systems.<br>
So make me wonder if has all to do with the nvidia-driver.<br>

On 4/23/23 00:26, David Souza wrote:<br>
&gt; Did you change something in your kernel config? I had the same problem once, because I forgot to enable these kernel options:<br>
&gt; (From the AMD64 Handbook)<br>
&gt; <br>
&gt; Device Drivers<br>
&gt;      Firmware Drivers ---&gt;<br>
&gt;          EFI (Extensible Firmware Interface) Support ---&gt;<br> &gt;              &lt;*&gt; EFI Variable Support via sysfs<br>
&gt;      Graphics support ---&gt;<br>
&gt;          Frame buffer Devices ---&gt;<br>
&gt;              &lt;*&gt; Support for frame buffer devices ---&gt;<br> &gt;                  [*] EFI-based Framebuffer Support<br>
&gt; <br>
&gt; <br>
&gt; Regards,<br>
&gt; David<br>
&gt; <br>
&gt; On Sat, Apr 22, 2023, 20:56 &lt;<a href="mailto:thelma@sys-concept.com" target="_blank" rel="noreferrer">thelma@sys-concept.com</a> &lt;mailto:<a href="mailto:thelma@sys-concept.com" target="_blank" rel="noreferrer">thelma@sys-concept.com</a>&gt;&gt;
wrote:<br>
&gt; <br>
&gt;     I upgraded to kernel 6.1.19 and nvidia-525.105.17<br>
&gt; <br>
&gt;     But during boot text is not showing up/scrolling<br>
&gt; <br>
&gt;     -- <br>
&gt;     Thelma<br>
&gt; <br>

</blockquote></div></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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
>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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
>

<div dir="ltr"><div>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.</div><div>Can you also print the
output of:</div><div><br></div><div>$ dmesg  | grep fbcon <br></div><div><br></div><div>This would be to check the kernel output if it tries to set a device for outputting kernel messages to a framebuffer device.<br></div><div><br></div><div>I think
there is an option missing in your kernelconfig. Did you build your own kernel or are you using a binary or similar?<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Mo., 24. Apr. 2023 um 19:08 Uhr schrieb &lt;<a href="
mailto:thelma@sys-concept.com">thelma@sys-concept.com</a>&gt;:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On output of: $ dmesg | grep fb0<br>
on a box that doesn&#39;t show kernel text during boot:<br>

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

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

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

# Comment if you don&#39;t want GRUB to pass &quot;root=PARTUUID=xxx&quot; parameter to kernel<br>
GRUB_DISABLE_LINUX_PARTUUID=false<br>

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



On 4/23/23 18:07, David Souza wrote:<br>
&gt; Is your framebuffer device showing in /dev? It should be called /dev/fb0,1,2..... If yes could you post the output of<br>
&gt; $ dmesg | grep fb0<br>
&gt; <br>
&gt; On Sun, Apr 23, 2023, 22:31 &lt;<a href="mailto:thelma@sys-concept.com" target="_blank">thelma@sys-concept.com</a> &lt;mailto:<a href="mailto:thelma@sys-concept.com" target="_blank">thelma@sys-concept.com</a>&gt;&gt; wrote:<br>
&gt; <br>
&gt;     No, I did not change anything, during kernel upgrade only run: make oldconfig<br>
&gt; <br>
&gt;     but nvidia-drivers-525.105.17 compiled  with a note:<br>
&gt;     WARN: setup<br>
&gt;     Detected potential configuration issues with used kernel:<br> &gt;         CONFIG_FB_SIMPLE: is set, recommended to disable and switch to FB_EFI or<br>
&gt;           FB_VESA as it currently may be broken with &gt;=kernel-5.18.13 + NVIDIA:<br>
&gt;     <a href="https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341" rel="noreferrer" target="_blank">https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341</a> &lt;<a href="https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341"
rel="noreferrer" target="_blank">https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341</a>&gt;<br>
&gt;           (feel free to ignore this if it works for you)<br>
&gt; <br>
&gt;     Though, I got same note compiling nvidia-drivers-470.182.03  and kernel boot normally showing text.<br>
&gt; <br>
&gt;     WARN: setup<br>
&gt;     Detected potential configuration issues with used kernel:<br> &gt;         CONFIG_FB_SIMPLE: is set, recommended to disable and switch to FB_EFI or<br>
&gt;           FB_VESA as it currently may be broken with &gt;=kernel-5.18.13 + NVIDIA:<br>
&gt;     <a href="https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341" rel="noreferrer" target="_blank">https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341</a> &lt;<a href="https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341"
rel="noreferrer" target="_blank">https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341</a>&gt;<br>
&gt;           (feel free to ignore this if it works for you)<br>
&gt; <br>
&gt;     I don&#39;t use EFI on these systems.<br>
&gt;     So make me wonder if has all to do with the nvidia-driver.<br>
&gt; <br>
&gt;     On 4/23/23 00:26, David Souza wrote:<br>
&gt;      &gt; Did you change something in your kernel config? I had the same problem once, because I forgot to enable these kernel options:<br>
&gt;      &gt; (From the AMD64 Handbook)<br>
&gt;      &gt;<br>
&gt;      &gt; Device Drivers<br>
&gt;      &gt;      Firmware Drivers ---&gt;<br>
&gt;      &gt;          EFI (Extensible Firmware Interface) Support ---&gt;<br>
&gt;      &gt;              &lt;*&gt; EFI Variable Support via sysfs<br>
&gt;      &gt;      Graphics support ---&gt;<br>
&gt;      &gt;          Frame buffer Devices ---&gt;<br>
&gt;      &gt;              &lt;*&gt; Support for frame buffer devices ---&gt;<br>
&gt;      &gt;                  [*] EFI-based Framebuffer Support<br>
&gt;      &gt;<br>
&gt;      &gt;<br>
&gt;      &gt; Regards,<br>
&gt;      &gt; David<br>
&gt;      &gt;<br>
&gt;      &gt; On Sat, Apr 22, 2023, 20:56 &lt;<a href="mailto:thelma@sys-concept.com" target="_blank">thelma@sys-concept.com</a> &lt;mailto:<a href="mailto:thelma@sys-concept.com" target="_blank">thelma@sys-concept.com</a>&gt; &lt;mailto:<a href="
mailto:thelma@sys-concept.com" target="_blank">thelma@sys-concept.com</a> &lt;mailto:<a href="mailto:thelma@sys-concept.com" target="_blank">thelma@sys-concept.com</a>&gt;&gt;&gt; wrote:<br>
&gt;      &gt;<br>
&gt;      &gt;     I upgraded to kernel 6.1.19 and nvidia-525.105.17<br> &gt;      &gt;<br>
&gt;      &gt;     But during boot text is not showing up/scrolling<br> &gt;      &gt;<br>
&gt;      &gt;     --<br>
&gt;      &gt;     Thelma<br>
&gt;      &gt;<br>
&gt; <br>

</blockquote></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

<div dir="ltr"><br><br>On Sat, Apr 22, 2023 at 11:56 AM &lt;<a href="mailto:thelma@sys-concept.com">thelma@sys-concept.com</a>&gt; wrote:<br>&gt;<br>&gt; I upgraded to kernel 6.1.19 and nvidia-525.105.17<br>&gt;<br>&gt; But during boot text is not
showing up/scrolling<br>&gt;<br>&gt; --<br>&gt; Thelma<br><br>Is this possibly a grub setting? Check /etc/default/grub or whatever <br>it might be on your system and look at <br><br>GRUB_CMDLINE_LINUX_DEFAULT=&quot;quiet splash&quot;<br><div><br></div><

If that&#39;s there then remove the word &#39;quiet&#39; and </div><div>run sudo update-grub or whatever is appropriate</div><div>for your system to set up the change.</div><div><br></div><div>HTH,</div><div>Mark</div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

<div dir="ltr"><br><br>On Mon, Apr 24, 2023 at 2:31 PM &lt;<a href="mailto:thelma@sys-concept.com">thelma@sys-concept.com</a>&gt; wrote:<br>&gt;<br>&gt; On 4/24/23 14:39, Mark Knecht wrote:<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt; On Sat, Apr 22, 2023 at
11:56 AM &lt;<a href="mailto:thelma@sys-concept.com">thelma@sys-concept.com</a> &lt;mailto:<a href="mailto:thelma@sys-concept.com">thelma@sys-concept.com</a>&gt;&gt; wrote:<br>&lt;SNIP&gt;<br>&gt; # Append parameters to the linux kernel command line
for non-recovery entries<br>&gt; #GRUB_CMDLINE_LINUX_DEFAULT=&quot;&quot;<br>&lt;SNIP&gt;<div><br></div><div>Consider uncommenting this line and running sudo update-grub</div><div><br></div><div>&gt; # The resolution used on graphical terminal.<br>&gt; #
Note that you can use only modes which your graphic card supports via VBE.<br>&gt; # You can see them in real GRUB with the command `vbeinfo&#39;.<br>&gt; #GRUB_GFXMODE=640x480</div><div>&gt; GRUB_GFXMODE=1024x768x32<br></div><div><br></div><div>While
I understand that you probably didn&#39;t change this setting do</div><div>you know that 1024x769x32 is ok?</div><div><br></div><div>Have you run vbeinfo or verified by some other means?</div><div><br></div><div>HTH,</div><div>Mark</div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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/

>           (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/

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEGfLZTV7dXdQXh/dDdCdyyQfftocFAmRHgN4ACgkQdCdyyQff tofWAQ//d65bxBXDTgSXgITecTrfeRy/eFllwh0rxHoHn2sXPX9XwldTKgOMXiZ8 HjuHN+dppSPkrGi0AA0EG1sfZwGlJNCEKk0us8MfZLQrjPb3PdKatuq8QGYqgJom yK61F1yAxoeVz9ydyoBb0g+end7esOkdIC4LMHgsix+ADm26z9uXigj/zAMGT3NR duBb57yehPX9bBsPT4rtTuFgvt1rfW9vQfFaCyh7WGakoEFX2Jsl/7IixYuBbKU+ V8IZeJO2B5/jXHEGoQx+w0lThKKrKV21BjxffGhOkx6Z//knkcfxe9it30N780DA z74DLy80q/xSmXvPdRA7YCCH7q3u3MaTVaucZg0gP9LV57hsLC1jRNSnBDems74F Y1QYYPbtMIdT/xvpK2jV+se7v3EDIFmoAYExQ0AJeY+zVD9KJLhvMuyBtB3Ic+X7 DWaTIBYo1dAUTKQ6cZU0WpJwAGVbprPAhfEpFttjjF9p4kt8kWEd67Xn2MCdzKL9 xXRHzKneqKysakUfbIfqK8mMLur77eklHLHkI6hDI6WOo+3tc+yhri21QH1L6Wlu NRwY4mirZtfJfByoWWLjWLXv9DLDENJxaDFXQv7u5Jf1G97LCqgsjTZ1aHhOiqg8 shjVegB5DkjyhIfhjcUWb+0gBejIleZYsXtk7z10W/ilMcQNFWQ=
=2Ox5
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEGfLZTV7dXdQXh/dDdCdyyQfftocFAmRIEHEACgkQdCdyyQff tofynw/+NkDUdSKNyseCd98/jcDR7CyYAxVhW5dcYoAmJdQuVvzS0UGHg3TGJxFr vgF0oYYlWAGMu0uNz/EmAj1kQ6h3BUd+VCjY+mKvNyCRNFobkpor29QTOT/Cw9Bd dDNh9T42EPTuicxpM01IFmZ08GuNhuVGxyTAEeJIAE44+VTMRiL3fx7Oh2vCMgaK Mhea05ow3A1VAz10YVppwumKPM1s6/fgQX0PpN6IjqaeD5gveaxwx9ax6Grjck6l bEvYjioz6z7KAGvP7JiKu6s37XHjfVbMHhFWZDpumNRY+tS+f97KZVgmNHLsrm0S VNAlA/GIy56bajkRn+9rMOJeyY6WDo0p+EUKGPMgG+MC3VDbyBzitcqiM0jUg9VN XH55X9jmzUqhgsqV2+2ZvuQi+00Dc8HeUWQ+tel6kNg12EgD7P2nUXe7IiIhzLJj FMDDea5rqEmGTHk7JEoIvgsdwJusc1lNcuHKIq+nMmSHrVr3JWygEVPhkaZdMH97 ZDGh+8zqZbmLh9EBIVfXmdW/plAUXMYsymCcUJ7a39AZC5nvtCwfRk2mWm5sSanz PeKWimtBGIiELHrFnO5mm97+F7tJxsBqD0SiyaK66FlHFN5FILHt1zrgIPPi83HB e3jC/Ymrhx6V7c9wCxGx2Gg86GOyRkYDHY+PXe5/EyaSJG84LKc=
=Bej0
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)