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 ... 76
16
Users / Re: rpi2
« on: March 22, 2015, 02:08:01 am »
I have not tested mythtv-player, nor built it for armhf.  I'll see about adding it to the builds.

J.

17
Developers / Re: Developing a Weather Plugin, videos
« on: March 22, 2015, 02:04:43 am »
If the icons will provide better information about weather conditions then I am happy to look at adding them to the skin pkgs. :D  Watch http://wiki.linuxmce.org/index.php/LinuxMCE-1204_pre-alpha and you'll know when things are ready.  Thanks guys!

J.

18
Installation issues / Re: CuBox-i from SolidRun
« on: March 22, 2015, 01:59:23 am »
Sounds good.  I'll see about rebuilding the armv7 build to ensure its' recent.

J.

19
Users / 1204/1404 HAL replacement !!! Please read!
« 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

20
Installation issues / Re: Pluto-vdr
« on: March 21, 2015, 01:44:52 am »
Can you post any error messages that you encountered?  Thanks!

J.

21
Developers / Re: Developing a Weather Plugin, videos
« 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.

22
Installation issues / Re: CuBox-i from SolidRun
« 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.

23
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.

24
Gogo your log shows two things:

1. you had a network connectivity problem to archive.ubuntu.com at some point during the installation
2. you ran out of memory for dpkg to use installing pkgs.  This is shown right at the end of the log.

J.

25
Installation issues / Re: CuBox-i from SolidRun
« on: March 17, 2015, 09:20:59 pm »
Diskless_Create will need to be altered/enhanced to build an armv7 trusty image.  The armv7 trusty packages first have to be in the repo, I've been intending to put them in but I have not gotten around to it yet.

U-Boot will have to be compiled specifically for our use as there are patches required for passing kernel boot parameters.

A default pxe-boot kernel/config will need to be placed in the /tftboot directory on the core.

A kernel for the cu-box (ideally in a packaged form) will also need to be available for the diskless image.

J.

26
When it finishes running again I'd appreciate it if you could pastebin the complete diskless_create log.  I have a feeling this is occuring simply becuase we haven't updated the packages in the 1404 main repo in a long time.  I will also try running it here as I have not run diskless_create on 1404 in a very long time.  We don't run it on the 1404 dvds atm either.

J.

27
Installation issues / Re: Problem with Kernel upgrade
« on: March 12, 2015, 03:49:10 pm »
You must run the dist-upgrade on the running MD.  I have not had any issues with dist-upgrading any of my MDs so I cannot re-create this.

The asterisk issues have not been seen before, sounds like a dkms issue with the dahdi components.  Without specific errors from the upgrade and following reboot I cannot speculate further.

J.

28
Developers / Re: Developing a Weather Plugin, videos
« on: March 10, 2015, 11:15:19 pm »
Code: [Select]
========== NEW LOG SECTION ==========
1       03/10/15 18:13:03       193 (spawning-device)   Starting... 2
1       03/10/15 18:13:03       193 (spawning-device)   Found /usr/pluto/bin/Weather
05      03/10/15 18:13:13.683           Weather: Config: NOAA <0xb6677700>
05      03/10/15 18:13:13.684           Weather: Use NOAA <0xb6677700>
05      03/10/15 18:13:13.684           Weather: Use NOAA language english <0xb6677700>
05      03/10/15 18:13:13.684           Weather: Use NOAA units 0 <0xb6677700>
05      03/10/15 18:13:13.684           Weather: Use NOAA Lat xx.xxx <0xb6677700>
05      03/10/15 18:13:13.684           Weather: Use NOAA Lon -xx.xxx <0xb6677700>
05      03/10/15 18:13:13.685           Weather: Starting Init Thread <0xb6677700>
05      03/10/15 18:13:13.686           Weather: Timer is set to: 3.000000 minutes <0xb6675b40>
05      03/10/15 18:13:13.690           Weather: Getting Weather Data using: NOAA <0xb54ffb40>
05      03/10/15 18:13:13.690           Weather: Inside use_NOAA <0xb54ffb40>
01      03/10/15 18:13:14.119           Get_NOAA: Failed to parse configuration <0xb54ffb40>

cfernandes this is the log output I am getting from Weather (lat/long removed).

J.

29
Users / Re: Pulse Eight HDMI CEC - Port?
« on: March 10, 2015, 11:08:06 pm »
Looks like the CEC adaptor is not communicating with libcec.  You can try to disable the CEC_Adaptor device in lmce, reload router and try connecting with cec-client.  If that doesn't work I'd look into it being a bad adaptor.

J.

30
Developers / Re: Developing a Weather Plugin, videos
« on: March 09, 2015, 11:48:42 pm »
So after DCEGen run I now get a new error.  Looks like an issue with the mutex calls.

