RE: Nvidia cable detection problems (was [PATCH] amd74xx: don't configure udma mode higher than BIOS did)

Unfortunately there's no standard way to do host side cable detect on
nForce systems without going through ACPI. It's done through a GPIO
pin. Board vendors are free to reallocate which GPIO pin is used for
this feature.

One possible solution is to leave the default DMA mode at whatever the
BIOS left it at. So if it's a UDMA5 drive but the BIOS left it at UDMA2
it was because of cable detect.

The *real* solution is to use the BIOS ACPI _GTM _STM methods for this.
Then you can remove all chipset specific knowledge from the IDE driver.
This is what the MS driver does on Windows, so you know it's received a
lot of testing from NVIDIA and board vendors.

-Allen

-----Original Message-----
From: Bartlomiej Zolnierkiewicz [mailto:bzolnier@xxxxxxxxx]
Sent: Monday, February 05, 2007 7:09 AM
To: Allen Martin
Subject: Fwd: Nvidia cable detection problems (was [PATCH]
amd74xx: don't configure udma mode higher than BIOS did)

Hi Allen,

Would it be possible to get some help on this issue?

Thanks,
Bart

---------- Forwarded message ----------
From: Tejun Heo <htejun@xxxxxxxxx>
Date: Feb 5, 2007 3:50 PM
Subject: Re: Nvidia cable detection problems (was [PATCH] amd74xx:
don't configure udma mode higher than BIOS did)
To: Alan <alan@xxxxxxxxxxxxxxxxxxx>
Cc: bzolnier@xxxxxxxxx, linux-ide@xxxxxxxxxxxxxxx,
linux-kernel@xxxxxxxxxxxxxxx


Alan wrote:
[--snip--]
CK804 IDE, at least mine, reports 80c in a lot of cases where it
shouldn't. I dunno the reason but it also makes drives confused
about cable type. Maybe it has the wrong capacitor
attached or something.
This is A8N-E from ASUS, probably one of the popular ones
using nf4.

I take it this was how you came to find every cable related
bug while
trying to work out what was going on ?

Yeap, pretty much. I thought fixing drive side cable
detection would fix it, but hell no.

When that happens, libata EH does its job and slows the
interface to
udma33 after quite a few error messages. On IDE, if this happens,
the drive is put into PIO mode making the machine painful to use.

No the IDE layer does DMA changedown fine, well apart from all the
error/timer races in the old IDE code.

I dunno. It always ended up in PIO mode in my case. I can
post the log if necessary.

[--snip--]
I agree with you that this is a hack and ugly as hell. I
don't like
it either, but it solves an existing problem which could have and
possibly will hit many users. So, I think this problem should at
least be verified. If it's just my BIOS/motherboard
that's crazy, I
have no problem forgetting about this.

It certainly seems to be Nvidia specific, so perhaps Nvidia can
provide more details on the Nforce4 cable detection ? As
with a lot of
Nvidia stuff there was much reverse engineering involved in the
original code base.

Hmmm... Anyone happen to have working nvidia contact?

And if its a specific board or couple of boards then we
should perhaps
use DMI to match them specifically.

So, anyone with CK804 (a.k.a NF4) up for some testing?

If it still goes I've got a rather iffy NF3 but not an NF4 handy.

Yeah, please. If I connect a hdd at the end of 40c cable and
leaving the middle connector empty, the 80c bit is always one
and the drive says it's 80c cable while the BIOS configured
mode is correctly udma33. This is the same for SAMSUNG
SP0802N, Maxtor 91301U3 and HITACHI_DK23BA-20.

--
tejun

-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Nvidia cable detection problems & ACPI (beware, slight off-top)
    ... Subject: Nvidia cable detection problems (was amd74xx: don't configure udma mode higher than BIOS did) ... I dunno the reason but it also makes drives confused ...
    (Linux-Kernel)
  • Re: A8N-SLI Deluxe : using SATA_RAID connectors just for extra SATA drives (not RAID) ?
    ... >>>drives and 2 on the Nvidia SATA ports No raid required ... >> I'm deducing that by flashing the controller with the IDE BIOS ... >> (as opposed to the RAID BIOS), that one might be able to simply ... No it was pretty straughforward with the Si3114 With the nvidia controller ...
    (alt.comp.periphs.mainboard.asus)
  • Re: HDD Compatibility
    ... and new larger drives appear in the ... BIOS Upgrades ... available expansion slot and then connecting your hard drives to it. ... than having to connect them to the controller card itself. ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: Ruined m-board with bios update
    ... Doubt that you will be back to this post to see this, but if you are, I received an an identical replacement motherboard from Intel today and just finished installing it. ... Plugged all the hard drives into the same connections as the old board and after all the other tiny little connections I turned it on. ... to re-set the clock in the bios and that was no problem. ... Turned power on & inserted recovery CD. ...
    (microsoft.public.windows.mediacenter)
  • Re: Ruined m-board with bios update
    ... Plugged all the hard drives ... reactivating on a new motherboard. ... Turned power on & inserted recovery CD. ... recovery bios! ...
    (microsoft.public.windows.mediacenter)