LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 12-27-2004, 06:25 PM   #1
kleer
LQ Newbie
 
Registered: Dec 2004
Location: wisconsin, us
Distribution: Slackware Linux 10.0
Posts: 21

Rep: Reputation: 15
hopeless... dualboot slackware + windows xp


ok not sure what im doing wrong or if LILO just wont work on my system but ill try to cover everything i have done thus far...

I am currently running Winblows XP Home NTFS and that is booting fine... so far

ok i partitioned my 40gig drive using BOOTITNG to resize my NTFS, worked very well and i was left with: /dev/hda1 = NTFS :: /dev/hda2 = linux swap :: /dev/hda3 = linux root

i used slackware cd to format my swap partition then format my linux root partition... i then installed all packages on my root partition

i then followed the steps in Slack Essentials to dual boot using LILO... I first used: # dd if=/dev/hda3 of=/tmp/bootsect.lnx bs=1 count=512 then threw bootsect.lnx on a floppy and put it on C:\

then i added a menu option to boot.ini using cmd prompt:
C:\attrib -r -a -s -h boot.ini
C:\edit boot.ini
added C:\bootsect.lnx="Slackware Linux" to the last line of boot.ini

My problem is i cannot install LILO to the superblock of Linux...
i run: lilconfig and select simple install and use Standard Linux Console
and then goto the screen: "Installing Linux Loader..." and there is a command line at the bottom of the screen root@slackware:#

the screen stays like that forever, LILO doesnt appear to complete installing....

I also tried Expert LILO Install... Start LILO with new Header... then added /dev/hda3 Linux Partition to the config file (as to make it bootable?)
the same result: "Installing Linux Loader..." and there is a command line at the bottom of the screen root@slackware:#

I reboot and at the OS menu option i pick Slackware Linux and the screen is black with a flickering thingy at the top left but linux doesnt load.... when i select Windows on the option windows loads fine, no damage yet....

does this mean LILO doesnt work with my system? if so how do i un-do what i have done with LILO and possibly use LOADLIN to dual boot slack with xp? i read a bit on GRUB and it seems a little too complicated for me... is there a safe way of writing LILO the the MBR in order to dual boot?

i'm open to suggestions i'm getting frustrated
thanks in advance
 
Old 12-27-2004, 08:46 PM   #2
comprookie2000
Gentoo Developer
 
Registered: Feb 2004
Location: Fort Lauderdale FL.
Distribution: Gentoo
Posts: 3,291
Blog Entries: 5

Rep: Reputation: 54
I allways used this guide and never hade a problem;
http://www.bitbenderforums.com/vb22/...?postid=311808
 
Old 12-27-2004, 09:52 PM   #3
kleer
LQ Newbie
 
Registered: Dec 2004
Location: wisconsin, us
Distribution: Slackware Linux 10.0
Posts: 21

Original Poster
Rep: Reputation: 15
great step-by-step walkthrough but it doesnt cover dual booting
thanks thou
guess im stuck booting with floppy
 
Old 12-27-2004, 10:15 PM   #4
jmike1
LQ Newbie
 
Registered: Dec 2004
Posts: 13

Rep: Reputation: 0
Have you considered using a product like Partition Magic/ Boot Magic that is designed to make dual-boot systems work? I'm in the process of doing just that. Will let you know if I have better results.

Mike
 
Old 12-27-2004, 10:30 PM   #5
whipermr5
Member
 
Registered: Dec 2004
Location: Singapore
Distribution: Fedora Core 5 Linux
Posts: 202

Rep: Reputation: 30
This looks too much like your thread in slackware > installation > ntfsresize. I'll answer there.
 
Old 12-28-2004, 12:48 AM   #6
DaHammer
Member
 
Registered: Oct 2003
Location: Planet Earth
Distribution: Slackware, LFS
Posts: 561

Rep: Reputation: 30
Post your lilo.conf file. Here's an example in a setup such as yours where you're installing lilo to the superblock. And it should get you going if you are using the default slackware kernel.
Code:
# LILO configuration file
#
#
# Where to install lilo too
#   For installing lilo to superblock, you MUST specify which parition you
#   want to install too, like /dev/hda3 NOT /dev/hda
#   /dev/hda   ---- MBR
#   /dev/hdaX  ---- Superblock (Where X = partition where lilo is to be installed)
boot="/dev/hda3"

# Present lilo boot prompt to user
prompt

# Continue booting default after x (miliseconds?)
timeout="50"


# VESA framebuffer console @ 1024x768x256
vga="773"


# Default kernel to boot
image = "/boot/vmlinuz"
  root = "/dev/hda3"
  label = "Slackware"
  read-only
  
  # If using a 2.4.x kernel, you'll need this for CDR/CDRWs to work
  #   Assumes your CDR/W is at /dev/hdc
  append="hdc=ide-scsi"

# Linux bootable partition config ends
First, boot up the CD/Rescue Floppy so that you can edit your lilo.conf. Use the one above, paying particular attention to the "boot=/dev/hda3". That's where lilo will be installed, in your case it will be installed to the superblock of hda3, which is where your linux parition according to your comments above.

Second, make sure you have the files vmlinuz & System.map in the /boot directory. Slackware sets these up as links.

Third, run the command "lilo".

Run this command:
Code:
dd if=/dev/hda3 of=/bootsect.lnx bs=1 count=512
Now you need to copy the bootsect.lnx file to your XP parition somehow. Probably easiest way is to mount a floppy and copy it there:
Code:
mkdir /mnt/floppy
mount /dev/fd0 /mnt/floppy
cp /bootsect.lnx /mnt/floppy
umount /dev/fd0
Reboot into wndows and place the file at C:/, and since you already edited the boot.ini file, you should be good to go. Just remember that you ALWAYS run lilo first, then create the bootsect.lnx file. Now reboot again. Good luck..

Last edited by DaHammer; 12-28-2004 at 12:52 AM.
 
Old 12-28-2004, 12:57 AM   #7
kleer
LQ Newbie
 
Registered: Dec 2004
Location: wisconsin, us
Distribution: Slackware Linux 10.0
Posts: 21

Original Poster
Rep: Reputation: 15
someone from other thread had me make it this:

boot=/dev/hda
install=/boot/boot.b
prompt
timeout=300
message=/boot/message
lba32
default=windows

image=/boot/vmlinuz
label=slackware
append="root=LABEL=/"
root=/dev/hda3

other=/dev/hda1
table=/dev/hda
label=windows

i have original version saved under /etc/lilo.conf.old
if u want me to post that one, can you step me through how to copy that possibly
thanks for the extended help
 
Old 12-28-2004, 01:26 AM   #8
DaHammer
Member
 
Registered: Oct 2003
Location: Planet Earth
Distribution: Slackware, LFS
Posts: 561

Rep: Reputation: 30
The one you have posted there is for installing lilo to the MBR, which is not what you are trying to do, going by what you posted above. If you install lilo to the MBR, then you will overwrite XP's manager which is/was in the MBR. Usually it will work either way, however the safest way that just about always works is to install it the Superblock, which is what the lilo.conf file I posted is for. Disadvantage is that it's more trouble to setup. Take your pick, try em both, whatever. Just keep in mind that if you try installing lilo with the lilo.conf you posted above, or if you have already ran lilo after using that file, then you may have already corrupted the MBR and may have to use the XP CD or a DOS bootdisk to fix the MBR.


As far as steps go, like I said above, boot to the Slackware CD or Rescue Floppy and edit the lilo.conf file. Then go from there. You can use the cat program to create /etc/lilo.conf if you're not comfortable with vi. Type in the following to use cat:
Code:
cat > /etc/lilo.conf << "EOF"
# LILO configuration file
#
#
# Where to install lilo too
#   For installing lilo to superblock, you MUST specify which parition you
#   want to install too, like /dev/hda3 NOT /dev/hda
#   /dev/hda   ---- MBR
#   /dev/hdaX  ---- Superblock (Where X = partition where lilo is to be installed)
boot="/dev/hda3"

# Present lilo boot prompt to user
prompt

# Continue booting default after x (miliseconds?)
timeout="50"


# VESA framebuffer console @ 1024x768x256
vga="773"


# Default kernel to boot
image = "/boot/vmlinuz"
  root = "/dev/hda3"
  label = "Slackware"
  read-only
  
  # If using a 2.4.x kernel, you'll need this for CDR/CDRWs to work
  #   Assumes your CDR/W is at /dev/hdc
  append="hdc=ide-scsi"

# Linux bootable partition config ends
EOF
 
Old 12-28-2004, 02:03 AM   #9
kleer
LQ Newbie
 
Registered: Dec 2004
Location: wisconsin, us
Distribution: Slackware Linux 10.0
Posts: 21

Original Poster
Rep: Reputation: 15
dont think LILO works on my system.... all i get is kernel panic... dont even wanna try putting it on MBR
 
Old 12-28-2004, 07:36 AM   #10
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 52
lilo will work great on your system.
i think the only thing you've done wrong is that you made a " bootsect.lnx " -file ( the "dd" command )
before lilo was installed.

if you just follow DaHammer's post ( #6) from the top down, you'll get it working.

