Hi, thanks for the response.
I am interested in Hyberbola because it is libre, systemd-free, and is the only OS that I've been able to locate that has serious misgivings (rightly so) about the Linux kernel and its adoption of horrible blobs.
The roadmap you have is great on paper and I wanted to begin my Hyperbola journey with installation of the Milky Way before the BSD migration.
I am familiar with Arch-based systems to some degree, and have used Obarun and Artix previously. Both have problems.

My GPU is: NVIDIA® GeForce® 940MX

I would ideally like i3-gaps or bspwm, but I don't mind anything fairly minimal - jwm, lxde, openbox, etc.

As long as I have something to get started with, then I can work out the rest on my own

So I just need instructions on how to get from the end of the installation guide to any lightweight graphical environment

Many thanks

It is not that complex as you think at all. First to mention is the GPU you are using could be somewhat of a problem. But we can try therefore: You can follow the generic installation-guide and after a first restart with installed GRUB you need to create your user with this (at that point I assume you are no longer booting from any installation-medium and only from your local drive, if you have problems at that point please let us look into this before):

useradd -g users -m -s /bin/bash [USERNAME]

Setup your password:

passwd [USERNAME]

Add yourself to the following basic groups:

usermod -aG audio [USERNAME]
usermod -aG video [USERNAME]
usermod -aG sys [USERNAME]
usermod -aG storage [USERNAME]
usermod -aG optical [USERNAME]
usermod -aG wheel [USERNAME]
usermod -aG power [USERNAME]

If you want to play games later on:

usermod -aG games [USERNAME]

So you should be ready now to install a graphical environment. Login as your newly created user and install:

doas pacman -S xenocara xorg-video-nouveau

From that point you would be able to execute a window-manager, I take IceWM and slim as example:

doas pacman -S icewm slim

After that you need to add slim to your execution-level:

doas rc-update add slim default

And create the following file so slim as login can execute icewm:

nano ~/.xinitrc

Content of the file:

DEFAULT_SESSION=icewm-session

case $1 in
icewm)
    exec icewm-session
    ;;
*)
    exec $DEFAULT_SESSION
esac

You should be good to go at that point, but perhaps steps are missing nevertheless for your system. This would be a rough scribble first!
Installation of Hyperbola is not that complicated, but for sure needs some work. Please be also informed: We don't support lxde, mate, xfce, gnome or kde at all. The reasoning is the mandatory dependency towards dbus.

Any help is welcome, but you should consider also not directly going back to another system before final having an overview if it is working or not on your system. That would be a first help for sure! The mentioned video-guide is for example not compatible with version 0.4 as we don't support xfce for example.

You need to start dhcpcd for getting a correct connection, either direct as root or via service on the default-level:

doas rc-update add dhcpcd default

Sorry, but is impossible to create a complete free and libre system with a full flavored environment at startup. The previous version of Hyperbola GNU/Linux-libre had also dbus included. But we don't distribute that any longer. Yes, it is harder and not that kind of user-friendly. But there is no bloat left. You need to understand the service-framework hyperrc (openrc) and therefore also how services work for getting further. I try to do my best getting through with you, noting where we can add more details for a better installation-guide.

Foremost you need to play around with OpenRC at all. So there are two runlevels getting used most:

boot
default

As written already you can add services to those runlevels like this:

doas rc-update add dhcpcd detault

This will execute the service at default-runlevel (recommended). You can review all installed services under:

/etc/init.d/

And the configuration-files under:

/etc/conf.d/

Beware: Not all services need a configuration there at all as those are only used for start-configurations and elementary parts of the services. To remove a service from a runlevel:

doas rc-update del dhcpcd default

This will remove dhcpcd then from default-runlevel.

Same to do when x-server is installed further and you want to execute it at startup, example with slim:

doas rc-update add slim default

I hope this is giving you a first idea how the service-framework is working. You can also look here for more: https://wiki.gentoo.org/wiki/OpenRC

I unexpectedly wrote a lot more than I intended

The most important thing is: HOW DO I START X ?

OK, I'm in. The annoying part is over, and now the hard work starts.

I intend to write guides for installation of the graphical environment and other 'bits' that many users would like.

When they're complete, I'll send them your way and you can see what you think of them.

Thanks for the help!

I hope I won't have too many questions, now that I can have the browser to search for answers in the same workspace as the terminal I'm grappling with! (previous to now I was having to logout and reboot from antiX USB every time I wanted to post on these forums or look for help)

Take care

If you want an ultra lightweight setup, I recommend, jwm.

Also, if you know how to set jwmkit up, its even easier, gives you a menu and a way to a poweroff easily, or via pressing a few keys at the same time.

only thing you need to do, is make sure, you change doas.conf to change the part of doas.conf to include these new two lines:

## Allow members of group wheel to execute any command
permit persist :wheel

## Same thing without a password
#permit nopass :wheel

## Allow tedu to run procmap as root without a password
permit nopass localuser as root cmd /sbin/poweroff
permit nopass localuser as root cmd /sbin/reboot
permit nopass localuser as root cmd /usr/sbin/s2ram

## Allow members of group power to execute power commands
permit nopass :power cmd openrc-shutdown
permit nopass :power cmd runit-halt
permit nopass :power cmd runit-shutdown
permit nopass :power cmd halt
permit nopass :power cmd poweroff
permit nopass :power cmd reboot
permit nopass :power cmd shutdown

## Allow root user to execute any command
#permit nopass root

Btw, you may notice a third line, right?

aka, s2ram as well,

However, there is no point, unless you have installed this:

uswsusp

also, when installed, it has a few steps for you to do, before iI think it would be to its maximum effectiveness.

that being said,

I detracted somewhat, from my original reply,

but there is one GOOD reason, you should use jwm...

JWM, uses the least cpu power, of any of the window managers that are still maintained, have a taskbar and even an application menu.

Thus, it is awesome for me, for darn sure, but you can feel free to do things however you like.

I just thought I would let you know this...

If you want, something more flashy, Lumina Desktop is also an option.

Hope this helps!

Greetings and welcome:

I'd recommend first to disable sndio. For that the following steps:

1. Mount the system with the downloaded ISO (on USB or DVD) again.
2. Get into your installation-partition with arch-chroot [DEVICE] /mnt
3. Do the following command: rc-update del sndiod default

It could be also something more than sndio itself. But first thing is to get the point of the problem on your installation.
You can always use ALSA only first and later add sndiod again. Nevertheless there could be óther problems like missing network-connections for dhcp. But as said: Needed to consider the point. So also the question: What kind of hardware is base for the installation? More details would help here.

yello mates

actually i had wrote some post installation wiki but dont have time and forget to share it on the past. i upload it on my pagure now.
it still not complete but already contains guides to set up full featured graphical desktop environment (xserver, sndio, doas, dhcp etc etc..)
it needs review and correction, and maybe include or refer it in hyperbola post installaion beginner guide

you can open it in browser:
https://pagure.io/hyperbola_wiki/blob/m … /guide.txt

or use git:
git clone https://pagure.io/hyperbola_wiki.git
cd hyperbola_wiki
nano guide.txt

goodnight