[SOLVED] Can't boot into Slackware 13.37 on my Dell XPS 15
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.
Distribution: Linux Mint 11 (Katya), Slackware 13.1, Slackware 13.37
Posts: 30
Rep:
Can't boot into Slackware 13.37 on my Dell XPS 15
When I installed Slackware 13.37 for the first time, there was no problem. Everything worked very well - as expected from this great distro.
But, the LILO won't detect Windows installation correctly. So I tried to edit it using liliconfig, where I wrongly entered the entry for Linux. So without further messing around with the system, I went for reinstalling the whole system.
Now when I chose 'Linux' in LILO menu, Some initial startup scripts ran correctly - like detecting and mounting the root and non-root file systems.
But then the suddenly screen went black. It happened so fast, then and again, that I couldn't take a look at what's wrong.
My best guess is that there's a problem with video driver. (The laptop has nVidia GeForce graphics card)
Sounds like KMS is kicking in and has issues with your video card or monitor. If you pass 'nomodeset' to the kernel, does the machine continue to come up?
Yes, it does have Optimus technology. I don't want to disable it however. Isn't there any other way around? Because as I mentioned, everything worked smoothly for the first time.
I read the thread you posted. The problem is that those steps are to be done in terminal and need Internet connection. I am not reaching the login stage while booting, and even if I do, I won't be able to connect to Internet as I have USB modem that has to be configured later on using an installation script.
Distribution: Linux Mint 11 (Katya), Slackware 13.1, Slackware 13.37
Posts: 30
Original Poster
Rep:
Quote:
Originally Posted by adamk75
Sounds like KMS is kicking in and has issues with your video card or monitor. If you pass 'nomodeset' to the kernel, does the machine continue to come up?
Do I have to do it while installing - at the point where the set-up asks whether you want to pass extra parameters while booting?
Do I have to do it while installing - at the point where the set-up asks whether you want to pass extra parameters while booting?
You can add nomodeset to the append line in /etc/lilo.conf. Then rerun lilo. You should be able to boot from the Slackware install DVD to do this if you can not boot the instaled system.
To use nomodeset during boot, I believe you press TAB when you see the lilo screen (there is a message on the screen actually), type in (or leave in, if it is already there) the name of the boot option you want (normally called Linux, unless you changed it in lilo.conf), type a space, then the word nomodeset. This is equivalent to going in lilo.conf and adding nomodeset to the append parameter - but as you can't even boot, you can pass nomodeset during boot.
It looks like I have the same problem, with an Intel integrated video chip, and at the moment I've switched to using nomodeset and the vesa Xorg driver - until I get to try a newer kernel. Here is the thread:
To use nomodeset during boot, I believe you press TAB when you see the lilo screen ...
Thanks for postting that. I could not exactly remember how to pass options to lilo 'on the fly' like that using the TAB key.
Although I have been using Slackware for several years, I have been booting Slckware from Ubuntu's grub. So I have very little experience with lilo.
Last edited by tommcd; 05-30-2011 at 01:12 PM.
Reason: correct a spelling typo. post content unchanged.
KDE is likely crashing because it is trying to enable compositing. Does xfce4 work? If so, start up xfce4, launch KDE's systemsettings, and then disable compositing in KDE (under desktop effects).
Well - if you get all the way to KDE - then 'nomodeset' actually works. Otherwise you wouldn't see anything on the screen after about the 12th second (on a slowish, Intel U2500, 1.2GHz machine) of the boot process.
On the other hand, I use Fluxbox, so not sure if there is a further problem with KDE.
Then again, maybe your problem is different then mine, as, without 'nomodeset' - my screen would go black before getting to mounting root volume.
Initial screen provides a sample of booting a kernel, then you can add parameters at the end of that input line to pass parameter(s) to the kernel. This way you do not need to modify the '/etc/lilo.conf' in order to pass parameters. If you decide later that parameters are necessary then place parameters in '/etc/lilo.conf' and then run 'lilo' to update your bootloader.
Distribution: Linux Mint 11 (Katya), Slackware 13.1, Slackware 13.37
Posts: 30
Original Poster
Rep:
Quote:
Originally Posted by adamk75
KDE is likely crashing because it is trying to enable compositing. Does xfce4 work? If so, start up xfce4, launch KDE's systemsettings, and then disable compositing in KDE (under desktop effects).
Adam
Thanks. That exactly was the problem. XFCE works fine. Guess I will use it as default
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.