[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: need help getting X server running...



I'm pretty new to Linux myself, and don't know how to redirect the output
messages of startx to a file, though I'm confident it can be done. Maybe
someone else can enlighten us on the details.

However, what you can do, is press Shift-PgUp; apparently Debian keeps a
buffer of the last couple of screens, and Shift-PgUp/Dwn will navigate
through them.

This method has allowed me to see the pertinent info I needed to get my X
up and running.

===================================== >
Kent West		       ==== >
kent.west@infotech.acu.edu   ==== >
KC5ENO			   ==== >
============================= >

A day without sunshine is like... night.
	-Steve Martin

On Sat, 24 Oct 1998, Jesse Evans wrote:

> Folks,
> 
>     Thanks for the tips, but so far still no joy.
> 
>     Regarding posting all the messages, I can't even read them all.
> As the messages start to scroll up, the display blinks (trying to go into
> graphics mode, I suspect,) then comes back to text.
> Most of the (**) messages run past during this blank-out time.
> 
>     How can I capture these messages into a file so that I
> may be able to see what's going on? I've tried looking in /var/log
> to see if anythere seems related, but haven't found anything.
> I think what I want to do is redirect stderr into a file, but
> I'm new to linux and don't know how to make that happen.
> 
> 
> -----Original Message-----
> From: Kent West <kent.west@infotech.acu.edu>
> To: Jesse Evans <jpjevans@earthlink.net>; Debian User Mail List
> <debian-user@lists.debian.org>
> Date: Thursday, October 22, 1998 7:54 AM
> Subject: Re: need help getting X server running...
> 
> 
> >At 09:06 PM 10/21/1998 -0700, Jesse Evans wrote:
> >>
> >> Folks,
> >>
> >>
> >>
> >>     (a long list of messages which scroll up the screen, followed by...)
> >>
> >>     *** none of the configured devices were detected ***
> >>    Fatal server error: no screens found
> >>    - X11 TransSocketUNIXConnect: Can't connect: errno = 111
> >>    giving up.
> >>
> >>    xinit: connection refused (errno 111) unable to connect to xserver
> >>    xinit: no such process (errno 3): server error
> >>
> >>    I'm running on a 133Mhz Intel PC with a Trident 9440 graphics chip.
> What
> >> is going on?
> >
> >
> >Also, post the full list of errors instead of just the last one about
> >TransSocket.....
> >
> >It's been my experience that by looking at those messages I'll see
> something
> >like "800x600 mode requires a horiz rate of 64), and then I can go bump up
> the
> >horiz rate in XF86Config to that setting (careful that you don't smoke your
> >monitor by pushing beyond it's capabilities) and get a working res.
> >
> >================================================
> >Kent West, Technology Support
> >kent.west@infotech.acu.edu
> >Abilene Christian Univ., Abilene, TX
> >915-674-2557  FAX: 915.674.6724
> >Amateur Radio: KC5ENO
> >Debian Linux: Ride the wave with the penguins!
> 
> >
> 
> 'til next we type...
> HAVE FUN!! -- Jesse
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
> 


Reply to: