You are not logged in.
I read the wiki and successfully applied:
- Have boot messages stay on tty1 / TTYVTDisallocate=no
- removed quiet in GRUB_CMDLINE_LINUX_DEFAULT
- enabled Early KMS start / MODULES=(nouveau)
One issue stays:
after "Loading initial ramdisk ..." the screen is cleared.
How can I disable this ?
Thanks for all pointers.
Last edited by ua4000 (2019-02-03 09:02:31)
Offline
"Loading initial ramdisk ..." - that's looks like bootloader. I don't believe you can keep its messages. Which bootloader do you use?
Offline
I'm using grub, almost with defaults,
except the last line is added:
$ egrep -i -v '^#|^$' /etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
GRUB_TERMINAL_INPUT=console
GRUB_GFXMODE=auto
GRUB_GFXPAYLOAD_LINUX=keep
GRUB_DISABLE_RECOVERY=true
GRUB_CMDLINE_LINUX_DEFAULT=""As far as I can see, the grub menue at booting time is somehow a graphical mode.
Offline
GRUB is independent and totally separate of whatever comes after it (initrd, windows, whatever) - you cannot scroll from one to the other.
Offline
Didn't you say you removed the quiet parameter?
Also this will require a re-run of grub-mkconfig after editing /etc/default/grub (or edit /boot/grub/grub.cfg directly)
Offline
Hi seth,
the last line removes the quiet, and yes I run grub-mkconfig.
Offline
I'm frankly unsure how the variables in the default are interpreted, "cat /boot/grub/grub.cfg"?
Offline
There is no quiet in my /boot/grub/grub.cfg - during boot I can see the infos about started services etc - so this part works fine.
Currently you can specify variables twice in /etc/default/grub, only the last one is used.
Offline
For clarification: do you get no boot messages or is this about "i want the stuff that was printed before loading the ramdisk to remain on screen" (to keep the grub dialog?)?
Offline
I see the grub menu, I see the message
Loading Linux linux ...
Loading initial ramdisk ...
and I see the messages from systemd (early hook, starting version 240), but at this time the grub infos were already cleared.
I assumed that I could prevent this clearing.
Offline
Not really. You could likely copy it and have it re-posted by the init script.
This sounds like an xy-problem? What's the point of keeping those two strings there?
Offline
I thought, I could keep those messages too, e.g. in case they show any error or unusual.
I have learned here now, that they are from grub, and that I cannot prevent them from clearing.
Thanks for all answers !
Offline
dmesg keeps a log of kernel messages from very early on.
except for those two lines from grub (which are just something that is defined in grub.cfg), my guess is there's everything in there from the moment the kernel is loaded (not initrd, i think, and definitely much earlier than systemd)
Offline