From: Wolfgang Denk <wd@denx.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: PCIe x4 cards not detected on Z370 mainboards
Date: Mon, 26 Mar 2018 17:09:27 +0200 [thread overview]
Message-ID: <20180326150927.9BFA72476FF@gemini.denx.de> (raw)
In-Reply-To: <20180326135107.GH210003@bhelgaas-glaptop.roam.corp.google.com>
Dear Bjorn,
In message <20180326135107.GH210003@bhelgaas-glaptop.roam.corp.google.com> you wrote:
>
> I guess you've already talked to MSI support, who told you:
>
> These are old controllers which don't support UEFI/GOP. this
> is the reason they don't work. Cards which have only legacy
> support cannot be operated in modern mainboards.
>
> That seems like sort of a lame excuse as a consumer, but if the BIOS
> writers decided they don't want to support older adapters, I don't
> know what we can really do about it.
What makes me wonder is why the Adaptec card behaves different here
- it is as old as the LSI controllers and certainly has no UEFI
compatible BIOS either.
> I searched for other reports ("GIGABYTE Z370-HD3 not detected") and
> found several that could be similar. One suggested enabling/disabling
I've seen these, too. Those that looked reliable were mostly about
graphics cards, though, and recent ones as well.
> CSM (UEFI compatibility support module) in the BIOS setup. If these
> BIOSes in fact decided not to support these old cards, my guess is
> there is no CSM in them, but it's worth checking.
At least it is not mentioned in the documentation, and I cannot find
any settings in the BIOS where I could switch off UEFI.
> Otherwise, I think I'm out of ideas. I don't think we've seen
> anything yet that indicates a Linux issue, although maybe Mika will
> come up with something from the acpidumps.
Agreed. Any information I could use for communication with the
motherboard vendors would be helpful.
What I cannot understand is why I am apparently one of the first
ones to run into such an issue? OK, SAS controllers is more server
stuff, and server mainboards are apparently more conservative in
their settings. But still...
Thanks!
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Copy from one, it's plagiarism; copy from two, it's research.
next prev parent reply other threads:[~2018-03-26 15:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 18:48 PCIe x4 cards not detected on Z370 mainboards Wolfgang Denk
2018-03-22 19:27 ` Bjorn Helgaas
2018-03-23 8:48 ` Wolfgang Denk
2018-03-24 4:47 ` Bjorn Helgaas
2018-03-24 20:15 ` Wolfgang Denk
2018-03-26 13:51 ` Bjorn Helgaas
2018-03-26 13:52 ` Bjorn Helgaas
2018-03-26 15:12 ` Wolfgang Denk
2018-03-26 19:09 ` Bjorn Helgaas
2018-03-27 13:46 ` Wolfgang Denk
2018-03-26 15:09 ` Wolfgang Denk [this message]
2018-03-25 12:28 ` Wolfgang Denk
2018-03-26 11:26 ` Mika Westerberg
2018-03-26 15:00 ` Wolfgang Denk
2018-03-26 15:59 ` Mika Westerberg
2018-03-27 16:05 ` Wolfgang Denk
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=20180326150927.9BFA72476FF@gemini.denx.de \
--to=wd@denx.de \
--cc=helgaas@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
/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).