Date: Mon, 29 May 2023 06:10:52 +0200 From: Ralf Mardorf <ralf-mardorf@riseup.net> To: questions@freebsd.org Subject: Re: Caught signal 6 (Abort trap). Server aborting Message-ID: <c5634e71ac749dba67db7198481d701036fa99e1.camel@riseup.net> In-Reply-To: <SEZPR01MB45525DCABBBE8276DB6138A3C54A9@SEZPR01MB4552.apcprd01.prod.exchangelabs.com> References: <SEZPR01MB45525DCABBBE8276DB6138A3C54A9@SEZPR01MB4552.apcprd01.prod.exchangelabs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2023-05-29 at 11:20 +0800, hlyg wrote: > [=C2=A0=C2=A0=C2=A0 90.740] (WW) Warning, couldn't open module intel > [=C2=A0=C2=A0=C2=A0 90.740] (EE) Failed to load module "intel" (module do= es not exist, 0) > [=C2=A0=C2=A0=C2=A0 90.740] (II) LoadModule: "modesetting" Hi, Intel doesn't maintain the FLOSS drivers anymore. My apologies, but I can only comment on Linux. However, it's unlikely much different for FreeBSD. For an old Intel chip I use an old long term Linux kernel with the Intel driver, but for my latest Intel core 13. generation I'm using the modesetting driver. This workaround alone still doesn't work. In addition I need to set the kernel option ibt=3Doff. FreeBSD might come with a similar pitfall. Intel chips >=3D 11. generation provide this hardware security measure. NVIDIA and Intel GPUs are known to cause problems, if this hardware feature is enabled by Linux kernels. Since you are using the modesetting driver, too, your FreeBSD kernel might cause the same or a similar issue. Regards, Ralf
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c5634e71ac749dba67db7198481d701036fa99e1.camel>