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 - mkbrown69

Pages: 1 ... 8 9 [10] 11 12 13
136
Users / Re: MD idle shutdown?
« on: April 23, 2012, 03:52:31 pm »
Thanks for the pointers, guys!

I'll dig into it a bit further when I get a bit of free time.  I'll probably post a bash script I use in Minimyth to shutdown a slave backend, so if someone else decides to pursue this as well, they can take some of those factors into account (i.e. don't shutdown if recording/transcoding/commflagging, etc).

Thanks again!

/Mike


137
Users / MD idle shutdown?
« on: April 21, 2012, 01:28:00 am »
Good day folks!

I've noticed that when the core restarts, it wakes up the MD's.  Given that they stay running, I'm presuming that there isn't an idle shutdown/sleep function, correct?  I'm just trying to confirm that it doesn't have an idle shutdown;  if it does exist, then I'll have to figure out why it's not working...

I'm running 10.04.

Thanks for your time!

/Mike

138
Users / Re: Mythtv and HD-PVR control of cable box.
« on: April 09, 2012, 04:39:06 am »
Kramden,

There's a firmware issue on current versions of firmware for Linux.  The fix will end up in up in a 3.3 Kernel.  Take a good read of <http://www.mythtv.org/wiki/Index.php/Hauppauge_HD-PVR>.

Note this part in particular:

 Note: 29-Aug-2011: The latest version of the firmware, 1.6.29207, dated July 27, 2011, causes oversaturation and color issues with the encoding of the analog signal. Until this is resolved, you do not want to upgrade to this version. Version 1.5.7, from June 17, 2010 appears to work. Hauppauge has acknowledged the issue and provided a link to the earlier firmware for non-Windows systems on their support page: Hauppauge HD-PVR support
A patch has been submitted upstream to fix this issue and it has been merged into Linux kernel v3.3-rc5.

This appears to be the fix:

Until a patch that sets the new defaults is committed to the kernel, you can use v4l2-ctl --set-ctrl brightness=0x80 --set-ctrl contrast=0x40 --set-ctrl hue=0xf --set-ctrl saturation=0x40 --set-ctrl sharpness=0x80 to set the proper defaults.

You might be able to put that into a channel change script.

Hope that helps!

/Mike

139
Purps,

Assuming you want the core to manage QoS or traffic shaping, this might get you started.  You could always google for more specific examples related to SIP & VOIP or RTP/RTSP protocols.

http://tldp.org/HOWTO/Traffic-Control-HOWTO/

HTH!

/Mike

140
Users / Re: A Split
« on: April 03, 2012, 06:50:04 pm »
hopefully, you verify your numbers in your day job better than you do in this forum... SCNR

We do not have a stable 804 release, but a stable 810 :P

Mea Culpa!  Thanks, I normally do my due diligence at work.  I was posting in the short amount of free time I had before bed, after doing a long z/OS system messages lab after a long day at work, so I'll put it down to having '04' on the <somewhat fried> brain.

 ;)

/Mike

141
Users / Re: Cameras, Motion, and notifications
« on: April 03, 2012, 06:43:53 pm »
JaseP,

Thanks!  But, that has more to do with Motion itself, and not so much with Motion Wrapper and the events emitted by it.  I'm looking to see if someone's done this already, and that the capability exists in the Out-of-the-box LMCE product, or if Kmotion or other integration is required.

Thanks for responding!  Much appreciated!

/Mike

142
Users / Cameras, Motion, and notifications
« on: April 03, 2012, 05:19:30 am »
Good day folks!

Could someone familiar with the camera, motion wrapper, and e-mail (or other) notifications possibly point me in the right direction?

I have two DCS-930L IP cameras configured with motion wrapper, which are visible on RoamingOrb and the Admin site (I'm not running MD's yet other than for preliminary testing).  The cameras have on-board motion detection and e-mail alerting, which I'm presently using to e-mail me about motion events.  The onboard software is pretty limited, so I get spammed when light levels change, and when I'm home, and so on.  I'd like to move the alerting and e-mail notification to LMCE, so I can add some smarts to it using event logic, and I'm wondering if:

A) it's functionality that presently exists, or if it'll take something like kmotion,
B) if so, what kind of event is emitted by motion wrapper (tripped, motion, true/false, number of pixels...), and
C) if anyone else is doing the same thing, and how is it working out for them

I'm just hoping to avoid running down a few rabbit holes... I've tried putting together some events, but not sure if I'm on the right track.  If someone could point me in the right direction, I'll go looking for the light  ;)

Thanks!

/Mike

143
Users / Re: A Split
« on: April 03, 2012, 05:03:15 am »
Just some thoughts thrown out for consideration...

In my $Day_Job, I work with the Enterprise Distros, and with a formalized set of change management processes.  In both, a significant change to form, fit, or function usually warrants a major version change, and an impact assessment weighing the need for change against the stability of the environment.

With 8.04 presently being the "stable release", and 10.04 being the alpha/beta "development release", might I suggest that a change in orbitors might constitute a major change to form, fit, and function.  Might it not be better to concentrate efforts on integrating and stabilizing the new orbitor with 10.04?  That way those who value stability can remain on 8.04 with the existing technology, and those who don't mind living on the edge can help with testing the new qOrbitor.

For the communities' consideration...

/Mike

144
Users / Thom, Our Thoughts are with you...
« on: March 29, 2012, 02:56:09 am »
and I am in a critical care ward on death watch for my father.

-Thom

Thom,

I think I can safely say that the LMCE communities' thoughts are with you and your loved ones.  May you cherish and celebrate the memories of the good times you've spent with your father, and I hope that those memories help bring comfort and peace to you both.  May your faith (or the Force ;-) grant you the strength, courage and peace of mind to face what comes.

Our Thoughts and best wishes are with you.  You are not alone.

/Mike

145
Installation issues / OT: Thom, our thoughts are with you...
« on: March 29, 2012, 02:51:38 am »
and I am in a critical care ward on death watch for my father.

-Thom

Thom,

I think I can safely say that the LMCE communities' thoughts are with you and your loved ones.  May you cherish and celebrate the memories of the good times you've spent with your father, and I hope that those memories help bring comfort and peace to you both.  May your faith (or the Force ;-) grant you the strength, courage and peace of mind to face what comes.

Our Thoughts and best wishes are with you.  You are not alone.

/Mike

146
Users / Re: Myth, VDR, or no TV at all...
« on: March 23, 2012, 06:58:34 pm »
Kicking off the comments discussion, I'm using MythTV in my production set-up.  I'm still playing around with LMCE, so it's running in a separate test environment.  When I'm done testing, and I can sync up the various MythTV levels and do a database export from prod and import to LMCE, I'll flip over to LMCE as the prod environment.  Don't have a lot of free cycles right now with work being busy, family life, and a Z/OS course on the side, so I'm not sure when the cut-over will happen.

My Master back-end is running MythTV 0.24.2, and has two PVR-1600 cards in it.  The analog inputs are connected to the CATV line (we still have analog on CATV in Canada), and the two digital inputs are hooked to a home-made 4 bay bow-tie antenna, picking up the local ATSC channels.

I have a disk-less slave back-end/Front-end running MiniMyth, with two PVR-150's.  One is hooked to CATV, the other is hooked to the Rogers STB.  I have three other MiniMyth disk-less front-ends running.

I'm excited about the release of 0.25, as I see the services API as a stable means to accomplish remote control of Myth.  0.24 came out with 'events', which 0.25 is extending on, which could be great integration points into LMCE DCE events.  0.25 also has AirPlay/AirVideo support baked in, the new OSD message class (send CID events discreetly while watching media), plus a whole lot of other bells and whistles.

Have a good one!

/Mike

147
Users / Myth, VDR, or no TV at all...
« on: March 23, 2012, 06:24:57 pm »
With the discussion about MythTV 0.25 and it's new services API, I'm curious as to how much each PVR back-end is used.  So, if you're presently using one of the 2 PVR back-ends that are supported in LMCE (either in LMCE or separately), why don't you cast a vote and comment if you want.  Since we don't have a 'popularity contest' capability in LMCE, this could be interesting to see how many people use the TV functionality, and what are the levels of usage for each PVR backend.

Thanks!

/Mike

148
Users / Re: climate question
« on: March 15, 2012, 08:10:30 pm »
_IF_,

Keep in mind, X10 is not the most robust PLC communications protocol out there, and it's not a closed loop system (meaning that commands are merely tossed onto the wire and are not acknowledged).  So, if your heaters are on, and the off command doesn't make it through, things could get quite toasty!  You'll want to make sure you embed retry logic into your events to resend the command periodically, or use a technology that does support ACK of commands and query status commands (INSTEON, UPB, Z-Wave, etc).

Most of the home automation lists I'm on recommend that you NOT control anything with X10 that can burn your house down if the off commands don't make it through; similarly, they don't recommend it for cases where a life could depend on it (your reptile cage, fish tank, etc).

HTH!

/Mike

149
Users / Re: physical address extension
« on: March 02, 2012, 05:28:53 am »
It has been my experience that doing what you suggest is a bad idea, I tried it once and had very undesirable results.

Tux-box1,

It's been running smoothly as a 64-bit kernel on a Debian 32-bit userland for 3 years now.  I've been running KVM based virtuals on the same system for almost 2 years now.  I was suggesting the 64-bit kernel as it would help you make use of your extra memory, which is one of the reasons I upgraded to 64-bit myself.  The trick is to use the 64-bit packaged kernel from the 32-bit architecture stream, which Debian makes it easy to do. 

Now that I've dug a little deeper in apt on my core, I'm seeing that Ubuntu (10.04) only packages i386 and generic (which equates to i686), plus a generic-pae.  They also have their server kernel, but I'm not sure it's 64-bit (I would presume not), and you'd lose drivers for consumer hardware.  So, to get a 64-bit kernel on 32-bit architecture stream, it would take getting the 64-bit streams packages and installing on 32-bit, which would likely have serious breakage.

So, the easiest approach on Ubuntu would be to install the generic-pae kernel if it exists in 8.10 (apt-cache search linux-image or linux-kernel |grep pae).  Don't install the server kernel; it'll be missing a lot of drivers for commodity hardware.  Whether or not you lose hardware acceleration would depend on your graphics card hardware and the quality of the drivers.  You will have a minor performance hit for the memory paging, but it should be negligible.

One thing to consider is what the box is doing when the memory is being used.  'free' and 'top' will tell you a lot there.  If you have lots cached and you're not swapping, you're in a good place.  Modern kernels will use free memory for the file system cache, and release it to apps as needed.  Here's a funny one for ya; Windows can run faster virtualized on Linux than directly on the bare metal, because of the Linux FS Cache.  It helps crank up the I/O speeds, where Windows typically has some trouble.

My comments are given as someone who administers Linux systems on many different hardware platforms, architectures and hypervisors at work.  Hope it helps!

/Mike

150
Users / Re: physical address extension
« on: March 01, 2012, 06:38:17 pm »
Or, you could install a 64-bit kernel.  My virtual host started life many moons ago as a Debian 3 32-bit system running on a Pentium 166.  It's received a few hardware and in-place OS upgrades along the way, and is running a 64-bit kernel with a 32-bit userland.  It runs fine, and I'm running a mixture of 64 and 32-bit virtuals.

So, another option for you to consider...

HTH!

/Mike

Pages: 1 ... 8 9 [10] 11 12 13