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.
On 3/22/06, Martin Stransky <stran...@redhat.com> wrote: > > 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 - http://people.redhat.com/stransky/alsa > 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* <d...@redhat.com <mailto:d...@redhat.com>> > wrote: > > > > On Tue, 2006-03-21 at 13:57 -0500, Sadda Teh wrote: > > > Might anyone be willing to apply the patch mentioned here: > > > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1895 > > <https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1895> (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 > > fedora-devel-list@redhat.com <mailto:fedora-devel-list@redhat.com> > > https://www.redhat.com/mailman/listinfo/fedora-devel-list > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://redhat.com/pipermail/fedora-devel-list/attachments/20060322/0ca4635d/attachment.html From drago...@feuerpokemon.de Wed Mar 22 12:51:07 2006 From: drago...@feuerpokemon.de (dragoran) Date: Wed Mar 22 12:51:11 2006 Subject: Anaconda: good work! In-Reply-To: <1143045982.24028.14.ca...@orodruin.boston.redhat.com> References: <131501c64dc2$fe1522b0$b6491...@td612671> <44217267.3070...@city-fan.org> <1143045982.24028.14.ca...@orodruin.boston.redhat.com> Message-ID: <44218e8b.2080...@feuerpokemon.de> I don't know if this is a feature or a bug but it seems like a bug: I tryed a harddisk install (the image was on /dev/md0 ) but I could'nt select it it only showed all /dev/sd(a|b)X but not /dev/md0 any reason for that or is this a bug?
