[SOLVED] Slackware current freezes at splash screen
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 have been using slackware since version 10.1 and really like it. I have never had a problem until lately, version 13.1 has been stable as a rock for me. The first 2 or 3 updates to current ran well but then the problem started. After installation Slackware would get to the splash screen and bring up the first picture of a disk drive then just hang and never go any further. I do have a good burn on the dvd, have checked the md5 and burned at 4x. then slack 13.37 does the same thing. this is on 4 different computers with several different video boards. I do believe the problem is mine so any help will be apreciated. I have googled and read most every post on the forum over the past few months and just have not been able to find a cure.
Have you tried to boot from the dvd disk and boot/load the huge kernel from the dvd disk?
Somewhere thereabouts there's (or used to be) an "In a pinch" message. The message tells how and shows what command (so as to get loaded the huge kernel from the dvd).
Accomplishing these actions merely allows to run a kernel that we did not have this precise kernel because it's on the dvd, not on our hard drive (even though a copy of it may be on our hard drive).
Such procedure has helped me with troubleshooting many times and each time I found it to be harmless.
--
Sometimes, as root, need to check/edit /etc/lilo.conf then run /sbin/lilo then reboot. (which sometimes can fix a bootup problem)
After installation Slackware would get to the splash screen and bring up the first picture of a disk drive then just hang and never go any further.
Do you mean by this that you are booting in run level 4 to the kdm login manager, login and then when KDE is starting the hang occurs?
If so, then this comment from the ChangeLog may be appropriate.
Quote:
Sun Nov 14 23:58:42 UTC 2010
...
If X crashes at start, try disabling compositing. Create a file named
/etc/X11/xorg.conf.d/disable-composite.conf with this in it:
Section "Extensions"
Option "Composite" "Disable"
EndSection
The change log implies the problem occurs only with Nvidia 6150SE chip sets. I have an nVidia Corporation C51PV (GeForce 6150) chip set on my motherboard. So perhaps the change log should refer to 6150 generically.
However, my tests were in a VirtualBox machine (VM). I just now started my Current VM and lspci does not report anything regarding the host machine chip set. lspci only reports VirtualBox hardware, although indirectly there still might be a connection to 6150 chip sets.
Regardless, the solution referenced by allend worked for me too in my VM.
I haven't yet tried testing on actual hardware. Possibly on actual hardware, after modifying xorg.conf and starting KDE, that disabling compositing in the KDE System Settings might allow removing the xorg.conf restriction. The trick is getting to do that. In my VM, all of the KDE Desktop Effects section is ghosted out because of disabling compositing directly in X.
If the posted solution fixes the hang, then you likely have a problem with hardware support for some KDE desktop effects. It may be possible to disable the problematic effects but enable others.
This post may be of use. http://www.linuxquestions.org/questi...2/#post4248844
The Option "Composite" "Disable" solved my bootup problem, now my text on the classic menu is dark as it should be part time and so light at other times that you can not even read it. Another problem is desktop effects can not be enabled. Those are 2 problems that I will work on later. Thanks for the help sure appreciate it
Another problem is desktop effects can not be enabled. Those are 2 problems that I will work on later. Thanks for the help sure appreciate it
Yeah, I suspected that might happen.
Possibly somebody who does not have this problem can start KDE, in System Settings disable compositing, look for what lines in the KDE config files immediately changed, and then post that in this thread. Then you could exit KDE, manually add that line to the appropriate config file (or use the kwriteconfig command), and remove the xorg restriction for compositing. I'm guessing/hoping then that you would see the desktop effects section become available in System Settings.
I went ahead and did an update-all and that seems to have cleared up video problems, the only problem now is desktop effects will not let me target it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.