Date: Tue, 22 Feb 2022 22:44:41 +0100 From: Michael Schuster <michaelsprivate@gmail.com> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: "linker_load_file ... unsupported file type" after upgrade attempts on -CURRENT Message-ID: <CADqw_gK-wXLzJPK9Q-iTo838qyh-YCskmNYBn82Eyi0kxyYbug@mail.gmail.com> In-Reply-To: <CADqw_gK_QFcCu2SRh_-H7Xu%2Bp2ZJggYsyhVurJfu1hKdHSwiEA@mail.gmail.com> References: <CADqw_gK_QFcCu2SRh_-H7Xu%2Bp2ZJggYsyhVurJfu1hKdHSwiEA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
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 <michaelsprivate@gmail.com>
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'
[-- Attachment #2 --]
<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">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).</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Sorry if anyone's gone to any lengths here, though I didn't get any feedback.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Thx</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Michael<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Feb 20, 2022 at 3:12 PM Michael Schuster <<a href="mailto:michaelsprivate@gmail.com">michaelsprivate@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:arial,helvetica,sans-serif;font-size:small">Hi,</div><div style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small">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.</div><div style="font-family:arial,helvetica,sans-serif;font-size:small">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.<br></div><div><br></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:small">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.</div><div style="font-family:arial,helvetica,sans-serif;font-size:small">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:</div><div style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small">"KLD hconf.ko: depends on kernel - not available or version mismatchmodule name"<br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small">here are the paths I get this message about:</div><div style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small">/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/lindebugfs.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="font-family:arial,helvetica,sans-serif;font-size:small"></div><br></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:small">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).<br></div></div><div><br></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:small">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 :-) </div></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small">TIA</div><div style="font-family:arial,helvetica,sans-serif;font-size:small">Michael<br></div></div>-- <br><div dir="ltr"><div dir="ltr"><div>Michael Schuster<br><a href="http://recursiveramblings.wordpress.com/" target="_blank">http://recursiveramblings.wordpress.com/</a><br></div><div>recursion, n: see 'recursion'<br></div></div></div></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Michael Schuster<br><a href="http://recursiveramblings.wordpress.com/" target="_blank">http://recursiveramblings.wordpress.com/</a><br></div><div>recursion, n: see 'recursion'<br></div></div></div></div>
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADqw_gK-wXLzJPK9Q-iTo838qyh-YCskmNYBn82Eyi0kxyYbug>