Last week arrived to me new hard disk I ordered so I reinstalled my os.
My goal is to have a updated linux system which let me see vdr throw xineliboutput or xine. I have a Skystar 1 and a Hauppauge HVR4000.
I did many tests without any success: - Debian Sid 64 (problem with alsa and remote) - Archlinux 64 (problem with remote and no image throw xineliboutput) - Sidux 32 (problem with remote and no image throw xineliboutput)
I tried vdr version 1.7.0 and 1.7.7 with s2api driver.
I think my main problem is evdev and xorg: evdev let every device under /dev/input/event* input in X: this mean that remote controlled by HVR4000's ir can input directly to X. Someone knows how to tell evdev to skip a particular /dev/input/event* ? or how to disable evdev?
2009/5/22 Fabio Bordin fabio.bordin.81@gmail.com:
Someone knows how to tell evdev to skip a particular /dev/input/event* ? or how to disable evdev?
Configure vdr to not use keyboard input. Instead use the remote plugin which can be configured with a specific input device.
In general, there's no perfect distro for bleeding edge vdr at the moment, you'll need to compile most stuff.
Il 22/05/2009 09:32, Torgeir Veimo ha scritto:
2009/5/22 Fabio Bordinfabio.bordin.81@gmail.com:
Someone knows how to tell evdev to skip a particular /dev/input/event* ? or how to disable evdev?
Configure vdr to not use keyboard input. Instead use the remote plugin which can be configured with a specific input device.
My problem is that vdr and remote plugin wont configure at statup.
I explain better: Fresh install, I copy *.conf file from vdr source dir to video dir. There is no remote.conf file. I start vdr from vdr-source dir with this comman: "./vdr -P"xinelibpouput -p" -P"remote -i /dev/input/eventX" where eventX is the device i want to use to control my remote.
Vdr start but let me see only a black screen with "no signal"
No remote.conf created.
If I copy the remote.conf from xineliboutput's wiki, vdr let me use keyboard if I start without remote plugin. If I start with remote plugin vdr let me see only no-signal. Last night even without remote plugin, vdr did not want to let me see tv.
In general, there's no perfect distro for bleeding edge vdr at the moment, you'll need to compile most stuff.
check out the remote.conf file and see if the device is already configured. If it is already configured, will not ask to learn them again.
On 22/05/2009, Fabio Bordin fabio.bordin.81@gmail.com wrote:
Il 22/05/2009 09:32, Torgeir Veimo ha scritto:
2009/5/22 Fabio Bordin fabio.bordin.81@gmail.com fabio.bordin.81@gmail.com:
Someone knows how to tell evdev to skip a particular /dev/input/event* ? or how to disable evdev?
Configure vdr to not use keyboard input. Instead use the remote plugin which can be configured with a specific input device.
My problem is that vdr and remote plugin wont configure at statup.
I explain better: Fresh install, I copy *.conf file from vdr source dir to video dir. There is no remote.conf file. I start vdr from vdr-source dir with this comman: "./vdr -P"xinelibpouput -p" -P"remote -i /dev/input/eventX" where eventX is the device i want to use to control my remote.
Vdr start but let me see only a black screen with "no signal"
No remote.conf created.
If I copy the remote.conf from xineliboutput's wiki, vdr let me use keyboard if I start without remote plugin. If I start with remote plugin vdr let me see only no-signal. Last night even without remote plugin, vdr did not want to let me see tv.
In general, there's no perfect distro for bleeding edge vdr at the moment, you'll need to compile most stuff.
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Ok but if remote.conf don't exist or is empty it should start the learn process. My vdr with empty remote.conf or inexistent remote.conf DON'T start the learn process.
Something I missed to tell: every vdr is patched with zulu's extension patch.
Il 22/05/2009 10:03, Theunis Potgieter ha scritto:
check out the remote.conf file and see if the device is already configured. If it is already configured, will not ask to learn them again.
On 22/05/2009, *Fabio Bordin* <fabio.bordin.81@gmail.com mailto:fabio.bordin.81@gmail.com> wrote:
Il 22/05/2009 09:32, Torgeir Veimo ha scritto:2009/5/22 Fabio Bordin<fabio.bordin.81@gmail.com> <mailto:fabio.bordin.81@gmail.com>:Someone knows how to tell evdev to skip a particular /dev/input/event* ? or how to disable evdev?Configure vdr to not use keyboard input. Instead use the remote plugin which can be configured with a specific input device.My problem is that vdr and remote plugin wont configure at statup. I explain better: Fresh install, I copy *.conf file from vdr source dir to video dir. There is no remote.conf file. I start vdr from vdr-source dir with this comman: "./vdr -P"xinelibpouput -p" -P"remote -i /dev/input/eventX" where eventX is the device i want to use to control my remote. Vdr start but let me see only a black screen with "no signal" No remote.conf created. If I copy the remote.conf from xineliboutput's wiki, vdr let me use keyboard if I start without remote plugin. If I start with remote plugin vdr let me see only no-signal. Last night even without remote plugin, vdr did not want to let me see tv.In general, there's no perfect distro for bleeding edge vdr at the moment, you'll need to compile most stuff._______________________________________________ vdr mailing list vdr@linuxtv.org <mailto:vdr@linuxtv.org> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hello,
On Fri, May 22, 2009 at 09:29:04AM +0200, Fabio Bordin wrote:
Last week arrived to me new hard disk I ordered so I reinstalled my os.
My goal is to have a updated linux system which let me see vdr throw xineliboutput or xine. I have a Skystar 1 and a Hauppauge HVR4000.
I did many tests without any success:
- Debian Sid 64 (problem with alsa and remote)
- Archlinux 64 (problem with remote and no image throw xineliboutput)
- Sidux 32 (problem with remote and no image throw xineliboutput)
I tried vdr version 1.7.0 and 1.7.7 with s2api driver.
I think my main problem is evdev and xorg: evdev let every device under /dev/input/event* input in X: this mean that remote controlled by HVR4000's ir can input directly to X. Someone knows how to tell evdev to skip a particular /dev/input/event* ? or how to disable evdev?
You have to configure xorg with the option
Option "AutoAddDevices" "no"
in the ServerLayout section. This will force xorg no to add all evdev automaticly and you can (you must) configure them manually.
You must then add something like this:
Section "InputDevice" Identifier "Keyboard0" Driver "evdev" Option "XkbModel" "evdev" Option "XkbLayout" "de" Option "XkbVariant" "nodeadkeys" Option "Device" "/dev/input/by-id/usb-Dell_Dell_USB_Keyboard_Hub-event-kbd" Option "CoreKeyboard" EndSection
I have attached my xorg.conf as example. This is a multi seat setup with 2 independent video cards, 2 keyboards and 2 mouses.
Regards, Artem
My preference, and many guys I know are using Debian. Also a few Gentoo guys in there.
Gentoo
On 22/05/2009, Albert Gall ss3vdr@gmail.com wrote:
Gentoo.
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi,
On Fri, May 22, 2009 at 05:14:58PM +0200, Theunis Potgieter wrote:
Gentoo
On 22/05/2009, Albert Gall ss3vdr@gmail.com wrote:
Gentoo.
I am also using gentoo ;)
Regards, Artem
On Fri, May 22, 2009 at 05:14:58PM +0200, Theunis Potgieter wrote:
Gentoo
On 22/05/2009, Albert Gall ss3vdr@gmail.com wrote:
Gentoo.
I've used Fedora since 2004 and vdr-1.3.x
I demand that Diego Pierotto may or may not have written...
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html> <head>
[snip]
One with a patched Thunderbird/Icedove which refuses to send HTML mail or, failing that, complains loudly and annoyingly about it.
Fabio Bordin wrote:
I think my main problem is evdev and xorg: evdev let every device under /dev/input/event* input in X: this mean that remote controlled by HVR4000's ir can input directly to X. Someone knows how to tell evdev to skip a particular /dev/input/event* ? or how to disable evdev?
During this years VDR-CAMP I had the same problem while helping someone to setup an Ubuntu-based system with a HVR4000. Artem Makhutov already suggested a solution, but this one is a little bit less intrusive:
Create a file /etc/hal/fdi/preprobe/10-ignore-cx88-ir.fdi with the following content:
<?xml version="1.0" encoding="UTF-8"?> <deviceinfo version="0.2"> <device> <match key="info.product" contains_ncase="cx88 IR"> <merge key="info.ignore" type="bool">true</merge> </match> </device> </deviceinfo>
See also:
http://media.ubuntuusers.de/forum/attachments/1852900/devinput.html
Tobias
-
Albert Gall -
Artem Makhutov -
Darren Salt -
Diego Pierotto -
Fabio Bordin -
Simon Baxter -
Theunis Potgieter -
Tobi -
Torgeir Veimo -
VDR User