Hello,
I'm trying to get softdevice working. Compilation went well (vdr-1-3-31), but starting
vdr-daemon --config=/var/lib/vdr --lib=/usr/lib/vdr/plugins -d -l 3 -p 2001 --video=/video -w 60 -u vdr -g vdr -P remote -P "softdevice -L /usr/lib/vdr/plugins -vo xv:"
gives me:
Nov 12 21:03:50 linux vdr[10465]: probing /dev/dvb/adapter0/frontend0 Nov 12 21:03:51 linux vdr[10465]: found 1 video device Nov 12 21:03:51 linux vdr[10465]: initializing plugin: remote (0.3.3): Remote control Nov 12 21:03:51 linux vdr[10465]: initializing plugin: softdevice (0.2.0): A software emulated MPEG2 device Nov 12 21:03:51 linux vdr[10465]: tuner on device 1 thread started (pid=10465, tid=-1220461648) Nov 12 21:03:51 linux vdr[10465]: Section handler thread started (pid=10465, tid=-1228850256) Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: patch version (2005-07-20) Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: Could not connect to X-server Nov 12 21:03:51 linux vdr[10465]: [softdevice] videoOut failure exiting
I put LoadModule "XvMC" in xorg.conf as mentioned in the plugin's README, and libxvmc1 and libxvmc-dev are installed.
I guess it could be that I have to put up an additional screen-section in xorg.conf, but I'm not really familiar with that. Or does that error derive from s.th. totally different?
Any help is greatly appreciated! André
On Samstag, 12. November 2005 21:12, Andre Bischof wrote:
Hello,
I'm trying to get softdevice working. Compilation went well (vdr-1-3-31), but starting
vdr-daemon --config=/var/lib/vdr --lib=/usr/lib/vdr/plugins -d -l 3 -p 2001 --video=/video -w 60 -u vdr -g vdr -P remote -P "softdevice -L /usr/lib/vdr/plugins -vo xv:"
gives me:
Nov 12 21:03:50 linux vdr[10465]: probing /dev/dvb/adapter0/frontend0 Nov 12 21:03:51 linux vdr[10465]: found 1 video device Nov 12 21:03:51 linux vdr[10465]: initializing plugin: remote (0.3.3): Remote control Nov 12 21:03:51 linux vdr[10465]: initializing plugin: softdevice (0.2.0): A software emulated MPEG2 device Nov 12 21:03:51 linux vdr[10465]: tuner on device 1 thread started (pid=10465, tid=-1220461648) Nov 12 21:03:51 linux vdr[10465]: Section handler thread started (pid=10465, tid=-1228850256) Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: patch version (2005-07-20) Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: Could not connect to X-server
You have to start your X-server _before_ you may start vdr with softdevice and xv out.
For a client/server setup, you need streamdev plugin and connect your client via streamdev to your server.
Nov 12 21:03:51 linux vdr[10465]: [softdevice] videoOut failure exiting
I put LoadModule "XvMC" in xorg.conf as mentioned in the plugin's README, and libxvmc1 and libxvmc-dev are installed.
Which README ? README of softdevice does not mention xvmc, as it does not support xvmc.
I guess it could be that I have to put up an additional screen-section in xorg.conf, but I'm not really familiar with that. Or does that error derive from s.th. totally different?
Any help is greatly appreciated! André
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi,
Stefan Lucke wrote: ...
Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: patch version (2005-07-20) Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: Could not connect to X-server
You have to start your X-server _before_ you may start vdr with softdevice and xv out.
The output above is from a term in kde, so I suppose the X-server should be running.
For a client/server setup, you need streamdev plugin and connect your client via streamdev to your server.
Does that apply if client/server are running on the same machine?
But the error appears anyway, or do you mean it should vanish when using streamdev as additional plugin?
Nov 12 21:03:51 linux vdr[10465]: [softdevice] videoOut failure exiting
I put LoadModule "XvMC" in xorg.conf as mentioned in the plugin's README, and libxvmc1 and libxvmc-dev are installed.
Which README ? README of softdevice does not mention xvmc, as it does not support xvmc.
Arg, excuse me for mixing up info-sources, that one was from http://www.vdr-wiki.de/wiki/index.php/Softdevice-plugin
... Quasi-Hardwaredekodierung über XvMC ("XVideo Motion Compensation"), recht geringe CPU-Last (~30%, prozessorunabhängig).
Unter anderem unterstützt von NVidia Grafikkarten (GF4MX400 sowie >= GF5), S3 Unichrome (u.a. auf VIA Epia Boards) und vielleicht anderen, laden über option "XvMC" in XF86config, falls installiert (Distribution ^^^^^^^^^^^^^^^^^^^^ checken!) ...
=> if you don't speak german, this means that XvMC should be good for NVidia-cards and "XvMC" should be put in XF86config (or xorg.conf I suppose).
I'd like to use softdevice with a Geforce 6600 and TV-Out, if this could be better please tell me.
In vdr-wiki is also written that softdevice does replace the mpeg2-decoder and outputs directly on a framebuffer, output could then be on a monitor or tv-out (for that part streamdev is needed?)
I guess it could be that I have to put up an additional screen-section in xorg.conf, but I'm not really familiar with that. Or does that error derive from s.th. totally different?
Any help is greatly appreciated!
That's true furthermore :-) André
On Samstag, 12. November 2005 22:44, Andre Bischof wrote:
Hi,
Stefan Lucke wrote: ...
Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: patch version (2005-07-20) Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: Could not connect to X-server
You have to start your X-server _before_ you may start vdr with softdevice and xv out.
The output above is from a term in kde, so I suppose the X-server should be running.
So vdr is running with another userid as you are logged in. 1. you need to set th DISPLAY variable (export DISPLAY=:0.0) 2. the user who wants to access your display needs permissions to do that For my tests, when running vdr from root I do sux which keeps authorisation to x-server contact.
For a client/server setup, you need streamdev plugin and connect your client via streamdev to your server.
Does that apply if client/server are running on the same machine?
You can do this even on the same machine.
But the error appears anyway, or do you mean it should vanish when using streamdev as additional plugin?
If you want to use vdr as a frontend / desktop application you don't need streamdev.
I'd like to use softdevice with a Geforce 6600 and TV-Out, if this could be better please tell me.
In vdr-wiki is also written that softdevice does replace the mpeg2-decoder and outputs directly on a framebuffer, output could then be on a monitor or tv-out (for that part streamdev is needed?)
Streamdev if only needed for transferring the dvb data from one vdr to another.
Maybe that is of some help: http://www.linuxtv.org/pipermail/vdr/2005-October/005510.html
Hi Stefan,
Stefan Lucke wrote: ...
Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: patch version (2005-07-20) Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: Could not connect to X-server
You have to start your X-server _before_ you may start vdr with softdevice and xv out.
The output above is from a term in kde, so I suppose the X-server should be running.
So vdr is running with another userid as you are logged in.
- you need to set th DISPLAY variable (export DISPLAY=:0.0)
- the user who wants to access your display needs permissions to do that For my tests, when running vdr from root I do sux which keeps authorisation to x-server contact.
I can't manage to do that. If I try to run vdr as user root, vdr-kbd complains to refuse to run with root priviledges. If I do "su vdr" whoami tells me to be still root - is that what you meant by "sux"? Because I don't know sux, and nothing like this is installed.
I tried: root@linux:/usr/lib/vdr# DISPLAY=:0.0;xset s off;vdr-daemon --config=/var/lib/vdr --lib=/usr/lib/vdr/plugins -d ib/vdr/plugins -vo xv:" -u vdr -g vdr Xlib: connection to ":0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key xset: unable to open display ":0.0"
as mentioned in the link you provided at the end of your posting.
BTW, is "-vo xv:" right for me? I couldn't find anything about XvMC, or should I better use xv with my graca, which uses v4l if I'm not completly wrong?
...
If you want to use vdr as a frontend / desktop application you don't
Glad to here that, so I didn't understand everything wrong ;-) That's exactly what I intend to do.
I'd like to use softdevice with a Geforce 6600 and TV-Out, if this could be better please tell me.
In vdr-wiki is also written that softdevice does replace the mpeg2-decoder and outputs directly on a framebuffer, output could then be on a monitor or tv-out (for that part streamdev is needed?)
Streamdev if only needed for transferring the dvb data from one vdr to another.
Maybe that is of some help: http://www.linuxtv.org/pipermail/vdr/2005-October/005510.html
So I think my main problem is exporting the display right. For the time being I've only one display, no tv-out, which I would experiment with later on, when the rest is running.
But I'm not used to exporting displays and don't know how to manage it for the user vdr - do you still have the patience helping me again?
André
I demand that Andre Bischof may or may not have written...
Stefan Lucke wrote: ...
[snip]
So vdr is running with another userid as you are logged in.
- you need to set th DISPLAY variable (export DISPLAY=:0.0)
- the user who wants to access your display needs permissions to do that For my tests, when running vdr from root I do sux which keeps authorisation to x-server contact.
I can't manage to do that. If I try to run vdr as user root, vdr-kbd complains to refuse to run with root priviledges.
ITYM "complains, refusing" (unless there's something called "refuse" to which it is complaining).
If I do "su vdr" whoami tells me to be still root - is that what you meant by "sux"? Because I don't know sux, and nothing like this is installed.
My guess is that user vdr's default shell is /bin/false.
# su - vdr -s /bin/bash
[snip]
Xlib: connection to ":0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key xset: unable to open display ":0.0"
[snip]
I'm not used to exporting displays and don't know how to manage it for the user vdr - do you still have the patience helping me again?
Hack: as root, copy ~$USER/.Xauthority into ~vdr.
Proper method: set user vdr's shell to /bin/sh and password to something appropriate, then connect using "ssh -X vdr@localhost". You'll probably want to set things up so that vdr is automatically started on login.
On Sun, 2005-11-13 at 19:56 +0000, Darren Salt wrote:
I demand that Andre Bischof may or may not have written...
Stefan Lucke wrote: ...
[snip]
So vdr is running with another userid as you are logged in.
- you need to set th DISPLAY variable (export DISPLAY=:0.0)
- the user who wants to access your display needs permissions to do that For my tests, when running vdr from root I do sux which keeps authorisation to x-server contact.
I can't manage to do that. If I try to run vdr as user root, vdr-kbd complains to refuse to run with root priviledges.
ITYM "complains, refusing" (unless there's something called "refuse" to which it is complaining).
If I do "su vdr" whoami tells me to be still root - is that what you meant by "sux"? Because I don't know sux, and nothing like this is installed.
My guess is that user vdr's default shell is /bin/false.
# su - vdr -s /bin/bash
[snip]
Xlib: connection to ":0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key xset: unable to open display ":0.0"
[snip]
I'm not used to exporting displays and don't know how to manage it for the user vdr - do you still have the patience helping me again?
Hack: as root, copy ~$USER/.Xauthority into ~vdr.
Proper method: set user vdr's shell to /bin/sh and password to something appropriate, then connect using "ssh -X vdr@localhost". You'll probably want to set things up so that vdr is automatically started on login.
To me, using ssh seems like a hack.
IMHO, more correct is either:
1. Work out how to make su preserve Xauthority. (Distribution specific?) In particular use "su" not "su -"
2. Make sure ~$USER/.Xauthority is readable by the vdr user and do export XAUTHORITY=~$USER/.Xauthority
OR
3. As user do: xauth extract /tmp/key :0 As vdr user: xauth merge /tmp/key
OR (HACK)
4. ln -s ~$USER/.Xauthority ~/vdr And make sure vdr user can read the file
Anyway, this should give you the correct idea.
On Sonntag, 13. November 2005 19:41, Andre Bischof wrote:
Hi Stefan,
Stefan Lucke wrote: ...
Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: patch version (2005-07-20) Nov 12 21:03:51 linux vdr[10465]: [XvVideoOut]: Could not connect to X-server
You have to start your X-server _before_ you may start vdr with softdevice and xv out.
The output above is from a term in kde, so I suppose the X-server should be running.
So vdr is running with another userid as you are logged in.
- you need to set th DISPLAY variable (export DISPLAY=:0.0)
- the user who wants to access your display needs permissions to do that For my tests, when running vdr from root I do sux which keeps authorisation to x-server contact.
I can't manage to do that. If I try to run vdr as user root, vdr-kbd complains to refuse to run with root priviledges. If I do "su vdr" whoami tells me to be still root - is that what you meant by "sux"? Because I don't know sux, and nothing like this is installed.
Maybe sux is specific to SuSe.
I tried: root@linux:/usr/lib/vdr# DISPLAY=:0.0;xset s off;vdr-daemon --config=/var/lib/vdr --lib=/usr/lib/vdr/plugins -d ib/vdr/plugins -vo xv:" -u vdr -g vdr Xlib: connection to ":0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key xset: unable to open display ":0.0"
as mentioned in the link you provided at the end of your posting.
So as normal user you may grant access to your x-session via xhost command "xhost +host_name" .
-
Andre Bischof -
Darren Salt -
Malcolm Caldwell -
Stefan Lucke -
Ville Skyttä