OK, I removed my patches to get access to detail mode again and the tty is filling with "couldn't write a log entry; log text too long" messages, but there is also some other output that scrolls past too fast for me to get it.<br>
<br><div class="gmail_quote">On Mon, Sep 27, 2010 at 5:54 PM, Jerome Martin <span dir="ltr"><<a href="mailto:jxm@risingtidesystems.com">jxm@risingtidesystems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Mmmhh. I am not familiar with these options so I blindly copied them, but it does not work. Only the kernel logs in dmesg, and same as before /dev/vcs1. Here is my full commandline (tried both with and without plymouth:debug as I suspect it might be redundant with plymouth.debug= ). An echo in /dev/kmsg does show up in dmesg ok. I also tried moving the options on the line, still no cigar.<div>
<br></div><div><div>[ 0.000000] Command line: initrd=/live/initrd.img boot=live noprompt nouser splash vga=0x311 plymouth:debug plymouth.debug=file:/dev/kmsg printk.time log_bug_len=1M BOOT_IMAGE=/live/vmlinuz </div><div>
<div></div><div class="h5"><div>
<br></div><br><div class="gmail_quote">On Mon, Sep 27, 2010 at 4:18 PM, Ray Strode <span dir="ltr"><<a href="mailto:halfline@gmail.com" target="_blank">halfline@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<div><br>
On Mon, Sep 27, 2010 at 3:13 AM, Jerome Martin<br>
<<a href="mailto:jxm@risingtidesystems.com" target="_blank">jxm@risingtidesystems.com</a>> wrote:<br>
> Fred here is using a patch very similar to my own, basically moving<br>
> the TIOCSCTTY of init out of plymouth's way.<br>
> As for the logs, I use a much stripped down system environment, with a ro<br>
> root and a COW on top of it that does not get mounted right away, so that<br>
> might explain the log issues.<br>
</div>Oh, okay. So, if the file system might be read-only at the time<br>
plymouth quits, then you should be able to boot with<br>
<br>
plymouth.debug=file:/dev/kmsg printk.time log_bug_len=1M<br>
<br>
on your kernel command line and the debug output will go to "dmesg"<br>
along wth nice timestamps. Then you can just<br>
<br>
dmesg > output.txt<br>
<br>
and post it here.<br>
<font color="#888888"><br>
--Ray<br>
</font></blockquote></div><br><br clear="all"><br></div></div>-- <br>Jérôme Martin<br>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Jérôme Martin<br>