Author Topic: SOLVED - New Media Director Orbiter Launch issue - Foxconn NT330i  (Read 1522 times)

Murdock

  • Guru
  • ****
  • Posts: 229
    • View Profile
Hello, I'm building a new MD and i've gone through the AVWizard setup and initial setup, the orbiter generates on the OSD though upon the generation I the screen is blank (X loads, though the cursor is idle in the middle). I'm not certain where to go next, here are some of the logs. Can anyone help point me in the right direction?

Code: [Select]
pluto.log
1       01/14/11 13:19:10       SetupAudioVideo (server)        Starting
1       01/14/11 13:19:13       Xconfigure (server)     Display Driver: nvidia
1       01/14/11 13:19:18       SetupAudioVideo (server)        '
1       01/14/11 13:19:18       SetupAudioVideo (server)        DBSetting: H3 Reboot:  Script Path: /usr/pluto/bin/
1       01/14/11 13:19:18       /etc/rc2.d/S99linuxmce (server) Starting X server (client: /usr/bin/xfwm4; parms: --compositor=off)
1       01/14/11 13:19:20       /etc/rc2.d/S99linuxmce (server) X server: backround; AlphaBlending: 0
1       01/14/11 13:21:02       DiskSpaceMonitor.sh (server)    Filesystem ( /mnt/device/36 ) has 135055 MB free
1       01/14/11 13:21:04       DiskSpaceMonitor.sh (server)    Filesystem ( /mnt/device/56 ) has 814915 MB free
1       01/14/11 13:22:00       /usr/pluto/bin/Spawn_Device.sh 101 (spawning-device)    14656 Dev: 101; Already Running list:
1       01/14/11 13:22:00       /usr/pluto/bin/Spawn_Device.sh 101 (spawning-device)    device: 101 ip: dcerouter cmd_line: App_Server
0       01/14/11 13:22:00       101 (spawning-device)   Entering 101
1       01/14/11 13:22:00       101 (spawning-device)   Starting... 1
1       01/14/11 13:22:00       101 (spawning-device)   Found /usr/pluto/bin/App_Server
1       01/14/11 13:22:01       /usr/pluto/bin/Spawn_Device.sh 102 (spawning-device)    14731 Dev: 102; Already Running list: 101,
1       01/14/11 13:22:01       /usr/pluto/bin/Spawn_Device.sh 102 (spawning-device)    device: 102 ip: dcerouter cmd_line: LaunchOrbiter.sh
0       01/14/11 13:22:02       102 (spawning-device)   Entering 102
1       01/14/11 13:22:02       102 (spawning-device)   Starting... 1
1       01/14/11 13:22:02       102 (spawning-device)   Found /usr/pluto/bin/LaunchOrbiter.sh
1       01/14/11 13:22:02       LaunchOrbiter (server)  Number of desktops found: 6 ; desktops activated? 1
1       01/14/11 13:22:02       LaunchOrbiter (server)  Primary desktop: 4 and secondary desktop 5
3       01/14/11 13:22:03       102 (spawning-device)   Device died... count=1/50 dev=102


run manually:
root@moon100:/usr/pluto/bin# /usr/pluto/bin/LaunchOrbiter.sh
+ /usr/pluto/bin/LaunchOrbiter.sh
WatchGyroRemote: no process killed
1       01/14/11 13:22:57       LaunchOrbiter (server)  Number of desktops found: 6 ; desktops activated? 1
1       01/14/11 13:22:57       LaunchOrbiter (server)  Primary desktop: 4 and secondary desktop 5
Copyright (C) 2004 Pluto, Inc., a Florida Corporation
www.plutohome.com
Phone: +1 (877) 758-8648
This program is distributed according to the terms of the Pluto Public License, available at:
http://plutohome.com/index.php?section=public_license
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the Pluto Public License for more details.
-----

envir_utf8: 0
WmCtrl::LowLevelCommand() : opened pDisplay=0x9dc9a38
WmCtrl::LowLevelCommand() : closed pDisplay=0x9dc9a38
envir_utf8: 0
WmCtrl::LowLevelCommand() : opened pDisplay=0x9dc9a38
Invalid type of _NET_CLIENT_LIST property.
Invalid type of _WIN_CLIENT_LIST property.
Cannot get client list properties.
(_NET_CLIENT_LIST or _WIN_CLIENT_LIST)
WmCtrl::LowLevelCommand() : closed pDisplay=0x9dc9a38
envir_utf8: 0
WmCtrl::LowLevelCommand() : opened pDisplay=0x9dc9a38
Invalid type of _NET_CLIENT_LIST property.
Invalid type of _WIN_CLIENT_LIST property.
Cannot get client list properties.
(_NET_CLIENT_LIST or _WIN_CLIENT_LIST)
WmCtrl::LowLevelCommand() : closed pDisplay=0x9dc9a38
envir_utf8: 0
envir_utf8: 0
WmCtrl::LowLevelCommand() : opened pDisplay=0x9dc9a38
WmCtrl::LowLevelCommand() : closed pDisplay=0x9dc9a38
envir_utf8: 0
WmCtrl::LowLevelCommand() : opened pDisplay=0x9dc9a38
Invalid type of _NET_CLIENT_LIST property.
Invalid type of _WIN_CLIENT_LIST property.
Cannot get client list properties.
(_NET_CLIENT_LIST or _WIN_CLIENT_LIST)
WmCtrl::LowLevelCommand() : closed pDisplay=0x9dc9a38
./Orbiter: symbol lookup error: ./Orbiter: undefined symbol: _Z15db_wrapper_initP8st_mysql
++ echo -ne '\033]0;root@moon100: /usr/pluto/bin\007'
root@moon100:/usr/pluto/bin#

102_LaunchOrbiter.sh.log
========== NEW LOG SECTION ==========
1       01/14/11 13:25:11       102 (spawning-device)   Starting... 18
1       01/14/11 13:25:11       102 (spawning-device)   Found /usr/pluto/bin/LaunchOrbiter.sh
Return code: 127
3       01/14/11 13:25:12       102 (spawning-device)   Device died... count=18/50 dev=102
Fri Jan 14 13:25:12 CST 2011 died
« Last Edit: January 16, 2011, 01:43:25 am by Murdock »

Murdock

  • Guru
  • ****
  • Posts: 229
    • View Profile
Re: New Media Director Orbiter Launch issue - Foxconn NT330i
« Reply #1 on: January 15, 2011, 03:42:00 am »
Here's the DCErouter.log on the core when this occurs:

