[mythtv-users] Lirc not working after update

[jonny Linux]

On 10/31/05, Minh Duong <minh_duong at yahoo.com> wrote:
>
> After I updated using apt-get update and apt-get
> dist-upgrade, lirc seems not to be working. I searched
> the archived and there was some discussion at the
> beginning of the month with FC4, but so solution was
> posted. For some reason, /dev/lirc is not being
> created. Instead there is /dev/lircd. When trying to
> load the module manually with modprobe lirc_i2c, the
> module won't load. From the log files:
>
> ----
> Oct 30 17:39:38 star lircd-0.7.2[2654]: lircd(any)
> ready
> Oct 30 17:39:38 star lircd: lircd startup succeeded
> Oct 30 17:39:57 star lircd-0.7.2[2654]: accepted new
> client on /dev/lircd
> Oct 30 17:39:57 star lircd-0.7.2[2654]: could not get
> file information for /dev/lirc
> Oct 30 17:39:57 star lircd-0.7.2[2654]:
> default_init(): No such file or directory
> Oct 30 17:39:57 star lircd-0.7.2[2654]: caught signal
> ---



I don't know if this is the same problem, but I have a FC3 machine, and I
did a yum update a couple of days ago. It installed kernel 2.6.12-1.1381_FC3,
and when I boot this kernel it gives me no /dev/lirc0, only a /dev/lircd, so
lirc doesn't work.

If I reboot to the previous kernel, 2.6.12-1.1376_FC3, /dev/lirc0 and
/dev/lircd are both created and lirc works.

I'm using a custom built lirc_serial device, so I assumed the lirc_serial
device hasn't been compiled into the updated kernel. Could this be your
problem? Can you try rebooting to an older kernel?

Jonny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20051101/98a8892d/attachment.htm