SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So I have been using slax for quite sometime, but alas have been on an outdated kernel. I tried to just clean install 12.0 w/ the 2.6.21 kernel I believe. Everything is ok for the most part, but I can't startx. Upon execution of startx I get
(==) LOG File:/var/log/Xorg.0.log
(==) Using config file "/etc/X11/Xorg.conf"
II Module already built in
II Module already built in
(EE)VIA (0) No valid modes found
(EE) Screen(s) found but none have usable configuration
Fatal Server error:
no screens found
giving up
xinit: connection reset by peer (errorno 104)
unable to connect to X server
xinit: No such process (errorno 3): server error
Sorry I had to type that in manually because my nix is on a seperate partition. I get the same error with the backtrack live cd btw. I have an averatec laptop that is kinda old, but always worked fine with slack 10. For the record I installed Suse 10.3 and it had no problems. Maybe I will try to update everything but the x pkgs.
ok this is stupid replying to myself, but perhaps if someone has the same problem this will help.
First I tried editing the /etc/X11/xorg.conf file to no avail. I then wanted to see what exactly startx was calling and having problems with. I just wanted to get a different error message than the above. I did
mv xorg.conf xorg.conf.old
cp xorg.conf-vesa xorg.conf
I then got some different error which I don't recall but the key was it was different. Next I did the same w/ the xorg.conf-fbdev and startx ran fine except for taking a couple of seconds longer than would have liked, but now I can edit it down.
Other possible xorg.conf setup tools are `xorgconfig` (my favourite) and `xorgsetup`. You need significant knowledge of your hardware if you use `xorgconfig`, but it should almost never fail if you provide the correct information. `xorgsetup`, on the other hand, requires no knowledge of the hardware, but may produce an unusable xorg.conf sometimes (it tries to guess the correct values depending on the hardware it detects).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.