Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

Lirc broken again

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


philledwards at gmail

May 7, 2010, 5:11 AM

Post #1 of 5 (475 views)
Permalink
Lirc broken again

I'm running Fedora 12 and have just upgraded from 0.22 to 0.23 using
the ATrpms repo. Unfortunately this has resulted in lirc not working
yet again. It really does seem to be a bit of a problem child, does
lirc.

I found a thread at
http://old.nabble.com/wrong-major-number-problem-td28133597.html which
looked like the same symptoms as I'm getting, but the solution there
was to recompile from source. I only install from binary rpms so this
isn't an option for me.

This is what I see in /var/log/messages after booting:

May 7 22:07:07 elm lircd-0.8.6[1166]: lircd(default) ready, using
/var/run/lirc/lircd
May 7 22:07:15 elm smbd[1395]: [2010/05/07 22:07:15, 0]
smbd/server.c:457(smbd_open_one_socket)
May 7 22:07:15 elm smbd[1395]: smbd_open_once_socket:
open_socket_in: Address already in use
May 7 22:07:15 elm smbd[1395]: [2010/05/07 22:07:15, 0]
smbd/server.c:457(smbd_open_one_socket)
May 7 22:07:15 elm smbd[1395]: smbd_open_once_socket:
open_socket_in: Address already in use
May 7 22:07:17 elm kernel: lirc_dev: IR Remote Control driver
registered, major 249
May 7 22:07:18 elm kernel: lirc_serial: auto-detected active high receiver
May 7 22:07:18 elm kernel: lirc_serial lirc_serial.0: lirc_dev:
driver lirc_serial registered at minor = 0
May 7 22:07:19 elm kernel: agpgart-intel 0000:00:00.0: AGP 3.0 bridge
May 7 22:07:19 elm kernel: agpgart-intel 0000:00:00.0: putting AGP V3
device into 8x mode
May 7 22:07:19 elm kernel: nvidia 0000:01:00.0: putting AGP V3 device
into 8x mode
May 7 22:07:20 elm acpid: client connected from 1460[0:500]
May 7 22:07:20 elm acpid: 1 client rule loaded
May 7 22:07:23 elm lircd-0.8.6[1166]: accepted new client on
/var/run/lirc/lircd
May 7 22:07:23 elm lircd-0.8.6[1166]: could not get hardware features
May 7 22:07:23 elm lircd-0.8.6[1166]: this device driver does not
support the LIRC ioctl interface
May 7 22:07:23 elm lircd-0.8.6[1166]: major number of /dev/lirc0 is 249
May 7 22:07:23 elm lircd-0.8.6[1166]: LIRC major number is 61
May 7 22:07:23 elm lircd-0.8.6[1166]: check if /dev/lirc0 is a LIRC device
May 7 22:07:23 elm lircd-0.8.6[1166]: Failed to initialize hardware
May 7 22:07:23 elm lircd-0.8.6[1166]: accepted new client on
/var/run/lirc/lircd
May 7 22:07:25 elm lircd-0.8.6[1166]: accepted new client on
/var/run/lirc/lircd
May 7 22:07:31 elm lircd-0.8.6[1166]: accepted new client on
/var/run/lirc/lircd
...
May 7 22:07:39 elm kernel: lirc_serial: ignoring spike: 0 0 4be4028b
4be4028b 7b53d 7b518
May 7 22:08:19 elm kernel: lirc_serial: ignoring spike: 0 0 4be402b3
4be402b3 85bd9 85bb2
May 7 22:08:28 elm kernel: lirc_serial: ignoring spike: 0 0 4be402bc
4be402bc 87726 87700
May 7 22:09:18 elm kernel: lirc_serial: ignoring spike: 0 0 4be402ee
4be402ee 93512 934eb
May 7 22:09:34 elm kernel: lirc_serial: ignoring spike: 0 0 4be402fe
4be402fe 973a9 97384
May 7 22:09:45 elm kernel: lirc_serial: ignoring spike: 0 0 4be40309
4be40309 99e83 99e5c
May 7 22:09:48 elm kernel: lirc_serial: ignoring spike: 0 0 4be4030c
4be4030c 9ae19 9adf2
May 7 22:09:50 elm kernel: lirc_serial: ignoring spike: 0 0 4be4030e
4be4030e 9b879 9b853

Any ideas what I need to do to fix this?

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


philledwards at gmail

May 7, 2010, 6:12 AM

Post #2 of 5 (479 views)
Permalink
Re: Lirc broken again [In reply to]

This looks very similar (identical maybe) to
http://old.nabble.com/trouble-using-lirc-on-fc12-%28wrong-major-node-number-for-device-%29%60-td27540791.html.
Fedora 12, serial IR receiver, and inconsistencies in the device major
number.

Problem is, there wasn't a fix there - just an acknowledgement that
there may be a problem with lirc and serial receivers.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


gaberubin at gmail

May 7, 2010, 9:23 AM

Post #3 of 5 (465 views)
Permalink
Re: Lirc broken again [In reply to]

On Fri, May 7, 2010 at 6:12 AM, Phill Edwards <philledwards [at] gmail> wrote:
> This looks very similar (identical maybe) to
> http://old.nabble.com/trouble-using-lirc-on-fc12-%28wrong-major-node-number-for-device-%29%60-td27540791.html.
> Fedora 12, serial IR receiver, and inconsistencies in the device major
> number.
>
> Problem is, there wasn't a fix there - just an acknowledgement that
> there may be a problem with lirc and serial receivers.

Odds are your problem is not the same as the one I just encountered
(you are using a serial ir receiver and I was using the one that came
with my pvr-350); however, it is possible. Upgrading the kernel
enabled a new lirc driver that took over /dev/lirc0 and I had to
blacklist it. You may want to do a lsmod |grep lirc to see if that is
happening to you. Here is the thread that explains more with Jarod's
fix: http://www.gossamer-threads.com/lists/mythtv/users/434728?search_string=lirc;#434728
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


philledwards at gmail

May 7, 2010, 9:07 PM

Post #4 of 5 (460 views)
Permalink
Re: Lirc broken again [In reply to]

> Odds are your problem is not the same as the one I just encountered
> (you are using a serial ir receiver and I was using the one that came
> with my pvr-350); however, it is possible.  Upgrading the kernel
> enabled a new lirc driver that took over /dev/lirc0 and I had to
> blacklist it.  You may want to do a lsmod |grep lirc to see if that is
> happening to you.  Here is the thread that explains more with Jarod's
> fix: http://www.gossamer-threads.com/lists/mythtv/users/434728?search_string=lirc;#434728

Yeah, I saw that post when I was trying to figure out how to fix this.
I don't think I've got the same issue that you had because I only have
these serial devices when I do lsmod, and these were the ones that
have always been loaded.

# lsmod | grep -i lirc
lirc_serial 9969 0
lirc_dev 12341 1 lirc_serial

# dmesg | grep lirc
lirc_dev: IR Remote Control driver registered, major 249
lirc_serial: auto-detected active high receiver
lirc_serial lirc_serial.0: lirc_dev: driver lirc_serial registered
at minor = 0

I'm not really sure what to do with this one as it sounds like there's
a bug. Jarod's end comments on the post at
http://old.nabble.com/trouble-using-lirc-on-fc12-%28wrong-major-node-number-for-device-%29%60-td27540791.html
were "But you're the second person I've seen with this same problem.
I'll have to dig out some serial hardware and see if I can reproduce
the problem here".

If I revert to an earlier kernel version might that solve things at
least for now?

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


philledwards at gmail

May 7, 2010, 9:32 PM

Post #5 of 5 (455 views)
Permalink
Re: Lirc broken again [In reply to]

I think I've fixed this. The problem was that with the upgrade (using
yum update), there was a new kernel installed as well as a new version
of lirc. The default kernel to boot in grub, however, was the OLD
kernel not the new one, so the machine was booting up the old kernel
which I presume is incompatible in some way with the new version of
lirc. Now that I've forced it to boot into the new kernel, lirc is
working again.

For the record my versions are:
kernel - 2.6.32.11-99.fc12.i686
lirc - 0.8.6-6.fc12

Hope that helps anyone else who runs into this.

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

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.