The officially official Devuan Forum!

You are not logged in.

#1 Re: DIY » [SOLVED] Weather display in conky, a simple one-line-of-code solution » 2023-12-04 11:33:06

I use the Exaile music player, ... It's not in the repo

Maybe not yet.
But it has been added to the testing/ceres repo.

#2 Re: Other Issues » Seriously? » 2023-11-27 12:12:17

The answer is: fix it yourself (and/or file a bug report), or wait.

In my humble opinion, this should be promoted as the expected outcome for anyone wishing to venture into the testing/unstable waters.

Example:  A few days ago an update of nfs-common broke my ability to mount nfs shares.  I waited and no fix has showed up, yet, and I can find no bug report that addresses this.  So, I uninstalled and then reinstalled from excalibur repos.  Then I held the package to current level.  I wish I knew enough to file a helpful bug report, so instead, I will continue waiting.  In the meantime, my ceres is now fully functional, again.
If this is not something that excites you, then it would be rough sailing to jump into these waters.

#3 Re: Off-topic » now requires systemd » 2023-11-09 23:29:21

I apologize even before I ask this as I hope that I do not appear to be impatient, but will php packages for daedalus be built by any time soon?  Just trying to plan an upgrade eventually.  I have used these packages without issue for over 3 years now, so I trust them.

I did run a test by upgrading to's packages for daedalus and they appear to work fine, so this is a possibility.  If using's repo one will need to install "systemd-standalone-tmpfiles" beforehand. 

But I did get an awful feeling when I willfully installed something with "systemd" in its name.

#4 Re: Devuan » A report about systemd on » 2023-11-07 11:52:49

Hi rolfie, a quick question please.

Exception: you will need build-essential, dkms and headers to build the VBox modules, and you have to add 3 lines to /etc/modules.

Is this specific to the .deb file downloaded from the virtualbox site?  I use the virtualbox packages from debian - fast track repo for chimaera, daedalus, and excalibur - and the regular repo for ceres.  I do not have "build-essential" package installed, nor do I have any lines in /etc/modules related to virtualbox.  My setup works fine (as far as I know), and I was wondering if I was missing something.

#5 Re: Devuan » A report about systemd on » 2023-11-04 12:45:25

I have read more than once in several places on the 'net that virtualbox requires systemd.  This is not correct.  This is the output on a ceres install:

root@my-host:/home/me# apt info virtualbox
Package: virtualbox
Version: 7.0.12-dfsg-1
Status: install ok installed
Maintainer: Debian Virtualbox Team <>
Installed-Size: 134 MB
Depends: adduser, iproute2, procps, virtualbox-dkms (>= 7.0.12-dfsg-1) | virtualbox-source (>= 7.0.12-dfsg-1) | virtualbox-modules, python3 (<< 3.12), python3 (>= 3.11~), python3.11, python3:any, libc6 (>= 2.34), libcurl3-gnutls (>= 7.16.2), libdevmapper1.02.1 (>= 2:1.02.97), libgcc-s1 (>= 3.0), libgl1, libgsoap-2.8.124 (>= 2.8.124), liblzf1 (>= 1.5), libpng16-16 (>= 1.6.2), libsdl2-2.0-0 (>= 2.0.12), libssl3 (>= 3.0.0), libstdc++6 (>= 13.1), libtpms0 (>= 0.8.0~dev1), libvncserver1 (>= 0.9.10), libvpx8 (>= 1.12.0), libx11-6, libxml2 (>= 2.7.4), libxt6, zlib1g (>= 1:1.1.4)
Recommends: virtualbox-qt (= 7.0.12-dfsg-1), libqt5core5a (>= 5.15.1), libqt5gui5 (>= 5.0.2) | libqt5gui5-gles (>= 5.0.2), libqt5opengl5 (>= 5.0.2), libqt5widgets5 (>= 5.0.2), libxcb1, libxcursor1 (>> 1.1.2), libxext6
Suggests: vde2, virtualbox-guest-additions-iso

To get back on topic, well, I don't speak german so I can't comment on the linked article in the original post.

#6 Re: Other Issues » deb package installation issue » 2023-10-01 02:06:47

Question, how did you get to the root terminal prompt?  As a regular user, did you "su" to root or did you "su -" to root?  Might want to try "su -".

#7 Re: Installation » [SOLVED] Testing & Ceres » 2023-09-14 13:40:38

However, among Devuan users I have the feeling that Testing and Unstable are not used as often as with Debian. Maybe someone who works with Testing or Ceres and gets along with it will contact me.

I have been using both testing and ceres branches since around ascii.  I have installed on my hard drive the oldstable, stable, testing, and unstable versions - currently this is chimaera, daedalus, excalibur, and ceres.  As devuan gets upgraded to a new named version, I simply adjust the partitions, and grub.  Each is an installed snapshot of the stable - using refracta-tools.  I recycle the update/upgrade packages to keep these updated so as not to overuse the download mirrors.  Plus, to update each, I do it from within a chroot.  This works fine for me and I like it.

In my usage, I always use ceres as my daily driver and on the rare occasion that it does break**, I boot into the testing version and use it.  If it breaks, I go to stable.  This has worked fine for many years now and I have learned a lot.  I only recall one instance for a week or so where both the unstable and testing systems were unusable.  Fixing the unstable is usually done by doing nothing and waiting for a package fixed (dependency issue), and sometimes I have to temporarily pin (or mark) a package to a lower level.

In my experience, when using testing/unstable, I always update with "apt upgrade" and not "apt dist-upgrade".  This has saved me from breaking my systems about 15 to 20 times over the years.  Occasionally, in using testing/unstable, I do have to remove and reinstall a previous package, and I have to use the nvidia driver package to get suspend/hibernate to work as expected.  I do have to remember to reinstall all dkms packages when a new kernel is installed as they don't work initially, and have to be re-installed.  This has been happening with me for a few years now and I have not found a solution, yet.  (I haven't looked hard either, (-; )  Once in a while I will run an "apt dist-upgrade" to remove old and outdated packages, but I pay attention to what it wants to remove.  If in doubt, I leave it there and wait a while longer.  These are the only current issues I can recall. 

**A lot of problems with testing/unstable will sort itself out if you just wait a little while.  After all, these are not "stable" and problems are to be expected.  Don't use these developer tools if you don't want to learn.  It would be frustrating.

#8 DIY » How to Hibernate and Suspend » 2023-09-08 17:30:41

Replies: 0

The following information was taken mostly from the following link: … nux-distro

Situation:  Computers have this thing called power saving using Hibernation and Suspend.  I had never used it because, well, I never configured it correctly - but I really did not try very hard.  For a lot of years, I always left the computer running all day and would sometimes shut it down at night.  My local utility raised the electricity rates recently, so I thought I would try a little harder.

Result:  I have Hibernation and Suspend working flawless and upon waking up the system by either pressing the power button or typing a key on the keyboard or wiggling the mouse the system works perfectly.  Even if I save the system state with virtual machines running, they too will work perfectly.

How to configure for Hibernate/Suspend, taken from other devuan sources - mainly from
My system started as chimaera and was upgraded to daedalus.
- Create a swap partition as least as large as your current amount or RAM.
- Configure your system to use this partition as your swap area.
- at terminal run "blkid" to get the uuid info for this partition
- Add this swap partition to fstab

UUID=12345-your-uuid none    swap    sw    0    0

- Add entry to /etc/initramfs-tools/conf.d/resume


- Update initramfs with:

update-initramfs -u

-    reboot

This should get the Hibernation and Suspend working from the xfce menu.  In my case, I had a problem getting the system to wake up by pressing a keyboard key or moving the mouse.  Pressing the system power button worked fine.  I then found the link above and ran two commands to get some system information, and then made an entry to the /etc/rc.local file.

Command #1, as root: 

grep . /sys/bus/usb/devices/*/product

This will produce output that looks like this, as it will list your usb devices.  My usb keyboard and mouse were the bottom two:

/sys/bus/usb/devices/1-4/product:HD Pro Webcam C920
/sys/bus/usb/devices/1-5/product:USB Receiver
/sys/bus/usb/devices/1-6/product:USB Receiver

Command #2, as root:

grep . /sys/bus/usb/devices/*/power/wakeup

This will list the devices and whether they will be allowed to wake the system:
Note: all of mine were disabled, which is why they were not waking up the system.


In my case, I wanted my usb keyboard and usb mouse to wake the system, so I added this to my /etc/rc.local file:
echo enabled > /sys/bus/usb/devices/1-5/power/wakeup
echo enabled > /sys/bus/usb/devices/1-6/power/wakeup

In daedalus I had to add "sleep 30" to the  /etc/rc.local  to get it to work:

So the related contents of the rc.local file is:

sleep 30
echo enabled > /sys/bus/usb/devices/1-5/power/wakeup
echo enabled > /sys/bus/usb/devices/1-6/power/wakeup

Now, when I step away from the system and I don't know when I will return, I simply Menu > Logout > Suspend.  When I shut it down at night, I Menu > Logout > Hibernate.  These could be shortened with a script added to the desktop.

This works flawlessly now and has for over a year.  Hope this helps someone.

#9 Re: Other Issues » grup-pc on ceres, bug introduced because of /usr/merge » 2023-09-07 13:05:49

I don't think is it fixed in version 2.12~rc1-9 of grub-pc, which appeared in the repos yesterday:

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.4.0-4-amd64
Found initrd image: /boot/initrd.img-6.4.0-4-amd64
/usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found
dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned error ex
it status 127

apt policy grub-pc
  Installed: 2.12~rc1-9

After the upgrade produced this error, I did a complete removal of grub with:

apt remove grub-common grub-pc grub-pc-bin grub2-common --purge

And then installed with:

apt install grub-common grub-pc grub-pc-bin grub2-common os-prober

And it still produced the error above.
/etc/grub.d/25_bli is there and it contains:

set -e

# <comments removed>

cat << EOF
if [ "\$grub_platform" = "efi" ]; then
  insmod bli

lines #290-305 of /usr/sbin/grub-mkconfig are:

for i in "${grub_mkconfig_dir}"/* ; do
  case "$i" in
    # emacsen backup files. FIXME: support other editors
    *~) ;;
    # emacsen autosave files. FIXME: support other editors
    */\#*\#) ;;
      if grub_file_is_not_garbage "$i" && test -x "$i" ; then
        echo "### BEGIN $i ###"
        echo "### END $i ###"

Thanks sangam:

isn't changing shebang of /etc/grub.d/25_bli to #!/bin/sh should fix this?

It sure did, and it installed without error after doing an "apt dist-upgrade"

This package will need to be edited after installing or updating, or rebuilt.

#10 Other Issues » grup-pc on ceres, bug introduced because of /usr/merge » 2023-09-05 14:29:27

Replies: 5

I have a ceres mbr install (no efi) and I just did my daily update and got this error:

/usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found
dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned error ex
it status 127
Errors were encountered while processing:

An explanation can be found here from the developer, but to quote the last entry:

While this has been fixed upstream already, systems like yours are
also not supported anymore, since merged-usr is mandatory since

I'm going to set a fixed version in the future for the version
that includes the fix.

So, if you are running ceres, you might want to pin grub to what you have got and hold off on the update to version 2.12~rc1-7:

apt policy grub-pc
  Installed: 2.12~rc1-7
  Candidate: 2.12~rc1-7
  Version table:
*** 2.12~rc1-7 500
        500 ceres/main amd64 Packages
        100 /var/lib/dpkg/status

#11 Re: Freedom Hacks » Eudev broken on Ceres (maybe Daedulus) » 2023-07-24 19:39:49

A small typo in this line hunter0one:

apt-mark hold libgudev-1.0.0

You can also downgrade to version 237-2, which is the daedalus version.  This will fix it.

Activate the daedalus stanza in the sources.list, and "apt update".

sudo apt install libgudev-1.0-0=237-2

Comment out the daedalus stanza, or remove, from the sources.list file.

Then hold in apt with the command

apt-mark hold libgudev-1.0-0

The current broken version is 238-2, so the fixed version should have a higher number.
When it is fixed, remove hold with

apt-mark unhold libgudev-1.0-0

Then update as usual.

#12 Re: Installation » How to get a deployable full install media set » 2023-07-23 11:43:15

