Loading DRM kills computer
Farias Martinez
aaronfarias at att.net
Mon May 6 17:21:00 UTC 2019
I’m using current on both of my laptop one with the module i915kms and the other laptop uses radeonkms both work fine without a problem on my laptop. Which module are you having issues with.
Sent from my iPhone
> On May 6, 2019, at 11:32 AM, Hans Petter Selasky <hps at selasky.org> wrote:
>
>> On 2019-05-06 16:41, Thomas Laus wrote:
>> List
>> I have a graphics issue since about CURRENT r346025. Kernel loading DRM
>> kills 2 different computers. My i5 Skylake works, but my Atom D510
>> desktop and laptop Core2-duo both have this common issue. When the DRM
>> kernel module is loaded, I get a 'black screen' on the console and am
>> not able to login via ssh to shutdown the PC. If I comment out the
>> kldload DRM statement in rc.conf a boot is possible. I get the same
>> result 'black screen of death' when starting X without DRM being loaded.
>> I am reporting this a little late because of another issue. I am
>> working with some committers on a gptzfsboot problem and thought that
>> this DRM issue would have been discovered and fixed by someone else in
>> the last few weeks. I updated to CURRENT r347183 this morning and
>> updated all of my packages and ports at the same time.
>
> Did you build DRM from source? If no, then try that first.
>
> > This problem is
>> still present. I don't know how to isolate this issue. Is it a
>> framebuffer problem in the kernels after r346025, Current-DRM-kmod, or
>> the Intel driver "xf86-video-intel-2.99.917.20181203".
>
> --HPS
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current
mailing list