Hello wierdbeard65,

When I look on the Alt-F12 screen (just after the black screen) I see nothing that talk to me.
But, I have check the syslog file and search the different errors it give me.

Here the result:

Code:

root@moon74:~# cat /var/log/syslog.0 | grep error
Sep  5 10:14:04 moon74 kernel: [ 1727.279049] OrbiterGL[29732]: segfault at 94 ip b78ba305 sp b6200ff0 error 4 in libstdc++.so.6.0.10[b7823000+e3000]
Sep  5 10:14:55 moon74 kernel: [ 1778.110046] OrbiterGL[30502]: segfault at 94 ip b774f305 sp b6095ff0 error 4 in libstdc++.so.6.0.10[b76b8000+e3000]
Sep  5 11:15:14 moon74 automount[22945]: >> mount error 6 = No such device or address
Sep  5 11:15:14 moon74 automount[23148]: >> mount error 6 = No such device or address
Sep  5 12:15:01 moon74 kernel: [ 4152.530076]  CIFS VFS: Send error in SessSetup = -13
Sep  5 12:15:01 moon74 kernel: [ 4152.605581]  CIFS VFS: Send error in SessSetup = -13
Sep  5 12:15:01 moon74 kernel: [ 4152.608827]  CIFS VFS: Send error in SessSetup = -13
Sep  5 12:15:01 moon74 kernel: [ 4152.615673]  CIFS VFS: Send error in SessSetup = -13
Sep  5 12:15:01 moon74 kernel: [ 4152.618250]  CIFS VFS: Send error in SessSetup = -13
Sep  5 12:15:01 moon74 kernel: [ 4152.628219]  CIFS VFS: Send error in SessSetup = -13
Sep  5 18:01:28 moon74 kernel: [24939.604166]  CIFS VFS: Send error in SessSetup = -13
Sep  5 18:01:28 moon74 automount[25501]: >> mount error 13 = Permission denied
Sep  5 18:13:18 moon74 automount[14243]: >> mount error 111 = Connection refused
Sep  5 20:18:05 moon74 automount[19579]: >> mount error 6 = No such device or address
Sep  5 22:06:05 moon74 automount[30536]: >> mount error 6 = No such device or address
Sep  6 01:00:07 moon74 automount[16242]: >> mount error 6 = No such device or address
Sep  6 02:00:12 moon74 automount[15730]: >> mount error 6 = No such device or address
root@moon74:~#

It can be a  OrbiterGL segfault that caused my problem ?
I've installed so many times the system, I hope it is this and that a solution can be found.

Regards,
Philippe

Hello shakeel,

I have downgrade the nvidia driver to 173 without result.
I have not use "envyng" but the system "hardware drivers" kde4 application.

I don't think it is a nvidia driver issue.

Regards,
Philippe

Hi Peter,

If I compare for exemple 2 MD, I can see that the bad MD has only run 3 devices (HAL, App Server and Launch Orbiter).
I suppose that it can't run more because it stop or wait after something to finish.
I would have the media director setup (sarah) but I've not.
I can complete the setup of this MD and I suppose that the missing devices can't run before that setup.

   
Is this logical?

Regards,
Philippe

Hello Peter,

I did not give an answer because I do not know exactly what to reply.
I don't understand how to do this compare.
This MD is not really different than the others, so the devices are the same for me.

Regards,
Philippe

Hi Peter,

Here the inside of my Spawn_Device.log:

Code:

root@moon74:~# cat /var/log/pluto/Spawn_Device.log   
Sun Aug 30 17:53:06 CEST 2009 Spawn_Device 75 dcerouter App_Server
9830 Sun Aug 30 17:53:06 CEST 2009 WaitLock 'Spawn_Device' (75)
9830 Sun Aug 30 17:53:06 CEST 2009 WaitLock 'Spawn_Device' (75) success
Sun Aug 30 17:53:06 CEST 2009 About to be run: 75
9830 Sun Aug 30 17:53:06 CEST 2009 Unlock 'Spawn_Device' (75)
9830 Sun Aug 30 17:53:06 CEST 2009 Unlock 'Spawn_Device' (75) success
Sun Aug 30 17:53:08 CEST 2009 Spawn_Device 76 dcerouter LaunchOrbiter.sh
9974 Sun Aug 30 17:53:08 CEST 2009 WaitLock 'Spawn_Device' (76)
9974 Sun Aug 30 17:53:08 CEST 2009 WaitLock 'Spawn_Device' (76) success
Sun Aug 30 17:53:08 CEST 2009 About to be run: 76
9974 Sun Aug 30 17:53:08 CEST 2009 Unlock 'Spawn_Device' (76)
9974 Sun Aug 30 17:53:08 CEST 2009 Unlock 'Spawn_Device' (76) success
Sun Aug 30 17:53:12 CEST 2009 Spawn_Device 78 dcerouter HAL
10161 Sun Aug 30 17:53:12 CEST 2009 WaitLock 'Spawn_Device' (78)
10161 Sun Aug 30 17:53:12 CEST 2009 WaitLock 'Spawn_Device' (78) success
Sun Aug 30 17:53:12 CEST 2009 About to be run: 78
10161 Sun Aug 30 17:53:12 CEST 2009 Unlock 'Spawn_Device' (78)
10161 Sun Aug 30 17:53:12 CEST 2009 Unlock 'Spawn_Device' (78) success
Mon Aug 31 22:00:01 CEST 2009 Spawn_Device 75 dcerouter App_Server
9595 Mon Aug 31 22:00:01 CEST 2009 WaitLock 'Spawn_Device' (75)
9595 Mon Aug 31 22:00:01 CEST 2009 WaitLock 'Spawn_Device' (75) success
Mon Aug 31 22:00:01 CEST 2009 About to be run: 75
9595 Mon Aug 31 22:00:01 CEST 2009 Unlock 'Spawn_Device' (75)
9595 Mon Aug 31 22:00:01 CEST 2009 Unlock 'Spawn_Device' (75) success
Mon Aug 31 22:00:04 CEST 2009 Spawn_Device 76 dcerouter LaunchOrbiter.sh
10006 Mon Aug 31 22:00:04 CEST 2009 WaitLock 'Spawn_Device' (76)
10006 Mon Aug 31 22:00:04 CEST 2009 WaitLock 'Spawn_Device' (76) success
Mon Aug 31 22:00:04 CEST 2009 About to be run: 76
10006 Mon Aug 31 22:00:04 CEST 2009 Unlock 'Spawn_Device' (76)
10006 Mon Aug 31 22:00:04 CEST 2009 Unlock 'Spawn_Device' (76) success
Mon Aug 31 22:00:09 CEST 2009 Spawn_Device 78 dcerouter HAL
10497 Mon Aug 31 22:00:09 CEST 2009 WaitLock 'Spawn_Device' (78)
10497 Mon Aug 31 22:00:09 CEST 2009 WaitLock 'Spawn_Device' (78) success
Mon Aug 31 22:00:09 CEST 2009 About to be run: 78
10497 Mon Aug 31 22:00:09 CEST 2009 Unlock 'Spawn_Device' (78)
10497 Mon Aug 31 22:00:10 CEST 2009 Unlock 'Spawn_Device' (78) success
root@moon74:~#

About the increase of loglevel, which one should I choose ?

Have a nice day !
Philippe

Hello Peter,

If I look to the MD (moon74) locks directory I find pluto_spawned_local_devices.txt.
The content is:
75
76
78

This morning this MD freeze my ssh session when I want to go to its pluto directory from the dcerouter.
Yesterday I could go there without problem

ps ax | grep Orbiter give me:

Code:

root@moon74:~# ps ax | grep Orbiter
 7462 pts/6    R+     0:00 grep Orbiter
 9973 ?        Ss     0:03 /usr/bin/SCREEN -d -m -S OnScreen_Orbiter76 /usr/pluto/bin/Spawn_Device.sh 76 dcerouter LaunchOrbiter.sh
 9974 pts/4    Ss+    0:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 76 dcerouter LaunchOrbiter.sh
11689 pts/4    S+     0:00 /bin/bash /usr/pluto/bin/LaunchOrbiter.sh -d 76 -r dcerouter -l /var/log/pluto/76_LaunchOrbiter.sh.log
11719 pts/4    DLl+   0:31 ./OrbiterGL -d 76 -r dcerouter -l /var/log/pluto/76_LaunchOrbiter.sh.log

I have not made a compare between to MD logs files.
If I have some time this evening I will do that.

Regards,
Philippe

Hello Peter,

