Skip to contentSkip to conversation

Promise Ultra100 IDE PDC20265 chip problem

DISCUSSION Jeremy Jackson 1 participant 1 message Mar 1, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 1 line · [email protected] wrote:

(I am not subscribed to this list, if it is in fact a list. Please CC

any

Quoted 3 lines

replies to me directly - Thanks)

I am attempting to install the new beta release of Red Hat (fisher) on

my

Quoted 1 line

home computer. It has an Asus A7V motherboard and a Promise Ultra100

IDE

Quoted 1 line

controller (PDC20265 chip), with two partitions. Windows ME is

installed in

Quoted 1 line

the first partition. The second one is where I'm attempting to install

Red

Quoted 3 lines

Hat.

In previous releases of the Linux kernel, my hard drive was not seen

at all.

Quoted 1 line

I could go all the way up to the point in the Red Hat installation

where it

Quoted 1 line

wanted to do disk geometry, and then said that I didn't have any mass

media

Quoted 3 lines

device. Searching through various mail archives lead me to believe the

culprit was the PDC20265 controller chip and the fact that it was too

new to

Quoted 3 lines

be recognized.

In the new kernel 2.4.0 (and thereby the fisher release of Red Hat), I

now

Quoted 1 line

see the error below printed out to the console when booting from the

Red Hat

Quoted 1 line

installation floppy. After the error is printed out, my computer

hangs. I

Quoted 1 line

apologize in advance if this is not a Linux kernel issue, and

appreciate any

Quoted 9 lines

help that can be provided.

--Pete

[snip]

PDC 20265: chipset revision 2
PDC 20265: not 100% native mode: will probe irqs later

Quoted 7 lines

[snip]

Partition Check:
hde: [PTBL] [1826/255/63] hde1 hde2 < hde5hde: dma_intr: status=0x51 {

DriveReady SeekComplete Error }
hde: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=32885055,

sector=0

Quoted 6 lines

hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }

[last repeats 3-4 times]

hde: DMA disabled

this looks like a sign that the kernel you're using is configured to try to use

harddisk DMA right at boot. That *could* cause problems in rare cases. SectorIdNotFound looks like a bad sector on the harddisk though. looks like you can't get into linux at all... try scandisk from windows on Thorough setting (have to format linux partition as fat32 first).