From: Samuel Flory <sflory@rackable.com>
To: Teodor Iacob <Teodor.Iacob@astral.kappa.ro>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: UDMA 133 on a 40 pin cable
Date: Thu, 02 Jan 2003 11:47:56 -0800 [thread overview]
Message-ID: <3E14976C.8090403@rackable.com> (raw)
In-Reply-To: 20030102192316.GA28781@linux.kappa.ro
Teodor Iacob wrote:
>>>00:11.1 IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master
>>>IDE (rev 06)
>>>
>>>hdd: Maxtor 6Y060L0, ATA DISK drive
>>>
>>>the harddisk is DiamondPlus9 60GB 7200 rpm UDMA133 .. and the mainbboard
>>>is Soltek 75-FRV
>>>with KT400 chipset
>>>
>>>
>>>
>>>
>> What's hdc? Hdd is the secondary slave. If it's the only device on
>>the chain you should make sure you jumper the drive as a master.
>>
>>
>
>HDC it's a CD-RW .. it was not used at the time of the error ( i was doing
>mke2fs on hdd1 when I got those errors in dmesg ).
>
>
>
Try setting the cd-rw as a slave, and the hard drive as a master.
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-01-02 19:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 18:29 UDMA 133 on a 40 pin cable Teodor Iacob
2003-01-02 19:37 ` Alan Cox
2003-01-02 18:59 ` Teodor Iacob
2003-01-02 19:21 ` Samuel Flory
2003-01-02 19:23 ` Teodor Iacob
2003-01-02 19:47 ` Samuel Flory [this message]
2003-01-02 20:37 ` Teodor Iacob
2003-01-03 2:26 ` Joshua Stewart
2003-01-02 22:00 ` Lionel Bouton
2003-01-02 22:40 ` Ross Biro
2003-01-02 22:42 ` Teodor Iacob
2003-01-03 1:04 ` Lionel Bouton
2003-01-03 1:57 ` Alan Cox
2003-01-03 10:20 ` IDE termination (was Re: UDMA 133 on a 40 pin cable) John Bradford
2003-01-03 10:29 ` Andre Hedrick
2003-01-02 23:24 ` UDMA 133 on a 40 pin cable Alan Cox
2003-01-02 22:45 ` Ross Biro
2003-01-03 1:15 ` Lionel Bouton
2003-01-03 16:14 ` Vojtech Pavlik
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=3E14976C.8090403@rackable.com \
--to=sflory@rackable.com \
--cc=Teodor.Iacob@astral.kappa.ro \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.