[SOLVED] Can't boot into Slackware 13.37 on my Dell XPS 15
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.
Distribution: Linux Mint 11 (Katya), Slackware 13.1, Slackware 13.37
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)
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.
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 02:12 PM.
Reason: correct a spelling typo. post content unchanged.
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.