[mythtv-users] Re: USB MCE IR Receiver

Axel Thimm Axel.Thimm at ATrpms.net
Tue Mar 15 19:00:09 UTC 2005


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 <huffner at yahoo.com> 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
> > > <cnliberal at gmail.com> 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 <huffner at yahoo.com> 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 at mythtv.org
> > >
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > >
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> > 
> > 
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > 
> > 
> >

> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mythtv.org/pipermail/mythtv-users/attachments/20050315/72db9c5d/attachment-0001.pgp


More information about the mythtv-users mailing list