Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Dec 2019 22:45:27 +0100
From:      Per Hedeland <>
Subject:   Re: kernel: drmn0: This code is obsolete abandonware. Install the graphics/drm-legacy-kmod pkg
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 2019-12-30 22:07, Kurt Hackenberg wrote:
> On 2019-12-30 05:49, Per Hedeland wrote:
>> The message is from the in-kernel drm version, not the one installed
>> by the package...
> Right.
> And there's another complication: the release 12 package cannot be installed on a 12.1 system. Instead, you must compile that port, and use the port mechanism to install the compiled version. This is 
> because some internal kernel interface changed between 12.0 and 12.1.

Yes, this has been brought up several times, I think both here and in

> I think there's a version number, so the 12.1 kernel detects and refuses to load the package, which was compiled for 12.0. (Or 
> maybe loads it but refuses to run it.) That refusal may be why the obsolete DRM code included in the kernel runs, and puts out the "abandonware" message.

Actually I believe there is no such check - the 12.1 kernel loads the
compiled-for-12.0 module, and a variety of badness ensues, in most
cases either a panic or a hang. I.e. I don't believe this is the
reason for the obsolete in-kernel drm code being run.

> This is documented in this DRM bug report:
> If you think this is kind of a mess, then I agree with you. The problem is that these kernel modules are distributed as ports/packages, rather than with the kernel. That's policy, because the people 
> doing it decided that the DRM stuff changes too fast for the kernel release schedule to keep up with it. That is not expected to change.

Agreed, but I think the problem is not restricted to the DRM stuff,
but a general problem of having kernel modules in ports (for whatever
reason), since the packages are built for a specific kernel version
that may differ from the one where you install the package.  I have
been bitten several times by the virtualbox-ose-kmod package being out
of sync with the kernel I'm running, and thus routinely build it from
the port, even though I use the package for the "main" virtualbox-ose


Want to link to this message? Use this URL: <>