Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[nightflier]

It's a desktop computer? You could open the case and disconnect the data cable to sda.

[M0E-lnx]

You should know that if you're installing our bootloader to sdb1, you will also need to modify the bootloader installed to the MBR before you can boot off our bootloader.

This is typically done by adding an entry to that other bootloader to chain load into the bootsector you want to boot.  Not sure if you've done that

To sum it up, if you choose to install our bootloader to a bootsector (sda1, sdb1, etc) and you reboot without modifying the MBR bootloader, you will never see our boot options.

[StrayBit]

Thanks, nightflier.  I'll do that if all else fails.  With limited space, it will be hard.
I tried your suggestion, MOE-lnx.  Working with lilo

# -- Vector-RC3.1 on /dev/hdb1 --
other = /dev/hdb1
     label = Vector-RC3.1-sdb1
     loader=chain
     table=/dev/hdb1

yields

vector://home/bruce
root:# lilo -v
LILO version 24.2 (released 22-November-2015)
...
Boot other: /dev/hdb1, on /dev/hdb1, loader CHAIN
Fatal: open /dev/hdb1: No such file or directory

I've tried with hdb|hdb1 and without table.
hdb loader is grub.

[M0E-lnx]

Looks like you're doing this at the wrong place.
Why dont you back up and tell uswhich OS controls the bootloader installed to the MBR (the one that presents the boot menu first).  And tell us which bootloader that is.

Post your lilo.conf from your vector installation

Hopefully with that info we can point you in the right direction.

[StrayBit]

VL 7.3-STD-b2 is in sda1 with Lilo to sda MBR.
VL 7.3-STD-RC3.1 is in sb2 with grub in sdb MBR per your suggestion.  Used grub as lilo hangs on installation.
The reason for using sdb1 is that from b3 on, I have no mouse or keyboard after installation and reboot.  And I can't gslapt to unlock the kernel files to create an initrd - uh...
Would b2 initrd.gz work in lilo to bring up rc3.1?

[overthere]

What kernel is the working B2 using..the patched 44.27 came about that time, I think the current is 44.76 I am speculating that if the patched kernel started the issue it carried forward. for what that is worth.

[StrayBit]

gslapt is telling me

4.1.18-x86-1vl72

[nightflier]

RC3.1 uses kernel 4.4.76. Modules in B2's initrd would not be compatible with it.

How about posting your /etc/lilo.conf file?

[StrayBit]

Lilo.conf from b2

# LILO configuration file.
#
# Generated by VASM.
#
boot = /dev/disk/by-id/ata-ST340015A_5LAANG48
default = Vector
bitmap = /boot/bitmap/boot.bmp
compact
prompt
timeout = 500
change-rules
reset
lba32
vga = 788
# OS list
# -- Vector on /dev/sda1 --
image = /boot/vmlinuz
     label = Vector
     initrd = /boot/initrd.gz
     root = "UUID=3fb74c6a-0581-4ad2-9430-69080285671e"
     append = "quiet splash"
     read-only
# --
# -- Vector-TUI on /dev/sda1 --
image = /boot/vmlinuz
     label = Vector-TUI
     initrd = /boot/initrd.gz
     root = "UUID=3fb74c6a-0581-4ad2-9430-69080285671e"
     append = "2 verbose"
     read-only
# --
# -- Vector-RC3.1 on /dev/hdb1 --
other = /dev/hdb1
     label = Vector-RC3.1-sdb1
     loader=chain
     table=/dev/hdb1

and, if you want it, grub.cfg from Test(rc3.1)/boot/grub

# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  52462f97-415d-4de1-9769-2195f10535a4
else
  search --no-floppy --fs-uuid --set=root 52462f97-415d-4de1-9769-2195f10535a4
fi
if loadfont /usr/share/grub/unifont.pf2 ; then
  set gfxmode=800x600x16
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input gfxterm
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_vectorlinux_theme ###
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  52462f97-415d-4de1-9769-2195f10535a4
else
  search --no-floppy --fs-uuid --set=root 52462f97-415d-4de1-9769-2195f10535a4
fi
insmod png
if background_image /boot/grub2/themes/images/background-grub.png ; then
  set color_normal=white/black
  set color_highlight=magenta/black
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_vectorlinux_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Vector Linux 7.2 STD GNU/Linux, Linux 4.4.76" {
   insmod part_msdos
   insmod ext2
   set root='hd1,msdos1'
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  52462f97-415d-4de1-9769-2195f10535a4
   else
     search --no-floppy --fs-uuid --set=root 52462f97-415d-4de1-9769-2195f10535a4
   fi
   linux16   /boot/vmlinuz-4.4.76 root=/dev/disk/by-uuid/52462f97-415d-4de1-9769-2195f10535a4 ro quiet vga=788 
}
menuentry "Vector Linux 7.2 STD GNU/Linux, Linux 4.4.76 (TUI)" {
   insmod part_msdos
   insmod ext2
   set root='hd1,msdos1'
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  52462f97-415d-4de1-9769-2195f10535a4
   else
     search --no-floppy --fs-uuid --set=root 52462f97-415d-4de1-9769-2195f10535a4
   fi
   linux   /boot/vmlinuz-4.4.76 root=/dev/disk/by-uuid/52462f97-415d-4de1-9769-2195f10535a4 vga=788 ro 2
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###

### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

[nightflier]

That definitely won't work. Check the last section of lilo.conf, which uses outdated reference "/dev/hdb1".

I did a test setup similar to yours with two hard drives and used lilo. If you study the file below you will see that the configurator copied kernel and initrd from "boot" on sdb1 to the "/boot/tamu" directory on sda1 and use those for the boot.

Code: [Select]

# LILO configuration file                                                                                                         
# generated by 'liloconfig'                                                                                                       
#                                                                                                                                 
# Start LILO global section                                                                                                       
lba32 # Allow booting past 1024th cylinder with a recent BIOS                                                                     
boot = /dev/sda                                                                                                                   
default = linux                                                                                                                   
compact                                                                                                                           
prompt                                                                                                                             
timeout = 100                                                                                                                     
# Override dangerous defaults that rewrite the partition table:                                                                   
change-rules                                                                                                                       
reset                                                                                                                             
bitmap = /boot/bitmap/boot.bmp                                                                                                     
# Normal VGA console                                                                                                               
vga = normal
# End LILO global section

# Partition 1: Linux GUI mode
image = /boot/vmlinuz
root = /dev/sda1
label = linux
append = "4 "
read-only
initrd = /boot/initrd.gz
# Partition 2: Linux TUI mode
image = /boot/vmlinuz
root = /dev/sda1
label = linux-tui
append = "2 "
read-only
initrd = /boot/initrd.gz

# Partition 3: Linux
image = /boot/tamu/vmlinuz-vector-sdb1
root = /dev/sdb1
label = vector-sdb1
read-only
initrd = /boot/tamu/initrd-vector-sdb1


Note that "vliloconf" needed some help. I had to let it run and fail the installation to MBR, then manually edit the file and run "lilo", but at least this illustrates what it needs.

[nightflier]

And now that I think about it.. after editing lilo.conf, do you run "lilo" (as root, of course)?

Reason why I ask is that lilo should refuse to install with an erroneous lilo.conf file.

[overthere]

StrayBit

So just to be clear, you have VL7.2 B1 (not b2) 32 bit with kernel 4.1.18 on sda1 working well?

B2 32 bit had no keyboard or mouse and continued to current Rc 3.1?

the patched kernel offered as security update was 4.4.27 but you did not try it, instead you went with b2, which had no keyboard or mouse

If someone can confirm the B2 kernel was the same as the security posted 4.4.27 then the issue starts their.

if not you may try the update to a B1 install and see if you lose keyboard and mouse.

it is then the challenge to find what was changed in the kernel or modules that created the issue...

I install RC3.1 to sda2 with grub to sda2 and booted with dvd using linux root=/dev/sda2 ro

you could likely do the same to sdbx, I understand you did not install a bootloader...or installed to mbr

If you want to solve the lilo issue not completing during install try that after you get a keyboard and mouse. it is otherwise irrelevant.

sorry blablabla just my cent..I have two but I may need the other one.

[StrayBit]

nightflier:  When installing later images to sdb1, lilo would get to 100% and not proceed.  The reason I use sdb1 is that is what I know and do not know how to get that strange sequence of numbers except from reading lilo.conf.  I was unable to locate an initrd.gz in boot so could not use it.  And running lilo -v, as you say, produced error.
overthere:  (will post from other machine)  vector-version)

7.2 STD B2 built on Feb-01-2017

If I could get keyboard/mouse, then I could run lilo from sdb1 without problem.

[nightflier]

The command "blkid" will give you the UUIDs of your partitions.

If your last install to sdb1 completed when you selected grub as bootloader, there *should* be an initrd.gz in the boot dir on that partition. Now, as you want to use your lilo on sda, there is no need to install any bootloader. Re-install to sdb1 and select "none" for boot loader. If the installation finishes and you can see the kernel and initrd in sdb1, we can proceed to setting up your lilo on sda.

[StrayBit]

Re-installed RC3.1 without boot loader

vector://mnt/Test/boot
root:# ls -1
README.initrd@
System.map@
System.map-4.4.76
bitmap/
coffee.dat
config@
config-4.4.76
grub/
grub2/
inside.bmp
inside.dat
onlyblue.bmp
onlyblue.dat
tuxlogo.bmp
tuxlogo.dat
vmlinuz@
vmlinuz-4.4.76

I know I'm "blind in one eye and can't see out of the other 3" but I still don't see initrd except README