From: Bill S. <bso...@me...> - 2006-09-26 12:03:13
|
Hi I have a USB-UIRT tranciever that I wish to use with DirectFB as an i/o device. I have it running on a Linux machine (VIA EPIA-M) with the patches from http://www.davidnevel.org/ which I have applied to lirc 0.7.1. I can't find later patches for the current lirc package version. lircd starts up without problem, but when my app connects the daemon crashes with the following messages: usb 2-1: new full speed USB device using uhci_hcd and address 2 usb 2-1: configuration #1 chosen from 1 choice ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT232BM usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0 Jan 20 00:29:21 user.info kernel: usb 2-1: new full speed USB device using uhci_hcd and address 2 Jan 20 00:29:21 user.info kernel: usb 2-1: configuration #1 chosen from 1 choice Jan 20 00:29:21 user.info kernel: ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected Jan 20 00:29:21 user.info kernel: drivers/usb/serial/ftdi_sio.c: Detected FT232BM Jan 20 00:29:21 user.info kernel: usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0 # lircd -n lircd-0.7.1[621]: lircd(usb-uirt2_raw) ready lircd-0.7.1[621]: accepted new client on /dev/lircd lircd-0.7.1[621]: uirt2usb_raw: UIRT version 0509 ok lircd-0.7.1[621]: removed client lircd-0.7.1[621]: invalid lockfile (/var/lock/ifstate) detected lircd-0.7.1[621]: invalid lockfile (/var/lock/resolv.conf) detected lircd-0.7.1[621]: accepted new client on /dev/lircd lircd-0.7.1[621]: command_ext: checksum error lircd-0.7.1[621]: uirt2usb_raw: No UIRT2 device found at /dev/lirc lircd-0.7.1[621]: invalid lockfile (/var/lock/ifstate) detected lircd-0.7.1[621]: invalid lockfile (/var/lock/resolv.conf) detected lircd-0.7.1[621]: caught signal Terminated The USB-UIRT device seems to be receiving IR data as soon as lircd initiates a connection and I think this is the cause of the problem. I am investigating why this device is so sensitive (I think the data is ambient IR activity), but nevertheless this should not cause lircd to fall over. Has anyone had similar problems, does anyone known how to get this device working with the current lirc version, does anyone know how to stop lircd from crashing like this. Note that if I completely shield the module from IR sources while the connection is made then everything works much better. -- Bill Somerville This message has been scanned by MailController - www.MailController.altohiway.com |