From nobody Tue Feb 22 21:44:41 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B1A0E19D5B67 for ; Tue, 22 Feb 2022 21:44:54 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K3CPd4PPHz4tsT for ; Tue, 22 Feb 2022 21:44:53 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: by mail-il1-x135.google.com with SMTP id w4so2677095ilj.5 for ; Tue, 22 Feb 2022 13:44:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=QrGMtxmyNPlDj2bnXDwv+bwkylrJG7s0RwPjqEBnIK0=; b=e9Qfpcs4wvxcN5ZjtyJ7FI1N4/S/HRIpgjqO1s0RlbaI44Yot+QG5xSStfeLrRP2MH xSq5S225uTGgh6ZxkzKJ5fqjGeup3fJwlRmyw1v+3o8nJJ8hWFOUoMMq5S1rERa42KFE hZ8PEof6JQNa+oDYdAWtBkywegoDiuCRLv8LrxrhjHfBH4+/XKbaVB1nDge46H1DYA0f AZ8OA6w5lzBGyyhPNZAMK3GXMWGCWtQ5QpUF6YAeQlTJVNMJViFvQQ7Ogh7s07ou0VI0 2/QzUz0ssKjckdUq1n3QOZYhcNS3LR7yq4mzUdrvPeOu1r/s2tV7iLqVfhHHpK6LMEWC NXkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=QrGMtxmyNPlDj2bnXDwv+bwkylrJG7s0RwPjqEBnIK0=; b=vuR5rVBa1NnXz85LsfpzPAm8AUq2uA0ws8f/18vtIGQTzo/8UQHNHzHTTEsqyIZh6R bq52qyYu5lROvugl0WhTmffaLj+aiBr3ouNIVdbPABFeXSUhN+s38vaVLlMWQZljT+vs 9OmNL+RdEH8QlBkYkUUv73AWpF8nZggU7XzLX6UFajv1LCj0bD1cycc4GgbXzYJeylv1 WxGcxT1zVGloIYNQh8wOwDkN0WGgqim7OGj3Gj6VFyx9NweGfyLuKjdvB3/oWeS6oMTX qmkvA19QBRAXRE4AlL2Pzn0st8kb5Z06uOg6Wgo0l3KHwAnR8PUWx+Ycwb+pK2vcdnlI JccA== X-Gm-Message-State: AOAM532MvH2nU/Cs+jGTfOe8LSR9m76/Tiz/+zShqh1WsoH0TsevDfNl eHUz/IyrM/EqUvVfu75kNP381OCg7jyp8zLwhFc2st0IVJqHNA== X-Google-Smtp-Source: ABdhPJyj0trCXPZkNDofHue6Fgup5BH67SBviAdvDyymk/YhYJlRn5H+3PSKaGGNt6K2tyE/IdUK116QJnRjGBN2xmE= X-Received: by 2002:a05:6e02:194a:b0:2c2:59e2:d48e with SMTP id x10-20020a056e02194a00b002c259e2d48emr5806260ilu.128.1645566292684; Tue, 22 Feb 2022 13:44:52 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Michael Schuster Date: Tue, 22 Feb 2022 22:44:41 +0100 Message-ID: Subject: Re: "linker_load_file ... unsupported file type" after upgrade attempts on -CURRENT To: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="00000000000054728005d8a2422e" X-Rspamd-Queue-Id: 4K3CPd4PPHz4tsT X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=e9Qfpcs4; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of michaelsprivate@gmail.com designates 2607:f8b0:4864:20::135 as permitted sender) smtp.mailfrom=michaelsprivate@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::135:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MLMMJ_DEST(0.00)[freebsd-current]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N --00000000000054728005d8a2422e Content-Type: text/plain; charset="UTF-8" to respond to myself: I bit the bullet and installed one of the latest memstick images of -CURRENT , and am back up and running - with amdgpu and drm-current, and KDE (which had stopped working for me on the previous setup a while ago). Sorry if anyone's gone to any lengths here, though I didn't get any feedback. Thx Michael On Sun, Feb 20, 2022 at 3:12 PM Michael Schuster wrote: > Hi, > > I'm currently running on -CURRENT from November, though I think the > message for amdgpu.ko ("kernel: linker_load_file: /boot/modules/amdgpu.ko - > unsupported file type") started to appear as early as last August. Since > this isn't my daily driver (yet!), I didn't notice for quite a while, and > scfb is adequate for what little I currently do on FreeBSD. > When I initially installed this machine in Aug 2020, my GPU (Vega10 > Renoir) wasn't supported by DRM, so over time I made several builds of the > graphics/drm-devel-kmod port, which worked for a while last year. > > In the last weeks, in the time I managed to set aside for this work, I > made several attempts to bring this machine up-to-date, using "pkg > upgrade", building my own from /usr/src (always up-to-date using 'git > pull'), and beinstall.sh. (both separately and in combination). I always > work with separate build environments for these attempts. > All my upgrade attempts have resulted in a system that boots, but neither > starts X nor lets me log in on a console. There are "linker_load_file ... " > message for several .ko files, all preceded by a line like this: > > "KLD hconf.ko: depends on kernel - not available or version mismatchmodule > name" > > here are the paths I get this message about: > > /boot/kernel/cuse.ko > /boot/kernel/hconf.ko > /boot/kernel/hms.ko > /boot/kernel/hmt.ko > /boot/kernel/intpm.ko > /boot/kernel/lindebugfs.ko > /boot/kernel/linux.ko > /boot/kernel/linux64.ko > /boot/modules/amdgpu.ko > /boot/modules/drm.ko > > The information I found on the Internet about this error message seem to > indicate that I need to re-build the .ko being reported by the message with > the current kernel, which is .. hard if I can't even log in ;-). I would > also not expect a version mismatch after a pkg upgrade (but no, I didn't go > through all the output that generated). > > Does anyone have an idea what I can do to get past this obstacle? I could > of course always re-install, but that feels like giving in :-) > > TIA > Michael > -- > Michael Schuster > http://recursiveramblings.wordpress.com/ > recursion, n: see 'recursion' > -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion' --00000000000054728005d8a2422e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
to respond to myself: = I bit the bullet and installed one of the latest memstick images of -CURREN= T , and am back up and running - with amdgpu and drm-current, and KDE (whic= h had stopped working for me on the previous setup a while ago).
Sorry if anyone's gone to any lengths here, though I didn= 't get any feedback.

Thx
Michael

On Sun, Feb 20, 2022 at 3:1= 2 PM Michael Schuster <mich= aelsprivate@gmail.com> wrote:
Hi,

I'm currently running on -CUR= RENT from November, though I think the message for amdgpu.ko ("kernel:= linker_load_file: /boot/modules/amdgpu.ko - unsupported file type") s= tarted to appear as early as last August. Since this isn't my daily dri= ver (yet!), I didn't notice for quite a while, and scfb is adequate for= what little I currently do on FreeBSD.
When I initially installed this mac= hine in Aug 2020, my GPU (Vega10 Renoir) wasn't supported by DRM, so ov= er time I made several builds of the graphics/drm-devel-kmod port, which wo= rked for a while last year.

In the last weeks, in t= he time I managed to set aside for this work, I made several attempts to br= ing this machine up-to-date, using "pkg upgrade", building my own= from /usr/src (always up-to-date using 'git pull'), and beinstall.= sh. (both separately and in combination). I always work with separate build= environments for these attempts.
All my upgrade attempts have resulted in = a system that boots, but neither starts X nor lets me log in on a console. = There are "linker_load_file ... " message for several .ko files, = all preceded by a line like this:

"KLD hconf.ko: depends on kerne= l - not available or version mismatchmodule name"

here are t= he paths I get this message about:

/boot/kernel/cuse.ko
/boot/kerne= l/hconf.ko
/boot/kernel/hms.ko
/boot/kernel/hmt.ko
/boot/kernel/in= tpm.ko
/boot/kernel/lindebugfs.ko
/boot/kernel/linux.ko
/boot/kern= el/linux64.ko
/boot/modules/amdgpu.ko
/boot/modules/drm.ko
<= /div>

The information I found on the Internet about this err= or message seem to indicate that I need to re-build the .ko being reported = by the message with the current kernel, which is .. hard if I can't eve= n log in ;-). I would also not expect a version mismatch after a pkg upgrad= e (but no, I didn't go through all the output that generated).

Does anyone have an idea what I can do to get past th= is obstacle? I could of course always re-install, but that feels like givin= g in :-)

TIA
Michael
--
recursion, n: see 'recursion'


--
recursion, n: see 'recursion'=
--00000000000054728005d8a2422e--