Messages

hi

i'm having troubles installing a zwave device which is supposed to be working in LinuxMCe. but the problem is that after it is detected and installed, when I download the configuration from the controller I can't send any commands to light, so the lights aren't working. these are the logs:
DCErouter.log

07      08/13/08 15:23:47.036           Received Message from 91 (ZWave / Living Room) to -1001 (unknown / ), type 2 id 55 Eventownload Config Done, retry none, parameters: <0x806e9b90>
07      08/13/08 15:23:47.036             Parameter 12(Error Message): DEVICE DIDN'T RESPOND OR ZWAVE ERRORS <0x806e9b90>
07      08/13/08 15:23:51.089           Event #9 has no handlers <0x6dec4b90>

Zwave.log
========== NEW LOG SECTION ==========
1       08/13/08 15:07:55       81 (spawning-device)    Starting... 1
1       08/13/08 15:07:55       81 (spawning-device)    Found /usr/pluto/bin/ZWave
01      08/13/08 15:07:56.153           asynchThread started <0xb78d46c0>
05      08/13/08 15:08:01.014           ### Go to timeout queue <0xb68d1b90>
05      08/13/08 15:08:01.014           ### execute the next job from timeout queue <0xb68d1b90>
05      08/13/08 15:08:01.014           ZWJobInitialize::timeoutHandler <0xb68d1b90>
05      08/13/08 15:08:06.018           ### Go to timeout queue <0xb68d1b90>
05      08/13/08 15:08:06.018           ### execute the next job from timeout queue <0xb68d1b90>
05      08/13/08 15:08:06.019           ZWJobInitialize::timeoutHandler <0xb68d1b90>
05      08/13/08 15:08:07.822           Creating child 83 <0xb78d46c0>
05      08/13/08 15:08:07.822           Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb78d46c0>
05      08/13/08 15:08:07.822           Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb78d46c0>
05      08/13/08 15:08:07.822           Creating child 90 <0xb78d46c0>
05      08/13/08 15:08:07.822           Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb78d46c0>
05      08/13/08 15:08:07.822           Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb78d46c0>
05      08/13/08 15:09:02.039           -------------------------- Job Timeout 0x80e0ea8 _________ <0xb68d1b90>
05      08/13/08 15:19:26.803           Got a reload command from 0  <0xb50ceb90>
05      08/13/08 15:19:27.459           void ClientSocket::Disconnect() on this socket: 0x80a5518 (m_Socket: 7) <0xb78d46c0>
Return code: 2
2       08/13/08 15:19:27       81 (spawning-device)    Device requests restart... count=1/50 dev=81
2       08/13/08 15:19:27       81 (spawning-device)    Device was disabled or removed. Stopping and marking as not running.

dmesg and lsmod shows the drivers are installed.
can someone help me with this?thx

in /var/log/pluto is a log file called Xine_Player.log. can u paste the output when the dvd stops?

I have resolved my issues...
I go in advanced setting of media director, click on "view" for device template "Generic PC as MD", and valid "Allowed to modify" in Current Data #233 (+ save page).
In advanded setting i set "LMCE_MD_u0710_i386" in "Model" parameter.
I make a "Rebuilt Image" (maybe it's not necessary), Quick reload and my MD (Fiire Station) start.

But i have another problem. Fiire Station have a Via Unichrome Pro graphic chipset.
I can't start Xserver when "via" is setting in Xorg.conf.
I must set "vesa" to start.
I can't resolved this problem since i use LMCE. I have seen in mantis the same problem and i think that is resolved with 7.10 release.

Last question : When i add a media director, i can choose Fiire Station, but i never can boot with this config. When i boot with Fiire MD, I have red message "Failed Setup_config.sh". Do you have any explain?

Tks

can you please run bash -x Setup_config.sh in a terminal and paste the output? it should show you when the it stops, and what error is there.

can you please post the entire message before stop? it seems to be a problem with loading the drivers. personally, I saw this error when trying to setup a MD with nvidia network card.

maybe it could be helpful to force the mounting as rw of the diskless md. you should put just for a test the option rw into this line:
192.168.0.2:/usr/pluto/diskless/113 / nfs initr,udp,rsize=32768,wsize=32768,retrans=10,timeo=50 1 1
it should be after the miodification:
192.168.0.2:/usr/pluto/diskless/113 / nfs initr,udp,rw,rsize=32768,wsize=32768,retrans=10,timeo=50 1 1

do the same thing for the other line that are related to the md.

maybe you could try to modify in /etc/fstab the lines for every partition on your hdd. instead of UUID put the device correspondent to that UUID(/dev/sda1,2....).

if you have a powerful computer you don't have to worry very much about which filesystem  you are using. but, another good recommendation could be reiserfs which gave me better results than ext3.

Just out of curiosity, are the via Unichrome drivers part of the Ubuntu install?  Will LinuxMCE automatically install these when it detects a via MD? If not, how is fiire using them?

fiire uses for via station a licensed driver specially built for fiire. and it is not based on unichorme or via drivers

also you can post the output of cat /etc/fstab or mount to see if there are rw options. also, post the output of startx too see for any error messages. it is possible that the xorg.conf might be incorrect.

where is it stopping? and what's the message?

having 2 ip addreses does not mean that you have dhcp enabled. it's just an ip allocated to that card.

it must work (i've tested it in Europe). i suppose that you will not be able to use an epg system but in rest it will be ok. but you must have a tv card compatible with linux.

this issue appears sometimes when the partitions are not well made. also, another possible cause could be the sata controller. maybe you have to modify in BIOS instead of sata use parallel ata( or something like that).

i don't know what kind of chipset your tuner has. if it is a philips it should work fine. go to computing>mythtv setup and then go to capture cards and choose analog v4 capture card (also it has to be listed at Probed info).

have you read this http://www.mythtv.org/wiki/index.php/Hauppauge_WinTV_Nova-T_500_PCI?