Messages in this thread | | | Date | Thu, 1 Oct 1998 18:16:26 -0500 (CDT) | From | "Andre M. Hedrick" <> | Subject | Re: IDE problems ( set_multmode:error=0x04 {Drive Status Error} ) |
| |
poke this in around ide.c:2607
This out of 2.0.35 patched against Jumbo-9 of my contributions to that monsterpatch.
drive->mult_count = 0; if (id->max_multsect) { - drive->mult_req = INITIAL_MULT_COUNT; - if (drive->mult_req > id->max_multsect) - drive->mult_req = id->max_multsect; - if (drive->mult_req || ((id->multsect_valid & 1) && id->multsect)) - drive->special.b.set_multmode = 1; + id->multsect = ((id->max_multsect/2) > 1) ? id->max_multsect : 0; + id->multsect_valid = id->multsect ? 1 : 0; + drive->mult_req = id->multsect_valid ? id->max_multsect : INITIAL_MULT_COUNT; + drive->special.b.set_multmode = drive->mult_req ? 1 : 0; } + +drive->no_io_32bit = id->dword_io ? 1 : 0;
This change forces multisect to be set, if capable.
Cheers, Andre
On Fri, 2 Oct 1998, Meelis Roos wrote:
> R> I have see something wrong on my Debian 2.0 with (kernel 2.0.34) on > R> one pentium pro II. > R> > R> hda:hda: set_multmode > R> ststus=0x51 { DriveReady SeekComplete Error} > > The HD is probably a Samsung (3.x G?). These hard disks say that they > support multmode (it's multiple sectors per interrupt when using pio modes) > and the max is 16. But they refuse to set it to 0, they want only positive > numbers for multmode. Perhaps 0 > 16 now? :-) > > You can ignore the message, it does no harm AFAIK. Or you might want to use > default multmode of 16, not 0 (slight modification to the kernel). > This may not work with older HD-s though. > > -- > Meelis Roos (mroos@tartu.cyber.ee) > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/ >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |