lilo -v hangs...
by however from LinuxQuestions.org on (#52P2Z)
good day everyone,
I have been upgrading my slackware -current box regularly and flawlessly.
Last night I left my box upgrading and when i woke up this morning i tried to call /sbin/lilo and it hangs on this message:
Quote:
and i cannot terminate the execution with "ctrl+c" or "ctrl+z". I have to close the console window.
This is my laptop and this is my "uname -a" and "/etc/lilo.conf" respectively:
Code:bash-5.0# uname -a
Linux localhost.home 5.4.34 #1 SMP Tue Apr 21 14:55:26 CDT 2020 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/LinuxCode:# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
#compact # faster, but won't work on all systems.
# Standard menu.
message = /boot/boot_message.txt
# Append any additional kernel parameters:
append=" "
#prompt
#timeout = 5
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# 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 = Slackware
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config endsNow, I really do not know whether it is safe to turn the computer off and try to restart, as i am afraid (from past experience) that it won't boot up.
Could any kernel expert advise me on this? will slackware boot normally?
Thank you in advance


I have been upgrading my slackware -current box regularly and flawlessly.
Last night I left my box upgrading and when i woke up this morning i tried to call /sbin/lilo and it hangs on this message:
Quote:
bash-5.0# /sbin/lilo -v LILO version 24.2 (released 22-November-2015) * Copyright (C) 1992-1998 Werner Almesberger (until v20) * Copyright (C) 1999-2007 John Coffman (until v22) * Copyright (C) 2009-2015 Joachim Wiedorn (since v23) This program comes with ABSOLUTELY NO WARRANTY. This is free software distributed under the BSD License (3-clause). Details can be found in the file COPYING, which is distributed with this software. Warning: LBA32 addressing assumed Reading boot sector from /dev/sda |
This is my laptop and this is my "uname -a" and "/etc/lilo.conf" respectively:
Code:bash-5.0# uname -a
Linux localhost.home 5.4.34 #1 SMP Tue Apr 21 14:55:26 CDT 2020 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/LinuxCode:# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
#compact # faster, but won't work on all systems.
# Standard menu.
message = /boot/boot_message.txt
# Append any additional kernel parameters:
append=" "
#prompt
#timeout = 5
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# 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 = Slackware
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config endsNow, I really do not know whether it is safe to turn the computer off and try to restart, as i am afraid (from past experience) that it won't boot up.
Could any kernel expert advise me on this? will slackware boot normally?
Thank you in advance