From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 111151] [pata_amd][pata_acpi] Internal base address register error prevents initialization of PATA drive
Date: Fri, 22 Jan 2016 20:57:09 +0000 [thread overview]
Message-ID: <bug-111151-11633-mRlI54EmX2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-111151-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=111151
Alan <alan@lxorguk.ukuu.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alan@lxorguk.ukuu.org.uk
--- Comment #1 from Alan <alan@lxorguk.ukuu.org.uk> ---
You say "sata|ide interface: based on Marvell 88i8030 controller chip"
The 88i8030 is a PATA/SATA bridge, it's not a controller chip. It's an ancient
lump of glue for nailing a SATA driver to a PATA port.
[1.916367] pata_amd 0000:00:09.0: version 0.4.1
[1.916383] pata_amd 0000:00:09.0: can't enable device: BAR 0 [io size 0x0008]
not assigned
[1.916453] pata_amd: probe of 0000:00:09.0 failed with error -22
[2.509228] pata_acpi 0000:00:09.0: can't enable device: BAR 0 [io size 0x0008]
not assigned
[2.509299] pata_acpi: probe of 0000:00:09.0 failed with error -22
So the BIOS hasn't configured the controller by the look of it. That or it is
disabled in the NVRAM settings.
It tried pata_amd, that failed it tried pata_acpi that failed for the same
reason.
The Ultra-AL is known to work so that suggests to me there's perhaps some kind
of setting error on your board.
Might be useful if you could do an lspci -vvxxx with the box booting something
like a live USB installation, and then attach it. That would at least allow
folks to see how the firmware has left the setup.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-01-22 20:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 19:55 [Bug 111151] New: [pata_amd][pata_acpi] Internal base address register error prevents initialization of PATA drive bugzilla-daemon
2016-01-22 20:57 ` bugzilla-daemon [this message]
2016-01-23 1:17 ` [Bug 111151] " bugzilla-daemon
2016-01-23 1:38 ` bugzilla-daemon
2016-01-23 11:43 ` bugzilla-daemon
2016-01-23 12:15 ` bugzilla-daemon
2016-01-23 17:09 ` bugzilla-daemon
2016-01-23 18:58 ` bugzilla-daemon
2016-01-23 21:09 ` bugzilla-daemon
2016-01-23 21:13 ` bugzilla-daemon
2016-01-23 23:09 ` bugzilla-daemon
2016-01-23 23:29 ` bugzilla-daemon
2016-02-04 22:43 ` bugzilla-daemon
2016-02-04 22:44 ` bugzilla-daemon
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=bug-111151-11633-mRlI54EmX2@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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).