You are not logged in.

#1 2018-02-07 21:24:26

Xwang
Member
Registered: 2012-05-14
Posts: 353

System hangs at ramdisk loading after today upgrades

Hi,
I've upgraded the system (an asus n752vx laptop with optimus and nvidia driver), but after reboot it hangs loading the ramdisk with the ".. loading initial ramdisk ..." message as the last one.

I've managed to downgrade all the packges and this is the pacman log:

[2018-02-07 00:04] [PACMAN] Running '/usr/bin/pacman -Sy'
[2018-02-07 00:04] [PACMAN] synchronizing package lists
[2018-02-07 19:02] [PACMAN] Running 'pacman --color auto -Sy'
[2018-02-07 19:02] [PACMAN] synchronizing package lists
[2018-02-07 19:03] [PACMAN] Running 'pacman --color auto -S -u'
[2018-02-07 19:03] [PACMAN] starting full system upgrade
[2018-02-07 19:07] [ALPM] transaction started
[2018-02-07 19:07] [ALPM] upgraded iana-etc (20170824-1 -> 20180131-1)
[2018-02-07 19:07] [ALPM] upgraded libsystemd (236.81-1 -> 237.0-2)
[2018-02-07 19:07] [ALPM] upgraded systemd (236.81-1 -> 237.0-2)
[2018-02-07 19:07] [ALPM] upgraded linux (4.14.15-1 -> 4.15.1-2)
[2018-02-07 19:07] [ALPM] upgraded acpi_call (1.1.0-96 -> 1.1.0-99)
[2018-02-07 19:07] [ALPM] upgraded fluidsynth (1.1.6-5 -> 1.1.9-1)
[2018-02-07 19:07] [ALPM] upgraded nvidia-utils (387.34-5 -> 390.25-2)
[2018-02-07 19:07] [ALPM-SCRIPTLET] If you run into trouble with CUDA not being available, run nvidia-modprobe first.
[2018-02-07 19:07] [ALPM] upgraded lib32-nvidia-utils (387.34-1 -> 390.25-1)
[2018-02-07 19:07] [ALPM] upgraded lib32-opencl-nvidia (387.34-1 -> 390.25-1)
[2018-02-07 19:07] [ALPM] upgraded lib32-systemd (236.81-1 -> 237.0-1)
[2018-02-07 19:07] [ALPM] upgraded libao (1.2.2-1 -> 1.2.2-2)
[2018-02-07 19:07] [ALPM] upgraded linux-headers (4.14.15-1 -> 4.15.1-2)
[2018-02-07 19:07] [ALPM] upgraded nvidia (387.34-21 -> 390.25-4)
[2018-02-07 19:07] [ALPM] upgraded opencl-nvidia (387.34-5 -> 390.25-2)
[2018-02-07 19:07] [ALPM] upgraded python-pillow (4.3.0-1 -> 5.0.0-1)
[2018-02-07 19:07] [ALPM] upgraded python-setuptools (1:38.5.0-1 -> 1:38.5.1-1)
[2018-02-07 19:07] [ALPM] upgraded python2-pillow (4.3.0-1 -> 5.0.0-1)
[2018-02-07 19:07] [ALPM] upgraded python2-setuptools (1:38.5.0-1 -> 1:38.5.1-1)
[2018-02-07 19:07] [ALPM] upgraded rubberband (1.8.1-3 -> 1.8.1-4)
[2018-02-07 19:07] [ALPM] upgraded serd (0.22.0-1 -> 0.22.0-2)
[2018-02-07 19:07] [ALPM] upgraded sord (0.14.0-1 -> 0.14.0-2)
[2018-02-07 19:07] [ALPM] upgraded sratom (0.4.6-1 -> 0.4.6-2)
[2018-02-07 19:07] [ALPM] upgraded systemd-sysvcompat (236.81-1 -> 237.0-2)
[2018-02-07 19:07] [ALPM] upgraded v4l-utils (1.12.5-1 -> 1.14.1-1)
[2018-02-07 19:07] [ALPM] transaction completed
[2018-02-07 19:07] [ALPM] running '60-linux.hook'...
[2018-02-07 19:07] [ALPM] running '90-linux.hook'...
[2018-02-07 19:07] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-02-07 19:07] [ALPM-SCRIPTLET] ==> Starting build: 4.15.1-2-ARCH
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-02-07 19:07] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-02-07 19:07] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2018-02-07 19:07] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-02-07 19:07] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-02-07 19:07] [ALPM-SCRIPTLET] ==> Starting build: 4.15.1-2-ARCH
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-02-07 19:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-02-07 19:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-02-07 19:07] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-02-07 19:08] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-02-07 19:08] [ALPM] running 'nvidia.hook'...
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Starting build: 4.15.1-2-ARCH
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Starting build: 4.15.1-2-ARCH
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-02-07 19:08] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-02-07 19:08] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-02-07 19:08] [ALPM] running 'systemd-hwdb.hook'...
[2018-02-07 19:08] [ALPM] running 'systemd-sysusers.hook'...
[2018-02-07 19:08] [ALPM] running 'systemd-tmpfiles.hook'...
[2018-02-07 19:08] [ALPM] running 'systemd-update.hook'...
[2018-02-07 19:08] [ALPM] running 'update-desktop-database.hook'...
[2018-02-07 21:40] [PACMAN] Running 'pacman -U iana-etc-20170824-1-any.pkg.tar.xz libsystemd-236.81-1-x86_64.pkg.tar.xz systemd-236.81-1-x86_64.pkg.tar.xz linux-4.14.15-1-x86_64.pkg.tar.xz acpi_call-1.1.0-96-x86_64.pkg.tar.xz fluidsynth-1.1.6-5-x86_64.pkg.tar.xz nvidia-utils-387.34-5-x86_64.pkg.tar.xz lib32-nvidia-utils-387.34-1-x86_64.pkg.tar.xz lib32-opencl-nvidia-387.34-1-x86_64.pkg.tar.xz lib32-systemd-236.81-1-x86_64.pkg.tar.xz libao-1.2.2-1-x86_64.pkg.tar.xz linux-headers-4.14.15-1-x86_64.pkg.tar.xz nvidia-387.34-21-x86_64.pkg.tar.xz opencl-nvidia-387.34-5-x86_64.pkg.tar.xz python-pillow-4.3.0-1-x86_64.pkg.tar.xz python-setuptools-1:38.5.0-1-any.pkg.tar.xz python2-pillow-4.3.0-1-x86_64.pkg.tar.xz python2-setuptools-1:38.5.0-1-any.pkg.tar.xz rubberband-1.8.1-3-x86_64.pkg.tar.xz serd-0.22.0-1-x86_64.pkg.tar.xz sord-0.14.0-1-x86_64.pkg.tar.xz sratom-0.4.6-1-x86_64.pkg.tar.xz systemd-sysvcompat-236.81-1-x86_64.pkg.tar.xz v4l-utils-1.12.5-1-x86_64.pkg.tar.xz'
[2018-02-07 21:40] [ALPM] transaction started
[2018-02-07 21:40] [ALPM] downgraded iana-etc (20180131-1 -> 20170824-1)
[2018-02-07 21:40] [ALPM] downgraded libsystemd (237.0-2 -> 236.81-1)
[2018-02-07 21:40] [ALPM] downgraded systemd (237.0-2 -> 236.81-1)
[2018-02-07 21:40] [ALPM] downgraded linux (4.15.1-2 -> 4.14.15-1)
[2018-02-07 21:40] [ALPM] downgraded acpi_call (1.1.0-99 -> 1.1.0-96)
[2018-02-07 21:40] [ALPM] downgraded fluidsynth (1.1.9-1 -> 1.1.6-5)
[2018-02-07 21:40] [ALPM] downgraded nvidia-utils (390.25-2 -> 387.34-5)
[2018-02-07 21:40] [ALPM-SCRIPTLET] If you run into trouble with CUDA not being available, run nvidia-modprobe first.
[2018-02-07 21:40] [ALPM] downgraded lib32-nvidia-utils (390.25-1 -> 387.34-1)
[2018-02-07 21:40] [ALPM] downgraded lib32-opencl-nvidia (390.25-1 -> 387.34-1)
[2018-02-07 21:40] [ALPM] downgraded lib32-systemd (237.0-1 -> 236.81-1)
[2018-02-07 21:40] [ALPM] downgraded libao (1.2.2-2 -> 1.2.2-1)
[2018-02-07 21:40] [ALPM] downgraded linux-headers (4.15.1-2 -> 4.14.15-1)
[2018-02-07 21:40] [ALPM] downgraded nvidia (390.25-4 -> 387.34-21)
[2018-02-07 21:40] [ALPM] downgraded opencl-nvidia (390.25-2 -> 387.34-5)
[2018-02-07 21:40] [ALPM] downgraded python-pillow (5.0.0-1 -> 4.3.0-1)
[2018-02-07 21:40] [ALPM] downgraded python-setuptools (1:38.5.1-1 -> 1:38.5.0-1)
[2018-02-07 21:40] [ALPM] downgraded python2-pillow (5.0.0-1 -> 4.3.0-1)
[2018-02-07 21:40] [ALPM] downgraded python2-setuptools (1:38.5.1-1 -> 1:38.5.0-1)
[2018-02-07 21:40] [ALPM] downgraded rubberband (1.8.1-4 -> 1.8.1-3)
[2018-02-07 21:40] [ALPM] downgraded serd (0.22.0-2 -> 0.22.0-1)
[2018-02-07 21:40] [ALPM] downgraded sord (0.14.0-2 -> 0.14.0-1)
[2018-02-07 21:40] [ALPM] downgraded sratom (0.4.6-2 -> 0.4.6-1)
[2018-02-07 21:40] [ALPM] downgraded systemd-sysvcompat (237.0-2 -> 236.81-1)
[2018-02-07 21:40] [ALPM] downgraded v4l-utils (1.14.1-1 -> 1.12.5-1)
[2018-02-07 21:40] [ALPM] transaction completed
[2018-02-07 21:40] [ALPM] running '60-linux.hook'...
[2018-02-07 21:40] [ALPM] running '90-linux.hook'...
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> Starting build: 4.14.15-1-ARCH
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> Starting build: 4.14.15-1-ARCH
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-02-07 21:40] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-02-07 21:40] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-02-07 21:41] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-02-07 21:41] [ALPM] running 'nvidia.hook'...
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Starting build: 4.14.15-1-ARCH
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Starting build: 4.14.15-1-ARCH
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-02-07 21:41] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-02-07 21:41] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-02-07 21:41] [ALPM] running 'systemd-hwdb.hook'...
[2018-02-07 21:41] [ALPM] running 'systemd-sysusers.hook'...
[2018-02-07 21:41] [ALPM] running 'systemd-tmpfiles.hook'...
[2018-02-07 21:41] [ALPM] running 'systemd-update.hook'...
[2018-02-07 21:41] [ALPM] running 'update-desktop-database.hook'...

This is my kernel command line:

 linux   /vmlinuz-linux root=UUID=74296c4e-84df-4eda-87a1-09be9d8e114b rw  pci=noaer nvidia-drm.modeset=1 initcall_debug no_console_suspend ignore_loglevel dyndbg="file suspend.c +p" 

which writes a lot of debugging on the screen when booting, but after the upgrade nothing has been written except for the "loading initial ramdisk" message.

Can you help me, please?


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#2 2018-02-08 23:16:57

Xwang
Member
Registered: 2012-05-14
Posts: 353

Re: System hangs at ramdisk loading after today upgrades

Today I've reinstalled the upgraded packages and I've installed the lts kernel and nvidia driver too.
The 4.14.17-1-lts kernel loads correctly.
The 4.15.1-2 kernel hangs after "loading initial ramdisk" message with no other message.


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#3 2018-02-08 23:24:20

loqs
Member
Registered: 2014-03-06
Posts: 17,324

Re: System hangs at ramdisk loading after today upgrades

Any change if you remove nvidia-drm.modeset=1 or blacklist the nvidia driver?

Online

#4 2018-02-08 23:26:53

Xwang
Member
Registered: 2012-05-14
Posts: 353

Re: System hangs at ramdisk loading after today upgrades

Yesterday I've tried removing all the kernel parameters without success.
I've not tried to blacklist nvidia (Is it possible to blacklist only when I load the 4.15.1-2kernel and keep nvidia on the lts?).


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#5 2018-02-08 23:32:50

loqs
Member
Registered: 2014-03-06
Posts: 17,324

Re: System hangs at ramdisk loading after today upgrades

Yes see Kernel_modules#Using_kernel_command_line_2 and only change the boot entry for the linux kernel.

Online

#6 2018-02-08 23:34:14

Xwang
Member
Registered: 2012-05-14
Posts: 353

Re: System hangs at ramdisk loading after today upgrades

Thanks.
Tomorrow I will try.


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#7 2018-02-09 23:11:11

Xwang
Member
Registered: 2012-05-14
Posts: 353

Re: System hangs at ramdisk loading after today upgrades

loqs wrote:

Any change if you remove nvidia-drm.modeset=1 or blacklist the nvidia driver?

Blacklisting nvidia has not resolved the issue.
The new kernel doesn't load.


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#8 2018-02-09 23:17:09

loqs
Member
Registered: 2014-03-06
Posts: 17,324

Re: System hangs at ramdisk loading after today upgrades

Just to ensure it is not just a screen issue nothing is recorded in the journal from these failed boots?
If not you could try more kernel options,  check the linux 4.15.2-2 update if that fails might have to bisect the kernel see if you can locate the cause of the issue.

Online

#9 2018-02-09 23:20:34

Xwang
Member
Registered: 2012-05-14
Posts: 353

