Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Users / 1204/1404 HAL replacement !!! Please read!
« Last post by phenigma on March 21, 2015, 02:19:48 am »
Hey there LMCE'ers!   :o

A major change within the linux community has driven a need for a change to the hardware detection methods within the lmce smart home automation system.  This change will affect all users of LMCE1204 (Ubuntu Precise) and up, including the pre-pre-alpha LMCE1404 (Ubuntu Trusty).

The linux community dropped support for hald (the hal daemon) which provided hardware detection events and information to applications, including lmce, for many years.  This change happened about 4 years ago.  LMCE has been sheltered from the changes because Ubuntu has maintained support for hald through the 1204 LTS release.  As of Ubuntu 1404 LTS hald has been discontinued completely.

In order to maintain our level of automatic hardware detection, and ultimately improve it beyond its' current capabilities, hal detection is being replaced with udev based device detection with appropriate device detected/removed event notifications for dcerouter.

udev is the hardware event notification system that has replaced the hald (hal daemon) in the general linux community.  udev has been incorporated into the new systemd (system daemon) which is becoming the standard for boot managment and service launching under the linux kernel.  LMCE will also support systemd launching in the near future.

In the next few days we will be pushing an updated version of the HAL daemon that linuxmce uses to detect devices.  The HAL daemon was named for its interface to the hald.  The updated version of our HAL daemon will now interface with udev directly rather than hald.  The package in question is "pluto-hald".  At the moment the pkg name will not change to avoid issues with upgrades.  Eventually the package name will change to reflect the new "lmce-" package naming convention.

Once the update is deployed you will need to
Code: [Select]
apt-get update
apt-get dist-upgrade
your lmce core and MD devices to receive the new device detection system.  I am doing everything I can to mitigate issues that people may encounter during this upgrade process and I can offer the following observations so far:
  • Some devices may trigger the Setup Wizard to appear.  This is usually the Wizard confirming that the new device is actually the old device.  i.e.  My Zwave dongle is re-detected (due to changes in device identification) but recognizes that it is actually the old (original) device and simply requests confirmation of that fact.
  • GSD devices may need to have their serial ports reset (as they may be lost) and saved, followed by a router reload.  No issues have been observed after this with serial devices.

As always we ask you to remember that this is ongoing alpha software with very few developers contributing.  If you have any issues please file tickets in the trac system (contact posde in IRC for credentials).  Please watch http://wiki.linuxmce.org/index.php/LinuxMCE-1204_pre-alpha to follow changes to the 1204 development version, including when this change hits release.

Thanks everyone and enjoy LinuxMCE!

(J.)ason
72
Installation issues / Re: Pluto-vdr
« Last post by phenigma on March 21, 2015, 01:44:52 am »
Can you post any error messages that you encountered?  Thanks!

J.
73
Developers / Re: Developing a Weather Plugin, videos
« Last post by phenigma on March 21, 2015, 01:43:55 am »
 :D  You guys rock!  Let me know when things are tested enough for me to package it all up.  I've been super busy and haven't had a chance to do much testing with it beyond the earlier posts.

J.
74
Installation issues / Re: CuBox-i from SolidRun
« Last post by phenigma on March 21, 2015, 01:41:37 am »
yikes.  ok.  there's lots there to look at. 

  • u-boot, once setup correctly, will pick the proper default kernel from the tftpboot directory.
  • what distro of linux are you running? any arm version will require a proper build of lmce.(ubuntu 1404 armv7 is built but not pushed to the lmce repos)
  • If I can get specific instructions wrt the kernel then I can create a default kernel image for the device. (You may have provided these but there is a lot there to sort through.  :)
  • u-boot needs some patches which are written specific to the rpi version, I will need to alter them for the cubox (or more generically for many devices if I can, but I've only ever seen one so far ;-|  )  Can you provide specific references to the board and version to use with mainline u-boot?
  • the device tree files are becoming the standard method of differentiating hardware for non-i386/arm64 based systems.  u-boot can handle these for the most part but, again, I may need specifics.

I see there are kernel build instructions included, is there any other way to get the kernel?

Although I do not own one I do see the potential of these devices.  They are in-line with rpi2 specs and hdmi-cec is supported with libcec.  This makes is easy for us to support cec control as well.

I'm super occupied so I'm trying to be succinct, which may seem terse or short.  Not my intent.

You're doing some great investigations!  Let's get things to a point where we can actually boot a device!

In fact, we can ignore PXE booting completely for now if you can install ubuntu trusty on it somehow ;)  I can guide you through creating a disked MD that doesn't need u-boot and PXE booting for now.

J.
75
Installation issues / Re: Dependancy issues running Diskless_CreateTBZ.sh
« Last post by phenigma on March 21, 2015, 01:26:42 am »
Excellent!  I'm glad the issues worked themselves out with the extra RAM.  Keep in mind that 1404 is just on the cusp of being in a usable state.  There are items, like mythtv, which are not configured properly at the moment.  We need any and all help people are willing and able to provide.  Thanks for testing!

J.
76
Installation issues / Re: Pluto-vdr
« Last post by posde on March 20, 2015, 07:43:19 pm »
Check that vdr-plugin-streamdev-client and vdr-plugin-xineliboutput are installed on the moon.
77
Installation issues / Re: Pluto-vdr
« Last post by pointman87 on March 20, 2015, 07:38:51 pm »
The only info i got is in the attached syslog, seems like its something with the connection to sxfe

BR Daniel
78
Marketplace / Dianemo-RPi2 Preview Edition - for Raspberry Pi2 FAQ
« Last post by totallymaxed on March 20, 2015, 03:20:14 pm »
Q: Where will Dianemo-Rpi2 differ from existing Dianemo software?

Dianemo-Rpi2 will share considerable commonality of features with the current Dianemo software but there will also be many areas where we will take the opportunity to have a re-think of our approach. One such area is in the way that you create device templates and interconnect devices with other devices or aspects of the system. In Dianemo-Rpi2 we plan to have a visual editor fro creating/editing device templates (both code and screen layouts) and for how you decide the interconnections between a template instance and other devices too. We want to make that process visual rather than simply a matter of editing text files of code or settings. We will support traditional editing too but we want to make creating and using device templates and devices much more accessible to users and we think this visual approach, dragging elements onto the screen and then connecting their inputs/outputs and adding logic etc, will make customising and extending Dianemo-Rpi2 by non coders much more accessible.

I'm not sure this feature will be in place for the first release but we will release it asap.

Q: If I'm an existing Dianemo customer will I need a new license to get access to Dianemo-Rpi2?

Unless you have already been allocated a trial slot then yes you will need a new license. Dianemo-Rpi2 is our first ARM based product and will require a separate license to our current Dianemo X86 based product. The good news is that you can get a new ARM only license for a special $99 USD price currently.

Q: Will the current ARM only license price of $99 USD be available after you launch Dianemo-Rpi2?

The honest answer is we have not settled on our pricing yet for Dianemo-Rpi2. But we do see the current $99 USD price as a special introductory price prior to launch. So we would encourage you take advantage of this pricing now if your interested.

However whatever our eventual pricing is if you purchase your ARM only license now we will provide you with whatever features benefits we announce for Dianemo-Rpi2 at its launch - essentially you will be 'Grandfathered in'. So getting involved in the trial by purchasing an ARM license now will be a saving and will also get you any other benefits etc that we announce when we launch. So there is no risk to participating.

Q: How long will the current $99 USD ARM only license offer continue for?

The current ARM only license offer will only be available until we feel we have enough people for the trial testing period. So our advice is that if you want to participate in the trial or want an ARM based NC/Core then you should purchase an ARM only license soon.

Q: Will my Dianemo-Rpi2 license work with the final released version?

Yes it will. Any ARM only licenses purchased now are full licenses and will work as they should after we launch Dianemo-Rpi2.

Q: When will we receive the first preview release of Dianemo-Rpi2?

We are currently expecting to have the first builds ready for release to preview users in May 2015.

Q: Which OS will Dianemo-Rpi2 be compatible with?

Dianemo-Rp2 will ship on Raspian which is already ARMv7 compatible.

Q: What CODECS are available for the Rpi2?

Both the MPEG2 & VC-1 codecs are available for all models of the Rpi. The codecs can be purchased from here; http://swag.raspberrypi.org/collections/software

**Bare in mind you only need CODECS on RPi's that will be playing Video**

Q: Can I install Dianemo-Rpi2 on multiple SD cards?

Yes you can.  We've tried to make the license much less restrictive than previously. Each install will be associated with your License & details. With Dianemo-Rpi2 we allow you to install on multiple Rpi2's but they must be owned by you and be located at a single location as your license identifier will be on each install. You can also do a bootable image backup of you SD card to your PC's hardrive - this will enable you to restore to your SD card if you need to. You could even have multiple SD cards with a copy of Dianemo-Rpi2 on each that has different configurations - you might do this if you were experimenting with several configs or want to test different 3rd party hardware projects etc. The only limitation is that your license can only be installed on Rpi2's that are owned by you at a single location.

Q: Will Dianemo-Rpi2 support serial devices?

Yes we will support any USB serial adapters that are compatible with Rpi2. We will also support IP addressable serial servers/adapter such as the GC100 etc too.

Q: Will a Dianemo-Rpi2 Core/NC support a local MD & HDMI audio?

While the Rpi2 hardware will definitely support HDMI audio we do not currently plan to support MD functionality on the Core/NC itself. We don't think the performance will be adequate (we may revise this if tests prove performance is not a problem). But since adding another Rpi2 as an MD or as a UPnP Media player is simple and only costs an additional $35 USD we feel that’s an acceptable limitation.

Q: Will Dianemo-Rpi2 support MD's?

Yes we will but probably not at first release. We also will almost certainly not support PXE booted MD's for performance reasons - MD's will boot from a local SD card image. Our updater scripts will manage the updating of MD's automatically for you.

Q: What hardware will I need?

For your NC you will need a standard Raspberry Pi2 board and a compatible USB Gigabit NIC (you will need both a LAN side & WAN side NIC). Obviously a Raspberry Pi compatible case would also be a useful purchase and a suitable USB power supply (2500ma or greater rated if multiple USB ports used). A 32gb or larger Micro SD card will be needed for the OS and Dianemo firmware. All of these items can be purchased from any Raspberry Pi reseller.

For MD's you will need either a Rpib+ or Rpi2. No 2nd NIC required. Again a suitable case is not required but is probably a good idea and a USB power supply (2500ma or greater rated if multiple USB ports used). A 8gb or larger Micro SD card for the MD OS and Dianemo MD firmware.

Q: Will I be able to access the Rpi2 GPIO pins?

Yes absolutely. If the Rpi supports it we want to too. One of the many advantages of the Rpi platform is being able to use all the I/O on the board either directly for simple projects or by using any of the many Rpi expansion boards that are available.

Q: What kind of system can be built around Dianemo-Rpi2?

Because MD's (if you use them) will boot from local SD storage and only Athena based UI skins will be supported the average load on the system will be much lower than with existing NC's. There will also be other architectural changes that will improve performance on low power ARM hardware too. Add all these changes together and we are confident that a Dianemo-Rpi2 NC will be able to support an average sized house. Part of the testing process during the trial will be designed to measure performance capabilities for a range of system configurations.

Q: What expansion limitations will there be?

The Rpi2 obviously lacks PCie slots so any expansion in the NC will need to be achieved without requiring those. But it does have 40 GPIO pins and both DSI & CSI expansion connectors for all manner of add on hardware (it's full compatible with Rpi expansion boards Etc). We hope that many standard Rpi expansion boards/projects will be integrated into Dianemo-Rpi2 by both you guys and also by us. The Rpi2 also has 4x USB 2.0 ports (although we use one of those for the 2nd NIC). Adding audio/video media storage is easily handled by adding a low cost NAS (or multiple NAS's even) to your LAN for unlimited media storage. Ripping disc based media can be done from a PC or by adding a USB optical drive. So all in all there are few if any expansion limitations that cannot be easily worked around.

Q: How many MD/MM's will Dianemo-Rpi2 handle concurrently?

Since MD/MM's will boot from local SD storage and will stream media from LAN based storage like a NAS the load imposed on the NC will be considerably lower. Also there will be no UI's to regen which also removes a large overhead. So our expectation is that Dianemo-Rpi2 will handle these loads comfortably but until we have the Preview underway we can't provide a definitive answer. My feeling is that in reality this will not be a limiting factor for most users.

Q: Will Dianemo-Rpi2 support LMS and SqueezeSlaves?

Yes it will. Again as in the reply to the question re MD/MM's above we will need to test the limits of performance during the Preview. Clearly a Rpi2 Core will have a more limited capacity than a big Intel based Core but we expect for the vast majority of use cases this will not be a factor. For the most of the time our big Intel based Cores are barely being used and it's only during regens and PXE booting MM/MD's that there big processors are needed. So by removing these, and a few other performance hogging pieces of code, we can build a Core on Rpi2 that will perform well overall with far less hardware.



79
Users / Re: Dianemo Installation
« Last post by totallymaxed on March 20, 2015, 01:07:48 pm »
Glad we could help.

Andy
80
Marketplace / Dianemo Athena UI & iPhone Orbiter Preview Video
« Last post by totallymaxed on March 19, 2015, 04:17:52 pm »
I've just posted a short (and very rough!) video of new iPhone Athena UI & App in action. You can see it at the top of this page;

http://wp.me/P4KgIc-aF

I'll post more of these images as we debug both the App and the Responsive Athena UI Skin for iPhone.

All the best


Andy
[/quote]
Pages: 1 ... 6 7 [8] 9 10