Date: Fri, 7 May 2021 21:45:45 -0400 (EDT) From: Chris Hill <chris@monochrome.org> To: Graham Perrin <grahamperrin@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: i915kms kernel module causing freezes on FreeBSD 13.0-RELEASE Message-ID: <alpine.BSF.2.20.2105072136430.96788@tripel.monochrome.org> In-Reply-To: <68023ace-7338-5e39-28f9-22bf1ff78365@gmail.com> References: <CA%2B4jMao_YgwF_Jn8CG8ucU0c7AgnmoBknMtPEhPet0XcJJrr9A@mail.gmail.com> <68023ace-7338-5e39-28f9-22bf1ff78365@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 8 May 2021, Graham Perrin wrote: > On 07/05/2021 19:09, Matt K wrote: >> - These are the possibilities to have a stable usable system with X: >> 1. not mentioning i915kms in rc.conf is a must. Then I can load X with XDM >> and it automatically pulls i915kms by specifying "Driver" "intel" in >> xorg.conf. >> 2. not mentioning i915kms in rc.conf is a must. Then I have to "kldload >> i915kms" and then I can "startx" and it works. In this case It does not >> matter if I have "modesetting" or "intel" in xorg.conf, both work. > > Try a third approach: > > kld_list="drm" I had a similar problem with X appearing to hang. In my case, I had to specify the full path: $ grep kms /etc/rc.conf kld_list="/boot/modules/i915kms.ko" ...in order to load the i915kms from the port graphics/drm-fbsd12.0-kmod rather than the one from the kernel. Yes, I had to build the port, not just install the pkg. Caveat: Matt just upgraded to 13.0; I'm still on 12.2-RELEASE-p4 on account of sloth. I'm guessing Matt probably needs graphics/drm-fbsd13-kmod. -- Chris Hill chris@monochrome.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.2105072136430.96788>