Check out refractasnapshot.

And "refractainstaller".

apt install refractasnapshot-base refractainstaller-base

Configure the snapshot build to your liking by altering the "/etc/refractasnapshot.conf" and the "/usr/lib/refractasnapshot/snapshot_exclude.list" files.

#13 Installation » xorg bug with daedalus rc5 ? » 2023-07-16 22:37:25

Replies: 0

I may have run across a slight bug while installing the daedalus rc5 release iso. 

I tried to install xorg and ran across this error:

root@localhost:/etc/apt# apt install xorg
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 luit : Breaks: x11-utils (< 7.7+6) but 7.7+5 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

I installed the rc5-netinstall iso file and initially only installed the system utilities and console productivity parts. Afterwards, I then tried to install xfce, lightdm, xorg, and a few other desktop programs.
It was the xorg package that gave me the problem.

This was the situation after the initial netinstall:

root@localhost:/etc/apt# apt policy xorg
  Installed: (none)
  Candidate: 1:7.7+23
  Version table:
     1:7.7+23 500
        500 [url][/url] daedalus/main amd64 Packages

Once I ran the below to manually install x11-utils, xorg installed as expected.

root@localhost:/etc/apt# apt install x11-utils
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libxcb-shape0 libxv1 libxxf86dga1
Suggested packages:
The following packages will be REMOVED:
The following NEW packages will be installed:
  libxcb-shape0 libxv1 libxxf86dga1 x11-utils
0 upgraded, 4 newly installed, 1 to remove and 0 not upgraded.
Need to get 355 kB of archives.
After this operation, 831 kB of additional disk space will be used.
Do you want to continue? [Y/n] 

A subsequent reboot and the lightdm login worked fine.

It looks like it initially is trying to install an older version of the "x11-utils" package.  I hope that package "luit" was not important.  My sources.list file is the default, but I added the "non-free" and "contrib" sections to the repo lines.

#14 Re: Devuan » Devuan 5 Daedalus Release (Debian 12 - Bookworm) | Looking for info » 2023-06-28 13:56:22

The only thing you will need to do is to enable security, updates and backports if required. They will become activated once Daedalus changes to stable.

I saw it mentioned somewhere, I think on the mailing list, that the "updates" and "security" parts are now active.  I have added this to the daedalus repository and can confirm that they are now active.  Have not checked the backports, yet.

#15 Re: Devuan » Devuan 5 Daedalus Release (Debian 12 - Bookworm) | Looking for info » 2023-06-16 19:52:38

If were to do a clean install using the Daedalus iso while it is in development, will there be any additional steps I'd need to make once Daedalus is moved to stable? Or would I be able to continue running Daedalus as installed?

Unless there is a major change made that can not be altered by apt re-installing a package, then yes you should be able to continue using it.  Personally, I do not foresee this happening.  I am sure that this will be mentioned again, but you will need to alter your /etc/apt/sources.list file after daedalus goes stable.  Right now, only the "main" repo is available in daedalus.

#16 Re: Hardware & System Configuration » nfs setup server and client (nit permanently in the network) » 2023-05-23 00:10:17

You can also run into problems if the server goes down while the client still has the share mounted.
I find it better to use autofs, which will mount the share when you try to use it.

And autofs will unmount the nfs share at a preferred and configured timeout period.

#17 Re: Desktop and Multimedia » [SOLVED] Remote X session - what works? » 2023-04-29 20:20:17

ssh, vnc, rdesktop is basically all I know.

There are a lot of possibilities here and I will throw out the one example that I use the most:  Xephyr, Xming, and SSH and the technology is called Nested Xsessions.

Xephyr is a linux program which runs nested X sessions on the client (local) system.  Xming is the windows program that displays the remote system on a local windows computer.  SSH is the tunnel to transport the xsession from remote to local.  You might have to also use Putty with windows and Xming.  At the time, I had never heard of "nested Xsessions" before so this was all new to me.  I prefer it over VNC, X11vnc, etc. as you do not have to have an Xsession running on the remote system.  It only has to be installed, and you start the remote xsession from the local machine and it displays within the Xephyr window on the local desktop.

