<p>I'm not sure what the issue is; i was running a stock 2.6.22 debian kernel and framebuffer itself seemed to work fine. Did the 2.6.24 kernel make the switch to uvesafb from vesafb?</p><p>The real problem I encountered on debian was that even with a working framebuffer, splashy kept making the system hang on boot; some sort of problem with libdirectfb causing it to timeout:</p>
<p><a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454917">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454917</a><br></p><br><div><span class="gmail_quote">On 3/15/08, <b class="gmail_sendername">Yan Seiner</b> <<a href="mailto:yan@seiner.com">yan@seiner.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
Scott D. Davilla wrote:<br> ><br> > If you are Ubuntu (maybe applies to debian too), they by default<br> > blacklist most all framebuffers. The incantation is<br> ><br> > Commented those lines in /etc/modprobe.d/blacklist-framebuffer :<br>
> #blacklist nvidiafb<br> > #blacklist vesafb<br> > Added those lines to /etc/initramfs-tools/modules:<br> > fbcon<br> > vesafb<br> > Then running update-initramfs.<br> Well the crazy thing is that I can't get vesafb or fbcon to build as<br>
modules. I'm using a vanilla 2.6.24 kernel. The only option I have is<br> to build them into the kernel....<br> <br> Anyone know how to build those as modules in 2.6.24?<br> <br><br> <br> <br> _______________________________________________<br>
mythtv-users mailing list<br> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</blockquote></div><br>