LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 07-14-2005, 07:13 PM   #1
darkarcon2015
Member
 
Registered: Jun 2004
Location: Potsdam, NY
Distribution: Fedora Core 6
Posts: 201

Rep: Reputation: 30
Slackware Won't Boot


I just installed Slackware 10.1on my IBM T42 Thinkpad (2379DXU) and it will not boot. Intead, Windows XP boots. I did install LILO, but I installed it to the root partition, not the master boot record. Should I just install it there or can I access it somehow else? Thanks for any help.
 
Old 07-14-2005, 07:17 PM   #2
Linux~Powered
Member
 
Registered: Jan 2004
Location: /lost+found
Distribution: Slack`er-current
Posts: 845

Rep: Reputation: 31
You can boot up Slack with the cd and fix lilo with pkgtool.
 
Old 07-14-2005, 07:17 PM   #3
stefan_nicolau
Member
 
Registered: Jun 2005
Location: Canada
Distribution: Debian Etch/Sid, Ubuntu
Posts: 529

Rep: Reputation: 32
The simplest way to dual-boot is to install lilo or grub to the mbr.
There is also an alternate method for cain-loading lilo through ntloader, but I would not recommend it.
 
Old 07-15-2005, 02:20 AM   #4
falcon79
LQ Newbie
 
Registered: Jun 2004
Posts: 15

Rep: Reputation: 0
Simply, set the bootable flag for your linux partition. This way, you should get the lilo menu.
But maybe you should put lilo into your mbr
 
Old 07-15-2005, 03:48 AM   #5
Kahless
Member
 
Registered: Jul 2003
Location: Pennsylvainia
Distribution: Slackware / Debian / *Ubuntu / Opensuse / Solaris uname: Brian Cooney
Posts: 503

Rep: Reputation: 30
Ive beem putting it on the mbr for a long time, its not as scary as it sounds. if you mess up and give up on linux, you can restore your mbr with a windows boot floppy anyway.
 
Old 07-15-2005, 04:13 AM   #6
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 12,050

Rep: Reputation: 971Reputation: 971Reputation: 971Reputation: 971Reputation: 971Reputation: 971Reputation: 971Reputation: 971
Don't set the bootable flag on the linux partition if you still have the XP bootloader in the MBR.
It won't help get Linux going, and XP specifically checks for this and aborts the load.

Whilst you can load Linux from boot.ini, you *really* don't want to do this with lilo.
Serious PITA.
Grub is less of a pain, but you will be much better off with one of *nix loaders.
I prefer (and always use) grub, but Pat has mandated lilo.
 
Old 07-15-2005, 06:00 AM   #7
stefan_nicolau
Member
 
Registered: Jun 2005
Location: Canada
Distribution: Debian Etch/Sid, Ubuntu
Posts: 529

Rep: Reputation: 32
I used ntloader to chainload GRUB, before I realized the uselessness of this, and installed GRUB to the mbr.
To uninstall (and install the XP bootloader), in windows you can just run fdisk /mbr. (warning: this will make linux unbootable.
 
Old 07-15-2005, 07:45 AM   #8
erickFis
Member
 
Registered: Jun 2003
Location: Brasil
Distribution: Slackware 13.1_64 Gold Edition
Posts: 205

Rep: Reputation: 32
Here is what you need (what I used to use in my pc):

Create the following partitions on you disk (lets supose hda)

- hda1, with about 20 mb, where we will put the kernel images, for booting
- hda2, for the Win XP (do you really want this?), with the size you want
- hda3, for swap
- hda4, for /
- hda5, for your home.

Use #cfdisk to do this, and set the hda2 to be the bootable partition.

Then install you win on hda2, leaving the others partitions.
Now install your linux and, when installing, you must tell that the /boot folder will be mounted at hda1. (as well tell that /home will be at hda5, for more confort).

Then install and configure properly the LILO, editing /etc/lilo.conf and telling it to look for boot images for linux in /dev/hda.

You must tell LILO to be installed on superblock, by running #pkgtool

The windows will the setted automatically when you run the LILO setup tool (#pkgtool, when using slackware).

Good luck!

Last edited by erickFis; 07-15-2005 at 07:48 AM.
 
Old 07-15-2005, 08:23 AM   #9
glussier
Member
 
Registered: Jul 2005
Location: Montreal, Qc, Canada
Distribution: Fedora Core 5/6 Slackware 10.1/11
Posts: 120

Rep: Reputation: 15
Quote:
Originally posted by stefan_nicolau
The simplest way to dual-boot is to install lilo or grub to the mbr.
There is also an alternate method for cain-loading lilo through ntloader, but I would not recommend it.
And why so? I've been doing-it for years with lilo and never had a problem. No matter what you do you still end-up with 2 bootloaders, 1 for nt and it's own world and another one for linux.
 
Old 07-15-2005, 11:18 PM   #10
WH16
LQ Newbie
 
Registered: Jan 2004
Location: NC
Distribution: Slackware
Posts: 9

Rep: Reputation: 0
Wow, you guys went around the world to answer this one


SOLUTION 1:
All you have to do is re-install Lilo to root. Take a boot disk (or one of your Slackware CDs) and set the boot option in this fashion:

boot: root=/dev/hda2 (or whatever your root partition may be)

Then, as root, all you have to do is simply:

/sbin/lilo


You will see it adding your Windows and Linux partition as boot options. Afterwards, you will then need to remove the lilo boot from the root partition otherwise you will see Lilo twice when you first boot up

SOLUTION 2:
You can also set it to load from the NT Loader if you want like someone already suggested (and it's technically safer than installing Lilo in your /mbr), it's simple and easy (but you'll still probably want to remove that Lilo boot from your root ):

http://www.littlewhitedog.com/content-52.html

Easy way to do this without a floppy drive, just create the file somewhere on your Windows partition if you have it mounted in Linux and your root have read/write rights to it. If not, use Explore2fs in Windows.


Last edited by WH16; 07-15-2005 at 11:30 PM.
 
Old 07-17-2005, 02:43 AM   #11
stefan_nicolau
Member
 
Registered: Jun 2005
Location: Canada
Distribution: Debian Etch/Sid, Ubuntu
Posts: 529

Rep: Reputation: 32
Quote:
Originally posted by glussier
And why so? I've been doing-it for years with lilo and never had a problem. No matter what you do you still end-up with 2 bootloaders, 1 for nt and it's own world and another one for linux.
Because:
A) More trouble to configure, and you have to recreate the boot image each time you re-install lilo.
B) Your Linux boot is dependant on god-knows-what modifications Microsoft makes to ntloader.
 
Old 07-18-2005, 12:14 AM   #12
WH16
LQ Newbie
 
Registered: Jan 2004
Location: NC
Distribution: Slackware
Posts: 9

Rep: Reputation: 0
Quote:
Originally posted by stefan_nicolau
Because:
A) More trouble to configure, and you have to recreate the boot image each time you re-install lilo.
Is it really more trouble than doing certain things in Linux? lol

Quote:
Originally posted by stefan_nicolau
B) Your Linux boot is dependant on god-knows-what modifications Microsoft makes to ntloader.
Ah, so you are fearful of Microsoft's tactics. I'm sure when it will be unsafe to use the NT boot loader everyone will know, no need to scare some one off from using this technique for no reason but fear.

Last edited by WH16; 07-18-2005 at 12:16 AM.
 
Old 07-18-2005, 06:23 AM   #13
stefan_nicolau
Member
 
Registered: Jun 2005
Location: Canada
Distribution: Debian Etch/Sid, Ubuntu
Posts: 529

Rep: Reputation: 32
Quote:
Is it really more trouble than doing certain things in Linux? lol
Yes. Your system will become unbootable if you forget to take boot image when you install a new kernel (before rebooting), boot into windows, and install it. This is a lot more complicated than adding a few lines to a grub configuration file. Since most distributions now automatically install kernels and make all bootloader changes, you may forget all this, and end up with an unbootable system, again.
Quote:
no need to scare some one off from using this technique for no reason but fear.
I'm not trying to "scare some one off from using" a fabulously good technique, my point is that there are no advantrages to this technique, while there are plenty of disadvantages.
Quote:
I'm sure when it will be unsafe to use the NT boot loader everyone will know
What use will it be to know you can't boot anymore?
 
Old 07-18-2005, 09:20 AM   #14
darkarcon2015
Member
 
Registered: Jun 2004
Location: Potsdam, NY
Distribution: Fedora Core 6
Posts: 201

Original Poster
Rep: Reputation: 30
Err, I didn't mean for everyone to get so heated about this. I simply followed Linux~Powered's directions.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
About Slackware 9.1 boot disk?? ftp://ftp.kpn.be/pub/linux/slackware/slackware-9.1-is AL3OMDAH Slackware 4 04-18-2007 09:54 AM
Dual boot windows/slackware, but slackware installed first? Cryptic_K Slackware 3 11-20-2006 12:49 PM
Slackware boot and windows boot zonen Linux - Newbie 7 02-21-2005 03:57 PM
system alarm on boot in slackware 10.0 but not win2000(dual boot) Arch Stanton Slackware 3 01-24-2005 10:33 AM
Fresh Slackware 9.1 installation requires boot disk to boot smithtodda Slackware - Installation 7 06-23-2004 09:06 PM


All times are GMT -5. The time now is 12:37 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration