Messages

Perhaps I may be dense in this, but where does one go about acquiring a WebDT 366 from? I've checked around occasionally on ebay and craigslist, but have never even once seen one available.

In an ideal world, not only should a motion sensor turn on a light and turn it back off again after a set amount of time, it should queue it's status so that if it keeps getting tripped, it will reset the off timer. I have been hoping to set this exact type of scenario up, but for a long hallway inside with a motion sensor at either end (it's so long, I might use three...) If I were to use the X10 Eagle Eye, I would only have to set them all to the same code and linuxmce would think that they are one unit.

This brings up a side matter... has anyone gotten linuxmce to respond to X10 signals yet? I've only even been able to transmit them.

I have next to no idea what I'm talking about here, but I'd imagine that this is in a config file buried somewhere on the core.

Here's my config page. My system doesn't have any dedicated serial ports so I'm using a USB dongle and have the only option in the drop-down selected.


http://img204.imageshack.us/img204/157/screenshot3rg5.jpg

I was just screwing around a couple of minutes ago and decided to change 'Comm Method' in the CM11a's Device Template from RS232 to USB... suddenly it started working ... kinda. It's currently transposing most of my commands to different housecodes (o7 to m7 for instance), attempting to brighten non-dimmable modules, and absolutely no media-initiated scene starts. Oh, and occasionally it'll send commands to the wrong unit codes as well. (I test a lighting scenario that is only supposed to turn on o7 and it tries to brighten m8).


http://img204.imageshack.us/img204/9997/screenshot2rw3.jpg

I'm using a Testerlink 4819 (sorta like this guy but much less complex: http://www.smarthome.com/2200att.html) to see the gibberish on the line, otherwise I would have never known it was sending commands at all.

Two more things I should add... I've been puzzling over what on earth the crossed-out 'F' symbol is on the floorplan page. I doesn't appear to do anything other than display a larger 'F' not crossed-out which toggles with the first one:


http://img84.imageshack.us/img84/653/screenshotab0.jpg

Also, here's a dump of my log for the most recent time I've tried installing and testing all four X10 devices in the room. From what I can tell, it looks like light switch templates don't know how to talk to the CM11a's template for some reason:

Code Select Expand

