From: "Tobias Müller" <Tobias_Mueller@twam.info>
To: linux-ide@vger.kernel.org
Subject: Re: 40-wire cable detected when directly connected
Date: Sat, 12 Jan 2008 14:40:18 +0100 [thread overview]
Message-ID: <4788C342.2000308@twam.info> (raw)
In-Reply-To: <47883378.9060507@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
Hi
> Please apply the attached patch and specify libata.force_cbl=80 as
> kernel boot parameter. If you load libata from initrd or after boot you
> need to pass 'force_cbl=80' as module parameter. How you do it depends
> on your distro.
[ 41.116289] ata7: forcing 80c
[ 41.116356] ata7.00: ATA-4: SanDisk SDCFX4-8192, HDX 4.20, max UDMA/66
[ 41.116420] ata7.00: 16007040 sectors, multi 0: LBA
[ 41.116489] ata7.00: limited to UDMA/33 due to 40-wire cable
[ 41.117219] ata7.00: configured for UDMA/33
Speed is still the same and hdparm -I /dev/sdc sill says
[...]
Capabilities:
LBA, IORDY(may be)(cannot be disabled)
Standby timer values: spec'd by Vendor
R/W multiple sector transfer: Max = 4 Current = 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
[...]
Regards
Tobias
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3389 bytes --]
next prev parent reply other threads:[~2008-01-12 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 17:24 40-wire cable detected when directly connected Tobias Müller
2008-01-11 3:53 ` Tejun Heo
2008-01-11 11:47 ` Tobias Müller
2008-01-12 3:26 ` Tejun Heo
2008-01-12 13:40 ` Tobias Müller [this message]
2008-01-13 6:06 ` Tejun Heo
2008-01-12 14:38 ` Bartlomiej Zolnierkiewicz
2008-01-12 14:29 ` Tobias Müller
2008-01-12 16:09 ` Bartlomiej Zolnierkiewicz
2008-01-12 16:14 ` Bartlomiej Zolnierkiewicz
2008-01-12 16:22 ` Tobias Müller
2008-01-12 17:23 ` Tobias Müller
2008-01-11 13:56 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4788C342.2000308@twam.info \
--to=tobias_mueller@twam.info \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).