Broken HPT366?

Broken HPT366?

Post by TomG » Wed, 10 May 2000 04:00:00



I doubt you broke your chip.  can you enter the HPT bios screen via the
Control H command?  if so, can you then make the HPT bios see any drives?  I
don't know what the newest bios is for your board but many people have had
trouble with the 1.21 version of HPT bios.  I don't know if there is a way
for you to get to 1.22 HPT bios or not but if you can, try that as well.


Quote:> I suspect I have a broken HPT366 chip or motherboard, but I wanted
> to see if anyone else had similar problems.

> I have an Abit BP-6, dual celeron 466's (not overclocked),
> with the HPT 366 chip on-board.  The chip reads,

>   HighPoint JAPAN
>   HPT366
>   9920 L010

> (incidentally, I noticed on http://www.highpoint-tech.com/hpt366.htm
>  that some chips seem to have newer "lot" numbers).

> And I have three hard drives:
>   QUANTUM FIREBALL CR13.0A
>   Maxtor 52049U4 (x2)

> I've tried various combinations of the Quantum and the Maxtors
> on the two HPT IDE channels, and in every case, devices on the
> first HPT IDE channel are not recognized by the BIOS, nor by
> Linux 2.3.99pre6 (probably as a consequence of the BIOS not
> initializing them). For example, with the Quatum on the plain
> IDE channel and one Maxtor on each HPT channel, Linux reports
> the following (my comments in []'s),

>   HPT366: onboard version of chipset, pin1=1 pin2=2
>   HPT366: IDE controller on PCI bus 00 dev 98
>   HPT366: not 100% native mode: will probe irqs later
>       ide2: BM-DMA at 0xb400-0xb407, BIOS settings: hde:pio, hdf:pio
>                                                        [^^^ bad]
>   HPT366: IDE controller on PCI bus 00 dev 99
>   HPT366: not 100% native mode: will probe irqs later
>       ide3: BM-DMA at 0xc000-0xc007, BIOS settings: hdg:DMA, hdh:pio
>                                                        [^^^ good]

>   hda: QUANTUM FIREBALL CR13.0A, ATA DISK drive
>   hdc: CR-4802TE, ATAPI CDROM drive
>   hdg: Maxtor 52049U4, ATA DISK drive
>   ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>   ide1 at 0x170-0x177,0x376 on irq 15
>   [ide2 (first HPT channel) not reported!]
>   ide3 at 0xb800-0xb807,0xbc02 on irq 11
>   hda: 25429824 sectors (13020 MB) w/418KiB Cache, CHS=1582/255/63,
> UDMA(33)
>   hdg: 40020624 sectors (20491 MB) w/2048KiB Cache, CHS=39703/16/63,
> UDMA(66)

> The second channel works fine, with any of the individual drives,
> or with two drives on the same channel (master/slave).  I want
> to take advantage of software RAID-0, and my impression is
> that one-drive-per-channel is they way to go.

> I tried three different UDMA/66 cables (80 wires, blue end on
> the mobo), with no difference.

> I upgraded my flash with BP6_NJ.BIN (1.21 I believe), so I get
> the Blue HPT bios screen, but devices on the first HPT channel
> are still not being detected.

> So my questions are:
> Is there anything I can do to get drives deteced on the first
>   HPT channel?
> Am I missing something?
> Do you think my HPT366 is broken?

> Thanks in advance,
> -Jamie

 
 
 

Broken HPT366?

Post by Jamie Guina » Thu, 11 May 2000 04:00:00


I suspect I have a broken HPT366 chip or motherboard, but I wanted
to see if anyone else had similar problems.

I have an Abit BP-6, dual celeron 466's (not overclocked),
with the HPT 366 chip on-board.  The chip reads,

  HighPoint JAPAN
  HPT366
  9920 L010

(incidentally, I noticed on http://www.highpoint-tech.com/hpt366.htm
 that some chips seem to have newer "lot" numbers).

And I have three hard drives:
  QUANTUM FIREBALL CR13.0A
  Maxtor 52049U4 (x2)

I've tried various combinations of the Quantum and the Maxtors
on the two HPT IDE channels, and in every case, devices on the
first HPT IDE channel are not recognized by the BIOS, nor by
Linux 2.3.99pre6 (probably as a consequence of the BIOS not
initializing them). For example, with the Quatum on the plain
IDE channel and one Maxtor on each HPT channel, Linux reports
the following (my comments in []'s),

  HPT366: onboard version of chipset, pin1=1 pin2=2
  HPT366: IDE controller on PCI bus 00 dev 98
  HPT366: not 100% native mode: will probe irqs later
      ide2: BM-DMA at 0xb400-0xb407, BIOS settings: hde:pio, hdf:pio
                                                       [^^^ bad]
  HPT366: IDE controller on PCI bus 00 dev 99
  HPT366: not 100% native mode: will probe irqs later
      ide3: BM-DMA at 0xc000-0xc007, BIOS settings: hdg:DMA, hdh:pio
                                                       [^^^ good]

  hda: QUANTUM FIREBALL CR13.0A, ATA DISK drive
  hdc: CR-4802TE, ATAPI CDROM drive
  hdg: Maxtor 52049U4, ATA DISK drive
  ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
  ide1 at 0x170-0x177,0x376 on irq 15
  [ide2 (first HPT channel) not reported!]
  ide3 at 0xb800-0xb807,0xbc02 on irq 11
  hda: 25429824 sectors (13020 MB) w/418KiB Cache, CHS=1582/255/63,
UDMA(33)
  hdg: 40020624 sectors (20491 MB) w/2048KiB Cache, CHS=39703/16/63,
UDMA(66)

The second channel works fine, with any of the individual drives,
or with two drives on the same channel (master/slave).  I want
to take advantage of software RAID-0, and my impression is
that one-drive-per-channel is they way to go.

I tried three different UDMA/66 cables (80 wires, blue end on
the mobo), with no difference.

I upgraded my flash with BP6_NJ.BIN (1.21 I believe), so I get
the Blue HPT bios screen, but devices on the first HPT channel
are still not being detected.

So my questions are:  
Is there anything I can do to get drives deteced on the first
  HPT channel?
Am I missing something?
Do you think my HPT366 is broken?

Thanks in advance,
-Jamie

 
 
 

Broken HPT366?

Post by Jamie Guina » Thu, 11 May 2000 04:00:00


I suspect I have a broken HPT366 chip or motherboard, but I wanted
to see if anyone else had similar problems.

I have an Abit BP-6, dual celeron 466's (not overclocked),
with the HPT 366 chip on-board.  The chip reads,

  HighPoint JAPAN
  HPT366
  9920 L010

(incidentally, I noticed on http://www.highpoint-tech.com/hpt366.htm
 that some chips seem to have newer "lot" numbers).

And I have three hard drives:
  QUANTUM FIREBALL CR13.0A
  Maxtor 52049U4 (x2)

I've tried various combinations of the Quantum and the Maxtors
on the two HPT IDE channels, and in every case, devices on the
first HPT IDE channel are not recognized by the BIOS, nor by
Linux 2.3.99pre6 (probably as a consequence of the BIOS not
initializing them). For example, with the Quatum on the plain
IDE channel and one Maxtor on each HPT channel, Linux reports
the following (my comments in []'s),

  HPT366: onboard version of chipset, pin1=1 pin2=2
  HPT366: IDE controller on PCI bus 00 dev 98
  HPT366: not 100% native mode: will probe irqs later
      ide2: BM-DMA at 0xb400-0xb407, BIOS settings: hde:pio, hdf:pio
                                                       [^^^ bad]
  HPT366: IDE controller on PCI bus 00 dev 99
  HPT366: not 100% native mode: will probe irqs later
      ide3: BM-DMA at 0xc000-0xc007, BIOS settings: hdg:DMA, hdh:pio
                                                       [^^^ good]

  hda: QUANTUM FIREBALL CR13.0A, ATA DISK drive
  hdc: CR-4802TE, ATAPI CDROM drive
  hdg: Maxtor 52049U4, ATA DISK drive
  ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
  ide1 at 0x170-0x177,0x376 on irq 15
  [ide2 (first HPT channel) not reported!]
  ide3 at 0xb800-0xb807,0xbc02 on irq 11
  hda: 25429824 sectors (13020 MB) w/418KiB Cache, CHS=1582/255/63,
UDMA(33)
  hdg: 40020624 sectors (20491 MB) w/2048KiB Cache, CHS=39703/16/63,
UDMA(66)

The second channel works fine, with any of the individual drives,
or with two drives on the same channel (master/slave).  I want
to take advantage of software RAID-0, and my impression is
that one-drive-per-channel is they way to go.

I tried three different UDMA/66 cables (80 wires, blue end on
the mobo), with no difference.

I upgraded my flash with BP6_NJ.BIN (1.21 I believe), so I get
the Blue HPT bios screen, but devices on the first HPT channel
are still not being detected.

So my questions are:  
Is there anything I can do to get drives deteced on the first
  HPT channel?
Am I missing something?
Do you think my HPT366 is broken?

Thanks in advance,
-Jamie

 
 
 

Broken HPT366?

Post by Jamie Guina » Thu, 11 May 2000 04:00:00



> I doubt you broke your chip.  can you enter the HPT bios screen via the
> Control H command?  if so, can you then make the HPT bios see any drives?  I
> don't know what the newest bios is for your board but many people have had
> trouble with the 1.21 version of HPT bios.  I don't know if there is a way
> for you to get to 1.22 HPT bios or not but if you can, try that as well.

Tried 1.22 just now, still can't see anything on the primary HPT
channel.
Not that I broke it myself, but it really looks like a bad HPT chip.

I suppose the best I can do (short of replacing the motherboard) is put
one Maxtor 20G on the secondary HPT, and the other Maxtor 20G on my
secondary PIIX4 IDE channel (UDMA/33).  Not optimal, but I imagine
better
than putting both on the same HPT cable.

-Jamie

 
 
 

Broken HPT366?

Post by TomG » Thu, 11 May 2000 04:00:00


maybe not... you ought to try both and benchmark with HDTach or something
similar...



> > I doubt you broke your chip.  can you enter the HPT bios screen via the
> > Control H command?  if so, can you then make the HPT bios see any
drives?  I
> > don't know what the newest bios is for your board but many people have
had
> > trouble with the 1.21 version of HPT bios.  I don't know if there is a
way
> > for you to get to 1.22 HPT bios or not but if you can, try that as well.

> Tried 1.22 just now, still can't see anything on the primary HPT
> channel.
> Not that I broke it myself, but it really looks like a bad HPT chip.

> I suppose the best I can do (short of replacing the motherboard) is put
> one Maxtor 20G on the secondary HPT, and the other Maxtor 20G on my
> secondary PIIX4 IDE channel (UDMA/33).  Not optimal, but I imagine
> better
> than putting both on the same HPT cable.

> -Jamie

 
 
 

Broken HPT366?

Post by chris moor » Thu, 11 May 2000 04:00:00


install large drives with maxblast software from cold boot on floppy disk
download it at maxtor.com
chr


> > I doubt you broke your chip.  can you enter the HPT bios screen via the
> > Control H command?  if so, can you then make the HPT bios see any drives?  I
> > don't know what the newest bios is for your board but many people have had
> > trouble with the 1.21 version of HPT bios.  I don't know if there is a way
> > for you to get to 1.22 HPT bios or not but if you can, try that as well.

> Tried 1.22 just now, still can't see anything on the primary HPT
> channel.
> Not that I broke it myself, but it really looks like a bad HPT chip.

> I suppose the best I can do (short of replacing the motherboard) is put
> one Maxtor 20G on the secondary HPT, and the other Maxtor 20G on my
> secondary PIIX4 IDE channel (UDMA/33).  Not optimal, but I imagine
> better
> than putting both on the same HPT cable.

> -Jamie

 
 
 

Broken HPT366?

Post by chris moor » Thu, 11 May 2000 04:00:00


install large drives with maxblast software from cold boot on floppy disk
download it at maxtor.com
chris


> > I doubt you broke your chip.  can you enter the HPT bios screen via the
> > Control H command?  if so, can you then make the HPT bios see any drives?  I
> > don't know what the newest bios is for your board but many people have had
> > trouble with the 1.21 version of HPT bios.  I don't know if there is a way
> > for you to get to 1.22 HPT bios or not but if you can, try that as well.

> Tried 1.22 just now, still can't see anything on the primary HPT
> channel.
> Not that I broke it myself, but it really looks like a bad HPT chip.

> I suppose the best I can do (short of replacing the motherboard) is put
> one Maxtor 20G on the secondary HPT, and the other Maxtor 20G on my
> secondary PIIX4 IDE channel (UDMA/33).  Not optimal, but I imagine
> better
> than putting both on the same HPT cable.

> -Jamie

 
 
 

Broken HPT366?

Post by Fx » Sat, 13 May 2000 04:00:00


I have the Quantum Fireball CX 13Gb and the same BP6, but my hard disk is
faster in ATA33 than ATA66. I suspect that it is broken. It's correct?



Quote:> I suspect I have a broken HPT366 chip or motherboard, but I wanted
> to see if anyone else had similar problems.

> I have an Abit BP-6, dual celeron 466's (not overclocked),
> with the HPT 366 chip on-board.  The chip reads,

>   HighPoint JAPAN
>   HPT366
>   9920 L010

> (incidentally, I noticed on http://www.highpoint-tech.com/hpt366.htm
>  that some chips seem to have newer "lot" numbers).

> And I have three hard drives:
>   QUANTUM FIREBALL CR13.0A
>   Maxtor 52049U4 (x2)

> I've tried various combinations of the Quantum and the Maxtors
> on the two HPT IDE channels, and in every case, devices on the
> first HPT IDE channel are not recognized by the BIOS, nor by
> Linux 2.3.99pre6 (probably as a consequence of the BIOS not
> initializing them). For example, with the Quatum on the plain
> IDE channel and one Maxtor on each HPT channel, Linux reports
> the following (my comments in []'s),

>   HPT366: onboard version of chipset, pin1=1 pin2=2
>   HPT366: IDE controller on PCI bus 00 dev 98
>   HPT366: not 100% native mode: will probe irqs later
>       ide2: BM-DMA at 0xb400-0xb407, BIOS settings: hde:pio, hdf:pio
>                                                        [^^^ bad]
>   HPT366: IDE controller on PCI bus 00 dev 99
>   HPT366: not 100% native mode: will probe irqs later
>       ide3: BM-DMA at 0xc000-0xc007, BIOS settings: hdg:DMA, hdh:pio
>                                                        [^^^ good]

>   hda: QUANTUM FIREBALL CR13.0A, ATA DISK drive
>   hdc: CR-4802TE, ATAPI CDROM drive
>   hdg: Maxtor 52049U4, ATA DISK drive
>   ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>   ide1 at 0x170-0x177,0x376 on irq 15
>   [ide2 (first HPT channel) not reported!]
>   ide3 at 0xb800-0xb807,0xbc02 on irq 11
>   hda: 25429824 sectors (13020 MB) w/418KiB Cache, CHS=1582/255/63,
> UDMA(33)
>   hdg: 40020624 sectors (20491 MB) w/2048KiB Cache, CHS=39703/16/63,
> UDMA(66)

> The second channel works fine, with any of the individual drives,
> or with two drives on the same channel (master/slave).  I want
> to take advantage of software RAID-0, and my impression is
> that one-drive-per-channel is they way to go.

> I tried three different UDMA/66 cables (80 wires, blue end on
> the mobo), with no difference.

> I upgraded my flash with BP6_NJ.BIN (1.21 I believe), so I get
> the Blue HPT bios screen, but devices on the first HPT channel
> are still not being detected.

> So my questions are:
> Is there anything I can do to get drives deteced on the first
>   HPT channel?
> Am I missing something?
> Do you think my HPT366 is broken?

> Thanks in advance,
> -Jamie

 
 
 

Broken HPT366?

Post by Michele Di Mari » Thu, 25 May 2000 04:00:00


Hi Jamie,
    I have a similar problem under Windows2000. When I format in Raid 0
drives from different Ide channel I receive the Windwos2000 blue screen
reporting an error on htp366.sys.

My configuration is:
    Motherboard: Abit BE2 (with the latest bios from Abit)
    UDma Ide controller: htp 366 (drivers version: 1.25.0.10, Bios: 1.21)
    HD: 4x Quantum Fireball lct1 (20Gb)

When I define a striped partition (raid0) and I format it, I receive the
following error:

Error:
    Stop 000000D1:
    Driver Irql not less or equal

This don't happens if I create a partition on hd connected to the same
channel (Drive 0 and 1 or Drive 2 and 3), but it I declare a partition on
Drive 0, 1, 2, 3 or 1, 2, 3 it happens...

Someone can help me please?

Ciao,
    Michele


Quote:> I suspect I have a broken HPT366 chip or motherboard, but I wanted
> to see if anyone else had similar problems.

> I have an Abit BP-6, dual celeron 466's (not overclocked),
> with the HPT 366 chip on-board.  The chip reads,

>   HighPoint JAPAN
>   HPT366
>   9920 L010

> (incidentally, I noticed on http://www.highpoint-tech.com/hpt366.htm
>  that some chips seem to have newer "lot" numbers).

> And I have three hard drives:
>   QUANTUM FIREBALL CR13.0A
>   Maxtor 52049U4 (x2)

> I've tried various combinations of the Quantum and the Maxtors
> on the two HPT IDE channels, and in every case, devices on the
> first HPT IDE channel are not recognized by the BIOS, nor by
> Linux 2.3.99pre6 (probably as a consequence of the BIOS not
> initializing them). For example, with the Quatum on the plain
> IDE channel and one Maxtor on each HPT channel, Linux reports
> the following (my comments in []'s),

>   HPT366: onboard version of chipset, pin1=1 pin2=2
>   HPT366: IDE controller on PCI bus 00 dev 98
>   HPT366: not 100% native mode: will probe irqs later
>       ide2: BM-DMA at 0xb400-0xb407, BIOS settings: hde:pio, hdf:pio
>                                                        [^^^ bad]
>   HPT366: IDE controller on PCI bus 00 dev 99
>   HPT366: not 100% native mode: will probe irqs later
>       ide3: BM-DMA at 0xc000-0xc007, BIOS settings: hdg:DMA, hdh:pio
>                                                        [^^^ good]

>   hda: QUANTUM FIREBALL CR13.0A, ATA DISK drive
>   hdc: CR-4802TE, ATAPI CDROM drive
>   hdg: Maxtor 52049U4, ATA DISK drive
>   ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>   ide1 at 0x170-0x177,0x376 on irq 15
>   [ide2 (first HPT channel) not reported!]
>   ide3 at 0xb800-0xb807,0xbc02 on irq 11
>   hda: 25429824 sectors (13020 MB) w/418KiB Cache, CHS=1582/255/63,
> UDMA(33)
>   hdg: 40020624 sectors (20491 MB) w/2048KiB Cache, CHS=39703/16/63,
> UDMA(66)

> The second channel works fine, with any of the individual drives,
> or with two drives on the same channel (master/slave).  I want
> to take advantage of software RAID-0, and my impression is
> that one-drive-per-channel is they way to go.

> I tried three different UDMA/66 cables (80 wires, blue end on
> the mobo), with no difference.

> I upgraded my flash with BP6_NJ.BIN (1.21 I believe), so I get
> the Blue HPT bios screen, but devices on the first HPT channel
> are still not being detected.

> So my questions are:
> Is there anything I can do to get drives deteced on the first
>   HPT channel?
> Am I missing something?
> Do you think my HPT366 is broken?

> Thanks in advance,
> -Jamie

 
 
 

1. Make broken, top broken, flock errors, kernel modules broken

So many repetitive messages asking the same questions!  Does noone bother
to grep the topics for possible solutions?

Here are some of the answers to your problems:

If you upgrade to ELF libraries, you need an ELF linker:  get new ld.so.

If you upgrade your kernel, you will likely need to upgrade to (or higher):
termcap 2.0.8, proc-ps.0.99a, libc 5.3.12 (see below!), modules-1.3.69f,
gcc 2.7.2.

If you upgrade your libc, you will need to patch or upgrade make to make
3.74.

It may possible that when you upgrade your compiler, you may need to
install a new (ELF) libc.

--
--
William Burrow  --  Fredericton Area Network

2. 2.5.50-bk6-wli-1

3. 2.5: ieee1394 still broken, vesafb still broken, ipv6 still broken

4. RedHat CDE - run on Alpha?

5. Linux support for HPT366 UDMA/66 controller?

6. Time syncing

7. HPT366 Ultra/66 chipset support?

8. combine several windows into one

9. SO you have HPT366 UDMA66 and an ABit BP6 or BE6...

10. give better information which chipsets hpt366.c is for

11. HPT366 + IBM 13.5 GB 7200rpm ATA66 problem ...

12. HPT366: DMA errors?

13. Re : Sharing Interrupt+HPT366 Problem on BP6