View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 18 posts ] 
Go to page 1, 2  Next

Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Tue Dec 01, 2009 7:32 pm 
Offline
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location: Virginia, USA
I have a MCE USB remote that I had working under 5.5. I believe I got it to work under 5.5 by using the mceusb2 module.

It's now not working under R6.

lsmod | grep -i mce shows that lirc_mod_mce is running

lsusb shows "Bus 004 Device 003: ID 0471:060c Philips"

Not sure what else to do. I did find this on flyspray about MCEUSB

http://linhes.org/flyspray/index.php?do ... ask_id=366

and tried installing the CVS version of lirc listed there, and restarted lircd, but no luck.

Thanks for any assistance.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Jan 04, 2010 9:05 pm 
Offline
Joined: Fri Nov 04, 2005 7:11 am
Posts: 61
Somehow I suspect that the fix for the MCE keyboards has broken our MCE blaster by loading the wrong kernel module. I can see that my blaster transmits something but my cable box doesn't respond anymore. My remote control functions work fine btw.

Here are the modules that load when I plug in the remote control transceiver on R6:

lirc_mod_mce 16772 0
lirc_dev 13492 1 lirc_mod_mce
usbcore 136848 6 lirc_mod_mce,usbhid,uhci_hcd,ehci_hcd

Here is my lsusb on R6:
Bus 004 Device 005: ID 0471:0815 Philips eHome Infrared Receiver

For reference purposes only, here are the modules that are present on my mythbuntu machine where the remote and transmitter both work:
lirc_mceusb 15232 1
lirc_dev 10804 3 lirc_mceusb

lsusb on mythbuntu
Bus 002 Device 002: ID 0471:0815 Philips eHome Infrared Receiver

I looked at the bug report that you mentioned but I don't really understand what it means.

I tried removing the lirc_mod_mce, modprobing lirc_mceusb and restarting lircd which got me the dreaded "hardware doesn't support sending" error

Does anybody have any good ideas where to start?

_________________
BE: R8.4, HVR2250, MCE media center remote, GigaByte GA-EP43-UD3L, 2gb ram

FE: Linhes 8.4, Mythbuntu, Linux Mint DE


Top
 Profile  
 
 Post subject:
PostPosted: Mon Jan 04, 2010 9:14 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
Are you running the latest lirc package from core-testing? the lirc_mod_mce module (which allows the keyboard to work as well as the remote) was fixed to allow the blaster to set the transmit carrier freq. It is discussed here:
http://knoppmyth.net/phpBB2/viewtopic.p ... 9&start=15
Without the fix, using the blaster with the lirc_mod_mce module resulted in a 66 kHz carrier which a lot of equipment wont recognise.
The fix was commited on 22 Nov 2009 and is in pkgrel 17.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jan 05, 2010 8:10 am 
Offline
Joined: Fri Nov 04, 2005 7:11 am
Posts: 61
Greg,

Thanks for the reply. That would definitely explain the behavior I'm seeing. I have 2 remaining questions.

1. If I change to core-testing for lirc, will that change me for everything, or is there a way to only upgrade lirc?

2. Did you have to change lircd.conf to set the carrier frequency or is it already set but being ignored?

_________________
BE: R8.4, HVR2250, MCE media center remote, GigaByte GA-EP43-UD3L, 2gb ram

FE: Linhes 8.4, Mythbuntu, Linux Mint DE


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jan 05, 2010 2:51 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
Im not sure about 1. May depend on whether there has been a kernel update in the testing repo. What I would do if all you want is the lirc change is:
Change pacman.conf to point to testing.
pacman -Sy lirc
Look at what it says it will upgrade and decide.
If that doesnt work, you can download the PKGBUILD and source files from here: http://linhes.org/cgit/cgit.cgi/LinHES- ... sting/lirc
and build the package on your system (with your kernel).

2. The carrier freq should already be in the lircd.conf for the device you are blasting. It was for me. I didnt need to add it.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jan 05, 2010 8:32 pm 
Offline
Joined: Fri Nov 04, 2005 7:11 am
Posts: 61
Thanks Greg

Everything worked fine. My frequency was 56000 btw.

_________________
BE: R8.4, HVR2250, MCE media center remote, GigaByte GA-EP43-UD3L, 2gb ram

FE: Linhes 8.4, Mythbuntu, Linux Mint DE


Top
 Profile  
 
 Post subject:
