The officially official Devuan Forum!

You are not logged in.

#226 Re: News & Announcements » The dev1galaxy.org (almost) No Code of Conduct » 2025-02-23 01:14:11

THE most sensible set of rules for any forum I have ever seen just about perfection.

#227 Re: Installation » [SOLVED] error 500 while upgrading » 2025-02-22 18:47:20

Are you using unstable too, green ? No problemo ?

I use the testing/unstable combination with apt pinning to get the packages from testing first then if needed from the unstable if they have not got there yet. It works well without problems.

#228 Re: Installation » [SOLVED] error 500 while upgrading » 2025-02-22 17:49:22

that solved 2/3 of the problem, still python3-apt didn't update, but I will wait for devs

That depends on a package in the unstable/ceres that does not exist.

root@9600k:~# apt install -s -t unstable  python3-apt

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:

Unsatisfied dependencies:
 python3-apt : Depends: libapt-pkg7.0 (>= 2.9.27+exp1) but it is not installable
Error: Unable to correct problems, you have held broken packages.
root@9600k:~# apt-cache policy libapt-pkg7.0
libapt-pkg7.0:
  Installed: (none)
  Candidate: (none)
  Version table:

#229 Re: Installation » [SOLVED] Does different apt mirrors even work? They didn't work for me » 2025-02-12 23:29:06

Good luck with it, I went through that entire list checking every one and as you have found most are useless for the purpose intended, being a mirror of Devuan.

#230 Re: Installation » Got wayland on gnome working(AMDGPU only, nvidia has problems) » 2025-02-11 16:07:30

For this purpose you can use Gnome auto-starting mechanism.

Indeed and use something like this to ensure you do not get conflicting instances of it started as well.

zeus@9600k:~$ cat bin/pipewire_start.sh 
#!/bin/bash

# Added to start pipewire on login to desktop
# https://dev1galaxy.org/viewtopic.php?id=5867
# was the ~/.xsessionrc -rw-rw-r-- permissions
# now ~/bin/pipewire_start.sh executable permissions
# as bash script loaded from KDE autostart in System Settings

# kill any existing pipewire instance to restore sound
pkill -u "$USER" -fx /usr/bin/pipewire-pulse 1>/dev/null 2>&1
pkill -u "$USER" -fx /usr/bin/wireplumber 1>/dev/null 2>&1
pkill -u "$USER" -fx /usr/bin/pipewire 1>/dev/null 2>&1

exec /usr/bin/pipewire &

# wait for pipewire to start before attempting to start related daemons
while [ "$(pgrep -f /usr/bin/pipewire)" = "" ] ; do
   sleep 1
done

# start wireplumber
exec /usr/bin/wireplumber &

# start pipewire-pulse
exec /usr/bin/pipewire-pulse &

#231 Re: Packaging for Devuan » Repositories and their compatibility Devuan » 2025-02-10 21:40:24

I just gave examples, no guaranteed solutions.

Indeed and I gave the practical in use examples of them to save him some time and further frustration.

#232 Re: Packaging for Devuan » Repositories and their compatibility Devuan » 2025-02-10 20:49:45

Last but not least you might use this example: http://ftp.fau.de/merged using the mirror ftp.fau.de from Germany. Adapt to your needs.

Well if your needs include excalibur or unstable it will not work.

Ign:5 http://ftp.fau.de/merged excalibur InRelease 
Ign:6 http://ftp.fau.de/merged unstable InRelease
Err:7 http://ftp.fau.de/merged excalibur Release
  404  Not Found [IP: 131.188.12.211 80]
Err:8 http://ftp.fau.de/merged unstable Release
  404  Not Found [IP: 131.188.12.211 80]
Error: The repository 'http://ftp.fau.de/merged excalibur Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
Error: The repository 'http://ftp.fau.de/merged unstable Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.

3.) Use http://de.deb.devuan.org/merged as example for Germany.

That however does.

Get:5 http://de.deb.devuan.org/merged excalibur InRelease [40.7 kB]
Get:6 http://de.deb.devuan.org/merged unstable InRelease [47.6 kB]
Get:7 http://de.deb.devuan.org/merged excalibur/main amd64 Packages [9,624 kB]
Get:8 http://de.deb.devuan.org/merged excalibur/main Translation-en [7,207 kB]
Get:9 http://de.deb.devuan.org/merged excalibur/main amd64 Contents (deb) [10.1 MB]
Get:10 http://de.deb.devuan.org/merged excalibur/non-free amd64 Packages [96.4 kB]
Get:11 http://de.deb.devuan.org/merged excalibur/non-free Translation-en [69.0 kB]
Get:12 http://de.deb.devuan.org/merged excalibur/non-free amd64 Contents (deb) [65.1 kB]
Get:13 http://de.deb.devuan.org/merged excalibur/contrib amd64 Packages [51.9 kB]
Get:14 http://de.deb.devuan.org/merged excalibur/contrib Translation-en [49.1 kB]
Get:15 http://de.deb.devuan.org/merged excalibur/contrib amd64 Contents (deb) [158 kB]
Get:16 http://de.deb.devuan.org/merged excalibur/non-free-firmware amd64 Packages [6,936 B]
Get:17 http://de.deb.devuan.org/merged excalibur/non-free-firmware Translation-en [4,641 B]
Get:18 http://de.deb.devuan.org/merged excalibur/non-free-firmware amd64 Contents (deb) [1,020 B]
Get:19 http://de.deb.devuan.org/merged unstable/main amd64 Packages [10.3 MB]

#233 Re: Packaging for Devuan » Repositories and their compatibility Devuan » 2025-02-10 17:24:51

RedGreen925, and how to see the mirror of the country?

Seen posting by someone mentioning the us. for the code when a person was having problem and figured I would try mine, it worked as well as the us. did when I tried it. I went through every mirror in the listing of them they have when I first installed to find good one and quite frankly it is not impressive errors all over the place with them. Ranging from timeouts/404 errors to not having release files or the gpg signing of them.

#234 Re: Packaging for Devuan » Repositories and their compatibility Devuan » 2025-02-10 14:14:56

Upgrading the system trying to migrate....

# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done

That is not the command to upgrade a system from one version to the next, if it is old enough the apt dist-upgrade is to be used or the apt full-upgrade is the new option. An apt upgrade with the old repository enabled should be done just before changing the sources.list to the new version to be used when changing repositories again to do it. For the mirrors problem you are having try ca.deb.devuan.org it seems to work well enough for me the deb.devuan.org arrangement was not the best at all. See if putting your country code in front of it will find a mirror that actually works for you or use mine. Now I check it again you are at the correct first step before the migration the apt upgrade of the old system.

#235 Re: Hardware & System Configuration » Desktop won't wake from sleep [again] » 2025-02-10 00:37:51

There have been suggestions that it is a kernel bug, also a plot between Microsoft and the BIOS makers. My money is on the kernel bug, or some oversight in the installation scripting.

Well if it is then upgrade your kernel you are four versions behind, the -31 kernel just came out yesterday. For the sleep problem no clue I never use it.

#236 Re: Installation » .xinitrc like in wayland ? » 2025-02-10 00:29:07

Are you possibly doing this for running pipewire in Wayland? I couldn't make it work on wayland so.

Not that I use it as it kills off my mouse button mapping I use but it does work in an autostart script I made the .xsessionrc into on my KDE desktop.

zeus@9600k:~$ cat bin/pipewire_start.sh
#!/bin/bash

# Added to start pipewire on login to desktop
# https://dev1galaxy.org/viewtopic.php?id=5867
# was the ~/.xsessionrc -rw-rw-r-- permissions
# now ~/bin/pipewire_start.sh executable permissions
# as bash script loaded from KDE autostart in System Settings

# kill any existing pipewire instance to restore sound
pkill -u "$USER" -fx /usr/bin/pipewire-pulse 1>/dev/null 2>&1
pkill -u "$USER" -fx /usr/bin/wireplumber 1>/dev/null 2>&1
pkill -u "$USER" -fx /usr/bin/pipewire 1>/dev/null 2>&1

exec /usr/bin/pipewire &

# wait for pipewire to start before attempting to start related daemons
while [ "$(pgrep -f /usr/bin/pipewire)" = "" ] ; do
   sleep 1
done

# start wireplumber
exec /usr/bin/wireplumber &

# start pipewire-pulse
exec /usr/bin/pipewire-pulse &

Edit: I think others desktops have a similar feature to do the same.

#237 Re: Packaging for Devuan » LXQt is too old » 2025-02-09 03:30:49

Debian stable never updates packages like that, any OS based on it, which daedalus is,  has the same limitations. If you want newer version then you need to upgrade to excalibur which has the version 32. This is always the main complaint about the Debian stable versions the software is frozen at the time of release not getting updated versions until the next stable release in about two years time they aim for these days.

root@9600k:~# apt policy lxqt
lxqt:
  Installed: (none)
  Candidate: 32+b1
  Version table:
     32+b1 950
        950 http://ca.deb.devuan.org/merged excalibur/main amd64 Packages
        600 http://ca.deb.devuan.org/merged unstable/main amd64 Packages

#238 Re: Hardware & System Configuration » How do I get apt-add-repository to work on Devuan? » 2025-02-07 17:50:02

Users shouldn't need to figure out how to fix it, then fix it, on their own - that's what we have distro developers and maintainers for after all...

In a perfect world this is true, that is not the one we live in. The time has come to use the report bug link included in that file to report the problem and hopefully have it solved by them. Until then you get to do the work around to get done what you need done.

#239 Re: Hardware & System Configuration » How do I get apt-add-repository to work on Devuan? » 2025-02-07 13:25:18

... unfortunately, that is not enough, two issues remain:

1. Case-sensitive comparison of "Devuan" and "devuan"  in /usr/lib/python3/dist-packages/aptsources/distro.py (probably, there should be a .tolower() call at some earlier point), and
2. The script parses the relevant meta-data wrong, concluding that the distribution's "codename" is excalibur ceres rather than just excalibur.

I'm not sure at this point how to fix that robustly; help is appreciated.

Well you seem fine with editing the distro.py, what is the problem with editing the other file need in this the os-release to match what is expected/required of it to work as you need. Make the two changed needed in it and it will work like you need it to do.

#240 Re: Hardware & System Configuration » How do I get apt-add-repository to work on Devuan? » 2025-02-06 22:10:07

And if not - can someone give me an idea regarding how to make the script find an appropriate template?

Sure make a duplicate of the /etc/os-release file with debian listed in it. Actually better off going to debian website and get the base-files package from testing using ar to extract the .deb you can download from the link. The files that are setting the OS version are in that package.

root@9600k:~# cat /etc/os-release 
PRETTY_NAME="Devuan GNU/Linux 6 (excalibur/ceres)"
NAME="Devuan GNU/Linux"
VERSION_ID="6"
VERSION="6 (excalibur/ceres)"
VERSION_CODENAME="excalibur ceres"
ID=devuan
ID_LIKE=debian
HOME_URL="https://www.devuan.org/"
SUPPORT_URL="https://devuan.org/os/community"
BUG_REPORT_URL="https://bugs.devuan.org/"
root@9600k:~# cat /etc/debian_version 
trixie/sid

Actually just did it here.

zeus@9600k:~$ cd Downloads/
zeus@9600k:~/Downloads$ mkdir base_files
zeus@9600k:~/Downloads$ mv base-files_13.6_amd64.deb base_files/
zeus@9600k:~/Downloads$ cd base_files/
zeus@9600k:~/Downloads/base_files$ ar -xv base-files_13.6_amd64.deb 
x - debian-binary
x - control.tar.xz
x - data.tar.xz
zeus@9600k:~/Downloads/base_files$ ll
total 192
72 -rw-rw-r--  1 zeus zeus 72836 Feb  6 17:51 base-files_13.6_amd64.deb
 0 lrwxrwxrwx  1 zeus zeus     7 Nov 22 10:40 bin -> usr/bin/
 4 drwxr-xr-x  2 zeus zeus  4096 Nov 22 10:40 boot/
 4 -rw-r--r--  1 zeus zeus  3196 Feb  6 17:52 control.tar.xz
68 -rw-r--r--  1 zeus zeus 69448 Feb  6 17:52 data.tar.xz
 4 -rw-r--r--  1 zeus zeus     4 Feb  6 17:52 debian-binary
 4 drwxr-xr-x  2 zeus zeus  4096 Nov 22 10:40 dev/
 4 drwxr-xr-x  7 zeus zeus  4096 Nov 22 10:40 etc/
 4 drwxr-xr-x  2 zeus zeus  4096 Nov 22 10:40 home/
 0 lrwxrwxrwx  1 zeus zeus     7 Nov 22 10:40 lib -> usr/lib/
 0 lrwxrwxrwx  1 zeus zeus     9 Nov 22 10:40 lib64 -> usr/lib64/
 4 drwxr-xr-x  2 zeus zeus  4096 Nov 22 10:40 proc/
 4 drwx------  2 zeus zeus  4096 Nov 22 10:40 root/
 4 drwxr-xr-x  2 zeus zeus  4096 Nov 22 10:40 run/
 0 lrwxrwxrwx  1 zeus zeus     8 Nov 22 10:40 sbin -> usr/sbin/
 4 drwxr-xr-x  2 zeus zeus  4096 Nov 22 10:40 sys/
 4 drwxrwxr-x  2 zeus zeus  4096 Nov 22 10:40 tmp/
 4 drwxr-xr-x 10 zeus zeus  4096 Nov 22 10:40 usr/
 4 drwxr-xr-x 11 zeus zeus  4096 Nov 22 10:40 var/
zeus@9600k:~/Downloads/base_files$ ll etc/
total 36
4 -rw-r--r-- 1 zeus zeus   11 Nov 22 10:40 debian_version
4 drwxr-xr-x 2 zeus zeus 4096 Nov 22 10:40 default/
4 drwxr-xr-x 3 zeus zeus 4096 Nov 22 10:40 dpkg/
4 -rw-r--r-- 1 zeus zeus    9 Nov 22 10:40 host.conf
4 -rw-r--r-- 1 zeus zeus   35 Nov 22 10:40 issue
4 -rw-r--r-- 1 zeus zeus   28 Nov 22 10:40 issue.net
0 lrwxrwxrwx 1 zeus zeus   21 Nov 22 10:40 os-release -> ../usr/lib/os-release
4 drwxr-xr-x 2 zeus zeus 4096 Nov 22 10:40 profile.d/
4 drwxr-xr-x 2 zeus zeus 4096 Nov 22 10:40 skel/
4 drwxr-xr-x 2 zeus zeus 4096 Nov 22 10:40 update-motd.d/
zeus@9600k:~/Downloads/base_files$ cat etc/debian_version 
trixie/sid
zeus@9600k:~/Downloads/base_files$ cat etc/os-release 
PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

So there are the two files needed since the Devuan seems to keep debian_version at the Debian version only the os-release needs to be used.  Copy the existing file to a backup and create a Debian version of it so you can easily switch back and forth between them.

root@9600k:~# cp /etc/os-release /etc/os-release.devuan
root@9600k:~# nano /etc/os-release.debian
root@9600k:~# cat /etc/os-release.debian
PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

So there you will have two files in there that can be switched back and forth when needed, like I now have in case this problem crops up in anything I do.

#241 Re: Installation » dual-boot time-zone issues » 2025-01-24 19:48:18

Can you please show me an equivalent command to insert to achieve then the proper time that also withstands rebooting into the respective Operating systems_?

Follow the instructions below to fix the windows time, it make it use the UTC.

https://doc.iosenag.net/windows/utc-clock.html

#242 Re: Hardware & System Configuration » Would double bluetooth, module + mini pci-e, cause bluetooth problems? » 2025-01-23 04:43:22

Other possibility would be to block the 2.1 bluetooth module from terminal using rfkill and some syntax.

Or you could use the system default way of doing it. Create a file in the /etc/modprobe.d/ directory blacklisting the module to prevent it from even loading. No loading of the module no hardware in use to create any possibility of conflict. An example from the only file I found put on the system by the people at Debian.

root@9600k:~# cat /etc/modprobe.d/intel-microcode-blacklist.conf 
# The microcode module attempts to apply a microcode update when
# it autoloads.  This is not always safe, so we block it by default.
blacklist microcode

#243 Re: Hardware & System Configuration » Devuan Daedalus: /i386-pc/normal.mod not found » 2025-01-18 23:34:40

No, I haven't.
Not if I want to install Devuan to a USB stick to use with non-UEFI hardware.

As you have figured out their broken installer will not let you do that, you are stuck with the work around you have used. Just like I finally figured out last year why the damn thing does not respect your choice for the /boot/efi partition you get to set when using manual partitioning as I always do. The damn thing per-selects every efi partition in the system for use as an efi system partition. Unless you go to every single one of them and de-select your choice is ignored depending on its position in the drive listing on that page. If your drive is third in the list then you damn well better make certain that one and two is not selected or those will be used before your choice. If last in list with more drives then every other partition needs to be de-selected before your choice will be used.

#244 Re: Hardware & System Configuration » Devuan Daedalus: /i386-pc/normal.mod not found » 2025-01-18 16:22:19

The problem also crops up with a Debian *.iso.

It appears you have solved the grub problem and as you mention good luck getting Debian people to do anything about it. Their "we care about our users" is nothing but words written down to make them feel better about themselves while doing exactly the opposite. They will ship known broken packages and do nothing to fix them because their policy says not to, unless of course they want to do the opposite then the fix gets made policy be damned. I have seen this hypocrisy in action for decades now.

#245 Re: Hardware & System Configuration » Devuan Daedalus: /i386-pc/normal.mod not found » 2025-01-18 14:20:13

The purpose behind my wanting to install a very small footprint Devuan on small capacity SD/MicroSD cards was to

As they say around here " there is more than one way to skin a cat" no clue why they pick a cat but the gist of it is there is always more than one option. Go to the source Debian, get the netinstall .iso do a minimal install then convert it to Devuan. That is how I got it on the box the Devuan installer will not boot on my machine, actually I just cloned my machine's Debian install and did the conversion. You get to test if the changes made by Devuan are the problem or if the Debian installers are the problem. Or do the cloning I have suggested before.

#246 Re: Hardware & System Configuration » best way to install kernel 6.12 in Daedalus » 2025-01-18 04:29:13

Thanks, is there no upgrade path to Excalibur?

Sure there is like any Debian install do you apt update and apt upgrade to have the latest packages installed. Edit the /etc/apt/sources.list changing to excalibur all the daedalus you see in the lines. Then apt update once more and this time apt full-upgrade. With any luck it goes well and you end up with new operating system the soon to be the next stable in few months. As always when doing something like this backup your important files. And really unless there is some pressing need to have the 6.12 kernel installed the 6.11 in the backports is probably all you need to have.

#247 Re: Hardware & System Configuration » Devuan Daedalus: /i386-pc/normal.mod not found » 2025-01-18 00:39:53

At this point looks like it is the installer itself then with it passing all those tests. An idea since you have grub installed on the disk just clone your install to the stick either while booted into it or booted from an install disk. The install disk is simplest way to do it as it is a straight up rsync command from the mounted install partition to the USB stick partition. As root or with sudo in front of the commands.

mkdir /tmp/oldroot
mkdir /tmp/newroot
mount /dev/sd?? /tmp/oldroot
mount /dev/sd?? /tmp/newroot
rsync -avP /tmp/oldroot/* /tmp/newroot/
blkid                <---- use to get old and newroot drive UUIDs
sed -i "s/oldroot_UUID/newroot_UUID/g" /tmp/newroot/boot/grub/grub.cfg
sed -i "s/oldroot_UUID/newroot_UUID/g" /tmp/newroot/etc/fstab

Now when I do this on EFI system never having done a MBR I have to change the UUID to the new root in the /boot/efi/EFI/debian/grub.cfg. Once that is done I have identical copy of the drive in the machine ready to boot on the drive it was cloned to. It works without fail so many times I have lost count of the times I have used that script I wrote to do this. If there are no other files that grub uses in booting a MBR drive other than those I show it should just boot your present install that was cloned onto the USB disk when put into your SUN machine. If wanting to do it from running machine then the rsync becomes this from my script. If logged into a graphical session with the /home directory in use then there are many other things that need to be excluded in that situation.

rsync -ahPHAXx --delete --exclude={/boot/efi/*,/dev/*,/proc/*,/sys/*,/tmp/*,/run/*,/mnt/*,/media/*,/swapfile,/lost+found} / /tmp/root/

This excludes everything that should not be copied from a running system as it is recreated on every boot unique to that boot. In my script the target for the copy is the /tmp/root/ that gets created by it. Something to try if it turns out the install disk is the problem as a way to get an OS on the USB stick. Now I look over it again if you have any other partitions being used you need to change them UUIDs as well on the USB stick fstab to those new UUIDs as well as copy them over.

#248 Re: Hardware & System Configuration » Devuan Daedalus: /i386-pc/normal.mod not found » 2025-01-17 05:13:26

Loading Linux 6.10.0-10-AMD64 ...

Is from the output you post so it is not the same kernel. That is why I asked that question. If you do not try a memtest the only other thing I can suggest is junk USB controller/driver for the controller. There is no way a fresh install should have a corrupted file system unless something causes that corruption while booting. That comes down to memory, controller or device used to boot with. It seems unlikely a new stick would be useless, one way to test that is use it on another device and see if it boot there.

#249 Re: Hardware & System Configuration » Devuan Daedalus: /i386-pc/normal.mod not found » 2025-01-17 00:57:02

[35.xxx] Ext-fs error (device sda1): __ext4_find_entry:1678: inode #2:
com init: reading lblock 0
[36.xxx] Ext-fs error (device sda1): __ext4_find_entry:1678: inode #13:
com init: reading lblock 0
[36.xxx] Ext-fs error (device sda1): __ext4_find_entry:1678: inode #1443:
com init: reading lblock 0

I find it hard to believe you could have file system errors on first boot of the operating system. That to me suggest corruption during the install. Have you created a memtest86+ boot disk and let it run a few passes to confirm the memory is still in good shape. Also where does the 6.10 kernel come from? That is not the stock kernel on that install disk.

#250 Re: News & Announcements » Merry Christmas » 2025-01-16 20:56:23

"Human derived "celebrations" are useless, inconsequential and delusional and bind us to fantasies and the narratives de jour ( or try to)."

And in the last hundred years or so purely made up bullshit aimed at selling yet more useless trash to be consumed.

Board footer

Forum Software