On Wed, 2014-01-08 at 11:12 +0200, Jani Nikula wrote:
> On Tue, 07 Jan 2014, "Lu, Ran" 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
> > control
On Wed, Jan 8, 2014 at 7:12 PM, Jani Nikula wrote:
> On Tue, 07 Jan 2014, "Lu, Ran" 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 t
On Tue, 07 Jan 2014, "Lu, Ran" 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
> pr
On Mon, 06 Jan 2014, "Lu, Ran" wrote:
> I just got a Retina MBP with Iris Pro and Nvidia GT 750. The iGPU works in
> OSX(Mavericks), but when I boot into Linux, the device was disabled. I
> debugged the kernel a little, apparently when pci_bus_read_dev_vendor_id is
> called for PCI 00:2.0 (the
Hi guys,
I just got a Retina MBP with Iris Pro and Nvidia GT 750. The iGPU works in
OSX(Mavericks), but when I boot into Linux, the device was disabled. I
debugged the kernel a little, apparently when pci_bus_read_dev_vendor_id is
called for PCI 00:2.0 (the intel gpu), it returns -1 which indic
