Ancora problemi con il telecomando.
Moderatori: ragno, tapino, alez, zulu, davidea
-
- Messaggi: 364
- Iscritto il: 23 ago 2007, 20:10
- Località: /dev/null
Ancora problemi con il telecomando.
Se avvio VDR da riga di comando il telecomando funziona:
cd /vdr/curent
./vdr -Premote -c /etc/vdr
Se riavvio, VDR non funziona più.
Sono valide i consigli per Udev descritte qui' http://vdr.spaghettilinux.org/index.php ... elecomando
anche se il remote.conf non è di tipo event ma cosi'?
remote-ir._Setup /proc/av7110_ir 00000000 21
remote-ir.Up 000000010001000E
remote-ir.Down 0000000100010012
remote-ir.Menu 0000000100010019
remote-ir.Ok 0000000100010010
remote-ir.Back 0000000100010003
remote-ir.Left 000000010001000F
remote-ir.Right 0000000100010011
remote-ir.Red 0000000100010015
remote-ir.Green 0000000100010016
remote-ir.Yellow 0000000100010017
remote-ir.Blue 0000000100010018
remote-ir.0 000000010001000D
remote-ir.1 0000000100010004
remote-ir.2 0000000100010005
remote-ir.3 0000000100010006
remote-ir.4 0000000100010007
remote-ir.5 0000000100010008
remote-ir.6 0000000100010009
remote-ir.7 000000010001000A
remote-ir.8 000000010001000B
remote-ir.9 000000010001000C
remote-ir.Play 0000000100010022
remote-ir.Pause 0000000100010013
remote-ir.Stop 0000000100010023
remote-ir.Record 0000000100010014
remote-ir.FastFwd 000000010001001B
remote-ir.FastRew 0000000100010028
remote-ir.Power 0000000100010002
remote-ir.Channel+ 0000000100010024
remote-ir.Channel- 0000000100010025
remote-ir.Volume+ 0000000100010026
remote-ir.Volume- 0000000100010027
cd /vdr/curent
./vdr -Premote -c /etc/vdr
Se riavvio, VDR non funziona più.
Sono valide i consigli per Udev descritte qui' http://vdr.spaghettilinux.org/index.php ... elecomando
anche se il remote.conf non è di tipo event ma cosi'?
remote-ir._Setup /proc/av7110_ir 00000000 21
remote-ir.Up 000000010001000E
remote-ir.Down 0000000100010012
remote-ir.Menu 0000000100010019
remote-ir.Ok 0000000100010010
remote-ir.Back 0000000100010003
remote-ir.Left 000000010001000F
remote-ir.Right 0000000100010011
remote-ir.Red 0000000100010015
remote-ir.Green 0000000100010016
remote-ir.Yellow 0000000100010017
remote-ir.Blue 0000000100010018
remote-ir.0 000000010001000D
remote-ir.1 0000000100010004
remote-ir.2 0000000100010005
remote-ir.3 0000000100010006
remote-ir.4 0000000100010007
remote-ir.5 0000000100010008
remote-ir.6 0000000100010009
remote-ir.7 000000010001000A
remote-ir.8 000000010001000B
remote-ir.9 000000010001000C
remote-ir.Play 0000000100010022
remote-ir.Pause 0000000100010013
remote-ir.Stop 0000000100010023
remote-ir.Record 0000000100010014
remote-ir.FastFwd 000000010001001B
remote-ir.FastRew 0000000100010028
remote-ir.Power 0000000100010002
remote-ir.Channel+ 0000000100010024
remote-ir.Channel- 0000000100010025
remote-ir.Volume+ 0000000100010026
remote-ir.Volume- 0000000100010027
VDRBox HD:
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
Re: Ancora problemi con il telecomando.
Dai questo comando da terminale e scrivi qui l'output:
Codice: Seleziona tutto
cat /proc/bus/input/devices
VDRBOX:
Software: ArchLinux 0.8 Don't Panic, VDR 1.6.0-2 con Extension Patch v.62 (> 70 plugins in IT)
Hardware: Intel P4 2,4 Ghz, 1 GB RAM, DVB-S Hauppauge WinTV Nexus-S rev 2.1, DVB-T Terratec Cinergy 1400, telecomando Terratec
Case: Compaq D510 SFF
Software: ArchLinux 0.8 Don't Panic, VDR 1.6.0-2 con Extension Patch v.62 (> 70 plugins in IT)
Hardware: Intel P4 2,4 Ghz, 1 GB RAM, DVB-S Hauppauge WinTV Nexus-S rev 2.1, DVB-T Terratec Cinergy 1400, telecomando Terratec
Case: Compaq D510 SFF
-
- Messaggi: 364
- Iscritto il: 23 ago 2007, 20:10
- Località: /dev/null
Re: Ancora problemi con il telecomando.
Eccomi, in questi giorni ho avuto un po' da fare.
[root@vdrbox ~]# cat /proc/bus/input/devices
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=mouse0 event0 ts0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7
I: Bus=0019 Vendor=0000 Product=0002 Version=0000
N: Name="Power Button (FF)"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=kbd event2
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button (CM)"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=kbd event3
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button (CM)"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/virtual/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=3
B: KEY=4000 0 0 0 0
I: Bus=0011 Vendor=0002 Product=0005 Version=0051
N: Name="ImPS/2 Logitech Wheel Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse1 event5 ts1
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=40001
B: SND=6
I: Bus=0001 Vendor=13c2 Product=0003 Version=0002
N: Name="DVB on-card IR receiver"
P: Phys=pci-0000:00:09.0/ir0
S: Sysfs=/devices/pci0000:00/0000:00:09.0/input/input7
U: Uniq=
H: Handlers=kbd event7
B: EV=100013
B: KEY=fc812 a052041 0 0 0 0 0 4000 40002800 1e1680 0 0 ffc
B: MSC=18
Posto anche udevinfo:
[root@vdrbox ~]# udevinfo -a -p $(udevinfo -q path -n /dev/input/event7)
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:09.0/input/input7/event7':
KERNEL=="event7"
SUBSYSTEM=="input"
DRIVER==""
ATTR{dev}=="13:71"
looking at parent device '/devices/pci0000:00/0000:00:09.0/input/input7':
KERNELS=="input7"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{modalias}=="input:b0001v13C2p0003e0002-e0,1,4,14,k71,72,73,74,8B,8D,9E,AE,160,166,16D,170,172,179,17B,181,184,18B,18E,18F,190,191,192,193,ram3,4,lsfw"
ATTRS{uniq}==""
ATTRS{phys}=="pci-0000:00:09.0/ir0"
ATTRS{name}=="DVB on-card IR receiver"
looking at parent device '/devices/pci0000:00/0000:00:09.0/input':
KERNELS=="input"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:09.0':
KERNELS=="0000:00:09.0"
SUBSYSTEMS=="pci"
DRIVERS=="dvb"
ATTRS{msi_bus}==""
ATTRS{broken_parity_status}=="0"
ATTRS{enable}=="1"
ATTRS{modalias}=="pci:v00001131d00007146sv000013C2sd00000003bc04sc80i00"
ATTRS{local_cpus}=="f"
ATTRS{irq}=="21"
ATTRS{class}=="0x048000"
ATTRS{subsystem_device}=="0x0003"
ATTRS{subsystem_vendor}=="0x13c2"
ATTRS{device}=="0x7146"
ATTRS{vendor}=="0x1131"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
Ho creato quindi /etc/udev/rules.d/10-local.rules in questo modo:
ATTRS{name}=="DVB on-card IR receiver", NAME="input/ir", SYMLINK+="input/rmctrl"
Seguendo il modello descrito qua'--->> http://vdr.spaghettilinux.org/index.php ... elecomando
è giusto?
[root@vdrbox ~]# cat /proc/bus/input/devices
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=mouse0 event0 ts0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7
I: Bus=0019 Vendor=0000 Product=0002 Version=0000
N: Name="Power Button (FF)"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=kbd event2
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button (CM)"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=kbd event3
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button (CM)"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/virtual/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=3
B: KEY=4000 0 0 0 0
I: Bus=0011 Vendor=0002 Product=0005 Version=0051
N: Name="ImPS/2 Logitech Wheel Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse1 event5 ts1
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=40001
B: SND=6
I: Bus=0001 Vendor=13c2 Product=0003 Version=0002
N: Name="DVB on-card IR receiver"
P: Phys=pci-0000:00:09.0/ir0
S: Sysfs=/devices/pci0000:00/0000:00:09.0/input/input7
U: Uniq=
H: Handlers=kbd event7
B: EV=100013
B: KEY=fc812 a052041 0 0 0 0 0 4000 40002800 1e1680 0 0 ffc
B: MSC=18
Posto anche udevinfo:
[root@vdrbox ~]# udevinfo -a -p $(udevinfo -q path -n /dev/input/event7)
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:09.0/input/input7/event7':
KERNEL=="event7"
SUBSYSTEM=="input"
DRIVER==""
ATTR{dev}=="13:71"
looking at parent device '/devices/pci0000:00/0000:00:09.0/input/input7':
KERNELS=="input7"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{modalias}=="input:b0001v13C2p0003e0002-e0,1,4,14,k71,72,73,74,8B,8D,9E,AE,160,166,16D,170,172,179,17B,181,184,18B,18E,18F,190,191,192,193,ram3,4,lsfw"
ATTRS{uniq}==""
ATTRS{phys}=="pci-0000:00:09.0/ir0"
ATTRS{name}=="DVB on-card IR receiver"
looking at parent device '/devices/pci0000:00/0000:00:09.0/input':
KERNELS=="input"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:09.0':
KERNELS=="0000:00:09.0"
SUBSYSTEMS=="pci"
DRIVERS=="dvb"
ATTRS{msi_bus}==""
ATTRS{broken_parity_status}=="0"
ATTRS{enable}=="1"
ATTRS{modalias}=="pci:v00001131d00007146sv000013C2sd00000003bc04sc80i00"
ATTRS{local_cpus}=="f"
ATTRS{irq}=="21"
ATTRS{class}=="0x048000"
ATTRS{subsystem_device}=="0x0003"
ATTRS{subsystem_vendor}=="0x13c2"
ATTRS{device}=="0x7146"
ATTRS{vendor}=="0x1131"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
Ho creato quindi /etc/udev/rules.d/10-local.rules in questo modo:
ATTRS{name}=="DVB on-card IR receiver", NAME="input/ir", SYMLINK+="input/rmctrl"
Seguendo il modello descrito qua'--->> http://vdr.spaghettilinux.org/index.php ... elecomando
è giusto?
VDRBox HD:
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
Re: Ancora problemi con il telecomando.
Prova a scrivere in questo modo la regola per udev:
Codice: Seleziona tutto
SYSFS{name}=="DVB on-card*", NAME="input/ir", SYMLINK+="input/rmctrl"
VDRBOX:
Software: ArchLinux 0.8 Don't Panic, VDR 1.6.0-2 con Extension Patch v.62 (> 70 plugins in IT)
Hardware: Intel P4 2,4 Ghz, 1 GB RAM, DVB-S Hauppauge WinTV Nexus-S rev 2.1, DVB-T Terratec Cinergy 1400, telecomando Terratec
Case: Compaq D510 SFF
Software: ArchLinux 0.8 Don't Panic, VDR 1.6.0-2 con Extension Patch v.62 (> 70 plugins in IT)
Hardware: Intel P4 2,4 Ghz, 1 GB RAM, DVB-S Hauppauge WinTV Nexus-S rev 2.1, DVB-T Terratec Cinergy 1400, telecomando Terratec
Case: Compaq D510 SFF
-
- Messaggi: 364
- Iscritto il: 23 ago 2007, 20:10
- Località: /dev/null
Re: Ancora problemi con il telecomando.
Fatto, purtroppo non risolvo.
lanciando invece manualmente,
cd /vdr/current
./vdr -Premote -Pskinsoppalusikka -c /etc/vdr/
il telecomando funge.
Mi sfugge qualcosa.....
lanciando invece manualmente,
cd /vdr/current
./vdr -Premote -Pskinsoppalusikka -c /etc/vdr/
il telecomando funge.
Mi sfugge qualcosa.....
VDRBox HD:
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
Re: Ancora problemi con il telecomando.
ma cosa intendi che da riga comando funziona , mentre da..., usi uno script per avviare vdr?
magari lo script non è corretto....
nello script prova così:
ciauz
magari lo script non è corretto....
nello script prova così:
Codice: Seleziona tutto
( cd /vdr/current ; ./vdr -Premote -Pskinsoppalusikka -c /etc/vdr/ )
VDRBOX: GA-K8NS, AMD Sempron 2600+, Hauppauge Nexus 2.1, LFS
-
- Messaggi: 364
- Iscritto il: 23 ago 2007, 20:10
- Località: /dev/null
Re: Ancora problemi con il telecomando.
Ciao, si uso lo script runvdr che posto per maggior chiarezza (prime righe che interessano):
VDRPRG="./vdr"
VDRCMD="$VDRPRG -w 60 -c /etc/vdr \
--shutdown='/etc/vdr/scripts/nvram.sh stop' \
--record='/etc/vdr/scripts/nvram.sh'
-Premote \
-Pskinenigmang \
-Pskinsoppalusikka \
"
non mi sembra sia differente. Eppure...
VDRPRG="./vdr"
VDRCMD="$VDRPRG -w 60 -c /etc/vdr \
--shutdown='/etc/vdr/scripts/nvram.sh stop' \
--record='/etc/vdr/scripts/nvram.sh'
-Premote \
-Pskinenigmang \
-Pskinsoppalusikka \
"
non mi sembra sia differente. Eppure...
VDRBox HD:
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
Re: Ancora problemi con il telecomando.
Per capire il problema servono altre info.
Se dal tuo script elimini la riga -Premote vdr si avvia?
Ciao
Se dal tuo script elimini la riga -Premote vdr si avvia?
Ciao
VDRBOX: GA-K8NS, AMD Sempron 2600+, Hauppauge Nexus 2.1, LFS
-
- Messaggi: 364
- Iscritto il: 23 ago 2007, 20:10
- Località: /dev/null
Re: Ancora problemi con il telecomando.
Sia con che senza -Premote vdr si avvia in automatico dopo aver acceso il pc.
Dimmi le info che servono e appena ho VDR sotto mano (domattina) le posto.
Ciao.
Dimmi le info che servono e appena ho VDR sotto mano (domattina) le posto.
Ciao.
VDRBox HD:
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
Re: Ancora problemi con il telecomando.
Lo script che esegui carica e scarica anche i moduli (driver) dvb?
Ciao
Ciao
VDRBOX: GA-K8NS, AMD Sempron 2600+, Hauppauge Nexus 2.1, LFS
-
- Messaggi: 364
- Iscritto il: 23 ago 2007, 20:10
- Località: /dev/null
Re: Ancora problemi con il telecomando.
Si. è praticamente quello descritto qui -->> http://vdr.spaghettilinux.org/index.php ... _ArchLinux
modificato solo per il lancio dei plugin remote, skinsoppalussika e skinenigmang.
VDRPRG="./vdr"
VDRCMD="$VDRPRG -w 60 -c /etc/vdr "
KILL="/usr/bin/killall -q -TERM"
# Detect whether the DVB driver is already loaded
# and return 0 if it *is* loaded, 1 if not:
function DriverLoaded()
{
if [ "`lsmod | grep dvb | wc -l`" -eq "0" ] ; then
return 1
else
return 0
fi
}
# Load all DVB driver modules needed for your hardware:
function LoadDriver()
{
modprobe dvb-ttpci
}
# Unload all DVB driver modules loaded in LoadDriver():
function UnloadDriver()
{
modprobe -r dvb-ttpci
}
modificato solo per il lancio dei plugin remote, skinsoppalussika e skinenigmang.
VDRPRG="./vdr"
VDRCMD="$VDRPRG -w 60 -c /etc/vdr "
KILL="/usr/bin/killall -q -TERM"
# Detect whether the DVB driver is already loaded
# and return 0 if it *is* loaded, 1 if not:
function DriverLoaded()
{
if [ "`lsmod | grep dvb | wc -l`" -eq "0" ] ; then
return 1
else
return 0
fi
}
# Load all DVB driver modules needed for your hardware:
function LoadDriver()
{
modprobe dvb-ttpci
}
# Unload all DVB driver modules loaded in LoadDriver():
function UnloadDriver()
{
modprobe -r dvb-ttpci
}
VDRBox HD:
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
Re: Ancora problemi con il telecomando.
Ho capito dove sta il problema, era la stessa cosa che succedeva a me!!!Ciao, si uso lo script runvdr che posto per maggior chiarezza (prime righe che interessano):
VDRPRG="./vdr"
VDRCMD="$VDRPRG -w 60 -c /etc/vdr \
--shutdown='/etc/vdr/scripts/nvram.sh stop' \
--record='/etc/vdr/scripts/nvram.sh'
-Premote \
-Pskinenigmang \
-Pskinsoppalusikka \
"
non mi sembra sia differente. Eppure...
Leggi bene qui:
http://vdr.spaghettilinux.org/index.php ... 2remote.22
Devi scrivere questo nel tuo script "runvdr":
Codice: Seleziona tutto
-P"remote -i /dev/input/ir"
VDRBOX:
Software: ArchLinux 0.8 Don't Panic, VDR 1.6.0-2 con Extension Patch v.62 (> 70 plugins in IT)
Hardware: Intel P4 2,4 Ghz, 1 GB RAM, DVB-S Hauppauge WinTV Nexus-S rev 2.1, DVB-T Terratec Cinergy 1400, telecomando Terratec
Case: Compaq D510 SFF
Software: ArchLinux 0.8 Don't Panic, VDR 1.6.0-2 con Extension Patch v.62 (> 70 plugins in IT)
Hardware: Intel P4 2,4 Ghz, 1 GB RAM, DVB-S Hauppauge WinTV Nexus-S rev 2.1, DVB-T Terratec Cinergy 1400, telecomando Terratec
Case: Compaq D510 SFF
-
- Messaggi: 364
- Iscritto il: 23 ago 2007, 20:10
- Località: /dev/null
Re: Ancora problemi con il telecomando.
Ok ragazzi, domattina ci provo e vediamo se con il vostro prezioso aiuto ce l'abbiamo fatta.
Intanto grazie.
Intanto grazie.
VDRBox HD:
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
-
- Messaggi: 364
- Iscritto il: 23 ago 2007, 20:10
- Località: /dev/null
Re: Ancora problemi con il telecomando.
Modificato lo script runvdr, VDR non parte più.
Con topVDR non è in esecuzione, non parte neanche in manuale con
./vdr -P'remote -i /dev/input/ir'-c /etc/vdr
dà il seguente errore:
[root@vdrbox current]# ./vdr -P'remote -i /dev/input/ir'-c /etc/vdr
vdr: error while reading '/video/sources.conf'
Che è il /video/sources.conf ?
Lanciandolo con ./vdr -Premote -c /etc/vdr VDR parte e iltelecomando funziona.
Con topVDR non è in esecuzione, non parte neanche in manuale con
./vdr -P'remote -i /dev/input/ir'-c /etc/vdr
dà il seguente errore:
[root@vdrbox current]# ./vdr -P'remote -i /dev/input/ir'-c /etc/vdr
vdr: error while reading '/video/sources.conf'
Che è il /video/sources.conf ?
Lanciandolo con ./vdr -Premote -c /etc/vdr VDR parte e iltelecomando funziona.
VDRBox HD:
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
HW: Asus P5N7A-VM (Nvidia 9300) + Intel Core 2 Duo E7500 2,93 Ghz + Kingston 2 Gb 800 Mhz ddr2 + 2X TT S2-3200 + Hauppauge WinTV MiniStick HD + WD Caviar Black 500 GB + WD Caviar Green 2 TB
SW: yaVDR64 0.5.0
Re: Ancora problemi con il telecomando.
Modifica lo script in questo modo:
VDRPRG="./vdr"
VDRCMD="$VDRPRG -w 60 -c /etc/vdr \
--shutdown='/etc/vdr/scripts/nvram.sh stop' \
--record='/etc/vdr/scripts/nvram.sh'
-Premote -i /dev/input/ir \
-Pskinenigmang \
-Pskinsoppalusikka \
"
Ora non ricordo bene la sintassi, quando sarò a casa controllo per vedere se è giusto. Intanto prova quella lì.
VDRPRG="./vdr"
VDRCMD="$VDRPRG -w 60 -c /etc/vdr \
--shutdown='/etc/vdr/scripts/nvram.sh stop' \
--record='/etc/vdr/scripts/nvram.sh'
-Premote -i /dev/input/ir \
-Pskinenigmang \
-Pskinsoppalusikka \
"
Ora non ricordo bene la sintassi, quando sarò a casa controllo per vedere se è giusto. Intanto prova quella lì.
VDRBOX:
Software: ArchLinux 0.8 Don't Panic, VDR 1.6.0-2 con Extension Patch v.62 (> 70 plugins in IT)
Hardware: Intel P4 2,4 Ghz, 1 GB RAM, DVB-S Hauppauge WinTV Nexus-S rev 2.1, DVB-T Terratec Cinergy 1400, telecomando Terratec
Case: Compaq D510 SFF
Software: ArchLinux 0.8 Don't Panic, VDR 1.6.0-2 con Extension Patch v.62 (> 70 plugins in IT)
Hardware: Intel P4 2,4 Ghz, 1 GB RAM, DVB-S Hauppauge WinTV Nexus-S rev 2.1, DVB-T Terratec Cinergy 1400, telecomando Terratec
Case: Compaq D510 SFF