OK I decided to make a new PVR with good parts this time and grabbed a P4 with a gig ram and 250 gig hd. I bought a haupauge 150 model 1062 and everthing works except the stupid USB remote.

I loaded up the latest version of knoppmyth and it doesnt work. I looked through some old threads mostly from 2006 and tried a lot of the fixes but no luck.

This is my remote.

http://www.hauppauge.com/images/mce_remote_with_beanbag_large.jpg

Can anyone tell me how to get it to work?

Hi,

Ok, I wil share what we had to do get a friends usb RC6 mce remote to work. Maybe it will help you also.

First, unlug the usb ir receiver and reboot.
Second, while it is rebooting, crack to remotes case and remove the funny logo in the middl;e button. It scares tux....
Third, once you have rebooted, open an xterm and switch to root. You will need to run the /usr/local/bin/lirc-reconfig.sh and scroll down to MCEUSB-new
Fourth, plug in the usb sensor and reboot
Fifth, try out your control, should mostly work. You may need to tweak the .mythtv/lircrc to fix a couple of buttons. The Esc may one of them. You will only have to restart the frontend t activate the changes.

There ways to do away with reboot but this works and is to easy understand. It may be the last time you need to reboot
Mike

I followed these steps and it still doesnt work...

Hi,

Going to have to assume the steps did work and you got the menu choices? If you open an xerm window (alt + x) and enter at $ irw that when you press the buttons you do or don't see information?

If not then repeat the process and select the -old version as the usb receiver is probably one of the easier to setup manually.

Just "don't work" is hard to analyse. Use (ctl + c) to stop irw.

Mike

when I put in irw it says nothing the first time.

If i put it in again its says connection refused.

what would you suggest I do next?

Hi,
That is normal results. irw will only display information as you press remote buttons and if the correct match is made to the receiver driver.

Mike

OK - first I have to tell you that, although I have gotten some USB ir receivers to work, the one pictured would never work for me. I suggest you buy the genuine Microsoft USB receiver (not other versions - like the Dell one). That one is common and many Knoppers (sorry - that just popped up...) use that version.

You can test the one you have - look in your /etc/lirc/hardware.conf for the DEVICE (should be something like DEVICE="/dev/lirc0"). Then stop lirc. From an xterm run "irrecord –d /dev/lirc0 ./test.conf" using whatever your DEVICE is. If irrecord starts then your hardware is at least seen by the software. Follow the instructions and see if it will record some button presses. Report back what happens.

Where do i find a MS genuine receiver? A search on ebay did not turn anything up other than dell receivers.

I have bought all of mine on ebay. For example:

http://cgi.ebay.com/Microsoft-Vista-MCE ... dZViewItem

or Newegg:

http://www.newegg.com/Product/Product.a ... 6880100851

If you search you can find these at lower costs (last one I bought was $16 delivered). Anyway, make sure the receiver has "Microsoft" printed on it. There are several out there that look the same but do not work (or do not work easily).

Did you test the one you have? Are you able to get irrecord to run (don't forget to stop lirc before you test this...)?

Toben
The MCE remote dos not work out of the box from R5A16 to R5F27. Also your hardware may not be supported yet. I need the all four posts below to determine / fix this. If you do not know how to obtain this information post back and I will walk you through.

1. Plug in the usb receiver and run lsmod and post ever line that has "lirc" in it to see if you have the correct modules loaded.

It may look something like this.

lirc_mceusb2 ......... 15748 .... 0
lirc_dev .................. 16132 .... 1 .... lirc_mceusb2
usbcore ................. 125448 .... 7 .... lirc_mceusb2, usbhid, usb_storage, uhci_hcd, ehci_hcd, ohci_hcd

2. Next run and post your USB information to see what hardware you have.

It may look like this.

Bus 003 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 001 Device 003: ID 0471:0815 Philips
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000

3. Next run and post your lirc_mceusb2 module information to see if your hardware is supported.

It may look like this.

> modinfo lirc_mceusb2
filename: /lib/modules/2.6.23-chw-4/misc/lirc_mceusb2.ko
license: GPL
author: Daniel Melander <lirc@rajidae.se>, Martin Blatter <martin_a_blatter@yahoo.com>
description: Philips eHome USB IR Transciever and Microsoft MCE 2005 Remote Control driver for LIRC
alias: usb:v1934p0602d*dc*dsc*dp*ic*isc*ip*
alias: usb:v147ApE017d*dc*dsc*dp*ic*isc*ip*
alias: usb:v147ApE015d*dc*dsc*dp*ic*isc*ip*
alias: usb:v045Ep00A0d*dc*dsc*dp*ic*isc*ip*
alias: usb:v043Ep9803d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1509p9242d*dc*dsc*dp*ic*isc*ip*
alias: usb:v195Dp7002d*dc*dsc*dp*ic*isc*ip*
alias: usb:v179Dp0010d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1784p0008d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1784p0007d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1784p0006d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1784p0001d*dc*dsc*dp*ic*isc*ip*
alias: usb:v03EEp2501d*dc*dsc*dp*ic*isc*ip*
alias: usb:v107Bp3009d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1308pC001d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1460p9150d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0609p0334d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0609p0322d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0609p031Dd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0471p060Cd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0471p0815d*dc*dsc*dp*ic*isc*ip*
depends: usbcore
vermagic: 2.6.23-chw-4 SMP preempt mod_unload 586
parm: debug:Debug enabled or not (bool)

4. Post your /etc/lirc/hardware.conf file.

TVBox

_________________
TVBox
LinHES R8.6.1

TVBox... I realize this is a very old thread to be posting to, but I am having the exact same issue and as there was no reply to your final response from the original poster, I've been left kind hangin' - hoping you can still assist?

My hardware is an AMD Athlon 64 x2 (mobo. manuf. around 2007) on which I have installed KM R5F27. My MCE remote is an RC6 with an SMK/Toshiba receiver - exactly the same as pictured in the link on the OP at the top of this thread http://www.hauppauge.com/images/mce_remote_with_beanbag_large.jpg (The remote and receiver came bundled with a Hauppauge WinTV-PVR USB2 MCE edition).

Hoping it will assist, here are the results:

lsmod [only the lirc results shown]
lirc_mceusb 13152 0
lirc_mceusb2 14980 0
lirc_dev 16772 2 lirc_mceusb,lirc_mceusb2
usbcore 111364 9 lirc_mceusb,usbhid,uhci_hcd,lirc_mceusb2,usb_storage,pvrusb2,ohci_hcd,ehci_hcd

lsusb
Bus 002 Device 002: ID 0609:031d SMK Manufacturing, Inc. [so this is an SMK/Toshiba G83C0004D410 receiver]
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 2040:2900 Hauppauge
Bus 001 Device 004: ID 0bda:0111 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 0000:0000

modinfo lirc_mceusb2
filename: /lib/modules/2.6.18-chw-13/misc/lirc_mceusb2.ko
description: Philips eHome USB IR Transciever and Microsoft MCE 2005 Remote Control driver for LIRC
author: Daniel Melander <lirc@rajidae.se>, Martin Blatter <martin_a_blatter@yahoo.com>
license: GPL
vermagic: 2.6.18-chw-13 SMP preempt mod_unload 586 gcc-4.1
depends: usbcore
alias: usb:v0471p0815d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0609p031Dd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0609p0322d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1460p9150d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1308pC001d*dc*dsc*dp*ic*isc*ip*
alias: usb:v107Bp3009d*dc*dsc*dp*ic*isc*ip*
alias: usb:v03EEp2501d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1784p0001d*dc*dsc*dp*ic*isc*ip*
alias: usb:v179Dp0010d*dc*dsc*dp*ic*isc*ip*
alias: usb:v195Dp7002d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1509p9242d*dc*dsc*dp*ic*isc*ip*
alias: usb:v043Ep9803d*dc*dsc*dp*ic*isc*ip*
parm: debug:Debug enabled or not (bool)

hardware.conf
# /etc/lirc/hardware.conf
#
# 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"

Ralph
10 years ago, you are asking for a lot here. Some days I have trouble putting the correct names on the kids in the family but I will give it a shot. From what I can remember KM R5F27 was problematic when it came to MCE remotes. At that time there where two drivers mceusb and mceusb2 and never shall the two mix. Today (LinHES) both are integrated into one driver. Your SMK/Toshiba G83C0004D410 hardware requires the mceusb2 driver.

The command lsmod is listing the modules that are loading in your system. Below the two posts are compared.
At the end of each module are listed the dependent modules. In the information below the lirc_mceusb2 is feeding information
to the lirc_dev and usbcore modules. The first problem I see is that you have two MCE driver modules loading.
The module (lirc_mceusb) in bold should not be loading.

In the next command lsusb we will find If the usb is recognizing your hardware.
0609:031d SMK Manufacturing, Inc

Using the modinfo command we are looking if your hardware is supported by the lirc_mceusb2 driver.
Everything looks good in this quote.


In the hardware.conf file we are going to look at which modules are told to load.
On the line MODULES="lirc_dev lirc_mceusb" two modules are instructed to load
lirc_dev
lirc_mceusb

My guess is that your problem is here. I would change lirc_mceusb to lirc_mceusb2 and reboot.
Run the command lsmod again to make sure no lirc_mceusb modules are loading.


Now the million dollar question. What is keeping you attached to R27
The hardware that I am running is similar to yours.
AMD Athlon 64 x2 3800
Biostar motherboard with 4 gig of DDR2 memory
2 TB hard drive
Microsoft USB remote receiver model: 1040 (RC6 protocol)
LinHES 8.4

Post your outcome

_________________
TVBox
LinHES R8.6.1

Thanks TVBox - actually "only" 8 years ago, but I don't think your kids have to worry about your memory - seems to still be spot on!
OK, I made the correction to hardware.conf so that it's now:

# /etc/lirc/hardware.conf
#
# 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_mceusb2"

I then confirmed that the result of lsmod had changed, now:
lirc_mceusb2 14980 0
lirc_dev 16772 1 lirc_mceusb2
usbcore 111364 8 usbhid,uhci_hcd,lirc_mceusb2,usb_storage,pvrusb2,ehci_hcd,ohci_hcd

Result of lsusb remained unchanged apart from some different Bus/Device numbering, but I assume that's not an issue?

The results of modinfo lirc_mceusb2 still contains:
alias: usb:v0609p031Dd*dc*dsc*dp*ic*isc*ip*

So on the face of it, all looking good - but - still no response from the remote.

I then went back and re-tried mjl's original instructions in the second post of this thread, but no matter whether I set up lirc-reconfig to be MCEUSB-new or MCEUSB-old it made no difference. I did notice that if I attempt lirc-reconfig with the USB receiver plugged in, there is no menu, it just automatically sets it up as AMCEUSB-new:
┌LIRC Configuration
│ Setting up
│ AMCEUSB-new
│ remote...

In most cases, running irw just returns "connect: Connection refused" even on the first attempt. A couple of times I got lucky (I think when setup as AMCEUSB-new, but not sure) and irw did run, but returned no information when I pressed any of the remote's buttons.

So we're getting there, but not quite there yet...

With regard to your million dollar question... I actually started an upgrade path a year ago (yeah, the wheels turn slowly...) and this is covered in another post, http://forum.linhes.org/viewtopic.php?f=22&t=24181 - but to precis, my daily driver is actually still running R5A30.2 on a Pentium 4! I had some issues with the database which prevented me from upgrading past that version until, with the help of others in that post, I sorted the database issue out.

It seemed to me from other posts that it would be easiest to upgrade from R5F27 (probably first to 5.5, but maybe straight to LinHES) than to attempt an upgrade directly from R5A30.2 - especially with my old P4 hardware.

Nothing is as easy as it first sounds of course, and after having upgraded to R5F, I had a video driver issue with the old hardware, and R5F27 kept crashing on it.

So I've now just acquired this "new" Athlon 64x2 4400+ box whose mobo has nVidia GeForce 6150SE integrated graphics, which I think should work fine with Knopp. If not, I should be able to pickup a better nVidia card fairly cheaply.

So my goal at the moment is first to get a bare R5F27 installed on the new box and confirm that everything runs smoothly - then the plan is to import my (extensive) database onto it, via a quick series of database upgrades from R5A to R5F (using VMs). Once R5F seems to be running smoothly, then I would go the next step to R5.5/LinHES.

The immediate challenge is getting the USB remote working (my old/current/working R5A daily driver uses serial port IR, not USB). Whilst eventually I'll want to get my current custom remote control working, I figured the quickest way for the time being would just be to get the MCE one going instead. (Hopefully I'll be able to use the MCE's SMK receiver to talk to a non-MCE remote by fiddling with lirc configuration? If not, I'll be happy enough just to stick with a working MCE remote.)

After sorting this one out, the next challenge will be getting a second instance of lirc running, so that Myth can change channels on my cable box. This works fine on my old serial port box, but I have no idea how to do it on the new box...

Ralph
This has to be setup manualy. The files that the /usr/local/bin/lirc-reconfig.sh script used where incorrect.
There are three files that need to be corrected and placed in the following locations.
etc/lirc/hardware.conf
/etc/lirc/lircd.conf
/home/mythtv/.mythtv/lircrc


I assume you mean MCEUSB-new.
It should setup automatically. It uses your Device ID 0609:031d SMK Manufacturing, Inc
and matches it to your alias: usb:v0609p031D in the correct device driver.

So plug in the receiver, reboot and run lirc-reconfig.sh script once and never again.
You will just be writing bad information over-top of things we just fixed.
Now recheck your hardware.conf file to see if it was changed. There are multiples of this file.
It must be the one in this location /etc/lirc/hardware.conf

Download the attached files and move to the locations below.
Overwrite the original file. If you want the old file back run lirc-reconfig.sh script which will overwrite with crap.
Make sure to check permissions.
/home/mythtv/.mythtv/lircrc
/etc/lirc/lircd.conf

Now back to the million dollar question.
What is so valuable that you would loose if you started over?
Is it the data base?
Old recordings?
New recordings?

_________________
TVBox
LinHES R8.6.1

Actually no - it was definitely 'recognising' it as:
┌LIRC Configuration
│ Setting up
│ AMCEUSB-new
│ remote...
Is that significant though?
Thanks for the files! OK so this is what I did...

* Re-ran lirc-reconfig
* Confirmed that /etc/lirc/hardware.conf had updated itself - it had, but nothing had changed, so the important last line was still MODULES="lirc_dev lirc_mceusb2"
* Overwrote /home/mythtv/.mythtv/lircrc & /etc/lirc/lircd.conf with the ones you supplied
* Ensured that the permissions weren't changed from lirc-reconfig's bodgy versions (permissions for lircrc were mythtv:mythtv, and for lircrd.conf were root:root)
* Rebooted
* Confirmed again that /etc/lirc/hardware.conf still contained MODULES="lirc_dev lirc_mceusb2", and that lircrc and lircd.conf were the files you supplied

But still no response from the remote, and irw returns "connect: Connection refused" (EDIT: I discovered that restarting lirc fixes that - but still no response from irw when remote buttons pressed)
Redid all a few times, even tried different USB port - did I follow your instructions correctly?

What's valuable is of course subjective... 3000 recordings (4.25TB), but also the database of what's been previously recorded, so that I don't end up re-recording eps that have been recorded previously. (Although I found that was also an issue in my initial upgrade to R5F27 on my old hardware, some previously recorded shows did get recorded again anyway due to their programid being slightly different - it started with 'SH' instead of 'EP' even though the numerals following were identical. I never got around to looking further into that at the time, that was a year ago...)