Lilo problem after dsl-hd-installForum: HD Install Topic: Lilo problem after dsl-hd-install started by: xcoil Posted by xcoil on May 01 2005,13:41
my problem its with LILO I did run "dsl-hdinstall" to hdb2 partion all ok even with the "mkliloboot" My partions are these : Device Boot Start End Blocks Id System /dev/hdb1 1 25 200781 82 Linux swap /dev/hdb2 26 87 498015 83 Linux Device Boot Start End Blocks Id System /dev/hda1 * 1 635 2560288+ c Win95 FAT32 (LBA) but on reboot i go directly to the Windows ME I presume that lilo its not installed then i boot DSL from CD and mount /dev/hdb2 /mnt/hdb2 then i edit my /mnt/hdb2/etc/lilo.conf its like this: vga=789 # +---------------------------------------------------------------+ # | !! Reminder !! | # | | # | Don't forget to run `lilo' after you make changes to this | # | conffile, `/boot/bootmess.txt', or install a new kernel. The | # | computer will most likely fail to boot if a kernel-image | # | post-install script or you don't remember to run `lilo'. | # | | # +---------------------------------------------------------------+ # Support LBA for large hard disks. # lba32 # Overrides the default mapping between harddisk names and the BIOS' # harddisk order. Use with caution. #disk=/dev/hde # bios=0x81 #disk=/dev/sda # bios=0x80 # Specifies 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. # boot=/dev/hda # Specifies the device that should be mounted as root. (`/') # root=/dev/hdb2 # Enable map compaction: # 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 # Installs the specified file as the new boot sector # You have the choice between: bmp, compat, menu and text # Look in /boot/ and in lilo.conf(5) manpage for details # install=/boot/boot-menu.b # Specifies the location of the map file # map=/boot/map # You can set a password here, and uncomment the `restricted' lines # in the image definitions below to make it so that 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 `lilo.conf', the password will be required, but a # standard default boot will not require one. # # This will, for instance, prevent anyone with access to the # console from booting with something like `Linux init=/bin/sh', # and thus becoming `root' without proper authorization. # # Note that if you really need this type of security, you will # likely also want to use `install-mbr' to reconfigure the MBR # program, as well as set up your BIOS to disallow booting from # removable disk or CD-ROM, then put a password on getting into the # BIOS configuration as well. Please RTFM `install-mbr(8)'. # # password=tatercounter2000 # Specifies the number of deciseconds (0.1 seconds) LILO should # wait before booting the first image. # delay=20 # You can put a customized boot message up if you like. If you use # `prompt', and this computer may need to reboot unattended, you # must specify a `timeout', or it will sit there forever waiting # for a keypress. `single-key' goes with the `alias' lines in the # `image' configurations below. eg: You can press `1' to boot # `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'. # # message=/boot/bootmess.txt prompt timeout=150 # prompt # single-key # delay=100 # timeout=100 # Kernel command line options that apply to all installed images go # here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in # the Linux kernel `Documentation' directory. # # append="" append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce noapic" # Boot up Linux by default. # default=Linux image=/boot/linux24 label=Linux read-only # restricted # alias=1 image=/vmlinuz.old label=LinuxOLD read-only optional # restricted # alias=2 # If you have another OS on this machine to boot, you can uncomment the # following lines, changing the device name on the `other' line to # where your other OS' partition is. # # other=/dev/hda4 # label=HURD # restricted # alias=3 other=/dev/hda1 label="Windows(hda1)" #EOF but when i run /mnt/hdb2/sbin/lilo the result is: Unrecognized token "! Please edit /etc/lilo.conf before running lilo!" at or above line 6 in file '/etc/lilo.conf' I i´m up :P it´s about the first 1024 Mb on HDB? anyone to help me with a clue? thanks of a newbie Posted by mikshaw on May 01 2005,14:25
It looks like /mnt/hdb2/etc/lilo.conf is a different file than /etc/lilo.conf.I'm thinking you'll want to check out what /etc/lilo.conf contains at or above line 6... could be as simple as a missing hash mark (#) at the beginning of a line. Posted by jimbo62 on May 01 2005,15:25
I am no expert, but it may be that lilo is installed in the MBR of hda1 and DSL is in hdb2. If so, your lilo entry for DSL has to point to the correct location for the image. Something like:image=/hdb2/boot/linux24 label=Linux root=/dev/hdb2 Or maybe even "image=/mnt/hdb2/boot/linux24" Good luck, jimbo
Posted by mikshaw on May 01 2005,15:41
a little clarification... there's no MBR in hda1. hda1 is a partition. hda is the drive, and the location of MBR.The lilo files you have on a partition are configuration files and the files necessary to install the bootloader...although I'm not 100% positive about this last statement. Posted by xcoil on May 01 2005,16:39
this is the result of mklilobootroot@ttyp0[root]# mkliloboot Enter root partition: /dev/hdb2 /dev/root on / type ext2 (rw) /dev/scd0 on /cdrom type iso9660 (ro) /dev/cloop on /KNOPPIX type iso9660 (ro) /ramdisk on /ramdisk type tmpfs (rw,size=44900k) /proc/bus/usb on /proc/bus/usb type usbdevfs (rw,devmode=0666) /dev/hdb2 on /mnt/hd type ext2 (rw) Setting up boot loader (LILO) into the master boot record.. part: /dev/hda1, typ: 12 Warning: /etc/lilo.conf should be writable only for root Warning: '/proc/partitions' does not exist, disk scan bypassed Warning: /dev/hdb is not on the first disk Added Linux * Skipping /vmlinuz.old Added Windows(hda1) }The lilo boot installation process is finished. You must reboot to continue the final stage of the hard drive install. Reboot now? (y/...): this is all ok? but lilo doesnt start at boot :| Posted by jimbo62 on May 01 2005,20:50
It looks to me like lilo is installed on hdb. So when hda boots up, it never sees lilo. If you want lilo to be a boot loader with a menu presented when you power up the computer, lilo must be installed to the MBR of hda.Good luck, jimbo Posted by SaidinUnleashed on May 01 2005,22:18
Or, you can simply put the second hdd in front of the first in the boot order of your bios.You will get a lilo menu, and still have th option to boot M$ from hda. -J.P. Posted by jimbo62 on May 02 2005,00:41
Hey J.P. thanks. I always wondered why anyone would install lilo to the MBR of a second hard drive. I didn't realize the second hard drive could be the boot drive.jimbo
Posted by cbagger01 on May 02 2005,02:23
Another way to boot your other drive without messing up the original MBR and bootloader for your original OS is to use a floppy-based bootmanager like the Smart Boot Manager. It is easy to use and does no harm to your hard drive. You still need to have a bootloader installed at the beginning of your OS partition, though.It is also possible to run LILO from a floppy but I have never done it myself. Posted by SaidinUnleashed on May 02 2005,03:03
It's also possible to make a grub floppy, complete with a menu.< Instructions here. > -J.P. Posted by xcoil on May 05 2005,19:50
the solution was install DSL on /dev/hda:P BUT RULLLEZZZZZZZZZz! ooh yeaahhh rulllezzz and fast! i love u DSL! |