<br><br><div class="gmail_quote">On Sat, Mar 17, 2012 at 6:31 PM, Brendan Jones <span dir="ltr"><<a href="mailto:brendan.jones.it@gmail.com">brendan.jones.it@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="im">On 03/17/2012 09:16 PM, Fernando Lopez-Lezcano wrote:<br>
> On 03/17/2012 08:58 AM, S C Rigler wrote:<br>
>> Yesterday I decided to go from a working F14 installation using a<br>
>> 2.6.33-rt x86_64 kernel using the proprietary Nvidia driver to F16 using<br>
>> whatever Nvidia driver would work. So far I have yet to find something<br>
>> that works.<br>
>><br>
>> The stock Fedora kernel works fine running either nouveau or the<br>
>> proprietary Nvidia driver. I'm typing this while I am booted into<br>
>> 3.2.9-2 running nouveau.<br>
><br>
> Good to hear that at least that is working...<br>
><br>
<br>
</div>FWIW, I am having no issues using the latest CCRMA kernels, nouveau or<br>
the patched 290.10 prop driver (hw is 1040/rev a1).<br>
<br>
I do get kernel oops'es in VirtualBox/KVM that I don't with the stock<br>
kernel but that is another (for upstream).<br>
<br>
One recommendation though, is you should really ensure your system clean<br>
of the prop drivers (and your initrd) when falling back to the nouveau<br>
drivers. Use the --uninstall option from nvidia, then reinstall<br>
mesa-GL*, otherwise everything becomes a little confused.<br>
<br>
regards,<br>
<br>
Brendan<br></blockquote><div><br></div><div>I pretty much started out trying to make nouveau work since I don't like having to patch the proprietary driver.</div><div><br></div><div>FWIW, both nouveau and the proprietary driver show similar behavior on the stock kernel when I try to boot it with "threadirqs".</div>
<div><br></div><div>I'm still trying to get some good log messages. I have plenty from earlier today, but they weren't consistent with each incident.</div><div><br></div><div>--Steve</div></div>