Anyone use HPT366 + UDMA in Linux?
Hello,
I am interested in anyone that has this sucessfully working - if you have maybe you can drop me a mail telling me how you did it :)
Thanks!
Ian
Quoted 5 lines · Ian Chilton
Hello,
I am interested in anyone that has this sucessfully working - if you have maybe you can drop me a mail telling me how you did it :)
If it still doesnt work in 2.4.20-rc1-ac2 or later please send me a detailed bug report
Hello,
Quoted 2 lines
If it still doesnt work in 2.4.20-rc1-ac2 or later please send me a detailed bug report
Does that mean you know it's been broken and/or are there changes to HPT366 in 2.4.20-rc1-ac2?
I've been trying 2.4.19, 2.4.20-pre11 and 2.4.20-rc1 with and without Rik's fairsched patch.
Thanks!
Bye for Now,
Ian
\|||/
(o o)
/---------------------------ooO-(_)-Ooo---------------------------\
| Ian Chilton Web: http://www.ichilton.co.uk |
| E-Mail: [email protected] Backup: [email protected] |
|-----------------------------------------------------------------|
| There are 10 types of people in the world: |
| Those who understand binary, and those who don't. |\-----------------------------------------------------------------/
Quoted 4 lines · Ian Chilton
Hello,
Quoted 9 lines
Quoted 4 lines
If it still doesnt work in 2.4.20-rc1-ac2 or later please send me a detailed bug report
Does that mean you know it's been broken and/or are there changes to HPT366 in 2.4.20-rc1-ac2?
What is means is Alan is doing a thankless job fixing the current ide
mess. The ac 2.4/2.5 trees are being used to test a number of updates. If you can provide Alan good bug report on the issue in 2.4.20-rc1-ac2. He will take a look at fixing the code. I think the info he needs would be:
-The ide section of dmesg or all of dmesg
-output of hdparm -vi /dev/hd(whatever)
-result of hdparm -d 1 /dev/hd(whatever)
Quoted 6 lines
I've been trying 2.4.19, 2.4.20-pre11 and 2.4.20-rc1 with and without Rik's fairsched patch.
Hello,
Quoted 4 lines
What is means is Alan is doing a thankless job fixing the current ide
mess. The ac 2.4/2.5 trees are being used to test a number of updates. If you can provide Alan good bug report on the issue in 2.4.20-rc1-ac2. He will take a look at fixing the code.
OK, great - i'll try to get 2.4.10-rc1-ac2-fairsched on asap!
Thanks!
Bye for Now,
Ian
\|||/
(o o)
/---------------------------ooO-(_)-Ooo---------------------------\
| Ian Chilton Web: http://www.ichilton.co.uk |
| E-Mail: [email protected] Backup: [email protected] |
|-----------------------------------------------------------------|
| There are 10 types of people in the world: |
| Those who understand binary, and those who don't. |\-----------------------------------------------------------------/
Hello!
Quoted 2 lines · Alan Cox
If it still doesnt work in 2.4.20-rc1-ac2 or later please send me a detailed bug report
All versions of hpt366.c newer than 0.18 (namely 0.22, 0.33 and 0.34) do not work on my setup, but hang during "partition check" on boot. I've tried changing UDMA mode in HPT BIOS, but it does not seem to affect anything and the drives are still recognized as "UDMA(100)". The latest kernel I tried was 2.4.20-rc-ac4, but it behaved just the same.
My setup is (all info gathered on 2.4.17 which is the last kernel version I can successfully boot with and which btw has been working flawlessly for a long time):
From dmesg:
HPT370A: chipset revision 4
HPT370A: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xe400-0xe407, BIOS settings: hde:pio, hdf:DMA
ide3: BM-DMA at 0xe408-0xe40f, BIOS settings: hdg:pio, hdh:DMAhdf: IC35L040AVER07-0, ATA DISK drive
hdh: IC35L040AVER07-0, ATA DISK drive
hdf: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=79780/16/63, UDMA(44)
hdh: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=79780/16/63, UDMA(44)
fantomas:/home/thorgal# hdparm -i /dev/hdf
/dev/hdf:
Model=IC35L040AVER07-0, FwRev=ER4OA44A, SerialNo=SX0SXM07352 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40 BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=80418240 IORDY=on/off, tPIO={min:240,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 AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: 2 3 4 5
Drive /dev/hdh is identical sans SerialNo.
Please tell me what other info I can provide to help you.
Best regards,
Milek
Signature · 3 lines
mailto:[email protected] | "Man in the Moon and other weird things" - http://wfmh.org.pl/~thorgal/ | see it at http://wfmh.org.pl/~thorgal/Moon/ PLEASE UPDATE YOUR ADDRESSBOOK WITH MY NEW EMAIL ADDRESS.
Hello,
I booed 2.4.19 with HPT366 compiled in and i have not got it to fall over yet :)
HPT366: onboard version of chipset, pin1=1 pin2=2
HPT366: IDE controller on PCI bus 00 dev 98
HPT366: chipset revision 1
HPT366: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xb400-0xb407, BIOS settings: hda:DMA, hdb:pio
HPT366: IDE controller on PCI bus 00 dev 99
HPT366: chipset revision 1
HPT366: not 100% native mode: will probe irqs later
ide1: BM-DMA at 0xc000-0xc007, BIOS settings: hdc:pio, hdd:piohda: IBM-DTLA-307045, ATA DISK drive
ide0 at 0xac00-0xac07,0xb002 on irq 15
hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=89355/16/63, UDMA(44)
Partition check:
hda: [PTBL] [5606/255/63] hda1 hda3 hda4
[root@buzz:~]# hdparm-5.2/hdparm -i /dev/hda
/dev/hda:
Model=IBM-DTLA-307045, FwRev=TX6OA5AA, SerialNo=YZDYZNM1366 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40 BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16 CurCHS=65535/1/63, CurSects=4128705, LBA=yes, LBAsects=90069840 IORDY=on/off, tPIO={min:240,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 AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: 2 3 4 5
Does this look normal?
Thanks!
Bye for Now,
Ian
\|||/
(o o)
/---------------------------ooO-(_)-Ooo---------------------------\
| Ian Chilton Web: http://www.ichilton.co.uk |
| E-Mail: [email protected] Backup: [email protected] |
|-----------------------------------------------------------------|
| There are 10 types of people in the world: |
| Those who understand binary, and those who don't. |\-----------------------------------------------------------------/
Hi!
Quoted 12 lines · Ian Chilton
I booed 2.4.19 with HPT366 compiled in and i have not got it to fall over yet :)
HPT366: onboard version of chipset, pin1=1 pin2=2
HPT366: IDE controller on PCI bus 00 dev 98
HPT366: chipset revision 1
HPT366: not 100% native mode: will probe irqs lateride0: BM-DMA at 0xb400-0xb407, BIOS settings: hda:DMA, hdb:pio HPT366: IDE controller on PCI bus 00 dev 99 HPT366: chipset revision 1 HPT366: not 100% native mode: will probe irqs later ide1: BM-DMA at 0xc000-0xc007, BIOS settings: hdc:pio, hdd:pio
Quoted 4 lines
hda: IBM-DTLA-307045, ATA DISK drive
ide0 at 0xac00-0xac07,0xb002 on irq 15
hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=89355/16/63, UDMA(44)
Your IBM-DTLA-307045 is on ATA100 and ATA66 bad_drives lists and is properly downgraded to UDMA3. Mine however (IC35L040AVER07-0), despite also being present on those lists, is recognized as UDMA5 by hpt366.c newer than 0.18. That may be the culprit.
Cheers,
Milek
Signature · 3 lines
mailto:[email protected] | "Man in the Moon and other weird things" - http://wfmh.org.pl/~thorgal/ | see it at http://wfmh.org.pl/~thorgal/Moon/ PLEASE UPDATE YOUR ADDRESSBOOK WITH MY NEW EMAIL ADDRESS.
Hello,
Quoted 32 lines
My setup is (all info gathered on 2.4.17 which is the last kernel version I can successfully boot with and which btw has been working flawlessly for a long time):
From dmesg:
HPT370A: chipset revision 4
HPT370A: not 100% native mode: will probe irqs lateride2: BM-DMA at 0xe400-0xe407, BIOS settings: hde:pio, hdf:DMA ide3: BM-DMA at 0xe408-0xe40f, BIOS settings: hdg:pio, hdh:DMAhdf: IC35L040AVER07-0, ATA DISK drive
hdh: IC35L040AVER07-0, ATA DISK drive
hdf: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=79780/16/63, UDMA(44)
hdh: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=79780/16/63, UDMA(44)fantomas:/home/thorgal# hdparm -i /dev/hdf
/dev/hdf:Model=IC35L040AVER07-0, FwRev=ER4OA44A, SerialNo=SX0SXM07352 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40 BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=80418240 IORDY=on/off, tPIO={min:240,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 AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: 2 3 4 5
Quoted 1 line
Drive
/dev/hdhis identical sans SerialNo.
I have the same problem with my Seagate on Abit BE6-II. This is last
succesfull boot (dmesg from 2.4.18):
...
Kernel command line: ... idebus=66
...
ide: Assuming 66MHz system bus speed for PIO modes ..
HPT370: IDE controller on PCI bus 00 dev 98
PCI: Found IRQ 11 for device 00:13.0
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
HPT370: using 33MHz PCI clock
ide2: BM-DMA at 0xe800-0xe807, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0xe808-0xe80f, BIOS settings: hdg:pio, hdh:piohda: WDC AC24300L, ATA DISK drive
hde: ST34310A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xd800-0xd807,0xdc02 on irq 11
hda: 8421840 sectors (4312 MB) w/256KiB Cache, CHS=524/255/63, UDMA(33)
hde: 8420832 sectors (4311 MB) w/512KiB Cache, CHS=8354/16/63, UDMA(33) Partition check:
hda: hda1 hda2 hda3 hda4
hde: hde1
.....
/dev/hde:
Model=ST34310A, FwRev=3.07, SerialNo=6AX03Y1Y
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } RawCHS=8354/16/63, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=512kB, MaxMultSect=16, MultSect=16 CurCHS=8354/16/63, CurSects=2111832192, LBA=yes, LBAsects=8420832 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 AdvancedPM=no
Drive Supports : Reserved : ATA-1 ATA-2 ATA-3 ATA-4
With 2.4.19 I must change hde to hdc....
I know my dist is only ATA33, but befor 2.4.19 I have only one 40-pin and one 80-pin cable...
---------------------------------------------------------------------------
Bc. Zdenek Kaminski <xkaminsk at fi.muni.cz>
homepage: http://rubisko.ascs.muni.cz/~xkaminsk/
IPv6 router homepage: http://merlot.ics.muni.cz/
Quoted 4 lines · Ian Chilton
Hello,
I am interested in anyone that has this sucessfully working - if you have maybe you can drop me a mail telling me how you did it :)
I am using an IBM-DTLA-307030 with HPT366 for almost 2 years with many kernels in 2.4 and 2.5 series without problems after limiting transfer rate to udma3 (44MB/s) in the HPT bios. You can also do it with hdparm if your boot disk is not on that controler. Trying udma4 resulted in _massive_ corruption (never tried recently). Of course, I enabled HPT366 support in kernel configuration. Hdparm gives 35 MM/sec. This is on an Abit BP6. Hope it helps.
Hello,
Quoted 1 line
I am using an IBM-DTLA-307030 with HPT366
I am also using an IBM disk (can't rember the model number of hand but it's a 45GB) with an Abit BP6.
Quoted 3 lines
transfer rate to udma3 (44MB/s) in the HPT bios. You can also do it with hdparm if your boot disk is not on that controler. Trying udma4 resulted in _massive_ corruption (never tried recently).
It seemed to work for a while but then things went screwy and I kept getting I/O errors all the time which needed a hard reset - could't even shut down.
I also noticed things like this in the log:
Nov 14 23:26:40 buzz kernel: hda: status error:
status=0x58 { DriveReady SeekComplete DataRequest }
Nov 14 23:26:40 buzz kernel: hda: drive not ready for command
Nov 14 23:28:47 buzz kernel: hda: status error:
status=0x58 { DriveReady SeekComplete DataRequest }
Nov 14 23:28:47 buzz kernel: hda: drive not ready for command
Nov 14 23:29:00 buzz kernel: APIC error on CPU0: 02(02)Is this anything like you got?
I'll try to drop it in the bios tonight (it is my boot drive). Are you using hdparm commands at all or just setting the bios to udma3?
Quoted 1 line
HPT366 support in kernel configuration.
I am not sure I did this but I'll check. Maybe it's just working as a normal ide interface or something?
Thanks!
Bye for Now,
Ian
\|||/
(o o)
/---------------------------ooO-(_)-Ooo---------------------------\
| Ian Chilton Web: http://www.ichilton.co.uk |
| E-Mail: [email protected] Backup: [email protected] |
|-----------------------------------------------------------------|
| There are 10 types of people in the world: |
| Those who understand binary, and those who don't. |\-----------------------------------------------------------------/
A message that is not in the archive (sent off-list or not yet received): 20021115173120.GA1152@gouv
Hello,
Quoted 2 lines
I do it in the bios and I have also limited the drive to udma3 to be on the safe side (IBM has an utility for doing it )
I have just enabled HPT366 in the kernel but have not touched the bios or drive. This is what hdparm gives:
[root@buzz:~/hdparm-5.2]# ./hdparm -i /dev/hda
/dev/hda:
Model=IBM-DTLA-307045, FwRev=TX6OA5AA, SerialNo=YZDYZNM1366 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40 BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16 CurCHS=65535/1/63, CurSects=4128705, LBA=yes, LBAsects=90069840 IORDY=on/off, tPIO={min:240,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 AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: 2 3 4 5
Does this mean it's already using udma3?
Thanks!
Ian
Quoted 10 lines · Ian Chilton
[root@buzz:~/hdparm-5.2]# ./hdparm -i /dev/hda
/dev/hda:Model=IBM-DTLA-307045, FwRev=TX6OA5AA, SerialNo=YZDYZNM1366 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40 BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16 CurCHS=65535/1/63, CurSects=4128705, LBA=yes, LBAsects=90069840 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
Quoted 12 lines
PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 *udma3 udma4 udma5 AdvancedPM=yes: disabled (255) WriteCache=enabled Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: 2 3 4 5Does this mean it's already using udma3?
Yes. hdparm -X 69 /dev/hda attempt to enable udma5, but may crash
your system. hdparm -X 67 /dev/hda should revert things. Be carefull.
I never had good luck, especially under heavy load, until I took out my IBM drives. I haven't had any problems with Redhat kernels (and before that stock 2.4.17) with my Western Digital.
-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Ian Chilton
Sent: Friday, November 15, 2002 10:29 AM
To: Leopold Gouverneur
Cc: [email protected]
Subject: Re: Anyone use HPT366 + UDMA in Linux?
Hello,
Quoted 1 line
I am using an IBM-DTLA-307030 with HPT366
I am also using an IBM disk (can't rember the model number of hand but it's a 45GB) with an Abit BP6.
Quoted 3 lines
transfer rate to udma3 (44MB/s) in the HPT bios. You can also do it with hdparm if your boot disk is not on that controler. Trying udma4 resulted in _massive_ corruption (never tried recently).
It seemed to work for a while but then things went screwy and I kept getting I/O errors all the time which needed a hard reset - could't even shut down.
I also noticed things like this in the log:
Nov 14 23:26:40 buzz kernel: hda: status error:
status=0x58 { DriveReady SeekComplete DataRequest }
Nov 14 23:26:40 buzz kernel: hda: drive not ready for command
Nov 14 23:28:47 buzz kernel: hda: status error:
status=0x58 { DriveReady SeekComplete DataRequest }
Nov 14 23:28:47 buzz kernel: hda: drive not ready for command
Nov 14 23:29:00 buzz kernel: APIC error on CPU0: 02(02)Is this anything like you got?
I'll try to drop it in the bios tonight (it is my boot drive). Are you using hdparm commands at all or just setting the bios to udma3?
Quoted 1 line
HPT366 support in kernel configuration.
I am not sure I did this but I'll check. Maybe it's just working as a normal ide interface or something?
Thanks!
Bye for Now,
Ian
\|||/
(o o)
/---------------------------ooO-(_)-Ooo---------------------------\
| Ian Chilton Web: http://www.ichilton.co.uk |
| E-Mail: [email protected] Backup: [email protected] |
|-----------------------------------------------------------------|
| There are 10 types of people in the world: |
| Those who understand binary, and those who don't. |\-----------------------------------------------------------------/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/