3 ms·
> Don’t miss this step! dmesg is always worth checking. Best advice given in the whole article. Many times I go to check something that "can't figure out what
by baldfat 11y ago
> Don’t miss this step! dmesg is always worth checking.
Best advice given in the whole article. Many times I go to check something that "can't figure out what is wrong." dmseg | tail and then the swearing begins on their end.
- jandrese 11y agoCan you imagine a world where the Windows System Event Viewer was this useful? It's amazing how much time one useful error message can save. Also, I'm a little disappointed that the author didn't drill down into what the actual problem was in his example. That java process is of course suspicious, but that might just be the video server and expected behavior.
- digi_owl 11y agodmesg and being able to run most things in a terminal to check what its doing (grumble, skype, grumble) is likely what has drawn many to Linux in the first place. And a likely source of misgivings regarding recent developments in the ecosystem...
- baldfat 11y agojournalctl is a good tool. I really like SystemD but wish we still had plain text logs.
- zantana 11y agoOne improvement (which may or may not be related to systemd, but is in newer kernels) is that dmesg has timestamps enabled by default which makes it much easier and `dmesg -H` is really nice as well.
- simoncion 11y agodmesg -T Has been available for years to print out human-readable timestamps. Check to see if dmesg is an alias to that on your system. Also, -IIRC- dmesg has printed system-uptime timestamps with every line since at least the early 2000's. One caveat: the times printed by dmesg -T will be incorrect if the system has suspended to RAM or disk. Check dmesg(1) for more info! :D