<p><br>
On Mar 18, 2012 3:17 PM, <<a href="mailto:andersvi@notam02.no">andersvi@notam02.no</a>> wrote:<br>
><br>
> >>>>> "S" == S C Rigler <<a href="mailto:riglersc@gmail.com">riglersc@gmail.com</a>> writes:<br>
><br>
> S> Seriously though, is there a list of "here try this" type of<br>
> S> things we can do?<br>
><br>
> Dont know of any list.<br>
><br>
> About the black screen after boot: a temporary workaround after boot is<br>
> possible at times by going to a text-console (fex. Ctrl-Alt-F2 ) and<br>
> kill X ('sudo killall -9 Xorg'), and if youre lucky X might come up and<br>
> present you a nice gdm.<br>
><br>
> As others have posted, make sure you get rid of any leftovers from<br>
> previously attempted drivers by whatever means you find.<br>
><br>
> Good luck.<br>
><br>
> -anders<br>
></p>
<p>This is actually a hard lockup when running the proprietary driver and not really a situation where I can switch to a text console. </p>
<p>I have made some progress with nouveau, however. I've enabled msi in snd-hda-intel and nouveau. Apparently you have to rebuild the initrd when changing parameters in modprobe.d. My laptop also has some quirks that I used to work around with some boot options on 2.6 kernels but at least one of those options has been renamed. So at this point it appears that things are better with nouveau. I'd like to revisit the proprietary driver at some point but it doesn't look like it's a show stopper anymore. </p>
<p>--Steve <br>
</p>