There is a lot written about this on the web, so check if you think it may fit your needs.  The many tutorials written on the web explains it better than I can.  The hardest part for me to get it working initially was getting the Display number right.  Also, you might have to make a few configuration changes on the server involving ssh xforwarding, so root access would be required there.

For my needs, I use it to access a remote server that is running in headless mode which has a lightweight xserver installed on it (Xfce).  It is not perfect but it is the best that I have used to access a remote server which does not have a X session running.  I have two aliases configured in my local client bash profile so it is easy and quick to access the remote server.

My goal is to get JWM on the remote server instead of Xfce, since it is uses less resources.  This is a work in progress.

#18 Re: Off-topic » now requires systemd » 2023-02-20 13:09:59

Well done and much appreciated!!

I agree.  Thank you.

#19 Re: Devuan Derivatives » Announcing JWM Kit Live [updated iso download] » 2023-01-20 02:31:23

Thank you for the newer post links.  I did a search and responded to the thread that showed first.  Sorry about posting in the oldest thread.

Thank you for your work / contribution.

#20 Re: Devuan Derivatives » Announcing JWM Kit Live [updated iso download] » 2023-01-19 10:54:43

Well I think I will resurrect an almost two year old thread today.  I think this belongs here instead of a new topic.

I am having trouble getting the following items from the JWM-Kit to open - Freedesktops, Trays, and Menus.  These will not open and I can see no notations anywhere in any log file that might display a missing dependency message or something similar.  Also it is not picking up the .desktop files to display within the menu.  So when I click on the start button (the rocket icon in the system tray - left side) I can see the menu but all that is displaying is the word "Applications", then a double line horizontal separator, and the word "Exit".  If the menu needs to be built manually, that is fine, but I am unable to open the menu builder program of JWM-Kit. 

I feel like I am missing a dependency, but that is a guess.  What I am using is a 64-bit beowulf minimal netinstall with a dist-upgrade to chimaera.  I installed jwm and xserver-xorg, then installed the jwmkit*.deb file, and finally the programs menu and arandr.  I am using the devuan 32bit build from the above links as a guide.

Any ideas on what is needed for the missing JWM-Kit programs to display?

Edit:  I think I was accurate with the missing dependency.  If anyone knows what it is, I would like to know.  This JWM-kit works fine on a chimaera netinstall 64bit build.  Been tinkering with it some this morning, and am impressed with it.

#21 Documentation » Wireguard VPN install » 2022-11-01 02:01:10

Replies: 0

This post may look long, and it is.  After installing, using, and fighting with an openvpn server for about 6 years, configuring and using a wireguard vpn server is much easier.  A lot has been shared on the internet on installing and configuring wireguard.  I don't think another one is needed, but I tried to put together a wireguard vpn and this is what I came up with on Devuan Chimaera. 

The information below was mainly taken from these two tutorials: … debian-10/

Dual stack ipv4 and ipv6: … -nat-ipv6/

Also, I did run across and implement a couple of features that appear to work well with wireguard and devuan.  These two items are 1- a sysvinit start/stop/status script, and 2- how to run multiple instances on the same vps, using different ports.  You may not need to run wireguard on multiple ports but if you have a dedicated vps server, and one port is blocked by an internet service provider, having another port available might be of use.  This "should" get a functional vpn tunnel operational, and then you can do more advanced things within the tunnel itself, if you wish.

Configuration steps:
- install wireguard
- Configure keys and wg0 file on both the server and peer (client)
- Create sysvinit startup script
- sysctl.conf edits to allow for routing on the server
- Add vpn profile to mobile device with a qr-code scan
- Import WireGuard profile using Network-Manager (nmcli)
- Create multiple instances of wireguard on different ports (same host/server) (optional)

On Server

apt install wireguard

create keys:

wg genkey | sudo tee /etc/wireguard/privatekey | wg pubkey | sudo tee /etc/wireguard/publickey


sudo nano /etc/wireguard/wg0.conf

Add to wg0.conf file, you may choose your own ip address subnets, and you may select a different port number:   

