From nobody Sun Feb 20 14:12:53 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 410AF19CCF86 for ; Sun, 20 Feb 2022 14:13:05 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (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 4K1nTD5T78z3J7R for ; Sun, 20 Feb 2022 14:13:04 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: by mail-il1-x12e.google.com with SMTP id q4so1348465ilt.0 for ; Sun, 20 Feb 2022 06:13:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=q+VSYKApOUs4dJUaT0VSYWMLjAHwomI8maVED7xALd0=; b=Y3A7zMXjTM85Ut861DYVFhJ3pkEq72SB41d64RD3NxCrh+LyH763kD53v+hOrjXKV2 qINWrtQWxAM4k2047tPshVkFM3vdbxGs2QdnG9t2h4CjBZmT3X+/AXrjUGDrJuzGi/+5 LN0FWrbfytyFGhwTRHm8qqu7ikq8kdTWiELJDU9hZXgByMVzvJmEZiN43bQ0UsZtSRoo e1hZmrN/ra2pG+eYSYWjrX5SaBDNdp/Yi1R/MnzZHBJmta/v9gTrlRd0bCnHy3R4xFY+ fHujxyuu7LsQiCfNQ2mfeNwT9yL7TAqNpkmbm6KiETJRmzX3cK7cImykipvoBJ9CSsVe dbzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=q+VSYKApOUs4dJUaT0VSYWMLjAHwomI8maVED7xALd0=; b=Px0DWmJAXriJlkcYuBvTIjxVAWSXg+5iZyTOAmxr3pfgUgDvgwiAFFrpFLN65k7l48 k0lYjM80cbfW+/bjwzT5pDl0EAu183RToYqCwBlrXaOVPR3iQmdA4SRLM39BcisxmA+B YJ330fTZgXQzRWeMucFeTGpczjRuNQUubmSDTlQ4dt8C4Yy3/hDVW/6jPKviCNZxqJUy KXsVA/k2jKbUyxtTIUTW5EfofxAHiQt7QnF4YO0wsW4Ek1sTYCuFN10NZGNBq+RbSurl 448hoiHgrgFvVcbO6N1LJSW6qbnTjb4+rYeXD6nR34xpbXOBkKbSJLTDQrduD8c/AIXM 7beg== X-Gm-Message-State: AOAM533mQJOujUe7Cq1Te3P/mt0vMPJ9g8Pnj540raRUVtxdrOma/4lB 6Qb0JNu8k53f59/XBr3cv0SvWLAXJg6L2juC609XhYQieOIpn6ri X-Google-Smtp-Source: ABdhPJxDAhiD9rprwkgwS3Xfs61A/h/7oePMS7VLIuA7FjtPCIgsFfLTIdLz5zlV1Y3UndlX3wEmaaTb3Q6/lsnJmlA= X-Received: by 2002:a05:6e02:1beb:b0:2bf:eed2:cd93 with SMTP id y11-20020a056e021beb00b002bfeed2cd93mr11996083ilv.99.1645366383897; Sun, 20 Feb 2022 06:13:03 -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 From: Michael Schuster Date: Sun, 20 Feb 2022 15:12:53 +0100 Message-ID: Subject: "linker_load_file ... unsupported file type" after upgrade attempts on -CURRENT To: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000d671f405d873b6b2" X-Rspamd-Queue-Id: 4K1nTD5T78z3J7R X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=Y3A7zMXj; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of michaelsprivate@gmail.com designates 2607:f8b0:4864:20::12e as permitted sender) smtp.mailfrom=michaelsprivate@gmail.com X-Spamd-Result: default: False [-3.94 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; 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::12e:from]; NEURAL_HAM_SHORT(-0.94)[-0.937]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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 --000000000000d671f405d873b6b2 Content-Type: text/plain; charset="UTF-8" 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' --000000000000d671f405d873b6b2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ;font-size:small">I'm currently running on -CURRENT from November, thou= gh I think the message for amdgpu.ko ("kernel: linker_load_file: /boot= /modules/amdgpu.ko - unsupported file type") started to appear as earl= y 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 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 the time I managed to set aside for this work, I mad= e several attempts to bring this machine up-to-date, using "pkg upgrad= e", building my own from /usr/src (always up-to-date using 'git pu= ll'), 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_lo= ad_file ... " message for several .ko files, all preceded by a line li= ke this:

"KLD hco= nf.ko: depends on kernel - not available or version mismatchmodule name&quo= t;

here are the pa= ths 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/lindebug= fs.ko
/boot/kernel/linux.ko
/boot/kernel/linux64.ko
/boot/modules/= amdgpu.ko
/boot/modules/drm.ko

The information I found on the Intern= et about this error message seem to indicate that I need to re-build the .k= o being reported by the message with the current kernel, which is .. hard i= f I can't even log in ;-). I would also not expect a version mismatch a= fter a pkg upgrade (but no, I didn't go through all the output that gen= erated).

Does anyone = have an idea what I can do to get past this obstacle? I could of course alw= ays re-install, but that feels like giving in :-)

TIA
Michael=
--
recursion, n: see 'recu= rsion'
--000000000000d671f405d873b6b2--