Messages

1

Users / Re: unable to change samba password

« on: July 29, 2010, 06:10:10 pm »

I'm still having issues with this.
I should get the fixes when they arrive by doing apt-get upgrade right?

I've setup a diskless mediadirector. It boots and I get the regular menu but no pictures are displayed.
When I do ctrl-alt-F1 I see theres some error messages:
CIFS VFS: Send error in SessSetup =  -13
CIFS VFS: cifs_mount failed w/return code =  -13

then after a while this line is repeated:
CIFS VFS: cifs_mount failed w/return code =  -6


I did try a couple of things to change the samba password for my main user, including manipulating directly in pluto_main.Users table. So maybe I've messed something up there also. I've created another user though which seems to work.
Would I need to tell the media director somewhere to use the second user?

2

Installation issues / Re: "UPDATED" Nvidia Driver install on MD (My Solution)

« on: July 28, 2010, 09:33:21 pm »

should this still work?
I got stuck at this part:

Once back at the prompt still root@moon##$ type telinit 1
 Now go to the MD in question it will have already killed X and will be waiting your response with the question enter or hit ctrl-d only hit enter

my md will just hang and not respond to anything but ctrl-alt-del after I type telinit 1

3

Users / Re: DVB Cards info needed for Templates

« on: July 21, 2010, 03:52:57 pm »

TerraTec Cinergy 1200 DVB-C

I currently use kernel 2.6.34 because of mantis (s2-liplianin) driver

sudo lspci -vn
02:07.0 0480: 1822:4e35 (rev 01)
        Subsystem: 153b:1178
        Flags: bus master, medium devsel, latency 32, IRQ 17
        Memory at fdfff000 (32-bit, prefetchable) [size=4K]
        Kernel driver in use: Mantis

sudo v4l2-ctl -n
Failed to open /dev/video0: No such file or directory

4

Installation issues / Re: Netboot - Can't open /tmp/net-eth0.conf

« on: July 18, 2010, 10:58:59 am »

I encountered this problem with an asus p5k board. it has two nic cards.
I just had to put the cable in the other network card then the problem went away for me.

(Might save someone some time)

5

Users / Re: x10 with cm11a, no commands working

« on: July 16, 2010, 02:36:40 pm »

Sorry, I misunderstood then.
I don't think this will be a practical solution for me because I have no place to put it without major work in the apartment.

I have the behaviour I want working with heyu, just a simple shell script:

Code: [Select]

#!/bin/sh
heyu on A3
sleep 5s
heyu off A3

heyu isn't working all that well on linuxmce though as it uses 100% cpu. Also it seems whatever runs a x10 command first of linuxmce or heyu gets the serial port until next reboot.

6

Users / Re: x10 with cm11a, no commands working

« on: July 16, 2010, 01:25:10 pm »

It wasn't there on my system.

This is what I tried:
I went to the web admin pages. "Show devices tree" - "Core" - "CM11A" - Create child device - pick device template.
then I browsed through "Device Template"

7

Users / Re: x10 with cm11a, no commands working

« on: July 15, 2010, 11:53:15 pm »

The linuxmce x10 is working.

I have put up a simple motor (Add A Motor 80) with a appliance module (on/off) attached to it to open and close my curtain.
However I need to send on and then off after the motor has stopped so it is ready to be run again by a new on signal.

Is there a device template for this? or will I need to use a scenario?

Looked at the scenario bit but didn't find any way to have it sleep for a specified time before it sends the next command.
I could of course send first an Off command then an On command, but that would mean theres always electricity on the motors so I would like to avoid that.

8

Users / Re: x10 with cm11a, no commands working

« on: July 12, 2010, 09:33:21 pm »

Kind of weird thing happened here. I installed heyu and that works but with 100% cpu usage. Did a reboot, now one of two configured x10 devices worked via linuxmce. Then I tried heyu, that worked with all devices. The one lamp in linuxmce x10 stopped working after heyu started. Even if I stop heyu it won't be controled by linuxmce anymore, so guess I need a reboot.

Is it possible to run any commands directly to the linuxmce X10 stuff in the terminal (like heyu)?
Any way to use heyu in linuxmce instead?

9

Users / Re: unable to change samba password

« on: July 12, 2010, 09:15:58 pm »

Any workaround or will I have to reinstall?

10

Users / unable to change samba password

« on: July 12, 2010, 12:48:48 pm »

Code: [Select]

sudo smbpasswd pluto_havard
New SMB password:
Retype new SMB password:
mod_smbfilepwd_entry: malformed password entry for user pluto_havard (passwd too short)
smbpasswd_update_sam_account: mod_smbfilepwd_entry failed!
Failed to modify entry for user pluto_havard.
Failed to modify password entry for user pluto_havard

I tried to change my samba password but it always gives me passwd too short message. I tried one really long password (22 chars) just too check if it was some policy thing, but dont think thats the case here.

11

Users / x10 with cm11a, no commands working

« on: July 11, 2010, 01:39:08 pm »

I've installed this image:
LinuxMCE-8.10-23036-i386.iso
I had to upgrade the kernel to 2.6.34 to get my tv cards working

I've then followed this guide
http://wiki.linuxmce.org/index.php/CM11

So now, I've got in the web admin under devices tree:
Core - CM11A (Device Template:CM11A #48, Device data: /dev/ttyS0) - livingroomlamp (Device Template:Light Switch (on/off) #37, Port/Channel Number: A6)

When I click "send command to device" on livingroomlamp and choose "on" in the dropdown I get this output:

Code: [Select]

Message Sent succesfully.
/usr/pluto/bin/MessageSend localhost -r 0 37 1 192 97 "" 98 ""
Response was:
RESP: OK
The light does not turn on though. If I click on the different log links there are no entries there.

Code: [Select]

havard@dcerouter:~$ cat /var/log/pluto/33_CM11A.log
05      07/11/10 8:08:57.388            Going to rotate logs... <0xb6a4fb90>
Return code: 143
3       07/11/10 12:32:53       33 (spawning-device)    Device died... count=10/50 dev=33
Sun Jul 11 12:32:53 CEST 2010 died
========== NEW LOG SECTION ==========
1       07/11/10 12:33:03       33 (spawning-device)    Starting... 11
1       07/11/10 12:33:03       33 (spawning-device)    Found /usr/pluto/bin/CM11A
05      07/11/10 12:33:03.366           Creating child 36 <0xb70fb6c0>
05      07/11/10 12:33:03.366           Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb70fb6c0>
05      07/11/10 12:33:03.366           Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb70fb6c0>
05      07/11/10 12:33:03.366           Creating child 37 <0xb70fb6c0>
05      07/11/10 12:33:03.366           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb70fb6c0>
05      07/11/10 12:33:03.366           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb70fb6c0>
Return code: 143
3       07/11/10 12:33:52       33 (spawning-device)    Device died... count=11/50 dev=33
Sun Jul 11 12:33:52 CEST 2010 died
========== NEW LOG SECTION ==========
1       07/11/10 12:34:02       33 (spawning-device)    Starting... 12
1       07/11/10 12:34:02       33 (spawning-device)    Found /usr/pluto/bin/CM11A
05      07/11/10 12:34:02.289           Creating child 36 <0xb71416c0>
05      07/11/10 12:34:02.289           Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb71416c0>
05      07/11/10 12:34:02.289           Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb71416c0>
05      07/11/10 12:34:02.289           Creating child 37 <0xb71416c0>
05      07/11/10 12:34:02.289           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb71416c0>
05      07/11/10 12:34:02.289           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb71416c0>
01      07/11/10 13:13:59.027           Failed sending address. <0xb613eb90>
01      07/11/10 13:28:05.375           Failed sending address. <0xb613eb90>
01      07/11/10 13:29:20.878           Failed sending address. <0xb613eb90>


I'm a noob in the ubuntu and linuxmce world so I don't really know what to do next, anybody have any suggestions?