Results 1 to 3 of 3

Thread: LILO only booting one OS

  1. #1
    Join Date
    Jul 2017
    Beans
    7

    LILO only booting one OS

    I am testing different boot loaders for my thesis and would really appreciate any help.

    I have 2 Hard drives:
    sda contains Windows 10
    sdb contains Linux Ubuntu 16.04


    I have installed LILO bootloader on Linux and have configured it and when I restart the system it boots up as it should. The problem is when I type "Windows" it boots up Windows but when I type Linux it says "Loading Linux." and keeps saying that "Loading Linux............................................. ........." like its stuck.


    "lilo.conf" configuration:


    Code:
    # /etc/lilo.conf  -   systemwide LILO configuration (LILO 24)
    # details see in manpages: lilo(8) and lilo.conf(5)
    
    
    # +-------------------------------------------------------------+
    # |                        !! Reminder !!                       |
    # |                                                             |
    # | Don't forget to run 'lilo' after you make changes to this   |
    # | conffile or you have installed a new kernel.                |
    # +-------------------------------------------------------------+
    
    
    
    
    # #################### LILO global section ######################
    
    
    # With all newer systems (until year 2004) you can use the RAM
    # above 15 MB. This option allows the use of this range of RAM.
    #large-memory
    
    
    # With all newer systems you can boot from any partition on disks 
    # with more than 1024 cylinders. This option allows the use of 
    # partitions above 1024 cylinders.
    
    
    lba32
    
    
    # Defines the boot device.  This is where Lilo installs its boot
    # block.  It can be either a partition, or the raw device, in which
    # case it installs in the MBR, and will overwrite the current MBR.
    # With newer kernel you should use the ID of the boot device, which
    # can be found here: /dev/disks/by-id/ata*.
    #boot = /dev/sdb
    
    
    boot = /dev/disk/by-id/ata-SAMSUNG_HD322HJ_S17AJ90QC03134
    
    
    # Defines the partition which is the root partition. This partition
    # will be mounted at first from the kernel. With newer kernel you
    # should use the UUID (UUID="...") of the root device, which can be
    # found here: /dev/disks/by-uuid/*.
    #root = /dev/sdb1
    
    
    root = "UUID=ba1a2592-53bf-4d5c-9b9e-4bfdc8ca8742"
    
    
    # This option may be needed for some software RAID installs.
    #raid-extra-boot = mbr-only
    
    
    # Enable map compaction.  This tries to merge read requests for 
    # adjacent sectors into a single read request. This drastically 
    # reduces load time and keeps the map smaller.  Using 'compact' 
    # is especially recommended when booting from a floppy disk.  
    # It is disabled here by default because it doesn't always work.
    #compact
    
    
    # Set the verbose level for bootloader installation. Value range:
    # 0 to 5. Default value is 0.
    
    
    verbose = 2
    
    
    # Specifies the location of the map file. Lilo creates the (sector) 
    # map file of direct sector addresses which are independent of any
    # filesystem.
    map = /boot/map
    
    
    # ---------------------------------------------------------------
    
    
    # Specifies the menu interface. You have the choice between:
    #   text: simple text menu with black background and white text
    #   menu: configurable text menu with background and text colors.
    #   bmp:  graphical menu with 640x480 bitmap background.
    install = text
    
    
    # A) Customized boot message for choice 'text'.
    # For the simple text menu you can set an extra message in the 
    # created file. Its text will be displayed before boot prompt.
    #message = /boot/message.txt
    
    
    # B) Configuration of the scheme for choice 'menu'.
    # Use following coding: <text>:<highlight>:<border>:<title>
    # The first character of each part sets the text frontcolor, 
    # the second character of earch part sets the text backcolor,
    # an upper-case character sets bold face text (frontcolor).
    #
    # E.g. 'menu-scheme=wm:rw:wm:Wm'. Possible colors: 
    # k=black, b=blue, g=green, c=cyan, r=red, m=magenta, y=yellow, w=white.
    menu-scheme = Wb:Yr:Wb:Wb
    #menu-title = " DESDEMONA Boot-Manager "
    
    
    # C) Configuration of the image for choice 'bmp'.
    # For the graphical menu you need a bitmap file, which needs a special
    # menu configuration in the file header (see: lilo -E). Ideally you 
    # use one of the delivered images of the lilo package.
    #   with 16 colors:    onlyblue, tuxlogo, inside
    #   with 256 colors:   coffee
    #   for Debian:        debianlilo, debian, debian-de
    #bitmap = /boot/tuxlogo.bmp
    
    
    # ---------------------------------------------------------------
    
    
    # Specifies the number of deciseconds (0.1 seconds) how long LILO 
    # should wait before booting the first image.  LILO doesn't wait if
    # 'delay' is omitted or set to zero. You do not see the defined menu.
    #delay = 20
    
    
    # Prompt to start one certain kernel from the displayed menu.
    # It is very recommeded to also set 'timeout'. Without timeout boot 
    # will not take place unless you hit return. Timeout is the number
    # of deciseconds (0.1 seconds) after there the default image will 
    # be started. With 'single-key' alias numbers for each menu line can
    # be used.
    
    
    prompt
    timeout = 100
    
    
    #single-key
    
    
    # ---------------------------------------------------------------
    
    
    # Specifying the VGA text mode that should be selected when booting.
    # The following values are recognized (case is ignored):
    #   vga=normal    80x25 text mode (default)
    #   vga=extended  80x50 text mode (abbreviated to 'ext')
    #   vga=ask       stop and ask for user input: choice of text mode
    #   vga=<mode>    use the corresponding text mode number. A list of  
    #                   available modes can be obtained by booting with  
    #                   'vga=ask' and then pressing [Enter].
    #
    # Another way is the use of frame buffer mode. Then the kernel 
    # will switch from the normal vga text mode (80x25) to the frame
    # buffer <mode> (if frame buffer support is in the kernel):
    #                   16bit:    32bit:
    #     640x480 :     0x311     0x312
    #     800x600 :     0x314     0x315
    #    1024x768 :     0x317     0x318
    #    1280x960 :     0x365     0x366
    #    1280x1024:     0x31A     0x31B
    #    1400x1050:     0x345     0x346
    #    1600x1200:     0x333     0x334
    #    1680x1050:     0x3D2     0x3D4
    #    1920x1440:     0x337     0x338
    #vga = ask
    vga = normal
    #vga = 0x317
    
    
    # ---------------------------------------------------------------
    
    
    # Set a password here and uncomment the 'restricted' lines in
    # the image definitions below. Then a password must be typed
    # to boot anything but a default configuration. If a command
    # line is given, other than one specified by an 'append'
    # statement in this lilo.conf, the password is required, but
    # a standard default boot will not require one.
    #
    # If anyone have access to the console, with this password and
    # the 'restricted' option you prevent booting with something
    # like 'Linux init=/bin/sh' and thus becoming `root' without
    # proper authorization.
    #password = count4this
    
    
    # Kernel command line options that apply to all installed images go
    # here.  See 'kernel-parameters.txt' in the Linux kernel 'Documentation'
    # directory. I.g. for start into 'init 5' write:  append="5"
    #append = ""
     
    # If you used a serial console to install Debian, this option should be
    # enabled by default.
    #serial = 0,9600
    
    
    # Set the image which should be started after delay or timeout.
    # If not set, the first defined image will be started.
    default = Windows
    
    
    
    
    # ################### LILO per-image section ####################
    
    
    # Each image is configured with the linux kernel (=image) and
    # usually with the initrd file. Configure all GNU/Linux systems
    # on other partitions, too.
    
    
    # Warning: labels must be less than 16 characters long.
    
    
    image = /boot/vmlinuz-4.4.0-31-generic
    	label = "Linux"
    	read-only
    #	restricted
    #	alias = 1
    #	optional
    	initrd = /boot/initrd.img-4.4.0-31-generic
    
    
    image = /boot/vmlinuz-4.4.0-92-generic
    	label = "Linux Old"
    	read-only
    #	restricted
    #	alias = 2
    #	optional
    	initrd = /boot/initrd.img-4.4.0-92-generic
    
    
    other = /dev/sda1
    	label = "Windows"
    	table=/dev/sda
    	change
    #	automatic

    This is the same configuration file without the comments:

    Code:
     
    lba32
    
     
    boot = /dev/disk/by-id/ata-SAMSUNG_HD322HJ_S17AJ90QC03134
    
     
    root = "UUID=ba1a2592-53bf-4d5c-9b9e-4bfdc8ca8742"
    
     
    verbose = 2
    
    map = /boot/map
    
    install = text
    
     
    prompt
    timeout = 100
     
    vga = normal
    
    default = Windows
    
    
    
    image = /boot/vmlinuz-4.4.0-31-generic
          label = "Linux"
          read-only
    #     restricted
    #     alias = 1
    #     optional
          initrd = /boot/initrd.img-4.4.0-31-generic
    
    image = /boot/vmlinuz-4.4.0-92-generic
          label = "Linux Old"
          read-only
    #     restricted
    #     alias = 2
    #     optional
          initrd = /boot/initrd.img-4.4.0-92-generic
    
    other = /dev/sda1
          label = "Windows"
          table=/dev/sda
          change
    #     automatic
    As you can see there is "Linux" and "Linux Old" as images, these were there by default whereas "Windows" was made manually by me.

    Is there something wrong with my configuration? If you need any more information I will be happy to provide it. Thanks in advance!

  2. #2
    Join Date
    Jul 2017
    Beans
    7

    Re: LILO only booting one OS

    I have found the solution for this, if I kept waiting while "Loading Linux...." was taking place it would take around 4 minutes 40 seconds to display "BIOS Data check successful" and ultimately boot Linux. I also discovered that in order to eliminate the 4 Minute 40 seconds wait you need to edit the lilo.conf and in the LILO Global Section, type "compact" and "Loading Linux..." will take less than 10 seconds.

    Apologies for the wasteful post but I wanted to post an answer to it instead of delete maybe someone actually stumbles upon it. Thanks

  3. #3
    Join Date
    Jul 2005
    Location
    I think I'm here! Maybe?
    Beans
    Hidden!

    Re: LILO only booting one OS

    Great news!

    Please mark as SOLVED from the Thread Tools menu up-top if this is now solved to your satisfaction. It is a great help to users searching the forum.
    DISTRO: Xubuntu 18.04-64bit --- Code-tags --- Boot-Repair --- Grub2 wiki & Grub2 Basics --- RootSudo --- Wireless-Info --- SolvedThreads

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •