<div dir="ltr">On Tue, Jun 18, 2013 at 9:46 AM, Devin Heitmueller <span dir="ltr"><<a href="mailto:dheitmueller@kernellabs.com" target="_blank">dheitmueller@kernellabs.com</a>></span> wrote:<br><div class="gmail_extra">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, Jun 18, 2013 at 9:43 AM, Tom Lichti <<a href="mailto:tom@redpepperracing.com">tom@redpepperracing.com</a>> wrote:<br>
> Instead of trying to find the needle in a haystack, do this:<br>
><br>
> grep -i -E "kworld|dvb" /var/log/messages<br>
><br>
> and<br>
><br>
> dmesg | grep -i -E "kworld|dvb"<br>
><br>
> The '-i' modifier says to ignore case, and -E is extended regexp, so it will<br>
> look for lines with kworld OR dvb.<br>
><br>
> If you want to view the whole file, by all means do the above, but trying to<br>
> find a single line amongst thousands by eye is going to be difficult.<br>
<br>
</div>Just an FYI: this is generally a bad idea. There are many very<br>
important lines that won't show up in a grep for kworld or dvb, which<br>
would be required by anybody who actually knows how to review the log<br>
file.<br>
<br>
Far better to yank the board for ten minutes, do a boot with the one<br>
card, run dmesg once, and then post the results. There won't be too<br>
much in there that accumulates in there in the 2-3 minutes it takes to<br>
boot the computer and get to a prompt (probably a couple thousand<br>
lines at most).<br>
<br>
Regards,<br>
<br>
Devin<br><br></blockquote><div><br></div><div>If he's trying to determine if there is a kworld board, this will tell us, as we are still trying to determine that. Your method works too. :)</div><div><br></div><div>It's also a learning process for the OP, since he is clearly not that familiar with Linux yet, just trying to add a tool to his arsenal.</div>
<div><br></div><div>Tom</div><div><br></div></div><br></div></div>