Salut,
je viens de l'acquerir, mais ces problèmes aussi.
problèmes rencontrés :
Méthode LIRC
- irw tue lircd ou s'il ne le tue pas, ne répond pas à la télécommande
- irrecord n'arrive pas à démarrer.
j'ai suivi tout le forums et le liens associés, mais en vain,
reste à faire :
tester la méthode kernel/gatos (bien que je n'ai pas d'inteface graphique, aka X)
pour que vous puissiez éventuellement m'aider, je vous joint mes logs :
OS: Debian Sid
kernel: 2.6.10
lircd 0.7.0
usbview :
Code :
- USB Receiver
- Manufacturer: X10 Wireless Technology Inc
- Speed: 1.5Mb/s (low)
- USB Version: 1.10
- Device Class: 00(>ifc )
- Device Subclass: 00
- Device Protocol: 00
- Maximum Default Endpoint Size: 8
- Number of Configurations: 1
- Vendor Id: 0bc7
- Product Id: 0004
- Revision Number: 1.00
|
chargement des modules :
$ modprobe lirc_atiusb debug=1 unique=1
remarque : lirc à été compilé avec l'option debug
kern.log :
Code :
- Mar 26 14:58:56 londinium kernel: lirc_dev: IR Remote Control driver registered, at major 61
- Mar 26 14:58:56 londinium kernel:
- Mar 26 14:58:56 londinium kernel: lirc_atiusb: USB remote driver for LIRC v0.4
- Mar 26 14:58:56 londinium kernel: lirc_atiusb: Paul Miller <pmiller9@users.sourceforge.net>
- Mar 26 14:58:56 londinium kernel: lirc_atiusb: debug mode enabled
- Mar 26 14:58:56 londinium kernel: lirc_atiusb: usb probe called
- Mar 26 14:58:56 londinium kernel: lirc_atiusb: acceptable inbound endpoint found
- Mar 26 14:58:56 londinium kernel: lirc_atiusb: acceptable outbound endpoint found
- Mar 26 14:58:56 londinium kernel: lirc_atiusb[2]: bytes_in_key=5 len=8 maxp=8 buf_len=5
- Mar 26 14:58:56 londinium kernel: lirc_dev: lirc_register_plugin:sample_rate: 0
- Mar 26 14:58:57 londinium kernel: lirc_atiusb[2]: X10 Wireless Technology Inc USB Receiver on usb1:2
- Mar 26 14:58:57 londinium kernel: lirc_atiusb[2]: send called (0x8004)
- Mar 26 14:58:57 londinium kernel: lirc_atiusb[2]: usb out called
- Mar 26 14:58:57 londinium kernel: lirc_atiusb[2]: send complete (0x8004)
- Mar 26 14:58:57 londinium kernel: usb_unlink_urb() is deprecated for synchronous unlinks. Use usb_kill_urb() instead.
- Mar 26 14:58:57 londinium kernel: Badness in usb_unlink_urb at drivers/usb/core/urb.c:457
- Mar 26 14:58:57 londinium kernel: [pg0+206877437/1070113792] usb_unlink_urb+0x9d/0xa0 [usbcore]
- Mar 26 14:58:57 londinium kernel: [pg0+207929710/1070113792] send_packet+0x16e/0x230 [lirc_atiusb]
- Mar 26 14:58:57 londinium kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
- Mar 26 14:58:57 londinium kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
- Mar 26 14:58:57 londinium kernel: [pg0+207932848/1070113792] usb_remote_probe+0x470/0x810 [lirc_atiusb]
- Mar 26 14:58:57 londinium kernel: [kobject_hotplug+624/768] kobject_hotplug+0x270/0x300
- Mar 26 14:58:57 londinium kernel: [pg0+206852242/1070113792] usb_probe_interface+0x72/0x90 [usbcore]
- Mar 26 14:58:57 londinium kernel: [driver_probe_device+47/128] driver_probe_device+0x2f/0x80
- Mar 26 14:58:57 londinium kernel: [driver_attach+92/160] driver_attach+0x5c/0xa0
- Mar 26 14:58:57 londinium kernel: [bus_add_driver+157/208] bus_add_driver+0x9d/0xd0
- Mar 26 14:58:57 londinium kernel: [driver_register+47/64] driver_register+0x2f/0x40
- Mar 26 14:58:57 londinium kernel: [vprintk+268/368] vprintk+0x10c/0x170
- Mar 26 14:58:57 londinium kernel: [pg0+206852492/1070113792] usb_register+0x4c/0xb0 [usbcore]
- Mar 26 14:58:57 londinium kernel: [printk+23/32] printk+0x17/0x20
- Mar 26 14:58:57 londinium kernel: [pg0+206717003/1070113792] usb_remote_init+0x4b/0x7e [lirc_atiusb]
- Mar 26 14:58:57 londinium kernel: [sys_init_module+354/528] sys_init_module+0x162/0x210
- Mar 26 14:58:57 londinium kernel: [syscall_call+7/11] syscall_call+0x7/0xb
- Mar 26 14:58:57 londinium kernel: lirc_atiusb[2]: send called (0x8007)
- Mar 26 14:58:57 londinium kernel: lirc_atiusb[2]: usb out called
- Mar 26 14:58:57 londinium kernel: lirc_atiusb[2]: send complete (0x8007)
- Mar 26 14:58:57 londinium kernel: usb_unlink_urb() is deprecated for synchronous unlinks. Use usb_kill_urb() instead.
- Mar 26 14:58:57 londinium kernel: Badness in usb_unlink_urb at drivers/usb/core/urb.c:457
- Mar 26 14:58:57 londinium kernel: [pg0+206877437/1070113792] usb_unlink_urb+0x9d/0xa0 [usbcore]
- Mar 26 14:58:57 londinium kernel: [pg0+207929710/1070113792] send_packet+0x16e/0x230 [lirc_atiusb]
- Mar 26 14:58:57 londinium kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
- Mar 26 14:58:57 londinium kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
- Mar 26 14:58:57 londinium kernel: [pg0+207932874/1070113792] usb_remote_probe+0x48a/0x810 [lirc_atiusb]
- Mar 26 14:58:57 londinium kernel: [kobject_hotplug+624/768] kobject_hotplug+0x270/0x300
- Mar 26 14:58:57 londinium kernel: [pg0+206852242/1070113792] usb_probe_interface+0x72/0x90 [usbcore]
- Mar 26 14:58:57 londinium kernel: [driver_probe_device+47/128] driver_probe_device+0x2f/0x80
- Mar 26 14:58:57 londinium kernel: [driver_attach+92/160] driver_attach+0x5c/0xa0
- Mar 26 14:58:57 londinium kernel: [bus_add_driver+157/208] bus_add_driver+0x9d/0xd0
- Mar 26 14:58:57 londinium kernel: [driver_register+47/64] driver_register+0x2f/0x40
- Mar 26 14:58:57 londinium kernel: [vprintk+268/368] vprintk+0x10c/0x170
- Mar 26 14:58:57 londinium kernel: [pg0+206852492/1070113792] usb_register+0x4c/0xb0 [usbcore]
- Mar 26 14:58:57 londinium kernel: [printk+23/32] printk+0x17/0x20
- Mar 26 14:58:57 londinium kernel: [pg0+206717003/1070113792] usb_remote_init+0x4b/0x7e [lirc_atiusb]
- Mar 26 14:58:57 londinium kernel: [sys_init_module+354/528] sys_init_module+0x162/0x210
- Mar 26 14:58:57 londinium kernel: [syscall_call+7/11] syscall_call+0x7/0xb
- Mar 26 14:58:57 londinium kernel: usbcore: registered new driver lirc_atiusb
|
les modules intéressants chargés (pas ati_remote)
Code :
- Module Size Used by
- lirc_atiusb 13164 0
- lirc_dev 13676 1 lirc_atiusb
- uhci_hcd 33968 0
- usbcore 122008 3 lirc_atiusb,uhci_hcd
|
les droits sur les périphériques :
Code :
- crw-rw-rw- 1 root root 61, 0 2005-03-20 21:19 /dev/lirc
- srw-rw-rw- 1 root root 0 2005-03-26 15:03 /dev/lircd
- prw-rw-rw- 1 root root 0 2005-03-20 21:19 /dev/lircm
|
démarrage de lircd
$ lircd --debug
/var/log/lircd :
Code :
- Mar 26 15:03:39 londinium lircd 0.7.0: caught signal
- Mar 26 15:03:43 londinium lircd 0.7.0: started server socket
- Mar 26 15:03:43 londinium lircd 0.7.0: parsing remote
- Mar 26 15:03:43 londinium lircd 0.7.0: parsing atiusb remote
- Mar 26 15:03:43 londinium lircd 0.7.0: config file read
- Mar 26 15:03:43 londinium lircd 0.7.0: lircd(atiusb) ready
|
test avec irrecord
sortie de irrecord :
Code :
- 15:04 root@londinium /etc# irrecord lircd.conf.mine
- irrecord - application for recording IR-codes for usage with lirc
- Copyright (C) 1998,1999 Christoph Bartelmus(lirc@bartelmus.de)
- irrecord: could not get hardware features
- irrecord: this device driver does not support the new LIRC interface
- irrecord: make sure you use a current version of the driver
- irrecord: could not init hardware (lircd running ? --> close it, check permissions
|
et si je lance irw, ça peut me tuer lircd :
/var/log/lircd
Code :
- Mar 26 15:20:26 londinium lircd 0.7.0: registering local client
- Mar 26 15:20:26 londinium lircd 0.7.0: accepted new client on /dev/lircd
- Mar 26 15:20:26 londinium lircd 0.7.0: could not get hardware features
- Mar 26 15:20:26 londinium lircd 0.7.0: this device driver does not support the new LIRC interface
- Mar 26 15:20:26 londinium lircd 0.7.0: make sure you use a current version of the driver
- Mar 26 15:20:26 londinium lircd 0.7.0: caught signal
|
Si vous avez des pistes pour que je m'en sorte, ça serai cool, et puis ça serait bien d'enterrer ce topic !
++franz
Message édité par fr4nz6 le 26-03-2005 à 21:01:33