Understood, I'm assuming that the changes will go into the kernel once they release their next RC (I hope). In the meantime I'll try to compile in the patch myself and see if it actually makes a difference. BTW, great kernel compilation instructions in the release notes. Thanks to whoever wrote those. Now, I'll go pester the folks at Alsa to get that patch upstream. <div>On 3/21/06, Dan Williams <<a href="mailto:dcbw@redhat.com">dcbw@redhat.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Tue, 2006-03-21 at 13:57 -0500, Sadda Teh wrote: > Might anyone be willing to apply the patch mentioned here: > <a href="https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1895">https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1895 </a> (You have > to click the Guest Login link to view) > > I, and probably many others have a motherboard affected by this bug. > It would be much appreciated if the fix would make it into FC5. > Thanks! Unless patches are crashers, they likely won't make it into FC5 without being in the upstream kernel. Work with the ALSA project to make sure that patch gets into the upstream kernel ASAP, and it will show up in Fedora quite soon after that. Part of this is for quality reasons; if the patch makes it into the kernel, then it's likely it's good enough. It's also for API reasons and maintainability. The less different Fedora kernels are from upstream "vanilla" kernels, the less work it is to update Fedora kernels every time a new upstream kernel is released. Dan -- fedora-devel-list mailing list <a href="mailto:fedora-devel-list@redhat.com"> fedora-devel-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/fedora-devel-list">https://www.redhat.com/mailman/listinfo/fedora-devel-list</a> </blockquote></div>