On Sat, Nov 21, 2015 at 04:27:34PM +0100, Mark Kettenis wrote:
> Hi Ossi,
>
> Your digging:
>
> > I went digging what produces the error
> >
> > error: [drm:pid0:inteldrm_attach] *ERROR* failed to init modeset
> >
>
> Helped quite a bit. I'm fairly certain the diff I just committed will fix
On Sat, Nov 21, 2015 at 04:27:34PM +0100, Mark Kettenis wrote:
> Hi Ossi,
>
> Your digging:
>
> > I went digging what produces the error
> >
> > error: [drm:pid0:inteldrm_attach] *ERROR* failed to init modeset
> >
> > and it looks like in sys/dev/pci/drm/drm_irq.c:1.66
> >
> >
Hi Ossi,
Your digging:
> I went digging what produces the error
>
> error: [drm:pid0:inteldrm_attach] *ERROR* failed to init modeset
>
> and it looks like in sys/dev/pci/drm/drm_irq.c:1.66
>
> drm_irq_install() calls
>
> if (drm_dev_to_irq(dev) == 0)
> return -EINVAL;
>
Thanks so much for that commit. The system boots up and has a very brief
moment of display corruption before it switches to inteldrm(4) and works
perfectly. This works on both my 2013 MacBook Air (Haswell HD 5000
graphics)) and 2015 MacBook Air (Broadwell HD 6000 graphics). I haven't
had a chance
I just tested a 2015 MacBook Air (HD 6000 graphics) and still see the
same display corruption. This seems to happen on all Intel Graphics Macs
at least from HD 4000 and up and specifically your system, the 12-inch
Retina MacBook, 2013 MacBook Air, and 2015 MacBook Air. Hopefully
kettenis@ will
Hi misc@,
Same issue what's described by Bryan Vyhmeister in
https://marc.info/?l=openbsd-misc=144614435718519
https://marc.info/?l=openbsd-misc=144622297912025
but with MacBookPro9,2 and Intel HD 4000 graphics (MacBook Pro
(13-inch, Mid 2012)). Snapshot and sources from mirror from today.
6 matches
Mail list logo
