civileme,
Thank you for your help.
Trying with the noautotune option made the 2.4-kernel successfully
boot without errors and hdparm -t /dev/hda gave 12.50 MB/sec. After
that timing of hdb resulted in the 'hdb: dma_intr: ...' errors and
gave 4.3 MB/sec. The log file showed:
...
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: DMA disabled
Apparently the first (master) disk shuts off DMA mode and goes to
pio!? After that also the first disk was back to 4.3 MB/sec.
Encouraged by the speeds available I took a closer at the cable
connecting the two disks. Due to cable length problems the cable
sitting there is a maxitower cable with four disk contacts (only two
are needed). Changing the contact for the second (slave) disk and
positioning the cable solved the problem, hooray! Now both disks run
with DMA and speeds between 12 and 12.5 MB/sec, and the noautotune
option to ide0 is not needed any longer for booting kernel-2.4.
/Svante
civileme writes:
> On Sunday 07 January 2001 19:09, you wrote:
> > civileme,
> >
> > Enclosed please find the information requested. The boot log is from
> > kernel-2.4.0-0.15mdk obtained by logging in remote via ssh (it takes a
> > loong time to get the bash prompt). Still cannot login from the
> > console :(
> >
> > /Svante
> Hrm,
>
> I would say try installing with
>
> linux ide0=noautotune ide1=noautotune
>
> Obviously the kernel is overzealous in setting the disks to the highest rate
> they'll go, so let's tell it to stop that behavior.... Just stick that into
>
> the append line for lilo or grub
>
> append="ide0=noautotune"
>
> should do it. If it autotunes your other devices, that's OK.
>
> Civileme
>
