NotebookForums.com › Forums › General Notebook Discussions › Linux & Other OS's › LILO on a secondary drive
New Posts  All Forums:Forum Nav:

LILO on a secondary drive

post #1 of 3
4/17/03 at 2:04am
Thread Starter 
I am somewhat experienced in installing Linux. RH7.2 on a toshiba 5005-s503 laptop (legacy-free bios ie bios settings in "Control Panel"!?!) . Had JBuilder, Oracle, weblogic 7, wireless net drivers, etc all running happily.


OK, got my 8887 and am taking the dive into Debian 30r1. My lappy came with a 60G which I have XP taking residence on. I just bought a 40G and a 2nd bracket and put it in. I installed Debian using the default menus (reminds me of the slackware days). Set my swap at 512 MB as the first part, then the rest (/dev/hdd2) as my root. I put lilo as superblock of this and made a bootfloppy. Bootfloppy works fine. Next I copied the first 512 bytes of the bootsector of the floppy to a file (dd if=/dev/hdd2 of=/bootsect.deb bs=512 count=1) and copied this file over to my NTFS partition (/dev/hda1), added it to boot.ini and when I tried to boot it, got L 01 01 ... Copied the bootsect of the floppy and got the same. Then went for broke and setup lilo to take over the mbr of /dev/hda and now my system is stuck booting to L 01 01 without even giving me the menu (I know how to fix this, just gotta dig out the damn xp cd or find the er floppy or maybe just nuke hda1 altogether once I get linux going) Is there an issue with LILO on a sager (3.15 bios) booting from a secondary slave? Or am I missing something really stupid?
Reply
Reply
post #2 of 3
4/17/03 at 4:11pm

lilo

yep ya are missing the chainloader option. Well i have to redirect you to man lilo as not to be taken as an insult just because depending your version of lilo, it could be different, i run sid. By the way if ya really want debian i will recommend running Sid for the 888X sager series, as for example acpi will be more mature and X will support 3d natively on an ati 9000 mobility, but here are a few hints.

- in order to have lilo of the MBR to chainload to a second lilo ( this one in the physical boot sector of the slave drive ), the second got to be installed. So install debian on the second hdd. Then, run lilo to install a MBR in the on the machine. Then BEFOR REBOOTING EVEN IF PROMPTED, drop to a shell, edit /etc/lilo.conf, and Define ya 2 boot and the default boot. The default /etc/lilo.conf on debian is very self explanatory. man lilo too. Remember to always rerun lilo as root anytime you edit the file to reflect the changes.

By the way, it seems that ya are trying to boot linux from windows bootloader ? Buhahahaha, no way only MS products are supported under thye MS bootloader. Surprised ? i am not. By the way the only way to dual boot an linux/MS box, no matter what drive lay out, is to give linux the bootloader, cause penguins are tolerant.
Uhmm man lilo will make more sense that i am trying to do.

anyhow post me ya lilo and a brief table of partitions with their significants names, and i could edit that for you.

Hope that helps.
Reply
Reply
post #3 of 3
4/18/03 at 4:33am
Thread Starter 
thanks for the reply. Yep just a lil rtfm on my part. man lilo.conf was the best. also the README.common.problems was good too. Wound up needing bios 0x81 in lilo.conf. Warning from lilo cued me in.

Now my win bootloader thing works too. And yes, lilo is 1st, just want to have win booter to have capability to go back to linux in case i fatfinger into windows. and besides, the penguin has a BEER

and taking yer advice about sid, got the dvd jigdoing up right now.

again, thanks
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux & Other OS's
NotebookForums.com › Forums › General Notebook Discussions › Linux & Other OS's › LILO on a secondary drive