Hi, I've got a problem getting X to run on a new 9.2 install.. The installation process happily worked with my driver and monitor (Nvidia GeForce/CTX monitor) but any attempt to start X results in a blank screen with a large 'skeleton X' mouse cursor. I've tried sax2 -l but this always results in the same blank screen when I fire it up. Also tried Yast. This reports the card properly with a VESA monitor, but when I reprobe the monitor is identified correctly, However selecting this results in the same blank screen, as does selecting 'Change' to try with lower settings. I've checked .X.err and the X logs in /var/messages but, apart from loads of missing fonts these show no errors that I can see, they again report the card and monitor correctly. So, where do I go there - do I need to install and Nvidia driver first, or are they only needed for 3-D? TIA, Colin
On Sunday 20 March 2005 01:47 am, Colin Fraser wrote: Hi Colin,
I've tried sax2 -l but this always results in the same blank screen when I fire it up.
I don't understand what you mean here... sorry. Are you saying you're getting the "black screen of death" when: a) you actually try to invoke SaX2 in VGA mode using "sax2 -l" or... b) you've tested and saved your configuration and then tried to start X? This is an important distinction.
Also tried Yast. This reports the card properly with a VESA monitor, but when I reprobe the monitor is identified correctly, However selecting this results in the same blank screen, as does selecting 'Change' to try with lower settings.
I've seen mistakes in the hardware configuration database before, where the reported monitor bandwidth capabilities don't actually match what the monitor supports. In these cases, your only option is to set the monitor up manually by going into "expert" mode and defining the ranges yourself.
I've checked .X.err and the X logs in /var/messages but, apart from loads of missing fonts these show no errors that I can see, they again report the card and monitor correctly.
Of course. They're not getting any feedback from the monitor telling them that the graphics subsystem is sending signals that are out of range.
So, where do I go there - do I need to install and Nvidia driver first, or are they only needed for 3-D?
AFAIK, they're like all the others in this regard: they should support basic 'plain vanilla' VESA-compliant VGA mode straight out of the box. HTH & good luck! - Carl -- _______________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Keys 68396713 & F8207216 Reg. Linux User #350527 http://counter.li.org/ ----->>>>>http://www.fsf.org/campaigns/supportlinuxbios.html <<<<<-----
Carl, Please see below,my answers to your queries. Thanks for the interest! Colin Carl E. Hartung wrote:
On Sunday 20 March 2005 01:47 am, Colin Fraser wrote:
Hi Colin,
I've tried sax2 -l but this always results in the same blank screen when I fire it up.
I don't understand what you mean here... sorry. Are you saying you're getting the "black screen of death" when:
Not exactly the ''black screen ...th' . In all cases it's a blank screen but the cursor shows a a large-sh hollow 'X'.
a) you actually try to invoke SaX2 in VGA mode using "sax2 -l" or...
As soon Sax2 starts up!
b) you've tested and saved your configuration and then tried to start X?
This is an important distinction.
Also tried Yast. This reports the card properly with a VESA monitor, but when I reprobe the monitor is identified correctly, However selecting this results in the same blank screen, as does selecting 'Change' to try with lower settings.
I've seen mistakes in the hardware configuration database before, where the reported monitor bandwidth capabilities don't actually match what the monitor supports. In these cases, your only option is to set the monitor up manually by going into "expert" mode and defining the ranges yourself.
I missed 'expert mode' That,I think, is what I was looking for when I tried the 'Change' option.
I've checked .X.err and the X logs in /var/messages but, apart from loads of missing fonts these show no errors that I can see, they again report the card and monitor correctly.
Of course. They're not getting any feedback from the monitor telling them that the graphics subsystem is sending signals that are out of range.
So, where do I go there - do I need to install and Nvidia driver first, or are they only needed for 3-D?
AFAIK, they're like all the others in this regard: they should support basic 'plain vanilla' VESA-compliant VGA mode straight out of the box.
HTH & good luck!
- Carl
On Sunday 20 March 2005 01:40 pm, Colin.Fraser wrote:
Carl, Please see below,my answers to your queries. Thanks for the interest!
You're welcome, but I'm really late getting out of here, so this has to be a short reply.
Not exactly the ''black screen ...th' . In all cases it's a blank screen but the cursor shows a a large-sh hollow 'X'.
This is an important clue. If that 'large-ish' hollow 'X' moves around with your mouse, it's probably not wrong monitor settings but something else entirely. I'll quickly cover some of the basics and sorry if you know all of this stuff already: Don't invoke SaX2 in run level 5 (when X is running.) Do one or the other: a) Boot into run level 3 (hit the number "3" key before selecting SuSE at the boot menu, or b) at the 'black' screen with the hollow 'X', do 'Ctl+Alt+F2' (F3 to F6 also work) to switch to another, text-based, console. Log in as root and run "init 3" to drop down to run level 3, where X is shut down but you've still got networking and multi-user support. Once you're sure X is down, do the "sax2 -l" drill all over again and try to stick with the defaults since you've said the hardware detection appears to be accurate. Test the settings, modify them as needed then save them before exiting SaX2. When you're back at the command prompt, as root, issue "init 5" which will launch X using KDM or GDM. You should arrive at a normal (graphical) greeter/login screen. You then need to verify that you're logging into your 'normal' desktop, either KDE or GNOME, and that the environment is loading correctly. Try this, see what happens and report back. I'll catch up on your progress by reading the thread late tonight or tomorrow. regards, - Carl -- ___________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Keys 68396713 & F8207216 Reg. Linux User #350527 http://counter.li.org/ --->>>>>http://www.fsf.org/campaigns/supportlinuxbios.html <<<<<---
participants (3)
-
Carl E. Hartung
-
Colin Fraser
-
Colin.Fraser