Re: Cannot get lirc_mceusb2 to do anything
|
From: Jarod Wilson <jarod@wi...> - 2008-09-11 01:41:08
|
On Wed, 2008-09-10 at 16:11 -0600, alhaz@... wrote: > Quoting pigdog <pigdog@...>: > > > Oops: 0000 [#1] SMP > > I'm gonna go out on a limb and suggest that this is the single most > salient portion of the dmesg output. Yeah, looks like the module went boom upon trying to load, so it not working isn't exactly a surprise. Probably need some newer lirc bits to work on 2.6.27, dunno where Mandr*'s lirc bits come from exactly. Fwiw, the lirc patches we're working on for upstream kernel submission work perfectly fine on 2.6.27 (I tested lirc_mceusb2 just a day or two ago on 2.6.27-rc5-git9). Not sure if there's still something that needs to go into lirc cvs to fix things on 2.6.27, I've not yet started re-syncing bits backwards from the git tree... -- Jarod Wilson jarod@... |
Thread view
|
From: pigdog <pigdog@no...> - 2008-09-10 21:53:40
|
I have a philips MCE remote on a Mandriva Cooker system here are my
details:
Lsusb gives the following info that shows the remote is seen
lsusb:
[root@... drivers]# lsusb
Bus 002 Device 001: ID 1d6b:0002
Bus 006 Device 002: ID 0471:0608 Philips
Bus 006 Device 001: ID 1d6b:0001
Bus 007 Device 001: ID 1d6b:0001
Bus 005 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 001 Device 001: ID 1d6b:0002
Dmesg shows me this:
lirc_dev: IR Remote Control driver registered, major 61
lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005
Remote Control driver for LIRC $Revision: 1.44 $
lirc_mceusb2: Daniel Melander <lirc@...>, Martin Blatter
<martin_a_blatter@...>
usb 6-1: reset full speed USB device using uhci_hcd and address 2
lirc_dev: lirc_register_plugin: sample_rate: 0
BUG: unable to handle kernel NULL pointer dereference at 00000000
IP: [<c023d96a>] vsnprintf+0x3a/0x7b0
*pde = 00000000
Oops: 0000 [#1] SMP
Modules linked in: lirc_mceusb2(+) lirc_dev nfsd auth_rpcgss
nls_iso8859_1 cifs exportfs nfs lockd nfs_acl sunrpc af_packet nvidia(P)
fuse tun ipv6 snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq
snd_pcm_oss coretemp snd_mixer_oss iptable_filter iptable_mangle
iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack ip_tables x_tables
binfmt_misc loop nls_utf8 ntfs dm_mod cpufreq_ondemand
cpufreq_conservative cpufreq_powersave acpi_cpufreq freq_table
snd_emu10k1 snd_rawmidi snd_ac97_codec ac97_bus ppdev snd_pcm
snd_seq_device snd_timer snd_page_alloc snd_util_mem snd_hwdep snd
soundcore thermal ohci1394 ieee1394 button i2c_i801 emu10k1_gp processor
e1000e intel_agp i2c_core gameport agpgart parport_pc parport heci
sr_mod iTCO_wdt iTCO_vendor_support evdev rtc_cmos sg usb_storage
pata_marvell ata_piix ahci libata dock sd_mod scsi_mod crc_t10dif ext3
jbd uhci_hcd ohci_hcd ehci_hcd usbcore [last unloaded: nf_conntrack]
Pid: 3889, comm: modprobe Tainted: P
(2.6.27-desktop586-0.rc5.7.1mnb #1)
EIP: 0060:[<c023d96a>] EFLAGS: 00010292 CPU: 0
EIP is at vsnprintf+0x3a/0x7b0
EAX: f47d3eb0 EBX: 00000000 ECX: 00000000 EDX: 00000014
ESI: fffffff4 EDI: f6e77ac0 EBP: d3267c58 ESP: d3267b34
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modprobe (pid: 3889, ti=d3266000 task=ef908000 task.ti=d3266000)
Stack: f6fa6f60 d3267b48 d3267b50 00000082 f6fa6f60 00000001 c1ffdb00
00000014
f47d3e9c 00000000 00000001 f47d3eb0 00000001 00000082 f7363f18
c0483eb8
00000000 d3267b80 c012af6b d3267b94 c01460fb 00000000 f7363f18
c0483eb8
Call Trace:
[<c012af6b>] ? default_wake_function+0xb/0x10
[<c01460fb>] ? autoremove_wake_function+0x1b/0x50
[<c01230a0>] ? __wake_up_common+0x40/0x70
[<c0123d50>] ? __wake_up+0x40/0x50
[<c0131566>] ? wake_up_klogd+0x36/0x40
[<c0131729>] ? release_console_sem+0x1b9/0x1d0
[<c02af2f3>] ? device_create_vargs+0xa3/0xc0
[<c02af338>] ? device_create+0x28/0x30
[<f8f67f99>] ? lirc_register_plugin+0x1e9/0x4e0 [lirc_dev]
[<f8f619b4>] ? usb_remote_probe+0x384/0x7d0 [lirc_mceusb2]
[<c023d87b>] ? string+0x2b/0xe0
[<c01eb506>] ? sysfs_addrm_finish+0x16/0x200
[<c01eacd3>] ? sysfs_add_one+0x13/0x50
[<c01ead61>] ? sysfs_addrm_start+0x51/0x90
[<c0382b3b>] ? mutex_lock+0xb/0x20
[<f885fee4>] ? usb_autopm_do_device+0x64/0xf0 [usbcore]
[<f886054f>] ? usb_probe_interface+0x9f/0x130 [usbcore]
[<c01ebc72>] ? sysfs_create_link+0x12/0x20
[<c02b0fb2>] ? driver_probe_device+0x82/0x1a0
[<c02b1141>] ? __driver_attach+0x71/0x80
[<c02b08c3>] ? bus_for_each_dev+0x53/0x80
[<c02b0e49>] ? driver_attach+0x19/0x20
[<c02b10d0>] ? __driver_attach+0x0/0x80
[<c02b025f>] ? bus_add_driver+0x1af/0x230
[<c02b12e9>] ? driver_register+0x69/0x140
[<f886081c>] ? usb_register_driver+0x7c/0x100 [usbcore]
[<f8b41000>] ? usb_remote_init+0x0/0x82 [lirc_mceusb2]
[<f8b41053>] ? usb_remote_init+0x53/0x82 [lirc_mceusb2]
[<c01012f6>] ? do_one_initcall+0x26/0x170
[<c01595f6>] ? sys_init_module+0x96/0x1c0
[<c019df0d>] ? sys_read+0x3d/0x70
[<c0103e5b>] ? sysenter_do_call+0x12/0x2f
[<c0380000>] ? generic_processor_info+0xad/0x18c
=======================
Code: d2 89 85 fc fe ff ff 89 95 f8 fe ff ff 0f 88 5e 07 00 00 8b 85 fc
fe ff ff 03 85 f8 fe ff ff 89 85 08 ff ff ff 0f 82 2e 03 00 00 <0f> b6
0b 8b b5 fc fe ff ff 84 c9 74 36 31 ff 80 f9 25 89 b5 04
EIP: [<c023d96a>] vsnprintf+0x3a/0x7b0 SS:ESP 0068:d3267b34
---[ end trace c2f82e9e2b757a0d ]---
So I believe the correct module has been loaded
I have modified my /etc/sysconfig/lircd file to look like this:
# Customized setings for lirc daemon
# The hardware driver to use, run lircd --driver=? for a list
DRIVER=default
# Hardware driver module to load
HWMOD=lirc_dev,lirc_mceusb2 (--> I have also tried each module 1 at a
time with the same results <--)
# The device node that communicates with the IR device.
# if you are using lirc_serial, set DEVICE to /dev/ttyS[0-9]
# where 0-9 is the serial port your IR receiver is plugged
# with devfs enabled
DEVICE=/dev/lircd/0
---snip---
When I run /etc/inid.d/lircd start it says OK and creates a file
/dev/lircd
I chmod this file to 666
However when I run irw nothing happens when I press any buttons on the
remote, this seems indicate an incorrect module is being used and mode2
gives
Me the following:
mode2: error opening /dev/lirc
mode2: No such file or directory
I cannot see the /dev/lirc file (but have a /dev/lircd file)
What am I missing to get this working
Any help is appreciated
Thanks in advance
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3432 (20080910) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
|
|
From: <alhaz@xm...> - 2008-09-10 22:11:42
|
Quoting pigdog <pigdog@...>: > Oops: 0000 [#1] SMP I'm gonna go out on a limb and suggest that this is the single most salient portion of the dmesg output. |
|
From: Jarod Wilson <jarod@wi...> - 2008-09-11 01:41:08
|
On Wed, 2008-09-10 at 16:11 -0600, alhaz@... wrote: > Quoting pigdog <pigdog@...>: > > > Oops: 0000 [#1] SMP > > I'm gonna go out on a limb and suggest that this is the single most > salient portion of the dmesg output. Yeah, looks like the module went boom upon trying to load, so it not working isn't exactly a surprise. Probably need some newer lirc bits to work on 2.6.27, dunno where Mandr*'s lirc bits come from exactly. Fwiw, the lirc patches we're working on for upstream kernel submission work perfectly fine on 2.6.27 (I tested lirc_mceusb2 just a day or two ago on 2.6.27-rc5-git9). Not sure if there's still something that needs to go into lirc cvs to fix things on 2.6.27, I've not yet started re-syncing bits backwards from the git tree... -- Jarod Wilson jarod@... |
|
From: pigdog <pigdog@no...> - 2008-09-11 20:15:39
Attachments:
Message as HTML
|
So here is a status update - I have the module loading properly now (I hope), but irw still does nothing when buttons are pressed on the remote although I can see the receiver is getting data because the LED on the reciever flashes when I press buttons, just in case you need the info again here it is: I tried it on an older kernel uname -r 2.6.26.3-desktop-1mnb lsusb Bus 002 Device 001: ID 1d6b:0002 Bus 006 Device 003: ID 0471:0608 Philips Bus 006 Device 001: ID 1d6b:0001 Bus 007 Device 001: ID 1d6b:0001 Bus 005 Device 001: ID 1d6b:0001 Bus 003 Device 001: ID 1d6b:0001 Bus 001 Device 001: ID 1d6b:0002 Bus 004 Device 001: ID 1d6b:0001 lsmod | grep lirc lirc_mceusb2 15748 0 lirc_dev 15284 1 lirc_mceusb2 usbcore 135536 6 lirc_mceusb2,usb_storage,uhci_hcd,ohci_hcd,ehci_hcd dmesg ---snip--- lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.44 $ lirc_mceusb2: Daniel Melander <lirc@...>, Martin Blatter <martin_a_blatter@...> usbcore: registered new interface driver lirc_mceusb2 usb 6-1: USB disconnect, address 2 usb 6-1: new full speed USB device using uhci_hcd and address 3 usb 6-1: configuration #1 chosen from 2 choices usb 6-1: New USB device found, idVendor=0471, idProduct=0608 usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 6-1: Product: eHome Infrared Transceiver usb 6-1: Manufacturer: Philips usb 6-1: SerialNumber: PS000DG4 usbcore: deregistering interface driver lirc_mceusb2 lirc_dev: IR Remote Control driver registered, major 61 lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.44 $ lirc_mceusb2: Daniel Melander <lirc@...>, Martin Blatter <martin_a_blatter@...> usbcore: registered new interface driver lirc_mceusb2 heci: schedule work the heci_bh_handler failed error=0 The only fishy thing I can see is most people talk about a /dev/lirc/0 device that should appear but I only get a /dev/lircd and I believe this is why irw is giving me nothing. How do I get the /dev/lirc/0 device to appear, I also saw on another thread/how to that in Mandriva I should copy a file from /tmp/.lirc or something cannot remember exactly what but I do not even get this to appear. Thanks again for the help. -----Original Message----- From: lirc-list-bounces@... on behalf of Jarod Wilson Sent: Thu 9/11/2008 3:45 AM To: lirc-list@... Subject: Re: Cannot get lirc_mceusb2 to do anything On Wed, 2008-09-10 at 16:11 -0600, alhaz@... wrote: > Quoting pigdog <pigdog@...>: > > > Oops: 0000 [#1] SMP > > I'm gonna go out on a limb and suggest that this is the single most > salient portion of the dmesg output. Yeah, looks like the module went boom upon trying to load, so it not working isn't exactly a surprise. Probably need some newer lirc bits to work on 2.6.27, dunno where Mandr*'s lirc bits come from exactly. Fwiw, the lirc patches we're working on for upstream kernel submission work perfectly fine on 2.6.27 (I tested lirc_mceusb2 just a day or two ago on 2.6.27-rc5-git9). Not sure if there's still something that needs to go into lirc cvs to fix things on 2.6.27, I've not yet started re-syncing bits backwards from the git tree... -- Jarod Wilson jarod@... ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ |
|
From: pigdog <pigdog@no...> - 2008-09-21 06:43:20
Attachments:
Message as HTML
|
Another status update: I decided to try another distro as I thought Mandriva might be the cause of my problem but I still get the same issues with ubuntu hardy It seems that my system is not creating the "/dev/lirc/0" device on ubuntu/mandriva I believe again the module is loading correctly as dmesg tells me it is registering new interface for lirc_mceusb2 etc. Nothing I seem to do makes the /dev/lirc/0 device. In ubuntu the irw command jumps back to shell (where in mandriva it appeared to "hang") I hope someone can help me get this going I have been trying for a couple of months now with absolutely no luck at all and I believe the error is actually in my stupidity. From: lirc-list-bounces@... [mailto:lirc-list-bounces@...] On Behalf Of pigdog Sent: 11 September 2008 10:30 PM To: Jarod Wilson; lirc-list@... Subject: RE: Cannot get lirc_mceusb2 to do anything So here is a status update - I have the module loading properly now (I hope), but irw still does nothing when buttons are pressed on the remote although I can see the receiver is getting data because the LED on the reciever flashes when I press buttons, just in case you need the info again here it is: I tried it on an older kernel uname -r 2.6.26.3-desktop-1mnb lsusb Bus 002 Device 001: ID 1d6b:0002 Bus 006 Device 003: ID 0471:0608 Philips Bus 006 Device 001: ID 1d6b:0001 Bus 007 Device 001: ID 1d6b:0001 Bus 005 Device 001: ID 1d6b:0001 Bus 003 Device 001: ID 1d6b:0001 Bus 001 Device 001: ID 1d6b:0002 Bus 004 Device 001: ID 1d6b:0001 lsmod | grep lirc lirc_mceusb2 15748 0 lirc_dev 15284 1 lirc_mceusb2 usbcore 135536 6 lirc_mceusb2,usb_storage,uhci_hcd,ohci_hcd,ehci_hcd dmesg ---snip--- lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.44 $ lirc_mceusb2: Daniel Melander <lirc@...>, Martin Blatter <martin_a_blatter@...> usbcore: registered new interface driver lirc_mceusb2 usb 6-1: USB disconnect, address 2 usb 6-1: new full speed USB device using uhci_hcd and address 3 usb 6-1: configuration #1 chosen from 2 choices usb 6-1: New USB device found, idVendor=0471, idProduct=0608 usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 6-1: Product: eHome Infrared Transceiver usb 6-1: Manufacturer: Philips usb 6-1: SerialNumber: PS000DG4 usbcore: deregistering interface driver lirc_mceusb2 lirc_dev: IR Remote Control driver registered, major 61 lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.44 $ lirc_mceusb2: Daniel Melander <lirc@...>, Martin Blatter <martin_a_blatter@...> usbcore: registered new interface driver lirc_mceusb2 heci: schedule work the heci_bh_handler failed error=0 The only fishy thing I can see is most people talk about a /dev/lirc/0 device that should appear but I only get a /dev/lircd and I believe this is why irw is giving me nothing. How do I get the /dev/lirc/0 device to appear, I also saw on another thread/how to that in Mandriva I should copy a file from /tmp/.lirc or something cannot remember exactly what but I do not even get this to appear. Thanks again for the help. -----Original Message----- From: lirc-list-bounces@... on behalf of Jarod Wilson Sent: Thu 9/11/2008 3:45 AM To: lirc-list@... Subject: Re: Cannot get lirc_mceusb2 to do anything On Wed, 2008-09-10 at 16:11 -0600, alhaz@... wrote: > Quoting pigdog <pigdog@...>: > > > Oops: 0000 [#1] SMP > > I'm gonna go out on a limb and suggest that this is the single most > salient portion of the dmesg output. Yeah, looks like the module went boom upon trying to load, so it not working isn't exactly a surprise. Probably need some newer lirc bits to work on 2.6.27, dunno where Mandr*'s lirc bits come from exactly. Fwiw, the lirc patches we're working on for upstream kernel submission work perfectly fine on 2.6.27 (I tested lirc_mceusb2 just a day or two ago on 2.6.27-rc5-git9). Not sure if there's still something that needs to go into lirc cvs to fix things on 2.6.27, I've not yet started re-syncing bits backwards from the git tree... -- Jarod Wilson jarod@... ------------------------------------------------------------------------ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ __________ Information from ESET NOD32 Antivirus, version of virus signature database 3435 (20080911) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 3436 (20080911) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 3446 (20080916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com |
|
From: <lirc@ba...> - 2008-09-21 11:00:17
|
Hi! pigdog "pigdog@..." wrote: [...] > Bus 006 Device 003: ID 0471:0608 Philips This device is currently not listed in the usb_remote_table in lirc_mceusb2.c. If you think lirc_mceusb2 is the right driver for your device, you will have to add it to the list. Christoph |
|
From: pigdog <pigdog@no...> - 2008-09-21 12:22:27
|
Good day,
Firstly I am very sure that lirc_mceusb2 is the right driver as it is a
philips remote with RC6 remote controller and research I have done seems
to suggest it is an OEM version of the Windows Media Center Remote, the
remote also works 100% with windows using the windows default driver for
the MCE remotes.
However would I be right in saying:
Goto /var/lib/dkms/lirc/0.8.3-4mdv2009.0/source/drivers/lirc_mceusb2 and
edit lirc_mceusb2.c and add
/* Philips - Sahara Branded */
{ USB_DEVICE(VENDOR_PHILIPS, 0x0608) },
Lines to the file so that my file looks like this
...snip...
#define VENDOR_PHILIPS 0x0471
#define VENDOR_SMK 0x0609
#define VENDOR_TATUNG 0x1460
#define VENDOR_GATEWAY 0x107b
#define VENDOR_SHUTTLE 0x1308
#define VENDOR_SHUTTLE2 0x051c
#define VENDOR_MITSUMI 0x03ee
#define VENDOR_TOPSEED 0x1784
#define VENDOR_RICAVISION 0x179d
#define VENDOR_ITRON 0x195d
#define VENDOR_FIC 0x1509
#define VENDOR_LG 0x043e
#define VENDOR_MICROSOFT 0x045e
#define VENDOR_FORMOSA 0x147a
#define VENDOR_FINTEK 0x1934
static struct usb_device_id usb_remote_table [] = {
/* Philips eHome Infrared Transceiver */
{ USB_DEVICE(VENDOR_PHILIPS, 0x0815) },
/* Philips Infrared Transceiver - HP branded */
{ USB_DEVICE(VENDOR_PHILIPS, 0x060c) },
/* Philips SRM5100 */
{ USB_DEVICE(VENDOR_PHILIPS, 0x060d) },
/* Philips - Sahara Branded */
{ USB_DEVICE(VENDOR_PHILIPS, 0x0608) },
/* SMK/Toshiba G83C0004D410 */
{ USB_DEVICE(VENDOR_SMK, 0x031d) },
/* SMK eHome Infrared Transceiver (Sony VAIO) */
{ USB_DEVICE(VENDOR_SMK, 0x0322) },
/* bundled with Hauppauge PVR-150 */
...snip...
Then with dkms rebuild and reinstall the module with the new code in
place
Then modprobe lirc_mceusb2
But this still gives me no response with irw and still does not create
the /dev/lirc/0 device
I know I am doing something wrong or leaving an important step out and
would like to get this working just need some direction
Kind Regards
Wayne Rolfe
Novicus Systems
T: 083 704 1624
F: 086 654 4043
E: wayne@...
W: http://www.novicus.com
-----Original Message-----
From: Christoph Bartelmus [mailto:lirc@...]
Sent: 21 September 2008 01:16 PM
To: lirc-list@...
Subject: Re: Cannot get lirc_mceusb2 to do anything
Hi!
pigdog "pigdog@..." wrote:
[...]
> Bus 006 Device 003: ID 0471:0608 Philips
This device is currently not listed in the usb_remote_table in
lirc_mceusb2.c. If you think lirc_mceusb2 is the right driver for your
device, you will have to add it to the list.
Christoph
------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3458 (20080921) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3458 (20080921) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
|
|
From: <lirc@ba...> - 2008-09-21 14:16:28
|
Hi! pigdog "pigdog@..." wrote: [...] > However would I be right in saying: > > Goto /var/lib/dkms/lirc/0.8.3-4mdv2009.0/source/drivers/lirc_mceusb2 and Please understand that when you try to use 2.6.27 I will not comment anything other than latest LIRC CVS. Christoph |
|
From: pigdog <pigdog@no...> - 2008-09-21 21:29:04
|
Good day,
OK so i think I have gotten a little further with the ubuntu system
Kernel 2.6.24-19-generic
lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 0e0f:0002
Bus 001 Device 002: ID 0471:0608 Philips
Bus 001 Device 001: ID 0000:0000
Dmesg | grep lirc
[ 1208.747761] lirc_dev: IR Remote Control driver registered, at major
61
[ 1208.784478] lirc_mceusb2: Philips eHome USB IR Transciever and
Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.33 $
[ 1208.784491] lirc_mceusb2: Daniel Melander <lirc@...>, Martin
Blatter <martin_a_blatter@...>
[ 1208.794981] usbcore: registered new interface driver lirc_mceusb2
And modified the lirc_mceusb2.c file to contain:
static struct usb_device_id usb_remote_table [] = {
/* Philips eHome Infrared Transceiver */
{ USB_DEVICE(VENDOR_PHILIPS, 0x0815) },
/* Philips Infrared Transceiver - HP branded */
{ USB_DEVICE(VENDOR_PHILIPS, 0x060c) },
/* Philips Infrared Transceiver - Sahara branded */
{ USB_DEVICE(VENDOR_PHILIPS, 0x0608) },
/* Philips SRM5100 */
{ USB_DEVICE(VENDOR_PHILIPS, 0x060d) },
/* Philips Infrared Transceiver - Omaura */
{ USB_DEVICE(VENDOR_PHILIPS, 0x060f) },
And using lirc version lirc-0.8.4pre1
My /etc/lirc/hardware.conf file looks like this
# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Windows Media Center Remotes (new version Philips et al.)"
REMOTE_MODULES="lirc_dev lirc_mceusb2"
REMOTE_DRIVER="default"
REMOTE_DEVICE="/dev/lirc" <-- (I had this as /dev/lirc/0 as well but no
different)
REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb"
REMOTE_LIRCD_ARGS=""
#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""
#Enable lircd
START_LIRCD="true"
#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"
# Default configuration files for your hardware if any
LIRCMD_CONF=""
#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""
I now get /dev/lirc /dev/lircd devices and irw now "hangs" as opposed to
kicking me back to shell like it used to
I have given up on trying to get it to run on Mandriva Cooker for now
and I am trying to focus on getting it working on a stable kernel
because the way I see it if I can just get it to run on 2.6.24 I can
then retrace my steps to try and get it working on the newer kernel but
first order of the day is to get it working by any means possible.
Kind Regards
Wayne Rolfe
Novicus Systems
T: 083 704 1624
F: 086 654 4043
E: wayne@...
W: http://www.novicus.com
-----Original Message-----
From: Christoph Bartelmus [mailto:lirc@...]
Sent: 21 September 2008 04:30 PM
To: lirc-list@...
Subject: Re: Cannot get lirc_mceusb2 to do anything
Hi!
pigdog "pigdog@..." wrote:
[...]
> However would I be right in saying:
>
> Goto /var/lib/dkms/lirc/0.8.3-4mdv2009.0/source/drivers/lirc_mceusb2
and
Please understand that when you try to use 2.6.27 I will not comment
anything other than latest LIRC CVS.
Christoph
------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3458 (20080921) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3458 (20080921) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
|
|
From: <lirc@ba...> - 2008-09-22 06:31:02
|
Hi! pigdog "pigdog@..." wrote: [...] > [ 1208.784478] lirc_mceusb2: Philips eHome USB IR Transciever and > Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.33 $ Whatever you are loading here, it's definitely not the kernel module contained in lirc-0.8.4pre1. Christoph |