* Promise PDC20269 - PIO Only? @ 2003-10-18 23:16 Jeremy Huddleston 2003-10-18 23:40 ` Måns Rullgård 0 siblings, 1 reply; 17+ messages in thread From: Jeremy Huddleston @ 2003-10-18 23:16 UTC (permalink / raw) To: andre; +Cc: linux-kernel -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/kcnOgKpk8srJOlIRAmvfAJ9lI/Dw5f6vNqHoAWdeSKXpsO8DdwCgmZ5y jlD7cw5xmmUOUA72y0PdCI4= =tMij -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-18 23:16 Promise PDC20269 - PIO Only? Jeremy Huddleston @ 2003-10-18 23:40 ` Måns Rullgård 0 siblings, 0 replies; 17+ messages in thread From: Måns Rullgård @ 2003-10-18 23:40 UTC (permalink / raw) To: linux-kernel Jeremy Huddleston <jeremyhu@uclink4.berkeley.edu> writes: > 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 got a PDC20268. My boot messages also say PIO. However, it still uses DMA by default. Check with "hdparm /dev/hdX" whether your disks use DMA. -- Måns Rullgård mru@users.sf.net ^ permalink raw reply [flat|nested] 17+ messages in thread
* Promise PDC20269 - PIO Only? @ 2003-10-19 1:19 Jeremy Huddleston 2003-10-19 7:08 ` Willy Gardiol 0 siblings, 1 reply; 17+ messages in thread From: Jeremy Huddleston @ 2003-10-19 1:19 UTC (permalink / raw) To: linux-ide -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/keaMgKpk8srJOlIRAhKDAKCNZt1RWrGP7eTzjwD4XLAs9djT8wCdEzpd GV8DEdYda15TmJxcZ/RJgU4= =R+w4 -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-19 1:19 Jeremy Huddleston @ 2003-10-19 7:08 ` Willy Gardiol 2003-10-19 10:11 ` Jeremy Huddleston 0 siblings, 1 reply; 17+ messages in thread From: Willy Gardiol @ 2003-10-19 7:08 UTC (permalink / raw) To: Jeremy Huddleston, linux-ide -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 - -- ! Willy Gardiol - gardiol@libero.it gardiol.eu.org Use linux for your freedom. "Tutti hanno dei pregiudizi, solo che i nostri sono giusti." Stefano Bagnasco (2002) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/kjiGQ9qolN/zUk4RAjHQAJ4pVt4LbM05DrgZA5xTmh9oeiRdRwCcCQ0D 0u8gzcHyx0wjLbA1jW/Zov0= =sGn9 -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-19 7:08 ` Willy Gardiol @ 2003-10-19 10:11 ` Jeremy Huddleston 2003-10-19 9:39 ` Willy Gardiol 0 siblings, 1 reply; 17+ messages in thread From: Jeremy Huddleston @ 2003-10-19 10:11 UTC (permalink / raw) To: gardiol, linux-ide; +Cc: Mark Hahn -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/kmNZgKpk8srJOlIRAlLgAKCDWijmkKXss4WSXcGDCfYGU41G0gCfW4x6 7ZEifZTYjX5OUqvoBB/+jxs= =0J1q -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-19 10:11 ` Jeremy Huddleston @ 2003-10-19 9:39 ` Willy Gardiol 2003-10-19 19:00 ` Jeremy Huddleston 0 siblings, 1 reply; 17+ messages in thread From: Willy Gardiol @ 2003-10-19 9:39 UTC (permalink / raw) To: Jeremy Huddleston, linux-ide; +Cc: Mark Hahn -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 - -- ! Willy Gardiol - gardiol@libero.it gardiol.eu.org Use linux for your freedom. "L'altrove è uno specchio in negativo. Il viaggiatore riconosce il poco che è suo, scoprendo il molto che non ha avuto e non avrà" Italo Calvino - Le città invisibili -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/klvJQ9qolN/zUk4RAgE8AKCMBgQg02ZONcteAKD97yr5l2h5XQCdELaz bhUUEPuD6F3JW2LCBZ8oaJg= =jJyT -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-19 9:39 ` Willy Gardiol @ 2003-10-19 19:00 ` Jeremy Huddleston 2003-10-19 19:01 ` Willy Gardiol 2003-10-19 21:18 ` Theepan 0 siblings, 2 replies; 17+ messages in thread From: Jeremy Huddleston @ 2003-10-19 19:00 UTC (permalink / raw) To: gardiol, linux-ide; +Cc: Mark Hahn -----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----- ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-19 19:00 ` Jeremy Huddleston @ 2003-10-19 19:01 ` Willy Gardiol 2003-10-19 20:45 ` Bartlomiej Zolnierkiewicz 2003-10-19 21:18 ` Theepan 1 sibling, 1 reply; 17+ messages in thread From: Willy Gardiol @ 2003-10-19 19:01 UTC (permalink / raw) To: Jeremy Huddleston, linux-ide; +Cc: Mark Hahn -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, in this case, i cant help more. Lets hope some "guru" from this list will give an hint ! Alle Sunday 19 October 2003 21:00, Jeremy Huddleston ha scritto: > 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 > > - > 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 - -- ! Willy Gardiol - gardiol@libero.it gardiol.eu.org Use linux for your freedom. "La guerra non farà mai finire alcuna guerra, nel migliore dei casi sarà stata una guerra in più." Gino Strada, Buskashì -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/kt+HQ9qolN/zUk4RArmiAJ9bidHaJnrj69o8+GPnxlG6kiIODgCeM7gq Z3ZzkFeyFFRfbdNcTnyJjKQ= =f62N -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-19 19:01 ` Willy Gardiol @ 2003-10-19 20:45 ` Bartlomiej Zolnierkiewicz 2003-10-19 23:03 ` Jeremy Huddleston 0 siblings, 1 reply; 17+ messages in thread From: Bartlomiej Zolnierkiewicz @ 2003-10-19 20:45 UTC (permalink / raw) To: gardiol; +Cc: Jeremy Huddleston, Mark Hahn, linux-ide Here is a hint. UDMA2 is a max if you don't use 80-wire cable. If you can't force mode by "hdparm -X" driver might be misdetecting cable type. Please change "#define PDC202_DEBUG_CABLE 0" to "#define PDC202_DEBUG_CABLE 1" in pdc202_new.c, recompile and retest. It should give some useful information. thanks, --bartlomiej On Sunday 19 of October 2003 21:01, Willy Gardiol wrote: > Well, in this case, i cant help more. > Lets hope some "guru" from this list will give an hint ! > > Alle Sunday 19 October 2003 21:00, Jeremy Huddleston ha scritto: > > 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 > > > > - > > 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 ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-19 20:45 ` Bartlomiej Zolnierkiewicz @ 2003-10-19 23:03 ` Jeremy Huddleston 2003-10-20 17:49 ` Bartlomiej Zolnierkiewicz 0 siblings, 1 reply; 17+ messages in thread From: Jeremy Huddleston @ 2003-10-19 23:03 UTC (permalink / raw) To: Bartlomiej Zolnierkiewicz; +Cc: linux-ide -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a lot of md output to the kernel logger when my system starts, so the IDE initialization output doesn't appear when I do my initial 'dmesg'... How do I increase the buffer size? I tried doing 'dmesg -s <really high numbers>', but I still can't get the output... Anyhow, I was trying the -X70 option to force udma6 on my 2.4.20 kernel (which was with the old driver), but when I do the force on 2.4.22-ac4, it works now, so thanks. What is the reason that the drive starts in pio mode when it is attatched to the promise controller, but it starts in DMA mode when it is on the other controller? Thanks again, Jeremy On Sunday October 19 2003 13:45, you wrote: > Here is a hint. UDMA2 is a max if you don't use 80-wire cable. > If you can't force mode by "hdparm -X" driver might be misdetecting > cable type. Please change "#define PDC202_DEBUG_CABLE 0" > to "#define PDC202_DEBUG_CABLE 1" in pdc202_new.c, recompile > and retest. It should give some useful information. > > thanks, > --bartlomiej > > On Sunday 19 of October 2003 21:01, Willy Gardiol wrote: > > Well, in this case, i cant help more. > > Lets hope some "guru" from this list will give an hint ! > > > > Alle Sunday 19 October 2003 21:00, Jeremy Huddleston ha scritto: > > > 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 > > > > > > - > > > 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/kxhMgKpk8srJOlIRAiS5AJ0RnzLkJhedxYTFilI8AECrDW+CmACdGkyk Eym+gcXPgKJGrESxaAC4iLc= =xCBs -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-19 23:03 ` Jeremy Huddleston @ 2003-10-20 17:49 ` Bartlomiej Zolnierkiewicz 2003-10-20 20:15 ` Jeremy Huddleston 0 siblings, 1 reply; 17+ messages in thread From: Bartlomiej Zolnierkiewicz @ 2003-10-20 17:49 UTC (permalink / raw) To: Jeremy Huddleston; +Cc: linux-ide On Monday 20 of October 2003 01:03, Jeremy Huddleston wrote: > I have a lot of md output to the kernel logger when my system starts, so > the IDE initialization output doesn't appear when I do my initial > 'dmesg'... How do I increase the buffer size? I tried doing 'dmesg -s > <really high numbers>', but I still can't get the output... /var/log/messages ? > Anyhow, I was trying the -X70 option to force udma6 on my 2.4.20 kernel > (which was with the old driver), but when I do the force on 2.4.22-ac4, it > works now, so thanks. > > What is the reason that the drive starts in pio mode when it is attatched > to the promise controller, but it starts in DMA mode when it is on the > other controller? Was the other controller on the same machine and with the same kernel? If not check if you have CONFIG_IDEDMA_PCI_AUTO set to Y in your .config file. Also please try to extract boot log... thanks, --bartlomiej > Thanks again, > Jeremy > > On Sunday October 19 2003 13:45, you wrote: > > Here is a hint. UDMA2 is a max if you don't use 80-wire cable. > > If you can't force mode by "hdparm -X" driver might be misdetecting > > cable type. Please change "#define PDC202_DEBUG_CABLE 0" > > to "#define PDC202_DEBUG_CABLE 1" in pdc202_new.c, recompile > > and retest. It should give some useful information. > > > > thanks, > > --bartlomiej > > > > On Sunday 19 of October 2003 21:01, Willy Gardiol wrote: > > > Well, in this case, i cant help more. > > > Lets hope some "guru" from this list will give an hint ! > > > > > > Alle Sunday 19 October 2003 21:00, Jeremy Huddleston ha scritto: > > > > 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 ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-20 17:49 ` Bartlomiej Zolnierkiewicz @ 2003-10-20 20:15 ` Jeremy Huddleston 2003-10-21 1:39 ` Jeremy Huddleston 0 siblings, 1 reply; 17+ messages in thread From: Jeremy Huddleston @ 2003-10-20 20:15 UTC (permalink / raw) To: Bartlomiej Zolnierkiewicz; +Cc: linux-ide -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 /var/log/messages doesn't contain all of the boot log because the kernel's buffer is too small. When syslog-ng starts up, the earliest thing in the log buffer is some raid stuff... I need to know how to increase the buffer size... anyone have any ideas? Oct 20 12:58:21 eradicator syslog-ng[1736]: Changing permissions on special file /dev/tty12 Oct 20 12:58:21 eradicator syslog-ng[1736]: syslog-ng version 1.6.0rc3 starting Oct 20 12:58:21 eradicator /part6's event counter: 0000015d Oct 20 12:58:21 eradicator md3: max total readahead window set to 744k Oct 20 12:58:21 eradicator md3: 3 data-disks, max readahead per data-disk: 248k Oct 20 12:58:21 eradicator raid5: device ide/host4/bus1/target0/lun0/part6 operational as raid disk 3 Oct 20 12:58:21 eradicator raid5: device ide/host4/bus0/target0/lun0/part6 operational as raid disk 2 I do have the ide-ribbon debug output though since it was after the controller initialization output: Oct 20 12:58:21 eradicator hdc: attached ide-cdrom driver. Oct 20 12:58:21 eradicator hdc: ATAPI 32X CD-ROM drive, 128kB Cache, UDMA(33) Oct 20 12:58:21 eradicator Uniform CD-ROM driver Revision: 3.12 Oct 20 12:58:21 eradicator ide2: 80-pin cable, 80-pin cable, 0 Oct 20 12:58:21 eradicator blk: queue c0349538, I/O limit 4095Mb (mask 0xffffffff) Oct 20 12:58:21 eradicator ide2: 80-pin cable, 80-pin cable, 0 Oct 20 12:58:21 eradicator ide3: 80-pin cable, 80-pin cable, 0 Oct 20 12:58:21 eradicator blk: queue c0349994, I/O limit 4095Mb (mask 0xffffffff) Oct 20 12:58:21 eradicator ide3: 80-pin cable, 80-pin cable, 0 Oct 20 12:58:21 eradicator ide3: 80-pin cable, 80-pin cable, 0 Oct 20 12:58:21 eradicator blk: queue c0349ad4, I/O limit 4095Mb (mask 0xffffffff) Oct 20 12:58:21 eradicator ide3: 80-pin cable, 80-pin cable, 0 Oct 20 12:58:21 eradicator ide4: 80-pin cable, 80-pin cable, 0 Oct 20 12:58:21 eradicator blk: queue c0349df0, I/O limit 4095Mb (mask 0xffffffff) Oct 20 12:58:21 eradicator ide4: 80-pin cable, 80-pin cable, 0 Oct 20 12:58:21 eradicator ide5: 80-pin cable, 80-pin cable, 0 Oct 20 12:58:21 eradicator blk: queue c034a24c, I/O limit 4095Mb (mask 0xffffffff) Oct 20 12:58:21 eradicator ide5: 80-pin cable, 80-pin cable, 0 Oct 20 12:58:21 eradicator PCI: Found IRQ 3 for device 00:0d.0 (12:49:44 Mon Oct 20 2003 root@eradicator) /usr/src/linux $ grep CONFIG_IDEDMA_PCI_AUTO .config CONFIG_IDEDMA_PCI_AUTO=y (13:08:17 Mon Oct 20 2003 root@terminator) /usr/src/linux $ grep CONFIG_IDEDMA_PCI_AUTO .config CONFIG_IDEDMA_PCI_AUTO=y The drives start in DMA mode by default on the other controllers, but not the PDC20267 or PDC20269. The PDC20267 is in a different system than the PDC20269. On Monday October 20 2003 10:49, Bartlomiej Zolnierkiewicz wrote: > On Monday 20 of October 2003 01:03, Jeremy Huddleston wrote: > > I have a lot of md output to the kernel logger when my system starts, so > > the IDE initialization output doesn't appear when I do my initial > > 'dmesg'... How do I increase the buffer size? I tried doing 'dmesg -s > > <really high numbers>', but I still can't get the output... > > /var/log/messages ? > > > Anyhow, I was trying the -X70 option to force udma6 on my 2.4.20 kernel > > (which was with the old driver), but when I do the force on 2.4.22-ac4, > > it works now, so thanks. > > > > What is the reason that the drive starts in pio mode when it is attatched > > to the promise controller, but it starts in DMA mode when it is on the > > other controller? > > Was the other controller on the same machine and with the same kernel? > If not check if you have CONFIG_IDEDMA_PCI_AUTO set to Y in your .config > file. Also please try to extract boot log... > > thanks, > --bartlomiej > > > Thanks again, > > Jeremy > > > > On Sunday October 19 2003 13:45, you wrote: > > > Here is a hint. UDMA2 is a max if you don't use 80-wire cable. > > > If you can't force mode by "hdparm -X" driver might be misdetecting > > > cable type. Please change "#define PDC202_DEBUG_CABLE 0" > > > to "#define PDC202_DEBUG_CABLE 1" in pdc202_new.c, recompile > > > and retest. It should give some useful information. > > > > > > thanks, > > > --bartlomiej > > > > > > On Sunday 19 of October 2003 21:01, Willy Gardiol wrote: > > > > Well, in this case, i cant help more. > > > > Lets hope some "guru" from this list will give an hint ! > > > > > > > > Alle Sunday 19 October 2003 21:00, Jeremy Huddleston ha scritto: > > > > > 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/lEJmgKpk8srJOlIRAtlgAJwJRCxe/ZcJLRo6g3vVXd467a9TswCcDPaj ZFZ/k7aA+2P2XDbp0hUOxe0= =Gdox -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-20 20:15 ` Jeremy Huddleston @ 2003-10-21 1:39 ` Jeremy Huddleston 2003-10-21 14:27 ` Bartlomiej Zolnierkiewicz 0 siblings, 1 reply; 17+ messages in thread From: Jeremy Huddleston @ 2003-10-21 1:39 UTC (permalink / raw) To: Bartlomiej Zolnierkiewicz; +Cc: linux-ide OK, I found where to increase the size of the kernel log buffer (linux/kernel/printk.c)... and here's the relevant output you requested: Thanks, Jeremy Oct 20 18:32:04 eradicator Uniform Multi-Platform E-IDE driver Revision: 7.00beta5-2.4 Oct 20 18:32:04 eradicator ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Oct 20 18:32:04 eradicator PIIX4: IDE controller at PCI slot 00:04.1 Oct 20 18:32:04 eradicator PIIX4: chipset revision 1 Oct 20 18:32:04 eradicator PIIX4: not 100% native mode: will probe irqs later Oct 20 18:32:04 eradicator ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:pio, hdb:pio Oct 20 18:32:04 eradicator ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio Oct 20 18:32:04 eradicator PDC20269: IDE controller at PCI slot 00:09.0 Oct 20 18:32:04 eradicator PCI: Found IRQ 3 for device 00:09.0 Oct 20 18:32:04 eradicator PCI: Sharing IRQ 3 with 00:04.2 Oct 20 18:32:04 eradicator PCI: Sharing IRQ 3 with 00:0d.0 Oct 20 18:32:04 eradicator PDC20269: chipset revision 2 Oct 20 18:32:04 eradicator PDC20269: not 100% native mode: will probe irqs later Oct 20 18:32:04 eradicator ide2: BM-DMA at 0xa800-0xa807, BIOS settings: hde:pio, hdf:pio Oct 20 18:32:04 eradicator ide2: 80-pin cable Oct 20 18:32:04 eradicator ide3: BM-DMA at 0xa808-0xa80f, BIOS settings: hdg:pio, hdh:pio Oct 20 18:32:04 eradicator ide3: 80-pin cable Oct 20 18:32:04 eradicator PDC20269: IDE controller at PCI slot 00:0a.0 Oct 20 18:32:04 eradicator PCI: Found IRQ 12 for device 00:0a.0 Oct 20 18:32:04 eradicator PDC20269: chipset revision 2 Oct 20 18:32:04 eradicator PDC20269: not 100% native mode: will probe irqs later Oct 20 18:32:04 eradicator ide4: BM-DMA at 0x9000-0x9007, BIOS settings: hdi:pio, hdj:pio Oct 20 18:32:04 eradicator ide4: 80-pin cable Oct 20 18:32:04 eradicator ide5: BM-DMA at 0x9008-0x900f, BIOS settings: hdk:pio, hdl:pio Oct 20 18:32:04 eradicator ide5: 80-pin cable Oct 20 18:32:04 eradicator hdc: CD-ROM 50X, ATAPI CD/DVD-ROM drive Oct 20 18:32:04 eradicator hde: Maxtor 6Y120P0, ATA DISK drive Oct 20 18:32:04 eradicator ide2: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator blk: queue c0365538, I/O limit 4095Mb (mask 0xffffffff) Oct 20 18:32:04 eradicator hdg: Maxtor 6Y120P0, ATA DISK drive Oct 20 18:32:04 eradicator hdh: Maxtor 4G120J6, ATA DISK drive Oct 20 18:32:04 eradicator ide3: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator blk: queue c0365994, I/O limit 4095Mb (mask 0xffffffff) Oct 20 18:32:04 eradicator ide3: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator blk: queue c0365ad4, I/O limit 4095Mb (mask 0xffffffff) Oct 20 18:32:04 eradicator hdi: Maxtor 6Y160P0, ATA DISK drive Oct 20 18:32:04 eradicator ide4: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator blk: queue c0365df0, I/O limit 4095Mb (mask 0xffffffff) Oct 20 18:32:04 eradicator hdk: Maxtor 6Y160P0, ATA DISK drive Oct 20 18:32:04 eradicator ide5: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator blk: queue c036624c, I/O limit 4095Mb (mask 0xffffffff) Oct 20 18:32:04 eradicator ide1 at 0x170-0x177,0x376 on irq 15 Oct 20 18:32:04 eradicator ide2 at 0xd000-0xd007,0xb802 on irq 3 Oct 20 18:32:04 eradicator ide3 at 0xb400-0xb407,0xb002 on irq 3 Oct 20 18:32:04 eradicator ide4 at 0xa400-0xa407,0xa002 on irq 12 Oct 20 18:32:04 eradicator ide5 at 0x9800-0x9807,0x9402 on irq 12 Oct 20 18:32:04 eradicator hde: attached ide-disk driver. Oct 20 18:32:04 eradicator hde: host protected area => 1 Oct 20 18:32:04 eradicator hde: 240121728 sectors (122942 MB) w/7936KiB Cache, CHS=238216/16/63, UDMA(133) Oct 20 18:32:04 eradicator hdg: attached ide-disk driver. Oct 20 18:32:04 eradicator hdg: host protected area => 1 Oct 20 18:32:04 eradicator hdg: 240121728 sectors (122942 MB) w/7936KiB Cache, CHS=238216/16/63, UDMA(133) Oct 20 18:32:04 eradicator hdh: attached ide-disk driver. Oct 20 18:32:04 eradicator hdh: host protected area => 1 Oct 20 18:32:04 eradicator hdh: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=14946/255/63, UDMA(133) Oct 20 18:32:04 eradicator hdi: attached ide-disk driver. Oct 20 18:32:04 eradicator hdi: host protected area => 1 Oct 20 18:32:04 eradicator hdi: 320173056 sectors (163929 MB) w/7936KiB Cache, CHS=19929/255/63, UDMA(133) Oct 20 18:32:04 eradicator hdk: attached ide-disk driver. Oct 20 18:32:04 eradicator hdk: host protected area => 1 Oct 20 18:32:04 eradicator hdk: 320173056 sectors (163929 MB) w/7936KiB Cache, CHS=19929/255/63, UDMA(133) Oct 20 18:32:04 eradicator Partition check: Oct 20 18:32:04 eradicator /dev/ide/host2/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 > Oct 20 18:32:04 eradicator /dev/ide/host2/bus1/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 > Oct 20 18:32:04 eradicator /dev/ide/host2/bus1/target1/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 > Oct 20 18:32:04 eradicator /dev/ide/host4/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 > Oct 20 18:32:04 eradicator /dev/ide/host4/bus1/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 > ... Oct 20 18:32:04 eradicator hdc: attached ide-cdrom driver. Oct 20 18:32:04 eradicator hdc: ATAPI 32X CD-ROM drive, 128kB Cache, UDMA(33) Oct 20 18:32:04 eradicator Uniform CD-ROM driver Revision: 3.12 Oct 20 18:32:04 eradicator ide2: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator blk: queue c0365538, I/O limit 4095Mb (mask 0xffffffff) Oct 20 18:32:04 eradicator ide2: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator ide3: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator blk: queue c0365994, I/O limit 4095Mb (mask 0xffffffff) Oct 20 18:32:04 eradicator ide3: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator ide3: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator blk: queue c0365ad4, I/O limit 4095Mb (mask 0xffffffff) Oct 20 18:32:04 eradicator ide3: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator ide4: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator blk: queue c0365df0, I/O limit 4095Mb (mask 0xffffffff) Oct 20 18:32:04 eradicator ide4: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator ide5: 80-pin cable, 80-pin cable, 0 Oct 20 18:32:04 eradicator blk: queue c036624c, I/O limit 4095Mb (mask 0xffffffff) Oct 20 18:32:04 eradicator ide5: 80-pin cable, 80-pin cable, 0 On Mon, 2003-10-20 at 13:15, Jeremy Huddleston wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > /var/log/messages doesn't contain all of the boot log because the kernel's > buffer is too small. When syslog-ng starts up, the earliest thing in the log > buffer is some raid stuff... I need to know how to increase the buffer > size... anyone have any ideas? > > Oct 20 12:58:21 eradicator syslog-ng[1736]: Changing permissions on special > file /dev/tty12 > Oct 20 12:58:21 eradicator syslog-ng[1736]: syslog-ng version 1.6.0rc3 > starting > Oct 20 12:58:21 eradicator /part6's event counter: 0000015d > Oct 20 12:58:21 eradicator md3: max total readahead window set to 744k > Oct 20 12:58:21 eradicator md3: 3 data-disks, max readahead per data-disk: > 248k > Oct 20 12:58:21 eradicator raid5: device ide/host4/bus1/target0/lun0/part6 > operational as raid disk 3 > Oct 20 12:58:21 eradicator raid5: device ide/host4/bus0/target0/lun0/part6 > operational as raid disk 2 > > I do have the ide-ribbon debug output though since it was after the controller > initialization output: > > Oct 20 12:58:21 eradicator hdc: attached ide-cdrom driver. > Oct 20 12:58:21 eradicator hdc: ATAPI 32X CD-ROM drive, 128kB Cache, UDMA(33) > Oct 20 12:58:21 eradicator Uniform CD-ROM driver Revision: 3.12 > Oct 20 12:58:21 eradicator ide2: 80-pin cable, 80-pin cable, 0 > Oct 20 12:58:21 eradicator blk: queue c0349538, I/O limit 4095Mb (mask > 0xffffffff) > Oct 20 12:58:21 eradicator ide2: 80-pin cable, 80-pin cable, 0 > Oct 20 12:58:21 eradicator ide3: 80-pin cable, 80-pin cable, 0 > Oct 20 12:58:21 eradicator blk: queue c0349994, I/O limit 4095Mb (mask > 0xffffffff) > Oct 20 12:58:21 eradicator ide3: 80-pin cable, 80-pin cable, 0 > Oct 20 12:58:21 eradicator ide3: 80-pin cable, 80-pin cable, 0 > Oct 20 12:58:21 eradicator blk: queue c0349ad4, I/O limit 4095Mb (mask > 0xffffffff) > Oct 20 12:58:21 eradicator ide3: 80-pin cable, 80-pin cable, 0 > Oct 20 12:58:21 eradicator ide4: 80-pin cable, 80-pin cable, 0 > Oct 20 12:58:21 eradicator blk: queue c0349df0, I/O limit 4095Mb (mask > 0xffffffff) > Oct 20 12:58:21 eradicator ide4: 80-pin cable, 80-pin cable, 0 > Oct 20 12:58:21 eradicator ide5: 80-pin cable, 80-pin cable, 0 > Oct 20 12:58:21 eradicator blk: queue c034a24c, I/O limit 4095Mb (mask > 0xffffffff) > Oct 20 12:58:21 eradicator ide5: 80-pin cable, 80-pin cable, 0 > Oct 20 12:58:21 eradicator PCI: Found IRQ 3 for device 00:0d.0 > > > (12:49:44 Mon Oct 20 2003 root@eradicator) > /usr/src/linux $ grep CONFIG_IDEDMA_PCI_AUTO .config > CONFIG_IDEDMA_PCI_AUTO=y > > (13:08:17 Mon Oct 20 2003 root@terminator) > /usr/src/linux $ grep CONFIG_IDEDMA_PCI_AUTO .config > CONFIG_IDEDMA_PCI_AUTO=y > > The drives start in DMA mode by default on the other controllers, but not the > PDC20267 or PDC20269. The PDC20267 is in a different system than the > PDC20269. > > On Monday October 20 2003 10:49, Bartlomiej Zolnierkiewicz wrote: > > On Monday 20 of October 2003 01:03, Jeremy Huddleston wrote: > > > I have a lot of md output to the kernel logger when my system starts, so > > > the IDE initialization output doesn't appear when I do my initial > > > 'dmesg'... How do I increase the buffer size? I tried doing 'dmesg -s > > > <really high numbers>', but I still can't get the output... > > > > /var/log/messages ? > > > > > Anyhow, I was trying the -X70 option to force udma6 on my 2.4.20 kernel > > > (which was with the old driver), but when I do the force on 2.4.22-ac4, > > > it works now, so thanks. > > > > > > What is the reason that the drive starts in pio mode when it is attatched > > > to the promise controller, but it starts in DMA mode when it is on the > > > other controller? > > > > Was the other controller on the same machine and with the same kernel? > > If not check if you have CONFIG_IDEDMA_PCI_AUTO set to Y in your .config > > file. Also please try to extract boot log... > > > > thanks, > > --bartlomiej > > > > > Thanks again, > > > Jeremy > > > > > > On Sunday October 19 2003 13:45, you wrote: > > > > Here is a hint. UDMA2 is a max if you don't use 80-wire cable. > > > > If you can't force mode by "hdparm -X" driver might be misdetecting > > > > cable type. Please change "#define PDC202_DEBUG_CABLE 0" > > > > to "#define PDC202_DEBUG_CABLE 1" in pdc202_new.c, recompile > > > > and retest. It should give some useful information. > > > > > > > > thanks, > > > > --bartlomiej > > > > > > > > On Sunday 19 of October 2003 21:01, Willy Gardiol wrote: > > > > > Well, in this case, i cant help more. > > > > > Lets hope some "guru" from this list will give an hint ! > > > > > > > > > > Alle Sunday 19 October 2003 21:00, Jeremy Huddleston ha scritto: > > > > > > 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 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.3 (GNU/Linux) > > iD8DBQE/lEJmgKpk8srJOlIRAtlgAJwJRCxe/ZcJLRo6g3vVXd467a9TswCcDPaj > ZFZ/k7aA+2P2XDbp0hUOxe0= > =Gdox > -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-21 1:39 ` Jeremy Huddleston @ 2003-10-21 14:27 ` Bartlomiej Zolnierkiewicz 2003-10-21 20:55 ` Jeremy Huddleston 0 siblings, 1 reply; 17+ messages in thread From: Bartlomiej Zolnierkiewicz @ 2003-10-21 14:27 UTC (permalink / raw) To: Jeremy Huddleston; +Cc: linux-ide DMA is enabled correctly on all drives by Linux IDE driver, (please note that BIOS leaved them in PIO). --bartlomiej > Oct 20 18:32:04 eradicator hde: attached ide-disk driver. > Oct 20 18:32:04 eradicator hde: host protected area => 1 > Oct 20 18:32:04 eradicator hde: 240121728 sectors (122942 MB) w/7936KiB > Cache, CHS=238216/16/63, UDMA(133) > Oct 20 18:32:04 eradicator hdg: attached ide-disk driver. > Oct 20 18:32:04 eradicator hdg: host protected area => 1 > Oct 20 18:32:04 eradicator hdg: 240121728 sectors (122942 MB) w/7936KiB > Cache, CHS=238216/16/63, UDMA(133) > Oct 20 18:32:04 eradicator hdh: attached ide-disk driver. > Oct 20 18:32:04 eradicator hdh: host protected area => 1 > Oct 20 18:32:04 eradicator hdh: 240121728 sectors (122942 MB) w/2048KiB > Cache, CHS=14946/255/63, UDMA(133) > Oct 20 18:32:04 eradicator hdi: attached ide-disk driver. > Oct 20 18:32:04 eradicator hdi: host protected area => 1 > Oct 20 18:32:04 eradicator hdi: 320173056 sectors (163929 MB) w/7936KiB > Cache, CHS=19929/255/63, UDMA(133) > Oct 20 18:32:04 eradicator hdk: attached ide-disk driver. > Oct 20 18:32:04 eradicator hdk: host protected area => 1 > Oct 20 18:32:04 eradicator hdk: 320173056 sectors (163929 MB) w/7936KiB > Cache, CHS=19929/255/63, UDMA(133) ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-21 14:27 ` Bartlomiej Zolnierkiewicz @ 2003-10-21 20:55 ` Jeremy Huddleston 2003-10-21 21:28 ` Bartlomiej Zolnierkiewicz 0 siblings, 1 reply; 17+ messages in thread From: Jeremy Huddleston @ 2003-10-21 20:55 UTC (permalink / raw) To: Bartlomiej Zolnierkiewicz; +Cc: linux-ide Hmm... I still think there's a bug here because similarly, the bios for my PDC2067 (FastTrak 100) says my drives are operating in UDMA Mode 5. To see this, I press ctr-f to enter the fasttrak configuration utility and goto the drive info page... But when linux starts, it shows: Oct 21 13:41:07 terminator PDC20267: IDE controller at PCI slot 01:0a.0 Oct 21 13:41:07 terminator PDC20267: chipset revision 2 Oct 21 13:41:07 terminator PDC20267: not 100% native mode: will probe irqs later Oct 21 13:41:07 terminator PDC20267: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER Mode. Oct 21 13:41:07 terminator ide2: BM-DMA at 0xd800-0xd807, BIOS settings: hde:pio, hdf:pio Oct 21 13:41:07 terminator ide3: BM-DMA at 0xd808-0xd80f, BIOS settings: hdg:pio, hdh:pio ... Oct 21 13:41:07 terminator hde: attached ide-disk driver. Oct 21 13:41:07 terminator hde: host protected area => 1 Oct 21 13:41:07 terminator hde: 195371568 sectors (100030 MB) w/2048KiB Cache, CHS=193821/16/63, UDMA(100) Oct 21 13:41:07 terminator hdg: attached ide-disk driver. Oct 21 13:41:07 terminator hdg: host protected area => 1 Oct 21 13:41:07 terminator hdg: 195371568 sectors (100030 MB) w/2048KiB Cache, CHS=193821/16/63, UDMA(100) Which do I believe? Promise's BIOS setup utility is reporting UDMA5, but linux says BIOS is reporting PIO... How are the linux drivers determining that it is operating in pio mode? It is actually fairly important to me that my drives start in UDMA5 mode rather than waiting for hdparm to run in my init scripts because of raid (linux md) reconstruction and filesystem checking that happens after a crash or power failure... On Tue, 2003-10-21 at 07:27, Bartlomiej Zolnierkiewicz wrote: > DMA is enabled correctly on all drives by Linux IDE driver, > (please note that BIOS leaved them in PIO). > > --bartlomiej > > > Oct 20 18:32:04 eradicator hde: attached ide-disk driver. > > Oct 20 18:32:04 eradicator hde: host protected area => 1 > > Oct 20 18:32:04 eradicator hde: 240121728 sectors (122942 MB) w/7936KiB > > Cache, CHS=238216/16/63, UDMA(133) > > Oct 20 18:32:04 eradicator hdg: attached ide-disk driver. > > Oct 20 18:32:04 eradicator hdg: host protected area => 1 > > Oct 20 18:32:04 eradicator hdg: 240121728 sectors (122942 MB) w/7936KiB > > Cache, CHS=238216/16/63, UDMA(133) > > Oct 20 18:32:04 eradicator hdh: attached ide-disk driver. > > Oct 20 18:32:04 eradicator hdh: host protected area => 1 > > Oct 20 18:32:04 eradicator hdh: 240121728 sectors (122942 MB) w/2048KiB > > Cache, CHS=14946/255/63, UDMA(133) > > Oct 20 18:32:04 eradicator hdi: attached ide-disk driver. > > Oct 20 18:32:04 eradicator hdi: host protected area => 1 > > Oct 20 18:32:04 eradicator hdi: 320173056 sectors (163929 MB) w/7936KiB > > Cache, CHS=19929/255/63, UDMA(133) > > Oct 20 18:32:04 eradicator hdk: attached ide-disk driver. > > Oct 20 18:32:04 eradicator hdk: host protected area => 1 > > Oct 20 18:32:04 eradicator hdk: 320173056 sectors (163929 MB) w/7936KiB > > Cache, CHS=19929/255/63, UDMA(133) ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-21 20:55 ` Jeremy Huddleston @ 2003-10-21 21:28 ` Bartlomiej Zolnierkiewicz 0 siblings, 0 replies; 17+ messages in thread From: Bartlomiej Zolnierkiewicz @ 2003-10-21 21:28 UTC (permalink / raw) To: Jeremy Huddleston; +Cc: linux-ide On Tuesday 21 of October 2003 22:55, Jeremy Huddleston wrote: > Hmm... I still think there's a bug here because similarly, the bios for > my PDC2067 (FastTrak 100) says my drives are operating in UDMA Mode 5. > To see this, I press ctr-f to enter the fasttrak configuration utility > and goto the drive info page... I think that BIOS says that they are UDMA5 _capable_. > But when linux starts, it shows: > Oct 21 13:41:07 terminator PDC20267: IDE controller at PCI slot 01:0a.0 > Oct 21 13:41:07 terminator PDC20267: chipset revision 2 > Oct 21 13:41:07 terminator PDC20267: not 100% native mode: will probe > irqs later > Oct 21 13:41:07 terminator PDC20267: (U)DMA Burst Bit ENABLED Primary > MASTER Mode Secondary MASTER Mode. > Oct 21 13:41:07 terminator ide2: BM-DMA at 0xd800-0xd807, BIOS settings: > hde:pio, hdf:pio > Oct 21 13:41:07 terminator ide3: BM-DMA at 0xd808-0xd80f, BIOS settings: > hdg:pio, hdh:pio > ... > Oct 21 13:41:07 terminator hde: attached ide-disk driver. > Oct 21 13:41:07 terminator hde: host protected area => 1 > Oct 21 13:41:07 terminator hde: 195371568 sectors (100030 MB) w/2048KiB > Cache, CHS=193821/16/63, UDMA(100) > Oct 21 13:41:07 terminator hdg: attached ide-disk driver. > Oct 21 13:41:07 terminator hdg: host protected area => 1 > Oct 21 13:41:07 terminator hdg: 195371568 sectors (100030 MB) w/2048KiB > Cache, CHS=193821/16/63, UDMA(100) > > Which do I believe? Promise's BIOS setup utility is reporting UDMA5, > but linux says BIOS is reporting PIO... How are the linux drivers > determining that it is operating in pio mode? It is actually fairly Look at ide_setup_dma() in drivers/ide/ide-dma.c. > important to me that my drives start in UDMA5 mode rather than waiting > for hdparm to run in my init scripts because of raid (linux md) > reconstruction and filesystem checking that happens after a crash or > power failure... You don't wait for hdparm, IDE driver _enables_ DMA _before_ RAID is mounted and _before_ user-space applications (such as hdparm) can be executed. "hdg: 195371568 sectors (100030 MB) w/2048KiB Cache, CHS=193821/16/63, UDMA(100)" ^^^^^^^^^ --bartlomiej > On Tue, 2003-10-21 at 07:27, Bartlomiej Zolnierkiewicz wrote: > > DMA is enabled correctly on all drives by Linux IDE driver, > > (please note that BIOS leaved them in PIO). > > > > --bartlomiej > > > > > Oct 20 18:32:04 eradicator hde: attached ide-disk driver. > > > Oct 20 18:32:04 eradicator hde: host protected area => 1 > > > Oct 20 18:32:04 eradicator hde: 240121728 sectors (122942 MB) w/7936KiB > > > Cache, CHS=238216/16/63, UDMA(133) > > > Oct 20 18:32:04 eradicator hdg: attached ide-disk driver. > > > Oct 20 18:32:04 eradicator hdg: host protected area => 1 > > > Oct 20 18:32:04 eradicator hdg: 240121728 sectors (122942 MB) w/7936KiB > > > Cache, CHS=238216/16/63, UDMA(133) > > > Oct 20 18:32:04 eradicator hdh: attached ide-disk driver. > > > Oct 20 18:32:04 eradicator hdh: host protected area => 1 > > > Oct 20 18:32:04 eradicator hdh: 240121728 sectors (122942 MB) w/2048KiB > > > Cache, CHS=14946/255/63, UDMA(133) > > > Oct 20 18:32:04 eradicator hdi: attached ide-disk driver. > > > Oct 20 18:32:04 eradicator hdi: host protected area => 1 > > > Oct 20 18:32:04 eradicator hdi: 320173056 sectors (163929 MB) w/7936KiB > > > Cache, CHS=19929/255/63, UDMA(133) > > > Oct 20 18:32:04 eradicator hdk: attached ide-disk driver. > > > Oct 20 18:32:04 eradicator hdk: host protected area => 1 > > > Oct 20 18:32:04 eradicator hdk: 320173056 sectors (163929 MB) w/7936KiB > > > Cache, CHS=19929/255/63, UDMA(133) ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Promise PDC20269 - PIO Only? 2003-10-19 19:00 ` Jeremy Huddleston 2003-10-19 19:01 ` Willy Gardiol @ 2003-10-19 21:18 ` Theepan 1 sibling, 0 replies; 17+ messages in thread From: Theepan @ 2003-10-19 21:18 UTC (permalink / raw) To: Jeremy Huddleston; +Cc: linux-ide 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 ^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2003-10-21 21:24 UTC | newest] Thread overview: 17+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2003-10-18 23:16 Promise PDC20269 - PIO Only? Jeremy Huddleston 2003-10-18 23:40 ` Måns Rullgård -- strict thread matches above, loose matches on Subject: below -- 2003-10-19 1:19 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 is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.