PostPosted: Sat Jan 23, 2010 5:45 pm 
Offline
Joined: Sun Sep 25, 2005 3:50 pm
Posts: 1013
Location: Los Angeles
I just picked up an AVS Gear GP-IR02BK based on reccomendations in the reviews on newegg.com. When I plug it into the box dmesg reveals:

Code:
usb 4-4: new full speed USB device using ohci_hcd and address 3
usb 4-4: config 1 interface 0 altsetting 0 endpoint 0x1 has an invalid bInterval 0, changing to 32
usb 4-4: config 1 interface 0 altsetting 0 endpoint 0x82 has an invalid bInterval 0, changing to 32
usb 4-4: configuration #1 chosen from 1 choice

lirc_mod_mce: Input driver for Microsoft MCE 2005 keyboard v0.1.5
lirc_mod_mce: Florian Demski
usb 4-4: reset full speed USB device using ohci_hcd and address 3
lirc_dev: lirc_register_plugin: sample_rate: 0
input: Topseed Technology Corp. eHome Infrared Transceiver as /class/input/input5
lirc_mod_mce[3]: Topseed Technology Corp. eHome Infrared Transceiver on usb4:3
usbcore: registered new interface driver lirc_mod_mce


lsusb shows:
Code:
Bus 004 Device 003: ID 1784:0008 TopSeed Technology Corp.


