Recent Posts

"Cheap" is my favorite word!  Well maybe second favorite...

There are always exceptions, clearance, thrift shop finds etc, but for the most part you truly do get what you pay for.  Forgive me if I leave any out as there is a ton of work making this operational.  The wiki sums this up better, but your options for orbiter 'types' is:

web-orbiter 2.0 :  laptop, pretty much everything with a browser.  I have used this on a Nintendo DSI XL.  No streaming cams to this, unless you tab switch away from the orbiter and open the cam url directly.

embedded orbiter (such as webdt-366, cisco 7970 and similar):  I believe this is what you are referring to when you say Linux OS running.  Supports streaming cams on devices I have tested. 

JavaMo:  have not tested

iOS apps :  (Dianemo S, Roaming Orb) :  Andrew will have to correct me here if I am mistaken but I believe cams are not supported for linuxmce on dianemo S due to their integration of kmotion??

qOrbiter:  This is exciting!  I do not currently have a capable device to test but the work being done is game changing.  Again you are going to get what you pay for in performance.  A tablet that was mentioned to me as pretty standard hardware capable of taking advantage of qOrbiter would be the Nexus 7.  Something very important to consider here btw is that investments here are not "home-bound,"  a tablet away from home functions like a tablet, when home it also becomes an orbiter.

One more point of clarity, I am used to having to make this distinction when introducing the system to family members.  Security Cameras being the exception, an orbiter does not play media.  Orbiters control Media Directors which play media.  If you can remember Media Directors as moon## devices the orbiter reference becomes easier to swallow as orbiters can control (orbit) a moon.  To cement this open an on-screen orbiter and change its room.  This one is the hardest for people to grasp i feel because a TV screen/monitor is viewed as a single image.  What you are seeing though is:

you       on-screen orbiter (living room)     media director (living room) display

change the onscreen orbiter in the living room though to  bedroom and you get:

you       on-screen orbiter (bedroom)         media director (living room) display

Play a movie using the onscreen orbiter now and the bedroom tv wakes up and starts playing.

did you do a apt-get dist-upgrade or just apt-get upgrade?

There are many great features in 10.4: Installation seems flawless, many of the devices that were laborious to install in 8.10 are PNP in 10.4 (gc-100 and PLM for example) and video streaming of movies and recorded TV seems to work better than ever.

However, there are also a number of surprising things I have been finding out while trying to get 8.10 devices to work on 10.4:

Don't try and upgrade the nvidia driver--it will put you into API mismatch hell

Ctrl alt backspace will not get you out of the x terminal in 10.4--you have to manually go in to the keyboard setup and tell it those keystrokes

The PNP que only gives you so many chances to use a device--use them up and you have to go into mysql and delete all instances of the device in the database so that it can start over.

Drivers that were buggy/non functional in 8.10 may seem functional in 10.4 but may still be buggy--do your research.

A case in point brought me to another surprising discovery: When you go to update a diskless MD (as when you change the buggy Realtek 8169 driver that comes with 10.4 to the updated 8168 driver that works well with 10.4) you run into a conflict between different kernels:

root@dcerouter:/boot# cd /usr/pluto/diskless/
root@dcerouter:/usr/pluto/diskless# chroot 80
root@dcerouter:/# depmod
WARNING: Couldn't open directory /lib/modules/2.6.32-45-generic: No such file or directory
FATAL: Could not open /lib/modules/2.6.32-45-generic/modules.dep.temp for writing: No such file or directory


root@dcerouter:/boot# uname -a
Linux dcerouter 2.6.32-45-generic #104-Ubuntu SMP Tue Feb 19 21:21:41 UTC 2013 i686 GNU/Linux

root@dcerouter:/# cd /lib/modules/
root@dcerouter:/lib/modules# ls
2.6.32-46-generic

What is going on? one says 45 and the other is 46.

My workaround (which seems to work so far):

root@dcerouter:/usr/pluto/diskless# chroot 80
root@dcerouter:/# depmod 2.6.32-46-generic
root@dcerouter:/# mkinitramfs -o initrd.img-`uname -r` 2.6.32-46-generic

here is the background on the issue:
http://wiki.linuxmce.org/index.php/Realtek_8168

I've done update and upgrade inside both the core and the MD

I admit profound ignorance when it comes to depmod and the different kernels in play. My question: Is this a bug that needs to be addressed?

Many thanks for any input.

maybe you can provide a more detailed bug report, e.g. what exactly you're doing. Are there any messages in syslog? Adding devices to rooms works fine (we've no other reports that indicate otherwise). But for the records, this is the old web admin written in cherrypy. The new interface is served via agorpc on port 8008. Just make sure to install the latest package.

OK, after updating my svn copy and running the updated agosimulator.py it doesn't go kablooey anymore. It appears that was what tripped it.

the source is here: http://www.agocontrol.com/trac/browser/agocontrol/agocontrol/core/rpc/html

maybe you can provide a more detailed bug report, e.g. what exactly you're doing. Are there any messages in syslog? Adding devices to rooms works fine (we've no other reports that indicate otherwise). But for the records, this is the old web admin written in cherrypy. The new interface is served via agorpc on port 8008. Just make sure to install the latest package.

afaict yes

Well... it still blows up, but slightly differently. I get the error only 50% of the time now, and refreshing the page gets me my page back without having to restart everything.

Code:

An error occured in a template

/opt/agocontrol/admin/agoadmin.py:231    default     inventory = discover()
/opt/agocontrol/admin/agoadmin.py:79     discover    if message.content:

Where exactly can I see this emberjs thingy?

OK, I get the general feel for that now. I was reading the code and not understanding the "why" part of the equation. Now I do and I can dig deeper into this. I've started building these objects and I'm reading the Hulu code. I guess I better figure out why Hulu isn't running on my MDs and fix that before I go and try to test this.  This will take me a bit, but it feels good to keep my C/C++ skills up to date. It has been a little while.

afaict yes

Armor Gnome,

    Thank you!  I hadn't though about the orbiter as a "view node" for cameras.  This is a much better solution than PIP.  I am in the process of getting some "cheap" Android devices to run the orbiter app.  Should this setup stream video, or would I need an orbiter running a Linux OS?