Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Users / Re: GSD issues - all devices died.
« Last post by mkbrown69 on August 29, 2015, 05:22:32 am »
Jason,

I commented out the stuff in my ISY driver's #350, and rebooted (a reload wasn't sufficient to restart the device.

It no longer segfaults. It loads all the GSD code, and then dies at the end, and tries to re-spawn.

Code: [Select]
1843:#### START SETTERS #############################################################
#######
1844:def initialize()
1845:super
1846:@returnParamArray=Array.new
1847:end
1848:####  END  SETTERS #############################################################
#######
1849:end
1851:Return code: 134
3       08/28/15 23:07:59       189 (spawning-device)   Device died... count=2/
50 dev=189
Fri Aug 28 23:07:59 EDT 2015 died
== ATTEMPT FRESH START ==
1       08/28/15 23:08:08       /usr/pluto/bin/Spawn_Device.sh 189 (spawning-device)15473 Dev: 189; Already Running list: 15,18,113,36,16,19,31,183,38,32,189,

1       08/28/15 23:08:08       /usr/pluto/bin/Spawn_Device.sh 189 (spawning-device)15473 Device 189 was marked as 'running'. Not starting
1       08/28/15 23:08:08       /usr/pluto/bin/Spawn_Device.sh 189 (spawning-device)15473 Dev: 189; Exiting because not starting


So, #350 does look to be the cause of the segfaults, but is not the only problem. My driver does use 350 for it's subscription feed from the ISY.

The CT30/CT80 only has a Conn_close() in #350, which probably isn't a issue to leave out. However, it also dies and res-spawns.
Code: [Select]
955:#### START SETTERS #############################################################
#######
 956:def initialize()
 957:super
 958:@returnParamArray=Array.new
 959:end
 960:####  END  SETTERS #############################################################
#######
 961:end
963:Return code: 134
3       08/28/15 23:07:47       183 (spawning-device)   Device died... count=1/
50 dev=183
Fri Aug 28 23:07:47 EDT 2015 died
========== NEW LOG SECTION ==========
1       08/28/15 23:07:57       183 (spawning-device)   Starting... 2
1       08/28/15 23:07:57       183 (spawning-device)   Found /usr/pluto/bin/Ge
neric_Serial_Device
RCODE:


Looks like you and Thom are closing in on it!

HTH!

/Mike
12
Installation issues / 10.04 installation issue - AVWizard
« Last post by jvandam87 on August 29, 2015, 02:35:40 am »
Hey all,

This is my first post here, and of course, it's because I'm having a problem.  Please bear with me as I'm not the most advanced computer guy out there. 

I recently decided to try to take my old desktop computer and repurpose it to use as a LinuxMCE hybrid.  Here's the specs on that computer, in case it's relevant:

CPU: Intel Pentium 4 2.8GHz
MoBo: Intel D915GUX
80 GB Hard Drive
3 Gig RAM
And I just recently upgraded it with an nVidia GT730 graphics card

I installed LinuxMCE version 10.04, and after rebooting, the AVWizard returned the error, "Failed to setup X."

I did some digging around the forum and found some old posting directing me to this page:

http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Add_ALSA_.24_Support

While my graphics card isn't listed on there, I assumed it would be similar to other nVidia cards, so I followed the same fix.  I entered the command screen and use the "sudo -I" command to work as root.  I then followed all of the commands to upgrade the Kernel to Natty.  Upon restart, the computer stops loading.  There's a lot of gibberish, but the last line is the following:

[Microsoft Microsoft Wireless Desktop Receiver 3.1] on USB-0000:00:1d.3-1/input1udevd-work[117]: '/sbin/modprobe -b pci:v000010DE0000F02sv00003842sd00002732bc03sc00i00' unexpected exit with status 0X0009

I assumed this had something to do with my wireless mouse and keyboard with the receiver plugged into the USB port.  So I unplugged that to see what would happen, and I restarted.  In this case I get a very similar message:

udevd-work[86]: '/sbin/modprobe -b pci:v000010DEd00000F02sv00003842sd00002732bc03sc00i00' unexpected exit with status 0X0009

At this point, I tried restarting several times hitting alt+F2 to re-enter the command mode, but either nothing happens at all, or I just get a black screen.  In any case, I'm unable to do anything further.

I then tried re-installing LinuxMCE 10.04.  This time, when I went to upgrade the Kernel to Natty, I also upgraded ALSA at the same time, but I ended up with the same problems.

I'm not really sure what to do at this point.  I'm not sure if I'm following outdated information, or there's something else I should try.  Any help would be much appreciated.

Thank you
13
Users / Re: Stopwatch / timer in events?
« Last post by posde on August 28, 2015, 10:35:56 pm »
More fixes. Thanks to the guys testing at IPTP I was able to squash a few more bugs. Updated binary is still at

http://deb.linuxmce.org/possy/eggtimer

Please report back.
14
Users / Re: Stopwatch / timer in events?
« Last post by posde on August 28, 2015, 10:31:12 am »
There has been an update to the binary, as well as to the device template.

You now have the ability to define a sensor to verify before turning OFF the device in question.

The way the egg timer works is:

* Send Start Egg Timer to the device with the parameters DeviceToLink (the light that will be turned on at the beginning), Timeout (the time after which the light will be turned off), VerifyStateDeviceID (the Device ID of the sensor that should be verified at the end of the timeout if it is tripped. If it is, the timer will be extended by the initial timeout.

* Send Cancel Egg Timer if you want to cancel the above timer before the end has been reached with a parameter defining if the OFF command should happen or not.

The reason for the new VerifyStateDeviceID are people that work the whole time, thus never stopping the motion sensor being tripped. Now it will continue to keep the light on.

Again, the binary is currently downloadable from http://deb.linuxmce.org/possy/eggtimer - and there is a small wiki page about it:

http://wiki.linuxmce.org/index.php/Egg_Timer

Feedback is appreciated.

PS: If you do not see the VerifyStateDeviceID when sending the Start Egg Timer command, make sure to sqlCVS upgrade the DCE repo.
15
Users / Changes to packages and install procedures, whew.
« Last post by phenigma on August 28, 2015, 06:15:45 am »
Hi all,

I hope that you are all enjoying LMCE as much as I tend to. I wanted to let everyone know about some pretty major changes that are occuring in the system.  This is meant both to inform and to solicit feedback as we go forward.

To date the LinuxMCE system has been a bit of a pain to install.  We have required an officilal installer script that you would run after installing ubuntu.  It has long been a goal of mine (and others) to remove this requirement and make the system install more like a normal ubuntu package.  Today we are very close to that.  I am working vigorously towards the ability to simply 'apt-get install lmce-blah'.  This allows us to more closely align with debian policies (something we want to do more of) and allows for easier integration into the ubuntu ecosystem.

I know that for some this could cause issues.  I, and others, hope to minimize any issues that might occur.  That doesn't mean that there won't be some 'growing pains' as we move forward.  We urge anyone that is testing on 1204 (or 1404 if you are really brave) to provide feedback.  IRC feedback is ideal but the forums here are a good place if you cannot access IRC.  If something is determined to be a proper bug (as is often the case) we will have you (or one of us) file a ticket in trac.  Trac is locked down for anonymous submits due to *massive* amounts of spam.  We still want your bug reports and would be very happy to grant trac access to submit tickets and information (code submissions are still relegated to devs only).

Going forward the plan is to support simple installation through normal apt procedures.  This would entail adding the lmce repo to the /etc/sources.list and then apt-get install blah package to install the remainder of LinuxMCE.  Tests are so far very successful and in the next day or two we will ask others to begin testing this procedure.  After that DVD installers will follow with the hopes that they too will work as easy (or easier) than they have been.

Many small install bugs are being squashed with regards to network setup and general installation.  Hopefully we can improve the setup further to reduce any issues that people may experience.  Some issues may be known, others not.

As always testing is really, really, appreciated.  Please follow: http://wiki.linuxmce.org/index.php/LinuxMCE-1204_pre-alpha for changes to LinuxMCE packages.

Happy LinuxMCE'ing!

J.

16
Users / Re: GSD issues - all devices died.
« Last post by phenigma on August 28, 2015, 05:43:37 am »
:( shitty.  Ok.  It was targeting a specific issue that tschak was having... And I thought it may relate.  That aside.  We think we've reduced it to #350 Process Incoming Data.  If there is any code in that section could you comment it out (#) and reload.  We *think* that's where our issues are coming from and may help us find a solution.

In most cases this fn is doing nothing at all.

Thanks for the feedback and the help narrowing things down!  We really appreciate the testing!  Let me know if there's anything else I can answer or help with.  We are trying to determine the ultimate cause, but it is proving quite elusive ;)

J.
17
Users / Re: GSD issues - all devices died.
« Last post by mkbrown69 on August 28, 2015, 05:05:41 am »
Jason,

Just to report back, your change in update 31133 did not resolve the problem. The devices still segfault the 50 times, then the screen session for the device is terminated.

Thanks for trying!

/Mike
18
Users / Re: Is it possible to host LinuxMCE on AWS?
« Last post by phenigma on August 27, 2015, 11:32:58 pm »
We do have the option of disk based mds that do not rely on nfs for full boot, only to share lmce dirs.  That being said, most comms go through the dcerouter (core) and everything the system does will be affected by that lag.

J.
19
Users / Re: apt-get upgrade problem
« Last post by phenigma on August 27, 2015, 11:31:11 pm »
ick, that'll prevent further upgrades.
20
Developers / Re: PHP to execute sudo command
« Last post by Govo on August 27, 2015, 11:13:31 pm »
Hi phenigma

No problem at all, I will try and hook up in IRC, it would great if the LMCE users went this, I am offer this for free when I am finish.

What I got done to day is added in the categories to database  and then allow them to be enabled through buttons,  tomorrow I will finish this section off so that it updates the DSG. this was  huge file to get in!

Check this short video clip.

https://www.dropbox.com/s/fdu4cakckxp5hrx/categories.mp4?dl=0

I have also found away to disable filtering and enable it again, but it brings me back visudo to get the command to executed, I go at that tomorrow.

Time to call it night for now  !


Cheers Gov



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