Moin,
bevor ich mich aufs Sofa zurücklehnen kann und mein yavdr Testsystem richtig benutzen kann muss erst Lirc laufen 
Genau da ist mein Problem.
Verwende einen USB FT232RL Wandler mit einem TSOP dran (hat bereits funktioniert unter anderen Systemen)
Code
root@vdr2:/# lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
In der yaVDR Configuration im Webbrowser habe ich Lirc auf FTDI FT232-based IR Receiver gestellt.
In /var/log/messages steht:
Code
Aug 7 10:20:45 vdr2 kernel: [ 2964.645956] USB Serial support registered for FTDI USB Serial Device
Aug 7 10:20:45 vdr2 kernel: [ 2964.646669] ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
Aug 7 10:20:45 vdr2 kernel: [ 2964.646937] usb 2-1: Detected FT232RL
Aug 7 10:20:45 vdr2 kernel: [ 2964.646947] usb 2-1: Number of endpoints 2
Aug 7 10:20:45 vdr2 kernel: [ 2964.646955] usb 2-1: Endpoint 1 MaxPacketSize 64
Aug 7 10:20:45 vdr2 kernel: [ 2964.646962] usb 2-1: Endpoint 2 MaxPacketSize 64
Aug 7 10:20:45 vdr2 kernel: [ 2964.646968] usb 2-1: Setting MaxPacketSize 64
Aug 7 10:20:45 vdr2 kernel: [ 2964.648664] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
Aug 7 10:20:45 vdr2 kernel: [ 2964.648729] usbcore: registered new interface driver ftdi_sio
Aug 7 10:20:45 vdr2 kernel: [ 2964.648736] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
Aug 7 10:20:46 vdr2 kernel: [ 2965.134581] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Aug 7 10:20:46 vdr2 kernel: [ 2965.134670] ftdi_sio 2-1:1.0: device disconnectedCode
root@vdr2:/# lsmod | grep usb
usbserial 33019 1 ftdi_sio
Mit cat /proc/bus/input/devices ist nix zu sehen:
Code
root@vdr2:/var/log# cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=mouse0 event2
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3
U: Uniq=
H: Handlers=kbd event3
B: EV=3
B: KEY=3f000b 0 0 0 0 0 0 0
I: Bus=0001 Vendor=10ec Product=0662 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=40001
B: SND=6
I: Bus=0001 Vendor=13c2 Product=000e Version=0002
N: Name="DVB on-card IR receiver"
P: Phys=pci-0000:05:00.0/ir0
S: Sysfs=/devices/pci0000:00/0000:00:1e.0/0000:05:00.0/input/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=100013
B: KEY=fc812 a052041 0 0 0 0 0 4000 40002800 1e1680 0 0 ffc
B: MSC=18Die yavdr erzeugte /etc/lirc/hardware.conf
Code
# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="FTDI FT232-based IR Receiver"
REMOTE_MODULES=""
REMOTE_DRIVER="ftdi"
REMOTE_DEVICE=""
REMOTE_LIRCD_CONF=""
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=""
lirc läuft:
Code
root@vdr2:/# ps -ef | grep lirc
root 596 1 0 10:22 ? 00:00:00 /usr/sbin/lircd --nodaemon --output=/var/run/lirc/lircd --driver=ftdi
root 1101 596 3 10:23 ? 00:01:07 /usr/sbin/lircd --nodaemon --output=/var/run/lirc/lircd --driver=ftdi
root 1511 1153 0 10:56 pts/0 00:00:00 grep --color=auto lirc
Die /etc/lirc/lirc.conf ist entsprechend meiner FB vorhanden.
Das Device /dev/ttyUSB0 wird nicht erstellt, weil ftdi_sio übernimmt.
Code
root@vdr2:/# ls -l /dev/li*
lrwxrwxrwx 1 root root 19 2010-08-07 10:22 /dev/lircd -> /var/run/lirc/lircd
Was kann ich tun damit meine FB läuft ? Hilfe
Trotzdem munter bleiben, Rossi