From: CaT <cat@zip.com.au>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Regression? 2.6.23.16 -> 2.6.32.9: ide/libata HD recognition
Date: Sat, 13 Mar 2010 18:39:58 +1100 [thread overview]
Message-ID: <20100313073958.GK2657@zip.com.au> (raw)
In-Reply-To: <4B998516.1000606@gmail.com>
On Thu, Mar 11, 2010 at 06:04:38PM -0600, Robert Hancock wrote:
> That sounds like you had a slave with no master on the second IDE
Indeed.
> channel. That really isn't a wise configuration and is prone to break
> (some devices don't work in this setup, some BIOSes choke, etc.) since
> the standard doesn't really allow this (the spec says that support for
> this configuration is "host specific" and not mandatory).
I've never had it cause issues. BIOS has always recognised the HDs and
linux, until now, has always been more than happy to work with them.
This is across many different mbs, ide chips and hds.
On this server a lone hdd has been the case for 4 years and has worked
fine.
> Essentially, fixing the hardware config to set the drive for master if
> it's the only device on the channel is likely the best solution overall.
It is what worked, after a lot of futzing around. Still, this is a
regression (from the pov of someone who just had to futz). Before
whatever change was made things were fine and futz-free.
--
"A search of his car uncovered pornography, a homemade sex aid, women's
stockings and a Jack Russell terrier."
- http://www.news.com.au/story/0%2C27574%2C24675808-421%2C00.html
prev parent reply other threads:[~2010-03-13 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 4:16 Regression? 2.6.23.16 -> 2.6.32.9: ide/libata HD recognition CaT
2010-03-10 18:47 ` Bill Davidsen
2010-03-11 22:54 ` CaT
2010-03-12 0:04 ` Robert Hancock
2010-03-13 7:39 ` CaT [this message]
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=20100313073958.GK2657@zip.com.au \
--to=cat@zip.com.au \
--cc=hancockrwd@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox