linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott James Remnant <scott@ubuntu.com>
To: linux-ide@vger.kernel.org
Cc: linux-hotplug-devel@lists.sourceforge.net
Subject: Problem with IDE driver not claiming the disk
Date: Mon, 05 Dec 2005 23:56:33 +0000	[thread overview]
Message-ID: <1133826994.8181.68.camel@localhost.localdomain> (raw)

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

Hi there,

We've been having some IDE problems at Ubuntu Towers and can't seem to
figure out what's up, and I was hoping you guys might instantly spot
what we're doing wrong ...

In order to get the root filesystem mounted (we're in initramfs at this
point), we do the following steps:

1) Run udevd.

   This has rules configured to load the ide-cd, ide-disk, ide-floppy or
   ide-tape modules when a device matching SUBSYSYTEM=="ide" is added.
   We decide which module to load by looking at /proc/ide/ide*/*/media
   (after waiting for that to turn up)

   This also has the standard rules to modprobe $MODALIAS, should that
   be set.

2) Look in /sys/bus/pci/devices for those with a class of 0x01* (storage
   devices), and write to the uevent file of each.


This results in ide-core being loaded, along with the appropriate driver
for the IDE controller and the "generic" module.  On my laptop (an HP
nc4010) I get the alim15x3 driver, on a colleague's (Acer 1520 AMD64) he
gets the via82cxxx driver.

At this point, there is nothing in /proc/ide other than an empty
"drivers" file, and nothing in /sys/bus/ide/devices -- though this
directory does now exist.

In particular there are also no events for any devices on the bus...


In order to get those events, and find out what's on the bus, we
explicitly load the "ide-generic" driver.  This spawns a whole number of
events, creating a whole array of devices -- /dev/hda* and friends.

The ide-disk module is loaded as a result of these events.


On my laptop with the alim15x3 driver, the disks appear to be bound to
this driver; in particular the following is true:

	# readlink /sys/bus/ide/devices/0.0
	../../../devices/pci0000:00/0000:00:10.0/ide0/0.0

	# readlink /sys/devices/pci0000:00/0000:00:10.0/driver
	../../../bus/pci/drivers/ALI15x3_IDE

However on the via82cxx laptop we see:

	# readlink /sys/bus/ide/devices/0.0
	../../../devices/pci0000:00/0000:00:11.1/ide0/0.0

	# readlink /sys/devices/pci0000:00/0000:00:11.1/driver
	../../../bus/pci/drivers/PCI_IDE

It looks like the device is being claimed by the ide-generic driver, and
not the VIA one.

Do you concur?  What are we doing wrong, or what is the driver doing
wrong?

Scott
-- 
Scott James Remnant
scott@ubuntu.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-12-05 23:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05 23:56 Scott James Remnant [this message]
2005-12-06  0:34 ` Problem with IDE driver not claiming the disk Bartlomiej Zolnierkiewicz
2005-12-06  1:36   ` Scott James Remnant
2005-12-06  8:23     ` Bartlomiej Zolnierkiewicz
2005-12-06 12:39       ` Scott James Remnant

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=1133826994.8181.68.camel@localhost.localdomain \
    --to=scott@ubuntu.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).