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, [email protected] 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, [email protected] wrote:
On 4/24/23 15:41, Mark Knecht wrote:
On Mon, Apr 24, 2023 at 2:31 PM <[email protected]
<mailto:[email protected]>> wrote:
>
> On 4/24/23 14:39, Mark Knecht wrote:
> >
> >
> > On Sat, Apr 22, 2023 at 11:56 AM <[email protected]
> > <mailto:[email protected]> <mailto:[email protected]
> > <mailto:[email protected]>>> 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
