[SOLVED] Syslinux - Getting Rid of Boot Messages

Sybrid · 2016-01-23 11:59:36

Hi.
Yesterday I installed Arch Linux and it works quite awesome.
I disabled the boot menu and now what's bugging me is the boot messages.
I know they are necessary but I'd prefer to see nothing on the screen and wait a couple of seconds until the OS boots, instead of watching all of the messages I can't even read go down while changing the screen resolution twice.
How do I get rid of them on syslinux?

Thanks a lot!

Last edited by Sybrid (2016-01-23 13:19:11)

Slithery · 2016-01-23 12:07:32

Welcome to the forums Sybrid.

The answer to your question (along with everything else you need to know about Arch) can usually be found in the wiki.

Have you read...
https://wiki.archlinux.org/index.php/Silent_boot

Slithery.

Last edited by Slithery (2016-01-23 13:15:53)

Sybrid · 2016-01-23 12:27:02

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> ERROR: Unable to write to /boot/initramfs-linux.img
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: Unable to write to /boot/initramfs-linux-fallback.img

having this error when trying to execute the mkinitcpio -p linux command

Head_on_a_Stick · 2016-01-23 12:28:45

having this error when trying to execute the mkinitcpio -p linux command

Did you run the command with root privileges?

Sybrid · 2016-01-23 12:31:49

Head_on_a_Stick wrote:

having this error when trying to execute the mkinitcpio -p linux command
Did you run the command with root privileges?

Damn I suck lol...
Now I did but I got this output:
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.3.3-3-ARCH
==> ERROR: Hook '...' cannot be found
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.3.3-3-ARCH
==> ERROR: Hook '...' cannot be found
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.

Not looking too good...

Head_on_a_Stick · 2016-01-23 12:36:48

You need to post the content of /etc/mkinitcpio.conf

Sybrid · 2016-01-23 12:40:31

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES=""

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS="base udev autodetect block filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev block filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev block mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev block lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(...)

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

Last edited by Sybrid (2016-01-23 12:45:55)

Head_on_a_Stick · 2016-01-23 12:43:03

Sybrid wrote:

HOOKS=(...)

Yeah, that's not going to work.

EDIT: In fairness, the ArchWiki page does seem to be a little unclear here.

You didn't have an fsck hook in your mkinitcpio.conf anyway so you didn't have to alter it (I think).

Please add [᠎code] tags to your post to aid readability.

Last edited by Head_on_a_Stick (2016-01-23 12:46:38)

Sybrid · 2016-01-23 12:46:37

Head_on_a_Stick wrote:

Sybrid wrote:
HOOKS=(...)
Yeah, that's not going to work.
Please add [᠎code] tags to your post to aid readability.

No problem.
So I need to change HOOKS=(...) to HOOKS="" right?

Head_on_a_Stick · 2016-01-23 12:47:20

Sybrid wrote:

So I need to change HOOKS=(...) to HOOKS="" right?

No, the system wouldn't boot then.

Just change the HOOKS line back to stock.

Sybrid · 2016-01-23 13:04:27

Head_on_a_Stick wrote:

Sybrid wrote:
So I need to change HOOKS=(...) to HOOKS="" right?
No, the system wouldn't boot then.
Just change the HOOKS line back to stock.

Okay, fixed, copied and done.
Next question:
Where do I change the kernel parameters? is it in the /boot/syslinux/syslinux.cfg config file?

Slithery · 2016-01-23 13:08:37

It's in the wiki...

https://wiki.archlinux.org/index.php/Sy … parameters

Sybrid · 2016-01-23 13:15:21

It worked! Thank you for your help!

Slithery · 2016-01-23 13:17:14

No problem

To mark the thread as solved, take a look at...
https://wiki.archlinux.org/index.php/Fo … ow_to_post

Arch Linux

#1 2016-01-23 11:59:36

[SOLVED] Syslinux - Getting Rid of Boot Messages

#2 2016-01-23 12:07:32

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#3 2016-01-23 12:27:02

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#4 2016-01-23 12:28:45

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#5 2016-01-23 12:31:49

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#6 2016-01-23 12:36:48

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#7 2016-01-23 12:40:31

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#8 2016-01-23 12:43:03

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#9 2016-01-23 12:46:37

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#10 2016-01-23 12:47:20

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#11 2016-01-23 13:04:27

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#12 2016-01-23 13:08:37

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#13 2016-01-23 13:15:21

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

#14 2016-01-23 13:17:14

Re: [SOLVED] Syslinux - Getting Rid of Boot Messages

Board footer