<div class="gmail_quote">On 9 May 2012 16:28, Matthew Sturdy <span dir="ltr"><<a href="mailto:matt.sturdy@gmail.com" target="_blank">matt.sturdy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>You could also look into /var/log/Xorg.0.log and see what X is doing on startup.</blockquote></div><div>Nothing obvious in there.. but I will check next time immediately after boot.</div></div></blockquote><div><br></div>
<div>Nope - there's nothing interesting in there... and it even seems to be finding the proper drivers:</div><div><br></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div class="gmail_quote">
<div><div>[ 180.874] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,</div></div></div><div class="gmail_quote"><div><div> i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,</div>
</div></div><div class="gmail_quote"><div><div> E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,</div></div></div><div class="gmail_quote"><div><div> 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,</div>
</div></div><div class="gmail_quote"><div><div> 4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,</div></div></div><div class="gmail_quote"><div><div> Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),</div>
</div></div><div class="gmail_quote"><div><div> Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),</div></div></div><div class="gmail_quote"><div><div> Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),</div>
</div></div><div class="gmail_quote"><div><div> Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),</div></div></div><div class="gmail_quote"><div><div> Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server</div>
</div></div></blockquote><div class="gmail_quote"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div class="im"><div>
<span></span></div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
One thing I like to try is to stop gdm/lightdm whatever, and then run<br>
startx. If it fails it often gives a helpful message. </blockquote></div><div>Good suggestion! thanks... Will try it next boot.</div><div></div></div></blockquote></div><br><div>This time when I dropped down to the console I killed the initx process that was running, and then ran startx. It started without errors.</div>
<div><br></div><div>It took me straight to my desktop, bypassing the usual login screens... where it prompted me to unlock the login keychain with my password. however, the desktop didn't seem to load properly, and after accepting my password, it stopped responding to the keyboard.</div>
<div><br></div><div>I return to tty3 and killed the process (CTRL+C). then I started gdm and all was ok again.</div><div><br></div><div>It seems to be a bug in gdm or unity at this stage.. .but I can't really raise it without knowing which!</div>
<div><br></div><div>Any other suggestions? </div><div>Matt</div>