How does one do it?! Or is this no longer possible???
I'm getting unexpected errors during boot that scroll off the screen too fast and/or I'm getting black screens (AMD driver and UP4 don't seem to like each other at all). If i can enable boot logging, then I could access the logs remotely via telnet/ssh. However, it would appear that /etc/default/bootlogd is no longer present after installing UP4 and recreating it doesn't seem to help either.
Enabling Boot Log after LMDE UP4
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
Enabling Boot Log after LMDE UP4
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Enabling Boot Log after LMDE UP4
It's obsolete now./etc/default/bootlogd is no longer present after installing UP4
So just run
Code: Select all
sudo apt-get install bootlogd
Re: Enabling Boot Log after LMDE UP4
Many thanks. I missed that while searching, I kept finding pages referencing the now obsolete method.Monsta wrote:It's obsolete now./etc/default/bootlogd is no longer present after installing UP4
So just run
and that should do itCode: Select all
sudo apt-get install bootlogd
Re: Enabling Boot Log after LMDE UP4
Many thanks here, too. The 3.2 kernel clears the screen after booting. I missed having those boot messages to check for errors.
Re: Enabling Boot Log after LMDE UP4
...
Last edited by Gandalf the White on Wed Apr 02, 2014 2:21 am, edited 1 time in total.
Re: Enabling Boot Log after LMDE UP4
It's always useful to read the thread before replying to it. Especially when necroposting.Gandalf the White wrote:I've turned on the boot log (I think), but it is empty. So maybe it is not turned on.