LIRC module not being created [Solved]

[pajamabama]

The 'lirc_mceusb2' module for my remote control receiver is not being built by portage for some reason. I have

Code: Select all

/etc/make.conf:
...
LIRC_DEVICES="... mceusb2 ..."


then run

Code: Select all

emerge lirc

but there is no module produced. Any ideas why?

This worked in SL 3.4. Now it's failing in 3.5.

[pajamabama]

I'm trying to build the 'mceusb2' remote control driver for my laptop. In the past I've accomplished this by adding that string to /etc/make.conf LIRC_DEVICES

/etc/make.conf

Code: Select all

...
LIRC_DEVICES="audio audio_alsa mceusb2"
...


then 'emerge lirc'.

Unfortunately, this seems to not be working now, and I'm thinking it's some kind of issue with entropy (perhaps?). The emerge completes but there's no mceusb2 module built. Anyway, so I try to use equo to install. But it doesn't build the module either. When I show the make.conf associated with the 'sabayonlinux.org' repository, it doesn't have the right LIRC_DEVICES line.

So I guess I have two questions, one, how do I edit the make.conf so that equo will know to build the correct device? And two, can anyone suggest why emerge is not creating it?

[wolfden]

merging topics here

you can request changes to make.conf
viewtopic.php?f=76&t=13891

[pajamabama]

FOLLOWUP:
it seems that the module is being built in

/lib/modules/2.6.25-sabayon/misc/lirc_mceusb2.ko

rather than

/lib/modules/2.6.25-sabayon-r1/misc/lirc_mceusb2.ko

which is apparently where modprobe is looking for it. Does anyone know what this means? Thanks.

PS.
I've added a request to include the mceusb2 module in entropy. Thanks for that too.

[sjieke]

Is your /usr/src/linux symlink pointing to the correct kernel source files?

[pajamabama]

It's pointing to /usr/src/rpm. Is that right?

Code: Select all

Oberon ~ # ls -l /usr/src/linux
lrwxrwxrwx 1 root root 3 2008-07-23 00:08 /usr/src/linux -> rpm


There are linux sources in there too, they're just not being referenced.

Code: Select all

Oberon ~ # ls /usr/src/
config  linux  linux-2.6.25-sabayon  linux-2.6.25-sabayon-r1  rpm


[deadfool]

did you tell it -N for new USE flags?

[sjieke]

Maybe rpm is also a symlink, you could check it using

Code: Select all

ls -l /usr/src/rpm

With the command

Code: Select all

eselect kernel list

you can list all available kernel sources.
With the command

Code: Select all

eselect kernel set X

(X is the number found in the previous command) you can set the sources to the kernel you use. This will update the /usr/src/linux symlink.

Before changing the symlink I would try deadfool's suggestion and emerge using the -N option

Code: Select all

emerge -avN lirc

The options specified in the command above stand for:

• a: ask if you want to install
• v: verbose mode, this lists the use flags that will be disabled and enabled for this build
• N: use new USE-flags specified in make.conf

[pajamabama]

I have no idea what /usr/src/rpm is. I certainly didn't set up my kernel that way. But 'eselect show' even said that was where my kernel sources were. And that's just not true, there's some stuff in there, but not kernel sources as far as I can see. As far as I can see it has nothing in it but a few hidden text files, all named '.keep_app-arch_rpm-0'. No idea what that is.

So I used eselect to change my kernel source to /usr/src/linux-2.6.25-sabayon-r1. Then emerge put the module in the right place. Ran 'depmod -a' and all is well. Happy remoting.

Thanks!

[sjieke]

I'm glad everything is ok now.

That rpm folder is indeed very strange. I looked on my machine and it is also present there, no idea what it is for but it is there
But my symlink points to the correct sources. Maybe someone does now what the meaning is for that rpm folder...