David Moore wrote:
As a complete novice to Linux, please bear with me if my explanation of the
problem is confused.

I installed Debian 3.0 r2 woody kernel 2.2.20 (many times on 2 different
machines) using defaults and keeping as simple as possible, but I have not
been able to get XWindows running.

I used taskel to select: XWindows, Desktop environment and C/C++

It boots into the bash shell fine except that during boot-up a message
appears: "Modprobe can't locate char-major-10-135"  (the pause key doesn't
halt the screen during boot-up so other important message might flash past
before I can write them down)


You can stop messages on a console with ctrl-s and start them again with ctrl-q. But that applies only if the init process has already started, not the kernel booting. Those are found on var/log/syslog or /var/log/messages.

Those char-xxx-xx-xxx things are documented in the kernel source but for the world of me I don't remember where. Anybody?



I have a Matrox MGA G200 - 16Mb Phillips SL200 19" monitor MS 2 button mouse on PS2 port

The problem is, when I try to run X, XFree386, xdm, kdm or gdm it does not
go to VGA mode but spews forth dialogue including the following lines which
seem significant:

"  Warning couldn't open module mga_hal
"  MGA: Failed to load module mga_hal (Module does not exist, 0)

" EE Screen(s) found, but none have a usable configuration.

" Fatal Server error no screens found

if I run xf86cfg, it goes to VGA mode and brings up the XWindows
configuration modules, but the mouse doesn't work.

I run xf86config and re-enter the hardware specs (to the best of my
ability), but this makes no difference.

I am basic level user with unix (some years ago), and without gui feel like
I have been thrown in the deep-end in a tied sack. If I had XWindows I could
probably start swimming.


You'll be swimming in notime.



David
--------------------------------------
David Moore
[EMAIL PROTECTED]





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Reply via email to