Bug 228791

http://www1.ap.dell.com/content/products/productdetails.aspx/2007wfp?c=au&l=en&s=dhs
X problems?
Or SaX problems?
Marcus, can you help? 

looks like a driver problem 

Could you reboot into runlevel 3 after the problem has occured and attach /etc/X11/xorg.conf and /var/log/Xorg.0.log? Thanks.

Created attachment 110156 [details]
var/log/Xorg.0.log

Created attachment 110157 [details]
etc/X11/xorg.conf

Nothing obvious I can see. Please also attach a logfile of the Xserver when the problem does not occur. So I can compare both logfiles.

Created attachment 110206 [details]
etc/X11/xorg.conf

Created attachment 110207 [details]
var.log/Xorg.0.log

I may have sent you a log file from a boot strait into lvl 3 the first time, these two were grabbed with the system was displaying black and I sshed into it with my laptop

There is no relevant difference between both logfiles. :-( So it's strange to see that the Xserver sometimes works, sometimes doesn't.

I suggest to use the NVIDIA driver for now - in case that's an option for you.

  http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html#1

that is just the thing, the x server never properly works. I have yet to see the graphical aspect of openSUSE 10.2 on this machine. I have been messing around in lvl 3 only (lvl 5 never loads for me to use, that is when it hangs, or whatever the term is [I think it is when init is running the call to load the WM])

Ok. In runlevel 3 when you execute manually /usr/bin/Xorg. What does happen. Does this still look correct?

ok when I execute Xorg I get the mouse as a black X (it is responsive), the background is a gray pattern.

Hmm ... this looks good. Ok, try this scenario (minimalistic fvwm2 based desktop)

  X -ac & sleep 3; DISPLAY=:0 fvwm2

or even

  X -ac & sleep 3; DISPLAY=:0 twm

Is this desktop usable? Of course you can start these commands when you have logged in via ssh - always recommend when debugging any Xserver issues.

X -ac & sleep 3; DISPLAY=:0 fvwm2 does launch a usable desktop.

Looks like progress to me :-)

Ok. Then I suggest to switch to xdm as displaymanager and check if it's related to the currently used displaymanager.

--> /etc/sysconfig/displaymanager

Set DISPLAYMANAGER to "xdm". Let me know which value was set before. Then start "rcxdm start". What do you see. Can you log in?

the value was "gdm".
I then started "rcxdm start" and the terminal said "done" but nothing had changed.

I then restarted hoping that lvl 5 would now be functional but again the system displays nothing other than a black screen and a X for your mouse when it boots.

So neither gdm nor xdm works on your Xserver. Very strange. Log in as normal user in runlevel 3 and try "startx". Maybe this will work for you.

(In reply to comment #17)
> the value was "gdm".
> I then started "rcxdm start" and the terminal said "done" but nothing had
> changed.
> 
> I then restarted hoping that lvl 5 would now be functional but again the system
> displays nothing other than a black screen and a X for your mouse when it
> boots.
> 

Just a clarification, the value WAS "gdm", I changed it to "xdm" then I started "rcxdm start"

sry forgot to make sure the info box was checked so this is a pointless comment just to get it assigned 

See my new comment #18.

ok running startx causes gnome to start. (After comment 17 I changed the value of DISPLAYMANAGER back to gdm.) however, I cannot got the main menu in gnome to open. I can add new panels, I can add things to the panels  and it looks like all the things I add to panels work with the notable exception of the main menu.

I think you need to press the right mouse button to activate the Gnome main menu. If this was not the problem I suggest to ' Option "noaccel" ' to your device sections of xorg.conf. BTW, I wonder that you have a dualhead setup ?!?

right clicking does not bring up the menu.

after adding the Option "noaccel" I attempted a boot into lvl 5 with the same black screen with a responsive mouse. I then booted into lvl 3 and ran startx but I still get the same crippled gnome.

a dualhead setup?

I have:
Gigabye GA-K8NXP-SLI ( http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=1859 )
AMD 3200+ 64-bit (I opt to run x86 until 64-bit become a little more supported)
Dell 2007WFP display
NVIDIA GeForce 6600 (2x in windows I run SLi)(the noaccel option was added bor both of them in xorg.conf)( http://www.nvidia.com/object/geforce6_techspecs.html )

It is the exact rig that I have use to run SUSE since the launch of 10.0 with the exception of the Dell display, about 3 weeks ago I upgraded from my old CRT. so the display and the fact that it is run using DVI rather then VGA are all that has changed. That and the new release of openSUSE.

OK. DVI via nv driver can definitely be a problem. And this one really doesn't look good (no TFT detected, instead CRT output is assumed).

(II) NV(0): I2C bus "DDC" initialized.
(II) NV(0): Probing for analog device on output A...
(--) NV(0):   ...can't find one
(II) NV(0): Probing for analog device on output B...
(--) NV(0):   ...can't find one
(II) NV(0): Probing for EDID on I2C bus A...
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(II) NV(0):   ... none found
(II) NV(0): Probing for EDID on I2C bus B...
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(II) NV(0):   ... none found
(II) NV(0): Unable to detect display type...
(==) NV(0): ...Using default of CRT
(II) NV(0): Unable to detect which CRTCNumber...
(==) NV(0): ...Defaulting to CRTCNumber 0
(II) NV(0): Using CRT on CRTC 0

I still have no SLI setup available for testing. :-(  I propose either to switch to the nvidia driver or create a single head configuration via SaX2.
"sax2 -c 0" or "sax2 -c 1" should do the trick.

It looks very similar to bug #176265.

I can not access bug 17625.
I installed the nvidia driver, runlevel 5 is still not functional. A few of the GUI elements are kinda quirky, but it seems as though everything is functional if I just boot into lvl 3 and run startx.

I can not get sax2 -c 0 or sax2 -c 1 to do anything and the GUI element to access sax2 does not work.

Proably you need to call "sax2 -r -a -c 0" / "sax2 -r -a -c 1" instead to generate an automatic configuration.

I ran "sax2 -r -a -c 0" which launched the automatic configuration and now the display will not display again. I am gonna try a fresh install with VGA and see if that works, if not I have a space 19" LCD on a different comp that I can swap out.

It doesn't make sense trying to investigate this issue any longer without any SLI hardware available. Setting to LATER for now. As already said I can only recommend to switch to the proprietary driver of NVIDIA.

Unfortunately I cannot reproduce this SLI problem with our 2x 7600 PCIe SLI
setup (there are different problems). I would need two GF 6600 PCIe cards for
reproducing the described problem.

Reopen.

Any improvements with openSUSE 10.3 Beta1?

downloading the cd now, should install towards the end of the week to see if their is any change. I have been running the system in normal mode rather than SLi mode while in Linux since the problem was closed months ago.

any update?

I have been running openSUSE 10.3 for the past hour or so with the computer in SLi mode with dual monitors and I have not seen any problems. Looks like 10.3 fixed it, thanks.

Ok.