I am trying to get my VLSystems MPlay Blast (the standalone one, not
Zalman HD135) to work with lirc 0.8.6 or 0.8.5 but it doesn't work.
The device is found by the kernel and mounted on /dev/ttyUSB0:
# dmesg |grep "usb 3-4"
usb 3-4: new full speed USB device using ohci_hcd and address 2
usb 3-4: New USB device found, idVendor=0403, idProduct=6001
usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-4: Product: FT232R USB UART
usb 3-4: Manufacturer: FTDI
usb 3-4: SerialNumber: A3000F9Z
usb 3-4: configuration #1 chosen from 1 choice
usb 3-4: Detected FT232RL
usb 3-4: Number of endpoints 2
usb 3-4: Endpoint 1 MaxPacketSize 64
usb 3-4: Endpoint 2 MaxPacketSize 64
usb 3-4: Setting MaxPacketSize 64
usb 3-4: FTDI USB Serial Device converter now attached to ttyUSB0
There are 2 end points because there is the LCD screen as output and
IR receiver as input. The LCD works out of the box with LCDproc.
At this page, I see that it should be working with the mplay driver
without any kernel module
VLSystem MPlay Blast mplay none mplay vlsystem/lircd.conf.mplay
I have the following:
# ps -ef | grep lircd
root 2862 1 0 15:59 ? 00:00:00 lircd --driver=mplay
But when I run irw, I don't see anything coming to the console when
pressing any key from the remote.
When starting lircd, I have the following message in the lircd log:
lircd-0.8.6: lircd(mplay) ready, using /var/run/lirc/lircd
When starting irw:
lircd-0.8.6: accepted new client on /var/run/lirc/lircd
Linux kernel version is 126.96.36.199 (I tried with 2.6.29 before).
I know that the remote control is not broken because the VLSystems
MPlay Blast has a direct connection to the soft power on the
motherboard and I can turn on the PC with the remote without problem.
Any help would be very much appreciated.
Links already visited to try to fix this issue: