Sweet! I thought I was going to have to recompile the whole kernel to test this out. So you're saying I can follow steps 1-5 with the drivers from CVS and then reboot and I should be running the latest hda module? Or do I also have to do step 6 as well? Thanks very much. <div>On 3/22/06, Martin Stransky <<a href="mailto:stransky@redhat.com">stransky@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">The patch was merged to ALSA CVS so you may check the new alsa-driver (when it comes) or download the affected file from ALSA CVS and merge it to the latest driver package. how-to is here - <a href="http://people.redhat.com/stransky/alsa">http://people.redhat.com/stransky/alsa</a> Ma. Sadda Teh wrote: > 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. > > On 3/21/06, *Dan Williams* <<a href="mailto:dcbw@redhat.com">dcbw@redhat.com</a> <mailto:<a href="mailto:dcbw@redhat.com"> dcbw@redhat.com</a>>> wrote: > > 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> > <<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> <mailto:<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>