this post was submitted on 10 Aug 2024
22 points (100.0% liked)

linux4noobs

1271 readers
1 users here now

linux4noobs


Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.


Seeking Support?

Community Rules

founded 1 year ago
MODERATORS
 

Is there a way to log all the stuff on start up to a text file so I can read it? It goes by way too fast! Mine shows some blue warnings but I can't read them.

To be clear I mean the part that explains what is starting or failing, like if you hit [ESC] during start up or don't have plymouth, not the plymouth splash screens.

top 4 comments
sorted by: hot top controversial new old
[–] Ephera@lemmy.ml 15 points 1 month ago (1 children)

If you open up a terminal and run the dmesg command, it should show up.

If you'd like it in a file, you can pipe it via standard shell features like so:

dmesg > boot.log
[–] ArcaneSlime@lemmy.dbzer0.com 3 points 1 month ago (1 children)

Thanks! Looks like this has even more info in it than the start up does for some reason, too.

[–] Ephera@lemmy.ml 5 points 1 month ago (1 children)

Ah yeah, it's all kernel messages since the start of the boot, so it won't stop at the end of the boot process, but I also imagine the boot screen (Plymouth) only shows warning and error messages.

You can filter it to only show warnings and worse with:

dmesg --level=warn+

Here's some more infos on that: https://unix.stackexchange.com/questions/390141/how-to-filter-the-dmesg-log-to-see-only-the-errors