Hi all, I'm new to Linux and I just installed(on my e: drive) Mandrake Linux 9.1 Below is my pc storage configuration: C:\ win2k 60mg /dev/hda /mnt/win_c E:\ Linux 40mg /dev/hdb /mnt/win_c2 I want dual boot. I chose lilo as bootloader. When the install completed, I rebooted the pc. I got all kind of garbage like: 070707070707070707.. I booted from the mandrake cd install and went in rescue. I restored Windows boot loader and now it works. But I don't see "Linux" in os selection. If I go back in mandrake rescue cd and install bootloader Mandrake distro, then the garbage appears again. I need to go back in rescue and restore Windows bootloader. How do I set the bootloader so that I can have dual boot. Seems like when I install Mandrake's bootloader, it overrides Windows setup. That's why I need to restore windows bootloader. In the install, when I setup the bootloader, I selected /dev/hdb as mount points. Should i reinstall lilo? What else should I try? Any suggestions? Thanks, Francois.
I want dual boot. I chose lilo as bootloader. When the install completed, I rebooted the pc. I got all kind of garbage like: 070707070707070707..
It appears that lilo is picking the kernel from a wrong location. Check your lilo configuration file. Particularly, check the options boot and root. Based on what you want(i.e. to dual boot), and your PC configuration, your lilo.conf file should look like this:
boot=/dev/hdb map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message linear default=linux image=/boot/vmlinuz-2.x.x-xx <-- replace this with the correct filename of your kernel label=linux read-only root=/dev/hdb1 image=/dev/hda1 label=win2k
[ June 19, 2003: Message edited by: Alton Hernandez ]
Hi Francois Bourgault, I run W2K and MDK 9.1 dual boot on a Dell GX260 just fine. My box has a 40GB HD, which a partitioned into four parts, keeping W2K on the first part and using the remainder for MDK. Here are my lilo.conf and fdisk readouts. ================================= boot=/dev/hda map=/boot/map vga=normal default="windows" keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="linux" root=/dev/hda6 initrd=/boot/initrd.img append="quiet devfs=mount hdc=ide-scsi acpi=off" vga=788 read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hda6 initrd=/boot/initrd.img append="devfs=mount hdc=ide-scsi acpi=off" read-only image=/boot/vmlinuz-enterprise label="linux-enterpris" root=/dev/hda6 initrd=/boot/initrd-enterprise.img append="devfs=mount hdc=ide-scsi acpi=off" read-only image=/boot/vmlinuz label="failsafe" root=/dev/hda6 initrd=/boot/initrd.img append="failsafe devfs=nomount hdc=ide-scsi acpi=off" read-only other=/dev/hda1 label="windows" table=/dev/hda other=/dev/fd0 label="floppy" unsafe ============================== and the output from fdisk -l ============================== [root@localhost jerry]# fdisk -l Disk /dev/ide/host0/bus0/target0/lun0/disc: 40.0 GB, 40000000000 bytes 255 heads, 63 sectors/track, 4863 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/ide/host0/bus0/target0/lun0/part1 * 1 1277 10257471 7 HPFS/NTFS /dev/ide/host0/bus0/target0/lun0/part2 1278 4863 28804545 f Win95 Ext'd (LBA) /dev/ide/host0/bus0/target0/lun0/part5 1278 1970 5566491 b Win95 FAT32 /dev/ide/host0/bus0/target0/lun0/part6 1971 3334 10956298+ 83 Linux /dev/ide/host0/bus0/target0/lun0/part7 3335 4736 11261533+ 83 Linux /dev/ide/host0/bus0/target0/lun0/part8 4737 4863 1020096 82 Linux swap [root@localhost jerry]# =============================== Describe your box...
Joined: Oct 30, 2001
Thanks for the information. I have a Dell Dimension 8100, P4, 512 RDRAM and 1.7GHz I did some research this morning and my problem is that I installed LILO on c Windows) disk's master boot record. All I need to do is install LILO on the /boot partition. I'll look at your conf file and change mine to look like the one you have included in your post. At least the boot and root options. Francois.
Placing LILO in the MBR is not a problem. I do it all the time. However, you do have to run lilo after editing lilo.conf. This reminds me a lot of my attempts to put Linux on a Compaq server. Install went great, but on boot I got something lile 10101010101010... I believe this was because Compaq was using some screwball proprietary disk controller and the installed OS's driver wasn't as clever as the install program's. I think the problem was solvable just by adding a special Compaq module and an option in lilo.conf. Dell has also been known to use strange disk controller hardware, so you might check out the Dell tech support and/or Mandrake support resources.
Customer surveys are for companies who didn't pay proper attention to begin with.