However I cannot get irw to work (because I don't have a lircd.conf for this device) and irrecord starts to work but I end up with this error:
Code:
No toggle bit mask found.
But I know for sure that RC6 has a toggle bit!
The newegg reviews state this thing uses the mceusb2 driver but that does not look like an option in LinHES.
Code:
FATAL: Module lirc_mceusb2 not found.
I can see the lirc_mceusb2 module is called lirc_mceusb2.ko.not in the /lib tree. Any advice on how to proceed?

_________________
Mike
My Hardware Profile


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jan 27, 2010 4:11 am 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
You could rename the module back to .ko and manually install it in preference to lirc_mod_mce just to see whether that works. You could also google for lircd.conf that goes with your remote.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jan 27, 2010 2:51 pm 
Offline
Joined: Sun Sep 25, 2005 3:50 pm
Posts: 1013
Location: Los Angeles
Greg Frost wrote:
You could rename the module back to .ko and manually install it in preference to lirc_mod_mce just to see whether that works. You could also google for lircd.conf that goes with your remote.


Ok, for anyone looking for a lircd.conf for a GP-IR02BK remote, I found one here. I have not tested it yet, but it looks promising.

As far as simply renaming the lirc_mceusb2.ko.not to lirc_mceusb2.ko, I got the same FATAL message when I tried to modprobe.

Code:
[mythtv@zotac ~]$ sudo mv /lib/modules/2.6.28-LinHES/kernel/drivers/misc/lirc_mceusb2.ko.not /lib/modules/2.6.28-LinHES/kernel/drivers/misc/lirc_mceusb2.ko
[mythtv@zotac ~]$ sudo modprobe lirc_mceusb2
FATAL: Module lirc_mceusb2 not found.
[mythtv@zotac ~]$ sudo sv restart lircd
ok: run: lircd: (pid 4746) 0s
[mythtv@zotac ~]$ sudo modprobe lirc_mceusb2
FATAL: Module lirc_mceusb2 not found.


Interestingly, starting with LIRC v0.8.6 the lirc_mceusb and lirc_mceusb2 are merged into a driver called lirc_mceusb. LinHES is currently using LIRC v0.8.5-CVS-pvr150, so it looks like I still need the lirc_mceusb2.

_________________
Mike
My Hardware Profile


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jan 27, 2010 5:19 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
The lirc_mod_mce module is *supposed* to take the place of lirc_mceusb2 as well as adding support for the MCE keyboard which uses the same IR receiver.

If the lircd.conf that you found doesnt work, you could try crafting one yourself by examining what you see when you do something like:
cat /dev/usb/hiddev0 | xxd -c 1

If you want a hand interpreting what that gives, let me know.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Jan 29, 2010 8:38 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
Please ignore the usb/hiddev0 stuff. I was getting confused with the way my dvico remote works.

You should have the lirc_mod_mce module loaded:
Code:
[gfrost@devnew ~]$ lsusb | grep Phil
Bus 005 Device 002: ID 0471:0815 Philips eHome Infrared Receiver


You need to stop lircd:
Code:
[root@devnew gfrost]# sv stop lircd
ok: down: lircd: 0s, normally up


Then with this command, examine the output of /dev/lirc0 when tapping the 1 button. I get something like this:
Code:
[root@devnew gfrost]# cat /dev/lirc0 | xxd -c 4
0000000: ffff ff00  ....
0000004: be0a 0001  ....
0000008: 2003 0000   ...
000000c: 2602 0001  &...
0000010: 5e01 0000  ^...
0000014: f401 0001  ....
0000018: 5e01 0000  ^...
000001c: 2602 0001  &...
0000020: 2003 0000   ...
0000024: f401 0001  ....
0000028: 2003 0000   ...
000002c: 7805 0001  x...
0000030: 5203 0000  R...
0000034: f401 0001  ....
0000038: 5e01 0000  ^...
000003c: 2602 0001  &...
0000040: 5e01 0000  ^...
0000044: f401 0001  ....
0000048: 9001 0000  ....
000004c: f401 0001  ....
0000050: 9001 0000  ....
0000054: f401 0001  ....
0000058: 9001 0000  ....
000005c: f401 0001  ....
0000060: 9001 0000  ....
0000064: c201 0001  ....
0000068: 9001 0000  ....
000006c: f401 0001  ....
0000070: 9001 0000  ....
0000074: f401 0001  ....
0000078: 9001 0000  ....
000007c: f401 0001  ....
0000080: 9001 0000  ....
0000084: 8403 0001  ....
0000088: 9001 0000  ....
000008c: f401 0001  ....
0000090: 9001 0000  ....
0000094: f401 0001  ....
0000098: 9001 0000  ....
000009c: c201 0001  ....
00000a0: 9001 0000  ....
00000a4: f401 0001  ....
00000a8: 5203 0000  R...
00000ac: f401 0001  ....
00000b0: 9001 0000  ....
00000b4: c201 0001  ....
00000b8: c201 0000  ....
00000bc: c201 0001  ....
00000c0: 9001 0000  ....
00000c4: b603 0001  ....
00000c8: 5203 0000  R...
00000cc: f401 0001  ....
00000d0: 9001 0000  ....
00000d4: c201 0001  ....
00000d8: 9001 0000  ....
00000dc: f401 0001  ....
00000e0: 9001 0000  ....
00000e4: f401 0001  ....
00000e8: 9001 0000  ....
00000ec: f401 0001  ....
00000f0: 9001 0000  ....
00000f4: f401 0001  ....
00000f8: 9001 0000  ....
00000fc: c201 0001  ....
0000100: c201 0000  ....
0000104: c201 0001  ....
0000108: 9001 0000  ....
000010c: b603 0001  ....
0000110: a086 0100  ....


Top
 Profile  
 
 Post subject:
PostPosted: Fri Jan 29, 2010 9:26 pm 
Offline
Joined: Mon Dec 24, 2007 9:47 am
Posts: 535
Location: Ottawa, Canada
Greg,
it may be easier for him to instead run:
Code:
mode2 --device=/dev/lirc0

so he can see the exact codes coming from the driver.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Jan 29, 2010 10:36 pm 
Offline
Joined: Sun Sep 25, 2005 3:50 pm
Posts: 1013
Location: Los Angeles
The number one:
Code:
[mythtv@zotac ~]$ sudo cat /dev/lirc1 | xxd -c 4
0000000: ffff ff00  ....
0000004: be0a 0001  ....
0000008: 2003 0000   ...
000000c: 2602 0001  &...
0000010: 5e01 0000  ^...
0000014: 2602 0001  &...
0000018: 5e01 0000  ^...
000001c: f401 0001  ....
0000020: 5203 0000  R...
0000024: f401 0001  ....
0000028: 2003 0000   ...
000002c: 7805 0001  x...
0000030: 5203 0000  R...
0000034: c201 0001  ....
0000038: c201 0000  ....
000003c: c201 0001  ....
0000040: c201 0000  ....
0000044: c201 0001  ....
0000048: c201 0000  ....
000004c: 8403 0001  ....
0000050: c201 0000  ....
0000054: c201 0001  ....
0000058: 9001 0000  ....
000005c: f401 0001  ....
0000060: c201 0000  ....
0000064: c201 0001  ....
0000068: 9001 0000  ....
000006c: 8403 0001  ....
0000070: c201 0000  ....
0000074: c201 0001  ....
0000078: c201 0000  ....
000007c: c201 0001  ....
0000080: c201 0000  ....
0000084: c201 0001  ....
0000088: 5203 0000  R...
000008c: c201 0001  ....
0000090: c201 0000  ....
0000094: c201 0001  ....
0000098: c201 0000  ....
000009c: c201 0001  ....
00000a0: c201 0000  ....
00000a4: 9001 0001  ....
00000a8: c201 0000  ....
00000ac: 8403 0001  ....


Also the number one:
Code:
[mythtv@zotac ~]$ sudo mode2 --device=/dev/lirc1
space 16777215
pulse 2700
space 850
pulse 500
space 400
pulse 450
space 400
pulse 500
space 850
pulse 500
space 850
pulse 1350
space 850
pulse 500
space 400
pulse 500
space 400
pulse 500
space 800
pulse 500
space 400
pulse 1400
space 400
pulse 900
space 850
pulse 1300
space 1350
pulse 400
space 500
pulse 850
space 450
pulse 850
space 70150
pulse 2700
space 900
pulse 450
space 450
pulse 400
space 450
pulse 450
space 900
pulse 450
space 900
pulse 1750


Code:
$ lsusb
Bus 003 Device 002: ID 1784:0008 TopSeed Technology Corp.

_________________
Mike
My Hardware Profile


Top
 Profile  
 
 Post subject:
PostPosted: Sat Jan 30, 2010 2:20 pm 
Offline
Joined: Mon Dec 24, 2007 9:47 am
Posts: 535
Location: Ottawa, Canada
mihanson wrote:
Interestingly, starting with LIRC v0.8.6 the lirc_mceusb and lirc_mceusb2 are merged into a driver called lirc_mceusb. LinHES is currently using LIRC v0.8.5-CVS-pvr150, so it looks like I still need the lirc_mceusb2.

Yes. that is my understanding. I have a how-to that shows you how to update to lirc-0.8.6 if you wish to try that.
see: http://knoppmyth.net/phpBB2/viewtopic.php?t=20749

As for the codes. Just so you know what is going on... When you press a button on the remote, mode2 will spit out the raw code from the mceusb driver.

lirc takes this raw code and maps it to labels using lircd.conf. It takes input in your case from lirc1 and outputs to lircd.

These labels then match your lircrc file which translates the labels to mythtv (and other program) commands.

The codes you identify with mode2 look really low level (ie. raw). Normally the driver will take this and generate a single code. Perhaps you don't have a driver in place?

I haven't tried the following but you can also specify a specific driver using "--driver=" as in:
Code:
mode2 --device=/dev/lirc1 --driver=lirc_mceusb2

Given your other issues this may fail.

If it all fails then my suggestion is to move forward to lirc-0.8.6 per my how-to and start from there. I can see in the 0.8.6 code that mceusb knows your device (based on your lsusb).


Top
 Profile  
 
 Post subject:
PostPosted: Sat Jan 30, 2010 6:01 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
mihanson: what is the command line for lircd? Where is what I have:
Code:
[gfrost@mythtv ~]$ ps xaww | grep lircd
 4304 ?        Ss     0:00 runsv lircd
25771 ?        S      0:09 /usr/sbin/lircd -r -n -d /dev/lirc0 --output /dev/lircd
30357 pts/0    S+     0:00 grep lircd
Notice that it explicitly specifies lirc0 whereas I see that for you to get mode2 to work, you had to tell it to use lirc1. Could that be your problem?
I doubt that upgrading lirc is going to help you because it looks like mode2 is detecting your remote signal properly. Do you have other lirc modules loaded that cause the mce to be on lirc1 instead of lirc0?
Code:
[gfrost@mythtv ~]$ lsmod | grep lirc
lirc_mod_mce           17156  1
lirc_dev               13492  1 lirc_mod_mce
usbcore               136848  4 lirc_mod_mce,ohci_hcd,ehci_hcd

Thanks for the mode2 tip christ. For the record this is what I get from the 1 button:
Code:
[root@devnew ~]# mode2 -d /dev/lirc0
space 16777215
pulse 0
space 350
pulse 550
space 800
pulse 500
space 800
pulse 1400
space 800
pulse 550
space 350
pulse 500
space 400
pulse 500
space 400
pulse 500
space 400
pulse 500
space 350
pulse 550
space 350
pulse 500
space 400
pulse 500
space 400
pulse 500
space 400
pulse 500
space 400
pulse 900
space 400
pulse 500
space 400
pulse 500
space 350
pulse 500
space 850
pulse 500
space 400
pulse 500
space 400
pulse 450
space 400
pulse 500
space 400
pulse 950
space 850
pulse 500
space 400
pulse 450
space 400
pulse 500
space 400
pulse 500
space 400
pulse 500
space 400
pulse 500
space 400
pulse 450
space 450
pulse 450
space 400
pulse 950
space 100000


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 18 posts ] 
Go to page 1, 2  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: Bing [Bot] and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu