LinuxMCE Forums
General => Installation issues => Topic started by: pga57 on August 18, 2009, 10:14:04 am
-
Hi,
I need some help to resolve black screens on 2 of my 6 MDs.
One with a nividia 6200LE video card (TV connected) and the other with an onboard 7100 nvidia (VGA connected).
The AVwizard steep worked with no problem.
I have the black screen (with white cursor) before Sarah and the location configuration.
I've look at all the msgs and wiki articles but don't find the solution.
The 2 MDs worked with Lmce 710.
I have regenerate the orbiters, modify the xorg.conf, switch the xorg.conf with another MD that work, rebuild the MD image, add the 810 updates, downgrade the nvidia driver, etc...
I don't find :-(
How can I resolve this ?
Thank's !
Philippe
-
if X isn't starting then the first step is always to review your /var/log/Xorg.0.log file... read through it carefully for any errors that might indicate why it was unable to connect to the display... usually a valid mode was not found or the driver isn't installed/working properly. This should give you clues as to how to modify your xorg.conf or what driver to install. Either way, if X can't start, nothing else in LMCE will work... so that is probably your blockage...
-
Humm... I've look at the Xorg.0.log and I think it is not those errors that cause my black screen:
dcerouter_1001027:~# cat /usr/pluto/diskless/72/var/log/Xorg.0.log | grep '(EE)'
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
What is the "NewInputDeviceRequest" ?
I have the same error on other MDs and they work very well.
I think the problem come after the X start.
On the screen I have for a few millisecond the orbiter creation screen (I suppose it because it is really quick) and it go away and nothing else.
When I click on the mouse, same things. It come for a few millisecond and go away.
It is very strange.
So do you have another suggestion I can look for ?
Philippe
Philippe
-
Hi,
I saw that you regenerated the orbiter, rebuilt the MD, etc. but have you tried deleting the MD and allowing it to be rediscovered?
-
Yes, I have try to delete one and rediscovered it but the result was the same.
What append after the AVwizard ? (first I have a cross and after a white cursor, so X is started)
Is there a log file I can look to find (and understand) the steep that block the MD build or launch process ?
Something is wrong but to find it.....
Thank's for your suggestions.
Philippe
-
Hi,
So your screen gets to the grey or blank screen with cursor...
...then go to webadmin
...select the Orbiter that belongs to the MD and do full regen
...watch the MD progress regen status - step 1 of 2 building screen 1 of xxx.
After about 20 - 25 minutes Orbiter Generation finished message is presented.
MD screen is black - no cursor.
On the Core from main menu do Quick reload.
So, I guess I'm saying do a full regen and watch it build. When finished do a quick regen.
After the full regen/quick reload it might still be necessary to reboot the MD.
-
Hello Pigdog,
thank's for your suggestion but it give not the result i wanted.
I allways have this black screen with white cursor after full regen and all the steps you proposed.
I begin to despair because it is not coherent.
Philippe
-
Dear Philippe,
what type of UI did you select in AVWizard?
OpenGL or Alphablending?
If you have chosen one of them try to go back to basic UI1
As this could be a graphic driver issue with OpenGL
I had similar issues as with new Kubuntu some older drivers are not supported
Rgds
Peter
-
Hello Peter,
I've just change the orbiter UI from UI2 to UI1 (after a rebuild image and a new AVwizard configuration) and have allways the same result.
I've look at the logs but I don't find something wrong (I'm not a expert).
Here my MD pluto log.
Do you find something that can explain the problem I have ?
1 08/19/09 08:33:10 /usr/pluto/bin/Spawn_Device.sh 99 (spawning-device) device: 99 ip: dcerouter cmd_line: App_Server
0 08/19/09 08:33:10 99 (spawning-device) Entering 99
1 08/19/09 08:33:11 99 (spawning-device) Starting... 1
1 08/19/09 08:33:11 99 (spawning-device) Found /usr/pluto/bin/App_Server
1 08/19/09 08:33:11 /usr/pluto/bin/Spawn_Device.sh 100 (spawning-device) 4090 Dev: 100; Already Running list: 99,
1 08/19/09 08:33:11 /usr/pluto/bin/Spawn_Device.sh 100 (spawning-device) device: 100 ip: dcerouter cmd_line: LaunchOrbiter.sh
0 08/19/09 08:33:11 100 (spawning-device) Entering 100
1 08/19/09 08:33:12 100 (spawning-device) Starting... 1
1 08/19/09 08:33:12 100 (spawning-device) Found /usr/pluto/bin/LaunchOrbiter.sh
1 08/19/09 08:33:12 LaunchOrbiter (server) Number of desktops found: 4 ; desktops activated?
1 08/19/09 08:33:12 LaunchOrbiter (server) Increasing number of desktops to: 6
1 08/19/09 08:33:12 LaunchOrbiter (server) Primary desktop: 4 and secondary desktop 5
1 08/19/09 08:33:14 /usr/pluto/bin/Spawn_Device.sh 102 (spawning-device) 4209 Dev: 102; Already Running list: 99,100,
1 08/19/09 08:33:15 /usr/pluto/bin/Spawn_Device.sh 102 (spawning-device) device: 102 ip: dcerouter cmd_line: HAL
0 08/19/09 08:33:15 102 (spawning-device) Entering 102
1 08/19/09 08:33:15 102 (spawning-device) Starting... 1
1 08/19/09 08:33:15 102 (spawning-device) Found /usr/pluto/bin/HAL
3 08/19/09 08:35:53 100 (spawning-device) Device died... count=1/50 dev=100
1 08/19/09 08:36:03 100 (spawning-device) Starting... 2
1 08/19/09 08:36:03 100 (spawning-device) Found /usr/pluto/bin/LaunchOrbiter.sh
1 08/19/09 08:36:03 LaunchOrbiter (server) Number of desktops found: 6 ; desktops activated? 1
1 08/19/09 08:36:03 LaunchOrbiter (server) Primary desktop: 4 and secondary desktop 5
1 08/19/09 08:36:04 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/46 ) has 1203054 MB free
1 08/19/09 08:36:05 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/47 ) is ReadOnly
1 08/19/09 08:36:06 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/47 ) has 1203054 MB free
2 08/19/09 08:37:03 99 (spawning-device) Device requests restart... count=1/50 dev=99
2 08/19/09 08:37:03 102 (spawning-device) Device requests restart... count=1/50 dev=102
1 08/19/09 08:37:11 99 (spawning-device) Starting... 1
1 08/19/09 08:37:11 99 (spawning-device) Found /usr/pluto/bin/App_Server
1 08/19/09 08:37:12 102 (spawning-device) Starting... 1
1 08/19/09 08:37:12 102 (spawning-device) Found /usr/pluto/bin/HAL
1 08/19/09 08:39:03 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/46 ) has 1203054 MB free
1 08/19/09 08:39:04 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/47 ) is ReadOnly
1 08/19/09 08:39:04 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/47 ) has 1203054 MB free
2 08/19/09 08:39:54 99 (spawning-device) Device requests restart... count=1/50 dev=99
2 08/19/09 08:39:55 102 (spawning-device) Device requests restart... count=1/50 dev=102
1 08/19/09 08:40:02 99 (spawning-device) Starting... 1
1 08/19/09 08:40:02 99 (spawning-device) Found /usr/pluto/bin/App_Server
1 08/19/09 08:40:03 102 (spawning-device) Starting... 1
1 08/19/09 08:40:03 102 (spawning-device) Found /usr/pluto/bin/HAL
1 08/19/09 08:42:03 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/46 ) has 1203054 MB free
1 08/19/09 08:42:04 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/47 ) is ReadOnly
1 08/19/09 08:42:05 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/47 ) has 1203054 MB free
1 08/19/09 08:42:15 SetupAudioVideo (server) Starting
1 08/19/09 08:42:16 SetupAudioVideo (server) '
1 08/19/09 08:42:16 SetupAudioVideo (server) DBSetting: S Reboot: Script Path: /usr/pluto/bin/
1 08/19/09 08:42:16 /usr/pluto/bin/Start_X.sh (server) Starting X server (client: /usr/bin/xfwm4; parms: --compositor=off)
1 08/19/09 08:42:17 /usr/pluto/bin/Start_X.sh (server) X server: backround; AlphaBlending: 0
1 08/19/09 08:42:26 /usr/pluto/bin/Spawn_Device.sh 99 (spawning-device) 9011 Dev: 99; Already Running list:
1 08/19/09 08:42:27 /usr/pluto/bin/Spawn_Device.sh 99 (spawning-device) device: 99 ip: dcerouter cmd_line: App_Server
0 08/19/09 08:42:27 99 (spawning-device) Entering 99
1 08/19/09 08:42:27 99 (spawning-device) Starting... 1
1 08/19/09 08:42:27 99 (spawning-device) Found /usr/pluto/bin/App_Server
1 08/19/09 08:42:28 /usr/pluto/bin/Spawn_Device.sh 100 (spawning-device) 9177 Dev: 100; Already Running list: 99,
1 08/19/09 08:42:28 /usr/pluto/bin/Spawn_Device.sh 100 (spawning-device) device: 100 ip: dcerouter cmd_line: LaunchOrbiter.sh
0 08/19/09 08:42:28 100 (spawning-device) Entering 100
1 08/19/09 08:42:28 100 (spawning-device) Starting... 1
1 08/19/09 08:42:29 100 (spawning-device) Found /usr/pluto/bin/LaunchOrbiter.sh
1 08/19/09 08:42:29 LaunchOrbiter (server) Number of desktops found: 6 ; desktops activated? 1
1 08/19/09 08:42:29 LaunchOrbiter (server) Primary desktop: 4 and secondary desktop 5
1 08/19/09 08:42:32 /usr/pluto/bin/Spawn_Device.sh 102 (spawning-device) 10062 Dev: 102; Already Running list: 99,100,
1 08/19/09 08:42:32 /usr/pluto/bin/Spawn_Device.sh 102 (spawning-device) device: 102 ip: dcerouter cmd_line: HAL
0 08/19/09 08:42:32 102 (spawning-device) Entering 102
1 08/19/09 08:42:33 102 (spawning-device) Starting... 1
1 08/19/09 08:42:33 102 (spawning-device) Found /usr/pluto/bin/HAL
1 08/19/09 08:45:03 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/46 ) has 1203054 MB free
1 08/19/09 08:45:04 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/47 ) is ReadOnly
1 08/19/09 08:45:05 DiskSpaceMonitor.sh (server) Filesystem ( /mnt/device/47 ) has 1203054 MB free
Thank's !
Philippe
-
Dear Philippe,
with your pluto log nothing is wrong. At least a first sight and based on my knowledge.
I still think there is something wrong with your X setup.
Please post your xorg.conf
Maybe I can find something there
Rgds
Peter
-
Hello Peter,
Here the xorg.conf for the MD (nvidia 6200) where I have a TV connected:
dcerouter_1001027:/usr/pluto/diskless# cat 98/etc/X11/xorg.conf
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
# RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "record"
Load "xtrap"
Load "speedo"
Load "type1"
Load "glx"
Load "int10"
Load "v4l"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbLayout" "us"
Option "XkbVariant" "basic"
Option "XkbModel" "pc105"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown Monitor Vendor"
ModelName "Unknown Monitor Model"
Modeline "640x480" 25.18 640 656 752 800 480 490 492 525
HorizSync 20-500
VertRefresh 59-61
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
Identifier "Card0"
Driver "nvidia"
VendorName "Unknown Vendor Name"
BoardName "Unknown Board Name"
Option "LinearAlloc" "16384"
#BusID "PCI:0:2:0"
# Option "NoDDC" "true"
Option "XvmcUsesTextures" "true"
Option "renderAccel" "true"
Option "NoDDCValue"
Option "UseEDID" "false"
Option "ExactModeTimingsDVI" "true"
Option "NoLogo" "true"
Option "NoBandWidthTest" "true"
Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"
Option "DynamicTwinView" "false"
Option "UseEvents" "true"
Option "ConnectedMonitor" "TV"
Option "TVOutFormat" "Composite"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Modes "640x480"
Virtual 640 480
EndSubSection
Option "XvmcUsesTextures" "true"
Option "renderAccel" "true"
Option "NoDDCValue"
Option "UseEDID" "false"
Option "ExactModeTimingsDVI" "true"
Option "NoLogo" "true"
Option "NoBandWidthTest" "true"
Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"
Option "DynamicTwinView" "false"
Option "UseEvents" "true"
Option "TVStandard" "PAL-N"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
Option "AutoAddDevices" "false"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
Option "AIGLX" "Off"
EndSection
Section "Extensions"
Option "Composite" "false"
Option "RENDER" "true"
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
For your information, after a apt-get update on this MD yesterday, I have on boot some "load messages" on the screen (big characters).
So I think that X work correctly.
Like I write before, this MD worked with lmce 710 without problem.
It is the reason why I say something is wrong and it would nice to find it.
I can't imagine I'm (I will be) alone with this problem.
Thank's a lot for your attention.
Philippe
-
Hello Philippe,
No I do not think You are alone on this, I think I have it too.
Can You please list the hardware of all the MD´s to figure out what differs.
BR Stefan
-
Hello Stefan,
I have post my hardware list on the wiki.
http://wiki.linuxmce.org/index.php/User:Pga57
The MDs that give problems are #1 and #4.
if you want more information let me know.
Philippe
-
Dear Philippe,
yes you are right with your assumption that X server is starting.
But the remaining black screen can mean a lot of different things.
First: I would need to know whether the "cursor" you mentioned in the subject is a text cursor or a mouse pointer?
If it is a text cursor x.server might be stopped due to a failure --> check Xorg.log or post it
if it is a mouse pointer it might be a conflict between MD Orbiter and X configuration (render, glx virt desktop .......so many options) mnain problem you will not really find a hint in Xorg.log
second: get a remote / ssh console you need to login as root into the MD
if you don't get root or password is not working check the wiki chroot comand helps to setup the password
make a backup of your xorg.file and delete everything what is not necessary
check the BusID with lspci and enter into xorg.conf
make a sudo killall Start_X_Wrapper.sh to kill the Xserver
and try startx to see if xserver is starting into KDE desktop
if yes you can check drivers , resolution and so on.....
the minimum configuration (with VGA connected) xorg.conf:
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
EndSection
Section "Module"
Load "glx"
EndSection
Section "Device"
Identifier "Configured Video Device"
Driver "nvidia"
Option "NoLogo" "True"
EndSection
So leaving your TV connected you will need to keep the entries:
Option "ConnectedMonitor" "TV"
Option "TVOutFormat" "Composite"
In general I would propose for first analysis to go with minimum configuration on an LCD/CRT monitor VGA connected
once this is running with proper nvidia drivers and resolution you can try to reconnect the TV.
Also the monitor configuration in the xorg.conf for sure does not fit the TV set
but this we can see only in the Xorg logfile .
As a general remark: before starting to go into deep try to setup from scratch the MD
on first starting please be aware that still some installation can happen and might take time - be patient
for sure you did it already, but I just wanted to mention it .....
As I spent already too much time configuring xorg.conf I know what might be waiting for you ;-)
Hope above will help to find the root cause.
If startx is not bringing up the KDe desktop try to go for vesa driver
and then find the right driver for your card.
Regards
Peter
-
please also try to switch off the screensaver on th MD
Web Administration
MediaDirector > Software modules -> Edit
Deselect ScreenSaver
Reload
Regards
Peter
-
Hello Peter,
Thank's for your reply and help.
About the "cursor" I describe on my previous msg, it is a mouse pointer. X is started.
I have delete a lot of things in my xorg.conf file and I have started Kde 4.1 without problems.
I only have a black screen when the OrbiterRenderer_SDL go on focus.
If I reduce it, I retrive the desktop.
I think so that the problem come from the Orbiter (UI1).
But I don't know why.
I have downgrade the nvidia from 1.80 to 1.77 but it don't resolve my black screen.
When I reboot my MD the devices are loaded and I can see the messages like "starting device Orbiter", "Starting device HAL" and after nothing else.
So it is not a driver problem, I suppose that something has change with the Orbiter and my MD don't like it ! ;-)
Regards,
Philippe
-
Dear Philippe,
so how about your xorg.log?
And did you disable the picture screen saver?
I am asking this because I had similar troubles with an old ATI Mobility 9000M
now running fine even with overlay on the TV (VAG connected)
What is for sure that in the Alpha there is something broken with the DISPLAY environment variable.
can you check if it is exported
echo $DISPLAY
If you get nothing back it would be the proof for my statement.
Simply addressing of the display ("On which to appear" seems to make problems)
and this can be part of an XServer setup problem as well
So my suggestion
VGA connected, UI1 and no screensaver
please try this - or did you already?
Rgds
Peter
-
Hello Peter,
I've just finished to test all the suggestions you make to me.
So, VGA connected, UI1 and no screensaver where tested but I've regret to say that it does not resolve my black screen :-(.
The echo $DISPLAY give nothing. It only give a result on the core media director.
Some MDs that worked on my lan give me nothing too, so can it be a problem... but not sure.
About my xorg files, here the 2 tested:
MD #4 (VGA only)
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
# RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection
Section "Module"
#Load "dbe"
#Load "extmod"
#Load "record"
#Load "xtrap"
#Load "speedo"
#Load "type1"
Load "glx"
#Load "int10"
#Load "v4l"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbLayout" "us"
Option "XkbVariant" "basic"
Option "XkbModel" "pc105"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown Monitor Vendor"
ModelName "Unknown Monitor Model"
Modeline "1024x768" 60.80 1024 1056 1128 1272 768 768 770 796
HorizSync 20-500
VertRefresh 59-61
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
Identifier "Card0"
Driver "nvidia"
VendorName "Unknown Vendor Name"
BoardName "Unknown Board Name"
#Option "LinearAlloc" "16384"
#BusID "PCI:0:10:0"
# #Option "NoDDC" "true"
#Option "XvmcUsesTextures" "true"
#Option "renderAccel" "true"
#Option "NoDDCValue"
#Option "UseEDID" "false"
#Option "ExactModeTimingsDVI" "true"
#Option "NoLogo" "true"
#Option "NoBandWidthTest" "true"
#Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"
#Option "DynamicTwinView" "false"
#Option "UseEvents" "true"
Option "ConnectedMonitor" "CRT"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Modes "1024x768"
Virtual 1024 768
EndSubSection
#Option "XvmcUsesTextures" "true"
#Option "renderAccel" "true"
#Option "NoDDCValue"
#Option "UseEDID" "false"
#Option "ExactModeTimingsDVI" "true"
#Option "NoLogo" "true"
#Option "NoBandWidthTest" "true"
#Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"
#Option "DynamicTwinView" "false"
#Option "UseEvents" "true"
#Option "TVStandard" "1024x768"
EndSection
Section "ServerFlags"
#Option "AllowMouseOpenFail" "true"
#Option "AutoAddDevices" "false"
#Option "BlankTime" "0"
#Option "StandbyTime" "0"
#Option "SuspendTime" "0"
#Option "OffTime" "0"
#Option "AIGLX" "Off"
EndSection
Section "Extensions"
Option "Composite" "false"
Option "RENDER" "true"
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
MD #1 (TV).
This second MD was tested with VGA only too , but the result was not better.
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown Monitor Vendor"
ModelName "Unknown Monitor Model"
Modeline "640x480" 25.18 640 656 752 800 480 490 492 525
HorizSync 20-500
VertRefresh 59-61
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
#Option "XvmcUsesTextures" "true"
#Option "renderAccel" "true"
#Option "NoDDCValue"
#Option "UseEDID" "false"
#Option "ExactModeTimingsDVI" "true"
Option "NoLogo" "true"
#Option "NoBandWidthTest" "true"
#Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"
#Option "DynamicTwinView" "false"
#Option "UseEvents" "true"
Option "TVStandard" "PAL-N"
DefaultDepth 24
SubSection "Display"
Modes "640x480"
Virtual 640 480
EndSubSection
EndSection
Section "Module"
#Load "dbe"
#Load "extmod"
#Load "record"
#Load "xtrap"
#Load "speedo"
Load "glx"
#Load "int10"
#Load "v4l"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbLayout" "us"
Option "XkbVariant" "basic"
Option "XkbModel" "pc105"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
EndSection
Section "Extensions"
#Option "Composite" "false"
#Option "RENDER" "true"
EndSection
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Device"
Identifier "Card0"
VendorName "Unknown Vendor Name"
BoardName "Unknown Board Name"
#Option "LinearAlloc" "16384"
#Option "XvmcUsesTextures" "true"
#Option "renderAccel" "true"
#Option "NoDDCValue"
#Option "UseEDID" "false"
#Option "ExactModeTimingsDVI" "true"
#Option "NoBandWidthTest" "true"
#Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"
#Option "DynamicTwinView" "false"
#Option "UseEvents" "true"
Option "ConnectedMonitor" "TV"
Option "TVOutFormat" "Composite"
Driver "nvidia"
Option "NoLogo" "True"
EndSection
Section "ServerFlags"
#Option "AllowMouseOpenFail" "true"
#Option "AutoAddDevices" "false"
#Option "BlankTime" "0"
#Option "StandbyTime" "0"
#Option "SuspendTime" "0"
#Option "OffTime" "0"
#Option "AIGLX" "Off"
EndSection
Section "ServerFlags"
#Option "AutoAddDevices" "False"
EndSection
I appreciate very much the time you spend to answer me.
I feel me less alone! ;-)
Regards,
Philippe
-
Dear Phillipe,
I only try to give suggestions, but I believe in waves- everything you give will come back once - maybe not on the direct way, but it will.
An if it's only for the feeling you are not alone...... ;)
so going into next round:
so I assume you can not get a proper result from
glxinfo | grep dir
so try following
DISPLAY=:0.0 glxinfo |grep dir
this should give you following result
direct rendering: Yes
if this is the case then your rendering is ok
also add module "dri" into xorg.conf
another question would be whether you can control the MD from another room Orbiter
and see whether you can startup TV or a video?
please check /etc/pluto/lastaudiovideo.conf
and /etc/Orbiter.conf
on one of my MD's I had to manually add
UseOpenGL=1
Please also check / compare
/var/log/pluto/xx_Launchorbiter.sh.log where xx is the device #
make sure Photo screensaver is really not starting
/var/log/pluto/xx_Photo.........
You should find the Orbiter also in the /var/log/pluto/running.pids
If something is not starting as it should check the
/usr/pluto/lock/pluto_spawned_local_devices.txt
if the device # of the not starting device is already in.
if so _ edit the file and delete the device numer
and restart the MD
Hope these things help to find the problem
Rgds
Peter
-
Hello Peter,
Like you said, the "glxinfo | grep dir" give nothing on the MD.
After add module "dri" into xorg.conf, it give me the "direct rendering: Yes" msg.
I've done a reboot but, the result was allways the black screen.
I've try to control the MD from another room Orbiter (N810) but I've no TV, video, Music or light controls for this MD.
I suppose that the config is not finished.
Like I say in a previous msg, I've not the possibility to view Sarah (MD setup) after the AVWizard setup for those MDs.
I've try to regenerate the orbiter but no result.
In the /etc/pluto/lastaudiovideo.conf, UseOpenGL=0. I modify it to 1.
In the /etc/Orbiter.conf, I only have:
EnableGenerator=0
DelayMin=1000
DelayMax=2000
NumberOfButtonsPerClick=0
GenerateMouseClicks=1
GenerateKeyboardEvents=0
KeysSetToGenerate=1
And no UseOpenGL value.
100_Launchorbiter.sh.log:
== ATTEMPT FRESH START ==
1 08/23/09 10:52:23 /usr/pluto/bin/Spawn_Device.sh 100 (spawning-device) 9745 Dev: 100; Already Running list: 99,
== FRESH START ==
1 08/23/09 10:52:23 /usr/pluto/bin/Spawn_Device.sh 100 (spawning-device) device: 100 ip: dcerouter cmd_line: LaunchOrbiter.sh
0 08/23/09 10:52:23 100 (spawning-device) Entering 100
========== NEW LOG SECTION ==========
1 08/23/09 10:52:23 100 (spawning-device) Starting... 1
1 08/23/09 10:52:23 100 (spawning-device) Found /usr/pluto/bin/LaunchOrbiter.sh
I have no /var/log/pluto/xx_Photo.........
In the /var/log/pluto/running.pids we find:
9671 Spawn_Device of /usr/pluto/bin/App_Server (by /usr/pluto/bin/Spawn_Device.sh)
9738 /usr/pluto/bin/App_Server (by /usr/pluto/bin/Spawn_Wrapper.sh)
9745 Spawn_Device of /usr/pluto/bin/LaunchOrbiter.sh (by /usr/pluto/bin/Spawn_Device.sh)
9812 /usr/pluto/bin/LaunchOrbiter.sh (by /usr/pluto/bin/Spawn_Wrapper.sh)
9943 Spawn_Device of /usr/pluto/bin/HAL (by /usr/pluto/bin/Spawn_Device.sh)
10062 /usr/pluto/bin/HAL (by /usr/pluto/bin/Spawn_Wrapper.sh)
In /usr/pluto/locks/pluto_spawned_local_devices.txt:
99
100
102
I've try to edit it and delete the 100 device but it reappar after rebooting the MD.
What is annoying is that KDE 4.1 seems to work normally, but not the orbiter.
You see, this is not yet won ! ;-)
Greetings,
Philippe
-
what is the last on screen status display message that you see?
-Thom
-
Hello Thom,
The last on screen status display message I see is "Starting device 102 HAL".
Nothing else appears except the mouse pointer.
And just before I have : "Starting device 99 App Server" and "Starting device 100 Onscreen Orbiter".
Philippe
-
can you give me a list of devices in your device tree? i wonder if you have duplicate devices...
-Thom
-
Hello Phillipe,
looking to the log file and confirmed by your last mail only 3 devices are starting up
99 AppSrv
100 Orbiter
102 HAL
So HAL is the last device
Please check xx_HAL.log if it is ok
Most probably your setup of the MD did not finish somewhere
you could try 2 things
Go to Web administration \\dcerouter\lmce-admin\
and go to Wizard>MediaDirector
go to the critical one and try a rebuild image
Quick reload router
startup MD
If this does not help try following
Make a new MD
copy the MAC address to the new one (delete from the old) and rebuild image
once ready !!!!! and only if its ready restart MD and wait to finish installation
Rgds
Peter
-
Thom,
Is this what you want?
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
-
Looking to your Hardware list there is missing one MD in the Device list
I think the Garage one, isn't it?
Which one is the not working one?
Rgds
Peter
-
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
-
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:
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
-
Peter,
Just wanted to let you know that I appear to be having the same issues. I reinstalled all from scratch yesterday (2.29) and when I installed the first MD, (and after AV wizard), it just goes to x with the small white mouse pointer. I've tried the usual suspects with no luck.
I've just done the updates to 2.31 on the core and have deleted the MD and am going to see how that goes.
Also, my core seems to have lost it's way in getting to lmce. It now presents the kde login and I have to manually click the (very handy!) lmce plasmoid. I know the old launch manager used to have a selectable toggle for this and would appreciate if someone could remind me how to do it without the launch manager.
much thanks,
joseph
-
Dear Joseph,
the autostart for the MD should be still in the /etc/pluto.conf if I´m not mistaken.
related the "black screen" can you provide your MD hardware description, xorg.conf , driver version
and also a couple of logs to be found in /var/log/pluto
starting the devices and also your device list
maybe we can find some common point with the problem of Philippe
Rgds
Peter
PS: I just saw Philippe is using the french distribution ( what else :-) )
@Joseph : which one are you using?
-
Dear Philippe,
your network problem comes most probably from the new feature
apt-cacher-ng
see also
http://forum.linuxmce.org/index.php?topic=8756.msg59273#msg59273 (http://forum.linuxmce.org/index.php?topic=8756.msg59273#msg59273)
check /etc/apt/apt.conf.d/02proxy
Rgds
Peter
-
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
-
Hi,
to solve a black screen problem, try this:
- from another pc login to lmce (es: http://192.168.80.1/pluto_admin
- create a new user
- login
- choose show device tree (low left corner)
- delete extra core.
- reboot
best regards
-
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
-
Bonsoir Philippe,
so we should check it from the basics
Let's follow the remark of Thom and also from enricomce to check your device list
so let get your actual device list once more
and also the different logfiles for the 2 MDs not working as already before
I think best thing would be to delete/ move / logrotate all logs in the diskless section and also for the core
and to make a complete restart.
logs must give us some hint.
but first check once more the device list for strange/double/unwanted entries
Rgds
Peter
-
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
-
Peter,
Thank you for your quick reply. had to go out of town for a few days and just got home and voila my MD is working! I don't know why - except perhaps it was taking a very long time to get itself together. I can still post config info if you like, but it's pretty vanilla from a couple of years ago - nvidia, etc, and I suspect it won't be of much help.
Also, thank you for the /etc/pluto.conf hint. I hit it with nano and I assumed that the setting to fix was changing DesktopActivated =1 to = 0. I did that and rebooted, but it didn't seem to have any effect. The core still booted into the KDE login and then went to the KDE desktop. I have tried searching the forums and wiki, but I haven't been able to choose the correct search terms to narrow the results.
Pointers welcome and thanks again,
joseph
-
I've had this too, and a reboot of the MD fixed it, every time.
Richard
-
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
hello pga,
i'm login with a .../Pluto_admin
anyway
I solved the black screen problem,
if you have more than 1 core in the device tree, leave only 1 core and delete the other.
scuse for my english.
i read very well, but i have same difficult to write
regard
enrico
-
Dear Joseph,
look at
http://wiki.linuxmce.org/index.php/Clean_Core (http://wiki.linuxmce.org/index.php/Clean_Core)
maybe this helps
Rgds
Peter
-
Peter,
Thank you. I'll have a look at that.
also, I installed another md and it got the dreaded black screen with x cursor as well...
mainboard in both are ASUS M2NPV-VM
mainboard in core is Asus P4P800-E Deluxe
and they've worked well for a couple of years.
joseph
-
are you guys using the latest build? it may just be doing orbiter regeneration.
-Thom
-
Thom,
That's a thought I had when the family room MD was alive after I was out of town for a few days.
Now the (second MD) home theater MD has been going for about a day, but I rebooted it a few times.
Is it possible that it can take on the order of days to gen?
thanks for sharing your thoughts!
joseph
-
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
-
guys, please start by ssh'ing into your machines and running top to see if any specific processes stand out as chewing up CPU. There may be something obvious. Failing that we will need to resort to trawling through some log files, but start with the low hanging fruit.
-
Hello Colin,
Top give me only 5% cpu usage on the bad MD.
Here some logs:
pluto.log
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
========== 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
========== 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
========== 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
-
Col,
thanks for the guidance. top shows nothing:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
7 root 15 -5 0 0 0 S 1 0.0 0:06.06 ksoftirqd/1
1 root 20 0 2920 1724 576 S 0 0.1 0:01.36 init
2 root 15 -5 0 0 0 S 0 0.0 0:00.04 kthreadd
3 root RT -5 0 0 0 S 0 0.0 0:00.02 migration/0
4 root 15 -5 0 0 0 S 0 0.0 0:03.62 ksoftirqd/0
5 root RT -5 0 0 0 S 0 0.0 0:00.00 watchdog/0
I'm going to reboot all again. What do you suggest next?
joseph
-
Hello Phillipe,
are these all logs of the md?
aren't there more devices?
if your answers are yes to both
then the black screen comes maybe from not starting all devices.
how about communication with dcerouter?
what does the core log show?
just an idea: if mythtv frontend hangs on one of my md's for short
time it shows a blck screen with mouse pointer.
try to check the mythtv config on the md or if not possible delete the mythtv device/ plugin from the md (via web admin)
small side step: if you ping dcerouter by name not ip from md do you get correct resloving? how is your network setup on the md / core?
Rgds
Peter
-
Hello Peter,
I have those logs in the /var/log/pluto moon directory (MD#1):
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 Philippe,
compared to my Md´s there are missing the orbiters child process logs like
simple phone, media player mythtv plugin which is also in your device list
if i remember well
and the timing of the Orbiter log is not in line with the pluto and HAL log
looks like Orbiter is not realy starting up.
chek the locks and spawned devices
and also ps ax | grep Orbiter to see if its running
Rgds
Peter
-
Hello,
I also have significant differences between the log files present on the MD that works compared to the one that doesn't.
md that works - moon62
root@moon62:/var/log/pluto# ls -lt
total 17640
-rw-r--r-- 1 root root 548748 Aug 30 22:52 65_LaunchOrbiter.sh.log
-rw-r--r-- 1 root root 16117 Aug 30 22:52 StorageDevices.log
-rw-r--r-- 1 root root 316750 Aug 30 22:52 umount-wrapper.log
-rw-r--r-- 1 root root 23670 Aug 30 22:51 pluto.log
-rw-r--r-- 1 root root 1038 Aug 30 22:38 69_LaunchPhoto_Screen_Saver.sh.log
-rw-r--r-- 1 root root 212 Aug 30 22:10 64_App_Server.log
-rwxr-xr-T 1 root root 2409 Aug 30 22:10 Spawn_not named_9597.log
-rw-r--r-- 1 root root 0 Aug 30 22:10 StorageDevices_Symlinks.log
-rw-r--r-- 1 root root 110 Aug 30 22:10 SetupUsers_Homes.log
-rw-r--r-- 1 root root 564635 Aug 30 21:12 68_Xine_Player.log
-rw-r--r-- 1 root root 807 Aug 30 21:12 70_MPlayer_Player.log
-rw-r--r-- 1 root root 3892 Aug 30 21:12 Spawn_Device.log
-rw-r--r-- 1 root root 807 Aug 30 21:12 71_MythTV_Player.log
-rw-r--r-- 1 root root 807 Aug 30 21:12 66_SimplePhone.log
-rw-r--r-- 1 root root 1550 Aug 30 21:11 running.pids
-rw-r--r-- 1 root root 4921 Aug 30 21:11 deaths
-rw-r--r-- 1 root root 4012 Aug 30 21:11 died_65_65
-rw-r--r-- 1 root root 5880 Aug 30 20:05 64_App_Server.log.1
-rw-r--r-- 1 root root 4115228 Aug 30 20:05 65_LaunchOrbiter.sh.log.1
-rw-r--r-- 1 root root 4709 Aug 30 20:05 66_SimplePhone.log.1
-rw-r--r-- 1 root root 1733 Aug 30 20:05 67_HAL.log.1
-rw-r--r-- 1 root root 7819786 Aug 30 20:05 68_Xine_Player.log.1
-rw-r--r-- 1 root root 5578 Aug 30 20:05 69_LaunchPhoto_Screen_Saver.sh.log.1
-rw-r--r-- 1 root root 4514 Aug 30 20:05 70_MPlayer_Player.log.1
-rw-r--r-- 1 root root 4511 Aug 30 20:05 71_MythTV_Player.log.1
-rw-r--r-- 1 root root 2908 Aug 30 20:05 73_Disk_Drive.log.1
-rw-r--r-- 1 root root 1993 Aug 30 20:05 74_External_Media_Identifier.log.1
-rw-r--r-- 1 root root 671 Aug 30 20:05 LaunchManager.log.1
-rw-r--r-- 1 root root 0 Aug 30 20:05 xorg.conf.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 CumulativeSpawn.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 CumulativeSpawnDaemon.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 LMCEUpdate.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 LaunchManager.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 LaunchManager.progress.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 PlutoServer.Logger.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 UpdateHelper.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 UpdateMedia.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 WatchGyro.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 Xconfigure.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 avremote_detect.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 avwizard_setup_av.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 73_Disk_Drive.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 74_External_Media_Identifier.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 77_Generic_Serial_Device.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 89_Generic_Serial_Device.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 AVWizard.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 Config_Device_Changes.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 ConfirmDependencies.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 CreateDevice.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 63_Generic_Serial_Device.log
-rw-r--r-- 1 root root 0 Aug 30 20:05 67_HAL.log
-rw-r--r-- 1 root root 26330 Aug 30 20:05 CumulativeSpawn.log.1
-rw-r--r-- 1 root root 1283290 Aug 30 20:04 umount-wrapper.log.1
-rw-r--r-- 1 root root 56443 Aug 30 20:04 StorageDevices.log.1
-rw-r--r-- 1 root root 143688 Aug 30 20:03 pluto.log.1
-rw-r--r-- 1 root root 0 Aug 30 19:31 StorageDevices_Symlinks.log.1
-rw-r--r-- 1 root root 330 Aug 30 19:31 SetupUsers_Homes.log.1
-rw-r--r-- 1 root root 1422 Aug 30 19:31 Config_Device_Changes.log.1
-rw-r--r-- 1 root root 2200 Aug 30 19:31 WatchGyro.log.1
-rw-r--r-- 1 root root 432 Aug 30 19:31 LMCEUpdate.log.1
-rw-r--r-- 1 root root 927 Aug 30 19:31 LaunchManager.progress.log.1
-rw-r--r-- 1 root root 432 Aug 30 19:31 UpdateHelper.log.1
-rw-r--r-- 1 root root 170 Aug 30 00:09 PlutoServer.Logger.log.1
-rw-r--r-- 1 root root 33405 Aug 30 00:01 getxmls.log
-rw-r--r-- 1 root root 706 Aug 29 08:07 64_App_Server.log.2.gz
-rw-r--r-- 1 root root 80337 Aug 29 08:07 65_LaunchOrbiter.sh.log.2.gz
-rw-r--r-- 1 root root 530 Aug 29 08:07 66_SimplePhone.log.2.gz
-rw-r--r-- 1 root root 314 Aug 29 08:07 67_HAL.log.2.gz
-rw-r--r-- 1 root root 955975 Aug 29 08:07 68_Xine_Player.log.2.gz
-rw-r--r-- 1 root root 622 Aug 29 08:07 69_LaunchPhoto_Screen_Saver.sh.log.2.gz
-rw-r--r-- 1 root root 498 Aug 29 08:07 70_MPlayer_Player.log.2.gz
-rw-r--r-- 1 root root 1187 Aug 29 08:07 73_Disk_Drive.log.2.gz
-rw-r--r-- 1 root root 1473 Aug 29 08:07 71_MythTV_Player.log.2.gz
-rw-r--r-- 1 root root 909 Aug 29 08:07 74_External_Media_Identifier.log.2.gz
-rw-r--r-- 1 root root 205 Aug 29 08:07 LaunchManager.log.2.gz
-rw-r--r-- 1 root root 0 Aug 29 08:07 xorg.conf.log.1
-rw-r--r-- 1 root root 0 Aug 29 08:07 77_Generic_Serial_Device.log.1
-rw-r--r-- 1 root root 0 Aug 29 08:07 89_Generic_Serial_Device.log.1
-rw-r--r-- 1 root root 0 Aug 29 08:07 AVWizard.log.1
-rw-r--r-- 1 root root 0 Aug 29 08:07 ConfirmDependencies.log.1
-rw-r--r-- 1 root root 0 Aug 29 08:07 CreateDevice.log.1
-rw-r--r-- 1 root root 0 Aug 29 08:07 UpdateMedia.log.1
-rw-r--r-- 1 root root 0 Aug 29 08:07 Xconfigure.log.1
-rw-r--r-- 1 root root 0 Aug 29 08:07 avremote_detect.log.1
-rw-r--r-- 1 root root 0 Aug 29 08:07 avwizard_setup_av.log.1
-rw-r--r-- 1 root root 0 Aug 29 08:07 63_Generic_Serial_Device.log.1
-rw-r--r-- 1 root root 20496 Aug 29 08:07 CumulativeSpawn.log.2.gz
-rw-r--r-- 1 root root 157 Aug 29 08:07 CumulativeSpawnDaemon.log.1
-rw-r--r-- 1 root root 136276 Aug 29 08:06 umount-wrapper.log.2.gz
-rw-r--r-- 1 root root 7670 Aug 29 08:06 pluto.log.2.gz
-rw-r--r-- 1 root root 9609 Aug 29 08:06 StorageDevices.log.2.gz
-rw-r--r-- 1 root root 20 Aug 28 13:53 StorageDevices_Symlinks.log.2.gz
-rw-r--r-- 1 root root 99 Aug 28 13:53 SetupUsers_Homes.log.2.gz
-rw-r--r-- 1 root root 166 Aug 28 13:53 Config_Device_Changes.log.2.gz
-rw-r--r-- 1 root root 142 Aug 28 13:53 WatchGyro.log.2.gz
-rw-r--r-- 1 root root 92 Aug 28 13:53 LMCEUpdate.log.2.gz
-rw-r--r-- 1 root root 216 Aug 28 13:53 LaunchManager.progress.log.2.gz
-rw-r--r-- 1 root root 92 Aug 28 13:53 UpdateHelper.log.2.gz
-rw-r--r-- 1 root root 2565 Aug 28 07:48 64_App_Server.log.3.gz
-rw-r--r-- 1 root root 246746 Aug 28 07:48 65_LaunchOrbiter.sh.log.3.gz
-rw-r--r-- 1 root root 2832 Aug 28 07:48 66_SimplePhone.log.3.gz
-rw-r--r-- 1 root root 1055 Aug 28 07:48 67_HAL.log.3.gz
-rw-r--r-- 1 root root 419929 Aug 28 07:48 68_Xine_Player.log.3.gz
-rw-r--r-- 1 root root 2983 Aug 28 07:48 69_LaunchPhoto_Screen_Saver.sh.log.3.gz
-rw-r--r-- 1 root root 2448 Aug 28 07:48 70_MPlayer_Player.log.3.gz
-rw-r--r-- 1 root root 2358 Aug 28 07:48 71_MythTV_Player.log.3.gz
-rw-r--r-- 1 root root 944 Aug 28 07:48 LaunchManager.log.3.gz
-rw-r--r-- 1 root root 20 Aug 28 07:48 ConfirmDependencies.log.2.gz
-rw-r--r-- 1 root root 20 Aug 28 07:48 CreateDevice.log.2.gz
-rw-r--r-- 1 root root 20 Aug 28 07:48 UpdateMedia.log.2.gz
-rw-r--r-- 1 root root 20 Aug 28 07:48 Xconfigure.log.2.gz
-rw-r--r-- 1 root root 20 Aug 28 07:48 avremote_detect.log.2.gz
-rw-r--r-- 1 root root 20 Aug 28 07:48 avwizard_setup_av.log.2.gz
-rw-r--r-- 1 root root 20 Aug 28 07:48 xorg.conf.log.2.gz
-rw-r--r-- 1 root root 20 Aug 28 07:48 63_Generic_Serial_Device.log.2.gz
-rw-r--r-- 1 root root 20 Aug 28 07:48 AVWizard.log.2.gz
-rw-r--r-- 1 root root 154840 Aug 28 07:48 umount-wrapper.log.3.gz
-rw-r--r-- 1 root root 15028 Aug 28 07:48 pluto.log.3.gz
-rw-r--r-- 1 root root 12969 Aug 28 07:48 StorageDevices.log.3.gz
-rw-r--r-- 1 root root 2869 Aug 27 23:38 Config_Device_Changes.log.3.gz
-rw-r--r-- 1 root root 333 Aug 27 23:38 LaunchManager.progress.log.3.gz
-rw-r--r-- 1 root root 20 Aug 27 23:37 StorageDevices_Symlinks.log.3.gz
-rw-r--r-- 1 root root 142 Aug 27 23:36 SetupUsers_Homes.log.3.gz
-rw-r--r-- 1 root root 223 Aug 27 22:53 WatchGyro.log.3.gz
-rw-r--r-- 1 root root 129 Aug 27 22:53 LMCEUpdate.log.3.gz
-rw-r--r-- 1 root root 129 Aug 27 22:53 UpdateHelper.log.3.gz
-rw-r--r-- 1 root root 238 Aug 27 22:31 died_66_66
-rw-r--r-- 1 root root 102 Aug 27 22:29 died_67_67
-rw-r--r-- 1 root root 102 Aug 27 22:25 died_68_68
-rw-r--r-- 1 root root 68 Aug 27 21:40 died_69_69
-rw-r--r-- 1 root root 1973 Aug 27 21:30 89_Generic_Serial_Device.log.2.gz
-rw-r--r-- 1 root root 1785 Aug 27 19:48 77_Generic_Serial_Device.log.2.gz
-rw-r--r-- 1 root root 1980 Aug 27 19:10 63_Generic_Serial_Device.log.3.gz
-rw-r--r-- 1 root root 146 Aug 27 19:10 PlutoServer.Logger.log.2.gz
-rw-r--r-- 1 root root 328 Aug 27 08:08 LaunchManager.log.4.gz
-rw-r--r-- 1 root root 20 Aug 27 08:08 UpdateMedia.log.3.gz
-rw-r--r-- 1 root root 20 Aug 27 08:08 Xconfigure.log.3.gz
-rw-r--r-- 1 root root 20 Aug 27 08:08 avremote_detect.log.3.gz
-rw-r--r-- 1 root root 20 Aug 27 08:08 avwizard_setup_av.log.3.gz
-rw-r--r-- 1 root root 20 Aug 27 08:08 xorg.conf.log.3.gz
-rw-r--r-- 1 root root 20 Aug 27 08:08 AVWizard.log.3.gz
-rw-r--r-- 1 root root 20 Aug 27 08:08 ConfirmDependencies.log.3.gz
-rw-r--r-- 1 root root 20 Aug 27 08:08 CreateDevice.log.3.gz
-rw-r--r-- 1 root root 140951 Aug 27 08:06 umount-wrapper.log.4.gz
-rw-r--r-- 1 root root 9586 Aug 27 08:06 pluto.log.4.gz
-rw-r--r-- 1 root root 10614 Aug 27 08:06 StorageDevices.log.4.gz
-rw-r--r-- 1 root root 3837 Aug 26 19:57 Config_Device_Changes.log.4.gz
-rw-r--r-- 1 root root 392 Aug 26 19:57 LaunchManager.progress.log.4.gz
-rw-r--r-- 1 root root 20 Aug 26 19:45 StorageDevices_Symlinks.log.4.gz
-rw-r--r-- 1 root root 99 Aug 26 19:45 SetupUsers_Homes.log.4.gz
-rw-r--r-- 1 root root 144 Aug 26 19:45 WatchGyro.log.4.gz
-rw-r--r-- 1 root root 92 Aug 26 19:45 LMCEUpdate.log.4.gz
-rw-r--r-- 1 root root 92 Aug 26 19:45 UpdateHelper.log.4.gz
-rw-r--r-- 1 root root 20 Aug 26 08:19 AVWizard.log.4.gz
-rw-r--r-- 1 root root 20 Aug 26 08:19 ConfirmDependencies.log.4.gz
-rw-r--r-- 1 root root 20 Aug 26 08:19 CreateDevice.log.4.gz
-rw-r--r-- 1 root root 20 Aug 26 08:19 UpdateMedia.log.4.gz
-rw-r--r-- 1 root root 20 Aug 26 08:19 Xconfigure.log.4.gz
-rw-r--r-- 1 root root 20 Aug 26 08:19 avremote_detect.log.4.gz
-rw-r--r-- 1 root root 20 Aug 26 08:19 avwizard_setup_av.log.4.gz
-rw-r--r-- 1 root root 20 Aug 26 08:19 xorg.conf.log.4.gz
-rw-r--r-- 1 root root 163072 Aug 26 08:18 umount-wrapper.log.5.gz
-rw-r--r-- 1 root root 6753 Aug 26 08:18 pluto.log.5.gz
-rw-r--r-- 1 root root 12193 Aug 26 08:18 StorageDevices.log.5.gz
-rw-r--r-- 1 root root 428 Aug 25 04:38 LaunchManager.log.5.gz
-rw-r--r-- 1 root root 20 Aug 25 04:38 StorageDevices_Symlinks.log.5.gz
-rw-r--r-- 1 root root 20 Aug 25 04:38 UpdateMedia.log.5.gz
-rw-r--r-- 1 root root 102 Aug 25 04:38 SetupUsers_Homes.log.5.gz
-rw-r--r-- 1 root root 43656 Aug 25 04:37 Config_Device_Changes.log.5.gz
-rw-r--r-- 1 root root 2397 Aug 25 04:37 LaunchManager.progress.log.5.gz
-rw-r--r-- 1 root root 20 Aug 25 04:35 ConfirmDependencies.log.5.gz
-rw-r--r-- 1 root root 1424 Aug 25 04:35 WatchGyro.log.5.gz
-rw-r--r-- 1 root root 46104 Aug 25 04:35 AVWizard.log.5.gz
-rw-r--r-- 1 root root 142 Aug 25 04:35 avwizard_setup_av.log.5.gz
-rw-r--r-- 1 root root 930 Aug 25 04:35 xorg.conf.log.5.gz
-rw-r--r-- 1 root root 20 Aug 25 04:34 Xconfigure.log.5.gz
-rw-r--r-- 1 root root 220 Aug 25 04:24 avremote_detect.log.5.gz
-rw-r--r-- 1 root root 92 Aug 25 04:24 LMCEUpdate.log.5.gz
-rw-r--r-- 1 root root 92 Aug 25 04:24 UpdateHelper.log.5.gz
-rw-r--r-- 1 root root 266 Aug 24 02:01 CreateDevice.log.5.gz
root@moon62:/var/log/pluto#
md that doesn't work - moon 79 - which has lots of kernmod logs.
root@moon79:/var/log/pluto# ls -lt
total 5668
-rw-r--r-- 1 root root 4146283 Aug 30 22:48 umount-wrapper.log
-rw-r--r-- 1 root root 333063 Aug 30 22:48 pluto.log
-rw-r--r-- 1 root root 174596 Aug 30 22:48 StorageDevices.log
-rw-r--r-- 1 root root 8192 Aug 30 22:11 81_App_Server.log
-rw-r--r-- 1 root root 2637 Aug 30 22:10 93_Disk_Drive.log
-rw-r--r-- 1 root root 2027 Aug 30 22:10 94_External_Media_Identifier.log
-rwxr-xr-T 1 root root 397 Aug 30 22:10 Spawn_serialports_10862.log
-rw-r--r-- 1 root root 952 Aug 30 22:10 running.pids
-rw-r--r-- 1 root root 3101 Aug 30 22:10 90_USB_UIRT_0038.log
-rw-r--r-- 1 root root 7603 Aug 30 22:10 Spawn_Device.log
-rw-r--r-- 1 root root 5617 Aug 30 22:10 82_LaunchOrbiter.sh.log
-rwxr-sr-T 1 root root 0 Aug 30 22:10 Spawn_setup_script_10876.log
-rwxr-sr-T 1 root root 0 Aug 30 22:10 Spawn_storagedevices_10863.log
-rwxr-sr-T 1 root root 0 Aug 30 22:10 Spawn_storagedevices_10871.log
-rwxr-sr-T 1 root root 0 Aug 30 22:10 Spawn_storagedevices_10872.log
-rwxr-sr-T 1 root root 0 Aug 30 22:10 Spawn_storagedevices_10858.log
-rw-r--r-- 1 root root 2454 Aug 30 22:10 84_HAL.log
-rw-r--r-- 1 root root 3220 Aug 30 22:10 LaunchManager.log
-rw-r--r-- 1 root root 0 Aug 30 22:09 StorageDevices_Symlinks.log
-rw-r--r-- 1 root root 660 Aug 30 22:09 SetupUsers_Homes.log
-rw-r--r-- 1 root root 537364 Aug 30 22:09 Config_Device_Changes.log
-rw-r--r-- 1 root root 14441 Aug 30 22:09 LaunchManager.progress.log
-rw-r--r-- 1 root root 720 Aug 30 22:09 LMCEUpdate.log
-rw-r--r-- 1 root root 720 Aug 30 22:09 UpdateHelper.log
-rw-r--r-- 1 root root 222 Aug 29 17:25 deaths
-rw-r--r-- 1 root root 204 Aug 29 17:25 died_82_82
-rwxr-xr-T 1 root root 1251 Aug 29 17:21 Spawn_not named_30940.log
-rwxr-xr-T 1 root root 397 Aug 29 16:24 Spawn_serialports_10487.log
-rwxr-sr-T 1 root root 0 Aug 29 16:23 Spawn_setup_script_10512.log
-rwxr-sr-T 1 root root 0 Aug 29 16:23 Spawn_storagedevices_10484.log
-rwxr-sr-T 1 root root 0 Aug 29 16:23 Spawn_storagedevices_10489.log
-rwxr-sr-T 1 root root 0 Aug 29 16:23 Spawn_storagedevices_10492.log
-rwxr-sr-T 1 root root 0 Aug 29 16:23 Spawn_storagedevices_10499.log
-rwxr-xr-T 1 root root 1251 Aug 28 13:54 Spawn_not named_17931.log
-rwxr-xr-T 1 root root 397 Aug 28 01:56 Spawn_serialports_28619.log
-rwxr-sr-T 1 root root 0 Aug 28 01:56 Spawn_setup_script_28641.log
-rwxr-sr-T 1 root root 0 Aug 28 01:56 Spawn_storagedevices_28620.log
-rwxr-sr-T 1 root root 0 Aug 28 01:56 Spawn_storagedevices_28625.log
-rwxr-sr-T 1 root root 0 Aug 28 01:56 Spawn_storagedevices_28626.log
-rwxr-sr-T 1 root root 0 Aug 28 01:56 Spawn_storagedevices_28534.log
-rw-r--r-- 1 root root 6241 Aug 28 01:55 80_Generic_Serial_Device.log
-rwxr-xr-T 1 root root 8076 Aug 27 23:38 Spawn_cdc_12920.log
-rwxr-xr-T 1 root root 31474 Aug 27 23:38 Spawn_cdc_11786.log
-rwxr-xr-T 1 root root 397 Aug 27 23:37 Spawn_serialports_11634.log
-rwxr-sr-T 1 root root 0 Aug 27 23:37 Spawn_storagedevices_11635.log
-rwxr-sr-T 1 root root 0 Aug 27 23:37 Spawn_storagedevices_11645.log
-rwxr-sr-T 1 root root 0 Aug 27 23:37 Spawn_storagedevices_11646.log
-rwxr-sr-T 1 root root 0 Aug 27 23:37 Spawn_storagedevices_11617.log
-rw-r--r-- 1 root root 0 Aug 27 21:08 UpdateMedia.log
-rw-r--r-- 1 root root 0 Aug 27 21:05 ConfirmDependencies.log
-rw-r--r-- 1 root root 305363 Aug 27 21:04 AVWizard.log
-rw-r--r-- 1 root root 239 Aug 27 21:04 avwizard_setup_av.log
-rw-r--r-- 1 root root 8585 Aug 27 21:04 xorg.conf.log
-rw-r--r-- 1 root root 0 Aug 27 21:03 Xconfigure.log
-rw-r--r-- 1 root root 1041 Aug 27 21:01 avremote_detect.log
-rw-r--r-- 1 root root 0 Aug 27 20:33 avremote.log
-rw-r--r-- 1 root root 66 Aug 27 20:33 kernmod.pluto-messagetrans.postinst.postinst.Thu, 27 Aug 2009 20:33:37 -0400.log
-rw-r--r-- 1 root root 66 Aug 27 20:33 kernmod.pluto-irbase.postinst.postinst.Thu, 27 Aug 2009 20:33:36 -0400.log
-rw-r--r-- 1 root root 66 Aug 27 20:33 kernmod.pluto-nvidia-video-drivers.postinst.postinst.Thu, 27 Aug 2009 20:33:03 -0400.log
-rw-r--r-- 1 root root 0 Aug 27 20:30 WatchGyro.log
-rw-r--r-- 1 root root 66 Aug 24 02:03 kernmod.pluto-pluto-media-db.postinst.postinst.Mon, 24 Aug 2009 06:03:03 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:03 kernmod.pluto-disc-drive-functions.postinst.postinst.Mon, 24 Aug 2009 06:03:02 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:02 kernmod.pluto-mythtv-player.postinst.postinst.Mon, 24 Aug 2009 06:02:42 +0000.log
-rw-r--r-- 1 root root 522 Aug 24 02:01 CreateDevice.log
-rw-r--r-- 1 root root 66 Aug 24 02:01 kernmod.pluto-orbiter.postinst.postinst.Mon, 24 Aug 2009 06:01:18 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:01 kernmod.pluto-boot-scripts.postinst.postinst.Mon, 24 Aug 2009 06:01:17 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:01 kernmod.pluto-createdevice.postinst.postinst.Mon, 24 Aug 2009 06:01:17 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-sdl-helpers.postinst.postinst.Mon, 24 Aug 2009 06:00:47 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-simplephone.postinst.postinst.Mon, 24 Aug 2009 06:00:47 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-add-software.postinst.postinst.Mon, 24 Aug 2009 06:00:46 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-disk-monitor.postinst.postinst.Mon, 24 Aug 2009 06:00:46 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-libserial.postinst.postinst.Mon, 24 Aug 2009 06:00:46 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-raid-tools.postinst.postinst.Mon, 24 Aug 2009 06:00:46 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-storage-devices.postinst.postinst.Mon, 24 Aug 2009 06:00:46 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-xine-player.postinst.postinst.Mon, 24 Aug 2009 06:00:46 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-dcecommon.postinst.postinst.Mon, 24 Aug 2009 06:00:45 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-pluto-main-db.postinst.postinst.Mon, 24 Aug 2009 06:00:45 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-plutoutils.postinst.postinst.Mon, 24 Aug 2009 06:00:45 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-serializeclass.postinst.postinst.Mon, 24 Aug 2009 06:00:45 +0000.log
-rw-r--r-- 1 root root 66 Aug 24 02:00 kernmod.pluto-app-server.postinst.postinst.Mon, 24 Aug 2009 06:00:29 +0000.log
root@moon79:/var/log/pluto#
advice welcome,
joseph
-
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:
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
-
Dear Phillippe,
the Spawn_Device.log would be interesting.
For sure not all of your devices are starting.
Question is which one. Hope to see it in Spawn_Device.log
On of possible next steps could be to increase loglevel
http://wiki.linuxmce.com/index.php/LogLevel (http://wiki.linuxmce.com/index.php/LogLevel)
Rgds
Peter
-
Hi Peter,
Here the inside of my Spawn_Device.log:
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 Philippe,
first please confirm once more, which of the devices is not showing up in the Spawn_Device.log
compared to your Device list.
Rgds
Peter
-
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 Philippe,
if you check the admin page, you can see the devices of your Md which should be there.
On the other hand you have your logfiles showing what is starting up.
e.g maybe xine player is not working properly....
Rgds
Peter
-
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
-
Hi Philippe,
could be, but I usually do not use this type of setup
I usually configure based on mac address the new MD on the admin site and then startup the
MD.
watchin the console Alt-F12 shows what it is doing.
Maybe this would give some hint on.
But this is also the reason why I asked to check on the web admin which devices are there
because if you see it on the web admin it means it is configured on the core/database
but maybe not on the MD.
Maybe a manual config might help
But before going into deep try once more a clean setup for the MD by first deleting everything from the Database related the one MD and go for a new install by preparing it on the web Admin and following on the
console of the MD
Rgds
Peter
-
I just posted a possible answer to this issue. I think you used version 177 of the nvidia drivers in a previous post but try version 173. It worked for me.
Here is the post that I explain the whole thing on:
http://forum.linuxmce.org/index.php?topic=8286.msg59879#msg59879
Hope this helps.
-
I had this problem (once I got my MD to actually boot - long story).
The logging screen (alt-F12) showed that it was unable to find a file (Modules.dep, I believe). So, on my core, I copied the file over from the core's directory to the MD's and then rebooted.
Just another possible solution for you!
-
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
-
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:
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 Peter,
Like I said to wierdbeard65 before, Alt-F12 screen, just after the black screen, give me nothing.
But it may be that it appears too fast.
I have look at the syslog and maybe I have find the problem.
I'm not sure (look at my previous post please) but the ObiterGL segfault can be the culprit.
I have the same errors on Kimberley MD:
dcerouter_1001352:/usr/pluto/bin# cat /usr/pluto/diskless/103/var/log/syslog |grep error
Sep 5 10:00:23 moon103 automount[473]: >> mount error 13 = Permission denied
Sep 5 10:00:23 moon103 kernel: [ 592.862866] CIFS VFS: Send error in SessSetup = -13
Sep 5 10:00:24 moon103 automount[1043]: >> mount error 13 = Permission denied
Sep 5 10:00:24 moon103 kernel: [ 593.820029] CIFS VFS: Send error in SessSetup = -13
Sep 5 10:00:37 moon103 kernel: [ 606.926909] OrbiterGL[1007]: segfault at 94 ip b7756305 sp b609bff0 error 4 in libstdc++.so.6.0.10[b76bf000+e3000]
Sep 5 10:01:04 moon103 kernel: [ 634.388416] OrbiterGL[2913]: segfault at 94 ip b77dc305 sp b6121ff0 error 4 in libstdc++.so.6.0.10[b7745000+e3000]
Sep 5 10:01:21 moon103 kernel: [ 651.308975] OrbiterGL[4507]: segfault at 94 ip b77e2305 sp b6127ff0 error 4 in libstdc++.so.6.0.10[b774b000+e3000]
Sep 5 10:14:18 moon103 automount[28441]: >> mount error 13 = Permission denied
Sep 5 10:14:18 moon103 kernel: [ 561.108374] CIFS VFS: Send error in SessSetup = -13
Regards,
Philippe
-
Hi Philippe,
check your /etc/fstab what should be mounted and if everything is mounted
you could also take a look in the mtab
looks like there are issues with mounting some of the filesystem over the net
try to mount manually
Rgds
Peter
-
I've just verify and all is mounted !
I've only grep the errors so, it is misleading.
Philippe
-
what about access rights?
in some other thread I saw also some setup issues related to some network switch problem.
are those MDs connected to other devices ore maybe (if managed) port setup different?
-
They have the same access and setup than the others.
For information, I've just delete and recreate the bad MD (with UI1).
If I check errors in this MD syslog, I found those:
dcerouter_1001352:~# cat /usr/pluto/diskless/116/var/log/syslog |grep error
Sep 6 14:14:30 moon116 kernel: [ 959.975449] LMCE_Launch_Man[29765]: segfaultat 0 ip 080648f8 sp b7a88130 error 4 in LMCE_Launch_Manager[8048000+41000]
Sep 6 14:14:36 moon116 kernel: [ 966.042011] CIFS VFS: Send error in SessSetup = -13
Sep 6 14:14:36 moon116 automount[31927]: >> mount error 13 = Permission denied
dcerouter_1001352:~#
I have a new segfault but it is now on LMCE_Launch_Man.
Everything is mounted, I have verify.
Philippe
-
Dear Philippe,
get a console on your MD and check
apt-get udate and upgrade
if upgrade says you need to dpkg --configure -a
some install did not finish
check also
/usr/pluto/bin/mythtv_setup.sh if it is executeable.
I had this issue now with the latest upgrade on the Core, which resulted in a broken setup an a blackscreen with white pointer
did a chmod 755 on mythtv_setup.sh
did apt-get upgrade
After that still there was the problem with the black screen and white pointer
and no way to activate my MythTV.
So I deleted all software from the OnScreen Orbiter (WebAdmin>Mediadirectors>affected Orbiter> Software Button)
I took off the pipe from all packages like MediaPlayer, MythTV BluetoothDongle......
Rebuilt Orbiter - Reload Router - working
Reactivated the Software in the WebAdmin - wait for install finished and reload Regen reload
Now working again
edit: after reboot not anymore working
Hope this helps for your problem as well.....
edit: so it will not help
Regards
Peter
-
Hello Peter,
I liked to announce it work, but it is allways the same.
After the update, dist-upgrade, deleted all software from the OnScreen Orbiter, rebuilt Orbiter and reload Router, it give only the bad screen.
I still tried reactivated the Software, Rebuilt Orbiter and reload router but I've nothing better.
I think I'm about to throw this MD to bulky !
The only positive point is that I did not have a segfault.
Regards,
Philippe
PS: Before post this, I've just read your edit ;-)
-
what does your MD do if u hit F8 , F6 and then F7 key?
does the orbiter appear?
for my broken core setup (still broken) this at least makes the orbiter come onto the screen
On startup it says Orbiter running on 127.0.0.1
This is just to verfy if it is the same problem
My MDs are not yet updated and still working fine
Rgds
Peter
-
Hi Peter,
The F6, F7 and F8 keys give nothing.
I think that the orbiter don't start.
Philippe
-
I have now reinstalled my core.
Still fighting with Xorg because of my old monitor which supports only special refresh rates.
Once I have my core Xorg up again I ll let you know.
What I found is some strange double entries in the Device status overview of the WebAdmin
( after deleting almost all I decided to reinstall the core bcause it became instable)
It showed more entries than the standard Device tree view
Maybe u find there a Orbiter plugin too much or some other App..
Rgds
Peter
Peter
-
Peter,
Did it work?
I still have two MDs that are affected. I also noticed that all of my MDs have a phantom TV device - "Acquos LCxxD6U / LCxxD7u/TV." I don't have any Acquos TV. I deleted it in the web admin and rebooted, but it was rediscovered.
I'm not sure if this has anything to do with the black screen & pointer, but thought I would mention the anomoly.
joseph
-
Please do an sqlcvs update of the dce repository. This was fixed a few weeks ago, and was the result of a bad checkin from a user.
-Thom
-
Thom,
much thanks! I'll try it when I get back.
To do the an sqlcvs update of the dce repository, do I follow the "Performing an update" procedure on the wiki page,
http://wiki.linuxmce.com/index.php/SqlCVS
Is this a remedy for the black screen as well, or simply the phantom TV devices?
thanks again,
joseph
-
Hello Peter,
Just to give you some news, I have change my "bad" MD (Salon) with another one and have just re-install the nvidiad board on it.
After a new boot and config I retrive the black screen with mouse pointer!
I continue my research.
Regards,
Philippe
PS: I have no multiple device on the MDs.
Only the core have those (4 Zwave controler !)
I ask to Hari, what I have to do.
-
Dear Philippe,
I think it is something with one of the latest updates.
I am playing now 2 days to setup my core - always starting into KDE
I now restarted another try from scratch
If any news I let you know
Rgds
Peter
-
Hi - not sure if I can shed any light.
I've been trying out LMCE for a while have loaded the August 24th version while trying to get video capture working from a Sat STB.
At some point, I was notified Ubuntu updates were available along with some LMCE ones. I happily accepted the offer to upgrade the system.
Everything went down hill after that and I'm now have the dreaded blank screen and the X-pointer.
What I did notice briefly on the core MD was a brief message just before everything went wrong similar to:
"Orbiter with same address as 127.0.0.1 detected & will be closed down".
Though its interesting to see you guys looking at logs to see what is wrong, IMHO it would be best to first determine what has changed.
Peter
-
After a Nightmare installation my core is up again.
Just UI1 but at least up.
I had issues on installation
After Kubuntu8.1 Aptidute and install_from_repo (this was all fine - didn't log into KDM only console)
I ran mce-installer
Now here the trouble started.
Error : package pluto-orbiter not found
package was available - don't know why it could not find it
After hours of trying I found that the setup is messing around with network interfaces
(yes I have 2 nics )
whatever I did (changing eth0 and eth1 or just cables) It always stopped there.
Disabled network setup in mce-install and run again - a lot of erreors complaining not beeing able to write to log
but at least it installed everything.
On start it could not connect to the DCERouter so I had to clean up the devices (many double entries)
Had to correct the Database Device for Nic ETH1 as it was in with {Extif} - IMHO some parsing error of the install script
Now setting up MythTV :-)
The Issue with the Blackscreen and Mousepointer is IMO a combination of xorg/driver/UI and some issues in the Launchmanager
to bring up the right screen to the front.
Maybe more when I setup my MD
But for sure dev's have to take a once more a look at it.
as there are more and more having similar issues
Rgds
Peter
-
Updated to previous post:
Now after manual install of Nvidia drivers (proprietary 180) and rerun of AVWizard
UI2 without alpha is running (didn't ry Alpha as it is not so important on the Core
But with standard nv driver MythTV was SlowMotion
All devices up and fine also Orbiter is not complaining about the 127.0.0.1 issue.
Now going to MD
This is an old NB with Radeon Mobility RV250 (9000) GPU
On boot setup runs , Orbiter generated (also checked parallel on WebAdmin) AvWizard failed
driver fglrx is not working with this old GPU
have to use radeon
after selecting RADEON on Webadmin for this MD
driver vesa is used
X is starting up
also AvWizard I could run
Result: BLACK SCREEN WITH MOUSE POINTER (and Orbiter Devices not showing up in Spawn file /usr/pluto/lock/
so
modprobe drm and radeon
depmod -a
putting an exit into Xconfigure (see wiki)
starting - no x
so I went on with
sudo apt-get remove --purge xorg-driver-fglrx
sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri
xorg.conf stays untouched
X is starting
and now Setup Video was started.......
after running through
Orbiter Regen is visible and then black screen with mouse pointer
But few seconds later -------- ORBITER is ON :-))))))))) and all devices as well (UI2 without Alpha)
So finally I can say for me it was a non clean installation of the video driver
(But maybe some dev made something during the last hours :-) but I think Thom was going to bed)
so now I still have to change the overlay screen and then I'm done
@Philippe
this brings us back to my first idea of xorg :-(
so maybe you check and google around to see for more details on your GPU and which driver is best
in any case check also the DISPLAY=:0.0 glxinfo |grep vendor
and make a clean uninstall of any previous driver
Rgds
Peter
-
Hello Peter,
I'm happy for you but... I've resolve my problem to ! ;-)
I'm not sure what the solution is because I've done 2 things:
1: I've remove a Dlink 8 ports switch and have connected the 2 bad MDs directly to the Linksys 16 ports switch
2: I've restart a AVWizard setup and selected UI2 directly.
Now, the 2 MDs worked !
The only things I have not resolve is that mythtv do not start directly after selected the TV menu button.
It give me the mythfrontend menu and when I start TV it stop after a few seconds.
So, it is better but not completly ok for me !
For me it is not a xorg problem but probably a script problem.
Regards,
Philippe
-
That sounds good
I think in both cases it is that the setup could not go to end.
The Mythtv made troubles here as well , but after several tries it reset the backend since then ok
Rgds
Peter
-
I have resolve my mythtv issue.
I have create some missings moonxx values in the mythconverg settings table:
BackendServerIP
BackendServerPort
BackendServerStatus
Change NetworkControlPort from 6546 to 10001 for the 2 lastest MD.
Run the mythtv_setup.pl file on the core.
Now mythtv work correctly.
Philippe