[elrepo] lirc_serial recommendation?

[Wade Berrier]

On Jan 06 17:56, Phil Perry wrote:
> On 06/01/15 06:04, Wade Berrier wrote:
> > On Jan 04 22:19, Wade Berrier wrote:
> >> On Jan 04 16:50, Phil Perry wrote:
> >>> On 04/01/15 14:10, Phil Perry wrote:
> >>>> On 04/01/15 14:03, Akemi Yagi wrote:
> >>>>> On Sun, Jan 4, 2015 at 4:46 AM, Phil Perry <phil at elrepo.org> wrote:
> >>>>>> On 04/01/15 01:08, Wade Berrier wrote:
> >>>>>>> Hello,
> >>>>>>>
> >>>>>>> What is the recommended way to install or build an lirc_serial package?
> >>>>>>> It's in the kernel staging area.
> >>>>>>>
> >>>>>>> I see that fedora ships staging drivers, but not enterprise linux.
> >>>>>>>
> >>>>>>> I'm specifically interested in el7.
> >>>>>>>
> >>>>>>> Recommendations to proceed?
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>>
> >>>>>>> Wade
> >>>>>
> >>>>>> Hi Wade,
> >>>>>>
> >>>>>> We have two options. We can either build the modules within a kernel or
> >>>>>> build them as standalone kmod (kernel module) packages.
> >>>>>>
> >>>>>> If you are a CentOS user we could ask Akemi if she would consider
> >>>>>> enabling these modules within the CentOS-Plus kernel - that is an el7
> >>>>>> kernel maintained by the CentOS project within which they have the
> >>>>>> flexibility to enable drivers (or apply patches) that Red Hat have
> >>>>>> chosen to ignore.
> >>>>>>
> >>>>>> The other option is that elrepo builds the driver as a standalone kmod
> >>>>>> package for you, backported from the latest 3.10.x kernel.
> >>>>>
> >>>>> The kmod option is the way to go whenever possible.
> >>>>>
> >>>>> The source code that is not enabled in the RHEL kernel is not being
> >>>>> maintained (updated), so it might have bugs and security issues.
> >>>>> Fedora is a moving target and its kernel is much newer.
> >>>>>
> >>>>> In addition, kmods can serve the whole EL community better. Switching
> >>>>> the kernel to the centosplus kernel may not be trivial if you are not
> >>>>> a CentOS user.
> >>>>>
> >>>>> Of course this does not mean I am unwilling to enable it in the plus
> >>>>> kernel. I will do that if a request is made. Then people can have a
> >>>>> choice. :)
> >>>>>
> >>>>> Akemi
> >>>>
> >>>> Thanks Akemi.
> >>>>
> >>>> I'll see if I can make a kmod package for this later today and get it
> >>>> out into the testing repository.
> >>>>
> >>>> Phil
> >>>>
> >>>
> >>> Hi Wade,
> >>>
> >>> I've built a kmod-lirc package from the drivers in staging of
> >>> kernel-3.10.63. It's currently syncing to our mirrors and should show up
> >>> shortly in the testing repository:
> >>>
> >>> http://elrepo.org/linux/testing/el7/x86_64/RPMS/kmod-lirc-0.0-1.el7.elrepo.x86_64.rpm
> >>>
> >>> The package contains the following lirc modules:
> >>>
> >>> /lib/modules/3.10.0-123.el7.x86_64/extra/lirc/lirc_bt829.ko
> >>> /lib/modules/3.10.0-123.el7.x86_64/extra/lirc/lirc_igorplugusb.ko
> >>> /lib/modules/3.10.0-123.el7.x86_64/extra/lirc/lirc_imon.ko
> >>> /lib/modules/3.10.0-123.el7.x86_64/extra/lirc/lirc_parallel.ko
> >>> /lib/modules/3.10.0-123.el7.x86_64/extra/lirc/lirc_sasem.ko
> >>> /lib/modules/3.10.0-123.el7.x86_64/extra/lirc/lirc_serial.ko
> >>> /lib/modules/3.10.0-123.el7.x86_64/extra/lirc/lirc_sir.ko
> >>> /lib/modules/3.10.0-123.el7.x86_64/extra/lirc/lirc_zilog.ko
> >>>
> >>> To test, please install with:
> >>>
> >>> yum --enablerepo=elrepo-testing install kmod-lirc
> >>>
> >>> Please could you let us know how the package works for you. You will
> >>> need to make sure the correct module for your hardware is loaded.
> >>
> >> Wow, thank you for the work on this.  It looks great and I plan on
> >> trying it out in the next few days.  I'll let you know how it goes.
> >>
> > 
> > Looks like something isn't quite right:
> > 
> > ------------------
> > 
> > warning: kmod-lirc-0.0-1.el7.elrepo.x86_64.rpm: Header V4 DSA/SHA1
> > Signature, key ID baadae52: NOKEY
> > ################################# [100%]
> > Updating / installing...
> > ################################# [100%]
> > Working. This may take some time ...
> > sed: -e expression #1, char 36: unterminated `s' command
> > modinfo: ERROR: Module /lib/modules/3.10.0-123.13.2.el7.x86_64/weak-updates/ not found.
> > /sbin/weak-modules: line 226: $tmpdir/extra-symvers-$module_krel: ambiguous redirect
> > sort: cannot read: 3.10.0-123.el7.x86_64: No such file or directory
> > join: extra operand '/tmp/weak-modules.Yzhbv3/modvers'
> > Try 'join --help' for more information.
> > Done.
> > 
> > ------------------
> > 
> > I'm running the latest kernel from updates (with all previous versions removed).
> > 
> > [root at eltest wberrier]# uname -a
> > Linux eltest 3.10.0-123.13.2.el7.x86_64 #1 SMP Thu Dec 18 14:09:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> > 
> > ------------------
> > 
> > But, I was able to load the lirc_serial module in a vm just fine.
> > 
> > ------------------
> > 
> > On a different machine (one that I actually have a remote hooked up
> > to), I'm getting this for some reason:
> > 
> > [ 5339.248363] Request for unknown module key 'The ELRepo Project (http://elrepo.org): ELRepo.org Secure Boot Key: f365ad3481a7b20e3427b61b2a26635b83fe427b' err -11
> > [ 5339.248461] lirc_serial: disagrees about version of symbol lirc_register_driver
> > [ 5339.248464] lirc_serial: Unknown symbol lirc_register_driver (err -22)
> > 
> > But, that's a pxeboot nfs root machine, which has been a bit finicky,
> > so it may be related to something else, I'm not sure just yet.
> > 
> > uname -a
> > Linux myth 3.10.0-123.13.2.el7.x86_64 #1 SMP Thu Dec 18 14:09:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> > 
> > (same kernel version as above)
> > 
> > ------------------
> > 
> > Ideas about the module installation and "disagreeing symbol version"?
> > 
> > Wade
> 
> Hi Wade,
> 
> Thanks for the feedback.
> 
> Yes, I see the same errors when installing (not sure what has caused that).
> 
> Despite things being broken, I was able to modprobe lirc_serial,
> although I don't have the hardware:
> 
> [ 1631.901120] lirc_dev: IR Remote Control driver registered, major 249
> [ 1631.901215] Request for unknown module key 'The ELRepo Project
> (http://elrepo.org): ELRepo.org Secure Boot Key:
> f365ad3481a7b20e3427b61b2a26635b83fe427b' err -11
> [ 1631.901250] lirc_serial: module verification failed: signature and/or
> required key missing - tainting kernel
> [ 1631.901496] lirc_serial: port existence test failed, cannot continue
> [ 1631.902449] platform lirc_serial.0: lirc_dev: driver lirc_serial
> registered at minor = 0
> 
> and unload it:
> 
> [ 1729.957885] lirc_dev: module unloaded
> 
> I didn't see the unknown symbol error you got but that maybe because I
> don't have the hardware. Still, unknown symbol errors are critical and
> lead to broken drivers so that is serious.

I wouldn't be surprised if the missing symbol was caused by an
unrelated issue on my machine (I've been seeing other issues with it).
Loading lirc_serial worked on one of my machines.

> 
> Upon further investigation it would appear there are too many module
> dependencies on other in tree modules so I think these drivers are best
> built in kernel. I would suggest we ask Akemi to enable these drivers in
> the centos-plus kernel if you need device support.
>

I think it's still worth having a kmod package for the drivers that do
work.  Maybe we could leave the ones out that have missing symbols?
Or, just package kmod-lirc_serial, since it loaded just fine?

I'll do some more testing.

Also, on a different note, I think it would also be useful to enable
these drivers in kernel-ml.

Wade