egag
 
Old 12-28-2004, 02:52 PM   #11
kleer
LQ Newbie
 
Registered: Dec 2004
Location: wisconsin, us
Distribution: Slackware Linux 10.0
Posts: 21

Original Poster
Rep: Reputation: 15
my lilo.conf is exactly what #6... should i still be getting a LILO boot menu?...because i am... cuz i create one in boot.ini so i got thru LILO boot menu, if i choose Windows then i have the boot.ini menu... i did if from the begininng, exported the bootsect after altering lilo.conf
still kernel panic

by the way, whenever i tried to install liloconfig expert/simple it would just stop responding at the "Installing Linux Loader..." screen

isnt editing lilo.conf just tip-toeing around that major problem?

Last edited by kleer; 12-28-2004 at 02:56 PM.
 
Old 12-28-2004, 05:07 PM   #12
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 52
-------------
exported the bootsect after altering lilo.conf
still kernel panic
--------------

after changing lilo.conf, did you run " lilo "
if so, what messages did you get ?

egag
 
Old 12-28-2004, 05:17 PM   #13
DaHammer
Member
 
Registered: Oct 2003
Location: Planet Earth
Distribution: Slackware, LFS
Posts: 561

Rep: Reputation: 30
The order should be like this:

1) Turn on PC
2) Windows bootmanager appears, with slackware as an option
3) If you pick windows, windows boots (no lilo prompt)
4) If you pick slackware, lilo prompt appears
5) Pick your kernel at the lilo prompt or just hit enter to boot the default kernel
6) Slackware boots

If you are seeing the lilo prompt prior to the windows bootmanager, or no windows bootmanager at all, then you have messed up your MBR. Most likely when you tried to install lilo to it. If that's the case, then you can either fix it with a DOS disk using fdisk, XP CD using the repair terminal, or try to get lilo working from the MBR so that it boots Windows and Slackware.

The dd command should always be ran AFTER any edits to lilo.conf & AFTER running lilo itself. And ONLY when installing lilo to the superblock.

Quote:
isnt editing lilo.conf just tip-toeing around that major problem?
No. Lilo can not possibly work if you do not configure it.

One other thing I failed to mention is which lilo.conf you're actually editing. If you are booting to a rescue floppy or CD, then chances are that your root is actually on a ramdisk vs hda3. Check and see if hda3 is mounted by running mount without any options. If it's it not, then mount it:

mkdir /mnt/hda3
mount /dev/hda3 /mnt/hda3

Then be sure and place a copy of your desired lilo.conf at /mnt/hda3/etc/lilo.conf:

cp /etc/lilo.conf /mnt/hda3/etc

Then run lilo, then the dd command, and then copy bootsect.lnx to your floppy for latter copying to C:/. Prior to rebooting, you'll probably want to unmount hda3 as well.

umount /dev/hda3

Also, if lilo is not working when installed to the superblock then there is almost a 99.9% chance that it's an configuration error and not lilo itself. Take your time and read the above instructions carefully, taking special care to do the steps in the exact order and not to use spaces for the labels and etc in lilo.conf.
 
Old 12-28-2004, 06:20 PM   #14
kleer
LQ Newbie
 
Registered: Dec 2004
Location: wisconsin, us
Distribution: Slackware Linux 10.0
Posts: 21

Original Poster
Rep: Reputation: 15
thanks for all the help, i really appreciate it

guess ill use xp cd to fix mbr - how do i get to repair teminal?

also to 'run' lilo all i do is: /sbin/lilo -v right?
 
Old 12-28-2004, 06:38 PM   #15
DaHammer
Member
 
Registered: Oct 2003
Location: Planet Earth
Distribution: Slackware, LFS
Posts: 561

Rep: Reputation: 30
Read this:

http://www.microsoft.com/resources/d...ns_fixmbr.mspx

The actual command to use inside the console is "fixmbr":
http://www.microsoft.com/resources/d...ns_fixmbr.mspx

And yeah, "/sbin/lilo -v" will work fine. but not -V. You can drop the -v altogether if you want.
 
  


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
Dualboot Win2K+Slackware akilles Linux - Newbie 3 10-04-2004 08:51 AM
FreeBSD/Slackware dualboot sether *BSD 18 09-01-2004 10:57 AM
slackware 7.1/Windows XP dualboot probs Ax3 Linux - General 4 04-12-2004 01:42 PM
Dualboot w/ Windows XP mm18050 Linux - General 6 11-22-2003 11:32 AM
Dualboot Slackware and Gentoo darkmage Linux - General 3 08-09-2002 08:18 PM


All times are GMT -5. The time now is 01:26 AM.

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