[lkml]   [2002]   [Sep]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.20-pre4-ac1 trashed my system
Andre Hedrick <> writes:

> On Sat, 31 Aug 2002, Mike Isely wrote:
>> On Fri, 30 Aug 2002, Andre Hedrick wrote:
>> > When you said you put it on primary channel, I realized that you have a
>> > system that breaks the rules of Promise and I am not sure.
>> What are the "rules of Promise" or where may I find such information?
> You do not want to sign the NDA's to get the data sheets, aquire all the
> hardware to test, generate tables of irregularities, query Promise, and
> then scratch your head why.
> I have a FastTrak 100 TX4 the BIOS fails to see beyond 128GB, but in
> practice it does.
> The PDC20267 will puke in 48-bit DMA, but run clean in 48-bit PIO :-/
> Oh but that is the primary channel, Seconday Channel is clean both ways :-\
> PDC20262 works in 48-bit DMA every where.
> PDC20265 similar to PDC20267 except yours.
> Rules are emperical tests and rants back at the OEM, and ....

Another data point: My experiences with 2.4.19-pre4-ac2 are remarkably
similar to Mike Isley's, but for a few interesting differences:

- 2.4.18 runs O.K.
- 2.4.19 hangs when checking for partitions
- 2.4.19-ac4 hangs, too
- 2.4.20-pre4 hangs, too
- 2.4.20-pre4-ac2 does not hang, but shows problems exactly as Mike is
- Claims 80pin cable is missing
- wrong data read from disk, write based on wrong read trashes fs

My hardware:
o Promise PDC20262 On-Board on a GigaByte GA-6BX7+ (Intel 440BX)
o Maxtor 120G (4G120J6)

>> > grep "hwif->addressing" pdc202xx.c
>> >
>> > Stub out the three lines.
>> >
>> > Recompile and reboot, it will be fixed
>> Will do. Thanks. If you have a more permanent fix you'd like me to
>> test, let me know.
> Oh another dang piece of the puzzle found and it does not fit anywhere!

Does this fix the bogus 80-pin message or does it just have to do with
block addressing and thus the "corruption" issue?

I'm asking because the 20262 seems to break ATAPI devices completely
once it was in a "wrong" mode. I.e. if my PX-W1610 on the second
channel is correctly detected as MDMA2 it works, if it is detected as
something else and I try to tweak it the channel and/or controller

Can I somewhere get a complete picture of what is *supposed* to work
with the '62 and what not?

Thanks a lot!

So long,

"I use emacs, which might be thought of as a thermonuclear
word processor."
-- Neal Stephenson, "In the beginning... was the command line"
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.105 / U:20.784 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site