- You booted Parabola OpenRC Edition w/LXDE LiveISO (Its CORRECT)

- Installed Parabola using the installer (desktop icon) and went through the step by step process, following all the steps including the last one that offer the additional programs available within the iso. I did not encountered issues during the steps.
- After my first failure I reinstalled all execpt the additional programs from the last step of the installer (cleaning up the drive sdc) but went to the exact same problem.

- You booted the HDD SSD and when OpenRC initialized the UTC time init script the system froze (yes, Its CORRECT)

I haven't tried the systemd iso versions, neither the command method or other custom scripts yet.

Its my 1st time trying to install a Parabola (or arch or any other OpenRC supported distro).

Did you used the install scripts? (those are not usable yet)

If you refer to the installer available from the desktop, yes
Not usable yet? I did not found this info.

the openRC ISO that you used is very new - this is the first bug report about it so it could be some time before it it fully usable - if you only want to get parabola installed the simplest way possible and if you do not mind systemd, i can suggest that the systemd/LXDE ISOs is the easiest to install

I can wait a bit for the fixes on the OpenRC ISO (a feature I was curious of after some reseach), I'm also glad to give feedback on this.

Other distros on systemd worked fine on my hardware but I wish to use & support a fully Free variant if possible and hope to learn the most from it.

Would be nice that you try to install Parabola with OpenRC using this same ISO but install the base system with pacstrap, not the installation scripts (yes, they are run when clicking the desktop icon with Parabola's logo)

Its my 1st time trying to install a Parabola (or arch or any other OpenRC supported distro).

I suspected so, a problem with an init script has low relation with the installation method. Anyways I'll launch soon the updated scripts (I'm still testing them).

OK, let me try this time using pacstrap with the webpage.

Unfortunately the new iso reproduce the same bug, freezing at the exact same point using the new script installer.

Haven't tryed the pacsctrap yet but I'm on it now.

UPDATE: The same problem exist using the pacstrap method! Could it be related to my hardware or bios config?

For me it smells like an OpenRC issue. Try to install Parabola in a VM with that hardware, to see it success at least in a virtual environment.

Virtual box installed, iso mounted on a 32bit host session, installing using the install GUI script then booted finally into a log-in prompt.

But its not helpful if I can't boot out of the VM. (can it have to do with 64bits settings?)

Could be. Have you tried to install 32-bits Parabola OpenRC installation?

Since the vm does not support 64bits I assume Its the 32bits I got into it.
(i686) was the only version available from the live grub

Is anybody else reported to have successfully installed the 64bits OpenRC (assuming on non VM)?
People keep installing/testing OS on VM but I doubt its a way to really test the iso.

Meanwhile I'm considering going for a systemd parabola version since I wish to learn i3vm and the other required elements to run my system.

I know that most ppl who have tried this ISOs works for them, but looks like yours is a particular case. To check the system architecture run uname -m

check done: I have indeed the i686 version on the Virtual machine.
I also did an minimal (non VM) install of the i686 version using the gui script but the same freeze happened:

Setting system clock using the hardware clock [UTC]

If that implies hardware clock detection, how can this not fail on VM..

Side notes :
- With the help of a french video tutorial by someone migrating to openRC it seems the next step in the boot queue is : checking local filesystems
- I disabled UEFI in the bios hoping to help linux to boot but that tend to prevent UEFI type booting on devices.
- before jumping into parabola I was able to install and run archmerge using its own gui installer.

Have you tried installing other OpenRC-based distros? e.g. Devuan?

The other option I'm thinking about is to install Artix and then migrate to Parabola. They currently support x64 only, fyi

ath-yf -

it seems like you are very specifically targeting a 32-bit virtualbox - is there any special reason for that particular setup? why not 64-bit? why not qemu? why not install on your PC hardware without a VM?

if you must use a VM i would suggest you may have a better experience with QEMU - i just tested this myself in a 32-bit QEMU and it installed and booted flawlessly - virtualbox is not entirely free software so it is really not appropriate for anyone from parabola to help you use it

devuan uses sysvinit BTW

I did not tried to install OpenRC before, virtualbox being the only thing I knew because I still mainly use windows7 for professional and overall use, unfortunately it only came with 32bit hosting.

My research on arch lead me to find manjaro-architect (very interesting and detailed installer method), I was able to install it today but the option to put openRC seems gone since the last time someone made their tutorial. I will have to dig their forums or try your suggestions.

As said above OpenRC seems to work at least on 32bits vm but not on 32bits non vm.
I've ordered another SSD to hopefully work on OpenRC in a non vm setup (trying directly with arch if necessary), meanwhile I have time to spend on Manjaro for i3 study.

Can I convert Manjaro into a Parabola? Using Parabola being my main goal I could also stick with its systemd version for a while at least on this hardware.

edit: artix-linux seems a good option to try openRC in my case, never heard of it before because I was not aware about systemd.
Their website mention manjaro temporary stopping support for OpenRC explaining why I did not find it during my install.

one option you have not mentioned would be to install parabola from one of the systemd ISOs and then replace systemd with openrc https://wiki.parabola.nu/OpenRC

That was my first plan but that would mean I will still be still dependent on a systemd iso to run out of systemd :S .
(Hope the issue is just related to my hardware, for info my MB is an Asus Z97 mark S)

I will report back after Artix and Parabola systemd are installed out of vm.

You can do a Systemd installation with an OpenRC ISO. Then when the system boots, migrate to OpenRC. Please be paranoic with any error you see and report it here

Update:
On the Artix i3 iso I encountered a graphical glitch that prevent also the use of the command line:
The screen flicker and the key input is scramble meaning I can't root log in.
(the GPU is GTX1050)

On the parabola openRC iso I experienced an early freeze on reboot after the pacstrap Systemd install this time at the very beginning.
The command line process went smooth all the way.

The conclusion I've is that your problem is specific to your PC. As a last trial, install Parabola OpenRC in a different machine, which should work. I'm sorry to say this, but I think I'll close this issue soon, since it can't be reproduced in most machines and this thread is behaving more like a support forum than a bug tracker.

I agree.
The only other hardware available for me is a 32bit laptop.

I will have to figure out by my own what part is causing this but I wanted to know here if this is touching other peoples with the same architecture.
That way we can at least isolate the issue.

Thanks

romechco -

it may be helpful if you post the contents of your /var/log/Xorg.0.log

if the network is working in your new install you can wasily paste it online with this command:

cat /var/log/Xorg.0.log | nc termbin.com 9999

or you can boot the ISO again and mount the target if you need to

mount /dev/WHATEVER /mnt
  cat /mnt/var/log/Xorg.0.log | nc termbin.com 9999

in either case you a URL will be printed that you can post here

Thank bill-auger

  cat /var/log/Xorg.0.log | nc termbin.com 9999

http://termbin.com/azkb

I'm not an expert and I don't want loose your time

romechco -

it looks like maybe you do not have a usable video driver installed - 'xf86-video-vesa' at least - but i also noticed it looks like you are using virtualbox which is not supported by parabola - could you try installing again in qemu or on your real hardware