linux 4.15.10-1 works fine

this bug is not fixed

problem still exists on linux-libre 4.16.7_gnu-1

linux-libre 4.17.2_gnu-1 also gets stuck during boot
parabola-systemd-cli-dual-complete-2018.06.02.iso also gets stuck during boot, it uses kernel 4.16.11_gnu

honestly idk how to fix this. Don't you have any other useful info? like dmesg logs or others?

how can i get them?

This bug, which seems very specific to your machine, could be due to some patch we use that ArchLinux doesn't. Try to build the latest linux-libre from abslibre but without patching anything..

If that doesn't work, please send us a video or photo of the bug (if it can be a video, the better), and also try to boot in fallback mode. If fallback doesn't work, then it is a serious problem.

btw, have you tried other kernels other than linux-libre? like pck, hardened, or xtreme? those are on 4.17 too

problem exists with linux-libre fallback, hardened and pck too

is this the best guide to use to "build the latest linux-libre from abslibre but without patching anything"?
https://wiki.archlinux.org/index.php/Kernels/Arch_Build_System

replaced hardware and the problem is gone

I have the same problem with openrc version and linux-libre 5.0, and i would like to help fix it.
In my case i have a GPU radeon rx570
And i have tried some diferent parameters at boot with grub or efi.
with grub i can boot into system with this parameter changed

set gfxpayload=text

and with rEFInd adding

nomodeset

In both cases i can't run a desktop enviroment and startx crashes with "no screens found".

Hi, I'm getting a similar issue with my clock at boot time. I just migrated from arch linux to parabola and then from systemd to openrc. I was following the parabola openrc wiki page.

I'm able to boot successfully but I get this error:

hwclock           | * Failed to set the system clock

It is also described here in this wiki:

https://forums-web2.gentoo.org/viewtopic-p-8420146.html?sid=6d05da1395af5fdb194181da9e4d7d57

I get this "red" error after running dmesg:

[ 9.686677] udevd⁸⁸⁹: Unknown key identifier 'zoom'

Not sure if that would help.

udev is added to sysinit successfully with the command sudo rc-update add udev sysinit

The hwclock service is not needed when using official Parabola kernels, since they use in-kernel method to handle the system time
https://wiki.gentoo.org/wiki/System_time#In-kernel_method

The solution is removing hwclock
https://wiki.gentoo.org/wiki/System_time#OpenRC_2

I knew about this issue and also read the Gentoo forum post, and I plan to package openrc so it doesn't enable hwclock by default

udev is added to sysinit successfully with the command sudo rc-update add udev sysinit

udev should be there by default when installing from nonsystemd/udev-init-scripts

Thanks! Removing the hwclock fixed the error at boot time.

Hi,

• Does 'hwclock -r works', or does it return the "Failed to set the system clock" error?
• What about running 'ntpdate pool.ntp.org' and trying 'hwclock -w'?
• What computer fails to boot?
• Does your computer needs a CMOS battery?
• What does the following command returns: 'grep . /sys/class/rtc/*/name'

Denis.

if the computer fails to boot, one must boot with a LiveISO - then chroot into the installed system and remove hwclock from the boot runlevel

# mount /dev/THE_SYSTEM_PARTITION /mnt
# arch-chroot /mnt
# rc-update remove hwclock boot
# exit 
# reboot

I completed the 'hwclock' thing with you said: https://labs.parabola.nu/issues/1642/quoted?journal_id=14752

But openrc still gets stuck on boot, after last update (pacman -Syu).

'localmount' * Mounting local filesystems ...............

rc.log can be viewed here:

[[https://bin.disroot.org/?fab4afb263a76a3d#2u4BmLSCsJDUicBaZaDbp1cYem7rjTWUZNPpSvsPCrPJ]]