Sunday, May 24, 2009

LinuxMCE Alpha2 Day 1



Day 2 is in progress. I'll update the link tomorrow.


I decided to give Linuxmce another shot since the kernel is now up to spec to support my onboard intel hda sound card and better memory management. I need a one stop shop to to the following things:

  • Home Automation: Zwave, and X10
  • Record TV (Preferably Mythtv due to me having a 4 years worth of recording)
  • Multiroom Audio (Prefereably Squeezecenter due to a couple of Squeezeboxes)
  • Multiroom Video
  • Asterisk Voip
  • Voicemail
  • Web Control
  • Scenes, Schedules
Linuxmce gives me that and so much more.

I spent Friday night (5/22/09) installing Kubuntu 8.10 (sad that 9.04 won't work with linuxmce yet), upgrading packages, and installing linuxmce with their provided scripts.

Starting bright and early on Saturday, I moved the alpha2 server my server closet and performed these steps:

  • Plugged my main web/automation server directly into the router with it's static assigned ip.
  • Plugged my Micasaverde Vera into the router directly
  • Plugged my Tmobile@Home Voip MTA directly into the router
  • Plugged the eth0 card on the alpha2 server directly into the router
  • Plugged the eth1 card on the alpha2 server into my 16-port gigabit switch
  • Turned off dhcp on my Linksys WRT310N that's connected to my cable modem (history has told me that I still want to do this because my network turns to much in the linuxmce internal/external network setup)
  • Unplugged the link from the router to the switch.
  • Powered up the alpha2 server
Within about a minute I realized that dhcp was not working. So I went thru the song and dance of powercycling all my network connected devices because I didn't have an hour to wait for all of them to get new leases.

I tinkered around with the interfaces file in vi and found that the netmask 255.255.255.0 eth0 line for card eth1 caused problems. I removed eth0 and restarted networking and dhcp started up. I powercycled all the devices and they got new leases.

Up next was setting up the pxe netboot on all my my frontend desktops that are already connected to tv's and monitors. First time boot worked and they got new leases and the pxe magic worked. Upon reboot they could not find the vmlinuz images. I thought that this might be a problem because they are all amd64 machines and thus detected as amd64. I rebuilt one of the orbiters as an i386 server in hopes that it would correct the problem. Quick reload of the dce router and reboot of the orbiter had the same problems.

I decided to try a real i386 machine. I went into the bios on my Asus Eeepc 1000HE and turned on the pxe boot. First boot worked just like the other and second boot the vmlinuz images could not be found. Yes, major problems if I actually want to use the correct way of having the orbiters use the alpha2 server in the inteded way.

From one of the desktops that failed the pxe boot experience I sshed into the alpha2 server and saw the the symlinks to the images were all bad so it's probably something in the linuxmce diskless boot scripts that is off. I opened up a ticket with them on this.

I changed the symlinks to the correct ones and then tried again. This time there was a nfs mount problem in the that forced me back to busybox. Again opened up a ticket with linuxmce developers.

With that aside I turned off pxe on all the desktop and just let them boot into regular ubuntu.


Up Next was Automation

I was still having problem with the nvidia drivers producing a black screen upon boot where the setup wizard was supposed to be. I showed up only once and never came back.

Previously in linuxmce if I plugged in a zwave usb controller it would popup the wizard and let me know that I plugged in a zwave controller and would ask if I wanted to setup lights. No X so no wizard. So I setup the rooms manually, added the X10 CM11A and Zwave Crontrollers manually. I setup a few X10 lights and they worked. This did not work in previous linuxmce versions.

Without X I don't think that I can set Zwave modules. At least from the web admin I couldn't find any templates to add zwave devices.

Up Next was Voip
Under the lines section Broadvoice was one of the default providers. I typed in my phone number and passwords and voila, I was registered with no headache. Calls were coming in but they were going to voicemail.

I tried to setup my handytone 286 adapter that is connected to my fax machine as an extension but it was having problems trying to connect to broadvoice at the same time as linuxmce and the web interface for the adapter wouldn't let me in to reconfigure it to point to the alpha2 server as an extension.


Up Next was Security
This did not go well at all. I have a couple of wifi cams and my hardwired security cameras also connected to a Aviosys 9100A 4-port video surveillance appliance that turns all my cameras into ip cameras with motion jpgs. Very cheap and effective solution.

My Micasaverde Vera uses the same dce router and motion wrappers as linuxmce and can view all the wifi cams and motion jpgs from the 9100a but alpha2 could not display any images.

Also the wifi cameras would not connect to a seperate router that I'd plugged into my gigabit switch because it did not know how to handle dhcp routing and dns with dhcp turned off. Not only that all my orbiters, wifi phones, cell phones, and laptops were now dead. I need to do some more experimentation with more routers to see how to get around this.

They worked on the linksys wrt310N but that was not a true test because it was bypassing the linuxmce dhcp routers.


Up Next Mythtv

I didn't even make it this far. I just turned the bloody thing off because it never even detected my hdhomerun or installed tuners.


At this point now I'm reinstalling Linuxmce alpha2 from scratch again. Maybe I'm insane and hope to get different results on the second time around. If nvidia and xorg play nice this time around I might actually get to configure the alpha2 server as expected. One positive side effect of the internal/external network were my browsing speeds and network transfers were amazing. I don't know if the qos on the linksys routing is slowing stuff down but once off of it ny speeds were explosive.

See you in day 2.
Post a Comment