From owner-freebsd-x11@freebsd.org Thu Mar 8 04:52:15 2018 Return-Path: Delivered-To: freebsd-x11@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 1F350F31D82 for ; Thu, 8 Mar 2018 04:52:15 +0000 (UTC) (envelope-from tom.b.rushworth@gmail.com) Received: from mail-pl0-x233.google.com (mail-pl0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6BE684AAE; Thu, 8 Mar 2018 04:52:14 +0000 (UTC) (envelope-from tom.b.rushworth@gmail.com) Received: by mail-pl0-x233.google.com with SMTP id f23-v6so2728372plr.10; Wed, 07 Mar 2018 20:52:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=reply-to:subject:references:to:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=OuL+WWrBBMx0VqxHHiB9s+UVtkIzlgCwz2cytftlk78=; b=G0r1FFL8s0HSLtqpUCBxwAVCHgePbV8LpKxt3xWrHYYSHItRk06yZuW0ACcqZsoVZv 9Z0aHBaM1rMA+PTG0LDWHmLimHuMDysYSSqF5yoBYCdB2iTJWdV3U6DSOlDibG5u/Qk6 KdZpxWjbq6tcfFpuv/Jqb6Son07dYdZDiGDjSfCv6r4KCPz1cYHclxz4oVjlgEQ2gPzw M2bKK4AMQXwDM/z4iL0loFeoDHlM2Btf0Ujf/x7EurBhBrllhVTZDoSgzTjGVRdqTQDg +CL90gbp4xTqNMhQqudRlK4n8XeqWVpzt542Pox5zDyr03jVWNaTmluyz+Ts+0kisXx+ HU1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:references:to:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=OuL+WWrBBMx0VqxHHiB9s+UVtkIzlgCwz2cytftlk78=; b=tsVCMrFwxo89zJlveWrnMLzuEVft3/rbUgXqyhYE2gNKNVwYbQfVxg8w7jCCmmaFqh YlrU3H/0Ij/bxpGyyE6q7iuYHkjADydX+1b3UgamRStwo7XIC0HgF2peqwdCKWZA9X2Q muZbutFkqr0vimply6rd53P5ur+ak8kLrl68jGTlfAXqKHXL51Ll2DIuiZk6+R4BDiWU eCAKDaQ5yyRHoxGymJ+PgWmo/0Ra0LRMakLG9PgGnCcA2f4zAJUSfTGKDCDMvHFi/nSb 8GeAbYsqi8TNnOetYHlY0gETBtuJoBDPLKNfhP9bXgTVdyoe2MzAaFg7laruPV74Rqpr 5wMQ== X-Gm-Message-State: AElRT7GExmIAcBrj8PVOGnisB6WB+1cFyhbk6d/pLhCgEf2IloQk8r6j 648Aoffkel8Mof2qFLOCUnM= X-Google-Smtp-Source: AG47ELsNhyTFwPqDyipjdGKH0OR2AbX0hA7Z2W3gPRhU1GbYlyKytumRkb/q8IVUlXFzX9/eJuSQJQ== X-Received: by 2002:a17:902:8d90:: with SMTP id v16-v6mr15117842plo.168.1520484733627; Wed, 07 Mar 2018 20:52:13 -0800 (PST) Received: from kelvin.mannynkapy.net ([207.102.139.9]) by smtp.gmail.com with ESMTPSA id n13sm39826133pfg.45.2018.03.07.20.52.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Mar 2018 20:52:12 -0800 (PST) Reply-To: tbr@acm.org Subject: Re: kldxref error when installing drm-next-kmod from ports 11.1 References: To: Jung-uk Kim , tbr@acm.org, freebsd-x11@freebsd.org From: Tom Rushworth Message-ID: Date: Wed, 7 Mar 2018 20:52:08 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 04:52:15 -0000 Hi All, Sorry for the delay in replying, it's been a very long time since I used patch and I'm rusty :). On 07/03/2018 13:25, Jung-uk Kim wrote: > On 03/06/2018 22:39, Tom Rushworth wrote: >> Hi All, >> >> I'm running X11 with screen saver and the i915kms graphics driver and >> they seem to work, however I got the following messages when installing >> drm-next-kmod from /usr/ports: >> >> Installing drm-next-kmod-4.11.g20180224... >> kldxref: error while reading >> //boot/modules/i915_bxt_huc_ver01_07_1398_bin.ko: Bad address >> kldxref: error while reading >> //boot/modules/i915_kbl_huc_ver02_00_1810_bin.ko: Bad address >> kldxref: error while reading >> //boot/modules/i915_skl_huc_ver01_07_1398_bin.ko: Bad address >> >> and I get them again when I install other kernel module (e.g. virtualbox >> kmods). >> >> The machine in question is a Compulab Airtop, CPU (from boot in >> /bar/log/messages): >> >> CPU: Intel(R) Xeon(R) CPU E3-1285L v4 @ 3.40GHz (3392.22-MHz K8-class CPU) >> Mar 5 07:45:01 maxwell kernel: Origin="GenuineIntel" Id=0x40671 >> Family=0x6 Model=0x47 Stepping=1 >> >> and from Xorg.log.0: >> >> 9.042] (--) intel(0): Integrated Graphics Chipset: Intel(R) Iris Pro >> Graphics P6300 >> >> # uname -a >> FreeBSD maxwell.mannynkapy.net 11.1-STABLE FreeBSD 11.1-STABLE #0 >> r330126: Thu Mar 1 11:27:24 PST 2018 >> tbr@maxwell:/usr/obj/usr/src/sys/MAXWELL amd64 >> >> The machine has 32G of memory. I checked out the latest 11.1 STABLE >> kernel source, built a custom kernel from GENERIC by dropping the >> network devices not present and the old ATA disk stuff, then checked out >> the latest stable ports and did "make install" in >> /usr/ports/graphics/drm-next-kmod. >> >> As I said, it seems to be running reasonably well, can anyone tell me if >> I should worry about the error messages? >> >> I have the entire "make install" output saved via the "script" command >> if more details are needed. >> >> Thanks in advance for any info or pointers. > > It looks the module names are too long. Please try the attached patch. > Note you need to rebuild both graphics/drm-next-kmod and > graphics/gpu-firmware-kmod. > > Jung-uk Kim > I couldn't quite get "make install" to work but I installed by hand and things look good. "make install" gave the following message: ===> Registering installation for gpu-firmware-kmod-g20180206_1 pkg-static: Unable to access file /usr/ports/graphics/gpu-firmware-kmod/work/stage/boot/modules/i915_bxt_huc_ver01_07_1398_bin.ko:No such file or directory plus two more for the other long names. I used the "make install" to build and stage them, then copied in the modules by hand and removed the old ones. It all runs, the graphics look good, and I can run: xldxref -d /boot/modules without any erorrs. Thanks for the patch - in fact, thanks to all involved for all the work on the i915 driver! Regards, -- Tom Rushworth