Date: Mon, 23 Sep 2019 15:52:11 -0400 From: Thomas Laus <lausts@acm.org> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: Booting anything after r352057 kills console Message-ID: <11db909b-57ee-b452-6a17-90ec2765c36e@acm.org>
next in thread | raw e-mail | index | archive | help
I updated my source today and when the computer was booted, the screen turned black at the point that the drm related kernel modules would normally load. Suspecting a drm issue, I commented out the rc.conf line that loads those kernel modules. This did not fix my problem. My last good kernel was r352057. I started to bi-sect the svn updates between today and r352057. Going backward, all the way to r352064 is not working. There were very few changes between r352057 and r352064. None of them seem to be console graphics related. The last entry in my boot log shows a successful entry of the security policy for ntp. No logged messages after this point. Where do I go from here? The computer is an Intel i5 Skylake with onboard graphics. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11db909b-57ee-b452-6a17-90ec2765c36e>