Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 20 Feb 2022 15:12:53 +0100
From:      Michael Schuster <michaelsprivate@gmail.com>
To:        FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject:   "linker_load_file ... unsupported file type" after upgrade attempts on -CURRENT
Message-ID:  <CADqw_gK_QFcCu2SRh_-H7Xu%2Bp2ZJggYsyhVurJfu1hKdHSwiEA@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
--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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">Hi,</div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></div><=
div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif=
;font-size:small">I&#39;m currently running on -CURRENT from November, thou=
gh I think the message for amdgpu.ko (&quot;kernel: linker_load_file: /boot=
/modules/amdgpu.ko - unsupported file type&quot;) started to appear as earl=
y as last August. Since this isn&#39;t my daily driver (yet!), I didn&#39;t=
 notice for quite a while, and scfb is adequate for what little I currently=
 do on FreeBSD.</div><div class=3D"gmail_default" style=3D"font-family:aria=
l,helvetica,sans-serif;font-size:small">When I initially installed this mac=
hine in Aug 2020, my GPU (Vega10 Renoir) wasn&#39;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.<br></div><div><br></div><div><div style=3D"font=
-family:arial,helvetica,sans-serif;font-size:small" class=3D"gmail_default"=
>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 &quot;pkg upgrad=
e&quot;, building my own from /usr/src (always up-to-date using &#39;git pu=
ll&#39;), and beinstall.sh. (both separately and in combination). I always =
work with separate build environments for these attempts.</div><div style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small" class=3D"gmail_=
default">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 &quot;linker_lo=
ad_file ... &quot; message for several .ko files, all preceded by a line li=
ke this:</div><div style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small" class=3D"gmail_default"><br></div><div style=3D"font-family:arial,=
helvetica,sans-serif;font-size:small" class=3D"gmail_default">&quot;KLD hco=
nf.ko: depends on kernel - not available or version mismatchmodule name&quo=
t;<br></div><div style=3D"font-family:arial,helvetica,sans-serif;font-size:=
small" class=3D"gmail_default"><br></div><div style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small" class=3D"gmail_default">here are the pa=
ths I get this message about:</div><div style=3D"font-family:arial,helvetic=
a,sans-serif;font-size:small" class=3D"gmail_default"><br></div><div style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small" class=3D"gmail_=
default">/boot/kernel/cuse.ko<br>/boot/kernel/hconf.ko<br>/boot/kernel/hms.=
ko<br>/boot/kernel/hmt.ko<br>/boot/kernel/intpm.ko<br>/boot/kernel/lindebug=
fs.ko<br>/boot/kernel/linux.ko<br>/boot/kernel/linux64.ko<br>/boot/modules/=
amdgpu.ko<br>/boot/modules/drm.ko<br></div></div><div><div style=3D"font-fa=
mily:arial,helvetica,sans-serif;font-size:small" class=3D"gmail_default"></=
div><br></div><div><div style=3D"font-family:arial,helvetica,sans-serif;fon=
t-size:small" class=3D"gmail_default">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&#39;t even log in ;-). I would also not expect a version mismatch a=
fter a pkg upgrade (but no, I didn&#39;t go through all the output that gen=
erated).<br></div></div><div><br></div><div><div style=3D"font-family:arial=
,helvetica,sans-serif;font-size:small" class=3D"gmail_default">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 :-) </div></div><div><div sty=
le=3D"font-family:arial,helvetica,sans-serif;font-size:small" class=3D"gmai=
l_default"><br></div><div style=3D"font-family:arial,helvetica,sans-serif;f=
ont-size:small" class=3D"gmail_default">TIA</div><div style=3D"font-family:=
arial,helvetica,sans-serif;font-size:small" class=3D"gmail_default">Michael=
<br></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data-smar=
tmail=3D"gmail_signature"><div dir=3D"ltr"><div>Michael Schuster<br><a href=
=3D"http://recursiveramblings.wordpress.com/" target=3D"_blank">http://recu=
rsiveramblings.wordpress.com/</a><br></div><div>recursion, n: see &#39;recu=
rsion&#39;<br></div></div></div></div>

--000000000000d671f405d873b6b2--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADqw_gK_QFcCu2SRh_-H7Xu%2Bp2ZJggYsyhVurJfu1hKdHSwiEA>