On Wed, May 17, 2017 at 2:12 PM, Niels Jakob Buch <njb...@gmail.com> wrote:
> That makes sense, will try that. > > But are there no log-file where this kernel output is stored? > Well it could be, but I do not think Robert persists logs between reboots. Maybe I'm wrong. So then assuming if what I say is true, you'd have to hope the error is actually logged. Then the problem is that if you lose all connectivity, how do you propose to see that information ? With a serial debug cable, you'll be directly connected to a tty terminal, so networking issues will not effect that. Which means not only can you get additional debug info, but you can also log into the system, for further troubleshooting if needed. You can try to use: root@wgd:~# more /var/log/messages or root@wgd:~# more /var/log/kern.log But I do not think either of these will do you any good. You can check to make sure though. Do keep in mind there will be a lot of info in there that does not have anything to do with what you're looking for. So you may run out of time before you get done reading through the files. However, if you have another Linux machine, you could scp those files to a remote system. If you are using Windows, there is a program called WinSCP I believe that should allow you to traverse into the /var/log directory, and copy those files out to your desktop. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORpE0_GEQ%2BV9sCgeLW-yC0NRgNZP8X1KivwTAigBdHr%2BxA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
