From: Mark Lord <lkml@rtr.ca>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Mike Mohr <akihana@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: expresscard hotplug not working
Date: Mon, 31 Aug 2009 08:45:47 -0400 [thread overview]
Message-ID: <4A9BC5FB.20000@rtr.ca> (raw)
In-Reply-To: <4A9BC239.9060009@rtr.ca>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
Mark Lord wrote:
> Matthew Garrett wrote:
>> On Thu, Aug 27, 2009 at 08:52:45AM -0400, Mark Lord wrote:
>>
>>> Just create a file called /etc/modprobe.d/pciehp,
>>> and stick this one line into it:
>>>
>>> options pciehp pciehp_force=1
>>>
>>> See if that works.
>>
>> It's worth noting that Windows didn't support native pcie hotplug
>> until Vista, and so any hardware that works with XP (ie, basically all
>> of it, including Dells) is supposed to be using acpi hotplug instead.
>> I've fixed one bug that led to acpiphp not working on some hardware,
>> but if anyone's still running with pciehp_force=1 then please send me
>> the output of acpidump so it can be fixed properly.
> ..
>
> My Dell works fine with PCIe hotplug under XP,
> but not under Linux without pciehp_force=1.
>
> I have not retested without that parameter for quite some time, though.
> What do I have to do to retest with "acpihp" ?
..
Okay, I figured it out. Not very difficult, either. :)
With acpiphp loaded, hotplug works on the ExpressCard slot
of my Dell i9400 notebook. Well, it *mostly* works.
The part that is still b0rked is that inserted cards get
"forgotten" about over suspend/resume (RAM) cycles.
With pciehp + pciehp_force=1, everything works properly,
including keeping devices around over suspend/resume.
I am attaching the output of "acpidump -b | gzip" to this message.
Cheers
[-- Attachment #2: acpidump.out.gz --]
[-- Type: application/x-gzip, Size: 8851 bytes --]
next prev parent reply other threads:[~2009-08-31 12:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 1:17 expresscard hotplug not working Mike Mohr
2009-08-26 6:45 ` Greg KH
2009-08-26 18:19 ` Mike Mohr
2009-08-26 21:02 ` Greg KH
2009-08-27 12:52 ` Mark Lord
2009-08-27 13:18 ` Mark Lord
2009-08-30 22:55 ` Matthew Garrett
2009-08-31 12:29 ` Mark Lord
2009-08-31 12:45 ` Mark Lord [this message]
2009-08-31 12:56 ` Matthew Garrett
2009-08-31 13:11 ` Mark Lord
2009-08-31 13:15 ` Matthew Garrett
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=4A9BC5FB.20000@rtr.ca \
--to=lkml@rtr.ca \
--cc=akihana@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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