Folks,
I've recently installed debian on my PC and can't get the X server
working. I've run the XF86Setup app and it completed sucessfully, telling
me I had established a properly working server, but when I quit, saving
the config to XF86Config, and run startx, I get the following:
What I don't really understand is why XF86Setup was able to function
just
fine with the S3 setup, but the actual S3 X server package failed...
But I'm
just trying not to think about it too much.
=
That's because XF86Setup doesn't use the
I have kdm starting at bootup to provide a login screen. so crtl-alt
backspace just restarts the unseen login screen.
On Mon, 31 Aug 1998 17:58:20 -0500 Kent West [EMAIL PROTECTED]
writes:
I'd try Ctrl-Alt-Backspace.
At 06:48 PM 8/31/1998 -0400, Brian D Kellogg wrote:
I set my default color
you can use ctrl-alt-F1 to switch to virtual console 1 from X. this should
give you a console login prompt. to get back to X, press alt-F7.
good luck,
ccg
On Mon, 31 Aug 1998, Brian D Kellogg wrote:
I have kdm starting at bootup to provide a login screen. so crtl-alt
backspace just
use crtlaltF1
this will get you a non-X login screen. You can then log in as root
an fix the problem.
_
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
At 06:48 PM 8/31/1998 -0400, Brian D Kellogg wrote:
I set my default color depth to 32 bit and now nothing displays on my
screen. Is there a way to exit it back to the prompt so I can change
the
default back to 24 bit.
thanx,
Brian
On Mon, 31 Aug 1998 17:58:20 -0500 Kent West [EMAIL
I set my default color depth to 32 bit and now nothing displays on my
screen. Is there a way to exit it back to the prompt so I can change the
default back to 24 bit.
thanx,
Brian
I'd try Ctrl-Alt-Backspace.
At 06:48 PM 8/31/1998 -0400, Brian D Kellogg wrote:
I set my default color depth to 32 bit and now nothing displays on my
screen. Is there a way to exit it back to the prompt so I can change the
default back to 24 bit.
thanx,
Brian
--
Unsubscribe? mail -s
Over the past four days, I have struggled with this recurring
problem. It first occurred when I installed the newest package version
of xbase and xserver-svga from the debian mirrors. I had also switched
to WindowMaker, so I thought maybe the problem was there.
So far: it hasn't happened to me
I have a feeling that it's your RAM. Have you tried the memtest
program? I myself have been running the latest slink xfree86 with no
problems whatsoever. If I were you I would try out memtest on
different combinations of your SIMMs.
Bake
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
I am running Debian 1.31.
I have a Novell 4.x server that is running Novel's IP system on it. I
can telnet to the server but it comes up and asks me if I want to use
the default X console display to work with. I have tried the default,
and setting it myself to no avail.
Accelerated X did not seem to
work, is it possible that I had to upgrade my version of the Xlibs since I
only upgraded the core system and not the X system? And... if that is true,
would my original plan of installing Xfree86 3.3.2 glibc2 while resymlinking my
Accelerated X binary help me get glibc2 working
Carroll Kong wrote:
I ran this
/home/damascus% xset r rate
Xlib: extension XFree86-Misc missing on display :0.0.
server does not have extension for r rate option
I get this odd error... when i try to run xset r rate? Not sure if I ran it
improperly... but the idea of me missing an
Hi Carroll,
happy. :) I use Accelerated X, but since that is a mere XServer binary,
(right?) can I install a glibc2 or libc5 version of XFree86 3.3.2 into
/usr/X11R6 and re symlink my Accelerated X binary to X and still expect it
to
work?
Debian's X is not a symbolic link. It is an
At 08:50 AM 12/12/97 +0100, Sten Anderson wrote:
Tommy Lakofski [EMAIL PROTECTED] writes:
whoops, this should have gone to the list too.
-- Forwarded message --
On Thu, 11 Dec 1997, Hamish Moffatt wrote:
[ I said: ]
It is NOT necessary for the last command to be
On 12 Dec 1997, Sten Anderson wrote:
Tommy Lakofski [EMAIL PROTECTED] writes:
Yes, by using exec to launch a command from a script, the process
associated with the script (/bin/sh) is replaced by the process
associated with the command. This saves a few system resources, since
the script
whoops, this should have gone to the list too.
-- Forwarded message --
On Thu, 11 Dec 1997, Hamish Moffatt wrote:
It is NOT necessary for the last command to be started with exec. In
fact, exec should only be used on the window manager, and only if that
is the last command
Tommy Lakofski [EMAIL PROTECTED] writes:
whoops, this should have gone to the list too.
-- Forwarded message --
On Thu, 11 Dec 1997, Hamish Moffatt wrote:
[ I said: ]
It is NOT necessary for the last command to be started with exec. In
fact, exec should only be
At 09:15 AM 12/10/97 -0600, Jens B. Jorgensen wrote:
These messages do not indicate a fatal error, only that you haven't
installed these X extensions. If you're using your own .xinitrc,
are you sure that the last command uses 'exec' rather than just
running a program? This would cause the X server
At 04:32 PM 12/10/97 +0100, Sten Anderson wrote:
Jens B. Jorgensen [EMAIL PROTECTED] writes:
These messages do not indicate a fatal error, only that you haven't
installed these X extensions. If you're using your own .xinitrc,
are you sure that the last command uses 'exec' rather than just
On Wed, Dec 10, 1997 at 05:51:40AM +0800, Bryan Barcelo wrote:
At 04:32 PM 12/10/97 +0100, Sten Anderson wrote:
Jens B. Jorgensen [EMAIL PROTECTED] writes:
These messages do not indicate a fatal error, only that you haven't
installed these X extensions. If you're using your own .xinitrc,
Hamish Moffatt [EMAIL PROTECTED] writes:
The window manager should always be last too. Specifically, the last
command should not end in , but it's most useful if that's the window
manager. You could make it xclock or something, but then you'd
have to kill the clock somehow to logout.
Depends
Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ):
|Hamish Moffatt [EMAIL PROTECTED] writes:
|
| The window manager should always be last too. Specifically, the last
| command should not end in , but it's most useful if that's the window
| manager. You could make it xclock or
Alan Su [EMAIL PROTECTED] writes:
Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ):
|Hamish Moffatt [EMAIL PROTECTED] writes:
|
| The window manager should always be last too. Specifically, the last
| command should not end in , but it's most useful if that's the window
|
Alan Su [EMAIL PROTECTED] writes:
Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ):
|
|Depends - most window managers will send a message to all active X
|clients when they exit that causes them to shut down.
|
I don't think this is right...I've fiddled a lot with window
On Wed, Dec 10, 1997 at 08:00:30PM -0800, Alan Su wrote:
Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ):
|Hamish Moffatt [EMAIL PROTECTED] writes:
|
| The window manager should always be last too. Specifically, the last
| command should not end in , but it's most useful if
Hamish Moffatt wrote (Thu, 11 Dec 1997 18:36:55 +1100 ):
|On Wed, Dec 10, 1997 at 08:00:30PM -0800, Alan Su wrote:
| Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ):
| |Hamish Moffatt [EMAIL PROTECTED] writes:
| |
| | The window manager should always be last too. Specifically, the
Sten Anderson wrote (10 Dec 1997 16:32:12 +0100 ):
|Jens B. Jorgensen [EMAIL PROTECTED] writes:
|
| These messages do not indicate a fatal error, only that you haven't
| installed these X extensions. If you're using your own .xinitrc,
| are you sure that the last command uses 'exec' rather than
Alan Su [EMAIL PROTECTED] writes:
Is there something wrong with using exec on an xterm, rather than a
window manager? I'm currently doing that which makes the duration of
an x session depend on the xterm rather than the window manager (which
is what I prefer), and I haven't run into any
Alan Su wrote:
Sten Anderson wrote (10 Dec 1997 16:32:12 +0100 ):
|Jens B. Jorgensen [EMAIL PROTECTED] writes:
|
| These messages do not indicate a fatal error, only that you haven't
| installed these X extensions. If you're using your own .xinitrc,
| are you sure that the last command
Hi Paul,
Sorry to bother you again, but I found the file you said and checked it out
and it seemed okay. I also made changes to the .xinitrc file in my
subdirectory. It worked for fvwm2 but when I replaced fvwm2 with olvwm,
xwindows loads up to the light blue background and then shuts down
Bryan Barcelo wrote:
Hi Paul,
Sorry to bother you again, but I found the file you said and checked it out
and it seemed okay. I also made changes to the .xinitrc file in my
subdirectory. It worked for fvwm2 but when I replaced fvwm2 with olvwm,
xwindows loads up to the light blue
Jens B. Jorgensen [EMAIL PROTECTED] writes:
These messages do not indicate a fatal error, only that you haven't
installed these X extensions. If you're using your own .xinitrc,
are you sure that the last command uses 'exec' rather than just
running a program? This would cause the X server to
Sten Anderson wrote:
Jens B. Jorgensen [EMAIL PROTECTED] writes:
These messages do not indicate a fatal error, only that you haven't
installed these X extensions. If you're using your own .xinitrc,
are you sure that the last command uses 'exec' rather than just
running a program? This
Hi! I'm having problems running X Windows after installing it. There's no
default window manager after running 'startx' at the command prompt even
if I specified one during the installation, so I have to type whatever
window manager I want to use at the console after it starts up. Does
anyone
Hello Bryan,yes there is a file that has the windows manager information.
It also tells what order to start them in. But you can only have one
running at a time. Here is mine, it is in /etc/X11/windows-managers
# This file contains a list of available window managers. The default
# Xsession
On Sun, 16 Nov 1997, Andrew J Tarr wrote:
Cheerfully trying to edit a new file, I got into the help minibuffer to
find out an Xemacs command. I tried loading a file, and got an error
message. I moved to the *scratch* buffer, but that turned out to be the
help minibuffer also. I then kept
Cheerfully trying to edit a new file, I got into the help minibuffer to
find out an Xemacs command. I tried loading a file, and got an error
message. I moved to the *scratch* buffer, but that turned out to be the
help minibuffer also. I then kept deleting buffers until Xemacs died, with
a core
Well it seems that I cannot accomplish anything without help from the
readers of this list. I tried to install X Windows by telling dselect
to install xbase and the other files it said it needed to go with it,
but of course it didn't work.
I installed these packages:
xbase_3.3-3.deb
Well it seems that I cannot accomplish anything without help from the
readers of this list. I tried to install X Windows by telling dselect
to install xbase and the other files it said it needed to go with it,
but of course it didn't work.
I installed these packages:
xbase_3.3-3.deb
Hello,
I'm trying to get X running (I downloaded the files in x11 from
the Debian 1.3 binaries.) I get the following error when I try to start
X using startx or xinit.
Fatal server error
no screens found
I used XF86Setup to configure the system. Do I have to set up
a special
Hi,
I found the problem, its a bug in the script xf86config. It wrote some bad
lines in my XF86Config in the mouse pointer section.
But, before i found that, i uninstall X-windows and reinstall it.
The problem is with PEX and XIE extenions, they are not loaded. What can i
do?
Thanks
Dany
--
In article [EMAIL PROTECTED] you wrote:
(--) SVGA: There is no mode definition named 800x600
(--) SVGA: Removing mode 800x600 from list of valid modes.
... [XF86Config:]
Section Monitor
HorizSync 31.5 - 35.1
VertRefresh 50-70
Here is the problem; the HorizSync range is too small. The
Jens B. Jorgensen writes:
Gith wrote:
[snip]
[ XF86Config file deleted ]
Check to make sure that you have the right file. When I ran the
auto-XF86 config program I ended up with /etc/X11/XF86Config and
/usr/X11R6/lib/X11/XF86Config as separate files and I think that
Jens B. Jorgensen writes:
Gith wrote:
[snip]
(**) SVGA: chipset: clgd5434
(**) SVGA: videoram: 1024k
(--) SVGA: clocks: 25.23 28.32 41.16 36.08 31.50 39.99 45.08 49.87
(--) SVGA: clocks: 64.98 72.16 75.00 80.01
(**) SVGA: Option mmio
(--) SVGA: Maximum allowed
Gith wrote:
Ok, since I've just recently gotten a computer that can run X
I'm still a newbie on how it works.
I want to start up in 800x600x256 mode. SVGALIB has no problem
doing this. I can't figure out how to get X to do it. X keeps
starting in 640x480.
This is for a Cirrus Logic
Ok, since I've just recently gotten a computer that can run X
I'm still a newbie on how it works.
I want to start up in 800x600x256 mode. SVGALIB has no problem
doing this. I can't figure out how to get X to do it. X keeps
starting in 640x480.
This is for a Cirrus Logic CL-GD5434 with 1Meg
In article [EMAIL PROTECTED] Jim Worthington [EMAIL PROTECTED] writes:
I really prefer running openwin, so I created the directory
/usr/openwin and copied all the stuff from my Slackware system over
to there (bin, lib, etc.) I can get openwin to start, display the
As a Sun workstation
I really prefer running openwin, so I created the directory
/usr/openwin and copied all the stuff from my Slackware system over
to there (bin, lib, etc.) I can get openwin to start, display the
As a Sun workstation user, I also prefer running openwin. I was under the
impression that this
Linux openwin logo, but before the screen turns blue, the X-server
exits with the message
lwm: can't find library 'libolg.so.3'
[.. snap ..]
This is a shared library and for libraries to be found you have to run
ldconfig as root after moving or installing libraries.
Also make sure
I had no luck getting X to run on my first installation of Debian
1.1 from the Gold cd from I-connect.
So I completely re-loaded the distribution, taking extra care to
resolve the dependency conflicts.
When I got to the configure packages section, I noticed in the
error message
dpkg -
In article [EMAIL PROTECTED] [EMAIL PROTECTED] (Ken Gaugler) writes:
I really prefer running openwin, so I created the directory
/usr/openwin and copied all the stuff from my Slackware system over
to there (bin, lib, etc.)
FYI: I will upload a xview package including the openwin-like
I really prefer running openwin, so I created the directory
/usr/openwin and copied all the stuff from my Slackware system over
to there (bin, lib, etc.) I can get openwin to start, display the
As a Sun workstation user, I also prefer running openwin. I was under the
impression that this
So I went back and fixed that, and everything configured fine
except the X server setup. After fixing a problem with the
mouse in XF86Config, I got X up and running fairly well. I think it
is giving me fvwm as the default window manager, and the middle mouse
button doesn't work right ( the
101 - 154 of 154 matches
Mail list logo
