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

Re: Improperly Configured Screen ?



SPELYA wrote:

Kent,

As recommanded I added "exit 0" at the beginning of the gdm file using the
command "nano gdm" from root, and it did work.  Now I can boot not using the
recover option, and I get a prompt line ending with $ (user environment, I
guess) instead of a prompt line with # (root environment).  I can enter a
regular user ID and password.  What do I do from here?

Maybe some additionnal information could help.  Another Debian-er had
suggested that I browse the log using the command
      less  /var/log/Xorg.0.log
Her are some general information and the warning or error messages I found
(I will try no to make too many typo error):
------------------------------
General info:
X windows System Version 6.9.0 release 21 dec 2005
X Protocol Version 11, rev 0, rel. 6.9

Build OS : Linux 2.6.15-1-686  i686[ELF]
Current OS:  Linxu MyPC 2.4.27-2-686 #1
OS Kernel: Linux Version 2.4.27-2-686

------------------------
Warning and error messages:
--       ATI (0): 8192 kb of SDRAM (1:1) detected (using 8191 kb)
WW  ATI (0): Cannot shadow an accelerated frame buffer

II       Module i2C:  Vendor = "X.org Foundation" compiled 6.9.0 ..........
WW  ATI (0): i2C bus Mach64 initialisation failure
II       ATI (0):  i2C bus "Mach64" removed

**      Configured mouse;  Core Pointer
**      Option "Device"  "/dev/input/mice"
EE     xf860OpenSerial :  Cannot open  "/dev/input/mice"
EE     PreInit failed for input device "Configured mouse"
II       Unloaded Module : "mouse"
WW  No core pointer registered
II       XINPUT :  Adding extended input device "Generic Keyboard" (type:
KEYBOARD)

No core pointer
Fatal Server error: failed to initalize cor devices

Ah; there's a problem. X can't find your mouse.

X believes you have a mouse on /dev/input/mice, but apparently you do
not. Do you have a ps/2 mouse, a serial mouse, or a USB mouse (or
something entirely different)?

If USB, /dev/input/mice should work; if serial or ps/2, I'm not
surprised it doesn't work. In that case, reconfigure X with
"dpkg-reconfigure xserver-xorg" and specify /dev/psaux as the location
of your ps/2 mouse, or /dev/ttyS[0-3] for your serial mouse (probably).

Then try starting X manually with "startx &". Does the system work? (If
not, you might can semi-gracefully shutdown X with Ctrl-Alt-Backspace;
or you might can get back to VT1 with Ctrl-Alt-F1, at which point you
can kill X with some other magic commands we'll go into if need be.)

Also, at the console prompt (non-X), you can get a feel for your mouse
working on /dev/input/mice by entering "cat /dev/input/mice" and moving
your mouse around; if your mouse is working, you should see a bunch of
garbage appear on your screen. Ctrl-C will stop this process (and you
might need to blindly enter "reset" if your display now produces garbage
in response to your typing).

BTW, I'm [again] putting this back on-list; it's considered improper on
this list to take threads off-list unless they veer off-topic. By
keeping the discussion on-list, everything gets archived so that the
issue becomes part of the documentation for Debian, and others who might
have better input can add their two cents.
--
Kent



Reply to: