Closed cdwijs closed 10 years ago
I spoke too soon. There already is a repository armv7h. I only needed to add the following to /etc/pacman.conf, and run pacman -Sy:
[vdr4arch] SigLevel = PackageRequired Server = http://creimer.net/vdr4arch/repos/vdr4arch/os/armv7h/
The following link lists all architectures, currently arm, armv6h, armv7h, i686, x86_64: http://creimer.net/vdr4arch/repos/vdr4arch/os/
Kind regards, Cedric
Yes, I fixed the Server= line in README.md. As I wrote in your other Bug. README.md is outdated and I could really need someone to update it and/or finish the translation of the wiki page.
Hi, I have just finished the English translation, except the words I didn't understand. For Debian, I have created a complete manual, to watch digitenne in the Netherlands. I would like to add that information to this wiki, ported to arch linux and vdr4arch Is it OK when I use the same chapters? My manual is here: https://wiki.debian.org/VDR Kind regards, Cedric ----Origineel Bericht---- Van : notifications@github.com Datum : 17/08/2014 10:21 Aan : vdr4arch@noreply.github.com Cc : cedric.dewijs@telfort.nl Onderwerp : Re: [vdr4arch] armv7h repro for allwinner A20? (#60) Yes, I fixed the Server= line in README.md. As I wrote in your other Bug. README.md is outdated and I could really need someone to update it and/or finish the translation of the wiki page. — Reply to this email directly or view it on GitHub.
Wow. That was fast. I just looked over it. Some parts of the German wiki site were missing. I translated them on my own now.
About the wiki additions: Wow, this is huge... But well, feel free to add it here. Good documentation is never wrong.
I tried to enable xineliboutput. The configuration file needs some work: [root@alarm vdr]# cd /etc/vdr/conf.d [root@alarm conf.d]# systemctl stop vdr [root@alarm conf.d]# ln -s ../conf.avail/50-xineliboutput.conf . [root@alarm conf.d]# ls -l total 8 -rw-r--r-- 1 root root 4478 Aug 7 2014 10-vdr.conf lrwxrwxrwx 1 root root 35 Dec 31 17:10 50-xineliboutput.conf -> ../conf.avail/50-xineliboutput.conf [root@alarm conf.d]# systemctl start vdr This is what I see in /var/log/everything.log: Dec 31 17:10:43 alarm vdr: [349] starting plugin: xineliboutput Dec 31 17:10:43 alarm vdr: [362] [vdr-sxfe] sxfe_display_open: failed to connect to X server (0.0) Dec 31 17:10:43 alarm vdr: [362] [vdr-sxfe] sxfe_display_open: failed to connect to X server (:0.0) Dec 31 17:10:43 alarm vdr: [362] [vdr-sxfe](ERROR %28xine_sxfe_frontend.c,1386%29: Connection refused) Dec 31 17:10:43 alarm vdr: [362] [vdr-sxfe] sxfe_display_open: failed to connect to X server (127.0.0.1:0.0 Dec 31 17:10:43 alarm vdr: [362] [vdr-sxfe](ERROR %28xine_sxfe_frontend.c,1391%29: Connection refused) Dec 31 17:10:43 alarm vdr: [362] [vdr-sxfe] sxfe_display_open: failed to connect to X server. Dec 31 17:10:43 alarm vdr: [362] [vdr-sxfe](ERROR %28xine_sxfe_frontend.c,1395%29: Connection refused) Dec 31 17:10:43 alarm vdr: [362] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window Dec 31 17:10:43 alarm vdr: [362] [xine..put] cXinelibLocal: Error initializing display Dec 31 17:10:43 alarm vdr: [362] [xine..put] cXinelibLocal::Action: thread finished Dec 31 17:10:44 alarm vdr: [349] [xine..put] cXinelibDevice::Start(): Local frontend init failed Dec 31 17:10:44 alarm vdr: [349] [xine..put] cXinelibOsdProvider: shutting down ! Dec 31 17:10:47 alarm vdr: [349] deleting plugin: xineliboutput Dec 31 17:10:47 alarm vdr: [349] exiting, exit code 2 The config file:
[xineliboutput]
Regards, Cedric ----Origineel Bericht---- Van : notifications@github.com Datum : 19/08/2014 11:19 Aan : vdr4arch@noreply.github.com Cc : cedric.dewijs@telfort.nl Onderwerp : Re: [vdr4arch] armv7h repro for allwinner A20? (#60) Wow. That was fast. I just looked over it. Some parts of the German wiki site were missing. I translated them on my own now. About the wiki additions: Wow, this is huge... But well, feel free to add it here. Good documentation is never wrong. — Reply to this email directly or view it on GitHub.
I have just read the VDR article on the arch linux wiki. After installing the packets, no configuration files have to be altered to use xineliboutput with VDR. https://wiki.archlinux.org/index.php/VDR Why didn't you package the default configuration files?
Kind regards, Cedric
I have obtained the xineliboutput.conf by executing the PKGCONFIG from archvdr: svn co https://svn.code.sf.net/p/archvdr/code archvdr The working configuration is:
[xineliboutput]
--local=none
--primary
/var/log/everything.org is: Aug 19 12:29:15 alarm vdr: [2374] initializing plugin: xineliboutput (1.1.0): X11/xine-lib output plugin Aug 19 12:29:15 alarm vdr: [2374] setting primary device to 1 Aug 19 12:29:15 alarm vdr: [2374] device 1 has no MPEG decoder Aug 19 12:29:15 alarm vdr: [2374] trying device number 4 instead Aug 19 12:29:15 alarm vdr: [2374] setting primary device to 4 Aug 19 12:29:15 alarm vdr: [2374] SVDRP listening on port 6419 Aug 19 12:29:15 alarm vdr: [2374] setting current skin to "lcars" Aug 19 12:29:15 alarm vdr: [2374] loading /var/lib/vdr/themes/lcars-default.theme Aug 19 12:29:15 alarm vdr: [2374] starting plugin: xineliboutput Aug 19 12:29:15 alarm vdr: [2374] switching to channel 1 Aug 19 12:29:15 alarm vdr: [2374] info: Channel not available!
Please update this config file in you package. Kind regards, Cedric
I have a working xineliboutput now. Needed configuration: cat /etc/vdr/50-xineliboutput.conf [xineliboutput]
--local=none
--remote=37890
--primary
Connect with
Now a graphical screen with "no signal" comes up as expected.
Please also add the following file to the package: /var/lib/vdr/plugins/xineliboutput/allowed_hosts.conf
I have u[dated the wiki to reflect above changes
The remote.conf was wrong. There were too many entries which are not necessary. Only XKeySyms makes sense. I think even XKeySyms doesn't make sense. If remote.conf is empty VDR starts up with a remote learning dialog.
For changes to PKGBUILDs please create a pull request.
OK. I looked over it again. Sorry, but as far as I know it's just wrong now.
Standalone-VDR means: No Client/Server! The plugin is in local mode. remote mode is disabled. Client/Server means: Two machines one server with plugin in remote mode and one client with vdr-sxfe or vdr-fbfe.
Please think before changing anything on the wiki...
I have an allwinner A20 running arch linux. Would you consider building the packages for this architecture?
Kind regards, Cedric
hardware: http://linux-sunxi.org/Olimex_A20-OLinuXino-Micro [root@alarm ~]# pacman -S vdr error: failed to prepare transaction (package architecture is not valid) :: package vdr-2.0.6-8-x86_64 does not have a valid architecture [root@alarm ~]# uname -a Linux alarm 3.4.90+ #3 SMP PREEMPT Sun Aug 17 00:11:36 MDT 2014 armv7l GNU/Linux [root@alarm ~]# cat /proc/cpuinfo Processor : ARMv7 Processor rev 4 (v7l) processor : 0 BogoMIPS : 811.21
processor : 1 BogoMIPS : 813.99
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 4
Hardware : sun7i Revision : 0000 Serial : 0000000000000000