LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (http://www.linuxquestions.org/questions/linux-software-2/)
-   -   LILO does not take change after modifying lilo.conf (http://www.linuxquestions.org/questions/linux-software-2/lilo-does-not-take-change-after-modifying-lilo-conf-4175432848/)

ic_torres 10-18-2012 04:40 AM

LILO does not take change after modifying lilo.conf
 
setup:

1. installed LILO in MBR (hda)--windows
2. linux HD is in hdc
3. OS/LILO installed good.
4. edited lilo.conf to change the timeout and labels; run lilo command.. returned good.
5. reboot
6. upon rebooting, the changes in the LILO did not took place.

anything i might missed?

/dev/random 10-18-2012 03:44 PM

Quote:

Originally Posted by ic_torres (Post 4808885)
setup:

1. installed LILO in MBR (hda)--windows
2. linux HD is in hdc
3. OS/LILO installed good.
4. edited lilo.conf to change the timeout and labels; run lilo command.. returned good.
5. reboot
6. upon rebooting, the changes in the LILO did not took place.

anything i might missed?

Hi ic_torres,
You have to run lilo again (just type lilo as root) this is because anytime you make changes to /etc/lilo.conf you need to reinstall the boot loader in order for lilo to use these changes at boot time.

Also what dist is this and can you post your lilo.conf (usually when you rerun lilo it works)

ic_torres 10-18-2012 05:08 PM

Quote:

Originally Posted by /dev/random (Post 4809373)
Hi ic_torres,
You have to run lilo again (just type lilo as root) this is because anytime you make changes to /etc/lilo.conf you need to reinstall the boot loader in order for lilo to use these changes at boot time.

Also what dist is this and can you post your lilo.conf (usually when you rerun lilo it works)

Hi Random, yes after i edited my lilo.conf, i run lilo command .. and as i posted, it went good.. i just wondered on why the changes did not took effect when i did a reboot. . (i do this wayback and it returned good) just wondering why now it did not. .. (i have replaced my board that's why i had to reinstall)

i am using Vector 6.0 . . . :)


LILO.conf
Quote:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
default = linux
compact
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
bitmap = /boot/bitmap/boot.bmp
# Normal VGA console
vga = normal
# 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
# Partition 1 : DOS/Windows
other = /dev/hda1
label = Windows
table = /dev/hda
# Partition 2: Linux GUI mode
image = /boot/vmlinuz
root = /dev/hdc13
label = Vector6.0
append = " "
read-only

# Partition 3: Linux TUI mode
#image = /boot/vmlinuz
# root = /dev/hdc13
# label = linux-tui
# append = "2 "
# read-only

# Partition 4: Linux GUI mode
#image = /boot/vmlinuz
# root = /dev/hdc13
# label = linux-gui
# append = "4 "
# read-only

# Partition 5: Linux
image = /boot/tamu/vmlinuz-linux-hdc2
root = /dev/hdc2
label = Slackware
read-only
initrd = /boot/tamu/initrd-linux-hdc2
# Partition 6: Linux
image = /boot/tamu/vmlinuz-vector-hdc3
root = /dev/hdc3
label = vector-hdc3
read-only

# Partition 7: Linux
image = /boot/tamu/vmlinuz-vector-hdc12
root = /dev/hdc12
label = vector-hdc12
read-only





results upon running lilo command :

Quote:



root:# /sbin/lilo -v -v
LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 02:39:03 on Apr 1 2008.
Running Linux kernel 2.6.27.12 on i686

Warning: LBA32 addressing assumed
raid_setup returns offset = 00000000 ndisk = 0
BIOS VolumeID Device
Reading boot sector from /dev/hda
pf_hard_disk_scan: ndevs=2
0300 2E1B2E1A /dev/hda
1600 542D2676 /dev/hdc
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 3
device codes (canonical) = 3
mode = 0x03, columns = 80, rows = 25, page = 0
Using BITMAP secondary loader
Calling map_insert_data
Secondary loader: 19 sectors (0x3800 dataend).
Warning: The boot sector and map file are on different disks.
bios_boot = 0x80 bios_map = 0x81 map==boot = 0 map S/N: 542D2676
Mapping bitmap file /boot/bitmap/boot.bmp -> std.bmp
Calling map_insert_file
Compaction removed 594 BIOS calls.
Bitmap: 603 sectors.
BIOS data check was okay on the last boot

Boot other: /dev/hda1, on /dev/hda, loader CHAIN
Compaction removed 0 BIOS calls.
Mapped 6 (4+1+1) sectors.
Added Windows

Boot image: /boot/vmlinuz -> vmlinuz-2.6.27.12
Setup length is 23 sectors.
Compaction removed 8486 BIOS calls.
Mapped 8650 sectors.
Added Vector6.0

Boot image: /boot/tamu/vmlinuz-linux-hdc2
Setup length is 14 sectors.
Compaction removed 3465 BIOS calls.
Mapped 3540 sectors.
Mapping RAM disk /boot/tamu/initrd-linux-hdc2
Compaction removed 3710 BIOS calls.
RAM disk: 3769 sectors.
Added Slackware

Boot image: /boot/tamu/vmlinuz-vector-hdc3
Setup length is 15 sectors.
Compaction removed 4708 BIOS calls.
Mapped 4801 sectors.
Added vector-hdc3

Boot image: /boot/tamu/vmlinuz-vector-hdc12
Setup length is 23 sectors.
Compaction removed 8489 BIOS calls.
Mapped 8650 sectors.
Added vector-hdc12

Fatal: Default image doesn't exist.
Removed temporary file /boot/map~



Wim Sturkenboom 10-19-2012 12:52 AM

You have a 'fatal' at the end of the output of the lilo command ;) My guess is that lilo therefore did not write to the MBR.

/dev/random 10-19-2012 09:27 AM

I am thinking the same thing, comment out the image map and see if it works, if it does, then you need to either replace the image or remove the line that gives you the fatal message.


All times are GMT -5. The time now is 10:25 PM.