All of lore.kernel.org
 help / color / mirror / Atom feed
From: ljb <ljb1813@pobox.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: cdrom_id from udev-135 hangs
Date: Thu, 26 Feb 2009 02:57:04 +0000	[thread overview]
Message-ID: <go50e0$fec$1@ger.gmane.org> (raw)
In-Reply-To: <gnvkgg$m04$1@ger.gmane.org>

bryan@kadzban.is-a-geek.net wrote:
>...
> Disable CONFIG_IDE.  Or disable CONFIG_BLK_DEV_IDE.  Or maybe disable
> CONFIG_BLK_DEV_IDECD (but I don't know if the PIIX libata driver will
> pick up just the CD drive).  Or disable CONFIG_BLK_DEV_PIIX.  This is in
> approximate order of most-general to most-specific options; turning off
> the last option will disable the least amount of code.
>
> (I have CONFIG_IDE disabled entirely, but whether you can do that will
> depend on your current IDE chipset(s) and their level of libata support..)
>
> There may be ways to do this with kernel options as well, but I don't
> know of any offhand.  Check Documentation/kernel-parameters.txt for the
> full list of flags; something appropriate may be in there.  (At least
> that would let you avoid recompiling.)

I was afraid it might take something like that - recompile without IDE or
IDECD. I'll have to think about if I'm brave enough to try that. Also
considering the libata PATA drivers are considered "experimental".

I did look at kernel-parameters.txt before posting to see if there was
something for libata like the old 2.4 option for having ide-scsi handle the 
CD instead of the regular IDE driver.  I didn't find anything there. I did
find this in ide.txt: "ide_core.noprobe=1.0". It causes the IDE driver to
ignore my CD drive (master device, secondary channel). But libata doesn't
pick it up automatically. If there is a way to get it to do so, I haven't
found it.


      parent reply	other threads:[~2009-02-26  2:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24  2:02 cdrom_id from udev-135 hangs ljb
2009-02-24  2:14 ` Kay Sievers
2009-02-25  3:24 ` ljb
2009-02-25  4:11 ` Bryan Kadzban
2009-02-26  2:57 ` ljb [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='go50e0$fec$1@ger.gmane.org' \
    --to=ljb1813@pobox.com \
    --cc=linux-hotplug@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.