On Thu, Nov 16, 2006 at 02:07:45PM +0000, Seán O Sullivan wrote: > Deon Bredenhann wrote: > > Hi all > > > > I just upgraded from 2.6.9-34.0.2.EL to 2.6.9-42.0.3.EL > > And I have the following installed > > lirc-kmdl-2.6.9-34.0.2.EL-0.8.0-55.el4.at > > lirc-kmdl-2.6.9-42.0.3.EL-0.8.1-63_cvs20060930.el4.at > > lirc-0.8.1-63_cvs20060930.el4.at > > lirc-devices-0.8-3.el4.at > > lirc-lib-0.8.1-63_cvs20060930.el4.at > > And the ivtv kmdls. > > System is a Centos4 with all updates and a Hauppauge PVR 350 > > > > I browsed through the archives a bit and saw a few posts about broken > > lirc after upgrade. I did a few tests and saw that if I boot with the > > previous kernel and keep all the lircd packages the same, lirc seems to > > work fine. So it looks like the problem is in the latest kmdl. > > > > If I do my modprobe for lirc in the latest kernel, I get the following > > in messages. Keeping everything the same, even modprobe.conf and booting > > with previous kernel works fine. > > > > kernel: lirc_dev: Unknown symbol class_device_destroy > > kernel: lirc_dev: Unknown symbol class_device_destroy > > kernel: lirc_i2c: Unknown symbol lirc_unregister_plugin > > kernel: lirc_i2c: Unknown symbol lirc_register_plugin > > > > Anyone out there found a solution for this yet. Should I just run an > > older kernel? > > I'm seeing same issue, although only setup lirc when box had > 2.6.9-42.0.3 kernel, so can't verify it works on older (what is the > latest kernel lirc works on?).
I can confirm that this is a build issue, e.g. the rpms are broken, at least for class_device_destroy, and lirc_*_plugin is probably triggered by that. > Is this issue going to be fixed in later kernel updates, or is it a case > of waiting till rhel5 (when hopefully it will be fixed?). It is certainly fixable, as the issue is that RHEL4's 2.6.9 isn't really 2.6.9 and needs adjustment of the kernel version checks in any kernel module projects. But it needs time to invest, so if someone plays with the sources and finds which conditionals need fixing, I'd be grateful for the (RHEL4 specific) patch. RHEL5 will start from a rathe unmodified kernel and will therefore break less things (as it will not be lying to the external kernel module projects), but in probably 1-2 years you will have the same situation there, too. -- Axel.Thimm at ATrpms.net
pgpCxNjAsd0jw.pgp
Description: PGP signature
_______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
