Op donderdag 5 juli 2018 18:21:28 CEST schreef Per Jessen:

Dave Howorth wrote:

...

I'm planning to install MythTV. It's not clear to me so far exactly what I need to install or what I need to do.

YaST lists a bunch of mythtv packages from packman. The latest available seems to be 27 whilst I understand the current version of mythtv is 29. I don't see any particular package that installs it. The closest I have found is mythtv-0_27-setup and its description says "MythTV provides a unified graphical interface for recording and viewing television programs. Refer to the mythtv package for more information. This package contains only the setup software for configuring the mythtv backend."

But there is no mythtv package listed.

Hi Dave

I've been running MythTV for almost six years, overall it works really well.

i | libmyth-0_25 | Library providing mythtv support i | mythtv-0_25-backend | Server component of mythtv (a DVR) i | mythtv-0_25-base-themes | Core user interface themes for mythtv i | mythtv-0_25-common | Common components needed by multiple other MythTV components i | mythtv-0_25-frontend | Client component of mythtv (a DVR) i | mythtv-0_25-setup | Setup the mythtv backend i | mythweb-0_25 | The web interface to MythTV i | perl-MythTV-0_25 | Perl bindings for MythTV i | php-MythTV-0_25 | PHP bindings for MythTV i | python-MythTV-0_25 | Python bindings for MythTV

...

As it happens, I think I do want the backend, because I'm installing a tuner card (TBS6205) so I can record programmes. I intend to then export them over my network to a FireTV box plugged into my TV and running kodi, although I'm open to better ideas.

You're going to need the MythTV frontend to program recordings, I think. Playback over kodi is fine. The web interface is neat, but I don't use it much.

...

google also shows various people apparently overwhelmed by complexity, which is why I'd like to find an accurate set of instructions. Does anybody know of one?

I think my first mythtv setup took a few hours, 3-4-5, I'm not sure. It was in 2012 - old desktop PC with a receiver card, a laptop as frontend. IIRC the mythtv-common triggers install of the basic needs. Did a setup for a friend last year, incl. DVB and PVR, took me an ~5 hours too.. I know they're still using and updating the stuff, but I didn't record the steps I took to get it working. I do remember reading a lot of outdated docs and "rephrasing" commands invoked.

-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, 05 Jul 2018 18:47:17 +0200 Per Jessen wrote:

Knurpht@openSUSE wrote:

...

Op donderdag 5 juli 2018 18:21:28 CEST schreef Per Jessen:

...

I think my first mythtv setup took a few hours, 3-4-5, I'm not sure. It was in 2012 - old desktop PC with a receiver card, a laptop as frontend.

IIRC the mythtv-common triggers install of the basic needs. Did a setup for a friend last year, incl. DVB and PVR, took me an ~5 hours too.

afair, it's not because it is really so complex, it just takes a little time until you have gained an understanding of "how it works". In particular how MythTV works with tuners, channels, sources etc.

I forgot - I even wrote this:

http://rambling.jessen.ch/it/moving-to-mythtv/

Not an installation guide, just a success story!

Thanks Per, Gertjan. mythtv-common doesn't seem to pull in anything at all in YaST but is itself pulled in by mythtv-setup. I'll do a bit more reading until my card arrives and try to make some notes when I do set it up. Most of the documentation refers to mysql; does it work out of the box with mariadb instead, do you know? My experience with mysql just predates the mariadb split, and my dvb experience is even older. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Dave Howorth wrote:

mythtv-common doesn't seem to pull in anything at all in YaST but is itself pulled in by mythtv-setup. I'll do a bit more reading until my card arrives and try to make some notes when I do set it up.

Most of the documentation refers to mysql; does it work out of the box with mariadb instead, do you know? My experience with mysql just predates the mariadb split, and my dvb experience is even older.

Mine is installed with mysql, but I see mariadb was available too at the time. I have both mysql and mariadb installed in a number of places, I have yet to notice any incompatibilities. I know there are some minor ones, I just haven't hit any of them yet. I doubt if you'll notice much difference between the two - maybe in the initial setup work, but not in the database ops. If I were doing a new installation today, I think I would probably try it with mariadb first. -- Per Jessen, Zürich (16.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2018-07-06 07:38, Per Jessen wrote:

Dave Howorth wrote:

...

mythtv-common doesn't seem to pull in anything at all in YaST but is itself pulled in by mythtv-setup. I'll do a bit more reading until my card arrives and try to make some notes when I do set it up.

Most of the documentation refers to mysql; does it work out of the box with mariadb instead, do you know? My experience with mysql just predates the mariadb split, and my dvb experience is even older.

Mine is installed with mysql, but I see mariadb was available too at the time. I have both mysql and mariadb installed in a number of places, I have yet to notice any incompatibilities. I know there are some minor ones, I just haven't hit any of them yet.

I doubt if you'll notice much difference between the two - maybe in the initial setup work, but not in the database ops. If I were doing a new installation today, I think I would probably try it with mariadb first.

My test install of MythTV used mariadb-10 -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)

Dave Howorth wrote:

I just got my TBS6205 card and started trying to install it and mythtv. I'm a bit worried by the ReadMe.txt that comes with the TBS6205 driver zip. It starts with:

#sudo rm -rf /lib/modules/`uname -r`/kernel/drivers/media/

which seems like a rather drastic thing to do. Is that a normal thing to do?

That does sound like overkill. Those modules will likely be rebuilt, but still.

The file then goes on to say:

#tar jxvf media_build-2018-0206.tar.bz2 #cd media_build #./install.sh #reboot

#dmesg | grep tbsversion

Sounds like building the kernel module. You'll need to install the kernel source, if you haven't already.

I'm waiting to be approved to post a question on the TBS forum but I thought I'd ask here first. The good news is that the card is installed and listed by lspci and that mythtv appeared to install OK from YaST.

Sounds good! -- Per Jessen, Zürich (26.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 08 Jul 2018 18:30:15 +0200 Per Jessen wrote:

Per Jessen wrote:

...

Dave Howorth wrote:

...

I just got my TBS6205 card and started trying to install it and mythtv. I'm a bit worried by the ReadMe.txt that comes with the TBS6205 driver zip. It starts with:

#sudo rm -rf /lib/modules/`uname -r`/kernel/drivers/media/

which seems like a rather drastic thing to do. Is that a normal thing to do?

That does sound like overkill. Those modules will likely be rebuilt, but still.

...

The file then goes on to say:

#tar jxvf media_build-2018-0206.tar.bz2 #cd media_build #./install.sh #reboot

#dmesg | grep tbsversion

The instructions here are a little more elaborate, although they also explicitly say that your card is not (yet) supported:

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

Well just above that, the page says "These instructions are taken directly from those pages, e.g. tbs' wiki. Go there for latest official word on build procedure." and if you follow the link then you will find the 6205 card listed as supported. So I suspect the linuxtv page is just out of date. Anyway, I've asked on their forum and will see what they have to say. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, 9 Jul 2018 11:05:28 +0200 "Carlos E. R." wrote:

On 2018-07-09 11:02, Dave Howorth wrote:

...

On Sun, 08 Jul 2018 18:30:15 +0200 Per Jessen <> wrote:

...

Per Jessen wrote:

...

Dave Howorth wrote:

...

I just got my TBS6205 card and started trying to install it and mythtv. I'm a bit worried by the ReadMe.txt that comes with the TBS6205 driver zip. It starts with:

#sudo rm -rf /lib/modules/`uname -r`/kernel/drivers/media/

which seems like a rather drastic thing to do. Is that a normal thing to do?

That does sound like overkill. Those modules will likely be rebuilt, but still.

...

The file then goes on to say:

#tar jxvf media_build-2018-0206.tar.bz2 #cd media_build #./install.sh #reboot

#dmesg | grep tbsversion

The instructions here are a little more elaborate, although they also explicitly say that your card is not (yet) supported:

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

Well just above that, the page says "These instructions are taken directly from those pages, e.g. tbs' wiki. Go there for latest official word on build procedure." and if you follow the link then you will find the 6205 card listed as supported. So I suspect the linuxtv page is just out of date. Anyway, I've asked on their forum and will see what they have to say.

If it were really supported you would not have anything to do. At most, load some module or configure a file or start a service.

Yes, that's my feeling too :( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, 09 Jul 2018 19:21:55 +0200 Per Jessen wrote:

Dave Howorth wrote:

...

On Sun, 08 Jul 2018 18:30:15 +0200 Per Jessen wrote:

...

Per Jessen wrote:

...

Dave Howorth wrote:

...

I just got my TBS6205 card and started trying to install it and mythtv. I'm a bit worried by the ReadMe.txt that comes with the TBS6205 driver zip. It starts with:

#sudo rm -rf /lib/modules/`uname -r`/kernel/drivers/media/

which seems like a rather drastic thing to do. Is that a normal thing to do?

That does sound like overkill. Those modules will likely be rebuilt, but still.

...

The file then goes on to say:

#tar jxvf media_build-2018-0206.tar.bz2 #cd media_build #./install.sh #reboot

#dmesg | grep tbsversion

The instructions here are a little more elaborate, although they also explicitly say that your card is not (yet) supported:

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

Well just above that, the page says "These instructions are taken directly from those pages, e.g. tbs' wiki. Go there for latest official word on build procedure." and if you follow the link then you will find the 6205 card listed as supported. So I suspect the linuxtv page is just out of date.

Sorry, I meant say that too - that you've got some newer source code, so that page needs updating.

Even if it may appear a bit complex, I wouldn't worry about it at all Dave - just crack on and see if you get a module built, then see what happens when you load it. Then back to mythtv.

Hmm, that's my problem, I do worry about it. I don't remember ever building a kernel module, so that's new. I vaguely remember removing and replacing modules, so that bit might come back to me. Then I don't trust instructions that start by telling me to throw out the baby with the bathwater and then rebuild both the baby and the bathwater. I don't mind trying to build a specific new module to interface with this specific new card but I'm very reluctant to replace all the modules in that system directory with code that I've just downloaded from some random site on the internet. And then I don't understand whether firmware is needed and how that whole mechanism works. So I'm fairly far outside my comfort zone at the minute. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Dave Howorth wrote:

On Mon, 09 Jul 2018 19:21:55 +0200 Per Jessen wrote:

...

Even if it may appear a bit complex, I wouldn't worry about it at all Dave - just crack on and see if you get a module built, then see what happens when you load it. Then back to mythtv.

Hmm, that's my problem, I do worry about it. I don't remember ever building a kernel module, so that's new.

It is perhaps a little daunting, but it's really nothing special. If you've ever used the Nvidia drivers, similar procedure. Also, it isn't rebuilding the entire kernel, only that one module.

I vaguely remember removing and replacing modules, so that bit might come back to me.

insmod <module> <options> modprobe <module> <options> rmmode <module> Check output with 'dmesg'.

Then I don't trust instructions that start by telling me to throw out the baby with the bathwater and then rebuild both the baby and the bathwater.

That does seem a little too much, I agree. It is unlikely all of those modules will be affected.

I don't mind trying to build a specific new module to interface with this specific new card but I'm very reluctant to replace all the modules in that system directory with code that I've just downloaded from some random site on the internet.

Right.

And then I don't understand whether firmware is needed and how that whole mechanism works.

For now, you can leave that issue alone - I don't know your card, but if firmware is needed, I would expect it to be loaded later, maybe with some user space utility.

So I'm fairly far outside my comfort zone at the minute.

Do you have a testsystem to try it out on? Any old PC will do. -- Per Jessen, Zürich (19.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2018-07-09 21:22, Dave Howorth wrote:

On Mon, 09 Jul 2018 19:21:55 +0200 Per Jessen <> wrote:

...

Dave Howorth wrote:

...

On Sun, 08 Jul 2018 18:30:15 +0200 Per Jessen wrote:

...

Per Jessen wrote:

...

Dave Howorth wrote:

...

I just got my TBS6205 card and started trying to install it and mythtv. I'm a bit worried by the ReadMe.txt that comes with the TBS6205 driver zip. It starts with:

#sudo rm -rf /lib/modules/`uname -r`/kernel/drivers/media/

which seems like a rather drastic thing to do. Is that a normal thing to do?

That does sound like overkill. Those modules will likely be rebuilt, but still.

It is an overkill, but if you are rebuilding the kernel they get recreated. Problem is, you need to rebuild not only your card module, because the tree holds more than that: Telcontar:~ # ls /lib/modules/4.4.138-59-default/kernel/drivers/media/ common dvb-core dvb-frontends firewire i2c mmc pci platform radio rc tuners usb v4l2-core Telcontar:~ # Why delete firewire, i2c? And then, they are acting on the 32 bit tree, not the 64 bit! I would have a look at what the tar contains, and at what the install script really does. And mind, do all this every time there is a kernel update. Not nice. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)

On 2018-07-10 11:10, Per Jessen wrote:

Carlos E. R. wrote:

...

And then, they are acting on the 32 bit tree, not the 64 bit!

Huh? All kernel modules are in /lib/modules.

Oh, you are right.

...

And mind, do all this every time there is a kernel update. Not nice.

When you are bleeding edge, there will always be blood :-)

Not in Leap... -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)

On Tue, 10 Jul 2018 11:38:21 +0200 Per Jessen wrote:

Carlos E. R. wrote:

...

On 2018-07-10 11:10, Per Jessen wrote:

...

...

And mind, do all this every time there is a kernel update. Not nice.

When you are bleeding edge, there will always be blood :-)

Not in Leap...

Leap isn't bleeding edge though. Leap is bit further behind on the adaption curve. Dave is gingerly trying out the bleeding edge when he needs to use drivers yet to make it into the kernel. Having to rebuild after a kernel update is good practice :-)

Hmm, such niceties escape me, and I suspect also escape the developers involved. Is there a readable explanation anywhere of how the V4L project is supposed to work, from the point of view of a hardware manufacturer's programmers? They're saying I need to use the latest version of the media subsystem. That sounds like it might be a fairly normal situation, and if so, is there an 'approved' way in openSUSE to do that? What makes it more awkward in my case is that they use their own media-build repository, which while open source, appears to contain lots of scripts and potentially code that have been hacked about with somewhat. Plus they develop using ubuntu and centos, not opensuse. So the scripts don't run. And I bought this card because I had read that TBS linux support was good ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/20/2018 10:15 AM, Dave Howorth wrote:

I notice that something has set up a system user 'mythtv' but I don't know exactly how setup is done. Should I su to that user before I start?

Funny how documentation is always an after-thought.... When suse moved to systemd, I don't think the yast informational tips/descriptions, etc.. received a rework. At least with systemd it is just about as easy to manage from the command-line as the init scripts were. In the case of a service like mariadb, it's just a systemctl status mariadb ## is it enabled/running? Not enabled? systemctl enable mariadb ## will now start on boot systemctl start mariadb ## start it now, since it wasn't on boot (process works in reverse with 'stop' and 'disable' to have it no longer start at boot) Glad to see you are making progress with MythTV. It's sounds like a rather large and sprawling setup -- made more challenging based on the kernel backports. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org