|
pga57
|
 |
« on: August 18, 2009, 09: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
|
|
|
|
« Last Edit: September 01, 2009, 09:54:58 am by pga57 »
|
Logged
|
|
|
|
colinjones
Alumni
LinuxMCE God

Posts: 3003
|
 |
« Reply #1 on: August 18, 2009, 03:14:52 pm » |
|
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...
|
|
|
|
|
Logged
|
|
|
|
|
pga57
|
 |
« Reply #2 on: August 18, 2009, 05:26:59 pm » |
|
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
|
|
|
|
|
Logged
|
|
|
|
pigdog
wants to work for LinuxMCE
 
Posts: 783
|
 |
« Reply #3 on: August 18, 2009, 05:33:34 pm » |
|
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?
|
|
|
|
|
Logged
|
|
|
|
|
pga57
|
 |
« Reply #4 on: August 18, 2009, 07:54:51 pm » |
|
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
|
|
|
|
|
Logged
|
|
|
|
pigdog
wants to work for LinuxMCE
 
Posts: 783
|
 |
« Reply #5 on: August 18, 2009, 08:11:19 pm » |
|
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.
|
|
|
|
|
Logged
|
|
|
|
|
pga57
|
 |
« Reply #6 on: August 18, 2009, 08:52:22 pm » |
|
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
|
|
|
|
|
Logged
|
|
|
|
|
PeterSchmid
|
 |
« Reply #7 on: August 18, 2009, 11:15:21 pm » |
|
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
|
|
|
|
|
Logged
|
|
|
|
|
pga57
|
 |
« Reply #8 on: August 19, 2009, 07:55:18 am » |
|
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
|
|
|
|
|
Logged
|
|
|
|
|
PeterSchmid
|
 |
« Reply #9 on: August 19, 2009, 10:58:17 pm » |
|
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
|
|
|
|
|
Logged
|
|
|
|
|
pga57
|
 |
« Reply #10 on: August 20, 2009, 06:29:03 am » |
|
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
|
|
|
|
|
Logged
|
|
|
|
|
ladekribs
|
 |
« Reply #11 on: August 20, 2009, 07:10:42 am » |
|
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
|
|
|
|
|
Logged
|
|
|
|
|
|
|
PeterSchmid
|
 |
« Reply #13 on: August 20, 2009, 10:48:37 pm » |
|
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
|
|
|
|
« Last Edit: August 20, 2009, 11:19:17 pm by PeterSchmid »
|
Logged
|
|
|
|
|
PeterSchmid
|
 |
« Reply #14 on: August 20, 2009, 11:52:05 pm » |
|
please also try to switch off the screensaver on th MD
Web Administration MediaDirector > Software modules -> Edit Deselect ScreenSaver
Reload
Regards
Peter
|
|
|
|
|
Logged
|
|
|
|
|