[mythtv-users] Re: USB MCE IR Receiver
Alright. I have fixed the 4KSTACKS issue and commented out the
EXTRAVERSIONS in the MAKEFILE. I successfully compiled LIRC. After
moving my .ko dev and mceusb files to their correct locations, I
rebooted the machine and received this error in my /var/log/messages:
Mar 20 18:31:05 mythfrontend kernel:
/home/mythtv/compile/lirc-0.7.0/drivers/lirc_mceusb/lirc_mceusb.c:
mceusb_setup2 - Unsuccessful initialization
Mar 20 18:31:05 mythfrontend kernel: usbcore: registered new driver lirc_mceusb
Mar 20 18:31:05 mythfrontend kernel:
/home/mythtv/compile/lirc-0.7.0/drivers/lirc_mceusb/lirc_mceusb.c: USB
Microsoft IR Transceiver Driver v0.2.jim
You can see that at the end, I tacked on the .jim to the .h driver
file in the #DEFINE section. I have compared my PRODUCTID and
VENDORID numbers to the ones in the lirc_mceusb.h file I made and they
are identical to my ProdID and VendorID. I have found the
mceusb_setup2 location in the lirc_mceusb.c file. Here is what it
says:
static void mceusb_setup2( struct usb_device *udev, struct usb_skel* dev )
{
char data[16];
int res, size;
memset( data, 0, 16 );
res = usb_control_msg(udev, usb_rcvctrlpipe(udev, 0),
USB_REQ_GET_STATUS, USB_DIR_IN, 0, 0,
data, 2, HZ);
dprintk("%s - Get Status: res = %d, status = 0x%x 0x%x",
__func__, res, data[0], data[1]);
memset( data, 0, 16 );
res = usb_control_msg(udev, usb_sndctrlpipe(udev, 0),
USB_REQ_SET_CONFIGURATION, 0, 1, 0,
data, 0, HZ);
dprintk("%s - Set Configuration #1: res = %d", __func__, res);
/* Doesn't seem strictly necessary, but the Windows driver does it */
memset( data, 0, 16 );
data[0] = 0;
data[1] = 0xFF;
data[2] = 0xAA;
data[3] = 0xFF;
data[4] = 0x0B;
res = usb_bulk_msg(udev, usb_sndbulkpipe(udev,
dev->bulk_out_endpointAddr),
data, 5, &size, HZ);
dprintk("%s - Send #1: res = %d, data = 0x%x 0x%x, size=%d,
sendAddr=%d", __func__, res, data[0],
data[1], size, dev->bulk_out_endpointAddr);
if (res == -ETIMEDOUT)
{
err("%s - Unsuccessful initialization", __func__);
return;
}
memset( data, 0, 16 );
res = usb_bulk_msg(udev, usb_rcvbulkpipe(udev,
dev->bulk_in_endpointAddr),
data, 16, &size, HZ);
dprintk("%s - Receive #1: res = %d, size=%d, receiveAddr=%d",
__func__, res, size, dev->bulk_in_endpointAddr);
memset( data, 0, 16 );
data[0] = 0xFF;
data[1] = 0x18;
res = usb_bulk_msg(udev, usb_sndbulkpipe(udev,
dev->bulk_out_endpointAddr),
data, 2, &size, HZ);
dprintk("%s - Send #2: res = %d, size=%d, sendAddr=%d",
__func__, res, size, dev->bulk_out_endpointAddr);
memset( data, 0, 16 );
res = usb_bulk_msg(udev, usb_rcvbulkpipe(udev,
dev->bulk_in_endpointAddr),
data, 16, &size, HZ * 5);
dprintk("%s - Receive #2: res = %d, size=%d, receiveAddr=%d",
__func__, res, size, dev->bulk_in_endpointAddr);
}
I am a little confused by the two memset(data,0,16) that is listed
above. What could be the problem here? Thanks!!
On Sat, 19 Mar 2005 17:23:59 +0100, Axel Thimm <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 18, 2005 at 06:49:05PM -0600, Jim Oltman wrote:
> > Axel,
> >
> > I built lirc against the kernel source I downloaded from ATRPMs.
> > Shouldn't this be setup and ready to go with 4KSTACKS and match the
> > kernel I have installed already? I know these are nooB questions but
> > I am about as noob as they get with compiling. Thanks!
>
> Instructions for setting up your kernel sources can be found in Fc3'
> release notes. You will need to copy over the right .config file and
> remove any EXTRAVERSION from the top Makefile.
>
> > On Wed, 16 Mar 2005 14:22:19 +0100, Axel Thimm <[EMAIL PROTECTED]> wrote:
> > > On Tue, Mar 15, 2005 at 09:31:06PM -0600, Jim Oltman wrote:
> > > > lirc_dev: version magic '2.6.10-prep 686 REGPARM gcc-3.4' should be
> > > > '2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4'
> > >
> > > Looks like you didn't build against a kernel source tree matching the
> > > kernel you want to target. Unfortunatley that's an open issue with
> > > RH's infrastructure for building external kmdls. Check the release
> > > notes for how to get the kernel sources set up and also check the
> > > kernel specfile for which steps are needed to configure/prepare the
> > > kernel sources.
> > >
> > ___
> > mythtv-users mailing list
> > mythtv-users@mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
> --
> Axel.Thimm at ATrpms.net
>
>
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Re: USB MCE IR Receiver
On Fri, Mar 18, 2005 at 06:49:05PM -0600, Jim Oltman wrote: > Axel, > > I built lirc against the kernel source I downloaded from ATRPMs. > Shouldn't this be setup and ready to go with 4KSTACKS and match the > kernel I have installed already? I know these are nooB questions but > I am about as noob as they get with compiling. Thanks! Instructions for setting up your kernel sources can be found in Fc3' release notes. You will need to copy over the right .config file and remove any EXTRAVERSION from the top Makefile. > On Wed, 16 Mar 2005 14:22:19 +0100, Axel Thimm <[EMAIL PROTECTED]> wrote: > > On Tue, Mar 15, 2005 at 09:31:06PM -0600, Jim Oltman wrote: > > > lirc_dev: version magic '2.6.10-prep 686 REGPARM gcc-3.4' should be > > > '2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4' > > > > Looks like you didn't build against a kernel source tree matching the > > kernel you want to target. Unfortunatley that's an open issue with > > RH's infrastructure for building external kmdls. Check the release > > notes for how to get the kernel sources set up and also check the > > kernel specfile for which steps are needed to configure/prepare the > > kernel sources. > > > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users -- Axel.Thimm at ATrpms.net pgpy0npuJvyLk.pgp Description: PGP signature ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Re: USB MCE IR Receiver
Axel, I built lirc against the kernel source I downloaded from ATRPMs. Shouldn't this be setup and ready to go with 4KSTACKS and match the kernel I have installed already? I know these are nooB questions but I am about as noob as they get with compiling. Thanks! On Wed, 16 Mar 2005 14:22:19 +0100, Axel Thimm <[EMAIL PROTECTED]> wrote: > On Tue, Mar 15, 2005 at 09:31:06PM -0600, Jim Oltman wrote: > > lirc_dev: version magic '2.6.10-prep 686 REGPARM gcc-3.4' should be > > '2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4' > > Looks like you didn't build against a kernel source tree matching the > kernel you want to target. Unfortunatley that's an open issue with > RH's infrastructure for building external kmdls. Check the release > notes for how to get the kernel sources set up and also check the > kernel specfile for which steps are needed to configure/prepare the > kernel sources. > -- > Axel.Thimm at ATrpms.net > > > ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Unfortunately no, I haven't had much of a chance to look at it. Hopefully this weekend. It's not quite as pressing for me since I've already got my main frontend working with the hauppauge remote. I'm putting this second frontend together in preparation for my new TV, which I still haven't saved up enough money to buy yet... -darren On Wed, 16 Mar 2005 20:57:48 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > Darren, > > Have you had any luck? I haven't had a chance to work on this tonight > due to work. > > On Mon, 14 Mar 2005 22:58:13 -0700, Darren Richards > <[EMAIL PROTECTED]> wrote: > > Ah, it all makes sense now. I hadn't read through the entire thread. > > Well, it looks as if I have enough information at my disposal to > > either get my new remote working, or really screw things up. Either > > way, I'm up for a challenge. > > > > Thanks, > > darren > > > > On Mon, 14 Mar 2005 21:19:40 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > > wrote: > > > The problem is the original source doesn't work with > > > the newer MCE remotes. If you look for one of my > > > previous posts, then you will see a newer > > > lirc_mceusb.c attached that you will need to overwrite > > > the existing file. > > > > > > Since I don't use Fedora Core, I can't tell you the > > > best way to get it running. The easiest way would be > > > to download version 0.7.0 of lirc from www.lirc.org, > > > overwrite the lirc_mceusb.c file with the newer one, > > > compile the new version, copy the new lirc_dev.ko and > > > lirc_mceusb.ko over the existing lirc modules (Make > > > sure to make a backup copy of the original module > > > files). They should be located in /lib/modules/*your > > > kernel version*/misc/ > > > > > > After that you can either unload the lirc_mseusb and > > > lirc_dev modules and reload them, or you can reboot > > > your system let the modules be loaded at startup. > > > (Assuming you have the appropriate entries in modules > > > autoloading config file.) > > > > > > > > > --- Darren Richards <[EMAIL PROTECTED]> wrote: > > > > > > > I guess I don't understand... What's the point in > > > > recompiling from > > > > source if you're grabbing the same version that > > > > mythtv-suite > > > > installed? I thought the whole point was to install > > > > a new version > > > > whcih (hopefully) has support for my new fancy > > > > remote and IR receiver. > > > > > > > > By the way, have you noticed the range and > > > > directionality on that > > > > thing? From anywhere in the room, I can literally > > > > point the remote in > > > > any direction and have the light on the receiver > > > > light up. Once we > > > > get it to work, this thing will work *really* well. > > > > > > > > -darren > > > > > > > > On Mon, 14 Mar 2005 21:56:06 -0600, Jim Oltman > > > > <[EMAIL PROTECTED]> wrote: > > > > > As I unserstand it, if you do that, you will > > > > damage the mythtv-suite > > > > > install. I tried something similar when i was > > > > trying to install an > > > > > older version of LIRC. It damaged the > > > > mythtv-suite install. I had to > > > > > format my drive and start over. I think I might > > > > be able to get the > > > > > lirc source from Axel's site. If I would have > > > > read far enough down > > > > > the page, I would have seen the src rpm there. I > > > > think I can use the > > > > > same rpm -i to get the source for that. But it is > > > > only a hunch. Am I > > > > > close guys? > > > > > > > > > > On Mon, 14 Mar 2005 20:47:19 -0700, Darren > > > > Richards > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > Jim, > > > > > > > > > > > > Isn't there a way to uninstall the version of > > > > LIRC installed with > > > > > > mythtv? I'm not asking rhetorically, but > > > > because I really don't know. > > > > > > Couldn't you just do an apt-get remove LIRC? > > > > > > > > > > > > -darren > > > > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 21:13:10 -0600, Jim Oltman > > > > <[EMAIL PROTECTED]> wrote: > > > > > > > If you are using ATRPMs to install mythtv, > > > > then lirc-lib is already > > > > > > > installed. Since that is a certain version of > > > > LIRC that is used in > > > > > > > that setup, if you get the wrong version of > > > > LIRC to compile, it won't > > > > > > > work. That is why we need to know what > > > > version is on ATRPMs. I will > > > > > > > email that list and try and find out.I > > > > just did, let's see who > > > > > > > responds. Thanks! > > > > > > > > > > > > > > On Mon, 14 Mar 2005 19:57:11 -0700, Darren > > > > Richards > > > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > > > Andy, > > > > > > > > > > > > > > > > If there's an update in the source code that > > > > may make my new IR > > > > > > > > receiver work, I'll definitely try my hand > > > > at compiling LIRC. Your IR > > > > > > > > blaster walkthrough already saved the day > > > > for me once before, so I > > > > > > > > have high confidence... I'll let you know > > > > how
Re: [mythtv-users] Re: USB MCE IR Receiver
Darren, Have you had any luck? I haven't had a chance to work on this tonight due to work. On Mon, 14 Mar 2005 22:58:13 -0700, Darren Richards <[EMAIL PROTECTED]> wrote: > Ah, it all makes sense now. I hadn't read through the entire thread. > Well, it looks as if I have enough information at my disposal to > either get my new remote working, or really screw things up. Either > way, I'm up for a challenge. > > Thanks, > darren > > On Mon, 14 Mar 2005 21:19:40 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > wrote: > > The problem is the original source doesn't work with > > the newer MCE remotes. If you look for one of my > > previous posts, then you will see a newer > > lirc_mceusb.c attached that you will need to overwrite > > the existing file. > > > > Since I don't use Fedora Core, I can't tell you the > > best way to get it running. The easiest way would be > > to download version 0.7.0 of lirc from www.lirc.org, > > overwrite the lirc_mceusb.c file with the newer one, > > compile the new version, copy the new lirc_dev.ko and > > lirc_mceusb.ko over the existing lirc modules (Make > > sure to make a backup copy of the original module > > files). They should be located in /lib/modules/*your > > kernel version*/misc/ > > > > After that you can either unload the lirc_mseusb and > > lirc_dev modules and reload them, or you can reboot > > your system let the modules be loaded at startup. > > (Assuming you have the appropriate entries in modules > > autoloading config file.) > > > > > > --- Darren Richards <[EMAIL PROTECTED]> wrote: > > > > > I guess I don't understand... What's the point in > > > recompiling from > > > source if you're grabbing the same version that > > > mythtv-suite > > > installed? I thought the whole point was to install > > > a new version > > > whcih (hopefully) has support for my new fancy > > > remote and IR receiver. > > > > > > By the way, have you noticed the range and > > > directionality on that > > > thing? From anywhere in the room, I can literally > > > point the remote in > > > any direction and have the light on the receiver > > > light up. Once we > > > get it to work, this thing will work *really* well. > > > > > > -darren > > > > > > On Mon, 14 Mar 2005 21:56:06 -0600, Jim Oltman > > > <[EMAIL PROTECTED]> wrote: > > > > As I unserstand it, if you do that, you will > > > damage the mythtv-suite > > > > install. I tried something similar when i was > > > trying to install an > > > > older version of LIRC. It damaged the > > > mythtv-suite install. I had to > > > > format my drive and start over. I think I might > > > be able to get the > > > > lirc source from Axel's site. If I would have > > > read far enough down > > > > the page, I would have seen the src rpm there. I > > > think I can use the > > > > same rpm -i to get the source for that. But it is > > > only a hunch. Am I > > > > close guys? > > > > > > > > On Mon, 14 Mar 2005 20:47:19 -0700, Darren > > > Richards > > > > <[EMAIL PROTECTED]> wrote: > > > > > Jim, > > > > > > > > > > Isn't there a way to uninstall the version of > > > LIRC installed with > > > > > mythtv? I'm not asking rhetorically, but > > > because I really don't know. > > > > > Couldn't you just do an apt-get remove LIRC? > > > > > > > > > > -darren > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 21:13:10 -0600, Jim Oltman > > > <[EMAIL PROTECTED]> wrote: > > > > > > If you are using ATRPMs to install mythtv, > > > then lirc-lib is already > > > > > > installed. Since that is a certain version of > > > LIRC that is used in > > > > > > that setup, if you get the wrong version of > > > LIRC to compile, it won't > > > > > > work. That is why we need to know what > > > version is on ATRPMs. I will > > > > > > email that list and try and find out.I > > > just did, let's see who > > > > > > responds. Thanks! > > > > > > > > > > > > On Mon, 14 Mar 2005 19:57:11 -0700, Darren > > > Richards > > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > > Andy, > > > > > > > > > > > > > > If there's an update in the source code that > > > may make my new IR > > > > > > > receiver work, I'll definitely try my hand > > > at compiling LIRC. Your IR > > > > > > > blaster walkthrough already saved the day > > > for me once before, so I > > > > > > > have high confidence... I'll let you know > > > how it goes. > > > > > > > > > > > > > > Thanks, > > > > > > > darren > > > > > > > > > > > > > > On Mon, 14 Mar 2005 20:28:00 -0600, Andy > > > Long <[EMAIL PROTECTED]> wrote: > > > > > > > > If you'd like to give compiling LIRC > > > another chance, Pete and I have > > > > > > > > written a guide for doing it on FC3. It's > > > directed at enabling more > > > > > > > > devices than 2 with LIRC (now not needed > > > for ATRPMS due to a change a > > > > > > > > few days ago), but should be pretty > > > straightforward. May be worth a > > > > > > > > shot if you'd like to try. > > > > > > > > > > > > > > > > > > > http://lircsetup.com/lirc/troubl
[mythtv-users] Re: USB MCE IR Receiver
On Tue, Mar 15, 2005 at 09:31:06PM -0600, Jim Oltman wrote: > lirc_dev: version magic '2.6.10-prep 686 REGPARM gcc-3.4' should be > '2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4' Looks like you didn't build against a kernel source tree matching the kernel you want to target. Unfortunatley that's an open issue with RH's infrastructure for building external kmdls. Check the release notes for how to get the kernel sources set up and also check the kernel specfile for which steps are needed to configure/prepare the kernel sources. -- Axel.Thimm at ATrpms.net pgpxIxJPuKPsx.pgp Description: PGP signature ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
I really hate to keep bugging people, but I am receiving an error in my /var/log/messages after I got the new lirc_dev and lirc_mceusb drivers put in the /lib/modules/2.6.10-1.770/updates/drivers/lirc (location of my other lirc drivers). Here is the error: lirc_dev: version magic '2.6.10-prep 686 REGPARM gcc-3.4' should be '2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4' The version of the kernel I got for compiling came from ATRPMs: http://www.atrpms.net/dist/fc3/kernel/kernel-2.6.10-1.770_14.rhfc3.at.src.rpm.html This is obviously not the right file. Should I be grabbing the spec file instead of the RPM file? Any help would be appreciated. Thanks! On Tue, 15 Mar 2005 21:12:27 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > I re-ran this and instead of changing the MAX IRCTL devices, I left > them as is. This then ran fine. I am about to try these modules to > see if they work! > > > On Tue, 15 Mar 2005 20:18:48 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > > BTW, I meant the compile that I did following the instructions located here: > > > > > > http://lircsetup.com/lirc/trouble/kernsource.php > > > > On Tue, 15 Mar 2005 20:13:29 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > > > Where does this deposit the new lirc_mceusb and lirc_dev modules? I > > > have only found the old versions, I think. They say they were last > > > modified on March 5th. Obviously, today is the 15th. > > > > > > From Joe Huffner > > > > > > The easiest way would be > > > to download version 0.7.0 of lirc from www.lirc.org, > > > overwrite the lirc_mceusb.c file with the newer one, > > > compile the new version, copy the new lirc_dev.ko and > > > lirc_mceusb.ko over the existing lirc modules (Make > > > sure to make a backup copy of the original module > > > files). They should be located in /lib/modules/*your > > > kernel version*/misc/ > > > > > > > > > This is not in my FC3 load. Can anyone tell me where these drivers > > > ended up? Thanks! > > > > > > On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > > > wrote: > > > > Just an FYI for those of us who bought one of the > > > > updated MCE remotes and receivers. I was checking out > > > > the lirc mailing list and someone has update the > > > > driver to include support. From what I can tell the > > > > update has not been updated in CVS. > > > > > > > > I found the info at: > > > > http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc > > > > > > > > Basically what I did was overwrite the lirc_mceusb.c > > > > in the drivers/lirc_mceusb directory with the source > > > > found in the mailing liste. (I have attached the new > > > > source file.) Then went through the install process > > > > documented. I used version .7.0 of lirc. > > > > > > > > Please note, from what I have read and experienced, > > > > there are some initialization problems. What seemed to > > > > "fix it" was unplugging the receiver and plugging it > > > > back in, until I no longer got an error message > > > > stating the device did not initialize. You can check > > > > this by running "tail -f /var/log/messages". Also, I > > > > read that running kernel 2.6.11 seemed to fix the > > > > initialization problem. However I cannot confirm this > > > > as I am running Gentoo Dev Kernel 2.6.9-r9. Another > > > > problem I am having is that I am getting non-stop > > > > error messages stating: > > > > > > > > "usb 2-2: bulk timeout on ep1in" > > > > > > > > In fact, I was getting about 4 of those messages per > > > > second. If/when I get time I am planning to upgrade to > > > > 2.6.11 to see if this fixes the issue. > > > > > > > > -joe > > > > > > > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > > > After deleting the section in my rc.local about the > > > > > mknod /dev/lirc0 c > > > > > 61 0 and replacing it with: > > > > > > > > > > ln -s /dev/lircd /dev/lirc0 > > > > > > > > > > I am no longer getting errors from lircd in the > > > > > /var/log/messages. > > > > > IRW runs but I am not seeing anything when I press > > > > > buttons on my > > > > > Hauppauge remote (it has also been setup in the > > > > > correct lircrc files). > > > > > When I run irrecord I am getting errors about lircd > > > > > not being > > > > > started. I am going to try commenting out the other > > > > > section in > > > > > rc.local pertaining to MCEUSB and see what happens. > > > > > > > > > > > > > > > On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > Here is where I am at so far. In my > > > > > /etc/rc.d/rc.local I made these changes... > > > > > > > > > > > > #!/bin/sh > > > > > > # > > > > > > # This script will be executed *after* all the > > > > > other init scripts. > > > > > > # You can put your own initialization stuff in > > > > > here if you don't > > > > > > # want to do the full Sys V style init stuff. > > > > > > > > > > > > touch /var/lock/subsys/local > > > > > > mknod /dev/lirc0 c 61 0 -I add
Re: [mythtv-users] Re: USB MCE IR Receiver
I re-ran this and instead of changing the MAX IRCTL devices, I left them as is. This then ran fine. I am about to try these modules to see if they work! On Tue, 15 Mar 2005 20:18:48 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > BTW, I meant the compile that I did following the instructions located here: > > > http://lircsetup.com/lirc/trouble/kernsource.php > > On Tue, 15 Mar 2005 20:13:29 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > > Where does this deposit the new lirc_mceusb and lirc_dev modules? I > > have only found the old versions, I think. They say they were last > > modified on March 5th. Obviously, today is the 15th. > > > > From Joe Huffner > > > > The easiest way would be > > to download version 0.7.0 of lirc from www.lirc.org, > > overwrite the lirc_mceusb.c file with the newer one, > > compile the new version, copy the new lirc_dev.ko and > > lirc_mceusb.ko over the existing lirc modules (Make > > sure to make a backup copy of the original module > > files). They should be located in /lib/modules/*your > > kernel version*/misc/ > > > > > > This is not in my FC3 load. Can anyone tell me where these drivers > > ended up? Thanks! > > > > On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > > wrote: > > > Just an FYI for those of us who bought one of the > > > updated MCE remotes and receivers. I was checking out > > > the lirc mailing list and someone has update the > > > driver to include support. From what I can tell the > > > update has not been updated in CVS. > > > > > > I found the info at: > > > http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc > > > > > > Basically what I did was overwrite the lirc_mceusb.c > > > in the drivers/lirc_mceusb directory with the source > > > found in the mailing liste. (I have attached the new > > > source file.) Then went through the install process > > > documented. I used version .7.0 of lirc. > > > > > > Please note, from what I have read and experienced, > > > there are some initialization problems. What seemed to > > > "fix it" was unplugging the receiver and plugging it > > > back in, until I no longer got an error message > > > stating the device did not initialize. You can check > > > this by running "tail -f /var/log/messages". Also, I > > > read that running kernel 2.6.11 seemed to fix the > > > initialization problem. However I cannot confirm this > > > as I am running Gentoo Dev Kernel 2.6.9-r9. Another > > > problem I am having is that I am getting non-stop > > > error messages stating: > > > > > > "usb 2-2: bulk timeout on ep1in" > > > > > > In fact, I was getting about 4 of those messages per > > > second. If/when I get time I am planning to upgrade to > > > 2.6.11 to see if this fixes the issue. > > > > > > -joe > > > > > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > > After deleting the section in my rc.local about the > > > > mknod /dev/lirc0 c > > > > 61 0 and replacing it with: > > > > > > > > ln -s /dev/lircd /dev/lirc0 > > > > > > > > I am no longer getting errors from lircd in the > > > > /var/log/messages. > > > > IRW runs but I am not seeing anything when I press > > > > buttons on my > > > > Hauppauge remote (it has also been setup in the > > > > correct lircrc files). > > > > When I run irrecord I am getting errors about lircd > > > > not being > > > > started. I am going to try commenting out the other > > > > section in > > > > rc.local pertaining to MCEUSB and see what happens. > > > > > > > > > > > > On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman > > > > <[EMAIL PROTECTED]> wrote: > > > > > Here is where I am at so far. In my > > > > /etc/rc.d/rc.local I made these changes... > > > > > > > > > > #!/bin/sh > > > > > # > > > > > # This script will be executed *after* all the > > > > other init scripts. > > > > > # You can put your own initialization stuff in > > > > here if you don't > > > > > # want to do the full Sys V style init stuff. > > > > > > > > > > touch /var/lock/subsys/local > > > > > mknod /dev/lirc0 c 61 0 -I added this > > > > line in hopes it > > > > > would attach to a line in my modprobe > > > > > > > > > > /usr/X11R6/bin/xset -dpms > > > > > /usr/X11R6/bin/xset s off > > > > > /usr/bin/mtd --daemon > > > > > > > > > > # I added these next two lines > > > > > > > > > > /sbin/modprobe lirc_mceusb > > > > > /usr/sbin/lircd --device=/dev/lirc0 > > > > --output=/dev/lircd > > > > > > > > > > In my /etc/modprobe.conf I have added this line: > > > > > > > > > > alias char-major-61 lirc_mceusb > > > > > > > > > > After implementing these changes, I can do a cat > > > > /var/log/messages and > > > > > see what I showed you before about the driver > > > > being loaded for the USB > > > > > Microsoft IR Transceiver. But I also get this > > > > listed: > > > > > > > > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > > > > accepted new client on > > > > > /dev/lircd > > > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > > > > could not
Re: [mythtv-users] Re: USB MCE IR Receiver
BTW, I meant the compile that I did following the instructions located here: http://lircsetup.com/lirc/trouble/kernsource.php On Tue, 15 Mar 2005 20:13:29 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > Where does this deposit the new lirc_mceusb and lirc_dev modules? I > have only found the old versions, I think. They say they were last > modified on March 5th. Obviously, today is the 15th. > > From Joe Huffner > > The easiest way would be > to download version 0.7.0 of lirc from www.lirc.org, > overwrite the lirc_mceusb.c file with the newer one, > compile the new version, copy the new lirc_dev.ko and > lirc_mceusb.ko over the existing lirc modules (Make > sure to make a backup copy of the original module > files). They should be located in /lib/modules/*your > kernel version*/misc/ > > > This is not in my FC3 load. Can anyone tell me where these drivers > ended up? Thanks! > > On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > wrote: > > Just an FYI for those of us who bought one of the > > updated MCE remotes and receivers. I was checking out > > the lirc mailing list and someone has update the > > driver to include support. From what I can tell the > > update has not been updated in CVS. > > > > I found the info at: > > http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc > > > > Basically what I did was overwrite the lirc_mceusb.c > > in the drivers/lirc_mceusb directory with the source > > found in the mailing liste. (I have attached the new > > source file.) Then went through the install process > > documented. I used version .7.0 of lirc. > > > > Please note, from what I have read and experienced, > > there are some initialization problems. What seemed to > > "fix it" was unplugging the receiver and plugging it > > back in, until I no longer got an error message > > stating the device did not initialize. You can check > > this by running "tail -f /var/log/messages". Also, I > > read that running kernel 2.6.11 seemed to fix the > > initialization problem. However I cannot confirm this > > as I am running Gentoo Dev Kernel 2.6.9-r9. Another > > problem I am having is that I am getting non-stop > > error messages stating: > > > > "usb 2-2: bulk timeout on ep1in" > > > > In fact, I was getting about 4 of those messages per > > second. If/when I get time I am planning to upgrade to > > 2.6.11 to see if this fixes the issue. > > > > -joe > > > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > After deleting the section in my rc.local about the > > > mknod /dev/lirc0 c > > > 61 0 and replacing it with: > > > > > > ln -s /dev/lircd /dev/lirc0 > > > > > > I am no longer getting errors from lircd in the > > > /var/log/messages. > > > IRW runs but I am not seeing anything when I press > > > buttons on my > > > Hauppauge remote (it has also been setup in the > > > correct lircrc files). > > > When I run irrecord I am getting errors about lircd > > > not being > > > started. I am going to try commenting out the other > > > section in > > > rc.local pertaining to MCEUSB and see what happens. > > > > > > > > > On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman > > > <[EMAIL PROTECTED]> wrote: > > > > Here is where I am at so far. In my > > > /etc/rc.d/rc.local I made these changes... > > > > > > > > #!/bin/sh > > > > # > > > > # This script will be executed *after* all the > > > other init scripts. > > > > # You can put your own initialization stuff in > > > here if you don't > > > > # want to do the full Sys V style init stuff. > > > > > > > > touch /var/lock/subsys/local > > > > mknod /dev/lirc0 c 61 0 -I added this > > > line in hopes it > > > > would attach to a line in my modprobe > > > > > > > > /usr/X11R6/bin/xset -dpms > > > > /usr/X11R6/bin/xset s off > > > > /usr/bin/mtd --daemon > > > > > > > > # I added these next two lines > > > > > > > > /sbin/modprobe lirc_mceusb > > > > /usr/sbin/lircd --device=/dev/lirc0 > > > --output=/dev/lircd > > > > > > > > In my /etc/modprobe.conf I have added this line: > > > > > > > > alias char-major-61 lirc_mceusb > > > > > > > > After implementing these changes, I can do a cat > > > /var/log/messages and > > > > see what I showed you before about the driver > > > being loaded for the USB > > > > Microsoft IR Transceiver. But I also get this > > > listed: > > > > > > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > > > accepted new client on > > > > /dev/lircd > > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > > > could not open /dev/lirc0 > > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > > > default_init(): No such device > > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > > > caught signal > > > > > > > > I am however getting errors on boot in the > > > Show/Hide Details window. > > > > Where can I view the errors that it is showing me? > > > They disappear to > > > > quickly to read. I am pretty sure the info I want > > > to see (about the > > > > errors on boot in Show/Hi
Re: [mythtv-users] Re: USB MCE IR Receiver
Where does this deposit the new lirc_mceusb and lirc_dev modules? I have only found the old versions, I think. They say they were last modified on March 5th. Obviously, today is the 15th. From Joe Huffner The easiest way would be to download version 0.7.0 of lirc from www.lirc.org, overwrite the lirc_mceusb.c file with the newer one, compile the new version, copy the new lirc_dev.ko and lirc_mceusb.ko over the existing lirc modules (Make sure to make a backup copy of the original module files). They should be located in /lib/modules/*your kernel version*/misc/ This is not in my FC3 load. Can anyone tell me where these drivers ended up? Thanks! On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> wrote: > Just an FYI for those of us who bought one of the > updated MCE remotes and receivers. I was checking out > the lirc mailing list and someone has update the > driver to include support. From what I can tell the > update has not been updated in CVS. > > I found the info at: > http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc > > Basically what I did was overwrite the lirc_mceusb.c > in the drivers/lirc_mceusb directory with the source > found in the mailing liste. (I have attached the new > source file.) Then went through the install process > documented. I used version .7.0 of lirc. > > Please note, from what I have read and experienced, > there are some initialization problems. What seemed to > "fix it" was unplugging the receiver and plugging it > back in, until I no longer got an error message > stating the device did not initialize. You can check > this by running "tail -f /var/log/messages". Also, I > read that running kernel 2.6.11 seemed to fix the > initialization problem. However I cannot confirm this > as I am running Gentoo Dev Kernel 2.6.9-r9. Another > problem I am having is that I am getting non-stop > error messages stating: > > "usb 2-2: bulk timeout on ep1in" > > In fact, I was getting about 4 of those messages per > second. If/when I get time I am planning to upgrade to > 2.6.11 to see if this fixes the issue. > > -joe > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > After deleting the section in my rc.local about the > > mknod /dev/lirc0 c > > 61 0 and replacing it with: > > > > ln -s /dev/lircd /dev/lirc0 > > > > I am no longer getting errors from lircd in the > > /var/log/messages. > > IRW runs but I am not seeing anything when I press > > buttons on my > > Hauppauge remote (it has also been setup in the > > correct lircrc files). > > When I run irrecord I am getting errors about lircd > > not being > > started. I am going to try commenting out the other > > section in > > rc.local pertaining to MCEUSB and see what happens. > > > > > > On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman > > <[EMAIL PROTECTED]> wrote: > > > Here is where I am at so far. In my > > /etc/rc.d/rc.local I made these changes... > > > > > > #!/bin/sh > > > # > > > # This script will be executed *after* all the > > other init scripts. > > > # You can put your own initialization stuff in > > here if you don't > > > # want to do the full Sys V style init stuff. > > > > > > touch /var/lock/subsys/local > > > mknod /dev/lirc0 c 61 0 -I added this > > line in hopes it > > > would attach to a line in my modprobe > > > > > > /usr/X11R6/bin/xset -dpms > > > /usr/X11R6/bin/xset s off > > > /usr/bin/mtd --daemon > > > > > > # I added these next two lines > > > > > > /sbin/modprobe lirc_mceusb > > > /usr/sbin/lircd --device=/dev/lirc0 > > --output=/dev/lircd > > > > > > In my /etc/modprobe.conf I have added this line: > > > > > > alias char-major-61 lirc_mceusb > > > > > > After implementing these changes, I can do a cat > > /var/log/messages and > > > see what I showed you before about the driver > > being loaded for the USB > > > Microsoft IR Transceiver. But I also get this > > listed: > > > > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > > accepted new client on > > > /dev/lircd > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > > could not open /dev/lirc0 > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > > default_init(): No such device > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > > caught signal > > > > > > I am however getting errors on boot in the > > Show/Hide Details window. > > > Where can I view the errors that it is showing me? > > They disappear to > > > quickly to read. I am pretty sure the info I want > > to see (about the > > > errors on boot in Show/Hide window) is not listed > > in > > > /var/log/messages. > > > > > > On Sun, 13 Mar 2005 18:38:09 -0600, Ron Johnson > > <[EMAIL PROTECTED]> wrote: > > > > On Sun, 2005-03-13 at 17:58 -0600, Jim Oltman > > wrote: > > > > > What I meant in that statement is that I got > > it to recognize the > > > > > receiver in the /var/log/messages but it is > > still not working. > > > > > > > > Yes, but *how* did you get "it" to recognize the > > receiver? > > > > > > > >
[mythtv-users] Re: USB MCE IR Receiver
Yeah Axel, I noted in a later email that i should have scrolled further down the page. Nothing like a noob mistake to end a Monday. I am not really familiar with CVS or compiling which is why I was asking those questions about which version. My bad. I think i will be able to compile the current version with the MCE receiver fix (I hope). If not, then I get to format my frontendagain! Again, sorry for the mixup. Jim On Tue, 15 Mar 2005 20:00:09 +0100, Axel Thimm <[EMAIL PROTECTED]> wrote: > On Mon, Mar 14, 2005 at 05:45:15PM -0600, Jim Oltman wrote: > > I just looked on ATRPMs website and there is no listing for getting > > the source code for the lirc drivers. > > Don't be impatient and just scroll to the bottom of the page ... > > > There is also no mention of exactly what "CVS version" I am using > > (0.7.0pre 4 or 5 or 6 or 7 or 8). I know that I have lirc 0.7.0-45 > > from ATRPMs but other than that, I have no idea. > > So, if there is no pre/cvs mark in the version/release, wouldn't it > make sense to assume it is a release cut and no cvs/pre? > > > Anyone know what version I could be running? I would LOVE to get > > this remote going so I could move on to bugging the list about other > > problems! :-) Thanks! > > I'd suggest checking with the lirc list for either a patch backported > to 0.7.0 or a release for 0.7.1. > > > On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > > wrote: > > > > > > Unless ATRPMS have been updated, then the only way to > > > get this to work would be to compile the drivers. My > > > guess is that these drivers will be updated in the > > > not-too-distant-future, but exactly when that happens > > > is up to the lirc maintainers. Then the RPMS will have > > > to be udpated as well. > > > > > > Something you can try is to leave your current lirc > > > installed. > > > > > > 1. Download the same version you have installed. > > > 2. Copy the the previously attached source code to the > > > appropriate place. > > > 3. Configure and compile source. > > > 4. Copy the new lirc_mceusb and lirc_dev modules over > > > the existing files. (After making a backup of the > > > originals of course.) > > > 5. Unload the modules, then load the new modules. (Or > > > reboot for the easiest way.) > > > > > > About your questions concerning my modprobe.conf and > > > what not. I don't have anything currently in their > > > except ethernet and video. Since my remote wasn't > > > working with lirc yet, there was no reason to put > > > anything in there. Also, I am running gentoo, so I > > > don't know the exact format of the modprobe.conf file, > > > but my guess is you would just want the module name > > > you would want to load. In this case it would just be > > > lirc_mceusb, all the other modules required by lirc > > > should be loaded. > > > > > > > > > > Since I used apt-get to install lirc and > > > > mythtv-suite, I take it that > > > > is would be EXTREMELY difficult for me to compile > > > > this new driver into > > > > lirc especially since I have never compiled anything > > > > in my entire life > > > > (except for those 2 semesters in college compiling C > > > > code that barely > > > > worked). As I understand it, mythtv-suite already > > > > has the lirc-lib > > > > included. Is there a way around all this? Does > > > > anyone know? My > > > > version of the mce_usb driver is listed as v0.2 but > > > > doesn't mention > > > > anything about this Dan Conti. Also, on ATRPMs it > > > > looks like Axel > > > > last updated the lirc drivers on Mar 5th 12:27 CET. > > > > Could you tell me > > > > how you were able to get your MCE IR receiver up and > > > > working (assuming > > > > I have the right driver). What did you put in your > > > > /etc/modprobe.conf? I didn't have a /dev/lirc0 only > > > > a /dev/lircd so > > > > in my rc.local I put these statements in: > > > > > > > > ln -s /dev/lircd /dev/lirc0 > > > > chmod 666 /dev/lirc0 > > > > > > > > /sbin/modprobe lirc_mceusb > > > > /usr/sbin/lircd --device=/dev/lirc0 > > > > > > > > Am I incorrect? Should I be doing something > > > > different? Thanks! > > > > > > > > > > > > On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman > > > > <[EMAIL PROTECTED]> wrote: > > > > > Since I used apt-get to install lirc and > > > > mythtv-suite, I take it that > > > > > is would be EXTREMELY difficult for me to compile > > > > this new driver into > > > > > lirc especially since I have never compiled > > > > anything in my entire life > > > > > (except for those 2 semesters in college compiling > > > > C code that barely > > > > > worked). As I understand it, mythtv-suite already > > > > has the lirc-lib > > > > > included. Is there a way around all this? Does > > > > anyone know? My > > > > > version of the mce_usb driver is listed as v0.2 > > > > but doesn't mention > > > > > anything about this Dan Conti. Also, on ATRPMs it > > > > looks like Axel > > > > > last updated the lirc drivers on
[mythtv-users] Re: USB MCE IR Receiver
On Mon, Mar 14, 2005 at 05:45:15PM -0600, Jim Oltman wrote: > I just looked on ATRPMs website and there is no listing for getting > the source code for the lirc drivers. Don't be impatient and just scroll to the bottom of the page ... > There is also no mention of exactly what "CVS version" I am using > (0.7.0pre 4 or 5 or 6 or 7 or 8). I know that I have lirc 0.7.0-45 > from ATRPMs but other than that, I have no idea. So, if there is no pre/cvs mark in the version/release, wouldn't it make sense to assume it is a release cut and no cvs/pre? > Anyone know what version I could be running? I would LOVE to get > this remote going so I could move on to bugging the list about other > problems! :-) Thanks! I'd suggest checking with the lirc list for either a patch backported to 0.7.0 or a release for 0.7.1. > On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > wrote: > > > > Unless ATRPMS have been updated, then the only way to > > get this to work would be to compile the drivers. My > > guess is that these drivers will be updated in the > > not-too-distant-future, but exactly when that happens > > is up to the lirc maintainers. Then the RPMS will have > > to be udpated as well. > > > > Something you can try is to leave your current lirc > > installed. > > > > 1. Download the same version you have installed. > > 2. Copy the the previously attached source code to the > > appropriate place. > > 3. Configure and compile source. > > 4. Copy the new lirc_mceusb and lirc_dev modules over > > the existing files. (After making a backup of the > > originals of course.) > > 5. Unload the modules, then load the new modules. (Or > > reboot for the easiest way.) > > > > About your questions concerning my modprobe.conf and > > what not. I don't have anything currently in their > > except ethernet and video. Since my remote wasn't > > working with lirc yet, there was no reason to put > > anything in there. Also, I am running gentoo, so I > > don't know the exact format of the modprobe.conf file, > > but my guess is you would just want the module name > > you would want to load. In this case it would just be > > lirc_mceusb, all the other modules required by lirc > > should be loaded. > > > > > > > Since I used apt-get to install lirc and > > > mythtv-suite, I take it that > > > is would be EXTREMELY difficult for me to compile > > > this new driver into > > > lirc especially since I have never compiled anything > > > in my entire life > > > (except for those 2 semesters in college compiling C > > > code that barely > > > worked). As I understand it, mythtv-suite already > > > has the lirc-lib > > > included. Is there a way around all this? Does > > > anyone know? My > > > version of the mce_usb driver is listed as v0.2 but > > > doesn't mention > > > anything about this Dan Conti. Also, on ATRPMs it > > > looks like Axel > > > last updated the lirc drivers on Mar 5th 12:27 CET. > > > Could you tell me > > > how you were able to get your MCE IR receiver up and > > > working (assuming > > > I have the right driver). What did you put in your > > > /etc/modprobe.conf? I didn't have a /dev/lirc0 only > > > a /dev/lircd so > > > in my rc.local I put these statements in: > > > > > > ln -s /dev/lircd /dev/lirc0 > > > chmod 666 /dev/lirc0 > > > > > > /sbin/modprobe lirc_mceusb > > > /usr/sbin/lircd --device=/dev/lirc0 > > > > > > Am I incorrect? Should I be doing something > > > different? Thanks! > > > > > > > > > On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman > > > <[EMAIL PROTECTED]> wrote: > > > > Since I used apt-get to install lirc and > > > mythtv-suite, I take it that > > > > is would be EXTREMELY difficult for me to compile > > > this new driver into > > > > lirc especially since I have never compiled > > > anything in my entire life > > > > (except for those 2 semesters in college compiling > > > C code that barely > > > > worked). As I understand it, mythtv-suite already > > > has the lirc-lib > > > > included. Is there a way around all this? Does > > > anyone know? My > > > > version of the mce_usb driver is listed as v0.2 > > > but doesn't mention > > > > anything about this Dan Conti. Also, on ATRPMs it > > > looks like Axel > > > > last updated the lirc drivers on Mar 5th 12:27 > > > CET. Could you tell me > > > > how you were able to get your MCE IR receiver up > > > and working (assuming > > > > I have the right driver). What did you put in > > > your > > > > /etc/modprobe.conf? I didn't have a /dev/lirc0 > > > only a /dev/lircd so > > > > in my rc.local I put these statements in: > > > > > > > > ln -s /dev/lircd /dev/lirc0 > > > > chmod 666 /dev/lirc0 > > > > > > > > /sbin/modprobe lirc_mceusb > > > > /usr/sbin/lircd --device=/dev/lirc0 > > > > > > > > Am I incorrect? Should I be doing something > > > different? Thanks! > > > > > > > > On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe > > > Huffner <[EMAIL PROTECTED]> wrote: > > > > > Just an FYI for those of us w
Re: [mythtv-users] Re: USB MCE IR Receiver
Ah, it all makes sense now. I hadn't read through the entire thread. Well, it looks as if I have enough information at my disposal to either get my new remote working, or really screw things up. Either way, I'm up for a challenge. Thanks, darren On Mon, 14 Mar 2005 21:19:40 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> wrote: > The problem is the original source doesn't work with > the newer MCE remotes. If you look for one of my > previous posts, then you will see a newer > lirc_mceusb.c attached that you will need to overwrite > the existing file. > > Since I don't use Fedora Core, I can't tell you the > best way to get it running. The easiest way would be > to download version 0.7.0 of lirc from www.lirc.org, > overwrite the lirc_mceusb.c file with the newer one, > compile the new version, copy the new lirc_dev.ko and > lirc_mceusb.ko over the existing lirc modules (Make > sure to make a backup copy of the original module > files). They should be located in /lib/modules/*your > kernel version*/misc/ > > After that you can either unload the lirc_mseusb and > lirc_dev modules and reload them, or you can reboot > your system let the modules be loaded at startup. > (Assuming you have the appropriate entries in modules > autoloading config file.) > > > --- Darren Richards <[EMAIL PROTECTED]> wrote: > > > I guess I don't understand... What's the point in > > recompiling from > > source if you're grabbing the same version that > > mythtv-suite > > installed? I thought the whole point was to install > > a new version > > whcih (hopefully) has support for my new fancy > > remote and IR receiver. > > > > By the way, have you noticed the range and > > directionality on that > > thing? From anywhere in the room, I can literally > > point the remote in > > any direction and have the light on the receiver > > light up. Once we > > get it to work, this thing will work *really* well. > > > > -darren > > > > On Mon, 14 Mar 2005 21:56:06 -0600, Jim Oltman > > <[EMAIL PROTECTED]> wrote: > > > As I unserstand it, if you do that, you will > > damage the mythtv-suite > > > install. I tried something similar when i was > > trying to install an > > > older version of LIRC. It damaged the > > mythtv-suite install. I had to > > > format my drive and start over. I think I might > > be able to get the > > > lirc source from Axel's site. If I would have > > read far enough down > > > the page, I would have seen the src rpm there. I > > think I can use the > > > same rpm -i to get the source for that. But it is > > only a hunch. Am I > > > close guys? > > > > > > On Mon, 14 Mar 2005 20:47:19 -0700, Darren > > Richards > > > <[EMAIL PROTECTED]> wrote: > > > > Jim, > > > > > > > > Isn't there a way to uninstall the version of > > LIRC installed with > > > > mythtv? I'm not asking rhetorically, but > > because I really don't know. > > > > Couldn't you just do an apt-get remove LIRC? > > > > > > > > -darren > > > > > > > > > > > > On Mon, 14 Mar 2005 21:13:10 -0600, Jim Oltman > > <[EMAIL PROTECTED]> wrote: > > > > > If you are using ATRPMs to install mythtv, > > then lirc-lib is already > > > > > installed. Since that is a certain version of > > LIRC that is used in > > > > > that setup, if you get the wrong version of > > LIRC to compile, it won't > > > > > work. That is why we need to know what > > version is on ATRPMs. I will > > > > > email that list and try and find out.I > > just did, let's see who > > > > > responds. Thanks! > > > > > > > > > > On Mon, 14 Mar 2005 19:57:11 -0700, Darren > > Richards > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > Andy, > > > > > > > > > > > > If there's an update in the source code that > > may make my new IR > > > > > > receiver work, I'll definitely try my hand > > at compiling LIRC. Your IR > > > > > > blaster walkthrough already saved the day > > for me once before, so I > > > > > > have high confidence... I'll let you know > > how it goes. > > > > > > > > > > > > Thanks, > > > > > > darren > > > > > > > > > > > > On Mon, 14 Mar 2005 20:28:00 -0600, Andy > > Long <[EMAIL PROTECTED]> wrote: > > > > > > > If you'd like to give compiling LIRC > > another chance, Pete and I have > > > > > > > written a guide for doing it on FC3. It's > > directed at enabling more > > > > > > > devices than 2 with LIRC (now not needed > > for ATRPMS due to a change a > > > > > > > few days ago), but should be pretty > > straightforward. May be worth a > > > > > > > shot if you'd like to try. > > > > > > > > > > > > > > > > http://lircsetup.com/lirc/trouble/kernsource.php > > > > > > > > > > > > > > -Andy > > > > > > > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 19:01:33 -0700, Darren > > Richards > > > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > > > My USB MCE remote just came in the mail > > today. I figured if there's a > > > > > > > > link to it from Jarod's guide, I should > > be able to get it working. > > > > > > > > Imagine my dismay when I started > > searching
Re: [mythtv-users] Re: USB MCE IR Receiver
The problem is the original source doesn't work with the newer MCE remotes. If you look for one of my previous posts, then you will see a newer lirc_mceusb.c attached that you will need to overwrite the existing file. Since I don't use Fedora Core, I can't tell you the best way to get it running. The easiest way would be to download version 0.7.0 of lirc from www.lirc.org, overwrite the lirc_mceusb.c file with the newer one, compile the new version, copy the new lirc_dev.ko and lirc_mceusb.ko over the existing lirc modules (Make sure to make a backup copy of the original module files). They should be located in /lib/modules/*your kernel version*/misc/ After that you can either unload the lirc_mseusb and lirc_dev modules and reload them, or you can reboot your system let the modules be loaded at startup. (Assuming you have the appropriate entries in modules autoloading config file.) --- Darren Richards <[EMAIL PROTECTED]> wrote: > I guess I don't understand... What's the point in > recompiling from > source if you're grabbing the same version that > mythtv-suite > installed? I thought the whole point was to install > a new version > whcih (hopefully) has support for my new fancy > remote and IR receiver. > > By the way, have you noticed the range and > directionality on that > thing? From anywhere in the room, I can literally > point the remote in > any direction and have the light on the receiver > light up. Once we > get it to work, this thing will work *really* well. > > -darren > > On Mon, 14 Mar 2005 21:56:06 -0600, Jim Oltman > <[EMAIL PROTECTED]> wrote: > > As I unserstand it, if you do that, you will > damage the mythtv-suite > > install. I tried something similar when i was > trying to install an > > older version of LIRC. It damaged the > mythtv-suite install. I had to > > format my drive and start over. I think I might > be able to get the > > lirc source from Axel's site. If I would have > read far enough down > > the page, I would have seen the src rpm there. I > think I can use the > > same rpm -i to get the source for that. But it is > only a hunch. Am I > > close guys? > > > > On Mon, 14 Mar 2005 20:47:19 -0700, Darren > Richards > > <[EMAIL PROTECTED]> wrote: > > > Jim, > > > > > > Isn't there a way to uninstall the version of > LIRC installed with > > > mythtv? I'm not asking rhetorically, but > because I really don't know. > > > Couldn't you just do an apt-get remove LIRC? > > > > > > -darren > > > > > > > > > On Mon, 14 Mar 2005 21:13:10 -0600, Jim Oltman > <[EMAIL PROTECTED]> wrote: > > > > If you are using ATRPMs to install mythtv, > then lirc-lib is already > > > > installed. Since that is a certain version of > LIRC that is used in > > > > that setup, if you get the wrong version of > LIRC to compile, it won't > > > > work. That is why we need to know what > version is on ATRPMs. I will > > > > email that list and try and find out.I > just did, let's see who > > > > responds. Thanks! > > > > > > > > On Mon, 14 Mar 2005 19:57:11 -0700, Darren > Richards > > > > <[EMAIL PROTECTED]> wrote: > > > > > Andy, > > > > > > > > > > If there's an update in the source code that > may make my new IR > > > > > receiver work, I'll definitely try my hand > at compiling LIRC. Your IR > > > > > blaster walkthrough already saved the day > for me once before, so I > > > > > have high confidence... I'll let you know > how it goes. > > > > > > > > > > Thanks, > > > > > darren > > > > > > > > > > On Mon, 14 Mar 2005 20:28:00 -0600, Andy > Long <[EMAIL PROTECTED]> wrote: > > > > > > If you'd like to give compiling LIRC > another chance, Pete and I have > > > > > > written a guide for doing it on FC3. It's > directed at enabling more > > > > > > devices than 2 with LIRC (now not needed > for ATRPMS due to a change a > > > > > > few days ago), but should be pretty > straightforward. May be worth a > > > > > > shot if you'd like to try. > > > > > > > > > > > > > http://lircsetup.com/lirc/trouble/kernsource.php > > > > > > > > > > > > -Andy > > > > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 19:01:33 -0700, Darren > Richards > > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > > My USB MCE remote just came in the mail > today. I figured if there's a > > > > > > > link to it from Jarod's guide, I should > be able to get it working. > > > > > > > Imagine my dismay when I started > searching the archives and came > > > > > > > across this thread. Jim, I'm in exactly > the same boat as you. Even > > > > > > > if there was a magical fix in CVS, I've > never successfully compiled > > > > > > > anything in my life. I'm completely > dependent upon apt-get and > > > > > > > ATRPMS. > > > > > > > > > > > > > > Please, please keep us posted if you > come up with anything. I'll > > > > > > > start digging into this probably > tomorrow, and maybe I'll have some > > > > > > > luck... > > > > > > > > > > > > > > -darren > > > > > > > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 17:
Re: [mythtv-users] Re: USB MCE IR Receiver
I guess I don't understand... What's the point in recompiling from source if you're grabbing the same version that mythtv-suite installed? I thought the whole point was to install a new version whcih (hopefully) has support for my new fancy remote and IR receiver. By the way, have you noticed the range and directionality on that thing? From anywhere in the room, I can literally point the remote in any direction and have the light on the receiver light up. Once we get it to work, this thing will work *really* well. -darren On Mon, 14 Mar 2005 21:56:06 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > As I unserstand it, if you do that, you will damage the mythtv-suite > install. I tried something similar when i was trying to install an > older version of LIRC. It damaged the mythtv-suite install. I had to > format my drive and start over. I think I might be able to get the > lirc source from Axel's site. If I would have read far enough down > the page, I would have seen the src rpm there. I think I can use the > same rpm -i to get the source for that. But it is only a hunch. Am I > close guys? > > On Mon, 14 Mar 2005 20:47:19 -0700, Darren Richards > <[EMAIL PROTECTED]> wrote: > > Jim, > > > > Isn't there a way to uninstall the version of LIRC installed with > > mythtv? I'm not asking rhetorically, but because I really don't know. > > Couldn't you just do an apt-get remove LIRC? > > > > -darren > > > > > > On Mon, 14 Mar 2005 21:13:10 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > > > If you are using ATRPMs to install mythtv, then lirc-lib is already > > > installed. Since that is a certain version of LIRC that is used in > > > that setup, if you get the wrong version of LIRC to compile, it won't > > > work. That is why we need to know what version is on ATRPMs. I will > > > email that list and try and find out.I just did, let's see who > > > responds. Thanks! > > > > > > On Mon, 14 Mar 2005 19:57:11 -0700, Darren Richards > > > <[EMAIL PROTECTED]> wrote: > > > > Andy, > > > > > > > > If there's an update in the source code that may make my new IR > > > > receiver work, I'll definitely try my hand at compiling LIRC. Your IR > > > > blaster walkthrough already saved the day for me once before, so I > > > > have high confidence... I'll let you know how it goes. > > > > > > > > Thanks, > > > > darren > > > > > > > > On Mon, 14 Mar 2005 20:28:00 -0600, Andy Long <[EMAIL PROTECTED]> wrote: > > > > > If you'd like to give compiling LIRC another chance, Pete and I have > > > > > written a guide for doing it on FC3. It's directed at enabling more > > > > > devices than 2 with LIRC (now not needed for ATRPMS due to a change a > > > > > few days ago), but should be pretty straightforward. May be worth a > > > > > shot if you'd like to try. > > > > > > > > > > http://lircsetup.com/lirc/trouble/kernsource.php > > > > > > > > > > -Andy > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > My USB MCE remote just came in the mail today. I figured if > > > > > > there's a > > > > > > link to it from Jarod's guide, I should be able to get it working. > > > > > > Imagine my dismay when I started searching the archives and came > > > > > > across this thread. Jim, I'm in exactly the same boat as you. Even > > > > > > if there was a magical fix in CVS, I've never successfully compiled > > > > > > anything in my life. I'm completely dependent upon apt-get and > > > > > > ATRPMS. > > > > > > > > > > > > Please, please keep us posted if you come up with anything. I'll > > > > > > start digging into this probably tomorrow, and maybe I'll have some > > > > > > luck... > > > > > > > > > > > > -darren > > > > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman <[EMAIL PROTECTED]> > > > > > > wrote: > > > > > > > I just looked on ATRPMs website and there is no listing for > > > > > > > getting > > > > > > > the source code for the lirc drivers. There is also no mention of > > > > > > > exactly what "CVS version" I am using (0.7.0pre 4 or 5 or 6 or 7 > > > > > > > or > > > > > > > 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than > > > > > > > that, > > > > > > > I have no idea. Anyone know what version I could be running? I > > > > > > > would > > > > > > > LOVE to get this remote going so I could move on to bugging the > > > > > > > list > > > > > > > about other problems! :-) Thanks! > > > > > > > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL > > > > > > > PROTECTED]> wrote: > > > > > > > > > > > > > > > > Unless ATRPMS have been updated, then the only way to > > > > > > > > get this to work would be to compile the drivers. My > > > > > > > > guess is that these drivers will be updated in the > > > > > > > > not-too-distant-future, but exactly when that happens > > > > > > > > is up to the lirc maintainers. Then the RPMS will have
Re: [mythtv-users] Re: USB MCE IR Receiver
Jim, Isn't there a way to uninstall the version of LIRC installed with mythtv? I'm not asking rhetorically, but because I really don't know. Couldn't you just do an apt-get remove LIRC? -darren On Mon, 14 Mar 2005 21:13:10 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > If you are using ATRPMs to install mythtv, then lirc-lib is already > installed. Since that is a certain version of LIRC that is used in > that setup, if you get the wrong version of LIRC to compile, it won't > work. That is why we need to know what version is on ATRPMs. I will > email that list and try and find out.I just did, let's see who > responds. Thanks! > > On Mon, 14 Mar 2005 19:57:11 -0700, Darren Richards > <[EMAIL PROTECTED]> wrote: > > Andy, > > > > If there's an update in the source code that may make my new IR > > receiver work, I'll definitely try my hand at compiling LIRC. Your IR > > blaster walkthrough already saved the day for me once before, so I > > have high confidence... I'll let you know how it goes. > > > > Thanks, > > darren > > > > On Mon, 14 Mar 2005 20:28:00 -0600, Andy Long <[EMAIL PROTECTED]> wrote: > > > If you'd like to give compiling LIRC another chance, Pete and I have > > > written a guide for doing it on FC3. It's directed at enabling more > > > devices than 2 with LIRC (now not needed for ATRPMS due to a change a > > > few days ago), but should be pretty straightforward. May be worth a > > > shot if you'd like to try. > > > > > > http://lircsetup.com/lirc/trouble/kernsource.php > > > > > > -Andy > > > > > > > > > On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards > > > <[EMAIL PROTECTED]> wrote: > > > > My USB MCE remote just came in the mail today. I figured if there's a > > > > link to it from Jarod's guide, I should be able to get it working. > > > > Imagine my dismay when I started searching the archives and came > > > > across this thread. Jim, I'm in exactly the same boat as you. Even > > > > if there was a magical fix in CVS, I've never successfully compiled > > > > anything in my life. I'm completely dependent upon apt-get and > > > > ATRPMS. > > > > > > > > Please, please keep us posted if you come up with anything. I'll > > > > start digging into this probably tomorrow, and maybe I'll have some > > > > luck... > > > > > > > > -darren > > > > > > > > > > > > On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman <[EMAIL PROTECTED]> > > > > wrote: > > > > > I just looked on ATRPMs website and there is no listing for getting > > > > > the source code for the lirc drivers. There is also no mention of > > > > > exactly what "CVS version" I am using (0.7.0pre 4 or 5 or 6 or 7 or > > > > > 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, > > > > > I have no idea. Anyone know what version I could be running? I would > > > > > LOVE to get this remote going so I could move on to bugging the list > > > > > about other problems! :-) Thanks! > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL > > > > > PROTECTED]> wrote: > > > > > > > > > > > > Unless ATRPMS have been updated, then the only way to > > > > > > get this to work would be to compile the drivers. My > > > > > > guess is that these drivers will be updated in the > > > > > > not-too-distant-future, but exactly when that happens > > > > > > is up to the lirc maintainers. Then the RPMS will have > > > > > > to be udpated as well. > > > > > > > > > > > > Something you can try is to leave your current lirc > > > > > > installed. > > > > > > > > > > > > 1. Download the same version you have installed. > > > > > > 2. Copy the the previously attached source code to the > > > > > > appropriate place. > > > > > > 3. Configure and compile source. > > > > > > 4. Copy the new lirc_mceusb and lirc_dev modules over > > > > > > the existing files. (After making a backup of the > > > > > > originals of course.) > > > > > > 5. Unload the modules, then load the new modules. (Or > > > > > > reboot for the easiest way.) > > > > > > > > > > > > About your questions concerning my modprobe.conf and > > > > > > what not. I don't have anything currently in their > > > > > > except ethernet and video. Since my remote wasn't > > > > > > working with lirc yet, there was no reason to put > > > > > > anything in there. Also, I am running gentoo, so I > > > > > > don't know the exact format of the modprobe.conf file, > > > > > > but my guess is you would just want the module name > > > > > > you would want to load. In this case it would just be > > > > > > lirc_mceusb, all the other modules required by lirc > > > > > > should be loaded. > > > > > > > > > > > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > Since I used apt-get to install lirc and > > > > > > > mythtv-suite, I take it that > > > > > > > is would be EXTREMELY difficult for me to compile > > > > > > > this new driver into > > > > > > > lirc especially since I have never compiled anything > > > > > > > in my
Re: [mythtv-users] Re: USB MCE IR Receiver
There is a lirc0.7.0_45.src RPM. Could I use the same command in your HOWTO that is used for the kernel source? rpm -i lirc-0.7.0-45.rhfc3.at.src.rpm ??? What do you think? Am I thinking correctly? On Mon, 14 Mar 2005 21:13:10 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > If you are using ATRPMs to install mythtv, then lirc-lib is already > installed. Since that is a certain version of LIRC that is used in > that setup, if you get the wrong version of LIRC to compile, it won't > work. That is why we need to know what version is on ATRPMs. I will > email that list and try and find out.I just did, let's see who > responds. Thanks! > > On Mon, 14 Mar 2005 19:57:11 -0700, Darren Richards > <[EMAIL PROTECTED]> wrote: > > Andy, > > > > If there's an update in the source code that may make my new IR > > receiver work, I'll definitely try my hand at compiling LIRC. Your IR > > blaster walkthrough already saved the day for me once before, so I > > have high confidence... I'll let you know how it goes. > > > > Thanks, > > darren > > > > On Mon, 14 Mar 2005 20:28:00 -0600, Andy Long <[EMAIL PROTECTED]> wrote: > > > If you'd like to give compiling LIRC another chance, Pete and I have > > > written a guide for doing it on FC3. It's directed at enabling more > > > devices than 2 with LIRC (now not needed for ATRPMS due to a change a > > > few days ago), but should be pretty straightforward. May be worth a > > > shot if you'd like to try. > > > > > > http://lircsetup.com/lirc/trouble/kernsource.php > > > > > > -Andy > > > > > > > > > On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards > > > <[EMAIL PROTECTED]> wrote: > > > > My USB MCE remote just came in the mail today. I figured if there's a > > > > link to it from Jarod's guide, I should be able to get it working. > > > > Imagine my dismay when I started searching the archives and came > > > > across this thread. Jim, I'm in exactly the same boat as you. Even > > > > if there was a magical fix in CVS, I've never successfully compiled > > > > anything in my life. I'm completely dependent upon apt-get and > > > > ATRPMS. > > > > > > > > Please, please keep us posted if you come up with anything. I'll > > > > start digging into this probably tomorrow, and maybe I'll have some > > > > luck... > > > > > > > > -darren > > > > > > > > > > > > On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman <[EMAIL PROTECTED]> > > > > wrote: > > > > > I just looked on ATRPMs website and there is no listing for getting > > > > > the source code for the lirc drivers. There is also no mention of > > > > > exactly what "CVS version" I am using (0.7.0pre 4 or 5 or 6 or 7 or > > > > > 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, > > > > > I have no idea. Anyone know what version I could be running? I would > > > > > LOVE to get this remote going so I could move on to bugging the list > > > > > about other problems! :-) Thanks! > > > > > > > > > > > > > > > On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL > > > > > PROTECTED]> wrote: > > > > > > > > > > > > Unless ATRPMS have been updated, then the only way to > > > > > > get this to work would be to compile the drivers. My > > > > > > guess is that these drivers will be updated in the > > > > > > not-too-distant-future, but exactly when that happens > > > > > > is up to the lirc maintainers. Then the RPMS will have > > > > > > to be udpated as well. > > > > > > > > > > > > Something you can try is to leave your current lirc > > > > > > installed. > > > > > > > > > > > > 1. Download the same version you have installed. > > > > > > 2. Copy the the previously attached source code to the > > > > > > appropriate place. > > > > > > 3. Configure and compile source. > > > > > > 4. Copy the new lirc_mceusb and lirc_dev modules over > > > > > > the existing files. (After making a backup of the > > > > > > originals of course.) > > > > > > 5. Unload the modules, then load the new modules. (Or > > > > > > reboot for the easiest way.) > > > > > > > > > > > > About your questions concerning my modprobe.conf and > > > > > > what not. I don't have anything currently in their > > > > > > except ethernet and video. Since my remote wasn't > > > > > > working with lirc yet, there was no reason to put > > > > > > anything in there. Also, I am running gentoo, so I > > > > > > don't know the exact format of the modprobe.conf file, > > > > > > but my guess is you would just want the module name > > > > > > you would want to load. In this case it would just be > > > > > > lirc_mceusb, all the other modules required by lirc > > > > > > should be loaded. > > > > > > > > > > > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > Since I used apt-get to install lirc and > > > > > > > mythtv-suite, I take it that > > > > > > > is would be EXTREMELY difficult for me to compile > > > > > > > this new driver into > > > > > > > lirc especially since I have never compiled anything > > > > > > > in
Re: [mythtv-users] Re: USB MCE IR Receiver
If you are using ATRPMs to install mythtv, then lirc-lib is already installed. Since that is a certain version of LIRC that is used in that setup, if you get the wrong version of LIRC to compile, it won't work. That is why we need to know what version is on ATRPMs. I will email that list and try and find out.I just did, let's see who responds. Thanks! On Mon, 14 Mar 2005 19:57:11 -0700, Darren Richards <[EMAIL PROTECTED]> wrote: > Andy, > > If there's an update in the source code that may make my new IR > receiver work, I'll definitely try my hand at compiling LIRC. Your IR > blaster walkthrough already saved the day for me once before, so I > have high confidence... I'll let you know how it goes. > > Thanks, > darren > > On Mon, 14 Mar 2005 20:28:00 -0600, Andy Long <[EMAIL PROTECTED]> wrote: > > If you'd like to give compiling LIRC another chance, Pete and I have > > written a guide for doing it on FC3. It's directed at enabling more > > devices than 2 with LIRC (now not needed for ATRPMS due to a change a > > few days ago), but should be pretty straightforward. May be worth a > > shot if you'd like to try. > > > > http://lircsetup.com/lirc/trouble/kernsource.php > > > > -Andy > > > > > > On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards > > <[EMAIL PROTECTED]> wrote: > > > My USB MCE remote just came in the mail today. I figured if there's a > > > link to it from Jarod's guide, I should be able to get it working. > > > Imagine my dismay when I started searching the archives and came > > > across this thread. Jim, I'm in exactly the same boat as you. Even > > > if there was a magical fix in CVS, I've never successfully compiled > > > anything in my life. I'm completely dependent upon apt-get and > > > ATRPMS. > > > > > > Please, please keep us posted if you come up with anything. I'll > > > start digging into this probably tomorrow, and maybe I'll have some > > > luck... > > > > > > -darren > > > > > > > > > On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > > > > I just looked on ATRPMs website and there is no listing for getting > > > > the source code for the lirc drivers. There is also no mention of > > > > exactly what "CVS version" I am using (0.7.0pre 4 or 5 or 6 or 7 or > > > > 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, > > > > I have no idea. Anyone know what version I could be running? I would > > > > LOVE to get this remote going so I could move on to bugging the list > > > > about other problems! :-) Thanks! > > > > > > > > > > > > On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL > > > > PROTECTED]> wrote: > > > > > > > > > > Unless ATRPMS have been updated, then the only way to > > > > > get this to work would be to compile the drivers. My > > > > > guess is that these drivers will be updated in the > > > > > not-too-distant-future, but exactly when that happens > > > > > is up to the lirc maintainers. Then the RPMS will have > > > > > to be udpated as well. > > > > > > > > > > Something you can try is to leave your current lirc > > > > > installed. > > > > > > > > > > 1. Download the same version you have installed. > > > > > 2. Copy the the previously attached source code to the > > > > > appropriate place. > > > > > 3. Configure and compile source. > > > > > 4. Copy the new lirc_mceusb and lirc_dev modules over > > > > > the existing files. (After making a backup of the > > > > > originals of course.) > > > > > 5. Unload the modules, then load the new modules. (Or > > > > > reboot for the easiest way.) > > > > > > > > > > About your questions concerning my modprobe.conf and > > > > > what not. I don't have anything currently in their > > > > > except ethernet and video. Since my remote wasn't > > > > > working with lirc yet, there was no reason to put > > > > > anything in there. Also, I am running gentoo, so I > > > > > don't know the exact format of the modprobe.conf file, > > > > > but my guess is you would just want the module name > > > > > you would want to load. In this case it would just be > > > > > lirc_mceusb, all the other modules required by lirc > > > > > should be loaded. > > > > > > > > > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > Since I used apt-get to install lirc and > > > > > > mythtv-suite, I take it that > > > > > > is would be EXTREMELY difficult for me to compile > > > > > > this new driver into > > > > > > lirc especially since I have never compiled anything > > > > > > in my entire life > > > > > > (except for those 2 semesters in college compiling C > > > > > > code that barely > > > > > > worked). As I understand it, mythtv-suite already > > > > > > has the lirc-lib > > > > > > included. Is there a way around all this? Does > > > > > > anyone know? My > > > > > > version of the mce_usb driver is listed as v0.2 but > > > > > > doesn't mention > > > > > > anything about this Dan Conti. Also, on ATRPMs it > > > > > > looks like Axel > > > >
Re: [mythtv-users] Re: USB MCE IR Receiver
Andy, If there's an update in the source code that may make my new IR receiver work, I'll definitely try my hand at compiling LIRC. Your IR blaster walkthrough already saved the day for me once before, so I have high confidence... I'll let you know how it goes. Thanks, darren On Mon, 14 Mar 2005 20:28:00 -0600, Andy Long <[EMAIL PROTECTED]> wrote: > If you'd like to give compiling LIRC another chance, Pete and I have > written a guide for doing it on FC3. It's directed at enabling more > devices than 2 with LIRC (now not needed for ATRPMS due to a change a > few days ago), but should be pretty straightforward. May be worth a > shot if you'd like to try. > > http://lircsetup.com/lirc/trouble/kernsource.php > > -Andy > > > On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards > <[EMAIL PROTECTED]> wrote: > > My USB MCE remote just came in the mail today. I figured if there's a > > link to it from Jarod's guide, I should be able to get it working. > > Imagine my dismay when I started searching the archives and came > > across this thread. Jim, I'm in exactly the same boat as you. Even > > if there was a magical fix in CVS, I've never successfully compiled > > anything in my life. I'm completely dependent upon apt-get and > > ATRPMS. > > > > Please, please keep us posted if you come up with anything. I'll > > start digging into this probably tomorrow, and maybe I'll have some > > luck... > > > > -darren > > > > > > On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > > > I just looked on ATRPMs website and there is no listing for getting > > > the source code for the lirc drivers. There is also no mention of > > > exactly what "CVS version" I am using (0.7.0pre 4 or 5 or 6 or 7 or > > > 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, > > > I have no idea. Anyone know what version I could be running? I would > > > LOVE to get this remote going so I could move on to bugging the list > > > about other problems! :-) Thanks! > > > > > > > > > On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > Unless ATRPMS have been updated, then the only way to > > > > get this to work would be to compile the drivers. My > > > > guess is that these drivers will be updated in the > > > > not-too-distant-future, but exactly when that happens > > > > is up to the lirc maintainers. Then the RPMS will have > > > > to be udpated as well. > > > > > > > > Something you can try is to leave your current lirc > > > > installed. > > > > > > > > 1. Download the same version you have installed. > > > > 2. Copy the the previously attached source code to the > > > > appropriate place. > > > > 3. Configure and compile source. > > > > 4. Copy the new lirc_mceusb and lirc_dev modules over > > > > the existing files. (After making a backup of the > > > > originals of course.) > > > > 5. Unload the modules, then load the new modules. (Or > > > > reboot for the easiest way.) > > > > > > > > About your questions concerning my modprobe.conf and > > > > what not. I don't have anything currently in their > > > > except ethernet and video. Since my remote wasn't > > > > working with lirc yet, there was no reason to put > > > > anything in there. Also, I am running gentoo, so I > > > > don't know the exact format of the modprobe.conf file, > > > > but my guess is you would just want the module name > > > > you would want to load. In this case it would just be > > > > lirc_mceusb, all the other modules required by lirc > > > > should be loaded. > > > > > > > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > > > > > > > Since I used apt-get to install lirc and > > > > > mythtv-suite, I take it that > > > > > is would be EXTREMELY difficult for me to compile > > > > > this new driver into > > > > > lirc especially since I have never compiled anything > > > > > in my entire life > > > > > (except for those 2 semesters in college compiling C > > > > > code that barely > > > > > worked). As I understand it, mythtv-suite already > > > > > has the lirc-lib > > > > > included. Is there a way around all this? Does > > > > > anyone know? My > > > > > version of the mce_usb driver is listed as v0.2 but > > > > > doesn't mention > > > > > anything about this Dan Conti. Also, on ATRPMs it > > > > > looks like Axel > > > > > last updated the lirc drivers on Mar 5th 12:27 CET. > > > > > Could you tell me > > > > > how you were able to get your MCE IR receiver up and > > > > > working (assuming > > > > > I have the right driver). What did you put in your > > > > > /etc/modprobe.conf? I didn't have a /dev/lirc0 only > > > > > a /dev/lircd so > > > > > in my rc.local I put these statements in: > > > > > > > > > > ln -s /dev/lircd /dev/lirc0 > > > > > chmod 666 /dev/lirc0 > > > > > > > > > > /sbin/modprobe lirc_mceusb > > > > > /usr/sbin/lircd --device=/dev/lirc0 > > > > > --output=/dev/lircd > > > > > > > > > > Am I incorrect? Should I be doing somethi
Re: [mythtv-users] Re: USB MCE IR Receiver
After reading this tutorial, it seems that I could damage my current lirc install. Is this correct? I guess I could always save the lirc_mceusb file I need...and then re-install my entire frontend exactly the way I have it now (kernel and all). Not horrible I guess, considering I have done it several times. It still comes down to knowing which version of lirc to grab from the CVS snapshots. Any thoughts? On Mon, 14 Mar 2005 20:28:00 -0600, Andy Long <[EMAIL PROTECTED]> wrote: > If you'd like to give compiling LIRC another chance, Pete and I have > written a guide for doing it on FC3. It's directed at enabling more > devices than 2 with LIRC (now not needed for ATRPMS due to a change a > few days ago), but should be pretty straightforward. May be worth a > shot if you'd like to try. > > http://lircsetup.com/lirc/trouble/kernsource.php > > -Andy > > On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards > <[EMAIL PROTECTED]> wrote: > > My USB MCE remote just came in the mail today. I figured if there's a > > link to it from Jarod's guide, I should be able to get it working. > > Imagine my dismay when I started searching the archives and came > > across this thread. Jim, I'm in exactly the same boat as you. Even > > if there was a magical fix in CVS, I've never successfully compiled > > anything in my life. I'm completely dependent upon apt-get and > > ATRPMS. > > > > Please, please keep us posted if you come up with anything. I'll > > start digging into this probably tomorrow, and maybe I'll have some > > luck... > > > > -darren > > > > > > On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > > > I just looked on ATRPMs website and there is no listing for getting > > > the source code for the lirc drivers. There is also no mention of > > > exactly what "CVS version" I am using (0.7.0pre 4 or 5 or 6 or 7 or > > > 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, > > > I have no idea. Anyone know what version I could be running? I would > > > LOVE to get this remote going so I could move on to bugging the list > > > about other problems! :-) Thanks! > > > > > > > > > On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > Unless ATRPMS have been updated, then the only way to > > > > get this to work would be to compile the drivers. My > > > > guess is that these drivers will be updated in the > > > > not-too-distant-future, but exactly when that happens > > > > is up to the lirc maintainers. Then the RPMS will have > > > > to be udpated as well. > > > > > > > > Something you can try is to leave your current lirc > > > > installed. > > > > > > > > 1. Download the same version you have installed. > > > > 2. Copy the the previously attached source code to the > > > > appropriate place. > > > > 3. Configure and compile source. > > > > 4. Copy the new lirc_mceusb and lirc_dev modules over > > > > the existing files. (After making a backup of the > > > > originals of course.) > > > > 5. Unload the modules, then load the new modules. (Or > > > > reboot for the easiest way.) > > > > > > > > About your questions concerning my modprobe.conf and > > > > what not. I don't have anything currently in their > > > > except ethernet and video. Since my remote wasn't > > > > working with lirc yet, there was no reason to put > > > > anything in there. Also, I am running gentoo, so I > > > > don't know the exact format of the modprobe.conf file, > > > > but my guess is you would just want the module name > > > > you would want to load. In this case it would just be > > > > lirc_mceusb, all the other modules required by lirc > > > > should be loaded. > > > > > > > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > > > > > > > Since I used apt-get to install lirc and > > > > > mythtv-suite, I take it that > > > > > is would be EXTREMELY difficult for me to compile > > > > > this new driver into > > > > > lirc especially since I have never compiled anything > > > > > in my entire life > > > > > (except for those 2 semesters in college compiling C > > > > > code that barely > > > > > worked). As I understand it, mythtv-suite already > > > > > has the lirc-lib > > > > > included. Is there a way around all this? Does > > > > > anyone know? My > > > > > version of the mce_usb driver is listed as v0.2 but > > > > > doesn't mention > > > > > anything about this Dan Conti. Also, on ATRPMs it > > > > > looks like Axel > > > > > last updated the lirc drivers on Mar 5th 12:27 CET. > > > > > Could you tell me > > > > > how you were able to get your MCE IR receiver up and > > > > > working (assuming > > > > > I have the right driver). What did you put in your > > > > > /etc/modprobe.conf? I didn't have a /dev/lirc0 only > > > > > a /dev/lircd so > > > > > in my rc.local I put these statements in: > > > > > > > > > > ln -s /dev/lircd /dev/lirc0 > > > > > chmod 666 /dev/lirc0 > > > > > > > > > > /sbin/modprobe lirc_mceusb > > > > >
Re: [mythtv-users] Re: USB MCE IR Receiver
If you'd like to give compiling LIRC another chance, Pete and I have written a guide for doing it on FC3. It's directed at enabling more devices than 2 with LIRC (now not needed for ATRPMS due to a change a few days ago), but should be pretty straightforward. May be worth a shot if you'd like to try. http://lircsetup.com/lirc/trouble/kernsource.php -Andy On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards <[EMAIL PROTECTED]> wrote: > My USB MCE remote just came in the mail today. I figured if there's a > link to it from Jarod's guide, I should be able to get it working. > Imagine my dismay when I started searching the archives and came > across this thread. Jim, I'm in exactly the same boat as you. Even > if there was a magical fix in CVS, I've never successfully compiled > anything in my life. I'm completely dependent upon apt-get and > ATRPMS. > > Please, please keep us posted if you come up with anything. I'll > start digging into this probably tomorrow, and maybe I'll have some > luck... > > -darren > > > On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > > I just looked on ATRPMs website and there is no listing for getting > > the source code for the lirc drivers. There is also no mention of > > exactly what "CVS version" I am using (0.7.0pre 4 or 5 or 6 or 7 or > > 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, > > I have no idea. Anyone know what version I could be running? I would > > LOVE to get this remote going so I could move on to bugging the list > > about other problems! :-) Thanks! > > > > > > On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > > wrote: > > > > > > Unless ATRPMS have been updated, then the only way to > > > get this to work would be to compile the drivers. My > > > guess is that these drivers will be updated in the > > > not-too-distant-future, but exactly when that happens > > > is up to the lirc maintainers. Then the RPMS will have > > > to be udpated as well. > > > > > > Something you can try is to leave your current lirc > > > installed. > > > > > > 1. Download the same version you have installed. > > > 2. Copy the the previously attached source code to the > > > appropriate place. > > > 3. Configure and compile source. > > > 4. Copy the new lirc_mceusb and lirc_dev modules over > > > the existing files. (After making a backup of the > > > originals of course.) > > > 5. Unload the modules, then load the new modules. (Or > > > reboot for the easiest way.) > > > > > > About your questions concerning my modprobe.conf and > > > what not. I don't have anything currently in their > > > except ethernet and video. Since my remote wasn't > > > working with lirc yet, there was no reason to put > > > anything in there. Also, I am running gentoo, so I > > > don't know the exact format of the modprobe.conf file, > > > but my guess is you would just want the module name > > > you would want to load. In this case it would just be > > > lirc_mceusb, all the other modules required by lirc > > > should be loaded. > > > > > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > > > > > Since I used apt-get to install lirc and > > > > mythtv-suite, I take it that > > > > is would be EXTREMELY difficult for me to compile > > > > this new driver into > > > > lirc especially since I have never compiled anything > > > > in my entire life > > > > (except for those 2 semesters in college compiling C > > > > code that barely > > > > worked). As I understand it, mythtv-suite already > > > > has the lirc-lib > > > > included. Is there a way around all this? Does > > > > anyone know? My > > > > version of the mce_usb driver is listed as v0.2 but > > > > doesn't mention > > > > anything about this Dan Conti. Also, on ATRPMs it > > > > looks like Axel > > > > last updated the lirc drivers on Mar 5th 12:27 CET. > > > > Could you tell me > > > > how you were able to get your MCE IR receiver up and > > > > working (assuming > > > > I have the right driver). What did you put in your > > > > /etc/modprobe.conf? I didn't have a /dev/lirc0 only > > > > a /dev/lircd so > > > > in my rc.local I put these statements in: > > > > > > > > ln -s /dev/lircd /dev/lirc0 > > > > chmod 666 /dev/lirc0 > > > > > > > > /sbin/modprobe lirc_mceusb > > > > /usr/sbin/lircd --device=/dev/lirc0 > > > > --output=/dev/lircd > > > > > > > > Am I incorrect? Should I be doing something > > > > different? Thanks! > > > > > > > > > > > > On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman > > > > <[EMAIL PROTECTED]> wrote: > > > > > Since I used apt-get to install lirc and > > > > mythtv-suite, I take it that > > > > > is would be EXTREMELY difficult for me to compile > > > > this new driver into > > > > > lirc especially since I have never compiled > > > > anything in my entire life > > > > > (except for those 2 semesters in college compiling > > > > C code that barely > > > > > worked). As I understand it, mythtv-suite already > > > > has th
Re: [mythtv-users] Re: USB MCE IR Receiver
My USB MCE remote just came in the mail today. I figured if there's a link to it from Jarod's guide, I should be able to get it working. Imagine my dismay when I started searching the archives and came across this thread. Jim, I'm in exactly the same boat as you. Even if there was a magical fix in CVS, I've never successfully compiled anything in my life. I'm completely dependent upon apt-get and ATRPMS. Please, please keep us posted if you come up with anything. I'll start digging into this probably tomorrow, and maybe I'll have some luck... -darren On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > I just looked on ATRPMs website and there is no listing for getting > the source code for the lirc drivers. There is also no mention of > exactly what "CVS version" I am using (0.7.0pre 4 or 5 or 6 or 7 or > 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, > I have no idea. Anyone know what version I could be running? I would > LOVE to get this remote going so I could move on to bugging the list > about other problems! :-) Thanks! > > > On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > wrote: > > > > Unless ATRPMS have been updated, then the only way to > > get this to work would be to compile the drivers. My > > guess is that these drivers will be updated in the > > not-too-distant-future, but exactly when that happens > > is up to the lirc maintainers. Then the RPMS will have > > to be udpated as well. > > > > Something you can try is to leave your current lirc > > installed. > > > > 1. Download the same version you have installed. > > 2. Copy the the previously attached source code to the > > appropriate place. > > 3. Configure and compile source. > > 4. Copy the new lirc_mceusb and lirc_dev modules over > > the existing files. (After making a backup of the > > originals of course.) > > 5. Unload the modules, then load the new modules. (Or > > reboot for the easiest way.) > > > > About your questions concerning my modprobe.conf and > > what not. I don't have anything currently in their > > except ethernet and video. Since my remote wasn't > > working with lirc yet, there was no reason to put > > anything in there. Also, I am running gentoo, so I > > don't know the exact format of the modprobe.conf file, > > but my guess is you would just want the module name > > you would want to load. In this case it would just be > > lirc_mceusb, all the other modules required by lirc > > should be loaded. > > > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > > > Since I used apt-get to install lirc and > > > mythtv-suite, I take it that > > > is would be EXTREMELY difficult for me to compile > > > this new driver into > > > lirc especially since I have never compiled anything > > > in my entire life > > > (except for those 2 semesters in college compiling C > > > code that barely > > > worked). As I understand it, mythtv-suite already > > > has the lirc-lib > > > included. Is there a way around all this? Does > > > anyone know? My > > > version of the mce_usb driver is listed as v0.2 but > > > doesn't mention > > > anything about this Dan Conti. Also, on ATRPMs it > > > looks like Axel > > > last updated the lirc drivers on Mar 5th 12:27 CET. > > > Could you tell me > > > how you were able to get your MCE IR receiver up and > > > working (assuming > > > I have the right driver). What did you put in your > > > /etc/modprobe.conf? I didn't have a /dev/lirc0 only > > > a /dev/lircd so > > > in my rc.local I put these statements in: > > > > > > ln -s /dev/lircd /dev/lirc0 > > > chmod 666 /dev/lirc0 > > > > > > /sbin/modprobe lirc_mceusb > > > /usr/sbin/lircd --device=/dev/lirc0 > > > --output=/dev/lircd > > > > > > Am I incorrect? Should I be doing something > > > different? Thanks! > > > > > > > > > On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman > > > <[EMAIL PROTECTED]> wrote: > > > > Since I used apt-get to install lirc and > > > mythtv-suite, I take it that > > > > is would be EXTREMELY difficult for me to compile > > > this new driver into > > > > lirc especially since I have never compiled > > > anything in my entire life > > > > (except for those 2 semesters in college compiling > > > C code that barely > > > > worked). As I understand it, mythtv-suite already > > > has the lirc-lib > > > > included. Is there a way around all this? Does > > > anyone know? My > > > > version of the mce_usb driver is listed as v0.2 > > > but doesn't mention > > > > anything about this Dan Conti. Also, on ATRPMs it > > > looks like Axel > > > > last updated the lirc drivers on Mar 5th 12:27 > > > CET. Could you tell me > > > > how you were able to get your MCE IR receiver up > > > and working (assuming > > > > I have the right driver). What did you put in > > > your > > > > /etc/modprobe.conf? I didn't have a /dev/lirc0 > > > only a /dev/lircd so > > > > in my rc.local I put these statements in: > > > > > > > > ln -s /dev/lircd /
Re: [mythtv-users] Re: USB MCE IR Receiver
I just looked on ATRPMs website and there is no listing for getting the source code for the lirc drivers. There is also no mention of exactly what "CVS version" I am using (0.7.0pre 4 or 5 or 6 or 7 or 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, I have no idea. Anyone know what version I could be running? I would LOVE to get this remote going so I could move on to bugging the list about other problems! :-) Thanks! On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> wrote: > > Unless ATRPMS have been updated, then the only way to > get this to work would be to compile the drivers. My > guess is that these drivers will be updated in the > not-too-distant-future, but exactly when that happens > is up to the lirc maintainers. Then the RPMS will have > to be udpated as well. > > Something you can try is to leave your current lirc > installed. > > 1. Download the same version you have installed. > 2. Copy the the previously attached source code to the > appropriate place. > 3. Configure and compile source. > 4. Copy the new lirc_mceusb and lirc_dev modules over > the existing files. (After making a backup of the > originals of course.) > 5. Unload the modules, then load the new modules. (Or > reboot for the easiest way.) > > About your questions concerning my modprobe.conf and > what not. I don't have anything currently in their > except ethernet and video. Since my remote wasn't > working with lirc yet, there was no reason to put > anything in there. Also, I am running gentoo, so I > don't know the exact format of the modprobe.conf file, > but my guess is you would just want the module name > you would want to load. In this case it would just be > lirc_mceusb, all the other modules required by lirc > should be loaded. > > --- Jim Oltman <[EMAIL PROTECTED]> wrote: > > > Since I used apt-get to install lirc and > > mythtv-suite, I take it that > > is would be EXTREMELY difficult for me to compile > > this new driver into > > lirc especially since I have never compiled anything > > in my entire life > > (except for those 2 semesters in college compiling C > > code that barely > > worked). As I understand it, mythtv-suite already > > has the lirc-lib > > included. Is there a way around all this? Does > > anyone know? My > > version of the mce_usb driver is listed as v0.2 but > > doesn't mention > > anything about this Dan Conti. Also, on ATRPMs it > > looks like Axel > > last updated the lirc drivers on Mar 5th 12:27 CET. > > Could you tell me > > how you were able to get your MCE IR receiver up and > > working (assuming > > I have the right driver). What did you put in your > > /etc/modprobe.conf? I didn't have a /dev/lirc0 only > > a /dev/lircd so > > in my rc.local I put these statements in: > > > > ln -s /dev/lircd /dev/lirc0 > > chmod 666 /dev/lirc0 > > > > /sbin/modprobe lirc_mceusb > > /usr/sbin/lircd --device=/dev/lirc0 > > --output=/dev/lircd > > > > Am I incorrect? Should I be doing something > > different? Thanks! > > > > > > On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman > > <[EMAIL PROTECTED]> wrote: > > > Since I used apt-get to install lirc and > > mythtv-suite, I take it that > > > is would be EXTREMELY difficult for me to compile > > this new driver into > > > lirc especially since I have never compiled > > anything in my entire life > > > (except for those 2 semesters in college compiling > > C code that barely > > > worked). As I understand it, mythtv-suite already > > has the lirc-lib > > > included. Is there a way around all this? Does > > anyone know? My > > > version of the mce_usb driver is listed as v0.2 > > but doesn't mention > > > anything about this Dan Conti. Also, on ATRPMs it > > looks like Axel > > > last updated the lirc drivers on Mar 5th 12:27 > > CET. Could you tell me > > > how you were able to get your MCE IR receiver up > > and working (assuming > > > I have the right driver). What did you put in > > your > > > /etc/modprobe.conf? I didn't have a /dev/lirc0 > > only a /dev/lircd so > > > in my rc.local I put these statements in: > > > > > > ln -s /dev/lircd /dev/lirc0 > > > chmod 666 /dev/lirc0 > > > > > > /sbin/modprobe lirc_mceusb > > > /usr/sbin/lircd --device=/dev/lirc0 > > --output=/dev/lircd > > > > > > Am I incorrect? Should I be doing something > > different? Thanks! > > > > > > On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe > > Huffner <[EMAIL PROTECTED]> wrote: > > > > Just an FYI for those of us who bought one of > > the > > > > updated MCE remotes and receivers. I was > > checking out > > > > the lirc mailing list and someone has update the > > > > driver to include support. From what I can tell > > the > > > > update has not been updated in CVS. > > > > > > > > I found the info at: > > > > > > > http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc > > > > > > > > Basically what I did was overwrite the > > lirc_mceusb.c > > > > in the drivers/lirc_mceusb directory with the
Re: [mythtv-users] Re: USB MCE IR Receiver
Unless ATRPMS have been updated, then the only way to get this to work would be to compile the drivers. My guess is that these drivers will be updated in the not-too-distant-future, but exactly when that happens is up to the lirc maintainers. Then the RPMS will have to be udpated as well. Something you can try is to leave your current lirc installed. 1. Download the same version you have installed. 2. Copy the the previously attached source code to the appropriate place. 3. Configure and compile source. 4. Copy the new lirc_mceusb and lirc_dev modules over the existing files. (After making a backup of the originals of course.) 5. Unload the modules, then load the new modules. (Or reboot for the easiest way.) About your questions concerning my modprobe.conf and what not. I don't have anything currently in their except ethernet and video. Since my remote wasn't working with lirc yet, there was no reason to put anything in there. Also, I am running gentoo, so I don't know the exact format of the modprobe.conf file, but my guess is you would just want the module name you would want to load. In this case it would just be lirc_mceusb, all the other modules required by lirc should be loaded. --- Jim Oltman <[EMAIL PROTECTED]> wrote: > Since I used apt-get to install lirc and > mythtv-suite, I take it that > is would be EXTREMELY difficult for me to compile > this new driver into > lirc especially since I have never compiled anything > in my entire life > (except for those 2 semesters in college compiling C > code that barely > worked). As I understand it, mythtv-suite already > has the lirc-lib > included. Is there a way around all this? Does > anyone know? My > version of the mce_usb driver is listed as v0.2 but > doesn't mention > anything about this Dan Conti. Also, on ATRPMs it > looks like Axel > last updated the lirc drivers on Mar 5th 12:27 CET. > Could you tell me > how you were able to get your MCE IR receiver up and > working (assuming > I have the right driver). What did you put in your > /etc/modprobe.conf? I didn't have a /dev/lirc0 only > a /dev/lircd so > in my rc.local I put these statements in: > > ln -s /dev/lircd /dev/lirc0 > chmod 666 /dev/lirc0 > > /sbin/modprobe lirc_mceusb > /usr/sbin/lircd --device=/dev/lirc0 > --output=/dev/lircd > > Am I incorrect? Should I be doing something > different? Thanks! > > > On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman > <[EMAIL PROTECTED]> wrote: > > Since I used apt-get to install lirc and > mythtv-suite, I take it that > > is would be EXTREMELY difficult for me to compile > this new driver into > > lirc especially since I have never compiled > anything in my entire life > > (except for those 2 semesters in college compiling > C code that barely > > worked). As I understand it, mythtv-suite already > has the lirc-lib > > included. Is there a way around all this? Does > anyone know? My > > version of the mce_usb driver is listed as v0.2 > but doesn't mention > > anything about this Dan Conti. Also, on ATRPMs it > looks like Axel > > last updated the lirc drivers on Mar 5th 12:27 > CET. Could you tell me > > how you were able to get your MCE IR receiver up > and working (assuming > > I have the right driver). What did you put in > your > > /etc/modprobe.conf? I didn't have a /dev/lirc0 > only a /dev/lircd so > > in my rc.local I put these statements in: > > > > ln -s /dev/lircd /dev/lirc0 > > chmod 666 /dev/lirc0 > > > > /sbin/modprobe lirc_mceusb > > /usr/sbin/lircd --device=/dev/lirc0 > --output=/dev/lircd > > > > Am I incorrect? Should I be doing something > different? Thanks! > > > > On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe > Huffner <[EMAIL PROTECTED]> wrote: > > > Just an FYI for those of us who bought one of > the > > > updated MCE remotes and receivers. I was > checking out > > > the lirc mailing list and someone has update the > > > driver to include support. From what I can tell > the > > > update has not been updated in CVS. > > > > > > I found the info at: > > > > http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc > > > > > > Basically what I did was overwrite the > lirc_mceusb.c > > > in the drivers/lirc_mceusb directory with the > source > > > found in the mailing liste. (I have attached the > new > > > source file.) Then went through the install > process > > > documented. I used version .7.0 of lirc. > > > > > > Please note, from what I have read and > experienced, > > > there are some initialization problems. What > seemed to > > > "fix it" was unplugging the receiver and > plugging it > > > back in, until I no longer got an error message > > > stating the device did not initialize. You can > check > > > this by running "tail -f /var/log/messages". > Also, I > > > read that running kernel 2.6.11 seemed to fix > the > > > initialization problem. However I cannot confirm > this > > > as I am running Gentoo Dev Kernel 2.6.9-r9. > Another > > > problem I am having is that I am getting >
Re: [mythtv-users] Re: USB MCE IR Receiver
Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666 /dev/lirc0 /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd Am I incorrect? Should I be doing something different? Thanks! On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > Since I used apt-get to install lirc and mythtv-suite, I take it that > is would be EXTREMELY difficult for me to compile this new driver into > lirc especially since I have never compiled anything in my entire life > (except for those 2 semesters in college compiling C code that barely > worked). As I understand it, mythtv-suite already has the lirc-lib > included. Is there a way around all this? Does anyone know? My > version of the mce_usb driver is listed as v0.2 but doesn't mention > anything about this Dan Conti. Also, on ATRPMs it looks like Axel > last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me > how you were able to get your MCE IR receiver up and working (assuming > I have the right driver). What did you put in your > /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so > in my rc.local I put these statements in: > > ln -s /dev/lircd /dev/lirc0 > chmod 666 /dev/lirc0 > > /sbin/modprobe lirc_mceusb > /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd > > Am I incorrect? Should I be doing something different? Thanks! > > On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> > wrote: > > Just an FYI for those of us who bought one of the > > updated MCE remotes and receivers. I was checking out > > the lirc mailing list and someone has update the > > driver to include support. From what I can tell the > > update has not been updated in CVS. > > > > I found the info at: > > http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc > > > > Basically what I did was overwrite the lirc_mceusb.c > > in the drivers/lirc_mceusb directory with the source > > found in the mailing liste. (I have attached the new > > source file.) Then went through the install process > > documented. I used version .7.0 of lirc. > > > > Please note, from what I have read and experienced, > > there are some initialization problems. What seemed to > > "fix it" was unplugging the receiver and plugging it > > back in, until I no longer got an error message > > stating the device did not initialize. You can check > > this by running "tail -f /var/log/messages". Also, I > > read that running kernel 2.6.11 seemed to fix the > > initialization problem. However I cannot confirm this > > as I am running Gentoo Dev Kernel 2.6.9-r9. Another > > problem I am having is that I am getting non-stop > > error messages stating: > > > > "usb 2-2: bulk timeout on ep1in" > > > > In fact, I was getting about 4 of those messages per > > second. If/when I get time I am planning to upgrade to > > 2.6.11 to see if this fixes the issue. > > > > -joe > ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Fwd: [mythtv-users] Re: USB MCE IR Receiver
Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666 /dev/lirc0 /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd Am I incorrect? Should I be doing something different? Thanks! On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner <[EMAIL PROTECTED]> wrote: > Just an FYI for those of us who bought one of the > updated MCE remotes and receivers. I was checking out > the lirc mailing list and someone has update the > driver to include support. From what I can tell the > update has not been updated in CVS. > > I found the info at: > http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc > > Basically what I did was overwrite the lirc_mceusb.c > in the drivers/lirc_mceusb directory with the source > found in the mailing liste. (I have attached the new > source file.) Then went through the install process > documented. I used version .7.0 of lirc. > > Please note, from what I have read and experienced, > there are some initialization problems. What seemed to > "fix it" was unplugging the receiver and plugging it > back in, until I no longer got an error message > stating the device did not initialize. You can check > this by running "tail -f /var/log/messages". Also, I > read that running kernel 2.6.11 seemed to fix the > initialization problem. However I cannot confirm this > as I am running Gentoo Dev Kernel 2.6.9-r9. Another > problem I am having is that I am getting non-stop > error messages stating: > > "usb 2-2: bulk timeout on ep1in" > > In fact, I was getting about 4 of those messages per > second. If/when I get time I am planning to upgrade to > 2.6.11 to see if this fixes the issue. > > -joe ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Just an FYI for those of us who bought one of the updated MCE remotes and receivers. I was checking out the lirc mailing list and someone has update the driver to include support. From what I can tell the update has not been updated in CVS. I found the info at: http://search.gmane.org/?query=mce&group=gmane.comp.hardware.lirc Basically what I did was overwrite the lirc_mceusb.c in the drivers/lirc_mceusb directory with the source found in the mailing liste. (I have attached the new source file.) Then went through the install process documented. I used version .7.0 of lirc. Please note, from what I have read and experienced, there are some initialization problems. What seemed to "fix it" was unplugging the receiver and plugging it back in, until I no longer got an error message stating the device did not initialize. You can check this by running "tail -f /var/log/messages". Also, I read that running kernel 2.6.11 seemed to fix the initialization problem. However I cannot confirm this as I am running Gentoo Dev Kernel 2.6.9-r9. Another problem I am having is that I am getting non-stop error messages stating: "usb 2-2: bulk timeout on ep1in" In fact, I was getting about 4 of those messages per second. If/when I get time I am planning to upgrade to 2.6.11 to see if this fixes the issue. -joe --- Jim Oltman <[EMAIL PROTECTED]> wrote: > After deleting the section in my rc.local about the > mknod /dev/lirc0 c > 61 0 and replacing it with: > > ln -s /dev/lircd /dev/lirc0 > > I am no longer getting errors from lircd in the > /var/log/messages. > IRW runs but I am not seeing anything when I press > buttons on my > Hauppauge remote (it has also been setup in the > correct lircrc files). > When I run irrecord I am getting errors about lircd > not being > started. I am going to try commenting out the other > section in > rc.local pertaining to MCEUSB and see what happens. > > > On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman > <[EMAIL PROTECTED]> wrote: > > Here is where I am at so far. In my > /etc/rc.d/rc.local I made these changes... > > > > #!/bin/sh > > # > > # This script will be executed *after* all the > other init scripts. > > # You can put your own initialization stuff in > here if you don't > > # want to do the full Sys V style init stuff. > > > > touch /var/lock/subsys/local > > mknod /dev/lirc0 c 61 0 -I added this > line in hopes it > > would attach to a line in my modprobe > > > > /usr/X11R6/bin/xset -dpms > > /usr/X11R6/bin/xset s off > > /usr/bin/mtd --daemon > > > > # I added these next two lines > > > > /sbin/modprobe lirc_mceusb > > /usr/sbin/lircd --device=/dev/lirc0 > --output=/dev/lircd > > > > In my /etc/modprobe.conf I have added this line: > > > > alias char-major-61 lirc_mceusb > > > > After implementing these changes, I can do a cat > /var/log/messages and > > see what I showed you before about the driver > being loaded for the USB > > Microsoft IR Transceiver. But I also get this > listed: > > > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > accepted new client on > > /dev/lircd > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > could not open /dev/lirc0 > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > default_init(): No such device > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: > caught signal > > > > I am however getting errors on boot in the > Show/Hide Details window. > > Where can I view the errors that it is showing me? > They disappear to > > quickly to read. I am pretty sure the info I want > to see (about the > > errors on boot in Show/Hide window) is not listed > in > > /var/log/messages. > > > > On Sun, 13 Mar 2005 18:38:09 -0600, Ron Johnson > <[EMAIL PROTECTED]> wrote: > > > On Sun, 2005-03-13 at 17:58 -0600, Jim Oltman > wrote: > > > > What I meant in that statement is that I got > it to recognize the > > > > receiver in the /var/log/messages but it is > still not working. > > > > > > Yes, but *how* did you get "it" to recognize the > receiver? > > > > > > P.S. - Please do not erase the whole text of the > email you are > > > replying to. That makes it quite difficult to > follow the thread. > > > > > > -- > > > > - > > > Ron Johnson, Jr. > > > Jefferson, LA USA > > > PGP Key ID 8834C06B I prefer encrypted mail. > > > > > > Legality/morality of using open wireless points: > > > "If I leave my door unlocked are you going to > come into my house > > > in the middle of the night because you need to > use the restroom? > > > I pay a fixed rate for water. It's cold water so > there is no > > > electricity usage. No financial loss. I have 2.5 > bathrooms, so no > > > loss of usage on my end. Is this OK? Please, try > this and we'll > > > see if it's OK." > > > > http://www.warchalking.org/comments/2002/9/22/223831/236/135 > > > > > > > > > ___ > > > mythtv-users mailing list > > > mythtv-users@mythtv.org > > > > http:/
Re: [mythtv-users] Re: USB MCE IR Receiver
After deleting the section in my rc.local about the mknod /dev/lirc0 c 61 0 and replacing it with: ln -s /dev/lircd /dev/lirc0 I am no longer getting errors from lircd in the /var/log/messages. IRW runs but I am not seeing anything when I press buttons on my Hauppauge remote (it has also been setup in the correct lircrc files). When I run irrecord I am getting errors about lircd not being started. I am going to try commenting out the other section in rc.local pertaining to MCEUSB and see what happens. On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > Here is where I am at so far. In my /etc/rc.d/rc.local I made these > changes... > > #!/bin/sh > # > # This script will be executed *after* all the other init scripts. > # You can put your own initialization stuff in here if you don't > # want to do the full Sys V style init stuff. > > touch /var/lock/subsys/local > mknod /dev/lirc0 c 61 0 -I added this line in hopes it > would attach to a line in my modprobe > > /usr/X11R6/bin/xset -dpms > /usr/X11R6/bin/xset s off > /usr/bin/mtd --daemon > > # I added these next two lines > > /sbin/modprobe lirc_mceusb > /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd > > In my /etc/modprobe.conf I have added this line: > > alias char-major-61 lirc_mceusb > > After implementing these changes, I can do a cat /var/log/messages and > see what I showed you before about the driver being loaded for the USB > Microsoft IR Transceiver. But I also get this listed: > > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: accepted new client on > /dev/lircd > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: could not open /dev/lirc0 > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: default_init(): No such device > Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: caught signal > > I am however getting errors on boot in the Show/Hide Details window. > Where can I view the errors that it is showing me? They disappear to > quickly to read. I am pretty sure the info I want to see (about the > errors on boot in Show/Hide window) is not listed in > /var/log/messages. > > On Sun, 13 Mar 2005 18:38:09 -0600, Ron Johnson <[EMAIL PROTECTED]> wrote: > > On Sun, 2005-03-13 at 17:58 -0600, Jim Oltman wrote: > > > What I meant in that statement is that I got it to recognize the > > > receiver in the /var/log/messages but it is still not working. > > > > Yes, but *how* did you get "it" to recognize the receiver? > > > > P.S. - Please do not erase the whole text of the email you are > > replying to. That makes it quite difficult to follow the thread. > > > > -- > > - > > Ron Johnson, Jr. > > Jefferson, LA USA > > PGP Key ID 8834C06B I prefer encrypted mail. > > > > Legality/morality of using open wireless points: > > "If I leave my door unlocked are you going to come into my house > > in the middle of the night because you need to use the restroom? > > I pay a fixed rate for water. It's cold water so there is no > > electricity usage. No financial loss. I have 2.5 bathrooms, so no > > loss of usage on my end. Is this OK? Please, try this and we'll > > see if it's OK." > > http://www.warchalking.org/comments/2002/9/22/223831/236/135 > > > > > > ___ > > mythtv-users mailing list > > mythtv-users@mythtv.org > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > > > > > > > ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Here is where I am at so far. In my /etc/rc.d/rc.local I made these changes... #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local mknod /dev/lirc0 c 61 0 -I added this line in hopes it would attach to a line in my modprobe /usr/X11R6/bin/xset -dpms /usr/X11R6/bin/xset s off /usr/bin/mtd --daemon # I added these next two lines /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd In my /etc/modprobe.conf I have added this line: alias char-major-61 lirc_mceusb After implementing these changes, I can do a cat /var/log/messages and see what I showed you before about the driver being loaded for the USB Microsoft IR Transceiver. But I also get this listed: Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: accepted new client on /dev/lircd Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: could not open /dev/lirc0 Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: default_init(): No such device Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: caught signal I am however getting errors on boot in the Show/Hide Details window. Where can I view the errors that it is showing me? They disappear to quickly to read. I am pretty sure the info I want to see (about the errors on boot in Show/Hide window) is not listed in /var/log/messages. On Sun, 13 Mar 2005 18:38:09 -0600, Ron Johnson <[EMAIL PROTECTED]> wrote: > On Sun, 2005-03-13 at 17:58 -0600, Jim Oltman wrote: > > What I meant in that statement is that I got it to recognize the > > receiver in the /var/log/messages but it is still not working. > > Yes, but *how* did you get "it" to recognize the receiver? > > P.S. - Please do not erase the whole text of the email you are > replying to. That makes it quite difficult to follow the thread. > > -- > - > Ron Johnson, Jr. > Jefferson, LA USA > PGP Key ID 8834C06B I prefer encrypted mail. > > Legality/morality of using open wireless points: > "If I leave my door unlocked are you going to come into my house > in the middle of the night because you need to use the restroom? > I pay a fixed rate for water. It's cold water so there is no > electricity usage. No financial loss. I have 2.5 bathrooms, so no > loss of usage on my end. Is this OK? Please, try this and we'll > see if it's OK." > http://www.warchalking.org/comments/2002/9/22/223831/236/135 > > > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > > ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
On Sun, 2005-03-13 at 17:58 -0600, Jim Oltman wrote: > What I meant in that statement is that I got it to recognize the > receiver in the /var/log/messages but it is still not working. Yes, but *how* did you get "it" to recognize the receiver? P.S. - Please do not erase the whole text of the email you are replying to. That makes it quite difficult to follow the thread. -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. Legality/morality of using open wireless points: "If I leave my door unlocked are you going to come into my house in the middle of the night because you need to use the restroom? I pay a fixed rate for water. It's cold water so there is no electricity usage. No financial loss. I have 2.5 bathrooms, so no loss of usage on my end. Is this OK? Please, try this and we'll see if it's OK." http://www.warchalking.org/comments/2002/9/22/223831/236/135 signature.asc Description: This is a digitally signed message part ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
What I meant in that statement is that I got it to recognize the receiver in the /var/log/messages but it is still not working. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
On Sun, 2005-03-13 at 17:32 -0600, Jim Oltman wrote: > OK. I got my box to recognize the IR receiver. Now what? Here is my Well, what did you *do* to get your box to recognize the IR receiver? That's most valuable for the rest of us to know... > /var/log/messages pertaining to lirc: > > Mar 13 17:26:30 mythfrontend kernel: lirc_dev: IR Remote Control > driver registered, at major 61 > Mar 13 17:26:30 mythfrontend kernel: usbcore: registered new driver > lirc_mceusb > Mar 13 17:26:30 mythfrontend kernel: > /var/tmp/bach-build/BUILD/lirc-0.7.0/drivers/lirc_mceusb/lirc_mceusb.c: > USB Microsoft IR Transceiver Driver v0.2 > Mar 13 17:26:33 mythfrontend gdm-autologin(pam_unix)[4734]: session > opened for user mythtv by (uid=0) > Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: accepted new client on > /dev/lircd > Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: could not get file > information for /dev/lirc > Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: default_init(): No > such file or directory > Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: caught signal [snip] -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. "But a much bigger business is selling anti-spam software. This is a billion dollar market, and it is rapidly growing. Any simple and effective solution against spam would defeat revenues and drive several companies into bankrupt, would make consultants jobless. ... Have a single, simple, and permanent solution to the problem and - boom - this billion dollar market is dead. That's one of the reasons why people are expected to live with spam. They have to live with it to make them buy anti-spam software. Content filters are perfect products to keep this market alive." Hadmut Danisch signature.asc Description: This is a digitally signed message part ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
OK. I got my box to recognize the IR receiver. Now what? Here is my
/var/log/messages pertaining to lirc:
Mar 13 17:26:30 mythfrontend kernel: lirc_dev: IR Remote Control
driver registered, at major 61
Mar 13 17:26:30 mythfrontend kernel: usbcore: registered new driver lirc_mceusb
Mar 13 17:26:30 mythfrontend kernel:
/var/tmp/bach-build/BUILD/lirc-0.7.0/drivers/lirc_mceusb/lirc_mceusb.c:
USB Microsoft IR Transceiver Driver v0.2
Mar 13 17:26:33 mythfrontend gdm-autologin(pam_unix)[4734]: session
opened for user mythtv by (uid=0)
Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: accepted new client on
/dev/lircd
Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: could not get file
information for /dev/lirc
Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: default_init(): No
such file or directory
Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: caught signal
On Sun, 13 Mar 2005 17:12:58 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote:
> Can someone tell me what this means in my /var/log/messages?
>
> Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: accepted new client on
> /dev/lircd
> Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: could not get file
> information for /dev/lirc
> Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: default_init(): No
> such file or directory
> Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: caught signal
>
>
> On Sun, 13 Mar 2005 15:37:28 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote:
> > Well it didn't work. When I do a cat /var/log/messages | grep usb I get
> > this:
> >
> > Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver usbfs
> > Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver hub
> > Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver hiddev
> > Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver usbhid
> > Mar 13 15:21:21 mythfrontend kernel: drivers/usb/input/hid-core.c:
> > v2.0:USB HID core driver
> > Mar 13 15:21:21 mythfrontend kernel: usb 3-2: new full speed USB
> > device using ohci_hcd and address 2
> >
> > At one point, I actually got the usb3-2 to attach to a device I made
> > called /dev/ttyUSB0 but nothing after that. Here is my modprobe.conf:
> >
> > alias eth0 sk98lin
> > alias eth1 forcedeth
> > alias snd-card-0 snd-intel8x0
> > options snd-card-0 index=0
> > install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 &&
> > /usr/sbin/alsactl restore >/dev/null 2>&1 || :
> > remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ;
> > }; /sbin/modprobe -r --ignore-remove snd-intel8x0
> > alias usb-controller ehci-hcd
> > alias usb-controller1 ohci-hcd
> > # nvidia kernel module
> > alias char-major-195 nvidia-1_0-6629
> >
> > # LIRC Setup
> > alias char-major-61 lirc_mceusb
> > #Per Jared's instructions
> >
> > #alias char-major-188-0 usbserial
> > #options usbserial vendor=0x0471 product=0x0815
> > #alias ttyUSB0 lirc_mceusb
> > #install lirc_mceusb /sbin/modprobe lirc
> > # /sbin/modprobe --ignore-install lirc_mceusb
> >
> > There has got to be a way to get this working. Any ideas? Can I
> > provide anymore information?
> >
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Can someone tell me what this means in my /var/log/messages?
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: accepted new client on
/dev/lircd
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: could not get file
information for /dev/lirc
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: default_init(): No
such file or directory
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: caught signal
On Sun, 13 Mar 2005 15:37:28 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote:
> Well it didn't work. When I do a cat /var/log/messages | grep usb I get this:
>
> Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver usbfs
> Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver hub
> Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver hiddev
> Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver usbhid
> Mar 13 15:21:21 mythfrontend kernel: drivers/usb/input/hid-core.c:
> v2.0:USB HID core driver
> Mar 13 15:21:21 mythfrontend kernel: usb 3-2: new full speed USB
> device using ohci_hcd and address 2
>
> At one point, I actually got the usb3-2 to attach to a device I made
> called /dev/ttyUSB0 but nothing after that. Here is my modprobe.conf:
>
> alias eth0 sk98lin
> alias eth1 forcedeth
> alias snd-card-0 snd-intel8x0
> options snd-card-0 index=0
> install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 &&
> /usr/sbin/alsactl restore >/dev/null 2>&1 || :
> remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ;
> }; /sbin/modprobe -r --ignore-remove snd-intel8x0
> alias usb-controller ehci-hcd
> alias usb-controller1 ohci-hcd
> # nvidia kernel module
> alias char-major-195 nvidia-1_0-6629
>
> # LIRC Setup
> alias char-major-61 lirc_mceusb
> #Per Jared's instructions
>
> #alias char-major-188-0 usbserial
> #options usbserial vendor=0x0471 product=0x0815
> #alias ttyUSB0 lirc_mceusb
> #install lirc_mceusb /sbin/modprobe lirc
> # /sbin/modprobe --ignore-install lirc_mceusb
>
> There has got to be a way to get this working. Any ideas? Can I
> provide anymore information?
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Well it didn't work. When I do a cat /var/log/messages | grep usb I get this:
Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver usbfs
Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver hub
Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver hiddev
Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver usbhid
Mar 13 15:21:21 mythfrontend kernel: drivers/usb/input/hid-core.c:
v2.0:USB HID core driver
Mar 13 15:21:21 mythfrontend kernel: usb 3-2: new full speed USB
device using ohci_hcd and address 2
At one point, I actually got the usb3-2 to attach to a device I made
called /dev/ttyUSB0 but nothing after that. Here is my modprobe.conf:
alias eth0 sk98lin
alias eth1 forcedeth
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 &&
/usr/sbin/alsactl restore >/dev/null 2>&1 || :
remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ;
}; /sbin/modprobe -r --ignore-remove snd-intel8x0
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
# nvidia kernel module
alias char-major-195 nvidia-1_0-6629
# LIRC Setup
alias char-major-61 lirc_mceusb
#Per Jared's instructions
#alias char-major-188-0 usbserial
#options usbserial vendor=0x0471 product=0x0815
#alias ttyUSB0 lirc_mceusb
#install lirc_mceusb /sbin/modprobe lirc
# /sbin/modprobe --ignore-install lirc_mceusb
There has got to be a way to get this working. Any ideas? Can I
provide anymore information?
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
So you didn't have to mess with any /dev/ttyUSB0 stuff? I am gonna cross my fingers and hope that this will work too. On Sun, 13 Mar 2005 12:00:42 -0800, Jarod Wilson <[EMAIL PROTECTED]> wrote: > On Sunday 13 March 2005 10:48, Jim Oltman wrote: > > Has anyone had any luck getting this IR Receiver to work? I know that > > Jared has, but someone else has GOT to be using it too. > > I believe there were some hardware changes somewhere along the line, and so my > relatively old MCE USB receiver Just Works with lirc, while some newer ones > may not. Only theory I've got anyhow. My relevant modprobe.conf stuff is > simply: > > alias char-major-61 lirc_mceusb > > > > On Sat, 12 Mar 2005 17:21:47 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > [...] > > > # LIRC Setup > > > > > > alias char-major-188-0 usbserial > > > options usbserial vendor=0x0471 product=0x0815 > > > alias lirc0 lirc_mceusb > > > install lirc_mceusb ;\ > > > /sbin/modprobe --ignore-install lirc_mceusb > [...] > > -- > Jarod Wilson > [EMAIL PROTECTED] > > Got a question? Read this first... > http://catb.org/~esr/faqs/smart-questions.html > MythTV, Fedora Core & ATrpms documentation: > http://wilsonet.com/mythtv/ > MythTV Searchable Mailing List Archive > http://www.gossamer-threads.com/lists/mythtv/ > > > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > > ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
On Sunday 13 March 2005 10:48, Jim Oltman wrote: > Has anyone had any luck getting this IR Receiver to work? I know that > Jared has, but someone else has GOT to be using it too. I believe there were some hardware changes somewhere along the line, and so my relatively old MCE USB receiver Just Works with lirc, while some newer ones may not. Only theory I've got anyhow. My relevant modprobe.conf stuff is simply: alias char-major-61 lirc_mceusb > On Sat, 12 Mar 2005 17:21:47 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: [...] > > # LIRC Setup > > > > alias char-major-188-0 usbserial > > options usbserial vendor=0x0471 product=0x0815 > > alias lirc0 lirc_mceusb > > install lirc_mceusb ;\ > > /sbin/modprobe --ignore-install lirc_mceusb [...] -- Jarod Wilson [EMAIL PROTECTED] Got a question? Read this first... http://catb.org/~esr/faqs/smart-questions.html MythTV, Fedora Core & ATrpms documentation: http://wilsonet.com/mythtv/ MythTV Searchable Mailing List Archive http://www.gossamer-threads.com/lists/mythtv/ pgpH9vBf2qsUL.pgp Description: PGP signature ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Re: USB MCE IR Receiver
Has anyone had any luck getting this IR Receiver to work? I know that Jared has, but someone else has GOT to be using it too. On Sat, 12 Mar 2005 17:21:47 -0600, Jim Oltman <[EMAIL PROTECTED]> wrote: > My last post was about this very same thing, but I wasn't specific > enough and I caused a very nice person, Martin, to spend an aweful lot > of time helping me out. Apologies again! Getting down to it. When I > boot with the MCE USB receiver plugged in, cat /var/log/messages | > grep usb gives me this output: > > Mar 12 11:36:41 mythfrontend kernel: usbcore: registered new driver usbfs > Mar 12 11:36:41 mythfrontend kernel: usbcore: registered new driver hub > Mar 12 11:36:44 mythfrontend kernel: usbcore: registered new driver hiddev > Mar 12 11:36:44 mythfrontend kernel: usbcore: registered new driver usbhid > Mar 12 11:36:44 mythfrontend kernel: drivers/usb/input/hid-core.c: > v2.0:USB HID core driver > Mar 12 11:36:45 mythfrontend kernel: usb 3-2: new full speed USB > device using ohci_hcd and address 2 > > I am not sure what settings to put in my modprobe.conf and if I need > to edit lircd in /etc/rc.d/init.d/ or not. Here is the pertinent part > of my modprobe.conf after I followed some directions at > FedoraForum.org > (http://fedoraforum.org/forum/showthread.php?t=27829&highlight=ttyUSB0): > > # LIRC Setup > > alias char-major-188-0 usbserial > options usbserial vendor=0x0471 product=0x0815 > alias lirc0 lirc_mceusb > install lirc_mceusb ;\ > /sbin/modprobe --ignore-install lirc_mceusb > > Can anyone please point me in the right direction? What am I doing > wrong? Here are my system stats: > > Frontend System: > > 2500+ Athlon > 512MB PC2700 RAM > Asus A7N8X-E DLX Mobo > Chaintech FX5200 128MB RAM > DVD+R drive, Floppy drive > MCE USB IR Receiver/Blaster > Using Jarod's Guide > FC3 running vanilla 2.6.10_770 kernel > APT-GET all components (lirc, nvidia drivers, mythtv-suite, etc all > done on 3-11-05) > > Thanks to Jarod for his wonderful guide. Because of him I had a great > Mythbox going for months. And thanks to me for mucking it up!! > ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
