[Intel-gfx] i915 module does not find 82865G if configured as secondary
airlied at gmail.com
Tue Oct 11 01:25:24 PDT 2011
On Mon, Oct 10, 2011 at 9:53 PM, Chris Wilson <chris at chris-wilson.co.uk> wrote:
> On Mon, 10 Oct 2011 22:32:38 +0200, Tempura San <tempura.san at gmail.com> wrote:
> Non-text part: multipart/mixed
>> This would be great, but...
>> I have just tested the patches and it really messes up the system.
>> On the first boot I got a shell and was able to to a dmesg:
>> [ 46.775935] [drm] Initialized drm 1.1.0 20060810
>> [ 46.926398] i915 0000:00:02.0: enabling device (0000 -> 0003)
>> [ 46.926412] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>> [ 46.926422] i915 0000:00:02.0: setting latency timer to 64
>> [ 46.932858] [drm] set up 31M of stolen space
>> [ 46.933087] i915 0000:00:02.0: BAR 6: can't allocate resource (bogus
>> alignment) [0x0-0x0] flags 0x0
>> [ 46.933093] [drm] failed to find VBIOS tables
>> [ 46.978294] [drm] initialized overlay support
>> [ 47.308831] Console: switching to colour frame buffer device 160x64
>> [ 47.308849] fb0: inteldrmfb frame buffer device
>> [ 47.308853] registered panic notifier
>> [ 47.308868] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on
>> minor 0
>> [ 47.323940] vgaarb: this pci device is not a vga device
>> [ 47.355806] render error detected, EIR: 0x00000010
>> [ 47.355815] [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010,
>> [ 47.355835] render error detected, EIR: 0x00000010
> A page table error upon initialisation. It would seem like we depend
> upon the BIOS leaving the registers in a sane state, which is less
> likely in this situation since the BIOS was not using the card at all.
> We've certainly got better over time in this regard and the latest kernel
> is much more likely to succeed...
> However, I doubt that it is perfect, and your feedback would be most
There's a good chance that the hw just isn't initialised properly, there may
not even be stolen RAM in the GTT.
More information about the Intel-gfx