The officially official Devuan Forum!

You are not logged in.

#1 Re: Other Issues » [SOLVED] Upgrade from Jessie to Ascii: apt thinks I'm using "testing" » 2018-08-12 22:33:40

That fixed the problem! And it sort of answers the question of where the information comes from: the repository itself. Thanks!

#2 Re: Other Issues » [SOLVED] Upgrade from Jessie to Ascii: apt thinks I'm using "testing" » 2018-07-30 06:29:57

These are my files:

# cat /etc/apt/sources.list
deb ascii main contrib non-free
deb ascii-security main contrib non-free
deb ascii-updates main contrib non-free

# cat /etc/apt/sources.list.d/backports.list 
deb ascii-backports main contrib non-free

# cat /etc/apt/sources.list.d/virtualbox.list 
deb stretch contrib non-free

If I use apt-cache instead:

# apt-cache policy linux-image-amd64
  Installed: 4.9+80+deb9u5
  Candidate: 4.9+80+deb9u5
  Version table:
     4.16+94~bpo9+1 100
        100 ascii-backports/main amd64 Packages
 *** 4.9+80+deb9u5 500
        500 ascii/main amd64 Packages
        100 /var/lib/dpkg/status
     4.9+80+deb9u4 500
        500 ascii-security/main amd64 Packages

So the information about what are stable and testing must come from somewhere else?

#3 Other Issues » [SOLVED] Upgrade from Jessie to Ascii: apt thinks I'm using "testing" » 2018-07-19 18:26:42

Replies: 4


I (not quite) recently upgraded my system, but it looks like apt is still confused about my base system:

# apt search linux-image-amd64
Sorting... Done                      
Full Text Search... Done
linux-image-amd64/testing,now 4.9+80+deb9u5 amd64 [installed]
  Linux for 64-bit PCs (meta-package)

Here it indicates /testing instead of /stable or even better, /ascii. I am under the impression that the version should come from /etc/os-release but there is no such field in mine:

# cat /etc/os-release
PRETTY_NAME="Devuan GNU/Linux ascii"
NAME="Devuan GNU/Linux"

What is going on here?

#4 Re: Hardware & System Configuration » PostgreSQL 9.6 and pgAdmin4 v1.5 Installation » 2017-06-02 22:12:20

Please use BBCode to format your post, also, this might not be the correct section for that, but someone else should take care of it shortly.

#5 Re: Off-topic » Is Blackbox still today a recommended or outdated WM ? » 2017-06-02 21:53:06

spartrekus wrote:

Compiling didn't work much actually. In member function 'void bt::Image::hgradient(const bt::Color&, const bt::Color&, bool)': error: 'memcpy' was not declared in this scope
       memcpy(p, data, width * sizeof(RGB));

For the record, this is because GCC got stricter over time about including C headers. If you download blackbox_0.70.1-34.debian.tar.xz from a mirror and uncompress it, you'll find a list of patches, among which fix-ftbfs-gcc-4.3.diff which adds the missing #include directives. The problems will only start if the package ends up orphaned.

#6 Re: DIY » automatically disable screensaver during video (incl. web browser) » 2017-05-28 18:05:25

What if I'm playing my favourite albums on audacious while not being in front of the computer? I certainly would like the screensaver to work in that case.

#7 Re: Off-topic » your irc client » 2017-05-28 17:05:27

For a CLI, I'd definitely recommend weechat for the reasons given by pekman, plus sensible defaults (e.g. creates a separate window for each server).

For a GUI, if you only have one computer, Hexchat is definitely the way to go.

If you have several computers on your local network, however, Quassel is worth a try. You can install quassel-core on one machine (for instance a raspberry pi) and use quassel-client from any other machine to access your session. I find it a very interesting alternative to running Hexchat in VNC (or a similar way of keeping a GUI in a remote session).

#8 Re: Hardware & System Configuration » OpenVPN » 2017-04-27 03:44:08

Hi there,

Can you please do two things:

  • Use BBCode to format your posts (it will make for an easier read to other people)

  • Put the contents of your server and client openvpn config files

#9 Re: Intergalactic Communities » SPANISH devuan install guide, instalacion en español » 2017-04-25 02:35:59


I disagree about LVM. I think it's something you never knew you needed until it's too late:

  • With the proper file systems in use (some of them won't shrink...), you can resize your partitions on-the-fly, instead of having to reboot on a live CD

  • Whatever your file system is, you can create a snapshot for backup purposes

  • If you somehow run out of space, you can add a hard drive in your computer and extend your logical volume (and your partitions) transparently

Now it's story time. A few years ago, I only had a laptop, whose hard drive was failing. I needed to copy hundreds of GBs of data to a new HDD, but with a USB2 interface in the middle, it was going to take ages, and prevent me from working. But since I had LVM, I could actually do a live migration, and transfer my whole system onto the new HDD while still working, business as usual.

So I always install using LVM, just in case. The performance hit is, as far as I know, minimal, and there are great long-term advantages.

Also, from what's left of my Spanish, it seems that you're recommending to use only primary partitions because logical partitions are slower. I've never heard of that problem before. There should be no difference whatsoever.

#10 Documentation » Devuan stable and Skylake (and Kaby Lake?) integrated GPU - backports » 2017-04-04 21:38:35

Replies: 0
  • 2017-05-23 – Removed instructions for pinning backports, updated the apt install instructions


The default kernel (3.18) provided with Jessie does not properly support the integrated GPU of recent Intel CPUs. This leads to sub-par performance at best, and crashes at worst (even when doing something as mundane as switching between a VT and X). One solution consists in upgrading to Ascii, but it is not yet supported by the Devuan devs and there are issues at times. Another, more satisfying (IMHO) solution, is to use the jessie-backports branch.

Adding jessie-backports

This is as simple as adding a line in your sources.list, for convenience's sake I'm adding it as a separate file because I like to keep track of what I added to the system's defaults (you can replace auto by your country's code if you like):

# echo 'deb jessie-backports main contrib non-free' \
    > /etc/apt/sources.list.d/jessie-backports.list

Now you can update your list of packages:

# apt update

Installing the newer packages

What we need is a recent kernel and a recent X driver, we install them with the following command:

# apt install -t jessie-backports linux-base linux-image-amd64 xserver-xorg-video-intel

By appending a slash followed by the branch name, we force apt to pull packages from that branch, despite their lower priority.

Now you just need to reboot your system, and enjoy a well-deserved stability and performance.

Notes and drawbacks

Using a newer kernel implies that some packages need to be at the correct version too. On my laptop, I need to install the corresponding firmware package in order to be able to use my Intel wifi card (note that it is in the non-free section):

# apt install -t jessie-backports firmware-iwlwifi

But it can also break some other packages. For instance virtualbox, for which the best solution is to directly use their own repository for jessie (cf the "Debian-based Linux distributions" section at

#11 Re: Documentation » How to make the 'sleep' button work if yours doesn't » 2017-04-04 20:37:34

A slightly more complete solution

First, I commented out /etc/acpi/events/powerbtn-acpi-support:

#event=button[ /]power

This ensures that my laptop doesn't shutdown (or do anything special) when I press on the power button by mistake (it happens...).

Then I wrote a generic handler in /etc/acpi/events/default:

action=/etc/acpi/ %e

This is going to intercept every ACPI event and call a single script with all available arguments. I do not understand the design decision behind the ACPI daemon, with this concept of event files calling scripts, that tend to be so short and to multiply, so I prefer to put all the logic in a single script. Feel free to do it your own way smile

Finally, the file where the magic happens, /etc/acpi/


# log every event in /var/log/messages (can be commented later on)
logger "ACPI event $*"

case "$1" in
        [ $2 = "SBTN" ] && pm-suspend
        [ $2 = "LID" ] && [ $3 = "close" ] && pm-suspend

The actual values on someone else's system could be different, this is why it is convenient to log everything when testing the script.

Also, you do not need to restart your acpid service, you can just reload it (though I don't know whether that makes a real difference):

 # /etc/init.d/acpid reload

Board footer

Forum Software