From Newsgroup: alt.os.linux.mint


The following warning displayed during a compilation:

Warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
You are using: gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

I cannot clearly make out from synaptic which item to select to overcome this problem
--
Linux Mint 22.1 kernel version 6.8.0-51-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On 28/09/2025 12:37, pinnerite wrote:

The following warning displayed during a compilation:

Warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
You are using: gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

I cannot clearly make out from synaptic which item to select to overcome this problem

IME Asking Chat-GPT is a valid option when you have error messages like
this.

ChatGPT said:

That warning usually shows up when you try to build a kernel module (for example with dkms or directly via make) and your current compiler binary
is not exactly the same as the one used to build the running kernel.

In your case, the versions are effectively identical:

Kernel built with:
x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

Your compiler:
gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

The difference is just in the name of the binary
(x86_64-linux-gnu-gcc-13 vs gcc-13), not the actual compiler version.

rUON+A What this means:

ItrCOs only a harmless warning. The kernel checks that the compiler string matches exactly, but the build is fine because the versions are identical.

Ignore it, or ask Chat-GPT how to set an enviroment variable, CC
--
Adrian C
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Sun, 9/28/2025 7:37 AM, pinnerite wrote:

The following warning displayed during a compilation:

Warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
You are using: gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

I cannot clearly make out from synaptic which item to select to overcome this problem

Saw that during my build of your stuff, they are actually the same compiler.

Note that, when you install some of the cross-compiler packages, they have
long executable path names as well (similar to x86_64-linux-gnu-gcc-13), and those could be soft links to the actual compiler file, or they could be scripts of some sort which call the compiler (eventually). When the compiler was built, perhaps the build machine, it did a path evaluation, running into one of the many staged copies. Rather than the "plain" path entry gcc-13 (or just gcc -V if they were clever). The package information indicates they are at the same release level.
The kernel building machine, could actually be cross-compiling for a number
of platforms, such as ARM or RISC-V and x86_64 was "just one of the platforms we build for" and treated no differently. They could have been in essence "cross compiling for x86_64 while actually *on* x86_64" and that is why
your home build of a kernel (which is not staged for cross compiling)
resolves to a different GCC invocation location than the fancy-name
the kernel build happened to use.

Carry on :-)

Back to work.

You need some "symptoms", to tell me this is causing your actual build problem.

There can be warnings (not errors) during TBSDTV build, but as long
as it makes it to the end, then it is time to go onto the next steps.
These next steps, I did not test, as the steps after the build would be the install.
Every step has its own risks.

When you installed "build-essential", it is a meta-package that puts a
basic build set in place. It may include GCC and PERL, you'd have to check
to see what the entire list is. As far as I know, build-essential is
enough to build a kernel, but it can build many other things as well.
The rust compiler (now a part of building the entire kernel, not your
package), may be built in place (not sure), it may not necessarily
come from a distro package.

I only did the build of your package, to basically prove I could finish
the compiling stage. And it did seem to hit the end OK. Once that one item
in the control file was commented out (and you commented you'd already
done that), it seemed to be clear sailing after that. Only resolving
the location of the "vmlinux" location so the build environment finds
it, remains to be done. In the real kernel build (I built the entire
6.8.0 kernel on my LM222 VM, compile was pretty slow), the vmlinux file
on there is around 400MB, whereas the real vmlinux file is a lot smaller, like maybe 10MB or so and the one on the machine as the runtime seems
to be in /boot. I don't know what the intention of the TBSDTV build
is, in terms of which vmlinux it wants as reference materials.
As far as I know, the one in your /boot would be considered to be
a genkernel-derived one, so it should be good enough for install
on your own machine at least. I don't know what purpose would be
served, referencing the giant one in the 6.8.0 entire kernel build.

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Sun, 28 Sep 2025 14:30:22 +0100
Adrian Caspersz <email@here.invalid> wrote:

On 28/09/2025 12:37, pinnerite wrote:

The following warning displayed during a compilation:

Warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
You are using: gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

I cannot clearly make out from synaptic which item to select to overcome this problem

IME Asking Chat-GPT is a valid option when you have error messages like this.

ChatGPT said:

That warning usually shows up when you try to build a kernel module (for example with dkms or directly via make) and your current compiler binary
is not exactly the same as the one used to build the running kernel.

