SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hope somebody can help me.
I installed slackware current because itīs RC2 and i want to try KDE4,
but after upgrading i canīt start X, the system freezes in the splash
screen of KDE and nothing but the mouse respond, so i have to make a
I knew about the problems with the new Intel Driver and the new
version of X server that slack current ships but i thought tha because
it was RC2 things had got better.
Anyway i have tried all the versions of the intel driver slackware
current ships but still no joy. Both with an xorg.conf or without it
as indicated on the CHANGES_AND_HINTS file.
Anyone knows how to correct this?? can i use the driver shipped with
slack 12.2?? I really donīt want to go back to 12.2 now that i am on
My card it's an Intel 82865G, and i have to use the VESA driver in
order to start x.
Due to the upgrade of kde from 3.5.10 to 4.2.4, you will need to move your
existing $HOME/.kde/ out of the way (either completely remove it or back
it up somewhere else if you think you might need it again for whatever
reason); otherwise, you will almost surely experience odd configuration
problems with kde applications.
Sorry for responding late but i had to go out...
I have followd the steps indicated in CHANGES_AND_HINTS but still no luck:
Here are the logs for X with and without an xorg.conf. hope somebody can help me because i am totally lost by now.
Thanks in advance.
first I'd like to say is, that i really don't know what's exactly wrong here, but i have maybe a similar problem. I currently believe, that hal could be the problem.
Please publish your /var/log/kdm.log
While/after the Server crashed, press alt+print+r and then alt+print+e. What happens then?
Try to boot into runlevel 3, login as root and execute init 4. Does this work?
I started in telinit 3 and executed init 4, kdm starts ok but accepts no input. i did alt+print+r and alt+print+e and kdm restarts but still accept no inputs.
I attached kdm.log and xorg log
Hope you find something useful.
The only thing i noticed is that when a do telinit 4 hal tries to load i810 driver, and when i try to startx hal tries to load intel driver..
and check what happens. Is the startup normal? (In my case, this lead to a normal startup, but keys where remapped. Down key had function of return key and such crazy stuff.)
If it starts up normal, and you have such a problem like me with the key-bindings. You could try to set the Options back to true and copy a modified version of /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi to /etc/hal/fdi/policy/10-keymap.fdi.
I am really not sure, if it helps you, but it worked in my case. If it won't help, I have no idea, what is wrong.
Edit: Of course you need to restart hal, if you copy the keymap.fdi file. Another way to check, if the keyboard is the problem, is disconnecting it, until X is fully startet and then attach it.
Good luck and cu
Last edited by bonaire; 08-18-2009 at 01:57 PM.
Reason: Added Edit ;)
"I hate to say this, but it appears as if the 82865 chipsets are simply not going to work with 13.0 :/ There's nothing we can do about it either, it seems -- there have been numerous reports of it not working, and I can't find any indication of anything we're doing wrong. If someone has the inclination the bring it up on the xorg mailing list, feel free - I'm subscribed there, so I'll participate as needed.
Robby Workman http://slackware.com/~rworkman/ http://rlworkman.net http://slackbuilds.org
I tried them all but still no luck. In fact i already had the 3 options set to false in xorg.conf.
With the 184.108.40.2061 kde loads but after it loads the desktop it freezes.
Starting in telinit 3 and then telinit 4, kdm starts but accepts no inputs.
I will continue to play with xorg.conf to see if i can make it work...
Have you had some succes???