This is slackware though... once it works... leave it... and enjoy you're free time by slacking off... ;)

kersten, i've always updated to current my machines and never had a problem (of course i excluded what is exclued by defautl, kernel, devs, etc and compiled by hand that). When i upgraded to latest X.org release i created a new xorg.conf with X -configure and all went good. Then only thing you need to check after update to current is to look for .new config files. You can use locate .new and it will drop (most of them) the configuration files that are new and you should check as by default it doesn't replace any of them, it creates one with .new extention.

After all, if you've just made a new install, try -current if you still get all messed up, reinstall again because you haven't configured too much, and stick with -10 :)

I had the same problem when I did a swaret --upgrade -a ... X wouldn't load, all kinds of errors... I did a "xorgconfig" after I logged into the command line - with no x loaded, I used "ctrl+F6" to get to a command line.

Rebuild your xorg.conf file this way and it'll start again... It took a reboot after this to get the alsa module re-loaded (for me, anyhow...).

After all the work I put into this distro, I wasn't about to give up easy and re-install.

Also, An idea for using Xorg 6.8.1 in the future, make a new config file (say, xorg.conf-6.8.1) with all your settings, in case you screw up when editing the orginal :P. i always keep a copy of my xorg.conf, lilo.conf and a few others on hand that i know works.

I have been using Slackware current for a while now and have not really noticed anything broken, because the packages are well tested before they are placed in current. I agree with the author of the post above always keep a backup of all your important configuration files.

You shouldn't just blindly update using swaret, allways look at the changelog before
you do an upgrade.

Bookmark this :

http://www.slackware.com/changelog/current.php?cpu=i386

Indeed. I use Swaret, but I have dependency check disabled and commented out all third-party repositories. Reading the changelog is also a must, for example, it warns you about the Keyboard -> kbd change in xorg.conf. Checking for *.new files in /etc is also important.

I've posted similar problems in this thread http://www.linuxquestions.org/questi...hreadid=232892

I still haven't been able to find the cause or the solution. I just know the problems started after the last update.

Thanks for all the info everybody. Obviously I didn't do enough research before I started my updating frenzy.:D I'm sure that I'll be able to update without any trouble next time--just based on what I've learned from this thread! You really can't beat the slack community.
Anyway, this is assuming I ever get it to boot....

edit: nevermind, it's all up and running again....now, I just have to decide if I really want to try my luck with swaret again...

I've been reading posts in FAR-TOO-MANY-PLACES! about problems others are having with X 6.8.1 and it appears that the majority have nothing the do with the keyboard-->kbd change; most of the problems are with screen issues. Now I'm not so sure it is X that is causing the problem. Last night I uninstalled 6.8.1 and reinstalled 6.7.0 and the problems that I've described earlier ( http://www.linuxquestions.org/quest...threadid=232892) still happen.

I've been using Slackware for almost a year now and this is the worst problem I've encountered. Is there anything else in the September 19th update that would cause problems with the way objects are drawn on the screen? Are there any logs I could read to find clues?

Kent

Well, not changing the Keyboard driver to kbd results in a No screens found error (but I don't think that's what you mean;) ). I have no problems with the new drivers in current (actually they even seem a bit faster to me). I'm not sure where your problems stem from... xorg logs are one place to look... i

I found similar discussions at other sites and by setting the device option "NoAccel" to true in xorg.conf, the problems are gone and everything seems to be back to normal.