Date: Sat, 8 May 2021 08:10:14 +0200 From: Matt K <kilikmatej@gmail.com> To: Chris Hill <chris@monochrome.org> Cc: Graham Perrin <grahamperrin@gmail.com>, freebsd-questions@freebsd.org Subject: Re: i915kms kernel module causing freezes on FreeBSD 13.0-RELEASE Message-ID: <CA%2B4jMaqH7-Z7YCtoxvHdeOwA_g=s1=wuw3RfsueUuiPeAk1kng@mail.gmail.com> In-Reply-To: <alpine.BSF.2.20.2105072136430.96788@tripel.monochrome.org> References: <CA%2B4jMao_YgwF_Jn8CG8ucU0c7AgnmoBknMtPEhPet0XcJJrr9A@mail.gmail.com> <68023ace-7338-5e39-28f9-22bf1ff78365@gmail.com> <alpine.BSF.2.20.2105072136430.96788@tripel.monochrome.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 8, 2021 at 1:08 AM Graham Perrin <grahamperrin@gmail.com> wrote: > > Try a third approach: > > kld_list="drm" > > This works. I will keep an eye on the system, logs, etc, and let you know what I find. Now everything seems to be working as advertised. With xf86-video-intel, even TearFree is working. Where is this behavior documented? How did you know about this solution? I think that this means that my problem is solved, but the question remains: why does i915kms cause freezes when loaded from rc.conf and works normally when loaded by hand? This is not handbook-documented behavior. Nor is it consistent or transparent. On Sat, May 8, 2021 at 3:46 AM Chris Hill <chris@monochrome.org> wrote: > > 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. > > This is no longer the case, Chris. i915kms got removed from base in FreeBSD 13, so only /boot/modules/i915kms.ko from ports remains and that's what gets loaded with kld_list="i915kms". I tried and checked with kldstat -h -v -n. -- MK On Sat, May 8, 2021 at 3:46 AM Chris Hill <chris@monochrome.org> wrote: > > 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 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > -- MK
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B4jMaqH7-Z7YCtoxvHdeOwA_g=s1=wuw3RfsueUuiPeAk1kng>