Messages in this thread | | | Date | Thu, 26 Dec 2002 14:22:28 +0100 | From | Tomas Szepe <> | Subject | Re: Alot of DMA errors in 2.4.18, 2.4.20 and 2.5.52 |
| |
> On Wed, Dec 25, 2002 at 12:58:20PM +0100, Tomas Szepe wrote: > > > For some funny reason, a 2.4.20 kernel refuses to set the DMA-level on > > > the new disks (all connected to a UDMA5-capable Ultra100 TX2 controller) > > > to UDMA5,4,3 and settles it for UDMA2, which is the highest possibility > > > for the OLD onboard-controller (but NOT for the promise card). > > > > You need to boot 2.4.19 and 2.4.20 with 'ideX=ata66' where X is the > > number of the channel where you wish to use transfer modes above UDMA2. > > For instance, "ide0=ata66 ide1=ata66" will do the trick for the first two > > hdparm -X69 /dev/hda will put it into UDMA5/ata100 mode as well > (69 == 64 + UDMA mode). No need to specify it at boot time.
Not true. You definitely need to use the ideX boot param AND run hdparm -X?? /dev/hd? to make use of UDMA3+ on newer PDC controllers (unless you apply the patch posted on Dec 24 by Nikolai Zhubr).
-- Tomas Szepe <szepe@pinerecords.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |