All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Robert M. Stockmann" <stock@stokkie.net>, linux-kernel@vger.kernel.org
Subject: Re: SATA disk device naming ?
Date: Wed, 14 Jul 2004 13:20:28 +0200	[thread overview]
Message-ID: <200407141320.32608.arnd@arndb.de> (raw)
In-Reply-To: <40F35140.6020509@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 553 bytes --]

On Dienstag, 13. Juli 2004 05:04, Jeff Garzik wrote:
> Whoever builds your kernels changed around the kernel configuration on you.
> 
> SATA "disk naming" (what driver you use) did not change from 2.6.3 to 2.6.7.
> 
The thing that changed is the new BLK_DEV_IDE_SATA option that defaults
to 'n', while before it was enabled implicitly.

I was bitten by this as well. Unfortunately I have an md RAID-0 volume
which I can not start after hde/hdg become sda/sdb, so I'll probably
have to keep using the old IDE driver indefinitely.

	Arnd <><

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-14 11:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13  2:25 SATA disk device naming ? Robert M. Stockmann
2004-07-13  3:04 ` Jeff Garzik
2004-07-14 11:20   ` Arnd Bergmann [this message]
2004-07-15 17:37     ` Bartlomiej Zolnierkiewicz
2004-07-15 18:07       ` Jeff Garzik
2004-07-13  6:46 ` Eric D. Mudama
2004-07-13 13:24   ` Ian Soboroff
2004-07-13 16:23   ` Ricky Beam
2004-07-13 16:49     ` Jeff Garzik
2004-07-13 17:29       ` Tigran Aivazian
2004-07-13 22:35       ` Chris Wedgwood
2004-07-14  9:48         ` P
2004-07-15  2:44         ` Joel Becker
2004-07-25 19:05           ` Greg KH
2004-07-13 17:15     ` Tigran Aivazian
2004-07-13 16:58       ` Muli Ben-Yehuda
  -- strict thread matches above, loose matches on Subject: below --
2004-07-14  0:09 DaMouse

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=200407141320.32608.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stock@stokkie.net \
    /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.