Re: Hard drives recognized at only DMA

From: Grzegorz Czaplinski (G.Czaplinski_at_prioris.mini.pw.edu.pl)
Date: 12/07/03

  • Next message: Alexander Matthaei: "installation problems"
    Date: Sun, 7 Dec 2003 11:21:37 +0100
    To: Rafi Lurman <rlurman@adelphia.net>
    
    

    On Sun, Dec 07, 2003 at 02:17:31AM -0500, Rafi Lurman wrote:
    > I have two hard drives on the same cable, 1 master and 1 slave. They are both ATA133 IDE drives, but when I'm booting up FBSD 5.1 it says "ad0: DMA Limited to UDMA 33, non ATA66 cable or device". And it says the same for ad1. I am fairly sure that I'm using an 80-wire UDMA-133 IDE cable. So what could be causing FBSD to set the drives to only UDMA 33? Thanks.
    > _______________________________________________

    What if you remove one of the drives?
    Have you tried to change the cable? It looks like a cable problem.

    Cheers,
            greg

    --
    Grzegorz Czaplinski <gregory at prioris.mini.pw.edu.pl>
    "The Power to Serve, Right for the Power Users!" - http://www.FreeBSD.org/
     Fingerprint: EB77 E19D CFA2 5736 810F  847C A70F A275 2489 469F
    _______________________________________________
    freebsd-newbies@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
    To unsubscribe, send any mail to "freebsd-newbies-unsubscribe@freebsd.org"
    

  • Next message: Alexander Matthaei: "installation problems"

    Relevant Pages

    • Re: Hard Drive Size
      ... F is a clone of C and both are 160 GB drives. ... Are both positions internal IDE connections? ... original position. ... means that it isn't a cable problem or a C/S problem. ...
      (alt.os.windows-xp)
    • Re: Hard Drive Size
      ... F is a clone of C and both are 160 GB drives. ... Did you change the cables too? ... means that it isn't a cable problem or a C/S problem. ...
      (alt.os.windows-xp)
    • Re: Hardware problem in my Linux box
      ... Harold Weissman writes: ... {DriveReady SeekComplete Error} ... I have seen such things on drives that seem ... Then it's probably not a cable problem. ...
      (comp.os.linux.hardware)