Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!weretis.net!feeder4.news.weretis.net!news.netcologne.de!newsfeed-fusi2.netcologne.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Newsgroups: comp.os.linux.hardware Subject: Re: Disk stuck at PIO (not UDMA) Date: 19 Jun 2011 01:57:01 GMT Lines: 22 Message-ID: <9653bdF9p1U1@mid.individual.net> References: <0c4ba9ba-6088-4f02-b562-4ba3511e8848@x3g2000yqj.googlegroups.com> X-Trace: individual.net /NMvfWS4qNFh68fVDnBhuAu9j8KAPJ5+rXZs/GFeV8wI0/Zw== X-Orig-Path: not-for-mail Cancel-Lock: sha1:Jv+rrNHez3sPVnrGPL0Sz4xYHAY= User-Agent: tin/1.9.6-20100522 ("Lochruan") (UNIX) (Linux/2.6.38.8 (i686)) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.hardware:442 rusi wrote: > I have a Seagate Barracuda 160G PATA drive :ST3160215A > Windows (device-manager) is fixed at PIO. > Linux gives a bunch of errors on startup for trying UDMA and finally > starts in PIO. > Incidentally I tried uninstalling the windows driver and restarting > the machine in windows. > It first showed Multi-word DMA Mode 2 then after a minute it again > went back to PIO. This is typically a cable problem. Althernative a defective disk or disk controller chip. But the disk data cable is the prime suspect. Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans