<br><br><div class="gmail_quote">2010/2/13 Tomasz Torcz <span dir="ltr"><<a href="mailto:tomek@pipebreaker.pl">tomek@pipebreaker.pl</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sat, Feb 13, 2010 at 11:35:53AM -0600, Bruno Wolff III wrote:<br>
> On Sat, Feb 13, 2010 at 09:27:59 -0800,<br>
> darrell pfeifer <<a href="mailto:darrellpf@gmail.com">darrellpf@gmail.com</a>> wrote:<br>
> ><br>
> > <a href="https://bugzilla.redhat.com/show_bug.cgi?id=562514" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=562514</a><br>
> ><br>
> > You may have to edit you grub.conf. Look for missing lines compared to<br>
> > working stanzas.<br>
><br>
> That might not be the problem here. I am getting the initrd lines added<br>
> now when I install new kernels. And when you have this problem an obvious<br>
> error messages is displayed (at least when you have grub set to let you<br>
> see what's happening when you boot).<br>
<br>
</div> Please double-check initrd paths. Mine had superflous "/boot" in them.<br>
As I have separate /boot partitions, grub.conf should have just<br>
"initrd /initrams-...", without "/boot/".<br>
<font color="#888888"><br></font></blockquote><div><br></div><div>I've also had a couple of other oddities this week that have caused hangs.</div><div><br></div><div>A version of rsyslog was causing the boot to hang. Moving it out of init.d for a while fixed it until a new version came along.</div>
<div><br></div><div>The latest intel driver isn't working for me. I backed out to the next oldest version.</div><div><br></div><div>darrell</div></div><br>