root@ampit:~# sudo aptitude update
Hit http://mirrordirector.raspbian.org jessie InRelease
Hit http://mirrordirector.raspbian.org wheezy InRelease
Ign http://debian.bedroomlan.org unstable InRelease
Ign http://debian.bedroomlan.org unstable Release.gpg
Hit http://debian.bedroomlan.org unstable Release
Ign http://debian.bedroomlan.org unstable/non-free Sources/DiffIndex
Ign http://debian.bedroomlan.org unstable/contrib Sources/DiffIndex
Get: 1 http://mirrordirector.raspbian.org jessie/main armhf Packages [8,963 kB]
Get: 2 http://mirrordirector.raspbian.org wheezy/main Sources [6,081 kB]
Ign http://mirrordirector.raspbian.org jessie/main Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/main Translation-en
Get: 3 http://debian.bedroomlan.org unstable/non-free Sources [20 B]
Get: 4 http://debian.bedroomlan.org unstable/contrib Sources [20 B]
Err http://debian.bedroomlan.org unstable/main armhf Packages
404 Not Found [IP: 2a01:348:293::bed:1 80]
Err http://debian.bedroomlan.org unstable/non-free armhf Packages
404 Not Found [IP: 2a01:348:293::bed:1 80]
Err http://debian.bedroomlan.org unstable/contrib armhf Packages
404 Not Found [IP: 2a01:348:293::bed:1 80]
Ign http://debian.bedroomlan.org unstable/contrib Translation-en_GB
Ign http://debian.bedroomlan.org unstable/contrib Translation-en
Ign http://debian.bedroomlan.org unstable/main Translation-en_GB
Ign http://debian.bedroomlan.org unstable/main Translation-en
Ign http://debian.bedroomlan.org unstable/non-free Translation-en_GB
Ign http://debian.bedroomlan.org unstable/non-free Translation-en
Fetched 4 B in 31s (0 B/s)
W: Failed to fetch http://debian.bedroomlan.org/debian/dis ... f/Packages: 404 Not Found [IP: 2a01:348:293::bed:1 80]
W: Failed to fetch http://debian.bedroomlan.org/debian/dis ... f/Packages: 404 Not Found [IP: 2a01:348:293::bed:1 80]
W: Failed to fetch http://debian.bedroomlan.org/debian/dis ... f/Packages: 404 Not Found [IP: 2a01:348:293::bed:1 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
E: Couldn't rebuild package cache
I think the error means there is nothing for the rpi2 soc cpu hw and I must compile evrouter from source. Not sure tho !?! Will try the compile from source approach to make evrouter program.
Since program is on github I basically started from scratch and followed the process to install a program from github tutorial I found on the web. After reading that it took awhile but was straight forward. I should post a how to if I can easily use evrouter to allow usb devices to control Volumio thru redirecting their keyed inputs to shell mpc commands.
OK I have the program erouter compiled. I went the github, git-clone, repository approach to the open source program.
However, seems I broke Volumio in the process of compiling, linking and loading evrouter. All those php make file prompts I guess have to answered a certain way. I will try and address this later once I have a working piece of hw and evrouter running together.
Seems the problem now with running evrouter on the Volumio node is the lack of X11 display name. Have been some what successful in running evrouter in xvfb-run, with the command:
Yes good feedback. For a headless Volumio 1.55 system I had to run xvfb-run (had to install allot of X org stuff) and ran evrouter with that command that required X.
Don’t know if a xterm login is another way to keep X up in a headless operation. Your question remains whether using evrouter or using the xev / xbindkeys approach. As X is used in special Linux box headless numerical controllers I will ask this question in a Linux forum. Possibly an xterm login script would keep X up for key redirecting running healess? Otherwise just running any X daemon job with xvfb-run would keep X active for key redirecting.
I have another rpi2 so I was thinking of just putting full and current Raspbian on the rpi2 and investigate the xev with xbindkeys config file approach to investigate these issues. If it works then we can see if / how to resolve on to of Volumio.
I know the X org stuff takes up SD card space and rpi cpu cycles to run it all the time. However, sd card capacity is huge now and the rpi2 is so powerful. When I run Volumio 1.55 with a HiFiberry Amp+ board I never see CPU utilization much more that 10% running top.
