Actually, you hit a bug at alsa-66serv service. It was fixed and a new version was pushed to the observice repository. Thanks for the report.
So, update your alsa-66serv by pacman
# pacman -Sy alsa-66serv
Previously alsa-daemon dependent from alsa-restore which was a error because each service are mutually exclusive.
So disable both (replace <tree> by the name of your tree where alsa service is enabled)
# 66-disable -t <tree> -S alsa-daemon alsa-restore
Now you need to choice between one of them. Alsa-restore store your alsa state at each shutdown whereas alsa-daemon store the state "on the fly".
So, enable one of them e.g
# 66-enable -t <tree> -S alsa-restore
About documentation. We aware about the lack of documentation with examples. This will come but we need to found the time. We are a very very small team :).
Anyway,
- You got a sulogin:
- depending of the when the crash occur, you may need to remount your / with rw permissions. the right command is:
# mount -o remount,rw /
- depending of the when the crash occur, you should have the tty12 running.
- check what you have at /run/66/log/0/current which is the log of the boot.
- you can have more verbosity editing your /etc/66/init.conf and set VERBOSITY=4. At the next boot a lot of information will be available at the uncaught-logs (meaning /run/66/log/0/current file)
- you need to find information of your trees
- use the 66-intree program
- you need to find information of a services
- use the 66-inservice program
i instead copy the contents of my .66/conf/boot-user and export them from .zshenv instead, and left the 66-all up in .xinitrc. not sure if that safe
the file at .66/conf/boot-user/ will be created at every boot and need to be present for a nested user supervision tree. All user services will inherit of these variables when you start one.