SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As this happens on the newly build kernels as well as on the old ones (which did not show this behaviour until now, but since kernel build of the newer ones and new lilo.conf they do as well)
this is my lilo.conf
Code:
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda
default = 4.10.8
compact # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# 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,27,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
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 120
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
image = /boot/vmlinuz-4.9.13-matt
root = /dev/sda1
label = Kernel4913
read-only
# Linux bootable partition config ends
## kernelMe config start
image = /boot/vmlinuz-4.10.8
root = /dev/sda1
label = 4.10.8
read-only
## kernelMe config end
## kernelMe config start
image = /boot/vmlinuz-4.9.20
root = /dev/sda1
label = 4.9.20
read-only
## kernelMe config end
System runs fine, I cannot see any issues in my use, so I do not expect a hardware issue, but raher something with an altered lilo.conf which I do not recognize.
Edit: there are no suspicious lilo.conf entries as I verified with my old lilo.conf and nothing except the new boot entries have been added.
Last edited by Desertwulf; 04-04-2017 at 04:39 PM.
Reason: checked. lilo.conf
So I assume that "Freeing SMP alternatives memory" is nothing to worry about.
Also, an excerpt of /var/log/messages (instead of just the output of dmseg) could help.
Anyway, knowing neither you kernel config nor your hardware makes very hard to investigate.
As itsgregman already requested, please post or link to the script you used.
Oh and in any case: lilo has certainly nothing to do with this issue as the last thing it did was to load the kernel (with no specific kernel parameter).
But, a modified init script could play a role instead.
Last edited by Didier Spaier; 04-05-2017 at 03:26 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Kernel Build and lilo.conf
