• compatibility issur

    From pinnerite@pinnerite@gmail.com to alt.os.linux.mint on Sun Jul 19 12:23:12 2026
    From Newsgroup: alt.os.linux.mint

    I built a Mint 22.3 machine from scratch.
    Now using kernel 6.8.0-134

    Installed MythTV 35 and got it working fine.

    Then restored a backup of the database from another machine running
    kernel 6.8.0-84. When I restored this on the first machine, it caused
    MythTV to no longer be able to get live TV.

    After hours of testsand faffing about ChatGPT decided I should install
    kernel 6.8.0-84 on the first machine. The problem is I cannot access
    and download it!
    --
    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.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Sun Jul 19 09:59:07 2026
    From Newsgroup: alt.os.linux.mint

    On Sun, 7/19/2026 7:23 AM, pinnerite wrote:
    I built a Mint 22.3 machine from scratch.
    Now using kernel 6.8.0-134

    Installed MythTV 35 and got it working fine.

    Then restored a backup of the database from another machine running
    kernel 6.8.0-84. When I restored this on the first machine, it caused
    MythTV to no longer be able to get live TV.

    After hours of testsand faffing about ChatGPT decided I should install
    kernel 6.8.0-84 on the first machine. The problem is I cannot access
    and download it!



    I don't know. Maybe start here ?

    https://www.fosslinux.com/138008/how-to-install-and-try-different-linux-kernels-in-linux-mint.htm

    You'll need to back up the slash, before attempting to trash things :-)
    It's not that it would get trashed, but you might make a mess along
    the way, and want to do it a second time with all recipe refinements
    along the way, so not a lot of disk is wasted on "splatter".

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From german newsgroups@usualsuspectrider@gmail.com to alt.os.linux.mint on Sun Jul 19 16:55:34 2026
    From Newsgroup: alt.os.linux.mint

    Le 19/07/2026 |a 13:23, pinnerite a |-crit-a:
    I built a Mint 22.3 machine from scratch.
    Now using kernel 6.8.0-134

    Installed MythTV 35 and got it working fine.

    Then restored a backup of the database from another machine running
    kernel 6.8.0-84. When I restored this on the first machine, it caused
    MythTV to no longer be able to get live TV.

    After hours of testsand faffing about ChatGPT decided I should install
    kernel 6.8.0-84 on the first machine. The problem is I cannot access
    and download it!



    tient! d|-j|a lu ! |oa tourne en boucle les iA!?#
    --
    Amicalement,

    Frenchy Friendly, & French touch !

    german
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mike Easter@MikeE@ster.invalid to alt.os.linux.mint on Sun Jul 19 12:09:29 2026
    From Newsgroup: alt.os.linux.mint

    pinnerite wrote:
    Then restored a backup of the database from another machine running
    kernel 6.8.0-84. When I restored this on the first machine, it
    caused MythTV to no longer be able to get live TV.

    Linux MythTV:

    MythTV stores all of its configuration, Electronic Program Guide
    (EPG) data, and recording schedules in a relational (remove this one
    MariaDB or) MySQL database named mythconverg. This database consists
    of over 100 interconnected tables that are generated and maintained automatically by the MythTV backend.

    It doesn't seem that there should be some disaster between kernel -84
    and -134 since they are both 6.8.0-.

    I asked gglAIov about this and it said:

    When MythTV reports a database incompatibility after a Linux kernel
    update (like moving from 6.8.0-84 to 6.8.0-134), it usually means
    the backend package was also upgraded. The new software version
    requires a schema update for the mythconverg database.

    ... Not quite the same as the issue here, but close enough for a
    resemblance. Then it tells how to do the schema update.

    If you care to see that, here's the link; personally I know nothing
    about mythtv OR schema updating NOR proper disaster preparation for
    kernal hijinks:

    https://share.google/aimode/LxsLDnTRdTJwelkeo
    --
    Mike Easter
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Sun Jul 19 17:40:41 2026
    From Newsgroup: alt.os.linux.mint

    On Sun, 7/19/2026 3:09 PM, Mike Easter wrote:
    pinnerite wrote:
    Then restored a backup of the database from another machine running kernel 6.8.0-84. When I restored this on the first machine, it caused MythTV to no longer be able to get live TV.

    Linux MythTV:

    MythTV stores all of its configuration, Electronic Program Guide (EPG) data, and recording schedules in a relational (remove this one MariaDB or) MySQL database named mythconverg. This database consists of over 100 interconnected tables that are generated and maintained automatically by the MythTV backend.

    It doesn't seem that there should be some disaster between kernel -84
    and -134 since they are both 6.8.0-.

    I asked gglAIov about this and it said:

    When MythTV reports a database incompatibility after a Linux kernel
    update (like moving from 6.8.0-84 to 6.8.0-134), it usually means
    the backend package was also upgraded. The new software version
    requires a schema update for the mythconverg database.

    ... Not quite the same as the issue here, but close enough for a resemblance.-a Then it tells how to do the schema update.

    If you care to see that, here's the link; personally I know nothing about mythtv OR schema updating NOR proper disaster preparation for kernal hijinks:

    https://share.google/aimode/LxsLDnTRdTJwelkeo


    This premise seems highly unlikely somehow.

    I would consider the possibilities like this:

    1) Something is extremely broken. The file has not been
    located at all. Nothing has been loaded. A fatal error
    was thrown. Check the configuration to make sure the
    file is being picked up.

    2) If there is a versioning issue, you'd check the log the
    database software keeps, for evidence of "I've eaten some
    of this file, and I don't feel well".

    You need concrete evidence of mischief, not just a hint of mischief,
    to go to the trouble of messing around other stuff.

    When the new setup has a TV Tuner card, the hardware instance
    has changed, some addressing has changed. It's not the database
    itself which is corrupt, it's the pointer to the hardware that
    needs to be corrected for the new box. The MythTV software should
    then reach into the database and change the pointer to the hardware
    to match the real hardware on the current box. A configuration issue
    (the part I hate about MythTV), as I've tried to set up MythTV before
    the Alan era, and was defeated by the issue. I could not get the
    miserable thing to pick up my tuner. I've tried MythTV more than
    once, and on *one* occasion, I did get it working. But that was
    more luck than skill, as I likely was flailing about enough, to
    not even be able to make notes of what worked.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Wed Jul 22 10:53:35 2026
    From Newsgroup: alt.os.linux.mint

    On Sun, 7/19/2026 7:23 AM, pinnerite wrote:
    I built a Mint 22.3 machine from scratch.
    Now using kernel 6.8.0-134

    Installed MythTV 35 and got it working fine.

    Then restored a backup of the database from another machine running
    kernel 6.8.0-84. When I restored this on the first machine, it caused
    MythTV to no longer be able to get live TV.

    After hours of testsand faffing about ChatGPT decided I should install
    kernel 6.8.0-84 on the first machine. The problem is I cannot access
    and download it!



    I managed to make a recording in this God-forsaken piece of software.

    WHAT A MESS

    It's no wonder everything is a struggle in there. It's a click based NIGHTMARE!

    The mysql has an API version, which could change between releases.

    Database schema version is 1379

    But as for lugging that around, it is far from "portable", so
    there must be some pile of "tricks" to not dropping random bits
    of the thing on the floor and breaking it. It's not really mysql,
    it's innoDB.

    I still don't have LiveTV yet either, and my transcode is
    not configured, so I can't watch anything. But I found the file
    (or rather VLC found it), and I can play the file from /data/storgroup .
    I can't even understand why, if the OTA signal is mpeg2, why this
    stuff doesn't just fucking well work. Why would mpeg2 need
    to be transcoded to be viewed ??? I had some files (.wtv) from Media Center, which could be played using ffplay, just by identifying the
    audio and video stream (as the ts varies from station to station,
    and by program as well).

    [Picture]

    https://imgur.com/a/PDEZUm6

    https://i.postimg.cc/Hn421w2r/mythtv-web.jpg

    And ChatGPT must be out of its mind, if it thinks a kernel change
    is going to magically fix all this. There are just too many
    moving parts for practical usage.

    I don't understand, if the idea of the Linux desktop is to provide
    automation and smart ways of doing things, how does MythTV exemplify
    this trend ? This is probably the hardest I've worked, to get
    any single "application" to work on a computer! It would be faster
    for me to write my own code. As after all, VLC and plugging in the
    channel frequency from w_scan/w-scan package, and I can be instantly
    watching TV without all this faff (to get to the VLC level, takes
    about ten minutes work). I notice my TV station has moved from VHF to UHF, presumably so that some day VHF can be sold off for cellphones to use :-/

    Oh, and by the way, I didn't have to compile a driver :-) Lucky, eh?
    The firmware needed, isn't in /lib/firmware, but that didn't take
    too long to track down. A little rmmod saa7164 and modprobe saa7164
    and the firmware got picked up the first time. HVR2255 card.

    I couldn't possibly tell you how to fix that, as there is
    no readout for that "bag of files" they call a database. At
    least with sqlite files, You can beat them about, with .dump
    commands and have some idea what tables are in there. And there
    is also an sqlitebrowser you can use for looking at sqlite files.
    The mythconverg doesn't have the recordings in it, presumably
    just the metadata lives there. But as for the "design" of this
    database, I have no way to view it. Sure, there's a folder with
    the tables stored as separate files, but that's the limit of my
    view of the thing.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Wed Jul 22 19:22:36 2026
    From Newsgroup: alt.os.linux.mint

    On Wed, 7/22/2026 10:53 AM, Paul wrote:
    On Sun, 7/19/2026 7:23 AM, pinnerite wrote:
    I built a Mint 22.3 machine from scratch.
    Now using kernel 6.8.0-134

    Installed MythTV 35 and got it working fine.

    Then restored a backup of the database from another machine running
    kernel 6.8.0-84. When I restored this on the first machine, it caused
    MythTV to no longer be able to get live TV.

    After hours of testsand faffing about ChatGPT decided I should install
    kernel 6.8.0-84 on the first machine. The problem is I cannot access
    and download it!



    I managed to make a recording in this God-forsaken piece of software.

    WHAT A MESS

    It's no wonder everything is a struggle in there. It's a click based NIGHTMARE!

    The mysql has an API version, which could change between releases.

    Database schema version is 1379

    But as for lugging that around, it is far from "portable", so
    there must be some pile of "tricks" to not dropping random bits
    of the thing on the floor and breaking it. It's not really mysql,
    it's innoDB.

    I still don't have LiveTV yet either, and my transcode is
    not configured, so I can't watch anything. But I found the file
    (or rather VLC found it), and I can play the file from /data/storgroup .
    I can't even understand why, if the OTA signal is mpeg2, why this
    stuff doesn't just fucking well work. Why would mpeg2 need
    to be transcoded to be viewed ??? I had some files (.wtv) from Media Center, which could be played using ffplay, just by identifying the
    audio and video stream (as the ts varies from station to station,
    and by program as well).

    [Picture]

    https://imgur.com/a/PDEZUm6

    https://i.postimg.cc/Hn421w2r/mythtv-web.jpg

    And ChatGPT must be out of its mind, if it thinks a kernel change
    is going to magically fix all this. There are just too many
    moving parts for practical usage.

    I don't understand, if the idea of the Linux desktop is to provide
    automation and smart ways of doing things, how does MythTV exemplify
    this trend ? This is probably the hardest I've worked, to get
    any single "application" to work on a computer! It would be faster
    for me to write my own code. As after all, VLC and plugging in the
    channel frequency from w_scan/w-scan package, and I can be instantly
    watching TV without all this faff (to get to the VLC level, takes
    about ten minutes work). I notice my TV station has moved from VHF to UHF, presumably so that some day VHF can be sold off for cellphones to use :-/

    Oh, and by the way, I didn't have to compile a driver :-) Lucky, eh?
    The firmware needed, isn't in /lib/firmware, but that didn't take
    too long to track down. A little rmmod saa7164 and modprobe saa7164
    and the firmware got picked up the first time. HVR2255 card.

    I couldn't possibly tell you how to fix that, as there is
    no readout for that "bag of files" they call a database. At
    least with sqlite files, You can beat them about, with .dump
    commands and have some idea what tables are in there. And there
    is also an sqlitebrowser you can use for looking at sqlite files.
    The mythconverg doesn't have the recordings in it, presumably
    just the metadata lives there. But as for the "design" of this
    database, I have no way to view it. Sure, there's a folder with
    the tables stored as separate files, but that's the limit of my
    view of the thing.


    There is some available info, about migrating a backend.

    https://forum.mythtv.org/viewtopic.php?t=6232

    https://wiki.mythtv.org/wiki/Backend_migration

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.os.linux.mint on Thu Jul 23 01:10:25 2026
    From Newsgroup: alt.os.linux.mint

    On Wed, 22 Jul 2026 10:53:35 -0400, Paul wrote:

    The mysql has an API version, which could change between releases.

    Database schema version is 1379

    Been there, done that. This is why I donrCOt backup binary MySQL/MariaDB database files any more.

    Use the mariadb-dump command. This will output a (potentially large)
    file containing the exact SQL commands needed to recreate the
    database, including the saved counters for autoincrement fields --
    everything. You can feed that file into the mariadb command on the new installation to recreate the database.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.os.linux.mint on Thu Jul 23 01:36:40 2026
    From Newsgroup: alt.os.linux.mint

    On Wed, 22 Jul 2026 10:53:35 -0400, Paul wrote:

    I couldn't possibly tell you how to fix that, as there is no readout
    for that "bag of files" they call a database. At least with sqlite
    files, You can beat them about, with .dump commands and have some
    idea what tables are in there. And there is also an sqlitebrowser
    you can use for looking at sqlite files.

    Both SQLite and MariaDB/MySQL have command-line clients that let you
    introspect the database and otherwise mess about with it.

    In the rCLsqlite3rCY tool, the rCL.schemarCY command shows you the database structure. With the rCLmariadbrCY tool, you can type rCLshow columns from -2table-+;rCY for a brief summary, or rCLshow create table -2table-+;rCY for the
    full details.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From pinnerite@pinnerite@gmail.com to alt.os.linux.mint on Thu Jul 23 20:51:01 2026
    From Newsgroup: alt.os.linux.mint

    On Sun, 19 Jul 2026 12:23:12 +0100
    pinnerite <pinnerite@gmail.com> wrote:

    I built a Mint 22.3 machine from scratch.
    Now using kernel 6.8.0-134

    Installed MythTV 35 and got it working fine.

    Then restored a backup of the database from another machine running
    kernel 6.8.0-84. When I restored this on the first machine, it caused
    MythTV to no longer be able to get live TV.

    After hours of testsand faffing about ChatGPT decided I should install
    kernel 6.8.0-84 on the first machine. The problem is I cannot access
    and download it!


    After faffing about for days I gave it one last try today.
    Once again for the nth time I deleted the capture card entries and then rebuilt them again.
    This time LiveTV came up.

    I cannot explain why. I hate it when that happens.
    --
    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.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Thu Jul 23 17:49:33 2026
    From Newsgroup: alt.os.linux.mint

    On Thu, 7/23/2026 3:51 PM, pinnerite wrote:
    On Sun, 19 Jul 2026 12:23:12 +0100
    pinnerite <pinnerite@gmail.com> wrote:

    I built a Mint 22.3 machine from scratch.
    Now using kernel 6.8.0-134

    Installed MythTV 35 and got it working fine.

    Then restored a backup of the database from another machine running
    kernel 6.8.0-84. When I restored this on the first machine, it caused
    MythTV to no longer be able to get live TV.

    After hours of testsand faffing about ChatGPT decided I should install
    kernel 6.8.0-84 on the first machine. The problem is I cannot access
    and download it!


    After faffing about for days I gave it one last try today.
    Once again for the nth time I deleted the capture card entries and then rebuilt them again.
    This time LiveTV came up.

    I cannot explain why. I hate it when that happens.


    It's frustrating software for sure.

    It reminds me of why I don't watch TV :-)

    It's so much easier, to use VLC and just
    dial in the frequency and instantly I can
    be watching TV that way. VLC plus w-scan package
    plus of course the firmware for the tuner card
    (if it is missing).

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2