I have those logs in the /var/log/pluto moon directory (MD#1):

Code:

root@moon74:~# ls -l /var/log/pluto/
total 14280                         
-rw-r--r-- 1 root   root         15354 Aug 30 09:08 75_App_Server.log
-rw-r--r-- 1 root   root          2101 Aug 29 10:04 76_LaunchOrbiter.sh.log
-rw-r--r-- 1 root   root          8690 Aug 30 09:08 78_HAL.log             
-rw-r--r-- 1 root   root        285153 Aug 28 18:44 AVWizard.log           
-rw-r--r-- 1 root   root        437385 Aug 29 16:41 Config_Device_Changes.log
-rw-r--r-- 1 root   root             0 Aug 28 18:44 ConfirmDependencies.log 
-rw-r--r-- 1 root   root           575 Aug 28 14:27 CreateDevice.log         
-rw-r--r-- 1 root   root           432 Aug 29 10:03 LMCEUpdate.log           
-rw-r--r-- 1 root   root          3164 Aug 29 12:50 LaunchManager.log       
-rw-r--r-- 1 root   root         12834 Aug 29 16:41 LaunchManager.progress.log
-rw-r--r-- 1 root   root          1210 Aug 29 20:29 SetupUsers_Homes.log     
-rw-r--r-- 1 root   root          2332 Aug 29 10:04 Spawn_Device.log         
-rwxr-xr-T 1 root   root          7566 Aug 29 08:33 Spawn_cdc_13156.log       
-rwxr-xr-T 1 root   root          7566 Aug 29 09:05 Spawn_cdc_19486.log       
-rwxr-xr-T 1 root   root          7566 Aug 29 09:08 Spawn_cdc_20118.log       
-rwxr-xr-T 1 root   root          7557 Aug 29 14:51 Spawn_cdc_2514.log       
-rwxr-xr-T 1 root   root          7557 Aug 29 16:41 Spawn_cdc_6004.log       
-rwxr-xr-T 1 root   root          1251 Aug 29 08:35 Spawn_not named_13409.log
-rwxr-xr-T 1 root   root          1251 Aug 29 08:50 Spawn_not named_16471.log
-rwxr-xr-T 1 root   root          2409 Aug 29 20:29 Spawn_not named_19357.log
-rwxr-xr-T 1 root   root          2409 Aug 29 17:06 Spawn_not named_2102.log 
-rwxr-xr-T 1 root   root          1251 Aug 29 09:17 Spawn_not named_21997.log
-rwxr-xr-T 1 root   root          1251 Aug 29 09:34 Spawn_not named_25841.log
-rwxr-xr-T 1 root   root          1251 Aug 29 07:56 Spawn_not named_4689.log 
-rwxr-xr-T 1 root   root          1251 Aug 29 08:05 Spawn_not named_6889.log 
-rwxr-xr-T 1 root   root          1251 Aug 29 08:16 Spawn_not named_9455.log 
-rwxr-sr-T 1 root   root             0 Aug 29 10:04 Spawn_storagedevices_11113.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 10:04 Spawn_storagedevices_11114.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 08:27 Spawn_storagedevices_12087.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 08:27 Spawn_storagedevices_12088.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 30 09:08 Spawn_storagedevices_16569.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 30 09:08 Spawn_storagedevices_16570.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 09:11 Spawn_storagedevices_20895.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 09:11 Spawn_storagedevices_20896.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 09:20 Spawn_storagedevices_23300.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 09:20 Spawn_storagedevices_23316.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 14:51 Spawn_storagedevices_2366.log                                                                               
-rwxr-sr-T 1 root   root             0 Aug 29 14:51 Spawn_storagedevices_2367.log                                                                               
-rwxr-sr-T 1 root   root             0 Aug 29 12:50 Spawn_storagedevices_24029.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 12:50 Spawn_storagedevices_24030.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 09:25 Spawn_storagedevices_24334.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 09:25 Spawn_storagedevices_24336.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 09:36 Spawn_storagedevices_26633.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 09:36 Spawn_storagedevices_26637.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 28 18:47 Spawn_storagedevices_26973.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 28 18:47 Spawn_storagedevices_26974.log                                                                             
-rwxr-sr-T 1 root   root             0 Aug 29 20:19 Spawn_storagedevices_7081.log                                                                               
-rwxr-sr-T 1 root   root             0 Aug 29 20:19 Spawn_storagedevices_7084.log                                                                               
-rw-r--r-- 1 root   root         92782 Aug 30 09:12 StorageDevices.log         
-rw-r--r-- 1 root   root             0 Aug 29 20:29 StorageDevices_Symlinks.log
-rw-r--r-- 1 root   root           432 Aug 29 10:03 UpdateHelper.log           
-rw-r--r-- 1 root   root             0 Aug 28 18:47 UpdateMedia.log             
-rw-r--r-- 1 root   root             0 Aug 28 17:52 WatchGyro.log               
-rw-r--r-- 1 root   root             0 Aug 28 18:43 Xconfigure.log             
-rw-r--r-- 1 root   root           626 Aug 28 18:41 avremote_detect.log         
-rw-r--r-- 1 root   root           239 Aug 28 18:44 avwizard_setup_av.log       
-rw-r--r-- 1 root   root            76 Aug 29 09:18 deaths                     
-rw-r--r-- 1 root   root            70 Aug 29 09:18 died_76_76                 
-rw-r--r-- 1 mythtv haldaemon      159 Aug 29 20:04 donerecording.log           
-rw-r--r-- 1 root   root         33488 Aug 30 00:01 getxmls.log                 
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-add-software.postinst.postinst.Fri, 28 Aug 2009 12:27:21 +0000.log                           
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-app-server.postinst.postinst.Fri, 28 Aug 2009 12:27:11 +0000.log                             
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-boot-scripts.postinst.postinst.Fri, 28 Aug 2009 12:27:45 +0000.log                           
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-createdevice.postinst.postinst.Fri, 28 Aug 2009 12:27:46 +0000.log                           
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-dcecommon.postinst.postinst.Fri, 28 Aug 2009 12:27:21 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:28 kernmod.pluto-disc-drive-functions.postinst.postinst.Fri, 28 Aug 2009 12:28:38 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-disk-monitor.postinst.postinst.Fri, 28 Aug 2009 12:27:21 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-libserial.postinst.postinst.Fri, 28 Aug 2009 12:27:21 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:28 kernmod.pluto-mythtv-player.postinst.postinst.Fri, 28 Aug 2009 12:28:23 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 17:54 kernmod.pluto-nvidia-video-drivers.postinst.postinst.Fri, 28 Aug 2009 17:54:34 +0200.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-orbiter.postinst.postinst.Fri, 28 Aug 2009 12:27:46 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-pluto-main-db.postinst.postinst.Fri, 28 Aug 2009 12:27:21 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:28 kernmod.pluto-pluto-media-db.postinst.postinst.Fri, 28 Aug 2009 12:28:38 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-plutoutils.postinst.postinst.Fri, 28 Aug 2009 12:27:21 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-raid-tools.postinst.postinst.Fri, 28 Aug 2009 12:27:22 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-sdl-helpers.postinst.postinst.Fri, 28 Aug 2009 12:27:22 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-serializeclass.postinst.postinst.Fri, 28 Aug 2009 12:27:21 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-simplephone.postinst.postinst.Fri, 28 Aug 2009 12:27:22 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-storage-devices.postinst.postinst.Fri, 28 Aug 2009 12:27:21 +0000.log
-rw-r--r-- 1 root   root            66 Aug 28 14:27 kernmod.pluto-xine-player.postinst.postinst.Fri, 28 Aug 2009 12:27:21 +0000.log
-rw-r--r-- 1 root   root        254741 Aug 30 09:12 pluto.log
-rw-r--r-- 1 root   root           977 Aug 30 09:08 running.pids
-rw-r--r-- 1 root   root      13204368 Aug 30 09:12 umount-wrapper.log
-rw-r--r-- 1 root   root          5883 Aug 28 18:44 xorg.conf.log

If you want that I post one of them, tell me.
The logs I post previous msg where cut to not clutter this topic.

About ping dcrouter from the bad moon, no problem. The resolving work.

My network setup is the same I have before with lmce 710.
What do you want to know exactly ?

Regards,
Philippe

Hello Colin,

Top give me only 5% cpu usage on the bad MD.

Here some logs:

pluto.log

Code:

t/device/73 ) has 1194328 MB free                                               
2       08/29/09 14:51:14       75 (spawning-device)    Device requests restart... count=1/50 dev=75                                                           
2       08/29/09 14:51:15       78 (spawning-device)    Device requests restart... count=1/50 dev=78                                                           
1       08/29/09 14:51:22       75 (spawning-device)    Starting... 1           
1       08/29/09 14:51:22       75 (spawning-device)    Found /usr/pluto/bin/App_Server                                                                         
1       08/29/09 14:51:23       78 (spawning-device)    Starting... 1           
1       08/29/09 14:51:23       78 (spawning-device)    Found /usr/pluto/bin/HAL
1       08/29/09 14:54:03       DiskSpaceMonitor.sh (server)    Filesystem ( /mnt/device/72 ) has 1194328 MB free                                               
1       08/29/09 14:54:07       DiskSpaceMonitor.sh (server)    Filesystem ( /mnt/device/73 ) is ReadOnly                                                       
1       08/29/09 14:54:07       DiskSpaceMonitor.sh (server)    Filesystem ( /mnt/device/73 ) has 1194328 MB free                                               
1       08/29/09 14:57:02       DiskSpaceMonitor.sh (server)    Filesystem ( /mnt/device/72 ) has 1194328 MB free             

App_Server.log

Code:

========== NEW LOG SECTION ==========
1       08/29/09 14:51:22       75 (spawning-device)    Starting... 1
1       08/29/09 14:51:22       75 (spawning-device)    Found /usr/pluto/bin/App_Server
05      08/29/09 14:51:25.262           Finished spawning 'storagedevices': /usr/pluto/bin/StorageDevices_Radar.sh . PID: 2366 <0xb680ab90>
05      08/29/09 14:51:25.272           Finished spawning 'storagedevices': /usr/pluto/bin/StorageDevices_Radar.sh . PID: 2367 <0xb680ab90>
05      08/29/09 14:51:25.666           PID 2366 exited with code 0 <0xb680ab90>
05      08/29/09 14:51:26.809           PID 2367 exited with code 0 <0xb680ab90>
05      08/29/09 14:51:27.861           Finished spawning 'cdc': /usr/pluto/bin/Config_Device_Changes.sh F      StartLocalDevice        Alert. PID: 2514 <0xb680ab90>
05      08/29/09 14:51:42.670           PID 2514 exited with code 0 <0xb680ab90>
05      08/29/09 16:41:18.313           Finished spawning 'cdc': /usr/pluto/bin/Config_Device_Changes.sh F      StartLocalDevice        Alert. PID: 6004 <0xb680ab90>
05      08/29/09 16:41:24.162           PID 6004 exited with code 0 <0xb680ab90>
05      08/29/09 17:06:40.117           Finished spawning '': /usr/pluto/bin/StorageDevices_Setup.sh --nocascade. PID: 2102 <0xb680ab90>
05      08/29/09 17:06:59.883   

LaunchOrbiter.sh.log

Code:

========== NEW LOG SECTION ==========
1       08/29/09 09:18:37       76 (spawning-device)    Starting... 3
1       08/29/09 09:18:37       76 (spawning-device)    Found /usr/pluto/bin/LaunchOrbiter.sh
05      08/29/09 9:18:37.925            will overwrite wm window id // void X11wrapper::Assign_WmWindow(Window) <0xb625bb80>
== ATTEMPT FRESH START ==
1       08/29/09 10:04:24       /usr/pluto/bin/Spawn_Device.sh 76 (spawning-device)     10828 Dev: 76; Already Running list: 75,
== FRESH START ==
1       08/29/09 10:04:24       /usr/pluto/bin/Spawn_Device.sh 76 (spawning-device)     device: 76 ip: dcerouter cmd_line: LaunchOrbiter.sh
0       08/29/09 10:04:24       76 (spawning-device)    Entering 76
========== NEW LOG SECTION ==========
1       08/29/09 10:04:25       76 (spawning-device)    Starting... 1
1       08/29/09 10:04:25       76 (spawning-device)    Found /usr/pluto/bin/LaunchOrbiter.sh

Hal.log

Code:

========== NEW LOG SECTION ==========
1       08/29/09 12:50:06       78 (spawning-device)    Starting... 1
1       08/29/09 12:50:06       78 (spawning-device)    Found /usr/pluto/bin/HAL
05      08/29/09 14:51:14.070           Got a reload command from 0  <0xb5fc8b90>
05      08/29/09 14:51:14.426           PlutoHalD::timeoutHandler ############ QUIT ++++++++++++++ <0xb77cbb90>
05      08/29/09 14:51:15.258           void ClientSocket::Disconnect() on thissocket: 0x8eaed00 (m_Socket: 7) <0xb784c8d0>
Return code: 2
2       08/29/09 14:51:15       78 (spawning-device)    Device requests restart... count=1/50 dev=78
Sat Aug 29 14:51:15 CEST 2009 Restart
========== NEW LOG SECTION ==========
1       08/29/09 14:51:23       78 (spawning-device)    Starting... 1
1       08/29/09 14:51:23       78 (spawning-device)    Found /usr/pluto/bin/HAL
root@moon74:~#

