On Fri, Sep 9, 2011 at 8:47 PM, roberth <rob...@openbsd.pap.st> wrote:
> On Fri, 09 Sep 2011 17:16:36 +0100
> Matej D=ach <matej.l...@gmail.com> wrote:
>
>> Intel HD Graphics (HM55 chipset) - including GPU acceleration (at
>> least 2D).
>
> It is being worked on. Atm from what i have read, even the vesa driver
> doesn't work that good.
>
> Owain has posted a diff for this on tech@ recently. (search for
> "sandybride").
> But there is more work to do, like pulling in the Xorg bits.
I have
$ sysctl kern.version
kern.version=OpenBSD 5.0-current (GENERIC.MP) #63: Thu Sep 8 12:10:28 MDT 2011
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
$
and before that my Sandybridge Intel GT2+ was able to do only around
7fps and work was somewhat slower in X, sound was stuttered and I was
not able to watch eg. movies with mplayer -vo x11, list of huge number
of files in directory was slow, vga was marked as not configured in
dmesg and so on. Except of that work was fine. Now every problem which
I've had before is gone and I have around 23fps, X is not sluggish,
sound is ok, movies are ok in mplayer, html5 movies runs and so on.
Yes, it's initial change (still KMS needed), but it's ok in 2D for me
and thx again to all devs for their superb job.
$ dmesg | grep -i vga
vga1 at pci0 dev 2 function 0 "Intel GT2+ Video" rev 0x09
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
intagp0 at vga1
inteldrm0 at vga1: apic 2 int 16
$
$ sudo pcidump -v 0:2:0
0:2:0: Intel GT2+ Video
0x0000: Vendor ID: 8086 Product ID: 0126
0x0004: Command: 0007 Status ID: 0090
0x0008: Class: 03 Subclass: 00 Interface: 00 Revision: 09
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR mem 64bit addr: 0x00000000e1400000/0x00400000
0x0018: BAR mem prefetchable 64bit addr: 0x00000000d0000000/0x10000000
0x0020: BAR io addr: 0x00004000/0x0040
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 1028 Product ID: 0492
0x0030: Expansion ROM Base Address: 00000000
0x0038: 00000000
0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
0x0090: Capability 0x05: Message Signaled Interrupts (MSI)
0x00d0: Capability 0x01: Power Management
0x00a4: Capability 0x13: PCI Advanced Features
$
$ glxinfo | grep -i render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_fragment_program,
$
$ grep -i intel /var/log/Xorg.0.log
[1368685.875] Identifier "Builtin Default intel Device 0"
[1368685.875] Driver "intel"
[1368685.875] Identifier "Builtin Default intel Screen 0"
[1368685.875] Device "Builtin Default intel Device 0"
[1368685.875] Screen "Builtin Default intel Screen 0"
[1368685.884] (**) |-->Screen "Builtin Default intel Screen 0" (0)
[1368685.885] (**) | |-->Device "Builtin Default intel Device 0"
[1368685.885] (==) No monitor specified for screen "Builtin Default
intel Screen 0".
[1368686.126] (II) LoadModule: "intel"
[1368686.127] (II) Loading /usr/X11R6/lib/modules/drivers/intel_drv.so
[1368686.148] (II) Module intel: vendor="X.Org Foundation"
[1368686.184] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
[1368686.248] (II) VESA(0): VESA VBE OEM: Intel(R)Sandybridge Mobile
Graphics Chipset Accelerated VGA BIOS
[1368686.248] (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
[1368686.248] (II) VESA(0): VESA VBE OEM Product: Intel(R)Sandybridge
Mobile Graphics Controller
[1368686.377] (II) UnloadModule: "intel"
[1368686.377] (II) Unloading /usr/X11R6/lib/modules/drivers/intel_drv.so
[1368686.383] (II) VESA(0): VESA VBE OEM: Intel(R)Sandybridge Mobile
Graphics Chipset Accelerated VGA BIOS
[1368686.383] (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
[1368686.383] (II) VESA(0): VESA VBE OEM Product: Intel(R)Sandybridge
Mobile Graphics Controller
$
>
> I'd say dualboot for now, see what works and help yourself by testing
> the offered patches.
