Linux ATA/IDE development
 help / color / mirror / Atom feed
From: "Theepan" <tornado@linuxfromscratch.org>
To: Jeremy Huddleston <jeremyhu@uclink4.berkeley.edu>
Cc: linux-ide@vger.kernel.org
Subject: Re: Promise PDC20269 - PIO Only?
Date: Sun, 19 Oct 2003 23:18:30 +0200	[thread overview]
Message-ID: <002001c39686$8c949e40$0200a8c0@tornado> (raw)
In-Reply-To: 200310191200.26656.jeremyhu@uclink4.berkeley.edu

Hi,

Try pass "ide2=ata66" and "ide3=ata66" to the kernel at lilo prompt (or
using 'append' directive in lilo.conf). This requires that you use 80pins
cable instead of standard 40pins cable.

--
Theepan


----- Original Message ----- 
From: "Jeremy Huddleston" <jeremyhu@uclink4.berkeley.edu>
To: <gardiol@libero.it>; <linux-ide@vger.kernel.org>
Cc: "Mark Hahn" <hahn@physics.mcmaster.ca>
Sent: Sunday, October 19, 2003 9:00 PM
Subject: Re: Promise PDC20269 - PIO Only?


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> It's still in mode2 after the explicit -X69 or -X70.  I have a 20267 on my
> other system, and it goes to mode5 with just the -d1...
>
> 11:53:45 Sun Oct 19 2003 root@eradicator)
> ~ $ hdparm -d1 -X69 /dev/hde
>
> /dev/hde:
>  setting using_dma to 1 (on)
>  setting xfermode to 69 (UltraDMA mode5)
>  using_dma    =  1 (on)
>
> (11:53:51 Sun Oct 19 2003 root@eradicator)
> ~ $ hdparm -i /dev/hde
>
> /dev/hde:
>
>  Model=Maxtor 6Y120P0, FwRev=YAR41VW0, SerialNo=Y40BMM7E
>  Config={ Fixed }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
>  BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=off
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4
>  DMA modes:  mdma0 mdma1 mdma2
>  UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5 udma6
>  AdvancedPM=yes: disabled (255) WriteCache=enabled
>  Drive conforms to: (null):
>
>  * signifies the current active mode
>
> (11:55:38 Sun Oct 19 2003 root@eradicator)
> ~ $ hdparm -d1 -X70 /dev/hde
>
> /dev/hde:
>  setting using_dma to 1 (on)
>  setting xfermode to 70 (UltraDMA mode6)
>  using_dma    =  1 (on)
>
> (11:55:44 Sun Oct 19 2003 root@eradicator)
> ~ $ hdparm -i /dev/hde
>
> /dev/hde:
>
>  Model=Maxtor 6Y120P0, FwRev=YAR41VW0, SerialNo=Y40BMM7E
>  Config={ Fixed }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
>  BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=off
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4
>  DMA modes:  mdma0 mdma1 mdma2
>  UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5 udma6
>  AdvancedPM=yes: disabled (255) WriteCache=enabled
>  Drive conforms to: (null):
>
>  * signifies the current active mode
>
>
> On Sunday October 19 2003 02:39, Willy Gardiol wrote:
> > Ok, you should also set explicitly the dma mode:
> > hdparm -d1 -X69
> > (69=udma100...)
> >
> > Alle Sunday 19 October 2003 12:11, Jeremy Huddleston ha scritto:
> > > I have done this, and the result is that it still doesn't use the
drive
> > > to its full potential:
> > >
> > > (03:07:19 Sun Oct 19 2003 root@eradicator)
> > > ~ $ hdparm -d1 /dev/hde
> > >
> > > /dev/hde:
> > >  setting using_dma to 1 (on)
> > >  using_dma    =  1 (on)
> > >
> > > (03:07:25 Sun Oct 19 2003 root@eradicator)
> > > ~ $ hdparm -i /dev/hde
> > >
> > > /dev/hde:
> > >
> > >  Model=Maxtor 6Y120P0, FwRev=YAR41VW0, SerialNo=Y40BMM7E
> > >  Config={ Fixed }
> > >  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
> > >  BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=off
> > >  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728
> > >  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> > >  PIO modes:  pio0 pio1 pio2 pio3 pio4
> > >  DMA modes:  mdma0 mdma1 mdma2
> > >  UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5 udma6
> > >  AdvancedPM=yes: disabled (255) WriteCache=enabled
> > >  Drive conforms to: (null):
> > >
> > >  * signifies the current active mode
> > >
> > > The PDC-Specific drivers are all compiled into the kernel
> > >
> > > On Sunday October 19 2003 00:08, Willy Gardiol wrote:
> > > > Have you tried to enable uDMA using hdpard after boot?
> > > > hdparm -d1 /dev/hdX
> > > >
> > > > There are also some options in kernel configurations which addresses
> > > > when you have more than one promise comtrollers, have you tried
them?
> > > > Last, also in the ide section of kernel config you can find an
option
> > > > which should enable by default UDMA, have you enabled it?
> > > >
> > > > bye!
> > > >
> > > > Alle Sunday 19 October 2003 03:19, Jeremy Huddleston ha scritto:
> > > > > Hi,
> > > > >
> > > > > I've been using two Promise PDC20269 cards for almost a year now
in
> > > > > my system. The cards are U133, but when the kernel boots up, I see
> > > > > the message that all the drives are operating in pio mode.  All
the
> > > > > drives are U133 drives, and they are shown as operating in DMA
mode
> > > > > when I put them on another controller.
> > > > >
> > > > > I've noticed this deficiency with vanilla linux-2.4.19 through
> > > > > linux-2.4.21, linux-2.4.22-ac4 as well as 2.6.0-test6-mm4...
> > > > >
> > > > > Is there a patch to the 2.4 kernels availible to enable this
support?
> > > > > Is this problem being addressed?  Is there any way I can help out?
> > > > >
> > > > > Thanks,
> > > > > Jeremy
> > > > > -
> > > > > To unsubscribe from this list: send the line "unsubscribe
linux-ide"
> > > > > in the body of a message to majordomo@vger.kernel.org
> > > > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-ide"
in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQE/kt9KgKpk8srJOlIRAgBpAJ0QDfObvr3iKSjMKoHi/c2Ppfo6BgCghaK3
> QqUuqdwTyitORk3PVnNXksA=
> =kQQn
> -----END PGP SIGNATURE-----
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



      parent reply	other threads:[~2003-10-19 21:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-19  1:19 Promise PDC20269 - PIO Only? Jeremy Huddleston
2003-10-19  7:08 ` Willy Gardiol
2003-10-19 10:11   ` Jeremy Huddleston
2003-10-19  9:39     ` Willy Gardiol
2003-10-19 19:00       ` Jeremy Huddleston
2003-10-19 19:01         ` Willy Gardiol
2003-10-19 20:45           ` Bartlomiej Zolnierkiewicz
2003-10-19 23:03             ` Jeremy Huddleston
2003-10-20 17:49               ` Bartlomiej Zolnierkiewicz
2003-10-20 20:15                 ` Jeremy Huddleston
2003-10-21  1:39                   ` Jeremy Huddleston
2003-10-21 14:27                     ` Bartlomiej Zolnierkiewicz
2003-10-21 20:55                       ` Jeremy Huddleston
2003-10-21 21:28                         ` Bartlomiej Zolnierkiewicz
2003-10-19 21:18         ` Theepan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002001c39686$8c949e40$0200a8c0@tornado' \
    --to=tornado@linuxfromscratch.org \
    --cc=jeremyhu@uclink4.berkeley.edu \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox