LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Does anyone know how to dual-boot Puppy 525 using LILO? (http://www.linuxquestions.org/questions/slackware-14/does-anyone-know-how-to-dual-boot-puppy-525-using-lilo-892388/)

Robert.Thompson 07-18-2011 06:54 PM

Does anyone know how to dual-boot Puppy 525 using LILO?
 
Hello:

I'm trying to install Puppy 525 on my Slackware 13.37 PC as a dual-boot using LILO.

Puppy is living, all on it's own, in sda6, a 6 GiB partition. It got there by using the Puppy Universal Installer and selecting a 'Full' install, not a 'Frugal' install.

I cannot find 'LILO' type instructions, only 'GRUB' type instructions.

Has anyone succeeded in doing a hard drive install of Puppy with the LILO boot loader?

Any suggestions would be appreciated.

Edit: I'll probably regret it, but I used Puppy's GRUB installer.

rokytnji 07-18-2011 07:24 PM

Take a look see through This.

http://www.google.com/cse?cx=0159956...pupsearch.html

psionl0 07-19-2011 01:00 AM

It is very easy to use lilo to boot up Puppy Linux. What I did was mount the puppy CD and copy its contents into /home/Puppy52 (/home is the mount point of my second hard drive partition). I also copied various .sfs files that I wanted puppy to mount when running.

I then edited lilo.conf to include the following:
Code:

# Linux bootable partition config begins
image = /home/Puppy52/vmlinuz
initrd=/home/Puppy52/initrd.gz
  root = /dev/sda2
  label = PuppyLinux_5.2
# Linux bootable partition config ends

(don't forget to run lilo afterwards ;)).

Robert.Thompson 07-19-2011 09:22 AM

Well, things do not seem to be working out.

The Grub boot loader launches Slackware or Puppy with no problem.

I did a 'Full' install of Puppy to sda6, not a 'Frugal' install.

When I try the LILO the boot loader, Slackware launches but Puppy does not.

Here is the Grub Menu.lst - this works: :)
Code:

<snip>
# Linux bootable partition config begins
  title Puppy Linux (on /dev/sda6)
  root (hd0,5)
  kernel /boot/vmlinuz root=/dev/sda6 ro vga=normal
# Linux bootable partition config ends
<snip>

Here is my latest lilo.conf - this does not work: :(
Code:

<snip>
# Linux bootable partition config begins
  image = /boot/vmlinuz
  initrd =/boot/initrd.gz
  root = /dev/sda6
  label = Puppy
  read-only
# Linux bootable partition config ends
<snip>

Here is the output from running lilo: :scratch:
Code:

root@lenovo:~# lilo
Warning: LBA32 addressing assumed
Added Linux_G *
Added Linux
Warning: The initial RAM disk is too big to fit between the kernel and
  the 15M-16M memory hole.  It will be loaded in the highest memory as
  though the configuration file specified "large-memory" and it will
  be assumed that the BIOS supports memory moves above 16M.
Added Puppy ?
2 warnings were issued.
root@lenovo:~#

Any suggestions would be appreciated.

brianL 07-19-2011 09:32 AM

Is Puppy's grub on /dev/sda6? If so, try this in Slack's lilo.conf:
Code:

other = /dev/sda6
  label = Puppy


Robert.Thompson 07-19-2011 09:37 AM

Quote:

Originally Posted by brianL (Post 4419022)
Is Puppy's grub on /dev/sda6? If so, try this in Slack's lilo.conf:
Code:

other = /dev/sda6
  label = Puppy


No, Puppy's grub is on /dev/sda1. This is also where lilo.conf is living.

Thanks,

brianL 07-19-2011 09:48 AM

If lilo is in the MBR, grub should be in /dev/sda6 to chainload it.

Robert.Thompson 07-19-2011 09:53 AM

Quote:

Originally Posted by brianL (Post 4419040)
If lilo is in the MBR, grub should be in /dev/sda6 to chainload it.

Thanks brianL. :)

I'm off to 'Puppyland' to re-install grub on /dev/sda6!

See you later, probably. :o

Edit:

Yikes! How do I launch my Puppy?

Can I use Slackware to install my existing GRUB boot loader?

Robert.Thompson 07-19-2011 10:19 AM

Double 'YIKES'!!

I seem to be digging a large hole, in sand, for myself.

I re-installed my original lilo.conf but got this msg when I ran lilo:
Code:

root@lenovo:~# lilo
Warning: LBA32 addressing assumed
Warning: Unable to determine video adapter in use in the present system.
Warning: Video adapter does not support VESA BIOS extensions needed for
  display of 256 colors.  Boot loader will fall back to TEXT only operation.
Added Linux_G *
Added Linux
3 warnings were issued.
root@lenovo:~#

Does anyone know what I should do?

Thanks,

brianL 07-19-2011 10:23 AM

Code:

Warning: LBA32 addressing assumed
That's not serious. Put lba32 somewhere in the global options in lilo.conf.
Code:

Warning: Unable to determine video adapter in use in the present system.
Warning: Video adapter does not support VESA BIOS extensions needed for
  display of 256 colors.  Boot loader will fall back to TEXT only operation.

No idea about them.

Robert.Thompson 07-19-2011 11:04 AM

Well, I re-ran liloconfig & installed lilo to the MBR and ran lilo.

A reboot didn't give me the lilo menu.

I had to boot into 'huge' as suggested in the error msg displayed, and, here I am.

This is my lilo.conf as a result of running liloconfig:
Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/root
  label = Linux
  read-only
# Linux bootable partition config ends

It looks good to me but it does not seem to get executed.

Edit: Ran # lilo -v -t -b /dev/sda1 and got:

Code:

root@lenovo:~# lilo -v -t -b /dev/sda1
LILO version 22.8 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 03:08:28 on Mar 27 2011

Warning: Ignoring entry 'boot'
Reading boot sector from /dev/sda1
Warning: Partition 1 on /dev/sda is not marked Active.
Warning: Unable to determine video adapter in use in the present system.
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/slack.bmp
Warning: Video adapter does not support VESA BIOS extensions needed for
  display of 256 colors.  Boot loader will fall back to TEXT only operation.
Calling map_insert_file

Boot image: /boot/vmlinuz -> vmlinuz-huge-smp-2.6.37.6-smp
Added Linux *

The boot sector and the map file have *NOT* been altered.
4 warnings were issued.
root@lenovo:~#


brianL 07-19-2011 11:09 AM

Try changing:
Code:

root = /dev/root
to:
Code:

root = /dev/sda1
If Slack's on /dev/sda1, that is.

Robert.Thompson 07-19-2011 11:38 AM

Quote:

Originally Posted by brianL (Post 4419144)
Try changing:
Code:

root = /dev/root
to:
Code:

root = /dev/sda1
If Slack's on /dev/sda1, that is.

Hi Brian:

It is on /dev/sda1 - stupid me!

Unfortunately, I still do not get the LILO menu on a reboot.

brianL 07-19-2011 11:41 AM

Mmm, I don't know what's gone wrong there. :scratch:

Robert.Thompson 07-19-2011 12:16 PM

Quote:

Originally Posted by brianL (Post 4419181)
Mmm, I don't know what's gone wrong there. :scratch:

Hi Brian:

Could it be:

Warning: Partition 1 on /dev/sda is not marked Active.

as displayed above?


All times are GMT -5. The time now is 04:49 AM.