myth-backend started before kernel driver it needs

Thank you for helping to improve Mythbuntu by opening this ticket. I am marking this ticket as confirmed because it appears to have enough information to help the developers understand the problem. It is possible I am wrong and another more experienced triager or developer may adjust the status of the ticket to "incomplete" and request additional information.

Bug marked as duplicate of this one has a suggestion:

I managed to get both cards working by playing with the /etc/init/mythtv-backend.conf file.

added "and started mysql and started udev-finish" to the dependencies

start on (local-filesystems and net-device-up IFACE=lo and started mysql and started udev-finish)

adding "and started mysql and started udev-finish" to /etc/init/mythtv-backend.conf worked for me too. It seems like the right fix. So who has the ability to roll it out?

Does adding just "started udev-finish" appear to work OK for you? The worry
with adding a dependency on mysql is that not all mythtv installs with a
backend will have mysql available.

On Wed, Apr 21, 2010 at 00:46, Joel Schopp <email address hidden> wrote:

> adding "and started mysql and started udev-finish" to /etc/init/mythtv-
> backend.conf worked for me too. It seems like the right fix. So who
> has the ability to roll it out?
>
> --
> myth-backend started before kernel driver it needs
> https://bugs.launchpad.net/bugs/556204
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to Mythbuntu.
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Triaged
> Status in “mythtv” package in Ubuntu: Triaged
>
> Bug description:
> In Lucid there isn't a dependency for myth-backend on kernel modules being
> loaded. The result is that it can run before the kernel module for the
> hardware is finished loading. The error looks like this in
> /var/log/myth/mythbackend.log
>
> 2010-04-05 22:06:05.431 DVBChan(3:/dev/dvb/adapter0/frontend0) Warning:
> Opening DVB frontend device failed.
> eno: No such file or directory (2)
> 2010-04-05 22:06:05.482 DVBChan(3:/dev/dvb/adapter0/frontend0) Error:
> Failed to open DVB frontend device due to fatal error or too many attempts.
> 2010-04-05 22:06:05.525 New DB connection, total: 3
> 2010-04-05 22:06:05.550 Connected to database 'mythconverg' at host:
> localhost
> 2010-04-05 22:06:05.566 mythbackend: Problem with capture cards: Card
> 3failed init
> 2010-04-05 22:06:05.633 DVBChan(4:/dev/dvb/adapter0/frontend0) Warning:
> Opening DVB frontend device failed.
> eno: No such file or directory (2)
> 2010-04-05 22:06:05.649 DVBChan(4:/dev/dvb/adapter0/frontend0) Error:
> Failed to open DVB frontend device due to fatal error or too many attempts.
> 2010-04-05 22:06:05.761 mythbackend: Problem with capture cards: Card
> 4failed init
> 2010-04-05 22:06:05.783 DVBChan(5:/dev/dvb/adapter1/frontend0) Warning:
> Opening DVB frontend device failed.
> eno: No such file or directory (2)
> 2010-04-05 22:06:05.790 DVBChan(5:/dev/dvb/adapter1/frontend0) Error:
> Failed to open DVB frontend device due to fatal error or too many attempts.
> 2010-04-05 22:06:05.800 mythbackend: Problem with capture cards: Card
> 5failed init
> 2010-04-05 22:06:05.807 MythBackend, Error: No valid capture cards are
> defined in the database.
> Perhaps you should re-read the installation
> instructions?
> 2010-04-05 22:06:05.817 mythbackend: No capture cards are defined: Please
> run the setup program.
>
> My current hack, which fixes the problem but is totally the wrong thing to
> do, is to add the following line to /etc/init/mythtv-backend.conf
>
> /bin/sleep 60
>
> Instead a proper dependency needs to be added in there, I just don't know
> enough about upstart to know how to do it.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mythbuntu-bugs
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mythbuntu-b...

Just took out the "and started mysql" part and left "and started udev-finish" and it seems to run fine.

OK, then we'll just need to do some regression testing to make sure this
isn't inducing another race condition between gdm and mythbackend (that's my
worry now)

On Wed, Apr 21, 2010 at 01:16, Joel Schopp <email address hidden> wrote:

> Just took out the "and started mysql" part and left "and started udev-
> finish" and it seems to run fine.
>
> --
> myth-backend started before kernel driver it needs
> https://bugs.launchpad.net/bugs/556204
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to Mythbuntu.
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Triaged
> Status in “mythtv” package in Ubuntu: Triaged
>
> Bug description:
> In Lucid there isn't a dependency for myth-backend on kernel modules being
> loaded. The result is that it can run before the kernel module for the
> hardware is finished loading. The error looks like this in
> /var/log/myth/mythbackend.log
>
> 2010-04-05 22:06:05.431 DVBChan(3:/dev/dvb/adapter0/frontend0) Warning:
> Opening DVB frontend device failed.
> eno: No such file or directory (2)
> 2010-04-05 22:06:05.482 DVBChan(3:/dev/dvb/adapter0/frontend0) Error:
> Failed to open DVB frontend device due to fatal error or too many attempts.
> 2010-04-05 22:06:05.525 New DB connection, total: 3
> 2010-04-05 22:06:05.550 Connected to database 'mythconverg' at host:
> localhost
> 2010-04-05 22:06:05.566 mythbackend: Problem with capture cards: Card
> 3failed init
> 2010-04-05 22:06:05.633 DVBChan(4:/dev/dvb/adapter0/frontend0) Warning:
> Opening DVB frontend device failed.
> eno: No such file or directory (2)
> 2010-04-05 22:06:05.649 DVBChan(4:/dev/dvb/adapter0/frontend0) Error:
> Failed to open DVB frontend device due to fatal error or too many attempts.
> 2010-04-05 22:06:05.761 mythbackend: Problem with capture cards: Card
> 4failed init
> 2010-04-05 22:06:05.783 DVBChan(5:/dev/dvb/adapter1/frontend0) Warning:
> Opening DVB frontend device failed.
> eno: No such file or directory (2)
> 2010-04-05 22:06:05.790 DVBChan(5:/dev/dvb/adapter1/frontend0) Error:
> Failed to open DVB frontend device due to fatal error or too many attempts.
> 2010-04-05 22:06:05.800 mythbackend: Problem with capture cards: Card
> 5failed init
> 2010-04-05 22:06:05.807 MythBackend, Error: No valid capture cards are
> defined in the database.
> Perhaps you should re-read the installation
> instructions?
> 2010-04-05 22:06:05.817 mythbackend: No capture cards are defined: Please
> run the setup program.
>
> My current hack, which fixes the problem but is totally the wrong thing to
> do, is to add the following line to /etc/init/mythtv-backend.conf
>
> /bin/sleep 60
>
> Instead a proper dependency needs to be added in there, I just don't know
> enough about upstart to know how to do it.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mythbuntu-bugs
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mythbuntu-bugs
> More help : https://help.launchpad.net/ListHelp
>

--
Mario Limonciello
superm1@gmai...

I'm running 10.04 with the recent 0.23 auto-builds and I have a dual tuner HVR-2200 card.

This combination has the same on boot race condition where the dual DVB-T tuners are still initialising after the backend has started and the devices are then missing from the available tuners.

Modifying /etc/init/mythtv-backend.conf to contain "and started udev-finish" as suggested above has resolved the problem.

Just confirming that I also have this problem and that this fix solved it. The line for me is now:
start on (local-filesystems and net-device-up IFACE=lo and started udev-finish)

Mythtv-frontend now starts before the backend is ready, but this is fine as the frontend automatically keeps retrying until it comes up. There don't seem to be any other ill effects.

Same problem here with a Hauppauge HVR-1110 - mythbackend is too fast for udev and adding the dependency solved this problem.

I wonder if this bug and https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/486264 are related.

I've pushed this change to the 0.24 auto-builds. I'm currently looking at how to add this to the 0.23 autobuild.

The upstart script change has been pushed to autobuilds for 0.23 and 0.24. These should show up in tomorrows builds.

This bug was fixed in the package mythtv - 0.23.0+fixes25138-0ubuntu1

---------------
mythtv (0.23.0+fixes25138-0ubuntu1) maverick; urgency=low

  [ Mario Limonciello ]
  * new upstream checkout (25138)

  [ Thomas Mashos ]
  * Added missingok for mirobridge log in logrotate (LP: #581283)
  * Backend now waits for udev to finish (LP: #556204)
  * Added patch to properly detect dbus during compile (LP: #574877)
 -- Mario Limonciello <email address hidden> Sun, 20 Jun 2010 00:11:00 -0500

When I checked https://launchpad.net/ubuntu/+source/mythtv/0.23.0+fixes25138-0ubuntu1 it seems this fix is in state "Failed to build". What does is mean?

It means that particular build failed. Shouldn't matter though because it was a 0.23.0 build for Maverick. Maverick shipped with a newer version (0.23.1). All Mythbuntu supported releases have newer versions available now anyway, so you might want to try those. I doubt you can even get that version anymore. Everything should have a newer version available and the only thing that has failed to build lately was the 0.24 mythplugins

I am having a similar problem with the Nebula DigiTV card. The change to mythtv-backend.conf has not resolved the problem for me. Please also see this bug:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368215

Me too.

I have just done a clean install with the latest Ubuntu and Mythtv on a PC with a Nebula PCI card.

I can watch live TV by running mplayer from a terminal, but Mythtv will not find any channels.