if you find something I'm interested ! ;-)
Today I do not know what to do more than I've done.

Regards,
Philippe

Thom,

I've just used the lasted build (complete re-install from yesterday) and have the same problem with 2 MDs.
It does not resolve this black screen with mouse pointer.

I continue to search but for the moment I have no success :-(

Regards,
Philippe

Bonsoir Peter,

Yes I think that better is to begin from the basics.
I'll repeat the manipulations (tests) tomorrow and post the results.
And all the logs in the diskless section and core will be erased to start again.

Regards,
Philippe

Hello Enricome,

"http://192.168.80.1/pluto_admin" does'nt exist anymore with 810 and I suppose you would say "http://192.168.80.1/lmce-admin".
I ve test with a existing user (not me) but after showing the device tree, I don't see any "extra core".
Can you please give more informations, I don't understand what you would suggest ?

Thank's,

Philippe

Bonjour Peter,

It's ok.... for apt-cacher-ng.

I've update the MDs and have retrive the "Starting device xxx" messages.
But it does not resolve my orbiter display problem.

So the solution must be found elsewhere.

Regards,
Philippe

Hello Peter,

I have try 2 things yesterday.

An image rebuild and a new MD install after deleting the bad MD.

No success. :-(

The core was upgraded with alpha 2.30 (apt-get update + apt-get dist-upgrade).
There was an improvement on AVwizard because now it appears directly on the TV but i suppose it is the result of the updates.
But I no longer get the "Starting device xxxx" messages on the screen.
I've try a update on the MD but I have some errors:

Code:

root@moon108:~# apt-get update                 
Ign file: ./ Release.gpg                       
Err http://fr.archive.ubuntu.com intrepid Release.gpg
  Could not connect to localhost:3142 (127.0.0.1). - connect (111 Connection refused)                                                                           
Err http://fr.archive.ubuntu.com intrepid-updates Release.gpg                   
  Could not connect to localhost:3142 (127.0.0.1). - connect (111 Connection refused)                                                                           

etc....

I have not taken the time to look further.

Regards,
Philippe

Hello Peter,

Yes your right.
The MD Garage is missing because I've reinstall completly lmce core a few days ago (but this MD worked).

The MDs that not working are "PC Salon - MD#1" and 'PC Kimberley - MD#4"

About your last suggestions, I'll test those tomorow.

Regards,
Philippe

Thom,
   
Is this what you want?

Code:

My Devices
CORE
DCERouter
File Grids Plug-in
General Info Plug-in
Climate Plug-in
Datagrid Plug-in
Infrared Plug-in
Lighting Plug-in
Orbiter Plug-in
Media Plug-in
Telecom Plug-in
Event Plug-in
Security Plug-in
Plug And Play Plug-in
Xine Plug-in
MythTV Plug-In
App Server
HAL
UPnP Server
Asterisk
Text To Speech
The core/hybrid
OnScreen Orbiter
Orbiter Embedded Phone
Xine Player
Photo Screen Saver
MPlayer Player
MythTV Player
ZWave
ZWave Embedded Climate Interfa
ZWave Embedded Security Interf
ZWave Controller
ZWave Controller
Plafond
Ventilateur
VR Salon
VR S. a Manger
VR Cuisine
STOCKRAID - STOCKRAID
Video
Musique
Motion Wrapper
Camera Facade
Camera Terrasse
HDHomeRun
Tuner 1
Tuner 0
PC S. de Douche
App Server
OnScreen Orbiter
Orbiter Embedded Phone
Xine Player
Photo Screen Saver
MPlayer Player
MythTV Player
GO Cordless GC1005M
HAL
Disk Drive
External Media Identifier
PC Home Cinema
App Server
OnScreen Orbiter
Orbiter Embedded Phone
Xine Player
Photo Screen Saver
MPlayer Player
MythTV Player
HAL
USB UIRT 0038
USB UIRT Embedded Transmit
Windows XP MC Remote (USBUIRT)
Videoprojecteur
Orbiter Webdt 366
Orbiter N810
PC Kimberley
App Server
OnScreen Orbiter
Orbiter Embedded Phone
Xine Player
MPlayer Player
MythTV Player
HAL
Disk Drive
External Media Identifier
PC Salon
App Server
OnScreen Orbiter
Orbiter Embedded Phone
Xine Player
MPlayer Player
MythTV Player
HAL

      
If not, how can I do that ?

Thank's,
Philippe