Address =,fd00::1/64
ListenPort = 51820
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE; ip6tables -A FORWARD -i %i -j ACCEPT; ip6tables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE; ip6tables -D FORWARD -i %i -j ACCEPT; ip6tables -t nat -D POSTROUTING -o eth0 -j MASQUERADE

AllowedIPs =,fd00::2   
PersistentKeepalive = 24


sudo chmod 600 /etc/wireguard/{privatekey,wg0.conf} … it-script/
Sysvinit start/stop/status script:

nano /etc/init.d/wg0

Add this to file:

#!/bin/sh -eu
# checkconfig: 2345 30 70
# description: set up a WireGuard interface simply
# Provides: wg-quick
# Required-Start: $local-fs $network
# Required-Stop: $local-fs $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: set up a WireGuard interface simply

description="wg-quick on $interface"

status() {
    /usr/bin/wg show $interface

start() {
    touch $logfile && date >>$logfile
    echo "starting $description ..." | tee -a $logfile
    $command up $interface >>$logfile 2>&1
    echo "... started $description" | tee -a $logfile

stop() {
    touch $logfile && date >>$logfile
    echo "stopping $description ..." | tee -a $logfile
    $command down $interface >>$logfile 2>&1
    echo "... stopped $description" | tee -a $logfile

case "${1-}" in
    status) status ;;
    start) start ;;
    restart) stop || true; start ;;
    stop) stop ;;
    *) echo "usage: $0 {status|start|restart|stop}" ;;

Make executable with

chmod +x /etc/init.d/wg0

Update default rc links:

update-rc.d wg0 defaults

Enable IPv4 and IPv6 routing on the server
In /etc/sysctl.conf, add or uncomment these, and save file

net.ipv6.conf.all.forwarding = 1

Save the file and apply the change:

sudo sysctl -p

Open up your firewall to allow for incoming udp connections to the port number you specified, if it is different from port 51820. 

On Client

apt install wireguard

create keys:

wg genkey | sudo tee /etc/wireguard/privatekey | wg pubkey | sudo tee /etc/wireguard/publickey

Create the file wg0.conf and add the following contents:

sudo nano /etc/wireguard/wg0.conf

Add this to the wg0.conf file on the client machine

Address =
DNS =,2620:0:ccc::1

Endpoint = SERVER_IP_ADDRESS:51820
AllowedIPs =

The client keys needed for a mobile device can be created on any computer, and does not need to be created on the mobile device itself.  I just created a different folder and populated it with the keys so that the other keys were not overwritten.

At this point, you should have a fully functional wireguard vpn server.  But you will need to start the wg0 service first.

service wg0 start

Useful commands to see wg0 on server, or use "service wg0 {start,stop,status}"
To start vpn tunneling:

sudo wg-quick up wg0

To stop the tunneling, bring down the wg0 interface:

sudo wg-quick down wg0

To check the interface state and configuration, run:

sudo wg show wg0

You can also verify the interface state with ip a show wg0:

ip a show wg0 … uard-ipv6/

Add vpn profile to mobile device with qr-code scan.  To generate qr code for android import: 

apt install qrencode

From the computer where the client keys and client wg0.conf file are located, as root

qrencode -t png -o wg0.png < wg0.conf


qrencode -t ansiutf8 < wg0.conf

The qr-code will display in the terminal, and from the wireguard mobile app
    Add > Scan from QR Code
Once the profile is imported, minor changes can be made to the profile itself as editing is allowed. … -on-linux/

How to import WireGuard profile using nmcli (Network-Manager) on Linux.  We can import /etc/wireguard/wg0.conf by typing the following command(s):

Set up shell environment variable:


Now import it using the nmcli command:

sudo nmcli connection import type wireguard file "$file"

Rename profile wg0 as hostname-wg0, or whatever you want it to be:

nmcli connection modify wg0 "hostname-wg0"

You may repeat this procedure for all WireGuard profiles on Linux when using NetworkManager CLI interface called nmcli.

Multiple instances on same host with different ports, minimal changes are needed to a newly created wg1 interface file.  The file can be given any name.
wg1 sounds good for this example.

Make duplicate of wg0.conf file

cd /etc/wireguard


cp wg0.conf wg1.conf

Edits to wg1.conf file, change the listening port

ListenPort = ??

    (whatever port you choose)

