Messages in this thread | | | From | Bartlomiej Zolnierkiewicz <> | Subject | Re: (was Re: [RFC] IDE 80-core cable detect - chipset-specific code to over-ride eighty_ninty_three()) | Date | Fri, 13 Feb 2004 18:33:03 +0100 |
| |
On Thursday 12 of February 2004 21:41, Miquel van Smoorenburg wrote: > In article <200402122106.41947.bzolnier@elka.pw.edu.pl>, > > Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> wrote: > >Hi, > > > >word93 of drive identify is: > > > >0x603b for IC35L120AVV207-0 > >0x3469 for QUANTUM FIREBALLlct20 30 > > > >and eighty_ninty_three() checks for bit 0x4000, so... > > > >Willy, it seems you are hitting some other problem. > >Have you already tried booting with "ide0=ata66"? > > That reminds me, there is currenly no way to boot with > ide0=ata33, right ?
Right.
> I have a tyan motherboard with a serverworks chipset, and the > (2.5" system-) disk is connected with a 40 pins cable. However > the serverworks chipset doesn't detect this, and tries to run > it in UDMA<lots> mode. That results in lots of nasty messages > before it falls back to UDMA33 mode.
It sounds like driver or BIOS bug. Can I get dmesg from this system?
> Could you put a way to force it into UDMA33 (UDMA2) mode on the > wishlist, please ?
Yep.
- 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/
| |