[SATLUG] kernel 4.0
sargonemail at gmail.com
Wed Apr 15 20:50:41 CDT 2015
One option is to set LILO or GRUB to use a serial console as the boot
console and then hook a laptop up with a serial cable and use a terminal
emulator to capture the boot process.
Modern hardware method to redirect console: edit /boot/grub/grub.conf and
adding "console=ttyS0" to the end of the boot line and attaching an old dot
matrix printer to /dev/ttyS0 ;)
On Wed, Apr 15, 2015 at 8:41 PM, Craig <sargonemail at gmail.com> wrote:
> Historically, console was redirected to serial port appropriate "screen
> capture" device (file, printer, display).
> Ummm... give prior moths discussion, redirecting to floppy attached to usb
> serial port might be a bad idea. ;)
> with /dev/stty0 redirected to a file or as input to a screen capture
> program might do the trick.
> On Wed, Apr 15, 2015 at 8:21 PM, Craig <sargonemail at gmail.com> wrote:
>> > Borris Demeler wrote:
>> > I am struggling with the 4.0 kernel - the kernel and modules compile fine,
>> > but it doesn't get very far in the booting process before a kernel panic
>> > strikes. My problem is this:
>> > The screen flashes by too fast to read, so I am not sure what is causing the
>> > panic, and of course no dmesg is saved on the box that could be evaluated.
>> > What trick can I use to examine the trace of the bootup process?
>> Run it under a VM instance and either trace the bootup process using tools outside of the VM and/or
>> outside of the VM redirect the console to a file.
More information about the SATLUG