Also, the noted [Peer] subnet must be different from wg0!
Change this from what is noted in the wg0.conf file:

AllowedIPs =,fd00::3


AllowedIPs =,fd01::3

The rest of the file can stay the same, including the keys.

sudo chmod 600 /etc/wireguard/wg1.conf

The best port to use for a vpn is open for discussion.  Which port is least likely to be blocked by internet carriers?
Wireguard only uses udp, not tcp.  Ports 443 and 53 are most often mentioned as least likely to be blocked.

Add / edit the /etc/init.d/wg1 script
Make copy of /etc/init.d/wg0 script

cd /etc/init.d


cp wg0 wg1

Open file /etc/init.d/wg1

nano wg1

and change the following line:


change to:


Save the file.

The first time above we ran
    update-rc.d wg0 defaults
to update the script links into the /etc/rc.d folders.  However, when it is run again with
    update-rc.d wg1 defaults
It does not build any links in any rc0, rc1, rc2... folders, and this response is noted in the terminal,

insserv: script wg1: service wg-quick already provided!

But the wg1 service still works, it just does not start at boot.  This can be corrected by adding

service wg1 start

to /etc/rc.local file so it will start at boot.  You might want the rc.local file to look like this:

service wg1 start
sleep 1
exit 0

The  service {wg0,wg1} start/stop/status  commands will work.

The additional memory usage for the extra interface is minimal on a 512mb vultr vps server.  CPU and memory use is quite light with wireguard in general.

Additional and helpful info on wireguard: … ts_on_the/

I hope I did not overlook anything.

I get a little paranoid using public wifi hotspots.  I am glad my vpn is operational again and I don't want to pay for a vpn if I can host my own.

#22 Re: Other Issues » Broken after dist-upgrade Daedalus » 2022-10-26 19:32:04

I too had this problem, so I uninstalled gnome-keyring.  Nothing much was removed maybe a dependency or two and I can't find anything that is not working, yet.  It no longer locks the cpu at 100% usage.

#23 Re: Hardware & System Configuration » [SOLVED] Realtet 8852 wireless in Chimaera » 2022-10-21 15:25:19

You need to target chimaera-backports for that package, just as you did for the individual kernel package.

I learned something new today.  I will install it now so my kernel does not get left behind on the update process. 

Thanks HOAS.

The same would be true for the header files as well.

apt install -t chimaera-backports linux-headers-amd64

#24 Re: Hardware & System Configuration » [SOLVED] Realtet 8852 wireless in Chimaera » 2022-10-21 11:06:11

Try this,

apt install -t chimaera-backports linux-image-5.18.0-0.deb11.4-amd64

Then you may uninstall the default kernel if you wish, after a reboot of course.  The reboot should boot the new kernel, and you can verify this by running - after the reboot,

uname -a

#25 Re: Hardware & System Configuration » [SOLVED] Realtet 8852 wireless in Chimaera » 2022-10-20 19:18:38

I had a similar issue two weeks ago.  I had a 5 or 6 year old HP laptop in good condition but the wifi card in it was only 2.4ghz and I wanted a 5ghz card for the speed.  So I bought one off of ebay.  It was a RTL8821CE 802.11ac.  It did not work with the stock kernel in chimaera, so I installed a newer kernel from chimaera-backports.  The dkms module built fine then and it works like a charm.  It was the first time I ever needed a newer backported kernel.

Installed the necessary firmware:

apt install firmware-realtek

Add the backports line to the  /etc/apt/sources.list  file

deb chimaera-backports main contrib non-free


apt update

Install the backported kernel:
apt install -t chimaera-backports linux-image-5.18-(whatever the version is in backports).

Might be best to install the kernel before the firmware.

It appears that this firmware-realtek package may support your RTL8852 card.  From the debian package page showing supported hardware:

* Realtek RTL8852AU Bluetooth config (rtl_bt/rtl8852au_config.bin)
* Realtek RTL8852AU Bluetooth firmware (rtl_bt/rtl8852au_fw.bin)
* Realtek RTL8852A firmware, version v0.9.12.2 (rtw89/rtw8852a_fw.bin)

Board footer

Forum Software