Salix Forums

I installed Salix OS 13.37 in a section separate from the version 13.1, after this 13.1 ceased to correctly boot (problems with the x server). How to fix it?

Post the contents of /etc/lilo.conf and tell us your partition layout.

Code: Select all

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
#compact        # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/salix.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,20,255,20,255,20
# 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,29,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

# Append any additional kernel parameters:
append="quiet  vt.default_utf8=1"
prompt
timeout = 50
# 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
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda1
  label = salix
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda4
  label = salix1337
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

Partitions. All is primary.
1. (sda1) - Salix 13.1.
2. (sda3) - swap.
3. (sda4) - Salix 13.37.
4. (sda2) - for data.

That's because you're booting 13.1 with the 13.37 kernel, which of course won't work, because the kernel modules from 13.37 are not available in the 13.1 partition. You need to mount the 13.1 partition from inside 13.37 and point lilo to the exact kernel.

Code: Select all

mkdir /mnt/sda1
mount /dev/sda1 /mnt/sda1

edit your lilo.conf like this for the 13.1 section:

Code: Select all

image = /mnt/sda1/boot/vmlinuz

and run lilo

Code: Select all

lilo -v

You will need to mount the sda1 partition every time you want to update lilo, or you'll get an error.

Ok, thank you George! I reinstalled lilo with the help of the program Lilo Setup.

Salix Forums

13.1 and 13.37 together on the HDD [OK]

13.1 and 13.37 together on the HDD [OK]

Re: 13.1 and 13.37 together on the HDD

Re: 13.1 and 13.37 together on the HDD

Re: 13.1 and 13.37 together on the HDD

Re: 13.1 and 13.37 together on the HDD