From owner-freebsd-current@freebsd.org Wed Apr 4 19:09:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9307F6E43E for ; Wed, 4 Apr 2018 19:09:10 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 708156E6C5; Wed, 4 Apr 2018 19:09:10 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w34J92Xk034371 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Apr 2018 12:09:02 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w34J9276034370; Wed, 4 Apr 2018 12:09:02 -0700 (PDT) (envelope-from sgk) Date: Wed, 4 Apr 2018 12:09:02 -0700 From: Steve Kargl To: Ed Maste Cc: FreeBSD Current Subject: Re: Can't load linux64.ko module Message-ID: <20180404190902.GA34292@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180403162600.GA23894@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Apr 2018 19:09:11 -0000 On Wed, Apr 04, 2018 at 02:41:35PM -0400, Ed Maste wrote: > On 3 April 2018 at 12:26, Steve Kargl wrote: > > Booting a kernel from > > % uname -a > > FreeBSD sleepdirt 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r331370: \ > > Thu Mar 22 13:41:30 AKDT 2018 \ > > kargl@sleepdirt:/usr/obj/usr/src/amd64.amd64/sys/SLEEPDIRT amd64 > > > > gives the following from dmesg > > > > % dmesg | grep linux > > link_elf_obj: symbol elf64_linux_vdso_fixup undefined > > linker_load_file: /boot/kernel/linux64.ko - unsupported file type > > Are you loading the linuxulator bits from modules or trying to compile > it into the kernel? Did your case work in the past but break recently? > > As a point of reference, my laptop is at r331538+0a541b719b64 (my WIP > branch), and loading linux.ko and linux64.ko is successful. kernel and world are from r331370. kernel config file contains options COMPAT_LINUX32 options COMPAT_LINUXKPI options LINPROCFS When booting, the kernel tries to load the module. A manual loading of the module results in % kldload /boot/kernel/linux64.ko kldload: an error occurred while loading module /boot/kernel/linux64.ko. Please check dmesg(8) for more details. sleepdirt:fvwm:root[203] dmesg | tail -2 link_elf_obj: symbol elf64_linux_vdso_fixup undefined linker_load_file: /boot/kernel/linux64.ko - unsupported file type Now, that I look at /sys/amd64/conf/NOTES again, I find that there is a COMPAT_LINUX as well as the COMPAT_LINUX32. I must have conflated that two options into being the same thing. I have to update the system for the recent security announcement, so I update everything and change my kernel config file. -- Steve