In your case, the versions are effectively identical:

Kernel built with:
x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

Your compiler:
gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

The difference is just in the name of the binary
(x86_64-linux-gnu-gcc-13 vs gcc-13), not the actual compiler version.

rUON+A What this means:

ItrCOs only a harmless warning. The kernel checks that the compiler string matches exactly, but the build is fine because the versions are identical.

Ignore it, or ask Chat-GPT how to set an enviroment variable, CC

--
Adrian C

Sadly when complete make -j4
after having edited /opt/media_build/backports/backports.txt
to comment out:

[6.8.1023]
# add v6.8-ccs.patch } recommended to avoid the problem below
add v6.8-spi.patch } but doesn't
add v6.8_remove.patch }

it ends like this:

CC [M] /opt/media_build/v4l/ccs-limits.o
/opt/media_build/v4l/ccs-core.c: In function 'ccs_set_ctrl': /opt/media_build/v4l/ccs-core.c:668:21: error: too many arguments to function 'pm_runtime_get_if_active'
668 | pm_status = pm_runtime_get_if_active(&client->dev, true);
| ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /opt/media_build/v4l/ccs-core.c:22: ./include/linux/pm_runtime.h:75:12: note: declared here
75 | extern int pm_runtime_get_if_active(struct device *dev);
| ^~~~~~~~~~~~~~~~~~~~~~~~
CC [M] /opt/media_build/v4l/ccs-data.o
make[4]: *** [scripts/Makefile.build:243: /opt/media_build/v4l/ccs-core.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [/usr/src/linux-headers-6.8.0-51-generic/Makefile:1925: /opt/media_build/v4l] Error 2
make[2]: *** [Makefile:240: __sub-make] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-6.8.0-51-generic'
make[1]: *** [Makefile:53: default] Error 2
make[1]: Leaving directory '/opt/media_build/v4l'
make: *** [Makefile:26: all] Error 2
/opt/media_build$

The reason I am using kernel version 6.8.0-51-generic is that was the install kernel and alloewed me to use both screens. However I edited twom lines in grub:

# GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10

to defer boot up until I had selected kernel version 6.8.0-51-generic and now I only get one screen again!

I am truly cheesed off.

Alan
--
Linux Mint 22.1 kernel version 6.8.0-51-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Sun, 9/28/2025 3:35 PM, pinnerite wrote:

On Sun, 28 Sep 2025 14:30:22 +0100
Adrian Caspersz <email@here.invalid> wrote:

On 28/09/2025 12:37, pinnerite wrote:

The following warning displayed during a compilation:

Warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
You are using: gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0 >>>
I cannot clearly make out from synaptic which item to select to overcome this problem

IME Asking Chat-GPT is a valid option when you have error messages like
this.

ChatGPT said:

That warning usually shows up when you try to build a kernel module (for
example with dkms or directly via make) and your current compiler binary
is not exactly the same as the one used to build the running kernel.

In your case, the versions are effectively identical:

Kernel built with:
x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

Your compiler:
gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

The difference is just in the name of the binary
(x86_64-linux-gnu-gcc-13 vs gcc-13), not the actual compiler version.

rUON+A What this means:

ItrCOs only a harmless warning. The kernel checks that the compiler string >> matches exactly, but the build is fine because the versions are identical. >>
Ignore it, or ask Chat-GPT how to set an enviroment variable, CC

--
Adrian C

Sadly when complete make -j4
after having edited /opt/media_build/backports/backports.txt
to comment out:

[6.8.1023]
# add v6.8-ccs.patch } recommended to avoid the problem below
add v6.8-spi.patch } but doesn't
add v6.8_remove.patch }

it ends like this:

