From: Steven Newbury <steve@snewbury.org.uk>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: Help to enable Iris Pro on Retina MBP 11.3
Date: Wed, 08 Jan 2014 13:46:11 +0000 [thread overview]
Message-ID: <1389188771.25695.24.camel@artifact> (raw)
In-Reply-To: <87zjn6bzwc.fsf@intel.com>
On Wed, 2014-01-08 at 11:12 +0200, Jani Nikula wrote:
> On Tue, 07 Jan 2014, "Lu, Ran" <hephooey@gmail.com> wrote:
> > Hi Jani,
> >
> > As a matter of fact, I tried kernel from 3.9 to 3.13-rc6, all of them cannot
> > read the pci information from 0:2.0, and lspci do not have Iris Pro as a video
> > controller. I put in the attachment dmesg output from 3.12.6, I added some
> > printk to show the results from pci_bus_read_dev_vendor_id, otherwise it is a
> > vanilla kernel. I do not think I get any extra information by adding
> > drm.debug=0xe because the pci device is never registered properly, but it was
> > there anyway.The weird thing is grub can read pci device fine, I took a picture
> > since I do not know how to save outputs in grub console. I did some test with
> > another laptop with a working HD 4600. It seems even if I use setpci -s 0:2.0
> > 4.b=0 to disable the device, it is still responsive to further setpci and I
> > can bring it back by setting 4.b=7. Now it does not look like the video card
> > is disable. I guess maybe something wrong in the ACPI table triggered the
> > kernel to read the wrong place. But still strange it only missed that
> > particular bus. In case you are interested, I also put the dsdt table in the
> > attachment, I can provide other tables if they are important.
>
> I don't have much clues here. Are there any bios settings you could
> tweak? Did you try without the nvidia driver loaded?
>
> BR,
> Jani.
>
>
Might it be unable to allocate enough PCI address or it gets allocated
above 4G? There are patches queued up for pci-next (plus a few in my
tree for i915; I need to get back to these) to get PCI address space
above 4G working. Probably unrelated...
prev parent reply other threads:[~2014-01-08 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 23:20 Help to enable Iris Pro on Retina MBP 11.3 Lu, Ran
2014-01-07 8:02 ` Jani Nikula
2014-01-07 21:14 ` Lu, Ran
2014-01-08 9:12 ` Jani Nikula
2014-01-08 9:18 ` Dave Airlie
2014-01-08 14:53 ` Lu, Ran
2014-01-08 13:46 ` Steven Newbury [this message]
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=1389188771.25695.24.camel@artifact \
--to=steve@snewbury.org.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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