linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: roger@opq.se
Cc: linux-ide@vger.kernel.org
Subject: Re: libata question
Date: Wed, 02 Aug 2006 03:45:48 +0900	[thread overview]
Message-ID: <44CFA15C.8080109@gmail.com> (raw)
In-Reply-To: <1154457583.4665.5.camel@shark.pacific>

Roger Oberholtzer wrote:
> On Wed, 2006-08-02 at 00:33 +0900, Tejun Heo wrote:
>> Roger Oberholtzer wrote:
>>> Should hotplug work with Intel Corporation 82801GB/GR/GH (ICH7
>>> Family) chipset? I am trying kernel 2.6.17.7

Ah.. I should have spotted this earlier.  2.6.17.7 doesn't contain 
updated EH and doesn't support any of new features including 
hot/warmplug.  Please try 2.6.18-rc3.

>>> I have been trying the warmplug stuff. But I am not convinced it is 
>>> acting as I expect. If I remove a disk and then do a scan, shouldn't
>>> the disk entry go away?
>> Eventually, yes.  Do you mind to send me the dmesg?
> 
> I have picked out the lines related to this. Some of the complaints at
> the end are probably when I moved the disk. 

Yeap, those look pretty normal for the previous code.  :p

>>> I know about the problems with just removing a disk. But this is with
>>> one that is not mounted. I just want to see if the disks are properly
>>> sensed as coming and going. I am using the warmplug instructions on
>>> your web site.
>> There are some complications with piix PCS register (port 
>> enable/disable) which always seems to have some problem.  If you can use 
>> AHCI mode, it will be *much* better.
> 
> OK. How do I get it in ahci mode? I see that both the ata_piix and achi
> drivers are loaded. This is what is loaded:

Plain ICH7 doesn't support ahci. ICH7R supports ahci mode and usually 
configurable in the BIOS menu.  On my board (P5LD2), it's in the first 
page (the left-most one where the clock setting is and hard disks are 
enumerated), it's called IDE configuration or something.

>> If you think the driver doesn't do the right thing(tm), please send me 
>> detailed info.  I'll try to fix the problem if possible or explain why 
>> it can't be fixed at the very least.
> 
> I bet the driver does the right thing. The trick is knowing what that is
> supposed to be. And how to use the various commands on files in /sys at
> the correct time and in the correct order.

Really, it's not that complicated.

-- 
tejun

  reply	other threads:[~2006-08-01 18:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 15:18 libata question Roger Oberholtzer
2006-08-01 15:33 ` Tejun Heo
2006-08-01 18:39   ` Roger Oberholtzer
2006-08-01 18:45     ` Tejun Heo [this message]
2006-08-01 19:03       ` Roger Oberholtzer
2006-08-01 19:06         ` Tejun Heo
2006-08-02  7:05           ` Roger Oberholtzer
2006-08-02  7:20             ` Tejun Heo
2006-08-02  8:06               ` Roger Oberholtzer
2006-08-02 14:35               ` Roger Oberholtzer
2006-08-02 15:02                 ` Tejun Heo
2006-08-03  7:26                   ` Roger Oberholtzer
2006-08-03  7:58                     ` Tejun Heo
2006-08-03  8:49                       ` Roger Oberholtzer
2006-08-03 20:08                         ` Stefan Smietanowski
2006-08-02  1:22 ` 31244 PCI Card sam song

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=44CFA15C.8080109@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=roger@opq.se \
    /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).