Code: [Select]
(1204)root@1404builder:/var/lmce-build/svn/trunk/src/Weather# make clean
for dir in ; do cd $dir; make clean; cd ..; done
rm -f Main.o Weather.o ../Gen_Devices/WeatherBase.o NOAA.o WWO.o Main.d Weather.d ../Gen_Devices/WeatherBase.d NOAA.d WWO.d Weather Weather.so >/dev/null
(1204)root@1404builder:/var/lmce-build/svn/trunk/src/Weather# make bin | tee buildlog.txt
Computing dependencies for WWO.cpp done
Computing dependencies for NOAA.cpp done
Computing dependencies for ../Gen_Devices/WeatherBase.cpp done
Computing dependencies for Weather.cpp done
Computing dependencies for Main.cpp done
g++ -c -I.. -I../DCE -I/usr/include/mysql -DKDE_LMCE -DDEBUG -DTHREAD_LOG -DLOG_ALL_QUERIES  -Wall -fPIC -ggdb3  Main.cpp -o Main.o
g++ -c -I.. -I../DCE -I/usr/include/mysql -DKDE_LMCE -DDEBUG -DTHREAD_LOG -DLOG_ALL_QUERIES  -Wall -fPIC -ggdb3  Weather.cpp -o Weather.o
Weather.cpp: In constructor 'DCE::Weather::Weather(int, std::string, bool, bool, DCE::Router*)':
Weather.cpp:45:83: error: no matching function for call to 'pluto_pthread_mutex_t::pluto_pthread_mutex_t()'
Weather.cpp:45:83: note: candidates are:
../PlutoUtils/MultiThreadIncludes.h:112:2: note: pluto_pthread_mutex_t::pluto_pthread_mutex_t(std::string, bool)
../PlutoUtils/MultiThreadIncludes.h:112:2: note:   candidate expects 2 arguments, 0 provided
../PlutoUtils/MultiThreadIncludes.h:101:7: note: pluto_pthread_mutex_t::pluto_pthread_mutex_t(const pluto_pthread_mutex_t&)
../PlutoUtils/MultiThreadIncludes.h:101:7: note:   candidate expects 1 argument, 0 provided
Weather.cpp:45:83: error: no matching function for call to 'pluto_pthread_mutex_t::pluto_pthread_mutex_t()'
Weather.cpp:45:83: note: candidates are:
../PlutoUtils/MultiThreadIncludes.h:112:2: note: pluto_pthread_mutex_t::pluto_pthread_mutex_t(std::string, bool)
../PlutoUtils/MultiThreadIncludes.h:112:2: note:   candidate expects 2 arguments, 0 provided
../PlutoUtils/MultiThreadIncludes.h:101:7: note: pluto_pthread_mutex_t::pluto_pthread_mutex_t(const pluto_pthread_mutex_t&)
../PlutoUtils/MultiThreadIncludes.h:101:7: note:   candidate expects 1 argument, 0 provided
Weather.cpp: In constructor 'DCE::Weather::Weather(DCE::Command_Impl*, DCE::DeviceData_Impl*, DCE::Event_Impl*, DCE::Router*)':
Weather.cpp:55:65: error: no matching function for call to 'pluto_pthread_mutex_t::pluto_pthread_mutex_t()'
Weather.cpp:55:65: note: candidates are:
../PlutoUtils/MultiThreadIncludes.h:112:2: note: pluto_pthread_mutex_t::pluto_pthread_mutex_t(std::string, bool)
../PlutoUtils/MultiThreadIncludes.h:112:2: note:   candidate expects 2 arguments, 0 provided
../PlutoUtils/MultiThreadIncludes.h:101:7: note: pluto_pthread_mutex_t::pluto_pthread_mutex_t(const pluto_pthread_mutex_t&)
../PlutoUtils/MultiThreadIncludes.h:101:7: note:   candidate expects 1 argument, 0 provided
Weather.cpp:55:65: error: no matching function for call to 'pluto_pthread_mutex_t::pluto_pthread_mutex_t()'
Weather.cpp:55:65: note: candidates are:
../PlutoUtils/MultiThreadIncludes.h:112:2: note: pluto_pthread_mutex_t::pluto_pthread_mutex_t(std::string, bool)
../PlutoUtils/MultiThreadIncludes.h:112:2: note:   candidate expects 2 arguments, 0 provided
../PlutoUtils/MultiThreadIncludes.h:101:7: note: pluto_pthread_mutex_t::pluto_pthread_mutex_t(const pluto_pthread_mutex_t&)
../PlutoUtils/MultiThreadIncludes.h:101:7: note:   candidate expects 1 argument, 0 provided
make: *** [Weather.o] Error 1

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