<div dir="auto">Hi thanks for the tips, 12.0 current from the svn head and drm-next-kmod from ports didnt load up when vt initialized on boot. Im currently looking at the vesa kmod, getting this error that im trying to work out.<div dir="auto"><br></div><div dir="auto">$ kldload vesa</div><div dir="auto">module_register_init: MOD_LOAD (vesa, 0x< f and numbers>, 0) error 19</div><div dir="auto">sysctl_unregister_oid: failed to unregister sysctl</div><div dir="auto"><br></div><div dir="auto">~fire</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Oct 19, 2017 11:11 AM, "Pete Wright" <<a href="mailto:pete@nomadlogic.org">pete@nomadlogic.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 10/18/2017 19:42, fire crow wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Pete/Talk,<br>
i'm having a kernel panic when trying to run the latest<br>
freebsd-base-graphics branch. wondering if anyone else has seen this<br>
issue or how i can report it/who i can debug it with.<br>
<br>
here are the steps i have taken<br>
<br>
$ git clone <a href="https://github.com/FreeBSDDesktop/freebsd-base-graphics" rel="noreferrer" target="_blank">https://github.com/FreeBSDDesk<wbr>top/freebsd-base-graphics</a><br>
$ git checkout drm-next<br>
$ mv /usr/src /usr/src.current<br>
$ mkdir /usr/src<br>
$ cp freebsd-base-graphics/* /usr/src<br>
$ cd /usr/src<br>
$ make -j2 buildworld<br>
$ make -j2 kernel<br>
$ shutdown -r now<br>
then i arrive in the kernel panic ( screenshot attached)<br>
<br>
here is what pciconf says about my graphics card<br>
$ pciconf -lv | grep -A 2 vgapci<br>
vgapci0@pci0:0:2:0Â class=0x030000 card=0x390517aa chip=0x22b18086<br>
rev=0x35 hdr=0x0<br>
vender = 'Intel Corporation'<br>
device = 'Atom/Celeron/PEndium Processor x5-E8000/J3xxx/N3xxx<br>
Integrated Graphics Controller'<br>
<br>
and here is my /boot/loader.conf<br>
if_iwm_load="YES"<br>
iwm3160fw_load="YES"<br>
i915kms_load="YES"<br>
hw.vga.textmode=1<br>
kern.vt.fb.default_mode="1336x<wbr>768"<br>
<br>
all suggestions welcome<br>
~fire<br>
</blockquote>
<br>
hrm, i don't think this Atom chipset uses Intel HD Graphics (aka i915 GPU's). having said that i'm surprised it results in a panic. one thing you can try is to build/install a stock 12-CURRENT world and kernel on your system, then install the drm-next-kmod port/pkg:<br>
<br>
$ pkg info|grep drm-next<br>
drm-next-kmod-g20170918Â Â Â Â Â Â Â DRM modules for the linuxkpi-based KMS components<br>
$<br>
<br>
this is what i'm running now since the drm-next devs have merged their code upstream, so no need to run code off of the drm-next github branch anymore! it's possible there is some instability in that repo right now as i think they are updating things for linux-4.10 compatibility - so give the port/pkg a shot and see if that helps.<br>
<br>
-pete<br>
<br>
<br>
-- <br>
Pete Wright<br>
<a href="mailto:pete@nomadlogic.org" target="_blank">pete@nomadlogic.org</a><br>
@nomadlogicLA<br>
<br>
</blockquote></div></div>