From: Luca Capello <luca-wlebWZzHoyE@public.gmane.org>
To: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [REGRESSION] 'pciehp' stops working since 2.6.10-rc2
Date: Tue, 28 Dec 2004 21:41:22 +0100 [thread overview]
Message-ID: <41D1C4F2.40204@pca.it> (raw)
In-Reply-To: <41D1BD66.9070704-Y6VGUYTwhu0@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
on 12/28/2004 09:09 PM, Nate Lawson wrote:
> It is extremely unlikely that your laptop supports PCI Express. I think
> Intel has only released server chipsets (Grantsdale) that support this.
I think the same, but in this case, why hotplug finds something and try
to load the modules pci_hotplug, shpchp and pciehp?
Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFB0cTyVAp7Xm10JmkRAuoGAJ48tjUSB+ouzmaJRKeRaRcWK5anpQCdGnWA
9+XH2fUKUDxVIWjQuDdFHOI=
=HoRa
-----END PGP SIGNATURE-----
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-28 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 1:23 [REGRESSION] 'pciehp' stops working since 2.6.10-rc2 Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD30575E0068B-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-12-28 13:51 ` Luca Capello
[not found] ` <41D164F4.9080407-wlebWZzHoyE@public.gmane.org>
2004-12-28 20:09 ` Nate Lawson
[not found] ` <41D1BD66.9070704-Y6VGUYTwhu0@public.gmane.org>
2004-12-28 20:41 ` Luca Capello [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-27 18:28 Luca Capello
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=41D1C4F2.40204@pca.it \
--to=luca-wlebwzzhoye@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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