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.
Wow! This morning was a ride. I went o bed while this massive update was being done. Got up this morning and rebooted. Good thing I have another Slackware install to fall back on whilst I research problems.
Thanks to all of you that posted - both the problems and solutions. I was up and running in seconds.
not sure if it applies, but remember also to remove the obsoleted xf86-video-radeonhd, as Robby suggests in the link above.
Unfo, disabling the compositing helped me just to start X with vesa driver.
Didn't know xf86-video-radeonhd is obsolete, the ChangeLog doesn't say anything.
Anyway, thanks for the ideas but neither of the above helped me.
x blew up on me. I rebooted into init3, ran startx, and it tells me taht the server has a video driver abi version that this driver does not officially support. Then I get a fatal error, no screens found. I tried reinstalling the Nvidia drivers from Slackbuilds.org... no good. Help!
Are you running at least a 2.6.35 kernel? I know I don't upgrade kernels real often, and when I first used Robby's new xorg packages I had to first update the kernel. The nvidia driver I am using is 256.52. I just run the script, not the slackbuild version.
Yes, I'm running the .35 kernel. But I can't get a graphical login screen with the nv drivers, either. I ran rmmod to ditch the nvidia module, changed xorg to the nv drivers, and I got a little white box at the top of my screen with the following:
kstartupconfig4 does not exist or fails. The error code is 127. Check your installation.
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Looks like we have the same card and the same problem.
I disabled compositing, but it didn't make a bit of difference.
Up until last night, I have always downloaded the 'current' files to my hard drive and installed them from there. Last night I used slackpkg to do the upgrade so my 'current' files, prior to last night, were untouched.
So, I used upgradepkg to re-install the 'x' files from my 'current' 'x' directory and at least now I can use Xfce. I haven't tried KDE, yet.
I'll wait a few more days before trying to install last nights upgrades, again.
Last edited by cwizardone; 11-15-2010 at 10:20 AM.
Did a bit more google searching, was I supposed to allow it to upgrade aaa_elflibs? I'd just do it, but my google searching also suggested that it might be a bad idea to upgrade that package after upgrading the other ones. Someone please advise...