You are not logged in.
I already know about
cat /dev/vcs1 > /path/to/some_fileand
setterm -dump 1 -file /path/to/some_filebut these only work for what is actually on tty1's screen when the command is run (i.e., lines in the scrollback buffer do not get written to the file). I have "fbcon=scrollback:512" in grub2's kernel line, in case it matters.
(I am trying to recreate the old /var/log/boot but, since even in quiet mode grub2 prints [FAIL] and all the [OK] messages that follow, if the [FAIL] occurs early enough it scrolls off the screen. See here: https://bbs.archlinux.org/viewtopic.php … 1#p1439361)
EDIT: Link fixed. Thanks for the heads up, karol.
Last edited by bdantas (2014-07-24 20:31:46)
Offline
Please fix the link, it should be https://bbs.archlinux.org/viewtopic.php … 1#p1439361
Last edited by karol (2014-07-24 11:49:39)
Offline
Is it impossible to copy the contents of the scrollback buffer of a virtual console (e.g., tty1) to a file?
Offline
in theory you could dump the contents of the scrollback, this is the pointer to it https://git.kernel.org/cgit/linux/kerne … 6-rc7#n185
you could dump that before the console gets switched*, right before here: https://git.kernel.org/cgit/linux/kerne … 6-rc7#n846
* e.g. when X gets started and is about to get graphical
Offline
Is it impossible to copy the contents of the scrollback buffer of a virtual console (e.g., tty1) to a file?
Offline
I use 'systemd.show_status=0' along with 'quiet' to keep systemd from printing stuff I don't need.
Isn't systemd's journal enough to figure out what went wrong?
Offline
Yes, "sudo journalctl -b -p err" shows me exactly what went wrong, so I think there is no need to pursue this further.
Offline
Please remember to mark the thread as solved https://bbs.archlinux.org/viewtopic.php?id=130309
Offline
I favor that it isn't solved because what I asked is not possible. Fortunately, the journal obviates the need for a solution. Is it customary to mark as "solved" when a workaround is found?
Last edited by bdantas (2014-08-02 23:35:20)
Offline
Ah, OK.
Have you tried to keep the messages in the tty and start X from another tty, if needed?
You can then copy the messages by hand.
Offline
Exactly. Either that or, if X starts automatically in tty1 due to autologin enabled in DM, using "sudo journalctl -b -p err" to get equivalent information.
Offline