Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - phenigma

Pages: 1 [2] 3 4 ... 117
Users / Re: hdmi cec control player
« on: November 30, 2018, 03:35:37 am »
The AV pipes are not automatically created for these devices.  For input switching to work you will also have to connect the AV pipes in the connection wizard.

Sent from my Pixel using Tapatalk

The way I have build LinuxMCE so far is through packer and vagrant

All my builds are in Virtual Box.  I have one builder with multiple chroots.  I also have an armhf builder (that I need to resurrect) as I need to get the RPi3+ booting.

Docker is probably the fastest method I have tried due to the least overhead

I'm very interested in exactly how you've got this setup and launching.

however compiling pthsem fails in the container.

Mhm.  Yup.

VirtualBox while working, is unusable in my opinion for the size of LinuxMCE. Qemu does work but takes a fair few hours to do a complete build on a quad core under kvm but does work great for compiling and providing a functional test environment in vagrant. To model a LinuxMCE network system, even OpenGL with virgl and networking between systems, netboot, disked md etc. I have found this invaluable tool to test LinuxMCE more. I have used lxc in the past but have not tested this path yet but will do so as these are lightweight like a chroot. VMWare and several others are possible.

QEmu == Ewww, I can agree with that.  Not sure if you're referring to automated 'modeling'/testing of distributed lmce network or the exact specifics.  All my 'live' testing has so far been done using VMWare or VirtualBox and snapshot systems to install/test/revert/repeat.

parallel building

Add 'NUM_JOBS=XX' to /etc/lmce-build/builder.custom.conf to set the number of cores used during the build.

There are obviously some packages that will need fixing due to this change too, some packages will fail when make is invoked as parallel. some linking methods are different, I think --as-needed flag, so some libs will need juggling around with the link ordering, this is where I stopped, I reverted it because I knew it would break trusty and time better spent elsewhere.

Using the above will avoid building anything that fails multi-core builds.

So anyway, back to the original answer a change like this would break pre bionic builds and the only way I see is another branch. Knowing how LinuxMCE deals with this would be useful to move foward.

This is something that needs to be looked into going forward, our current build system is outdated, but it's not as simple as in many projects due to the database system we rely on.

Another option was to look at way to remove pthsem with more updated software that depended on it but it looks like it's used by some core things I cannot test due to lack of knx/eib hardware so that isn't an option currently for me.

Most everything is sacred but the knx/eib stuff has to work.  Everything we do here is supported and enabled by someone that relies on knx and that must be maintained.  Oh... and VDR too ;)

can be made. At the moment I am looking at ways to get my database changes in using this method but I am not going to lie I am struggling with LinuxMCE as you can well imagine.

Right now database changes have to be made by one of a few devs, some that haven't been seen for a while.  Changes in mysql forced updates in sqlCVS that seem to have broken anonymous commits/approvals.  I can work with you to get things input if necessary.

I would like to know more about how you work and how this all fits because I do not want to interfere with current build methods, so I am trying to make this an extension if you like, a wrapper around the buildscripts. I would welcome and help with this I don't want to waste your time the only thing stopping me uploading at the moment is it being so rough and cutting corners but I hope to work these out.

Official builds are all produced on one machine for all i386 and X86_64 builds and all official armhf builds have been made on my armhf builder.  Essentially all our build scripts cater to this primary builder.  I've added lots of speed-ups and I skip many steps in the build process in my chroot environments but that depends on not destroying the environments and knowing how to reset those steps to occur, none of these things are documented anywhere.

P.S. While I think of it, I have just managed to install a hybrid in vagrant with the debs from, I got access the vm by disabling the firewall in /etc/pluto.conf with a hack in the Vagrantfile but this is hardly optimal so wondered if there was a way to enable ssh access by the cli after apt install lmce-mybrid. the firewall comes up and blocks access so i had to disable the firewall because I don't know how to enable programmatically, the outside ssh access in LinuxMCE settings to stick. Phew. Thanks!

The firewall is severely broken and you're best option is to disable it entirely.

Things are pretty quiet but you might try to join #linuxmce-devel on freenode irc.  I try to get on daily and if I'm around then it can be easier to converse and 'brain dump' ;)

Keep having fun!


Do you have any specific examples?  I'm not against this but we do try to maintain compatibility between versions as much as possible.  I work in private branches that get pushed to master once tested across the various versions we have.  There are times when things change enough that code diverges greatly (CEC Adaptor is one I can specifically identify as unable to remain backwards compatible as the libraries have updated.


Users / Re: hdmi cec control player
« on: November 18, 2018, 09:30:00 pm »
Yup, that's it.  I use multiple player templates.  Just be sure the port is set properly and commands should be routed accordingly.

Sent from my Pixel using Tapatalk

Users / Re: Adding zwave lights
« on: November 07, 2018, 07:58:34 pm »
I don't see why multiple zwave networks wouldn't work.  You would only include certain devices into each network and adjust the controlled by, as you say.  I've not known anyone to do this but it could work.

I think the raspberry pi zwave module is supported by openzwave, but it would not be auto detected by LMCE at this point as no one has attempted to use one that I know of.


Users / Re: Adding zwave lights
« on: November 07, 2018, 06:12:24 pm »
I'm glad you have managed to get things working.  I did start an upgrade to the zwave system some time ago but didn't complete it.  Once that is done the openzwave interface should have better knowledge of a lot more devices.


Users / Re: Adding zwave lights
« on: November 06, 2018, 06:58:18 pm »
That log is the path to it on the core.  You can check var/log/pluto/89_Light_Switchonoff.log on the MD or the initial location on the core for that log.

Users / Re: disk md
« on: October 20, 2018, 04:08:06 am »
And yes, please make a new page!

Sent from my Pixel using Tapatalk

Users / Re: disk md
« on: October 20, 2018, 04:01:20 am »
I haven't looked at the current network settings that come up on a disked md.  Some changes on networking recently have changed, specifically device names.  The old pages you reference are very old and do not reflect the way things are now.  NM is disabled because it caused many issues, if you have suggestions for solutions I'm open to them.  Keep having fun!

Sent from my Pixel using Tapatalk

Users / Re: disk md
« on: October 18, 2018, 05:02:04 pm »
That's the correct method, I don't think there are any specific instructions anywhere else right now.  Feel free to document your findings. 

Sent from my Pixel using Tapatalk

Users / Re: disk md
« on: September 27, 2018, 07:24:45 pm »
If I were in your shoes, I would just run the regular detection process, let it create everything, and move the stuff over to the HDD, and let it boot from the HDD instead of PXE. Might even work without a lot of manual configuration.

There is a process for installing disked MDs.

The specific way your wanting to interact is something I've wanted as well but not possible currently the way lmce deals with media.  Posde's solution is the best at the moment, put a copy of each picture you want shown in the public structure that lmce would create on your new share.  Or copy those pics to the picture folder on the core.  There is no way to differentiate media when ignoring a folder tree.  All or nothing is how it works when lmce indexes a share (depending on public/private structure on setup). 

Sent from my Pixel using Tapatalk

I would add the share as public and block update media from scanning the folders you don't want scanned. 

Sent from my Pixel using Tapatalk

Installation issues / Re: diskless creation error
« on: March 27, 2018, 09:28:42 pm »
looks like you had a repo error, the packages exist.

Feature requests & roadmap / Re: Integration of streaming sites?
« on: December 14, 2017, 09:10:45 am »
Hi to all, it has been a while... but just to do a little follow up on this, this was the route im using for more than a year.  I added chrome as new computing app also kodi.  Not using Kodi much to be honest, but Netflix I´m using it, well,  My wife and kids! are using it everyday.  I just need a bit more computing power on that MD in order to have better navigation (ZOTAC MAG) navigates bit slow netflix website but once the streaming starts, all is ok.  Navigation is done by wireless keyboard and mouse.  The onscreen keyboard is useless.

Wow!  Great stuff honestly I haven't tried Netflix this way and take should!

Sent from my Pixel using Tapatalk

Pages: 1 [2] 3 4 ... 117