LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-12-2006, 03:12 PM   #1
ezor
Member
 
Registered: Mar 2006
Location: Toytown, NY
Distribution: Suse10.2 FreeBSD6.2
Posts: 83

Rep: Reputation: 15
Need help with Lilo


I have installed Slackware 10.2 on one computer, Slack only with no problem, and have now installed on a second box, dual boot with WinXP which is where the problem exists.

I could see no way to resize the Win partition with fdisk, so I used Yast on a Suse cd to resize it, then did the Slack install. If I now do fdisk p I get:

The number of cylinders for this disk is set to 4998. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: (1) Software that runs at boot time e.g. old versions of Lilo. (2) Booting and partitioning of software from other OSs e.g. DOS FDISK, OS/2 FDISK.

Device Boot Start End Blocks ID System
/dev/hda1 * 1 1668 13398178* 7 HPFS/NTFS
/dev/hda2 1669 1731 506047* 82 Linux Swap
/dev/hda3 1732 4997 26234145 83 Linux

Booting from HD, Lilo doesn't run and Windows starts. Booting from floppy starts Slack. Lilo.conf shows boot = /dev/hda3. At the bottom it shows root = /dev/hda3, label= Linux.

When I run Lilo, I get a message - "Warning: Partition 3 on /dev/hda is not marked active. Added Windows* Added Linux."

Any help would be appreciated.
 
Old 03-12-2006, 03:17 PM   #2
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
If it boots, then everything is ok. It's only a warning. I think you can solve it by using cfdisk and marking the hda3 partition as bootable.
 
Old 03-12-2006, 03:28 PM   #3
ezor
Member
 
Registered: Mar 2006
Location: Toytown, NY
Distribution: Suse10.2 FreeBSD6.2
Posts: 83

Original Poster
Rep: Reputation: 15
That didn't work. Now I can't boot Slack from the boot disk either. Back to the install cd.
 
Old 03-12-2006, 03:38 PM   #4
odevans
Member
 
Registered: Nov 2005
Location: Columbus, OH, USA
Distribution: Slackware
Posts: 246

Rep: Reputation: 30
Quote:
Originally Posted by ezor
Lilo.conf shows boot = /dev/hda3. At the bottom it shows root = /dev/hda3, label= Linux.
Any chance you can post your whole /etc/lilo.conf?
 
Old 03-12-2006, 03:52 PM   #5
ezor
Member
 
Registered: Mar 2006
Location: Toytown, NY
Distribution: Suse10.2 FreeBSD6.2
Posts: 83

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by odevans
Any chance you can post your whole /etc/lilo.conf?
I could, but I just RTFM, and during the install think I chose "root" as the place to install Lilo. Manual says "Lilo will only load from here if the Linux drive is the first drive. I will reinstall and use "mbr" to place Lilo which should overwrite the Windows booter. I'll post results.
 
Old 03-12-2006, 04:33 PM   #6
ezor
Member
 
Registered: Mar 2006
Location: Toytown, NY
Distribution: Suse10.2 FreeBSD6.2
Posts: 83

Original Poster
Rep: Reputation: 15
Okay, that fixed it. Manual goes into more detail than the on screen instructions. Installing Lilo to root worked when installing Slack as the only OS, but if dual booting install Lilo to mbr. Thanks guys for responding.
 
Old 03-12-2006, 04:36 PM   #7
odevans
Member
 
Registered: Nov 2005
Location: Columbus, OH, USA
Distribution: Slackware
Posts: 246

Rep: Reputation: 30
Thanks for letting us know you've got it sorted (and how--useful for other users). Glad to hear you're up and Slacking.
 
Old 03-12-2006, 04:41 PM   #8
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
I think installing lilo to superblock didn't work because linux was on /dev/hda3 not hda1.
 
  


Reply



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
Switching from grub to lilo, messed up Lilo.conf, rescuing via Knoppix. SonicGT Debian 2 08-21-2005 01:15 PM
Lilo lost, Install disk failing to restore Lilo on dual boot? Dobie Linux - Newbie 2 05-05-2004 05:00 PM
new kernel causes lilo crash; /sbin/lilo = Warning: device 0x0305 exceeds 1024 cylind dandysf Linux - Software 0 08-26-2003 04:50 PM
I install Slackware on small HDD with LILO, can't boot LILO? kleptophobiac Slackware 4 08-10-2003 04:50 PM
Made a bootdisk with RedHat 7.1 to boot: Gave me SYSLINUX, not LILO:Want to use LILO Colonel Panic Linux - Software 0 08-17-2001 06:21 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

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

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration