public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] PATA vs SATA kernel driver (was: 4 machines - no /dev/cdrom or /dev/dvd anymore)
Date: Wed, 09 Jan 2013 03:01:57 -0600	[thread overview]
Message-ID: <50ED3205.5050803@gmail.com> (raw)
In-Reply-To: <50ED1969.3010309@st.com>

Raffaele BELARDI wrote:
> On 01/07/2013 08:35 AM, Dale wrote:
>> As I understand it, /dev/hdxx is no longer
>> supported on current kernels.  All hard drives are /dev/sdxx and optical
>> drives are /dev/sr0(1,2,3,4 etc).
> Not true, I'm using /dev/hd for all my PATA HD and DVD drives and
> /dev/sd for the SATA HDs. Systems are ~amd64.
>
> At the time /dev/sr was introduced I tried it and had problems on the
> DVD burner (I don't recall which ones, maybe just related to the missing
> /dev/dvd link) so I decided to stick with the old driver.
>
> Is there any advantage to switch to the SATA driver also for PATA drives?
>
> raffaele
>


Did you see this in menuconfig:

< > ATA/ATAPI/MFM/RLL support **(DEPRECATED)**

The last entry on the change log I found on my 3.5.3 kernel was this:

 * 4.61  Jan 22, 2004    - support hardware sector sizes other than 2kB,
 *              Pascal Schmidt <der.eremit@email.de>

If you look at the ide.txt file, it still shows kernel version 2.6 so it
has not been updated to show it is in a series 3 kernel.  Since this is
depreciated, which generally means no longer maintained, you are using
very old drivers that are no longer maintained.  According to the
changelog, it has not been touched since 2004. 

I would think one huge advantage to switching would be drivers that are
maintained.  It may work but what if it has a problem that you don't see
yet?

I'm sure there are people on this list that are MUCH more familiar with
kernels that can answer your question with even more details but I found
that in less than five minutes on my own system.  I didn't even need
google.  So, unless some other more knowledgeable kernel guru comes
along, I would suggest you start using drivers that are not so
outdated.  I only have a regular desktop and my life doesn't rely on it
but I would not use drivers that far out of date that are marked
depreciated.  I certainly wouldn't when newer and maintained drivers are
so easily available in the same kernel.

Hope that helps.

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!



  reply	other threads:[~2013-01-09  9:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09  7:16 [gentoo-user] PATA vs SATA kernel driver (was: 4 machines - no /dev/cdrom or /dev/dvd anymore) Raffaele BELARDI
2013-01-09  9:01 ` Dale [this message]
2013-01-09  9:32   ` Alan McKinnon
2013-01-09  9:59     ` Dale
2013-01-09 10:24       ` Alan McKinnon
2013-01-09 18:58     ` Volker Armin Hemmann
2013-01-09 22:42     ` felix
2013-01-10 21:41       ` Walter Dnes
2013-01-10 22:14         ` Alan McKinnon
2013-01-24  3:42           ` Frank Steinmetzger
2013-01-09  9:57   ` Raffaele BELARDI
2013-01-09 10:35     ` Dale
2013-01-09 18:59     ` Volker Armin Hemmann

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=50ED3205.5050803@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.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