You are not logged in.
I put this in a separate thread because I seem to have a different problem to the 'double press' issue and I'm pretty sure my remote isn't covered by mceusb. I've got a remote that until recently worked perfectly with the lirc_atiusb driver. However I get no output with irw or in boxee. I still get this in my dmesg output:
lirc_atiusb: USB remote driver for LIRC $Revision: 1.88 $
lirc_atiusb: Paul Miller <pmiller9@users.sourceforge.net>
lirc_atiusb 3-1:1.0: lirc_dev: driver lirc_atiusb registered at minor = 0
lirc_atiusb[2]: X10 WTI RF receiver on usb3:2
usbcore: registered new interface driver lirc_atiusb
Here is lircd.conf:
# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.8.2(default) on Sun Aug 12 02:13:30 2007
#
# contributed by Ben Adler @ gmx dot net
#
# brand: Medion / X10 (part of http://www.medion.de/md8824/)
# remote control: RF Vista Remote Control (OR24V)
# P/N: 2003 5335
# devices being controlled by this remote: USB RF remote receiver (CM20E), P/N 2003 1776
begin remote
name Medion_X10
bits 16
eps 30
aeps 100
one 0 0
zero 0 0
pre_data_bits 8
pre_data 0x14
post_data_bits 16
post_data 0x0
gap 227978
toggle_bit_mask 0x80800000
begin codes
red 0x87B2
yellow 0x0934
blue 0x8AB5
green 0x0833
power 0xD702
text 0xEB16
tvrecord 0x6D98
disc 0xD904
table 0x86B1
tvplay 0xF11C
back 0x75A0
info 0x042F
volume_up 0x5E89
volume_down 0xDD08
mute 0x5580
channel_up 0xE00B
channel_down 0x618C
cursor_up 0xEF1A
cursor_down 0x77A2
cursor_left 0xF21D
cursor_right 0x749F
ok 0xF31E
start 0x709B
track_previous 0xF621
track_next 0x78A3
record 0xFC27
pause 0x7EA9
stop 0xFD28
seek_backward 0x79A4
play 0xFA25
seek_forward 0x7BA6
1 0xE20D
2 0x638E
3 0xE40F
4 0x6590
5 0xE611
6 0x6792
7 0xE813
8 0x6994
9 0xEA15
0 0x6C97
asterisk 0x0C37
hash 0x8DB8
clear 0x0530
enter 0x8BB6
end codes
end remote
And here is my current lsmod | grep lirc, although I've tried a bunch of different setups with and without the lirc package:
lirc_atiusb 12179 0
ir_lirc_codec 3135 0
lirc_dev 7140 2 lirc_atiusb,ir_lirc_codec
ir_core 12433 11 ir_lirc_codec,ir_sony_decoder,rc_hauppauge_new,ir_jvc_decoder,saa7134,budget_ci,ir_rc6_decoder,ir_rc5_decoder,ir_common,ir_nec_decoder
usbcore 115802 5 lirc_atiusb,usbhid,ohci_hcd,ehci_hcd
Thanks in advance, and sorry for the second thread.
Offline
hi there,
same problem here. no putput from irw and no actions through irexec. before the update to kernel 2.6.36 everything worked fine with my x10 RF USB reciever.
dmesg | tail
usb 4-4: new low speed USB device using ohci_hcd and address 3
lirc_atiusb 4-4:1.0: lirc_dev: driver lirc_atiusb registered at minor = 0
lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on usb4:3
lsmod | grep lirc
lirc_atiusb 13687 0
usbcore 137570 4 lirc_atiusb,ohci_hcd,ehci_hcd
lirc_dev 8500 1 lirc_atiusb
lsusb
Bus 004 Device 003: ID 0bc7:0006 X10 Wireless Technology, Inc. Wireless Transceiver (ACPI-compliant)
Am I using the wrong kernel modules for kernel 2.6.36??
Offline
Hi,
i have the same problem with my X10 Remote.
I wrote the lirc developers: http://old.nabble.com/lirc_atiusb-and-2 … 53763.html
They recommend to use the ati_remote module. But for my remote control this modules doesn't work as i want.
The current lirc_atiusb module is just a pre version. So i think this is an upstream bug.
The current solution for me: i stay with 2.6.35 as long the bug is fixed.
Offline
Hi,
i have the same problem with my X10 Remote.
I wrote the lirc developers: http://old.nabble.com/lirc_atiusb-and-2 … 53763.html
They recommend to use the ati_remote module. But for my remote control this modules doesn't work as i want.
The current lirc_atiusb module is just a pre version. So i think this is an upstream bug.The current solution for me: i stay with 2.6.35 as long the bug is fixed.
I'd have to roll back my graphics drivers amongst other things, and the new kernel fixed an issue with my network card I'll try the ati_remote module when I get home.
Last edited by rocktorrentz (2010-11-29 13:12:32)
Offline
We should give the developers some input and open a bugreport. The best solution for us would be if the module is working again.
Currently i am at work. Maybe i'll do this in the late evening.
Offline
We should give the developers some input and open a bugreport. The best solution for us would be if the module is working again.
Currently i am at work. Maybe i'll do this in the late evening.
I tried lirc-git with no such luck. I also tried ati_remote which registers key presses as keyboard events rather than going through lirc, but for some reason to get any output you have to press buttons twice.
I've just given up and downgraded kernel26, nvidia, nvidia-utils, lirc and lirc-utils. It's not ideal, but everything works...I'll keep an eye on this.
Offline
I know the problem with the double presses. There is patch for the kernel available. But that doesn't solve my problems that not every key on my remote is registered.
Offline
I know the problem with the double presses. There is patch for the kernel available. But that doesn't solve my problems that not every key on my remote is registered.
Yeah with ati_remote it only registers some keys, and only if you press them twice. I want my working lirc_atiusb back It works absolutely perfectly with the old lirc version and 2.6.35 kernel.
Offline