From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Christoph Pleger <Christoph.Pleger@cs.uni-dortmund.de>,
linux-kernel@vger.kernel.org
Subject: Re: PATA-disk named sda
Date: Fri, 6 Jul 2007 20:09:08 +0200 [thread overview]
Message-ID: <200707062009.08635.bzolnier@gmail.com> (raw)
In-Reply-To: <468E5420.7090605@shaw.ca>
Hi,
On Friday 06 July 2007, Robert Hancock wrote:
> Christoph Pleger wrote:
> > Hello,
> >
> >>> In the newest Ubuntu Release, my PATA-disk is called sda instead of
> >>> hda. Is that a general feature in newer kernel versions or is it a
> >>> special feature in Ubuntu?
> >> General. SATA and now PATA drives map onto the /dev/sd range as do
> >> SCSI, USB etc
> >
> > It seems to be not that simple, at least not if both the old IDE
> > interface and the new libata interface are enabled as modules: In my
> > Ubuntu system, I created two kernel packages (from the same kernel
> > source and with the same configuration) and installed them. Afterwards,
> > I re-created the initial ramdisks, one with the Ubuntu feisty utilities
> > and one with Debian etch utilities. So, I had the same kernel with
> > different ramdisks. With the Ubuntu ramdisk, my harddrive was named sda,
> > but with the Debian ramdisk, it was named hda.
> >
> > So, the name of the drive can depend on something which happens in the
> > ramdisk environment. Does anybody know what that is? And is there a
> > kernel command line parameter which restores the old behaviour?
> >
> > And what about hdparm (setting 32bit I/O and multi-sector mode)? Suren
> > wrote that 32bit I/O makes no sense when using DMA. Maybe that's right,
> > but it does not correspond with my experiences. At least, I have the
> > "feeling" that my IDE disks work much faster since I enabled 32bit
> > support (DMA already was on before).
>
> No, it has absolutely no effect in DMA mode.
>
> Currently the DMA, multi-sector mode, etc. are not controllable with
> hdparm with libata. libata is designed to use the fastest settings
> possible by default. In a lot of cases this messing with hdparm was only
> needed because of stupidity with the old IDE code (like DMA not being
> automatically enabled if the low-level driver was built modular).
AFAIR there has never been such issue with IDE subsystem.
In modular case you just have to remember to _not_ load generic
IDE host driver if you don't need it, same with libata PATA.
Bart
next prev parent reply other threads:[~2007-07-06 17:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.VMMtK2yPXE5gkxuIC8MWb1aPBiQ@ifi.uio.no>
[not found] ` <fa.23lYEA4r0kfTVDJ1AKcxSE4vGKA@ifi.uio.no>
[not found] ` <fa.DRDWDh+VAXx84D/6XHgY6h2wB+E@ifi.uio.no>
2007-07-06 14:39 ` PATA-disk named sda Robert Hancock
2007-07-06 17:58 ` Mark Lord
2007-07-06 18:47 ` Bartlomiej Zolnierkiewicz
2007-07-06 18:09 ` Bartlomiej Zolnierkiewicz [this message]
2007-07-06 8:21 Christoph Pleger
2007-07-06 9:13 ` Suren Karapetyan
2007-07-06 9:36 ` Christoph Pleger
2007-07-06 9:58 ` Suren Karapetyan
2007-07-06 17:55 ` Mark Lord
2007-07-07 18:33 ` Jan Engelhardt
2007-07-06 9:52 ` Alejandro Riveira Fernández
2007-07-06 10:11 ` Uwe Kiewel
2007-07-06 10:18 ` Alan Cox
2007-07-06 12:30 ` Christoph Pleger
2007-07-06 14:40 ` Gabriel C
2007-07-06 15:19 ` Alan Cox
2007-07-07 21:40 ` Rene Herman
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=200707062009.08635.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=Christoph.Pleger@cs.uni-dortmund.de \
--cc=hancockr@shaw.ca \
--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