Re: i386 DRMKMS results, 28 Jun 2014

[Stephan <stephanwib%googlemail.com@localhost>]

Hi all,

is that DRMKMS stuff enabled in the daily builds or is it neccessery
to build a custom kernel?


Regards,

Stephan

2014-06-29 1:47 GMT+02:00 David H. Gutteridge 
<dhgutteridge%sympatico.ca@localhost>:
> Hi all,
>
> Following an earlier report today of success with DRMKMS on amd64,
> I've just tested on i386 and can confirm it works for me. I haven't
> tried anything too demanding, but I'm able to boot, the console
> works, I'm able to switch VTs, and have run various applications in
> a Blackbox WM session without issue. dmesg excerpt is below. (The
> graphics chipset is an Intel 945GM.)
>
> Regards,
>
> Dave
>
> agp0 at pchb0: i915-family chipset
> agp0: detected 7932k stolen memory
> agp0: aperture at 0xc0000000, size 0x10000000
> i915drmkms0 at pci0 dev 2 function 0
> : vendor 0x8086 product 0x27ae (rev. 0x03)
> drmkms0 at i915drmkms0
> drm: Memory usable by graphics device = 256M
> drm: MTRR allocation failed.  Graphics performance may suffer.
> drm: Supports vblank timestamp caching Rev 1 (10.10.2010).
> drm: Driver supports precise vblank timestamp query.
> i915drmkms0: unable to map ROM
> drm: failed to find VBIOS tables
> drm kern warning: composite sync not supported
> drm: initialized overlay support
> drmkms0: interrupting at ioapic0 pin 16 (i915)
> drm kern warning: composite sync not supported
> i915drmkms0: framebuffer at 0xd9ecd000, size 1024x600, depth 32, stride 4096
> wsdisplay0 at i915drmkms0 kbdmux 1: console (default, vt100 emulation), using 
> wskbd0
> wsmux1: connecting to wsdisplay0
> fixme: max PWM is zero
> drmkms0: info: registered panic notifier
>