Mailing List Archive: MythTV: Users

Lircd starting too late?

Index | Next | Previous | View Threaded

mail at benlancaster

Jul 6, 2009, 2:10 PM

Post #1 of 6 (784 views)
Permalink

Lircd starting too late?

Hi,

I've been experiencing a few problems with LIRC starting too late from
cold boots (or after a hard reset), in that Xorg and Mythfrontend
start up before the lircd process so mythfrontend is unable to connect
to the lircd device. Restarting Mythfrontend fixes it, but it'd be
nice to figure out a permenant fix. The other symptom is that
mythlcdserver is unable to make use of the VFD in my case unless I
kill and restart mythlcdserver.

I'm running Mythbuntu 9.10 with Avenard's packages (didn't work with
the Mythbuntu debs either), and replaced XFCE with Ratpoison. The
remove uses the lirc_mceusb2, and the VFD uses the lirc_imon kmod.

Here's what Mythfrontend says:

mythtv: could not connect to socket
mythtv: No such file or directory
2009-07-06 20:03:05.923 lirc_init failed for mythtv, see preceding
messages

I can't see anything untoward in dmesg or messages, and chkconfig
shows that lirc should trigger when entering runlevel 2 through to 5:

# chkconfig --list | grep lirc
lirc 0:off 1:off 2:on 3:on 4:on 5:on
6:off

Thanks in advance for any pointers

Ben
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

digitalaudiorock at gmail

Jul 6, 2009, 2:28 PM

Post #2 of 6 (742 views)
Permalink

Re: Lircd starting too late? [In reply to]

On Mon, Jul 6, 2009 at 5:10 PM, Ben Lancaster<mail [at] benlancaster> wrote:
> Hi,
>
> I've been experiencing a few problems with LIRC starting too late from cold
> boots (or after a hard reset), in that Xorg and Mythfrontend start up before
> the lircd process so mythfrontend is unable to connect to the lircd device.
> Restarting Mythfrontend fixes it, but it'd be nice to figure out a permenant
> fix. The other symptom is that mythlcdserver is unable to make use of the
> VFD in my case unless I kill and restart mythlcdserver.
>
> I'm running Mythbuntu 9.10 with Avenard's packages (didn't work with the
> Mythbuntu debs either), and replaced XFCE with Ratpoison. The remove uses
> the lirc_mceusb2, and the VFD uses the lirc_imon kmod.
>
> Here's what Mythfrontend says:
>
> mythtv: could not connect to socket
> mythtv: No such file or directory
> 2009-07-06 20:03:05.923 lirc_init failed for mythtv, see preceding messages
>
> I can't see anything untoward in dmesg or messages, and chkconfig shows that
> lirc should trigger when entering runlevel 2 through to 5:
>
> # chkconfig --list | grep lirc
> lirc 0:off 1:off 2:on 3:on 4:on 5:on 6:off
>
> Thanks in advance for any pointers
>
> Ben

Here you go:

http://www.gossamer-threads.com/lists/mythtv/users/365421#365421

I can't imagine why Ubuntu starts lirc after gdm...I'd think they'd
have changed that by now.

Tom
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

drayson at net1plus

Jul 6, 2009, 2:37 PM

Post #3 of 6 (733 views)
Permalink

Re: Lircd starting too late? [In reply to]

> Hi,
>
> I've been experiencing a few problems with LIRC starting too late from
> cold boots (or after a hard reset), in that Xorg and Mythfrontend
> start up before the lircd process so mythfrontend is unable to connect
> to the lircd device. Restarting Mythfrontend fixes it, but it'd be
> nice to figure out a permenant fix. The other symptom is that
> mythlcdserver is unable to make use of the VFD in my case unless I
> kill and restart mythlcdserver.
>
> I'm running Mythbuntu 9.10 with Avenard's packages (didn't work with
> the Mythbuntu debs either), and replaced XFCE with Ratpoison. The
> remove uses the lirc_mceusb2, and the VFD uses the lirc_imon kmod.
>
> Here's what Mythfrontend says:
>
> mythtv: could not connect to socket
> mythtv: No such file or directory
> 2009-07-06 20:03:05.923 lirc_init failed for mythtv, see preceding
> messages
>
> I can't see anything untoward in dmesg or messages, and chkconfig
> shows that lirc should trigger when entering runlevel 2 through to 5:
>
> # chkconfig --list | grep lirc
> lirc 0:off 1:off 2:on 3:on 4:on 5:on
> 6:off
>
> Thanks in advance for any pointers
>
> Ben
> _______________________________________________

Whats your dmesg report?
Maybe put a delay on myth to confirm, or restart the frontend/X, not the
entire machine, as that would be pointless.

Marc

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Jul 6, 2009, 2:43 PM

Post #4 of 6 (741 views)
Permalink

Re: Lircd starting too late? [In reply to]

On Monday 06 July 2009 17:28:17 Tom Dexter wrote:
> On Mon, Jul 6, 2009 at 5:10 PM, Ben Lancaster<mail [at] benlancaster> wrote:
> > Hi,
> >
> > I've been experiencing a few problems with LIRC starting too late from cold
> > boots (or after a hard reset), in that Xorg and Mythfrontend start up before
> > the lircd process so mythfrontend is unable to connect to the lircd device.
> > Restarting Mythfrontend fixes it, but it'd be nice to figure out a permenant
> > fix. The other symptom is that mythlcdserver is unable to make use of the
> > VFD in my case unless I kill and restart mythlcdserver.
> >
> > I'm running Mythbuntu 9.10 with Avenard's packages (didn't work with the
> > Mythbuntu debs either), and replaced XFCE with Ratpoison. The remove uses
> > the lirc_mceusb2, and the VFD uses the lirc_imon kmod.
> >
> > Here's what Mythfrontend says:
> >
> > mythtv: could not connect to socket
> > mythtv: No such file or directory
> > 2009-07-06 20:03:05.923 lirc_init failed for mythtv, see preceding messages
> >
> > I can't see anything untoward in dmesg or messages, and chkconfig shows that
> > lirc should trigger when entering runlevel 2 through to 5:
> >
> > # chkconfig --list | grep lirc
> > lirc 0:off 1:off 2:on 3:on 4:on 5:on 6:off
> >
> > Thanks in advance for any pointers
> >
> > Ben
>
> Here you go:
>
> http://www.gossamer-threads.com/lists/mythtv/users/365421#365421
>
> I can't imagine why Ubuntu starts lirc after gdm...I'd think they'd
> have changed that by now.

Wow. Just, wow. Probably also explains the guy who wasn't getting any
vfd data from mythtv to his display unless he restarted mythlcdserver.
LCDd is probably getting started after mythfrontend too or something
along those lines.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

digitalaudiorock at gmail

Jul 6, 2009, 5:39 PM

Post #5 of 6 (740 views)
Permalink

Re: Lircd starting too late? [In reply to]

On Mon, Jul 6, 2009 at 5:43 PM, Jarod Wilson<jarod [at] wilsonet> wrote:
>
> Wow. Just, wow. Probably also explains the guy who wasn't getting any
> vfd data from mythtv to his display unless he restarted mythlcdserver.
> LCDd is probably getting started after mythfrontend too or something
> along those lines.
>
> --
> Jarod Wilson
> jarod [at] wilsonet

Why on earth would they not start gdm dead last???...unless of course
you want to act like Windows where you get a desktop like three
minutes before it's actually ready to use ;).

Tom
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Jul 6, 2009, 6:03 PM

Post #6 of 6 (727 views)
Permalink

Re: Lircd starting too late? [In reply to]

On 07/06/2009 08:39 PM, Tom Dexter wrote:
> On Mon, Jul 6, 2009 at 5:43 PM, Jarod Wilson<jarod [at] wilsonet> wrote:
>> Wow. Just, wow. Probably also explains the guy who wasn't getting any
>> vfd data from mythtv to his display unless he restarted mythlcdserver.
>> LCDd is probably getting started after mythfrontend too or something
>> along those lines.
>
> Why on earth would they not start gdm dead last???...unless of course
> you want to act like Windows where you get a desktop like three
> minutes before it's actually ready to use ;).

Starting gdm sooner that dead last is fine, if you take care that the
things starting *after* it actually work as expected if not started
before it, otherwise, yeah, um, fail... But you're probably right,
"look, we get to the desktop soooo fast, we're swell!" likely sums it
up... Besides, upstart fixed all these sorts of issue. Right?

--
Jarod Wilson
jarod [at] wilsonet

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads