X won't start, no errors in XFree86.0.log

X won't start, no errors in XFree86.0.log

[Jonathan Kallay]

I have been able to start X Windows in the past, but after plugging in a
different monitor (and changing the configuration file), startx will cause
the screen to go blank and never come back.  CTRL-ALT-BKSP won't work.  The
only way that I can see what is going on is by telnetting in from a
different computer and running startx.  No errors appear in the log file,
other than "Failed to load GLCore (module does not exist, 0)".  The very
bottom of the output reads:
 (II) [GLX]: Initializing GLX extension
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.

Any suggestions?


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: X won't start, no errors in XFree86.0.log

[Ray Olszewski]

At 02:38 PM 1/12/03 -0500, Jonathan Kallay wrote:
>I have been able to start X Windows in the past, but after plugging in a
>different monitor (and changing the configuration file), startx will cause
>the screen to go blank and never come back.  CTRL-ALT-BKSP won't work.  The
>only way that I can see what is going on is by telnetting in from a
>different computer and running startx.  No errors appear in the log file,
>other than "Failed to load GLCore (module does not exist, 0)".  The very
>bottom of the output reads:
>  (II) [GLX]: Initializing GLX extension
>XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
>       after 0 requests (0 known processed) with 0 events remaining.
>
>Any suggestions?

When I experience similar problems, the usual cause is a vsync or hsync 
value that the monitor does not support. Sensible monitors (pretty much all 
of them, these days) tuen themselves off under when they get settings that 
are inconsistent with their hardware capabilities. Since you say you 
plugged in a difeent monitor, this seems like the first thing to check ... 
that is, when you changed the configuration file, did you do so in a way 
consistent with the new hardware? I can't be more specific because you 
haven't provided any details (like what version of XFree86, what video 
driver, and what monitor ... and what config-file changes).

Aside from that, you say that "CTRL-ALT-BKSP won't work". So ...

Does CTRL-ALT-F1 (or the F* value for whatever vt you ran startx from) work 
to restore a console?

Does killing the startx process from the telnet session restore a console?

Does flipping through your specified modes (with CTRL-ALT-+) ever produce a 
mode that works?

Does powering the monitor off, then back on, have any effect?

BTW, you characterize this problem as " X won't start". My response assumes 
this characterization is wrong ... that is, that if you do a "ps ax" from 
yout telnet session, you will see X processes (startx, X, maybe a font 
manager or a wm, and maybe others) listed as running. If I am mistaken in 
this ... if instead you mean that startx actually exits and still leaves 
the display blank, without a vt showing, please be specific about that.


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: X won't start, no errors in XFree86.0.log

[Jonathan Kallay]

Ray,
  Thanks for the response.  Here are the answers to your questions, in no
particular order.
  I changed the vsync and hsync values according to the specs I looked up on
www.monitorworld.com, which are also consistent with the monitor type: a
mid-to-low-end 15" monitor.

 CTRL-ALT-F* does not work.  There are no X processes running- so X did, in
fact, fail to start.  I tried turning off the monitor, disconnecting it from
the video card, powering it on, turning it off, reconnecting it, and
powering it on again.  The monitor will "click" after a few seconds, as if
it is going into suspend mode, but the power light won't change to orange.

I can switch to a different virtual terminal, blindly login and type
commands, and they will work (e.g. shutdown -r now will reboot the machine)
.  So it looks like the display is being knocked out without coming back up
once X terminates.  I am using an NVidia TNT2 video card with the standard
nv driver.
----- Original Message -----
From: "Ray Olszewski" <ray@comarre.com>
To: <linux-newbie@vger.kernel.org>
Sent: Sunday, January 12, 2003 2:51 PM
Subject: Re: X won't start, no errors in XFree86.0.log


> At 02:38 PM 1/12/03 -0500, Jonathan Kallay wrote:
> >I have been able to start X Windows in the past, but after plugging in a
> >different monitor (and changing the configuration file), startx will
cause
> >the screen to go blank and never come back.  CTRL-ALT-BKSP won't work.
The
> >only way that I can see what is going on is by telnetting in from a
> >different computer and running startx.  No errors appear in the log file,
> >other than "Failed to load GLCore (module does not exist, 0)".  The very
> >bottom of the output reads:
> >  (II) [GLX]: Initializing GLX extension
> >XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
> >       after 0 requests (0 known processed) with 0 events remaining.
> >
> >Any suggestions?
>
> When I experience similar problems, the usual cause is a vsync or hsync
> value that the monitor does not support. Sensible monitors (pretty much
all
> of them, these days) tuen themselves off under when they get settings that
> are inconsistent with their hardware capabilities. Since you say you
> plugged in a difeent monitor, this seems like the first thing to check ...
> that is, when you changed the configuration file, did you do so in a way
> consistent with the new hardware? I can't be more specific because you
> haven't provided any details (like what version of XFree86, what video
> driver, and what monitor ... and what config-file changes).
>
> Aside from that, you say that "CTRL-ALT-BKSP won't work". So ...
>
> Does CTRL-ALT-F1 (or the F* value for whatever vt you ran startx from)
work
> to restore a console?
>
> Does killing the startx process from the telnet session restore a console?
>
> Does flipping through your specified modes (with CTRL-ALT-+) ever produce
a
> mode that works?
>
> Does powering the monitor off, then back on, have any effect?
>
> BTW, you characterize this problem as " X won't start". My response
assumes
> this characterization is wrong ... that is, that if you do a "ps ax" from
> yout telnet session, you will see X processes (startx, X, maybe a font
> manager or a wm, and maybe others) listed as running. If I am mistaken in
> this ... if instead you mean that startx actually exits and still leaves
> the display blank, without a vt showing, please be specific about that.
>
>
> --
> -------------------------------------------"Never tell me the
odds!"--------
> Ray Olszewski -- Han Solo
> Palo Alto, California, USA   ray@comarre.com
> --------------------------------------------------------------------------
-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: X won't start, no errors in XFree86.0.log

[Ray Olszewski]

Since my initial interpretation of your problem was wrong, I don't really 
have anything to suggest in particular ... only the general suggestion that 
you (or we) examine the startx output to STDERR for more information. If 
you want help at that level, please send us a followup with the redirected 
STDERR output. Also tell us what version of XFree86 you use, and what 
monitor. Oh yes, and what version of Linux (what distro, what kernel) ... 
just in case that matters.

I don't use nVidea stuff myself, so I don't know whether "the standard nv 
driver" means the binary-only one that nVidea provides or the Open Source 
one someone else now ships. Either, I'm told, can be the source of problems 
... the one from nVidea doesn't get satisfactorily updated, and the Open 
Source one suffers from a lack of cooperation from nVidea.

The symptoms leave me suspecting that the video card is getting switched to 
a mode that the monitor cannot support (not hard to do, unfortunately - I 
often do it with X and with MS Windows) and that X cannot switch out of 
when exiting. But without the details, that can be no more than a vague 
guess. For real help, someone else on the list, someone who has actually 
used nVidea hardware and drivers, should jump in.

At 03:46 PM 1/12/03 -0500, Jonathan Kallay wrote:
>Ray,
>   Thanks for the response.  Here are the answers to your questions, in no
>particular order.
>   I changed the vsync and hsync values according to the specs I looked up on
>www.monitorworld.com, which are also consistent with the monitor type: a
>mid-to-low-end 15" monitor.
>
>  CTRL-ALT-F* does not work.  There are no X processes running- so X did, in
>fact, fail to start.  I tried turning off the monitor, disconnecting it from
>the video card, powering it on, turning it off, reconnecting it, and
>powering it on again.  The monitor will "click" after a few seconds, as if
>it is going into suspend mode, but the power light won't change to orange.
>
>I can switch to a different virtual terminal, blindly login and type
>commands, and they will work (e.g. shutdown -r now will reboot the machine)
>.  So it looks like the display is being knocked out without coming back up
>once X terminates.  I am using an NVidia TNT2 video card with the standard
>nv driver.

[old stuff deleted]



--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: X won't start, no errors in XFree86.0.log

[Jonathan Kallay]

I had already compiled the nVidia driver but had not yet replaced the Driver
line in XF86Config with the new driver- the nVidia docs suggested getting
the X setup working first with the "nv" driver before switching to theirs.
Just for kicks, I tried the nVidia driver, and lo and behold, it works.

>
> The symptoms leave me suspecting that the video card is getting switched
to
> a mode that the monitor cannot support (not hard to do, unfortunately - I
> often do it with X and with MS Windows) and that X cannot switch out of
> when exiting. But without the details, that can be no more than a vague
> guess. For real help, someone else on the list, someone who has actually
> used nVidea hardware and drivers, should jump in.
>
> At 03:46 PM 1/12/03 -0500, Jonathan Kallay wrote:
> >Ray,
> >   Thanks for the response.  Here are the answers to your questions, in
no
> >particular order.
> >   I changed the vsync and hsync values according to the specs I looked
up on
> >www.monitorworld.com, which are also consistent with the monitor type: a
> >mid-to-low-end 15" monitor.
> >
> >  CTRL-ALT-F* does not work.  There are no X processes running- so X did,
in
> >fact, fail to start.  I tried turning off the monitor, disconnecting it
from
> >the video card, powering it on, turning it off, reconnecting it, and
> >powering it on again.  The monitor will "click" after a few seconds, as
if
> >it is going into suspend mode, but the power light won't change to
orange.
> >
> >I can switch to a different virtual terminal, blindly login and type
> >commands, and they will work (e.g. shutdown -r now will reboot the
machine)
> >.  So it looks like the display is being knocked out without coming back
up
> >once X terminates.  I am using an NVidia TNT2 video card with the
standard
> >nv driver.
>
> [old stuff deleted]
>
>
>
> --
> -------------------------------------------"Never tell me the
odds!"--------
> Ray Olszewski -- Han Solo
> Palo Alto, California, USA   ray@comarre.com
> --------------------------------------------------------------------------
-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: X won't start, no errors in XFree86.0.log

[pa3gcu]

On Wednesday 15 January 2003 21:15, Jonathan Kallay wrote:
> I had already compiled the nVidia driver but had not yet replaced the
> Driver line in XF86Config with the new driver- the nVidia docs suggested
> getting the X setup working first with the "nv" driver before switching to
> theirs. Just for kicks, I tried the nVidia driver, and lo and behold, it
> works.

The reason nvidia say get X working with the "nv" driver from XFree first is 
for the reason that if the nv driver works then all one needs to do is change 
one line in his/her XF86Config file, (2 lines could need altering as well), 
but thats why they say get it working with nv first.

The other point here is, you say you had compiled the NVdriver modules from 
nvidia but had not changed the XF86onfig file, that would explain the reason 
why X complained about not finding the module extention, GLX i belive it was, 
if you had noticed in the documantation that is explained in a round about 
way that if you compile the driver and kernel file then things get changed 
and replaced, that is the reason you were getting such an error message.

Now you can see the differance in video performance between nv and the 
NVdriver espesialy if you have a DVD player.

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: X won't start, no errors in XFree86.0.log

[pa3gcu]

On Sunday 12 January 2003 19:38, Jonathan Kallay wrote:
> I have been able to start X Windows in the past, but after plugging in a
> different monitor (and changing the configuration file), startx will cause
> the screen to go blank and never come back.  CTRL-ALT-BKSP won't work.  The
> only way that I can see what is going on is by telnetting in from a
> different computer and running startx.  No errors appear in the log file,
> other than "Failed to load GLCore (module does not exist, 0)".  The very
> bottom of the output reads:
>  (II) [GLX]: Initializing GLX extension
> XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
>       after 0 requests (0 known processed) with 0 events remaining.
>
> Any suggestions?

Yes, i do have some suggestions. 
I read your reply to Ray as well where you say you use the nv driver which is 
from XFree.

Firstly if you use a 2.2.xx kernel i would stongly advise you to get the 
relavant driver for your card from www.nvidia.com and install it.
You will see a lot of improvements to video speed and quality.

To adress your problem as is, the GLX module as its called resides in 
/usr/X11R6/lib/modules/extensions/
Check and make sure its there, according to your error its not.

What i dont understand is why should it dissapier if all you did was plugin 
another monitor and edit XF86Config(-4).

Normally speaking i never edit anything when changing monitors as they are 
basicly all the same, i mean they will work even if they are configured 
wrongly, (yes) the doc's say you can damage a monitor by giving incorrect 
params to XF86Config, however times change, most all monitors thesedays will 
simply give a click and not show any screen or show a screen with horizontal 
or vertical strips and no picture.

If all you did was edit XF86Config(-4) and change the monitor then i cant see 
why you lost a extention module, you must have done something else like 
install some software or you have made an typo in your XF86Config(-4) file.

Do as Ray said and give us more details.

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs