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.
I saw that it's already in the current.
I have some problems with XFree86 that hangs whenever I logout, or reboot without a shutdown. I believe that I need to reinstall the X server, but I would rather switch to Xorg at the same time.
So here are some questions about the installation:
- what will happen with my XF86config? I had many troubles before managed to make it right
- Did anyone try the slackware packages? are there any problems with dependencies e.t.c?
- In general, is it a good idea to upgrade my Xfree?
Are you using framebuffer support? I had the same problem and I already had xorg installed. I solved the problem by using the generic driver (VESA) for the framebuffer.
As for XF86Config, you can back it up, install xorg and use XF86Config as is but renamed to xorg.conf. In my opinion, switching to xorg is a good idea because xorg is like xfree but with one year of bug corrections. They just picked up xfree code and debugged it. At least that's the idea I have about it...
EDIT:
You may also need to change FontPath in XF86Config to the new font paths.
I removed all Xfree packages and then installed the Xorg (all packages).
All was done with removepkg and later installpkg.
Somehow, I had no problems at all (never happened to me before), quite the contrary, without changing anything I was able to logout of Kde, X, and restart my pc while the X worked as well as I could only wish. I think it's even faster than it was with XFree86.
I entered the /etc/X11 folder and noticed that nothing changed, the XF86config stayed where it was, unaltered.
Ok, so now all works fine, but still I want to have control of what's going on there (that's the reason we use slackware right?). I tried to execute xorgcfg (the graphical one?) out of the kconsole in my KDE (as root), but it shutdown in a moment printing a message that says no config file was found.
I believe not many had alredy switched to Xorg with slackware so it's hard to google the answer.
Does anyone know how to configure Xorg, where to find the config file, and if it's needed to rename my XF86cofig though it works fine like it is now.
Originally posted by Covel You must have a file xorg.conf if you're using xorg. Maybe it's a default xorg.conf file or a copy of XF86Config. Check it out in /etc/X11
Not so.
What it does have is a series of checks, much like XFree86. It'll look first for xorg.conf, and if it doesn't find that file, it'll search for another file. I'm not sure if it's XF86Config-4 or XF86Config, but if you have one of those files, then it'll use that as its backup. What I would do then is just copy the file and rename it as xorg.conf, just so you can tweak that, and if you do something wrong, you can use the other file, or overwrite the xorg.conf with the old XF86Config file.
What it does have is a series of checks, much like XFree86. It'll look first for xorg.conf, and if it doesn't find that file, it'll search for another file. I'm not sure if it's XF86Config-4 or XF86Config, but if you have one of those files, then it'll use that as its backup. What I would do then is just copy the file and rename it as xorg.conf, just so you can tweak that, and if you do something wrong, you can use the other file, or overwrite the xorg.conf with the old XF86Config file.
You're right. I just renamed my xorg.conf file to XF86Config and it worked
I heard that it is more difficult for nvidia users because they have to install the last driver (5336) which does not work well with Enemy Territory. Do you agree with that ? Because I am not sure.
I've installed X11 just now and it is working fine for me, I did have to reinstall the nVidia 5336 driver as GLX couldn't be initialised. I have noticed that after I exit from X11 that I get this error message:
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
Originally posted by BinaryLinux I've installed X11 just now and it is working fine for me, I did have to reinstall the nVidia 5336 driver as GLX couldn't be initialised. I have noticed that after I exit from X11 that I get this error message:
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
Doe's anyone know what I can do to fix this?
You could comment out that path from the /etc/X11/xorg.conf file. Then it won't look for that font there. It might do that automatically if you end up logging in as root and go into X from runlevel 3, but it would just be easier to comment it out by hand.
Originally posted by r_jensen11 You could comment out that path from the /etc/X11/xorg.conf file. Then it won't look for that font there. It might do that automatically if you end up logging in as root and go into X from runlevel 3, but it would just be easier to comment it out by hand.
Thanks for the information, I no longer get that message now after doing what you said.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.