Re: Lircd tainted

[Axel T. <Axel.Thimm@ATrpms.net>]

Hi,

On Sat, Jan 24, 2009 at 01:17:53AM -0500, John H wrote:
> I'm trying to solve a problem that has recently come up. I am now
> getting a lircd Tainted error in my dmesg and then I have to reboot to
> get my remote back. I was using the 0.8.4a package on Fedora 8 from
> atrpms.net. I figured this version was my problem so I downgraded to
> 0.8.3 and this didn't solve my problem. I'm running two instances of
> lirc with one being lirc_serial for my blaster and I'm also running a
> custom module from usbirboy. I've never had a problem in the past so
> I'm not sure if it's my rev of lircd or my kernel. The lircd tainted
> happens after about a couple of hours or so after I reboot on my
> MythTv system. My kernel is 2.6.26.8-57.fc8. If need be, I could
> compile lirc if it will solve my problem. Can anyone point me in the
> right directions?

recently Jarod pointed out to me that ATrpms should not be shipping
lirc for Fedora anymore as he's been keeping lirc up to good shape
within the main Fedora repos directly (thanks for that!).

As this also was an argument for him not wanting to use ATrpms I
decided to pass over the builds from ATrpms to him and comaintainers
to defuse it.

This means that for 2.6.26.8-57.fc8 you may have not received lirc
kmdl upgrades, and the way to describe your manual upgrades/downgrades
you may have a mixed system now. The best way to proceed is to remove
all lirc bits from your system and reinstall Jarod's from the main
Fedora repos (Everything and/on updates):

rpm -qa lirc\* | xargs rpm -e --nodeps --allmatches
yum install lirc

Since there are no lirc packages at ATrpms anymore for Fedora the
latter will pick up Jarod's. Then check to see if the issues are all
gone. If not please report again with the exact lines from dmesg.
-- 
Axel.Thimm at ATrpms.net