This is the second of my 2 problems from my upgrade. The first is is the general list. This is more hardware specific.

I just inherited a soundblaster usb ir reciever, model sb0540. R5F27 did not have support for it so I downloade the latest lirc code from the cvs tree and compiled. I know have the sb0540 lirc module and lirc starts up without a hitch. The only problem have is that it does not recieve any signals. It is like it is not plugged in. Everything in the box indicates that it is plugged in and working by I get nothing from any of the myriad of remotes I have laying around.

I have run irrecord and it times out saying that it cannot find a gap.

running mode2 outputs:
This program is only intended for receivers supporting the pulse/space layer.
Note that this is no error, but this program simply makes no sense for your
receiver.
In order to test your setup run lircd with the --nodaemon option and
then check if the remote works with the irw tool.

when I run lircd in no daemon and use irw I get the following output::
lircd: lircd(sb0540) ready
lircd: accepted new client on /dev/lircd
lircd: initializing '/dev/usb/hiddev0'

There is no output at all from irw, no matter what remote I use.


The lirc log file contains only the following lines:
Feb 23 22:46:37 mythserv2 lircd: lircd(sb0540) ready
Feb 23 22:50:08 mythserv2 lircd: caught signal
Feb 23 22:50:17 mythserv2 lircd: lircd(sb0540) ready
Feb 23 22:52:57 mythserv2 lircd: caught signal
Feb 23 22:56:22 mythserv2 lircd: lircd(sb0540) ready
Feb 23 23:01:19 mythserv2 lircd: caught signal
Feb 23 23:01:29 mythserv2 lircd: lircd(sb0540) ready
Feb 24 06:30:32 mythserv2 lircd: caught signal
Feb 24 06:32:07 mythserv2 lircd: lircd(sb0540) ready
Feb 24 06:35:11 mythserv2 lircd: caught signal
Feb 24 06:35:15 mythserv2 lircd: lircd(sb0540) ready
Feb 24 06:53:56 mythserv2 lircd: caught signal
Feb 24 06:54:51 mythserv2 lircd: lircd(sb0540) ready

I have tried several other drivers to no avail

Thanks

Andre