You are not logged in.
The main page https://www.devuan.org/ still shows the Devuan 4/Chimaera based information.
Ok, then you have your fallback option already. I am not 100% sure how that works in your case, I am used to use full disk encryption.
What happens in your case when the key stick isn't plugged in? Do you end up in the initramfs?
To make sure: you have not assigned a password to the encrypted /home as first step?
There is an option to cryptsetup named luksAddKey. With this option you can add further keys (either passwords or keyfiles) but this will ask for an already existing key. I have always used a passphrase as first key, and have no idea how to add a key with a keyfile as only option.
Normally this is a setting in the bios. Would be the first approach to fix this.
If ntp and nptdate aren't installed, you have no chance to use this path. BTW: with Daedalus(Bookworm) the path to the ntp.conf has changed to /etc/ntpsec.
Then cli remains: here is the link to an article that describes how to use the console to adjust date and time (scroll down towards the bottom past the timedatectl section): https://phoenixnap.com/kb/how-to-set-or … ime-ubuntu
First of all you should correct the fourth line to also read:
deb http://deb.devuan.org/merged daedalus-proposed-updates mainSince Daedalus isn't released yet, I would uncomment this line for the time being.
The rest looks ok, at least for amd64 it works.
You will need to add the NEW sub-repo non-free-firmware to be able to load something from there. Change your sources.list to:
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmwareSome reading:
https://www.debian.org/releases/bookwor … e-firmware
I assume you have installed Chimaera = Devuan Stable? Or did you use Daedalus = Devuan Testing?
Devuan kernels are Debian kernels. Generally spoken make sure you have the meta package linux-image-amd64 installed. That makes sure that the latest released kernel is pulled. For Stable you have the choice to add backports as sub-repo, currently on 6.1 kernel. Don't pull in other distros, you will create a Franken Devuan.
The initramfs will be created by the installation post-processing.
Some further information: https://github.com/NixOS/nixpkgs/issues/229450
None
Sometimes they write nonsense ....
Which release do you use?
Which kernel?
Which firmware is installed?
And you should avoid using pkgmaster, use deb.devuan.org.
Other possibilities: network or firmware issues. Have you come across the new sub-repo for the non free firmware? You need to add non-free-firmware now to all lines in the sources.list if your hardware requires to load some firmware.
I think Thunar belongs to XFCE. I am no XFCE user, mine is Cinnamon and Mate. What I can tell is:
When /dev/sda5 is mounted to /delt, you should be able to find the mount point in the file system structure. Open Thunar, then open the File System. There you should see /delt. Try to open. May fail due to access rights.
To your post #5: all devices belong to /root, there is NO way to change rights to other than root.
What you need to do is when /dev/sda5 is mounted to /delt:
Open a root console, in there:
# lsblk
# df -h
# cd /delt
# mkdir hans
# chown hans.hans hansIs /dev/sda5 mounted?
Look at post #15
To swap: Well, the installation of the server most likely re-formatted the existing swap, causing a new UUID for the partition. You will need to check the uuid with blkid and correct the fstab to make it work again.
A server running in parallel to an existing installation can be achieved by using a virtual machine in your installation, e.g. Virtual Box, qemu.
Replace pkgmaster by deb, then consider if you require the deb-src part. If you are not compiling packages then delete the 3 entries, they are not required.
In addition I suggest to add non-free-firmware (new with Bookworn/Daedalus).
The errors you are getting are grub-efi related. I guess you have booted your install media in efi mode by mistake.
Make sure that you have CSM enabled in the bios.
When booting the install media, make sure you do not use the option marked efi. Explanation: on efi systems you will typically find media entries twice. One is named normally, that boots the legacy way. The other has an efi in the name, at least on my systems. That boots the installer in efi mode.
When you install Daedalus with KDE, you will get a working system. No need to fumble, the installation takes care for replacements for the banned packages. Well, I am not a KDE user, but I have tried once Devuan/KDE in a VM, works.
I am not aware about any GUI tool to manage sysvinit, what for? Its set during the installation, and normally you do not need to change anything.
On Mate/Cinnamon you get a log file viewer as GUI tool. I would assume something like that is also available for KDE.
I have installed PA on my workstation, my laptop is using pipewire. Both do the job.
@bill.p: Which configuration are you running? Haven't seen these kind of issues on my wife's PC running Chimaera, LightDM/Mate, openrc, up to date.
That problem isn't the lock, you get a clear message in that situation, no GTK related text.
Look at this thread: https://dev1galaxy.org/viewtopic.php?id=3331
Have you got a network manager running?
Look at the boot messages or check the syslog for the phrase "missing firmware".
BTW, here is a tutorial: https://tutorialforlinux.com/2021/06/15 … tallation/
That talks about firmware. You will need to enable non-free in Chimaera's sources.list.
First thing to check is if the wlan adapter requires firmware.
Thanks, that did the job. Did run the command on Tuesday, can't remember what the output was (may be none?), too many things going on here. When checking today I saw that all logs referenced in the conf have new date stamps and are much smaller now.
Maybe I will add that to my cron jobs to be run on each first day of the month.