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

Re: more problems with X

Brandt Dusthimer wrote:

For the upper 25% of the screen:  You have some type of Virtual Windows
setup.  You can get rid of it if you edit the XF86Config.
For the number pad: do you have Num Lock on?
For the Xstart up: if your configuration allows it, you can press
Ctrl-Alt-Bksp to dump yourself into bash or whatever you use.  If that boots
you back into X, I think there's a shell option like 'killx' or something
like that (???).  Otherwise, you can go into the shell (while in X) and do
an 'xf86config' if you want.  Then all you have to do is either restart X or

    Brandt Dusthimer

Greetings !

After help from a lot of folks on this list, I have a good news-bad news
situation. The good news is that x is now running.

The bad news:

(1) when x fires up, I only have what appears to be the upper left 25 %
of the screen;

What Brant says is likely the case. However, the problem may also be an incorrect video setup. How did you originally set up X? Did you do it by hand? By answering questions during a Debian install/dselect/apt session? Did you do it by running XF86Setup or xf86config? If you ran XF86Setup, and trying it several times doesn't give you any success, try running xf86config instead. And vice-versa.

(2) I have a Microsoft Natural keyboard, and the number pad on the far
right of the keyboard does not work;

It sounds like you don't have the correct keyboard setting in your /etc/XF86Config file. Not using the MS Natural Kbd, I don't know what's needed to fix it.

(3) linux automatically starts the xserver, and I can't get to a console
to check out my xf86config file to see what the is the problem.

There are several ways. Since X is starting automatically, this strongly points to the installation of wdm or xdm or kdm or gdm. Look in /etc/rc2.d, near the end of the file list, for a file named something like S99gdm or S90wdm. It is this file that is starting X when you boot up Linux. You could also do a "ps ax|more" or "ps ax|grep dm" to see if you see any ?dm-type service running.

You could kill that service, with something like "kill -9 145" (assuming 145 is the PID of the service; it's the number in the leftmost column when you do a "ps ax" that you want); however, that's kindda messy. Instead, run that file in /etc/rc2.d with the "stop" argument. For example "/etc/rc2.d/S99xdm stop". You'll want to make sure you don't have any unsaved work in X, because I believe this will kill X rather ungracefully. What I would recommend is to get out of the logged in X session to the login prompt, and then do a Ctrl-Alt-F[1 or 2], log in as root, and run the "S99xdm stop" command there. Now you can tinker around X-less to your heart's content.

To restart X, you can either manually say "startx" (it'll start logged in as whoever you're logged in as at the text terminal), or you can restart [x|g|w|k|etc]dm with "/etc/rc2.d/S99xdm start" and get back to the graphical login screen (don't forget you're still logged in as root on VT[whatever] though, so you might want to Ctrl-Alt-F[whatever] back and log out, then Alt-F[7 probably] back into X).

You could also delete the [x|whatever]dm program with dselect or with "apt-get purge [whatever]dm", but that's a more permanent solution.

You could also rename the S99[whatever] file to something like ~S99.. or NOS99.. or KS99.., etc, which won't stop the current running instance, but will prevent it from starting on the next system startup.

I will be most appreciative of any guidance. Please point me to a HOW-TO
or something that can give me some guidance.


Bob Edwards
Fayetteville, Arkansas


Reply to: