headers
Ian Macdonald | 1 Sep 2006 02:02

Re: irrecord/blaster problem

On Thu 31 Aug 2006 at 00:00:30 +0200, I wrote:

> I'm in The Netherlands and trying to set up a MythTV box to work with a
> Thomson DCI-52UPC digital cable set-top box, as used on the UPC cable
> network in Amsterdam.
> 
> I have two instances of lircd running, one which handles the MythTV
> remote-control, a Microsoft MCE unit, plus another for the IR blaster
> that is connected to /dev/ttyS0. The blaster is the red LED model from
> irblaster.info.
> 
> I couldn't find an existing lircd.conf on-line for the DCI-52UPC, so I
> attempted to make one, using irrecord and the USB Microsoft MCE IR
> receiver.

Sorry to follow up on myself, but it's been suggested to me that the
Microsoft MCE reader may not be able to correctly receive any IR codes
other than the ones from its own keyboard and remote control.

Does anyone know if this is true? If so, there's little point in my
trying to use it to construct an lircd.conf for my set-top box's remote.

I would actually be surprised if this is the case, since lirc_mceusb2
module causes the kernel to report the the Microsoft IR unit as a
Philips eHome Infrared Transceiver. If Philips made it, it seems
reasonable to expect it to be able to work with other devices, doesn't
it?

Ian
--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ian Macdonald | 1 Sep 2006 18:44

mod_mce freezes

Hello,

I'm running a MythTV box in combination with a Microsoft MCE
remote-control. Thanks to lirc_mceusb2, this works quite well.

Now, however, I'd like to start using the Microsoft MCE keyboard, too.
To this end, I downloaded and compiled mod_mce.

After removing lirc_mceusb2 from the running kernel, I can successfully
modprobe mod_mce, as evidenced here:

Sep  1 16:36:59 tourbillon kernel: mod_mce: Input driver for Microsoft
MCE 2005 keyboard v0.1.0

Unfortunately, that's about as far as I get, because when I hit ANY key
on either the keyboard or the remote control, the entire system
completely freezes. Nothing is logged and the box is not even pingable.

I should probably mention that I have another keyboard connected via
the PS/2 port, but I can't imagine that has anything to do with it.

Any ideas? I'd love to get this keyboard to run.

Ian
--

-- 
Ian Macdonald               | A day without sunshine is like a day
ian@...             | without orange juice. 
http://www.caliban.org/     | 
                            | 
                            |
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tomas Dubec | 1 Sep 2006 22:18

MCE remote

hi everybody,
i just got my remote, the shop where i bought it names it "Microsoft
remote control x/Rcvr for MCE", so i hoped for support in
usbmce/usbmce2. unfortunately it doesnt work.
here's output from lsusb:

Bus 003 Device 002: ID 1784:0001  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        16
  idVendor           0x1784 
  idProduct          0x0001 
  bcdDevice            0.00
  iManufacturer           1 Topseed
  iProduct                2 eHome Infrared Transceiver
  iSerial                 3 TS00070X
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
(Continue reading)

Permalink | Reply | 9 comments |
headers
Ian Macdonald | 1 Sep 2006 22:59

Re: MCE remote

On Fri 01 Sep 2006 at 22:18:46 +0200, you wrote:

> i just got my remote, the shop where i bought it names it "Microsoft
> remote control x/Rcvr for MCE", so i hoped for support in
> usbmce/usbmce2. unfortunately it doesnt work.
> here's output from lsusb:
> 
> any idea which lirc module should work, or is this remote even
> supported?

It's definitely supported. I'm using it. :-)

lirc_mceusb2 is the module you want. You should see a line like this in
your log when it's inserted:

Sep  1 16:36:58 tourbillon kernel: lirc_mceusb2[4]: Philips eHome Infrared Trans ceiver on usb2:4

Do you see something like that?

Otherwise, check that you have a valid /etc/lircd.conf in place for this
remote control. Do you have ~/.lircrc in place? Is lircd running?

Ian
--

-- 
Ian Macdonald               | Depart in pieces, i.e., split. 
ian@...             | 
http://www.caliban.org/     | 
                            | 
                            |
(Continue reading)

Permalink | Reply | 6 comments |
headers
Tomas Dubec | 1 Sep 2006 23:27

Re: MCE remote

On Fri, 1 Sep 2006 22:59:53 +0200
Ian Macdonald <ian@...> wrote:

> It's definitely supported. I'm using it. :-)
> 
> lirc_mceusb2 is the module you want. You should see a line like this
> in your log when it's inserted:

thanks for reply,
i'm afraid this is not the philips device, as lsusb says "topseed", or
is this the same?
i don't have /etc/lircd.conf because i cant even create one.
when inserted, dmesg says (lirc_mceusb2 already modprobed): 
usb 3-2: new full speed USB device using uhci_hcd and address 3
usb 3-2: configuration #1 chosen from 1 choice

irrecord then fails with:
irrecord: could not init hardware (lircd running ? --> close it, check
permissions)

lircd is not running...

> 
> Sep  1 16:36:58 tourbillon kernel: lirc_mceusb2[4]: Philips eHome
> Infrared Trans ceiver on usb2:4
> 
> Do you see something like that?

no, nothing like that.
are you soure, that according to the lsusb output i sent, this is the
(Continue reading)

Permalink | Reply | 5 comments |
headers
Ian Macdonald | 2 Sep 2006 00:06

Re: MCE remote

On Fri 01 Sep 2006 at 22:18:46 +0200, you wrote:

> i just got my remote, the shop where i bought it names it "Microsoft
> remote control x/Rcvr for MCE", so i hoped for support in
> usbmce/usbmce2. unfortunately it doesnt work.
> here's output from lsusb:
> 
> Bus 003 Device 002: ID 1784:0001  
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               1.10
>   bDeviceClass            0 (Defined at Interface level)
>   bDeviceSubClass         0 
>   bDeviceProtocol         0 
>   bMaxPacketSize0        16
>   idVendor           0x1784 
>   idProduct          0x0001 
>   bcdDevice            0.00
>   iManufacturer           1 Topseed
>   iProduct                2 eHome Infrared Transceiver
>   iSerial                 3 TS00070X
>   bNumConfigurations      1

Hmm, maybe Microsoft source these from various places.

My unit, which is flat, black and has the Microsoft logo on it,
identifies itself thus:

Bus 002 Device 004: ID 0471:0815 Philips
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ian Macdonald | 2 Sep 2006 00:12

Re: MCE remote

On Fri 01 Sep 2006 at 23:27:14 +0200, you wrote:

> i'm afraid this is not the philips device, as lsusb says "topseed", or
> is this the same?

I don't know, but I should have read your lsusb output more closely and
not just gone on what you were told the device was called at purchase
time.

> i don't have /etc/lircd.conf because i cant even create one.

If it's compatible with the Philips device, you won't need to. The lirc
distribution comes with an lircd.conf.mceusb file. Just rename that and
try it out.

> when inserted, dmesg says (lirc_mceusb2 already modprobed): 
> usb 3-2: new full speed USB device using uhci_hcd and address 3
> usb 3-2: configuration #1 chosen from 1 choice

The fact it's trying to use lirc_mceusb2 sounds hopeful. Have you added
anything to /etc/modprobe.conf to make it load lirc_mceusb2 or is it
doing that on its own?

Ian
--

-- 
Ian Macdonald               | Man who arrives at party two hours late
ian@...             | will find he has been beaten to the punch. 
http://www.caliban.org/     | 
                            | 
                            |
(Continue reading)

Permalink | Reply | 4 comments |
headers
Tomas Dubec | 2 Sep 2006 00:13

Re: MCE remote

On Sat, 2 Sep 2006 00:06:41 +0200
Ian Macdonald <ian@...> wrote:

> Hmm, maybe Microsoft source these from various places.
> 
> My unit, which is flat, black and has the Microsoft logo on it,
> identifies itself thus:

yeah, flat, black, but no microsoft logo for me:-/
well, thanks anyway

> 
> Bus 002 Device 004: ID 0471:0815 Philips 
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               1.10
>   bDeviceClass            0 (Defined at Interface level)
>   bDeviceSubClass         0 
>   bDeviceProtocol         0 
>   bMaxPacketSize0        16
>   idVendor           0x0471 Philips
>   idProduct          0x0815 
>   bcdDevice            0.00
>   iManufacturer           1 Philips
>   iProduct                2 eHome Infrared Transceiver
>   iSerial                 3 PH00EK6O
>   bNumConfigurations      1
> 
> So maybe the lirc_mceusb2 won't work for you; I don't know.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tomas Dubec | 2 Sep 2006 00:38

Re: MCE remote

On Sat, 2 Sep 2006 00:12:24 +0200
Ian Macdonald <ian@...> wrote:

> On Fri 01 Sep 2006 at 23:27:14 +0200, you wrote:
> 
> > i'm afraid this is not the philips device, as lsusb says "topseed",
> > or is this the same?
> 
> I don't know, but I should have read your lsusb output more closely
> and not just gone on what you were told the device was called at
> purchase time.
> 
> > i don't have /etc/lircd.conf because i cant even create one.
> 
> If it's compatible with the Philips device, you won't need to. The
> lirc distribution comes with an lircd.conf.mceusb file. Just rename
> that and try it out.

hmm, tried it right now, lircd starts, but is not working..

> 
> > when inserted, dmesg says (lirc_mceusb2 already modprobed): 
> > usb 3-2: new full speed USB device using uhci_hcd and address 3
> > usb 3-2: configuration #1 chosen from 1 choice
> 
> The fact it's trying to use lirc_mceusb2 sounds hopeful. Have you
> added anything to /etc/modprobe.conf to make it load lirc_mceusb2 or
> is it doing that on its own?

no, it's not, i modprobed those manualy before connecting. connection
(Continue reading)

Permalink | Reply | 3 comments |
headers
David Kuder | 2 Sep 2006 08:39
Picon

Re: MCE remote


I'm pretty sure you will have to add the VID/PID values to the 
lirc_mceusb2 module.
Near the top of lirc_mceusb2.c replace this:

-- CODE --
#define VENDOR_PHILIPS          0x0471
#define VENDOR_SMK              0x0609
#define VENDOR_TATUNG           0x1460

static struct usb_device_id usb_remote_table [] = {
         { USB_DEVICE(VENDOR_PHILIPS, 0x0815) },
		/* Philips eHome Infrared Transceiver */
         { USB_DEVICE(VENDOR_SMK, 0x031d) },
		/* SMK/Toshiba G83C0004D410 */
         { USB_DEVICE(VENDOR_TATUNG, 0x9150) },
		/* Tatung eHome Infrared Transceiver */
         { }	/* Terminating entry */
};
-- CODE --

With this:

-- CODE --
#define VENDOR_PHILIPS          0x0471
#define VENDOR_SMK              0x0609
#define VENDOR_TATUNG           0x1460
#define VENDOR_TOPSEED          0x1784

static struct usb_device_id usb_remote_table [] = {
(Continue reading)

Permalink | Reply | 2 comments |

Gmane