LinHES Forums
http://forum.linhes.org/

MCEUSB2 install under 5A22
http://forum.linhes.org/viewtopic.php?f=2&t=6637		 Page 1 of 2
Author:  fman [ Wed Oct 26, 2005 4:23 pm ]
Post subject:  MCEUSB2 install under 5A22
I've installed R5A22 of Knoppmyth using the following hardware

Neo2-FX
Athlon 64 3000
PVR-150 PAL
Microsoft USB remote (MCEUSB2)

I'm having difficulty getting the remote to work usign the lirc-reconfigure.sh script that is now included with knoppmyth. When I run it I get the following error message

These are some of the more popular remotes. If you don't
see your remote listed, please contact knoppmyth@gmail.com
with details on your remote.

1) adaptec 15) ericsson 29) pinnacle_systems
2) animax 16) hauppauge 30) pixelview
3) asus 17) hercules 31) provideo
4) atiusb 18) imon 32) rca-6n1
5) avermedia 19) iodata 33) remotec
6) avermedia98 20) knc_one 34) sasem
7) bestbuy 21) kworld 35) sigma_designs
8) caraca 22) leadtek 36) silitek
9) chronos 23) leadtek_pvr200 37) streamzap
10) commandir 24) life-view 38) technisat
11) cph03x 25) logitech 39) tekram
12) creative 26) mceusb 40) winfast_rm0010
13) dvico 27) packard_bell 41) x10
14) ea65 28) pcmak 42) Quit
Choose your remote: 26


WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING

I should have been able to auto-detect this remote. If you're
sure it's plugged
in, please send the contents of /var/log/mythtv/lirc-reconfig.log
to knoppmyth@gmail.com.
Otherwise, please be sure to plug the remote in and re-run this
script.

WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING

I can however see that the remote is connected and detected as a USB device.

T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 11 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs= 1
P: Vendor=0471 ProdID=0815 Rev= 0.00
S: Manufacturer=Philips
S: Product=eHome Infrared Transceiver
S: SerialNumber=PH00Fn24
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff
Driver=lirc_mceusb2
E: Ad=01(O) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms


So I'm guessing the script is broken and not detecting this variant of the mceusb controller.

I've manually copied the lircd.conf and lircrc files for mceusb2 to
/etc/lirc/lircd.conf and /home/mythtv/.mythtv/lircrc as required yet this remote still dosn't work under mythtv.

I can use irrecord to program the buttons correctly, so I'm thinking the lirc is infact seeing the remote and reading the codes correctly.

Any help in getting this up and working is appreciated.

re

FP
Author:  leev [ Wed Oct 26, 2005 5:17 pm ]
Post subject:  Similar probelm with 2004 MCE USB remote...
Getting the same problem but with the older 2004 verison of the remote...

I get this in my /var/log/mythtv/lirc-reconfig.log

T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 6 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=045e ProdID=006d Rev= 2.00
S: Manufacturer=Microsoft
S: Product=Microsoft IR Transceiver
S: SerialNumber=MS1EW588
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
/usr/local/bin/lirc-reconfig.sh:
/usr/local/bin/lirc-reconfig.sh: The MCEUSB remote should be in there somewhere.
/usr/local/bin/lirc-reconfig.sh:

Including those 3 lines at the end...

I got the remote working fine in A15/15.5/16 but the auto config didn't work, and despite following my notes, downloading a known good version of LIRC, compiling it, setting it up, etc, it's still not working...

Which is annoying as everything else is running just sweet.
Nice work Cesman and the rest of the devs!
Author:  fman [ Sat Oct 29, 2005 2:50 am ]
Post subject: 
OK - I managed to get this working. I ended up modifying the lirc-reconfig.sh script to recognise the eHome remote and tag this as being mceusb2. Once this was done I then moved the checked the lircd.conf file had been correctly replaced in /etc/ (Testing later showed the lircd is using the conf file in /etc not the one in /etc/lircd/

I then had to copy the .lircrc file from http://blatter.com/mceusb/ as the one in the current knoppmyth is incorrect, it even states this in the shell script. Once this was running I tested the command line operation of lircd by running irw from the command prompt.

Initially I received a "connection refused" message which told me that lircd wasn't running:) Started that with /etc/init.d/lircd start and then irw would start and keypresses on the remote would appear onscreen and correctly reference mceusb.

Fired up mythfrontend and away we went :) All working fine.

FP
Author:  leev [ Sat Oct 29, 2005 3:06 am ]
Post subject:  [Solved] MCEUSB remote now working!
Right then...

I reinstalled R5A22 from scratch, I noticed in the boot messages that lirc was being loaded, so when it came to the remote config script, I just selected quit, and carried on. Once installed I looked through the boot logs, it does in fact look like lirc_mceusb is being loaded (twice in fact, the second load fails), but looking at the config files in -

/etc/lircd.conf
/etc/lirc/lircd.conf
/home/mythtv/.mythtv/lircrc
/home/mythtv/.lircrc

They all appear to be for the Hauppauge PVR350 remote, so I copied the correct config files over -

cp /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb /etc/lircd.conf
cp /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb /etc/lirc/lircd.conf
and
my lircrc file to /home/mythtv/.mythtv/lircrc
and /home/mythtv/.lircrc

Rebooted and it works fine now :)

From this I guess, the installed must be aware of the mceusb remote and installs it, but slightly incorrectly by installing the correct software but the incorrect config files.

Not sure if the remote install script should put up a messages saying that it may have installed the remote already?

Lastly (being a newbie) where do I look to remove the second load of the lirc_mceusb driver?

Lastly, many thanks to Cesman and the dev for another release that rocks!
Author:  fman [ Sat Oct 29, 2005 3:20 am ]
Post subject: 
Good to see we are both having results, I need to mail my script changes to the devs. The newer microsoft remote seems to work really well, and being a HTPC remote has all the right buttons.

F
Author:  leev [ Thu Nov 24, 2005 6:27 am ]
Post subject: 
OK, now the bad news...
While acutally using my 2004 MCE remote, it turns out that while it appears to work, its having problems....
It works for a minute or so, then stops for 15-30secs, then works again for short while, then stops again, then works, you get the picture...

This convinced me (along with the video folder error) to install A26...

Everything under A26 is now working, except for the MCE remote...
Under A26, it now seems to be copying over the correct config files, it doesn't work at all... I copied over my config files but still no dice...

Myth's just not as slick using a wired keyboard somehow :(
Author:  nermander [ Thu Nov 24, 2005 6:44 am ]
Post subject: 
Someone will have to correct me if I'm wrong, but I think that for such remotes (that are controlled by a kernel module) you do no need to reconfigure lirc. (I guess it's the same of it's for example some USB device or for example the Nova-T remote)

Lirc consist of several parts: the driver and the deamon.

The driver part is ONLY needed if you use a receiver on the serial or parallell port.

If the remote is handled by a kernel module (as in this case) you only have to set the deamon up to use the right device and driver.

This is (if I remember correct, I'm not in front of my machine) controlled by /etc/lirc/hardware.conf. Just set the right device and driver in there and restart lirc with /etc/init.d/lirc restart.

The you can test it with irw. If it seems to give the wrong codes, you can always try to run irrecord to set it up.
Author:  leev [ Thu Nov 24, 2005 5:29 pm ]
Post subject: 
My /etc/lirc/hardware.conf looks like this..
------------------------------------------------
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
START_LIRCMD=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="default"
# If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be
# automatically used instead
DEVICE="/dev/usb/hiddev0"
MODULES="lirc_dev lirc_mceusb"
------------------------------------------------------
Which seems OK... lirc_mceusb is the right one...

Doing a ps -ax shows

4671 ? D 0:00 [lirc_dev]

irw when run says
connect: Connection refused

Now if I run -

lircd -n &
and then
irw

all the buttons work fine and show up on the console, but things don't happen in Myth...

So isn't Lirc running? or is Myth not listening?
Author:  nermander [ Fri Nov 25, 2005 1:56 am ]
Post subject: 
Run mythfrontend from an xterm och look for error messages. When it happened to me, it was a typo in /home/mythtv/.lircrc.
Author:  leev [ Fri Nov 25, 2005 2:41 am ]
Post subject: 
Ah! Good call - this looks like the problem...

---------------------------------------------
mythtv: could not connect to socket
mythtv: Connection refused
lirc_init failed for mythtv, see preceding messages
---------------------------------------------

The next question is why?

I can't see any other log output from Lirc in /var/log...

And there's also the issue the it works when I manually start lirc...

Is it just not not starting on boot?
Author:  leev [ Fri Nov 25, 2005 3:47 am ]
Post subject: 
Found this in the daemons.log
----------------------
Nov 23 23:43:02 mythtv lircd-0.7.2pvr150[3275]: accepted new client on /dev/lircd
Nov 23 23:43:02 mythtv lircd-0.7.2pvr150[3275]: could not open /dev/usb/hiddev0
Nov 23 23:43:02 mythtv lircd-0.7.2pvr150[3275]: default_init(): No such device
Nov 23 23:43:02 mythtv lircd-0.7.2pvr150[3275]: caught signal
----------------------

And this in the dmesg
----------------------
ohci_hcd 0000:00:02.1: nVidia Corporation nForce2 USB Controller (#2)
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
usb 1-2: new full speed USB device using ohci_hcd and address 2
ohci_hcd 0000:00:02.1: irq 11, io mem 0xdf004000
lirc_dev: IR Remote Control driver registered, at major 61
lirc_dev: lirc_register_plugin: sample_rate: 80
usbcore: registered new driver lirc_mceusb
/usr/src/lirc-0.7.2pvr150/drivers/lirc_mceusb/lirc_mceusb.c: IR Transceiver Driver v0.2
hub 2-0:1.0: USB hub found
----------------------
Unplugging and replugging gives this in messages
----------------------
Nov 25 09:41:34 mythtv kernel: usb 1-2: USB disconnect, address 3
Nov 25 09:41:34 mythtv kernel: /usr/src/lirc-0.7.2pvr150/drivers/lirc_mceusb/licd
Nov 25 09:41:45 mythtv kernel: ohci_hcd 0000:00:02.0: wakeup
Nov 25 09:41:45 mythtv kernel: usb 1-2: new full speed USB device using ohci_hc$
Nov 25 09:41:45 mythtv kernel: lirc_dev: lirc_register_plugin: sample_rate: 80
Nov 25 09:41:46 mythtv usb.agent[5741]: lirc_mceusb: already loaded
---------------------
Now I'm lost.... :/
Author:  nermander [ Fri Nov 25, 2005 5:28 am ]
Post subject: 
It looks as if the problem could be that USB devices get a more or less "random" id when you connect them.

I don't have enought knowledge on USB to know if you can either make the adress fixed in some way.

There is a similar problem with remotes using dev/input. They get assigned a different number on boot depending on if you have mouse or keayboard connected or not. I always have to boot my machine without mouse and keyboard and then connect them if I need them.

A quick search indicates that "udev rules" might be the solution.
Author:  __alex__ [ Sat Feb 11, 2006 12:16 pm ]
Post subject:  mceusb2 solution
Hello,

First post in this forum.

I've been having the very same problem as most of you with this remote.

The problem:
Feb 11 18:19:02 tv lircd-0.7.2pvr150[2620]: accepted new client on /dev/lircd
Feb 11 18:19:02 tv lircd-0.7.2pvr150[2620]: could not open /dev/usb/hiddev0
Feb 11 18:19:02 tv lircd-0.7.2pvr150[2620]: default_init(): No such device
Feb 11 18:19:02 tv lircd-0.7.2pvr150[2620]: caught signal

But as leev's pointed out (nov 25th 2005 post), this remote works (thanks mate)

Solution:

#receiver
Comment the following line in /etc/lirc/hardware.conf:
DEVICE="/dev/usb/hiddev0"
su -
cd /usr/src/
tar -xjf lirc-0.7.2pvr150.tar.bz2
cp lirc-0.7.2pvr150/remotes/mceusb/lircd.conf.mceusb /etc/lirc/lircd.conf
/etc/init.d/lirc restart

#remote
su - mythtv
cd .mythtv
wget http://blatter.com/mceusb/lircrc_MYTH_EXAMPLE
mv lircrc_MYTH_EXAMPLE lircrc
logout
kill -HUP `pidof gdm`

enjoy

Tested whith a clean R5A30.2 installation

--
Alex
Author:  apr67 [ Sat Feb 11, 2006 7:26 pm ]
Post subject:  Thanks.
I've been trying to make this work for a while with NO LUCK.

A couple of notes for the non-linux aware.
this line:

wget http://blatter.com/mceusb/lircrc_MYTH_EXAMPLE

The underscores on the lircrc_MYTH_EXAMPLE don't showup in my browser.

kill -HUP `pidof gdm`
(Its easier to reboot the mythbox)
Author:  L0o0ky [ Sat Feb 11, 2006 9:01 pm ]
Post subject:  I also have the mceusb remote (working after a litte tweakin
Check out this thread.

http://mysettopbox.tv/phpBB2/viewtopic.php?t=8178

I use the mceusb remote. The suggestions I made there have worked every time for me.

thanks,
Page 1 of 2 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/