Code: [Select]
08 01/14/11 20:41:15.070 Received Message from 102 (OnScreen Orbiter / tmp) to Infrared Plug-in(7), type 1 id  688 Command:Get Remote Control Mapping, retry none, parameters: <0x5fee0b90>
08 01/14/11 20:41:15.070   Parameter 5(Value To Assign):  <0x5fee0b90>
05 01/14/11 20:41:15.101 Socket::ReceiveData 0x9347a90 failed, bytes left 0 start: 1570000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 190 Incoming_Conn Socket 190 192.168.80.4EVENT 102 T=8 Event #102 <0x55eccb90>
05 01/14/11 20:41:15.101 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 190 192.168.80.4EVENT 102 T=8 Event #102 <0x55eccb90>
05 01/14/11 20:41:15.101 TCPIP: Closing connection to 102 (Router Dev #0) 0x9347a90 m_Socket: -1 <0x55eccb90>
05 01/14/11 20:41:15.101 Router::RemoveAndDeleteSocket 0x9347a90 102 <0x55eccb90>
05 01/14/11 20:41:15.101 Socket::ReceiveData 0x9349bd0 failed, bytes left 0 start: 1570000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 209 Incoming_Conn Socket 209 192.168.80.4EVENT 102 T=8 Event #102 <0x5fee0b90>
05 01/14/11 20:41:15.101 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 209 192.168.80.4EVENT 102 T=8 Event #102 <0x5fee0b90>
05 01/14/11 20:41:15.101 TCPIP: Closing connection to 102 (Router Dev #0) 0x9349bd0 m_Socket: -1 <0x5fee0b90>
05 01/14/11 20:41:15.101 Router::RemoveAndDeleteSocket 0x9349bd0 102 <0x5fee0b90>


Murdock

  • Guru
  • ****
  • Posts: 229
    • View Profile
Re: New Media Director Orbiter Launch issue - Foxconn NT330i
« Reply #2 on: January 15, 2011, 04:20:25 am »
Upon Manually attempting to send the infrared plugin a command from the web admin this is the output:

Code: [Select]
08 01/14/11 21:17:49.420 Received Message from 0 (unknown / ) to 7 (Infrared Plug-in / Workout Room), type 1 id 688 Command:Get Remote Control Mapping, retry none, parameters: <0x566cdb90>
08 01/14/11 21:17:49.420   Parameter 5(Value To Assign):  <0x566cdb90>
05 01/14/11 21:17:49.473 Socket::ReceiveData 0x93a5f70 failed, bytes left 0 start: 2550000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 208 Incoming_Conn Socket 208 127.0.0.1 <0x566cdb90>
05 01/14/11 21:17:49.473 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 208 127.0.0.1 <0x566cdb90>
05 01/14/11 21:17:49.473 TCPIP: Closing connection to -1003 (Router Dev #0) 0x93a5f70 m_Socket: -1 <0x566cdb90>
05 01/14/11 21:17:49.473 Router::RemoveAndDeleteSocket 0x93a5f70 -1003 <0x566cdb90>

Murdock

  • Guru
  • ****
  • Posts: 229
    • View Profile
Re: New Media Director Orbiter Launch issue - Foxconn NT330i
« Reply #3 on: January 15, 2011, 04:54:57 am »
infrared plugin log from the web admin:

Code: [Select]
08 01/14/11 21:53:41.830 Received Message from 102 (OnScreen Orbiter / Living Room/Family Room) to Infrared Plug-in(7), type 1 id  688 Command:Get Remote Control Mapping, retry none, parameters: <0x5f5d2b90>
08 01/14/11 21:53:41.830   Parameter 5(Value To Assign):  <0x5f5d2b90>
05 01/14/11 21:53:41.853 Socket::ReceiveData 0xa3a7630 failed, bytes left 0 start: 680000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 191 Incoming_Conn Socket 191 192.168.80.4EVENT 102 T=8 Event #102 <0x5edd1b90>
05 01/14/11 21:53:41.853 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 191 192.168.80.4EVENT 102 T=8 Event #102 <0x5edd1b90>
05 01/14/11 21:53:41.853 TCPIP: Closing connection to 102 (Router Dev #0) 0xa3a7630 m_Socket: -1 <0x5edd1b90>
05 01/14/11 21:53:41.853 Router::RemoveAndDeleteSocket 0xa3a7630 102 <0x5edd1b90>
05 01/14/11 21:53:41.854 Socket::ReceiveData 0xa3aa310 failed, bytes left 0 start: 680000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 192 Incoming_Conn Socket 192 192.168.80.4EVENT 102 T=8 Event #102 <0x5f5d2b90>
05 01/14/11 21:53:41.854 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 192 192.168.80.4EVENT 102 T=8 Event #102 <0x5f5d2b90>
05 01/14/11 21:53:41.854 TCPIP: Closing connection to 102 (Router Dev #0) 0xa3aa310 m_Socket: -1 <0x5f5d2b90>
05 01/14/11 21:53:41.854 Router::RemoveAndDeleteSocket 0xa3aa310 102 <0x5f5d2b90>


daballiemo

  • Guru
  • ****
  • Posts: 244
  • Full Blown Addict
    • View Profile
Re: New Media Director Orbiter Launch issue - Foxconn NT330i
« Reply #4 on: January 15, 2011, 09:19:38 am »
I presume you followed the wiki,

are you using the HDMI output? Can you list the NVidia driver version. Did you reload the router?

rgds

Han
HP N40L12.04 KVM with virt LCME8.10/10.04
MD: FoxConn NetBox 330I - Samsung LE 26 (1360* 768)
MD: M2NPV-VM dual core AMD 64/3800/2Gb/NV6150 - Samsung UE 55 C8700 (full hd, 3d)
MD: FoxConn NetBox 330I - LG 32ld350

Murdock

  • Guru
  • ****
  • Posts: 229
    • View Profile
Re: New Media Director Orbiter Launch issue - Foxconn NT330i
« Reply #5 on: January 15, 2011, 03:12:25 pm »
Hi Han,

1. Yes I followed the wiki and yes I'm using the HDMI output, this morning i'm going to test using the dvi to see if it does anything different.

2. nVidia driver xorg seems to be using is 195 (from xorg.conf):
Code: [Select]
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
        compiled for 4.0.2, module version = 1.0.0
        Module class: X.Org Server Extension
(II) NVIDIA GLX Module  195.36.15  Thu Mar 11 23:39:48 PST 2010
(II) Loading extension GLX
(II) LoadModule: "int10"


(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
        compiled for 1.4.99.905, module version = 1.3.1
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 2.1
(II) v4l driver for Video4Linux
(II) NVIDIA dlloader X Driver  195.36.15  Thu Mar 11 22:01:49 PST 2010
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) NVIDIA X compatibility module for ABI 4.0 built from git commit 98249dfa98b53a238b7d881beb5ec8b85f28ecd0 (server-1.5-branch)
(II) X log verbosity: 9
(II) Primary Device is: PCI 03@00:00:0
(WW) Falling back to old probe method for v4l
(II) Loading sub module "fb"
(II) LoadModule: "fb"


3. Yes, I've also rebooted the server.

Murdock

  • Guru
  • ****
  • Posts: 229
    • View Profile
Re: New Media Director Orbiter Launch issue - Foxconn NT330i
« Reply #6 on: January 15, 2011, 04:40:39 pm »
Looking at the router log, it appears this is the successful output:

Code: [Select]
08      01/15/11 0:09:49.123            Received Message from 87 (^[[36;1miPhone Proxy Orbiter / Living Room/Family Room^[[0m) to Infrared Plug-in(7), type 1 id  688 Command:^[[35;1mGet Remote Control Mapping^[[0m, retry none, parameters: <0x722b9b90>
08      01/15/11 0:09:49.123              Parameter 5(Value To Assign):  <0x722b9b90>
08      01/15/11 0:09:49.124            Received Message from 84 (^[[36;1miPad Proxy Orbiter / Living Room/Family Room^[[0m) to Infrared Plug-in(7), type 1 id  688 Command:^[[35;1mGet Remote Control Mapping^[[0m, retry none, parameters: <0x712b7b90>
08      01/15/11 0:09:49.124              Parameter 5(Value To Assign):  <0x712b7b90>
07      01/15/11 0:09:49.129            Event #65 has no handlers <0xa1eefb90>

Murdock

  • Guru
  • ****
  • Posts: 229
    • View Profile
Re: SOLVED - New Media Director Orbiter Launch issue - Foxconn NT330i
« Reply #7 on: January 16, 2011, 01:43:07 am »
Apparantly my beta build was too old and lost the ability to add media directors between july of 09 and today. Upon rebuilding the core the MD now successfully builds. I have had an issue on audio over HDMI, just had to uncheck the AC3 passthrough in the web admin, reloaded the router and everything works great!
« Last Edit: January 16, 2011, 01:57:30 am by Murdock »

posde

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 3012
  • Wastes Life On LinuxMCE Since 2007
    • View Profile
    • My Home
Re: SOLVED - New Media Director Orbiter Launch issue - Foxconn NT330i
« Reply #8 on: January 16, 2011, 12:19:18 pm »
Good to know you fixed it