CC [M] /opt/media_build/v4l/ccs-limits.o
/opt/media_build/v4l/ccs-core.c: In function 'ccs_set_ctrl': /opt/media_build/v4l/ccs-core.c:668:21: error: too many arguments to function 'pm_runtime_get_if_active'
668 | pm_status = pm_runtime_get_if_active(&client->dev, true);
| ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /opt/media_build/v4l/ccs-core.c:22: ./include/linux/pm_runtime.h:75:12: note: declared here
75 | extern int pm_runtime_get_if_active(struct device *dev);
| ^~~~~~~~~~~~~~~~~~~~~~~~
CC [M] /opt/media_build/v4l/ccs-data.o
make[4]: *** [scripts/Makefile.build:243: /opt/media_build/v4l/ccs-core.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [/usr/src/linux-headers-6.8.0-51-generic/Makefile:1925: /opt/media_build/v4l] Error 2
make[2]: *** [Makefile:240: __sub-make] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-6.8.0-51-generic'
make[1]: *** [Makefile:53: default] Error 2
make[1]: Leaving directory '/opt/media_build/v4l'
make: *** [Makefile:26: all] Error 2
/opt/media_build$

The reason I am using kernel version 6.8.0-51-generic is that was the install kernel and alloewed me to use both screens. However I edited twom lines in grub:

# GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10

to defer boot up until I had selected kernel version 6.8.0-51-generic and now I only get one screen again!

I am truly cheesed off.

Alan

Um, did you do a "make clean" in the build tree
between each one of these adventures ? Or are you
following the recipe and starting clean each time
and making the modification and so on ?

I think I may have done a "make clean" at some point, or
something similar.

Paul

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Sun, 28 Sep 2025 23:46:30 -0400
Paul <nospam@needed.invalid> wrote:

On Sun, 9/28/2025 3:35 PM, pinnerite wrote:

On Sun, 28 Sep 2025 14:30:22 +0100
Adrian Caspersz <email@here.invalid> wrote:

On 28/09/2025 12:37, pinnerite wrote:

The following warning displayed during a compilation:

Warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
You are using: gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0 >>>
I cannot clearly make out from synaptic which item to select to overcome this problem

IME Asking Chat-GPT is a valid option when you have error messages like >> this.

ChatGPT said:

That warning usually shows up when you try to build a kernel module (for >> example with dkms or directly via make) and your current compiler binary >> is not exactly the same as the one used to build the running kernel.

In your case, the versions are effectively identical:

Kernel built with:
x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

Your compiler:
gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

The difference is just in the name of the binary
(x86_64-linux-gnu-gcc-13 vs gcc-13), not the actual compiler version.

rUON+A What this means:

ItrCOs only a harmless warning. The kernel checks that the compiler string
matches exactly, but the build is fine because the versions are identical. >>
Ignore it, or ask Chat-GPT how to set an enviroment variable, CC

--
Adrian C

Sadly when complete make -j4
after having edited /opt/media_build/backports/backports.txt
to comment out:

[6.8.1023]
# add v6.8-ccs.patch } recommended to avoid the problem below
add v6.8-spi.patch } but doesn't
add v6.8_remove.patch }

it ends like this:

CC [M] /opt/media_build/v4l/ccs-limits.o /opt/media_build/v4l/ccs-core.c: In function 'ccs_set_ctrl': /opt/media_build/v4l/ccs-core.c:668:21: error: too many arguments to function 'pm_runtime_get_if_active'
668 | pm_status = pm_runtime_get_if_active(&client->dev, true);
| ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /opt/media_build/v4l/ccs-core.c:22: ./include/linux/pm_runtime.h:75:12: note: declared here
75 | extern int pm_runtime_get_if_active(struct device *dev);
| ^~~~~~~~~~~~~~~~~~~~~~~~
CC [M] /opt/media_build/v4l/ccs-data.o
make[4]: *** [scripts/Makefile.build:243: /opt/media_build/v4l/ccs-core.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [/usr/src/linux-headers-6.8.0-51-generic/Makefile:1925: /opt/media_build/v4l] Error 2
make[2]: *** [Makefile:240: __sub-make] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-6.8.0-51-generic' make[1]: *** [Makefile:53: default] Error 2
make[1]: Leaving directory '/opt/media_build/v4l'
make: *** [Makefile:26: all] Error 2
/opt/media_build$

The reason I am using kernel version 6.8.0-51-generic is that was the install kernel and alloewed me to use both screens. However I edited twom lines in grub:

# GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10

to defer boot up until I had selected kernel version 6.8.0-51-generic and now I only get one screen again!

I am truly cheesed off.

Alan

Um, did you do a "make clean" in the build tree
between each one of these adventures ? Or are you
following the recipe and starting clean each time
and making the modification and so on ?

I think I may have done a "make clean" at some point, or
something similar.

Paul

I have not only run make clean but also make distclean.
ChatGPT-5 has been gradually knocking down the reason for the errors.
It then tells me which library files to install and off we go again.
But each time we stop and repair, then we go on longer.
Right now make has been running for at least 15 minutes which is record
for this job. I'm keeping everything crossed.

Alan
--
Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

pinnerite wrote:

But each time we stop and repair, then we go on longer.

I tho't that is what compiling means :-/
--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Mon, 9/29/2025 4:02 PM, Mike Easter wrote:

pinnerite wrote:

But each time we stop and repair, then we go on longer.

I tho't that is what compiling means :-/

It's a steeplechase. You keep jumping over the barriers
until you get to "the end".

And it's only possible when you have a rich tree with
lots of -dev packages with .so library and .h header files.
That makes a big difference to how easy this stuff seems.

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Mon, 29 Sep 2025 21:48:39 -0400
Paul <nospam@needed.invalid> wrote:

On Mon, 9/29/2025 4:02 PM, Mike Easter wrote:

pinnerite wrote:

But each time we stop and repair, then we go on longer.

I tho't that is what compiling means :-/

It's a steeplechase. You keep jumping over the barriers
until you get to "the end".

And it's only possible when you have a rich tree with
lots of -dev packages with .so library and .h header files.
That makes a big difference to how easy this stuff seems.

Paul

After sapending yesterday constantly compiling the drivers,
arriving at an error, identifying a mising kernel module,
installing it and trying again.

Eventually I arrived at it913x which doesn't erxist in the 6.8
series kernels and cannot be created without source and makefile.

ChatGPT reckons I should go to a 5.15 kernel but tha is not
available in Mint 22.1 so it looks like I will have to drop
back to 21.3 or eatlier.

I will have to do a bit of research before I jump.

Alan
--
Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Wed, 10/1/2025 7:23 AM, pinnerite wrote:

On Mon, 29 Sep 2025 21:48:39 -0400
Paul <nospam@needed.invalid> wrote:

On Mon, 9/29/2025 4:02 PM, Mike Easter wrote:

pinnerite wrote:

But each time we stop and repair, then we go on longer.

I tho't that is what compiling means :-/

It's a steeplechase. You keep jumping over the barriers
until you get to "the end".

And it's only possible when you have a rich tree with
lots of -dev packages with .so library and .h header files.
That makes a big difference to how easy this stuff seems.

Paul

After sapending yesterday constantly compiling the drivers,
arriving at an error, identifying a mising kernel module,
installing it and trying again.

Eventually I arrived at it913x which doesn't erxist in the 6.8
series kernels and cannot be created without source and makefile.

ChatGPT reckons I should go to a 5.15 kernel but tha is not
available in Mint 22.1 so it looks like I will have to drop
back to 21.3 or eatlier.

I will have to do a bit of research before I jump.

Alan

Like this one then.

https://www.linuxtv.org/wiki/index.php/ITE_IT9135

*******

https://www.linuxtv.org/downloads/drivers/README

"NOTE: This is outdated, preserved just for media-build to run up to Kernel 5.18.

You can get the drivers directly from the git tree.
"

md5sum linux-media.tar.bz2
902750c59f402a8f92759d6f0b3943e0 linux-media.tar.bz2

I see that here, but I am unable to find the log of having obtained that.
It should have been in the download logs.

https://github.com/tbsdtv/media_build/releases

last Latest

Last V4L DVB sources snapshot and required firmwares
Used by build script

Assets

dvb-firmwares.tar.bz2 1.27 MB Mar 27
linux-media.tar.bz2 8.09 MB May 10 <=== This has the same MD5SUM as mine
linux-media.tar.bz2.md5 87 Bytes May 10
Source code (zip) Mar 19
Source code (tar.gz) Mar 19

~/Downloads/media_build/v4l$ ls
...
dm1105.mod.o isys_stream2mmio_rmgr.c rc-odroid.mod.c v4l2-async.o dm1105.o isys_stream2mmio_rmgr.h rc-odroid.mod.o v4l2.c dma2d.c it913x.c rc-odroid.o v4l2-common.c
dma2d.h it913x.h rc-pctv-sedna.c v4l2-common.o
dma2d-hw.c it913x.ko <=== rc-pctv-sedna.ko v4l2-compat-ioctl32.c
dma2d-regs.h it913x.mod rc-pctv-sedna.mod v4l2-compat-ioctl32.o
dmabuf-cache.c it913x.mod.c rc-pctv-sedna.mod.c v4l2-ctrls-api.c
dma.c it913x.mod.o rc-pctv-sedna.mod.o v4l2-ctrls-api.o
dma_global.h it913x.o rc-pctv-sedna.o v4l2-ctrls-core.c
dma.h itd1000.c rc-pine64.c v4l2-ctrls-core.o
dma_local.h itd1000.h rc-pine64.ko v4l2-ctrls-defs.c

Seems I've got one there.

This is an example of my work area.

[Picture]

https://i.postimg.cc/D0SVrwjn/media-build-work-area.gif

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Wed, 1 Oct 2025 11:47:53 -0400
Paul <nospam@needed.invalid> wrote:

On Wed, 10/1/2025 7:23 AM, pinnerite wrote:

On Mon, 29 Sep 2025 21:48:39 -0400
Paul <nospam@needed.invalid> wrote:

On Mon, 9/29/2025 4:02 PM, Mike Easter wrote:

pinnerite wrote:

But each time we stop and repair, then we go on longer.

I tho't that is what compiling means :-/

It's a steeplechase. You keep jumping over the barriers
until you get to "the end".

And it's only possible when you have a rich tree with
lots of -dev packages with .so library and .h header files.
That makes a big difference to how easy this stuff seems.

Paul

After sapending yesterday constantly compiling the drivers,
arriving at an error, identifying a mising kernel module,
installing it and trying again.

Eventually I arrived at it913x which doesn't erxist in the 6.8
series kernels and cannot be created without source and makefile.

ChatGPT reckons I should go to a 5.15 kernel but tha is not
available in Mint 22.1 so it looks like I will have to drop
back to 21.3 or eatlier.

I will have to do a bit of research before I jump.

Alan

Like this one then.

https://www.linuxtv.org/wiki/index.php/ITE_IT9135

*******

https://www.linuxtv.org/downloads/drivers/README

"NOTE: This is outdated, preserved just for media-build to run up to Kernel 5.18.

You can get the drivers directly from the git tree.
"

md5sum linux-media.tar.bz2
902750c59f402a8f92759d6f0b3943e0 linux-media.tar.bz2

I see that here, but I am unable to find the log of having obtained that.
It should have been in the download logs.

https://github.com/tbsdtv/media_build/releases

last Latest

Last V4L DVB sources snapshot and required firmwares
Used by build script

Assets

dvb-firmwares.tar.bz2 1.27 MB Mar 27
linux-media.tar.bz2 8.09 MB May 10 <=== This has the same MD5SUM as mine
linux-media.tar.bz2.md5 87 Bytes May 10
Source code (zip) Mar 19
Source code (tar.gz) Mar 19

~/Downloads/media_build/v4l$ ls
...
dm1105.mod.o isys_stream2mmio_rmgr.c rc-odroid.mod.c v4l2-async.o
dm1105.o isys_stream2mmio_rmgr.h rc-odroid.mod.o v4l2.c dma2d.c it913x.c rc-odroid.o v4l2-common.c
dma2d.h it913x.h rc-pctv-sedna.c v4l2-common.o
dma2d-hw.c it913x.ko <=== rc-pctv-sedna.ko v4l2-compat-ioctl32.c
dma2d-regs.h it913x.mod rc-pctv-sedna.mod v4l2-compat-ioctl32.o
dmabuf-cache.c it913x.mod.c rc-pctv-sedna.mod.c v4l2-ctrls-api.c
dma.c it913x.mod.o rc-pctv-sedna.mod.o v4l2-ctrls-api.o
dma_global.h it913x.o rc-pctv-sedna.o v4l2-ctrls-core.c
dma.h itd1000.c rc-pine64.c v4l2-ctrls-core.o
dma_local.h itd1000.h rc-pine64.ko v4l2-ctrls-defs.c

Seems I've got one there.

This is an example of my work area.

[Picture]

https://i.postimg.cc/D0SVrwjn/media-build-work-area.gif

Paul

I created a virtual Mint 21.3 and using kernel 5.15.0-157 successfully compiled the drivers.
I then installed Mint 21.3 on the "bare metal" and again succesfuly compiled the drivers.

Alan

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

pinnerite wrote:

I created a virtual Mint 21.3 and using kernel 5.15.0-157 successfully compiled the drivers.
I then installed Mint 21.3 on the "bare metal" and again succesfuly compiled the drivers.

Yay!
--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Thu, 2 Oct 2025 11:05:33 -0700
Mike Easter <MikeE@ster.invalid> wrote:

pinnerite wrote:

I created a virtual Mint 21.3 and using kernel 5.15.0-157 successfully compiled the drivers.
I then installed Mint 21.3 on the "bare metal" and again succesfuly compiled the drivers.

Yay!

--
Mike Easter

Back to the HTPC, I had taken backups of my MythTV recordings and of the /ver/lib/mysql directory.
Temprarily saved all hidden fies to a directory on /home and did a clean install to Mint 21.3.
To cut a long story short it all went well, as did the compilation.

Without ChatGPT I doubt that I would have saved the recordings.
It took ages but as I was ill anyway, I had the time.

Thanks for reading.

Alan
--
Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

pinnerite wrote:

Back to the HTPC, I had taken backups of my MythTV recordings and
of the /ver/lib/mysql directory. Temprarily saved all hidden fies to
a directory on /home and did a clean install to Mint 21.3. To cut a
long story short it all went well, as did the compilation.

Without ChatGPT I doubt that I would have saved the recordings. It
took ages but as I was ill anyway, I had the time.

I have very little experience w/ compiling, ranging from 'piece of cake'
to 'I need help here' to 'this is impossible, I quit'.

In reading, I found some interest in DKMS, described as:

Dynamic Kernel Module Support (DKMS) is a program/framework that
enables generating Linux kernel modules whose sources generally
reside outside the kernel source tree. The concept is to have DKMS
modules automatically rebuilt when a new kernel is installed.

That's from wp. Another area I read is Arch's wiki, which I LUV.

https://wiki.archlinux.org/title/Dynamic_Kernel_Module_Support

I have no idea whether or not that strategy might help your hardware/
software situation.

In arch:

This means that a user does not have to wait for a company, project,
or package maintainer to release a new version of the module. Since
the introduction of pacman hooks, the rebuild of the modules is
handled automatically when a kernel is upgraded.

My understanding is that in the dpkg world, those hooks are called
triggers,

dpkg triggers DKMS when a new kernel is installed or updated on a Debian-based system. This interaction ensures that out-of-tree
kernel modules managed by DKMS are automatically rebuilt and made
compatible with the new kernel.

--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Mike Easter wrote:

My understanding is that in the dpkg world, those hooks are called
triggers,

Creating a new DKMS from an out-of-tree driver

https://canonical-kteam-docs.readthedocs-hosted.com/public/tutorial/creating_dkms.html
--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Wed, 8 Oct 2025 10:42:10 -0700
Mike Easter <MikeE@ster.invalid> wrote:

Mike Easter wrote:

My understanding is that in the dpkg world, those hooks are called triggers,

Creating a new DKMS from an out-of-tree driver

https://canonical-kteam-docs.readthedocs-hosted.com/public/tutorial/creating_dkms.html

--
Mike Easter

Interesting but not helpful because the context is why has the necessary kerne module been dropped after Mint 21.3?

Am I never going to be able to upgrade to a later version of Mint?
That doesn't make sense.
It is a long way from user-friendly. More like user-hostile.
The last time this happened to me, I searched for and found a more user-friendly distro.

Alan
--
Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Wed, 8 Oct 2025 16:57:39 +0100, pinnerite wrote:

Back to the HTPC, I had taken backups of my MythTV recordings and of
the /v[a]r/lib/mysql directory.

At one time, I used to save backups of /var/lib/mysql. Trouble is, those
are tricky to restore.

A lot easier to use mysqldump (or mariadb-dump, now). This will give
you a large file of SQL commands that you can execute to reload a copy
of the database in the same state.
--- Synchronet 3.21a-Linux NewsLink 1.2