Date: Tue, 26 Feb 2019 14:23:01 +0100 From: Sid <sid@bsdmail.com> To: "Niclas Zeising" <zeising@freebsd.org> Cc: "Kevin Oberman" <rkoberman@gmail.com>, "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org> Subject: Re: drm-kmod startup error Message-ID: <trinity-5f2e0545-386d-45e0-a3a6-054341d9d570-1551187381144@3c-app-mailcom-lxa04> In-Reply-To: <8a211cbd-d453-3fc3-ea62-560e1673879f@freebsd.org> References: <trinity-cc3fba08-aae5-4472-9ebb-7b46a85eb95f-1550550148864@3c-app-mailcom-lxa13> <CAN6yY1vwLViUvLecp%2Bei3LjMgmoDB1KbqXOg2DMCh3ZFbPKevA@mail.gmail.com> <8a211cbd-d453-3fc3-ea62-560e1673879f@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Including VESA, SC or all video drivers in the KERNCONF for building a cus= tom kernel fixed it. drm-kmod was then built from ports. Before, I tried a cleanslate for both updated ports and packages. An older= ports version for these kernel modules didn't require VESA or SC KERNCONF= settings. Likely VESA. It's updated Releng, and as mentioned 11.2. That g= ave enough insight to fix this problem. Thanks. > Hi! > As Kevin says, it's very important to keep driver (drm-*-kmod) and > firmware (gpu-firmware-kmod) in sync with the kernel. If you are using > a release, and running GENERIC, it is enough to download the packages > with pkg and install them, but if you are using a custom kernel, or > running STABLE or CURRENT, then you need to compile the modules > yourself. The easiest way is usually to run `pkg delete > drm-fbsd11.2-kmod` and then `pkg autoremove` to remove any dependencies, > and then build graphics/drm-kmod from ports. This is safe to do even if > you are using pre-built packages for the rest of the system. > > Regards > -- > Niclas Zeising > FreeBSD Graphics Team > Sent: Tuesday, February 19, 2019 at 11:24 AM > From: "Niclas Zeising" > > On 2/19/19 6:41 AM, Kevin Oberman wrote: > > On Mon, Feb 18, 2019 at 8:36 PM Sid wrote: > > > >> I built and used from packages drm-fbsd11.2-kmod, and it had an error= on > >> startup. > >> > >> The errors are: > >> link_elf_obj: symbolic panic undefined > >> link_load_file: Unsupported file type > >> KLD drm.ko: depends on linuxkpi - not available or version mismatch > >> KLD drm.ko: depends on drmn - not available or version mismatch > >> linker_load_file: Unsupported file type > >> kldload: unexpected relocation type 4 > >> link_elf_obj: symbol uma_zalloc_arg undefined > >> linker_load_file: Unsupported file type > >> > >> kldload: unexpected relocation type 4 repeats many times. > >> > >> I just rebuilt world and kernel with linux and linx64 modules built f= or > >> FreeBSD 11.2. > >> > >> It is loaded from rc.conf, with kldlist=3D"amdgpu", others were tried= too, > >> "/boot/modules/radeonkms.ko radeonkms" > >> > >> I tried to unset syscons from loader.conf as I read from another thre= ad, > >> hw.syscons.disable=3D1. sc syscons and VESA are also not installed on= my > >> kernel. My console still loads without this, still with Radeon errors= . Xorg > >> is also not installed on my computer as I have this error for now. Al= l > >> ports and packes were removed, with a few reinstalled. It worked befo= re > >> upgrading to the changed name drm port. > >> > >> From the error messages, it looks like the latest drm ports or packa= ges > >> are mismatched with gpu-firmware-kmod or, at least, out of sync with = the > >> lin > >> > >> Thanks. > >> > > > > Are you running 11.2-RELEASE? A custom kerel config (not GENERIC)? The > > message looks like the kernel module is not in sync with your kernel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?trinity-5f2e0545-386d-45e0-a3a6-054341d9d570-1551187381144>