Debian "startx" problem.

Linux_N0oby · 02-03-2002, 07:54 PM

Ok, I'm on my 6th install on Debian. 4 out of the 6 times I had no problem installing a DM. Now after a fresh install, I can't even get 'startx' to work! The line that I think is stopping it is : Failed to initialize core devices. The only other errors are mouse problems. Does anyone know what to do in a situation like this?

alfie · 02-04-2002, 04:37 AM

Quote:

Originally posted by Linux_N0oby
The line that I think is stopping it is : Failed to initialize core devices. The only other errors are mouse problems.

It wouldn't be bad to check the whole output. Please keep in mind the following lines that are at the start of each startx output:

Code:

Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

So you check of course for (EE) lines, but also take a look at the (WW) and (!!) lines. They might offer additional infos, too.

What I usually do when debugging a broken startx:

Code:

startx 2>&1 | less

Then I can scroll back and track down the problem in all of the messages.

When it says it can't initialize the core devices the mouse might be one of those. Search for device in that output and look for errors or warnings there.

HTH,
Alfie

therion12 · 02-04-2002, 09:20 PM

Yeah i used to get that error, its like 90% it is the mouse and like 10% the keyboard.
Edit your XF86Config file and make sure you have the right mouse protocol setup. You will need to change this if you are using a optical mouse.

Linux_N0oby · 02-05-2002, 09:34 AM

Whatever it is, it's keeping me from starting a desktop manager. The current error it shows when I try "startx" is something about the video, and the "xinit". Would the mouse problem stop it from starting? I set the video the exact same way I did last time I got it to work.

therion12 · 02-05-2002, 06:33 PM

To see if its the mouse add this line to the XF86Config file:

"Option" "AllowMouseOpenFail"

If its an error in the xinit then that means you didn't specify a valid Desktop. These include but are not limited to KDE, GNOME, WM etc.

If you are using KDE the shortcut to add is:

exec startkde

in the ~/.xinitrc file..its a hidden file so to see it you need to "ls -a"

Linux_N0oby · 02-05-2002, 08:26 PM

Okay, here's the exact problem XF86 is having:

Config Error: /etc/X11/XF86Config : 48

SubSection "extmod"
^^^^^^^^^

Module section keyword expected
Giving Up.

I can't find anything that has to do with "extmod", nor do I know what it means. It is Line 48, and it seems to be what is causing my problem.

Also there isn't an XF86Setup file!?! Is there a package I'm missing?

therion12 · 02-05-2002, 09:39 PM

If you have the Core package then you should have one of a few different programs:

XF86Setup -- For old versions
xf86cfg -textmode -- for new versions
XFree86Config -- for old versions.

trickykid · 02-05-2002, 09:44 PM

Quote:

Originally posted by Linux_N0oby

Also there isn't an XF86Setup file!?! Is there a package I'm missing?

try using xf86config to configure X..

therion12 · 02-05-2002, 10:00 PM

Yeah try all those, it depends on alot of things but generally at least one of them work.

Linux_N0oby · 02-05-2002, 10:14 PM

I did use 'xf86config'. I had no problems with that. It just doesn't know what to do when it hits the: SubSection "extmod". Neither do I. :P Last install I had the XF86Setup file, but not this time. I don't know where the "extmod", file comes from, or if it even is a missing file. vI'm guessing whatever package has the XF86Setup file might have the soulution to my problem. I hope.

linuxcool · 02-06-2002, 12:31 AM

Try renaming the XF86Config file to XF86Config.old. Then run xf86config again and see if it will create a new XF86Config file for you that will work.

Linux_N0oby · 02-06-2002, 05:40 AM

Didn't work.

el_felipe · 02-06-2002, 06:58 PM

N0oby, many ways, two of them:

1) try "apt-get install xf86setup" (in sid) or if the package has a different name do an "apt-cache search XF86Setup" and then "apt-get install <package_name>"

This will have apt-get download and install packages + probably some dependecies (xserver-vga16...), then XF86Setup and follow the graphical setup.

or

2) "dpkg-reconfigure xserver-xfree86", or "xserver-whatever_xserver_you_have_installed", to see what x-server you have installed type "dpkg -l xserver*": those entries marked with "ii" are packages already installed.

Example:

felipe@entropic:~$ dpkg -l xserver*
[...]
pn xserver-mach32 <none> (no description available)
ii xserver-mach64 3.3.6-44 X server for ATI Mach64-based graphics cards
pn xserver-mach8 <none> (no description available)
pn xserver-mono <none> (no description available)
pn xserver-p9000 <none> (no description available)
pn xserver-s3 <none> (no description available)
pn xserver-s3v <none> (no description available)
ii xserver-svga 3.3.6-44 X server for SVGA graphics cards
[...]

Then I can dpkg-reconfigure xserver-svga or xserver-mach64

Hope this helps!

el_felipe
.
.

Linux_N0oby · 02-06-2002, 07:04 PM

Thank you! Well, I guess I'll see if it works. :P

Linux_N0oby · 02-06-2002, 10:33 PM

Okay, it showed that I only had it half installed. Also when I went to reinstall I noticed 2 xserver-comm files. One was 4.1.0, and the other was 3.3.x . Do I need both of these or is that what is causing my conflict? Well, I guess I will find out. Just for future reference, what is the best way to uninstall packages without really screwing anything up?