Re: System hangs at ramdisk loading after today upgrades

I don't think it is a screen issue because the "loading initial ramdisk" remains on the screen, but the system is completely unresponsive (alt+stamp+REISUB does not work).
Even using the emergency option do not solve the problem.


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#10 2018-02-10 00:01:00

Xwang
Member
Registered: 2012-05-14
Posts: 353

Re: System hangs at ramdisk loading after today upgrades

4.15.2-2 update does not boot too.
So at the moment, no 4.15 kernel works on my laptop.


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#11 2018-02-10 00:28:11

Xwang
Member
Registered: 2012-05-14
Posts: 353

Re: System hangs at ramdisk loading after today upgrades

Adding noefi solves the problem.
What does that kernel parameter do?
Is it safe to use the laptop in such a way?

EDIT
the noefi does not solve the problem because only sometimes the system starts.
Moreover sometimes also the lts does not start.
I've checked the EFI boot partition and this is the result:

sudo fsck /dev/sda1
[sudo] password di andreak: 
fsck da util-linux 2.31.1
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 2
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
? 3
/dev/sda1: 551 files, 40603/65536 clusters

Is the dirty boot partition maybe related?
Should I remove the dirty bit and copy original to backup (answer 1 to both questions)?

Last edited by Xwang (2018-02-10 01:18:44)


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#12 2018-02-10 17:36:35

Xwang
Member
Registered: 2012-05-14
Posts: 353

Re: System hangs at ramdisk loading after today upgrades

Adding the earlyprintk=efi,keep to the boot command I've discovered that 4.15.xxx kernels hang at the following line:

 ... x86: Booting SMP configuration ... 

So noefi does nothing to solve the problem and still I can't load a 4.15 kernel.
Any idea?


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

#13 2018-02-11 11:23:43

Xwang
Member
Registered: 2012-05-14
Posts: 353

Re: System hangs at ramdisk loading after today upgrades

Today I've tried to add acpi=off to the kernel boot parameters of the 4.15 kernel, because I've seen that the 4.14-LTS kernel report the following line:"Using ACPI (MADT) for SMP configuration information"
So since the 4.15 kernels hang at "Booting SMP configuration", I wanted to see if the problem is ACPI related.
It seems so.
With acpi=off the boot sequence keep going  up to the moment moment when the X system should be activated, but then it stops (maybe something in my system doen't work correctly with the acpi=off).
So it seems as if the SMP configuration given by acpi is broken on 4.15 (and my i7-6700HQ).
Should I open a bug in archlinux?

EDIT
I've gone back to use the same kernel parameters I'm using with the 4.14-lts and I've avoided to pass to the 4.15 kernel the intel-ucode image changing this line in the grub.cfg file:

initrd  /intel-ucode.img /initramfs-linux.img

to

initrd /initramfs-linux.img

Now the system works perfectly.
I've tried to downgrade the intel-ucode, but system keeps hanging if initdr calls the intel-ucode.img with the newer kernel.
So it seems I've found a workaround, but somehow the system does not work correctly if I try to use intel-ucode and newer kernel.
It seems a weird bug, but I don't know to which package should I refer to open a bug.

Last edited by Xwang (2018-02-11 12:04:41)


I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.

Offline

Board footer

Powered by FluxBB