Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Latest i386 DRMKMS results



On Sat, Apr 26, 2014 at 12:30:22AM -0500, John D. Baker wrote:
> With the recent updates to DRMKMS stuff, I set about seeing if the
> situation was improved from before on my DELL OptiPlex GX-260.

For me, things improved on amd64 (haven't tried i386) today with

P sys/external/bsd/drm2/dist/drm/i915/intel_bios.c
P sys/external/bsd/drm2/include/linux/dmi.h
P sys/external/bsd/drm2/include/linux/init.h
P sys/external/bsd/drm2/linux/files.drmkms_linux
U sys/external/bsd/drm2/linux/linux_dmi.c

for the first time my Ivy Bridge laptop and Sandy Bridge laptop booted
into a usable state! (failed last night without those patches)

i915drmkms0 at pci0 dev 2 function 0: Intel Sandy Bridge Integrated Graphics 
Device (rev. 0x09)
drmkms0 at i915drmkms0
drm: Memory usable by graphics device = 2048M
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.
drm: GMBUS [i915 gmbus panel] timed out, falling back to bit banging on pin 3
drmkms0: interrupting at ioapic0 pin 16 (i915)    
i915drmkms0: framebuffer at 0xffff8000469f8000, size 1366x768, depth 32, stride 
5504
wsdisplay0 at i915drmkms0 kbdmux 1: console (default, vt100 emulation), using 
wskbd0
wsmux1: connecting to wsdisplay0
drmkms0: info: registered panic notifier 

Ivy Bridge:
i915drmkms0 at pci0 dev 2 function 0: vendor 0x8086 product 0x0162 (rev. 0x09)
drmkms0 at i915drmkms0
drm: Memory usable by graphics device = 2048M
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.
drmkms0: interrupting at ioapic0 pin 16 (i915)
i915drmkms0: framebuffer at 0xffff80008aaf3000, size 1280x1024, depth 32, 
stride 5120
wsdisplay0 at i915drmkms0 kbdmux 1: console (default, vt100 emulation), using 
wskbd0
wsmux1: connecting to wsdisplay0
drmkms0: info: registered panic notifier

Attempting X, old VESA xorg.conf works, though vertical offset is strange.

Attempting intel driver gets a black screen. At least the system is
responsive though!

[   499.214] (--) intel(0): Output LVDS1 using initial mode 1366x768 on pipe 0
[   499.214] (==) intel(0): DPI set to (96, 96)
[   499.214] (II) Loading sub module "dri2"
[   499.214] (II) LoadModule: "dri2"
[   499.218] (II) Loading /usr/X11R7/lib/modules/extensions/libdri2.so
[   499.218] (II) Module dri2: vendor="X.Org Foundation"
[   499.218]    compiled for 1.10.6, module version = 1.2.0
[   499.219]    ABI class: X.Org Server Extension, version 5.0
[   499.219] (==) Depth 24 pixmap format is 32 bpp
[   499.241] (II) intel(0): SNA initialized with Sandybridge (gen6, gt2) backend
[   499.241] (==) intel(0): Backing store disabled
[   499.241] (==) intel(0): Silken mouse enabled
[   499.244] (II) intel(0): HW Cursor enabled
[   499.244] (II) intel(0): RandR 1.2 enabled, ignore the following RandR 
disabled message.
[   499.245] (==) intel(0): DPMS enabled
[   499.257] (II) intel(0): [DRI2] Setup complete
[   499.257] (II) intel(0): [DRI2]   DRI driver: i965
[   499.257] (II) intel(0): direct rendering: DRI2 Enabled
...
[   499.379] (II) GLX: Initialized DRI2 GL provider for screen 0
[   499.384] (II) intel(0): switch to mode 1366x768@60.2 on pipe 0 using LVDS1, 
position (0, 0), rotation normal
[   499.406] (II) intel(0): Setting screen physical size to 361 x 203

so looks promising... (This is native xorg, -current/amd64)

Cheers,

Patrick


Home | Main Index | Thread Index | Old Index