This time Leon Brooks <[EMAIL PROTECTED]> becomes daring and writes:
> On Thursday 06 March 2003 10:47 am, Vox wrote: >> This time "Alexander Rayborn" <[EMAIL PROTECTED]> >> becomes daring and writes: >>> I've not been able to use Mandrake since 9.0. I've been hoping that the >>> PDC20276 problems would be fixed with 9.1, but from the looks of the >>> release candidates and betas it doesn't look like that's the case. >>> Since it works fine in Red Hat 8.0, looks like I will have to go there >>> again (or maybe 8.1 Phoebe). I don't really understand why someone at >>> Mandrake doesn't just buckle down and ask someone at Red Hat what to do >>> about the PDC20276 problem since it works fine in RH's distros. That's >>> a lot of customers that Mandrake will lose to the newer ATA100/133 >>> controllers if they don't get it fixed. Shame. > >> And I just found this out the hard way too :/ I got a new box last >> night, with a PDC20276 and...2.4.21 doesn't want to work there :/ > >> The strange thing is...2.4.19-16mdk works perfectly fine with it >> (well...the alsa drivers for the sound of this mboard suck...but >> that's a different matter). > >> If somebody can shine a light on this problem, I'd be more than >> happy > > https://listman.redhat.com/pipermail/ataraid-list/2002-December/001396.html: > > The only problems I've had was with 2.4.20-ac1 - it didn't recognize > the RAID - but now all goes well because I switched back to the > vanilla 2.4.20 > > IIRC, Mandrake like -ac style kernels? If so, maybe a hint in there. Mmmm...that may be where the problem comes from...the main difference I see between 2.4.19-16mdk (which works perfectly fine with this controller) and 2.4.21-can't-remember-what (which doesn't work) is that the .19 has only one driver for this controller, while .21 has a PDC202XX_OLD and a PDC202XX_NEW...and neither of them work :/ > WRT performance, this raises it from 2MB/s to 30MB/s for one user: Thanks...with .19-16mdk I have no performance issues at all...all my 3HDs do 30MB/s no problem > Also, this mention: > https://listman.redhat.com/pipermail/ataraid-list/2002-December/001396.html > When I set "CONFIG_PDC202XX_FORCE=y" to: "# CONFIG_PDC202XX_FORCE is > not set" in the config file and then recompiled the 2.4.19 kernel, > it solved my problems. Obviously there is something wrong with > this code. In my working 19-16mdk (compiled by mandrake, got it from cooker some time ago), I have it set to not set, so I was thinking that one is close to the truth...but in 21-0.11mdk (which doesn't work) I have the # CONFIG_PDC202XX_FORCE is not set also...and it still doesn't work. So, in the end...I *think* the problem comes from the driver splitting, but I can't be sure because I didn't try a single kernel between 19-16mdk and 21-0.11mdk Vox -- Think of the Linux community as a niche economy isolated by its beliefs. Kind of like the Amish, except that our religion requires us to use _higher_ technology than everyone else. -- Donald B. Marti Jr.
pgp00000.pgp
Description: PGP signature
