You are not logged in.
- Topics: Active | Unanswered
#1 2017-10-19 22:04:52
- Olintonatiuh
- Member
- Registered: 2014-02-11
- Posts: 6
Every time I start plymouth by means of quiet splash I get this error
Every time I start plymouth by means of "quiet splash" I get this error,the fan goes crazy and the computer freezes, however to remove splash from grub ,the system start correctly , without the plymouth screen, to access the plymouth screen, I have to press the right arrow, my disk is completely encrypted with lvm2 and lucks and pressing right arrow I can use correctly the password text area, my pc is a acer e5-511p
https://photos.app.goo.gl/OxmirBvYBFE9NuWM2
H/W path Device Class Description
=======================================================
system Aspire E5-511P (Aspire E5-511P_0905_
/0 bus Aspire E5-511P
/0/0 memory 64KiB BIOS
/0/4 processor Intel(R) Celeron(R) CPU N2930 @ 1.
/0/4/8 memory 32KiB L1 cache
/0/4/9 memory 1MiB L2 cache
/0/7 memory 24KiB L1 cache
/0/f memory 8GiB System Memory
/0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MH
/0/f/1 memory SODIMM [empty]
/0/100 bridge Atom Processor Z36xxx/Z37xxx Series
/0/100/2 display Atom Processor Z36xxx/Z37xxx Series
/0/100/13 storage Atom Processor E3800 Series SATA AHC
/0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celero
/0/100/14/0 usb1 bus xHCI Host Controller
/0/100/14/0/2 bus USB2.0 Hub
/0/100/14/0/2/1 communication Bluetooth wireless interface
/0/100/14/0/2/3 input Optical Mouse
/0/100/14/0/3 input Touchscreen
/0/100/14/0/4 multimedia HD WebCam
/0/100/14/1 usb2 bus xHCI Host Controller
/0/100/1a generic Atom Processor Z36xxx/Z37xxx Series
/0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series
/0/100/1c bridge Atom Processor E3800 Series PCI Expr
/0/100/1c/0 generic RTL8411B PCI Express Card Reader
/0/100/1c/0.1 enp1s0f1 network RTL8111/8168/8411 PCI Express Gigabi
/0/100/1c.1 bridge Atom Processor E3800 Series PCI Expr
/0/100/1c.1/0 wlp2s0 network QCA9565 / AR9565 Wireless Network Ad
/0/100/1f bridge Atom Processor Z36xxx/Z37xxx Series
/0/100/1f.3 bus Atom Processor E3800 Series SMBus Co
/0/1 scsi0 storage
/0/1/0.0.0 /dev/sda disk 1TB ST1000LM014-1EJ1
/0/1/0.0.0/1 /dev/sda1 volume 449MiB Windows NTFS volume
/0/1/0.0.0/2 /dev/sda2 volume 99MiB Windows FAT volume
/0/1/0.0.0/3 /dev/sda3 volume 15MiB reserved partition
/0/1/0.0.0/4 /dev/sda4 volume 99GiB Windows NTFS volume
/0/1/0.0.0/5 /dev/sda5 volume 858MiB Windows NTFS volume
/0/1/0.0.0/6 /dev/sda6 volume 709GiB Windows NTFS volume
/0/1/0.0.0/7 /dev/sda7 volume 512MiB EXT4 volume
/0/1/0.0.0/8 /dev/sda8 volume 120GiB EFI partition
/0/2 scsi1 storage
/0/2/0.0.0 /dev/cdrom disk DVDRAM GUA0Nsudo journalctl -b [16:59:04]
-- Logs begin at Thu 2017-10-19 16:55:59 CDT, end at Thu 2017-10-19 17:02:32 CDT
oct 19 16:55:59 E5-511P kernel: Linux version 4.9.56-1-lts (builduser@andyrtr) (
oct 19 16:55:59 E5-511P kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-lts root
oct 19 16:55:59 E5-511P kernel: x86/fpu: Legacy x87 FPU detected.
oct 19 16:55:59 E5-511P kernel: x86/fpu: Using 'eager' FPU context switches.
oct 19 16:55:59 E5-511P kernel: e820: BIOS-provided physical RAM map:
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000000000000-0x00000000000
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x000000000006f000-0x00000000000
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000000070000-0x00000000000
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000000086000-0x00000000000
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001ff
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000200
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000020100000-0x0000000077c
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000077cf8000-0x0000000077d
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000077d88000-0x00000000786
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000078608000-0x00000000787
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000078708000-0x00000000787
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000078748000-0x00000000793
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000079366000-0x0000000079c
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000079c66000-0x0000000079f
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x00000000e00f8000-0x00000000e00
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x00000000fed01000-0x00000000fed
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x00000000ffb80000-0x00000000fff
lines 1-23...skipping...
-- Logs begin at Thu 2017-10-19 16:55:59 CDT, end at Thu 2017-10-19 17:02:32 CDT. --
oct 19 16:55:59 E5-511P kernel: Linux version 4.9.56-1-lts (builduser@andyrtr) (gcc version 7.2.0 (GCC) ) #1 SMP Thu Oct 12 22:34:15 CE
oct 19 16:55:59 E5-511P kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-lts root=/dev/mapper/Sistema-Raiz rw cryptdevice=/dev/sda8:Cifr
oct 19 16:55:59 E5-511P kernel: x86/fpu: Legacy x87 FPU detected.
oct 19 16:55:59 E5-511P kernel: x86/fpu: Using 'eager' FPU context switches.
oct 19 16:55:59 E5-511P kernel: e820: BIOS-provided physical RAM map:
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usable
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] ACPI NVS
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000000070000-0x0000000000085fff] usable
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000000086000-0x000000000009ffff] reserved
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000200fffff] reserved
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000020100000-0x0000000077cf7fff] usable
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000077cf8000-0x0000000077d87fff] type 20
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000077d88000-0x0000000078607fff] reserved
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000078608000-0x0000000078707fff] ACPI NVS
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000078708000-0x0000000078747fff] ACPI data
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000078748000-0x0000000079365fff] usable
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000079366000-0x0000000079c65fff] ACPI NVS
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000079c66000-0x0000000079ffffff] usable
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x00000000e00f8000-0x00000000e00f8fff] reserved
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] reserved
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x00000000ffb80000-0x00000000ffffffff] reserved
oct 19 16:55:59 E5-511P kernel: BIOS-e820: [mem 0x0000000100000000-0x000000027fffffff] usable
oct 19 16:55:59 E5-511P kernel: NX (Execute Disable) protection: active
oct 19 16:55:59 E5-511P kernel: efi: EFI v2.31 by INSYDE Corp.
oct 19 16:55:59 E5-511P kernel: efi: ACPI 2.0=0x78747014 ESRT=0x77e35918 SMBIOS=0x78607000
oct 19 16:55:59 E5-511P kernel: SMBIOS 2.7 present.
oct 19 16:55:59 E5-511P kernel: DMI: Acer Aspire E5-511P/Aspire E5-511P, BIOS V1.10 09/09/2015
oct 19 16:55:59 E5-511P kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
oct 19 16:55:59 E5-511P kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
oct 19 16:55:59 E5-511P kernel: e820: last_pfn = 0x280000 max_arch_pfn = 0x400000000
oct 19 16:55:59 E5-511P kernel: MTRR default type: uncachable
oct 19 16:55:59 E5-511P kernel: MTRR fixed ranges enabled:
oct 19 16:55:59 E5-511P kernel: 00000-9FFFF write-back
oct 19 16:55:59 E5-511P kernel: A0000-BFFFF uncachable
lines 1-36Offline
#2 2017-10-19 22:20:22
- Slithery
- Administrator
- From: Norfolk, UK
- Registered: 2013-12-01
- Posts: 5,776
Offline
#3 2017-10-29 19:04:10
- Olintonatiuh
- Member
- Registered: 2014-02-11
- Posts: 6
Re: Every time I start plymouth by means of quiet splash I get this error
# 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="i915"
# 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="base udev encrypt lvm2 autodetect modconf block filesystems keyboard fsck"
HOOKS="base udev plymouth plymouth-encrypt lvm2 autodetect modconf block filesystems keyboard fsck"
# 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=""Offline
#4 2017-11-05 12:30:26
- petris
- Member
- Registered: 2017-07-08
- Posts: 1
Re: Every time I start plymouth by means of quiet splash I get this error
I don't remember where I saw it in the wiki, however I believe the plymouth-encrypt and lvm2 hooks should be between the block and filesystems hook, and the keyboard hook places before plymouth-encrypt, like this:
HOOKS="base udev plymouth autodetect modconf block keyboard plymouth-encrypt lvm2 filesystems fsck"
I don't know if this fixes your issue or not however it may be related.
Offline