== ATTEMPT FRESH START ==
1 08/15/08 00:29:05 /usr/pluto/bin/Spawn_Device.sh 69 (spawning-device) 23647 Dev: 69; Already Running list: 15,16,17,18,28,29,20,24,32,22,25,21,63,
== FRESH START ==
1 08/15/08 00:29:05 /usr/pluto/bin/Spawn_Device.sh 69 (spawning-device) device: 69 ip: localhost cmd_line: CM11A
0 08/15/08 00:29:05 69 (spawning-device) Entering 69
========== NEW LOG SECTION ==========
1 08/15/08 00:29:05 69 (spawning-device) Starting... 1
1 08/15/08 00:29:05 69 (spawning-device) Found /usr/pluto/bin/CM11A
05 08/15/08 0:29:05.272 Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 69 last error 2 <0x2ae7d68d5940>
05 08/15/08 0:29:05.272 The router must be reloaded before this device is fully functional <0x2ae7d68d5940>
05 08/15/08 0:29:05.274 void ClientSocket::Disconnect() on this socket: 0x62e9d0 (m_Socket: 5) <0x2ae7d68d5940>
05 08/15/08 0:29:05.284 Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 69 last error 2 <0x2ae7d68d5940>
05 08/15/08 0:33:07.405 Got a reload command from 0  <0x41001950>
05 08/15/08 0:33:07.679 void ClientSocket::Disconnect() on this socket: 0x62eeb0 (m_Socket: 6) <0x2ae7d68d5940>
Return code: 2
2 08/15/08 00:33:07 69 (spawning-device) Device requests restart... count=1/50 dev=69
Fri Aug 15 00:33:07 PDT 2008 Restart
========== NEW LOG SECTION ==========
1 08/15/08 00:33:15 69 (spawning-device) Starting... 1
1 08/15/08 00:33:15 69 (spawning-device) Found /usr/pluto/bin/CM11A
05 08/15/08 0:33:16.084 Creating child 70 <0x2b1eeef45940>
05 08/15/08 0:33:16.084 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x2b1eeef45940>
05 08/15/08 0:33:16.084 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Creating child 71 <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Creating child 72 <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2b1eeef45940>
05 08/15/08 0:37:42.313 Got a reload command from 0  <0x41001950>
05 08/15/08 0:37:42.710 void ClientSocket::Disconnect() on this socket: 0x62eeb0 (m_Socket: 6) <0x2b1eeef45940>
Return code: 2
2 08/15/08 00:37:42 69 (spawning-device) Device requests restart... count=1/50 dev=69
Fri Aug 15 00:37:42 PDT 2008 Restart
========== NEW LOG SECTION ==========
1 08/15/08 00:37:50 69 (spawning-device) Starting... 1
1 08/15/08 00:37:50 69 (spawning-device) Found /usr/pluto/bin/CM11A
05 08/15/08 0:37:51.308 Creating child 71 <0x2b59849e4940>
05 08/15/08 0:37:51.308 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2b59849e4940>
05 08/15/08 0:37:51.308 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2b59849e4940>
05 08/15/08 0:37:51.308 Creating child 72 <0x2b59849e4940>
05 08/15/08 0:37:51.308 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2b59849e4940>
05 08/15/08 0:37:51.308 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2b59849e4940>
05 08/15/08 0:37:51.309 Creating child 73 <0x2b59849e4940>
05 08/15/08 0:37:51.309 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2b59849e4940>
05 08/15/08 0:37:51.309 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2b59849e4940>
05 08/15/08 0:37:51.309 Creating child 75 <0x2b59849e4940>
05 08/15/08 0:37:51.309 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x2b59849e4940>
05 08/15/08 0:37:51.309 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x2b59849e4940>
01 08/15/08 0:40:55.268 Failed sending address. <0x41802950>
01 08/15/08 0:41:40.509 No response from CM11A device. <0x41802950>
01 08/15/08 0:42:10.823 Failed sending address. <0x41802950>
01 08/15/08 0:42:56.059 No response from CM11A device. <0x41802950>
01 08/15/08 0:43:26.365 Failed sending address. <0x41802950>
01 08/15/08 0:44:41.888 Failed sending address. <0x41802950>
01 08/15/08 0:45:12.018 No response from CM11A device. <0x41802950>
01 08/15/08 0:46:12.918 No response from CM11A device. <0x41802950>
01 08/15/08 0:46:58.335 Failed sending function. <0x41802950>
01 08/15/08 0:48:13.773 No response from CM11A device. <0x41802950>
01 08/15/08 0:48:13.873 Failed sending address. <0x41802950>
01 08/15/08 0:49:29.404 Failed sending address. <0x41802950>
01 08/15/08 0:50:30.684 No response from CM11A device. <0x41802950>
01 08/15/08 0:51:00.994 Failed sending address. <0x41802950>
01 08/15/08 0:52:16.520 Failed sending address. <0x41802950>
01 08/15/08 0:52:47.126 No response from CM11A device. <0x41802950>
01 08/15/08 0:53:47.642 Failed sending function. <0x41802950>
01 08/15/08 0:55:04.917 No response from CM11A device. <0x41802950>
01 08/15/08 0:55:20.040 No response from CM11A device. <0x41802950>
01 08/15/08 0:56:05.452 Failed sending address. <0x41802950>
01 08/15/08 0:57:20.979 Failed sending address. <0x41802950>
01 08/15/08 0:57:51.113 No response from CM11A device. <0x41802950>
01 08/15/08 0:59:22.303 Failed sending function. <0x41802950>
01 08/15/08 1:00:37.745 No response from CM11A device. <0x41802950>
01 08/15/08 1:00:37.845 Failed sending address. <0x41802950>
01 08/15/08 1:01:53.364 Failed sending address. <0x41802950>
01 08/15/08 1:03:08.887 Failed sending address. <0x41802950>
01 08/15/08 1:04:09.223 No response from CM11A device. <0x41802950>
01 08/15/08 1:04:24.346 No response from CM11A device. <0x41802950>
01 08/15/08 1:04:24.458 Failed sending address. <0x41802950>
01 08/15/08 1:05:25.265 No response from CM11A device. <0x41802950>
01 08/15/08 1:06:10.602 No response from CM11A device. <0x41802950>
01 08/15/08 1:07:30.293 No response from CM11A device. <0x41802950>
01 08/15/08 1:07:30.393 Failed sending address. <0x41802950>
01 08/15/08 1:08:13.422 No response from CM11A device. <0x41802950>
01 08/15/08 1:08:43.739 Failed sending address. <0x41802950>
01 08/15/08 1:09:59.626 No response from CM11A device. <0x41802950>
01 08/15/08 1:11:19.289 No response from CM11A device. <0x41802950>
01 08/15/08 1:11:49.982 No response from CM11A device. <0x41802950>
01 08/15/08 1:12:35.395 Failed sending function. <0x41802950>
01 08/15/08 1:13:50.930 Failed sending address. <0x41802950>
01 08/15/08 1:14:21.068 No response from CM11A device. <0x41802950>
01 08/15/08 1:15:06.481 Failed sending address. <0x41802950>
01 08/15/08 1:16:22.011 Failed sending address. <0x41802950>
01 08/15/08 1:17:38.010 Failed sending function. <0x41802950>
01 08/15/08 1:17:53.497 No response from CM11A device. <0x41802950>
01 08/15/08 1:18:54.017 Failed sending function. <0x41802950>
01 08/15/08 1:19:39.257 No response from CM11A device. <0x41802950>
01 08/15/08 1:20:09.563 Failed sending address. <0x41802950>
01 08/15/08 1:21:25.086 Failed sending address. <0x41802950>
01 08/15/08 1:22:40.626 Failed sending address. <0x41802950>
01 08/15/08 1:23:10.751 No response from CM11A device. <0x41802950>
01 08/15/08 1:23:56.171 Failed sending address. <0x41802950>
01 08/15/08 1:25:11.690 Failed sending address. <0x41802950>
01 08/15/08 1:25:41.828 No response from CM11A device. <0x41802950>
01 08/15/08 1:27:13.022 Failed sending function. <0x41802950>
01 08/15/08 1:28:28.560 Failed sending address. <0x41802950>
01 08/15/08 1:30:29.864 Failed sending function. <0x41802950>
01 08/15/08 1:30:59.998 No response from CM11A device. <0x41802950>
01 08/15/08 1:31:15.122 No response from CM11A device. <0x41802950>
01 08/15/08 1:31:45.426 Failed sending address. <0x41802950>
05 08/15/08 1:32:50.321 Got a reload command from 0  <0x41001950>
01 08/15/08 1:33:03.153 No response from CM11A device. <0x41802950>
05 08/15/08 1:33:03.158 void ClientSocket::Disconnect() on this socket: 0x62eeb0 (m_Socket: 6) <0x2b59849e4940>
Return code: 2
2 08/15/08 01:33:03 69 (spawning-device) Device requests restart... count=1/50 dev=69
Fri Aug 15 01:33:03 PDT 2008 Restart
========== NEW LOG SECTION ==========
1 08/15/08 01:33:11 69 (spawning-device) Starting... 1
1 08/15/08 01:33:11 69 (spawning-device) Found /usr/pluto/bin/CM11A
05 08/15/08 1:33:11.462 Creating child 71 <0x2af8436bb940>
05 08/15/08 1:33:11.462 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2af8436bb940>
05 08/15/08 1:33:11.462 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2af8436bb940>
05 08/15/08 1:33:11.462 Creating child 72 <0x2af8436bb940>
05 08/15/08 1:33:11.462 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2af8436bb940>
05 08/15/08 1:33:11.463 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2af8436bb940>
05 08/15/08 1:33:11.463 Creating child 73 <0x2af8436bb940>
05 08/15/08 1:33:11.463 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2af8436bb940>
05 08/15/08 1:33:11.463 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2af8436bb940>
05 08/15/08 1:33:11.463 Creating child 75 <0x2af8436bb940>
05 08/15/08 1:33:11.463 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x2af8436bb940>
05 08/15/08 1:33:11.463 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x2af8436bb940>

Hey guys, I've been trying to install a CM11a X10 interface into my core for over a week now to no avail. I have it plugged into a Prolific PL2303 USB to Serial adapter and it's working fine with heyu (http://heyu.tanj.com/), a command line-based X10 control program.

I've gone through the steps in 'Setup', 'Adding Lights', and 'Troubleshooting' here: http://wiki.linuxmce.org/index.php/CM11 and ran the configuration videos. I've also tried tweaking settings in the CM11a's page and the individual lights' pages, and even deleted them and re-run the configuration multiple times. At one point I thought it might have been a capitalization or numerical issue, so I tried all four ways (i.e. A1, A01, a1, a01) for all devices in the room, and even tried moving everything to the default housecode (I don't normally use A).

I'm stuck now with full functionality through heyu, but never once have I gotten linuxmce to change the state of any of my X10 devices.

Any ideas?

That would appear to be the brainfart that I couldn't place my finger on... hahaha I hadn't even thought about a firewall. Do you control it from the core's admin site?

Is anyone using a bittorrent client successfully on the core to download media directly into linuxmce? I've ran into two obstacles so far. 1) I cannot seem to get any incoming bittorrent connections using KTorrent at all. 2) When I try to sudo apt-get install another client, neither the default 'linuxmce' or the password I set at install work.

My setup currently looks like this:

External: Cable modem ==> WRT54G as router ==> core/hybrid on one jack, and a laptop that I'm using for debugging on another jack

Internal: core/hybrid ==> Motion Computing tablet used as an orbiter

I am familiar with port forwarding and understand that it's possible for an ISP to block IP ranges, but no amount of tweaking the WRT54G and KTorrent have allowed me anything incoming. All that I have been able to guess is that somehow KTorrent is listening on eth1 instead of eth0. Any ideas?

Edit: Ok, I found some information on resetting root password here http://wiki.linuxmce.org/index.php/Resetting_Account_Passwords , but I am doubting that I'll be able to get another client working until I figure out the no incoming connections issue.

Do you have a specific model number?

From what I can tell, your TV card uses a 6 volt, 1.7 amp adapter. If you can't find that exact power, you can go higher on the amperage, but not the voltage.

There should be a sticker on it like in this picture: http://c1.neweggimages.com/NeweggImage/productimage/15-116-624-03.jpg which will confirm the voltage, amperage, and polarity, but you'll probably have to make a trip to radioshack to figure out the size of the connector.

Hey there, I'm having trouble auto-detecting windows shares and I'm not quite sure how to start troubleshooting more extensively.

My network setup looks like this:

External network:
Cable modem ==> Hybrid/Core on eth0

Internal network:
eth1 on Hybrid/Core ==> Linksys WRT54G acting as switch / access point (DHCP turned off) ==> Windows XP PC with shares that I want to mount, and laptop that's PXEing as an orbiter.

The primary problem that I'm facing currently is getting windows shares to mount. Several minutes after I first plugged my Windows PC in, I got a series of messages as linuxmce presumably detected my shares. I entered my login and password information for the Windows PC into the orbiter and I believe it said the device was configured.

I reloaded the router a couple of times over the course of a couple of hours, but other than the four initial videos that come with the DVD installation, nothing ever showed up in media. To be honest, I don't really care about keeping the content on the PC, so I tried to browse my linuxmce box to drag&drop files onto it from the PC but couldn't figure how to find my Core from the PC.

Any ideas how to either make linuxmce see my shares, or transfer media onto the Core directly?

Not applicable to me quite yet, but I'm thinking about an Aquos. Thank you. 

Ok, netbooting worked with the craptastic graphic settings, but now it just looks like a big mobile orbiter without a touchscreen. :-(

Think I'd have better luck wiping the 64bit core, installing the 32bit core, and attempting the medium graphic settings on the laptop? (OpenGL with overlay, but no alpha-blending)

Its unclear whether you had two nics in your core when you installed to it... but I would suggest the simplest solution is to reinstall a 2nd NIC (what chipsets do your NICs have?) and then reinstall from the DVD again. This will allow the installer to re-detect the NIcs and set them up correctly. Its possible to do this after installation too... but a reinstall is probably easier (you can use the retain /home directory option).

Unless your NICs are unsupported or the drivers are not present in the DVD then you should find this corrects your problems.

All the best

Andrew

The core was never powered on with only one NIC, three of them were swapped, but only after I'd exhausted every was I was aware of testing eth1 which randomly stopped working. And yeah... reinstalling :-P

Sounds like you need to edit /etc/udev/rules.d/70-persistent-net.rules to get rid of a bunch of cards you tried.  Maybe some corrections have to be made to /etc/network/interfaces as well.

Unfortunately, I have almost zero knowledge so far about editing config files, so I just bit the bullet and reinstalled. Everything's working smoother than before, but I've ran into a new issue - on netboot, my laptop freezes on the orbiter screen. A picture background from flickr loads, and the overlayed (but not alpha-blended) GUI appears, but nothing responds at all. My laptop's a Toshiba A135-S7403 (the Best Buy one from last Black Friday) with a GMA 950 which I thought should be able to support OpenGL from here: http://forum.linuxmce.org/index.php?topic=5019.0 I deleted the device from the core and I'm currently setting up the netboot again with the lowest graphic settings, and I'll post how that works out.

I noticed something else while looking through the device configuration that I hadn't even thought about before - I'm using the 64bit install on my hybrid/core, but my laptop's i386. In the laptop's device configuration, it refers to it twice as amd64 - will this cause problems?

Thanks for the responses, both of you!

OK, got another AMD 64 dvd image downloaded, and completed installation about seven hours ago. There were several minor hangups, but I'd been able to get past everything to the point where I thought I would experiment with net booting my laptop. DHCP found the boot location instantly and the laptop started downloading and installing (to ram?) the software needed, but got hung up after about five minutes. During this time, I had been trying to cure another problem by redoing the 'display res and sound' wizard on my hybrid/core which I had no idea would reload the core, let alone reboot the entire machine. The laptop seemed to take it in stride and tried to reconnect to the server, but it kept timing out. I let it sit for ten or so minutes before trying to jar it, but finally relented and hard powered it down. I had to run out the door on an errand for about an hour and briefly noticed that another computer on the internal network was showing a 'could not connect to server' page in firefox, but thought nothing of it.

Fast forward an hour later (five hours ago) and I tried net booting the laptop again, but this time it didn't find any DHCP. My first thought was a bad cord but I ruled that out, second thought was that my old wireless router (which I'd made static and was using as a switch) had locked up but I disproved that by connecting to its config page.

Five hours of HBOKing later, and here's where I'm at: The only NIC on the hybrid/core that is talking to any other machines at all now (old router, modem, internal computers etc) is the one integrated into the motherboard. I've tried three different PCI NICs, at least two of which were working just fine today even, and I can't get a peep out of them. This means that I have the choice of either an internal network, or an external network - not both. I've literally 'swapped interfaces' more than twenty times, coupled with every possible combination of powering down hardware in different orders and trying each configuration both ways (connecting integrated NIC to internal network and PCI to external, testing, then swapping them both without touching other settings). I've even isolated the internal network down to the hybrid/core, a crossover cable, and one other computer. The other computer can't even ping the PCI NICs! The oddest thing about this entire issue though, is that all three of the PCI NICs that I've tried have shown good link lights on themselves and and the other computer's NICs.

Here's a pretty common display in  Advanced | Network settings ... notice the lack of a MAC address on 'internal' (currently set to the PCI NIC)

EXTERNAL_IFACE     eth0
EXTERNAL_MAC    00:49:8D:50:B9:1E
EXTERNAL_IP    24.20.0.231
EXTERNAL_NETMASK    255.255.252.0
EXTERNAL_DHCP    1
INTERNAL_IFACE    eth1
INTERNAL_MAC    
INTERNAL_IP    192.168.1.1
INTERNAL_NETMASK    255.255.255.0
GATEWAY    24.20.0.1
DNS1    68.87.69.146
DNS2    68.87.78.130

The closest thing I have to a working theory about what's happened is that the 'display res and sound' wizard somehow has control of the NICs too. I'm guessing that my first PCI NIC (internal network) was old and failed when I was attempting to net boot, and the system ignored it when I started the wizard one or two minutes later, and treated the setup as one NIC with two IPs spoofed. If that is in fact the case, I have tried everything in my power short of wiping and reinstalling to correct the error - I've even exactly duplicated the events surrounding the wizard, but with a known good NIC, and reran the wizard. All this though, to no avail.

I'm going to give one more go at it tomorrow before completely reinstalling. Any ideas out there on anything else I should be looking into, or something that I'm not comprehending?

P.S. hardware problems and software problems can be annoying, but when they're both happening at the same time, it makes you want to throw you computer out the closest window ;-) (Though there still lies the possibility that this is entirely software related.)

Hey there, I ordered both the 32bit and 64bit install DVDs for $5 about a month ago and just opened the package now to install the 64bit, but it's so scratched that install fails. How would I go about getting a replacement sent out?