You are not logged in.
Yes it sucks. In the meantime I have a long document describing all these tweaks.
BTW: yes you have to create that edit unter /etc yourself. To make it work, either reboot or try a:
# udevadm control –reload
# udevadm triggerSystem:
Kernel: 6.12.57+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0 clocksource: tsc
Desktop: Cinnamon v: 6.4.10 tk: GTK v: 3.24.49 wm: Muffin v: 6.4.1 vt: 7 dm: LightDM v: 1.32.0
Distro: Devuan GNU/Linux 6 (excalibur)The upgrade to Excalibur removed the logviewer I used under Daedalus, the gnome-system-log package. Somebody told me that gnome-logs is the replacement. But this package only takes care for the systemd journal now.
My solution: install mate-utils. That package amongst other stuff contains the mate-system-log.
To make it work also for the syslog and dmesg I had to create a new menu entry. Main topic is the command:
pkexec /usr/bin/mate-system-logAs icon I selected /usr/share/icons/hicolor/48x48/apps/mate-system-log.png which came with the package.
Also I needed to supply a policy action for policykit. I had one in my backups from previously using Mate as desktop. To be stored in /usr/share/polkit-1/actions as org.mate.mate-system-log.policy. Contents:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE policyconfig PUBLIC
"-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
"http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">
<policyconfig>
<vendor>Mate-System-Log</vendor>
<vendor_url></vendor_url>
<icon_name>mate-system-log</icon_name>
<action id="org.mate-system-log.pkexec">
<description>Run mate-system-log as root</description>
<message>Authentication is required to run mate-terminal as root.</message>
<defaults>
<allow_any>no</allow_any>
<allow_inactive>auth_admin</allow_inactive>
<allow_active>auth_admin</allow_active>
</defaults>
<annotate key="org.freedesktop.policykit.exec.path">/usr/bin/mate-system-log</annotate>
<annotate key="org.freedesktop.policykit.exec.allow_gui">true</annotate>
</action>Hi there, I guess the drive that isn't automounted is ext(x)-formatted, isn't it? Well, there is a new quirk in the udev rules from corporate actors inhibiting automount for ext(x)-partitions and others coming in with Trixie. Found that on the German Debian forum.
Check out for a file /usr/lib/udev/rules.d/64-ext4.rules, it reads:
# SPDX-License-Identifier: GPL-2.0-or-later
#
# Copyright (C) 2023 Oracle. All rights reserved.
# Author: Darrick J. Wong <djwong@kernel.org>
#
# Don't let udisks automount ext4 filesystems without even asking a user.
# This doesn't eliminate filesystems as an attack surface; it only prevents
# evil maid attacks when all sessions are locked.
#
# According to http://storaged.org/doc/udisks2-api/latest/udisks.8.html,
# supplying UDISKS_AUTO=0 here changes the HintAuto property of the block
# device abstraction to mean "do not automatically start" (e.g. mount).
SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="ext2|ext3|ext4|ext4dev|jbd", ENV{UDISKS_AUTO}="0"To override this rule you either change the "0" into a "1" with the risk that your change is overwritten from another update, or better write your own rule and save it to /etc/udev/rules.d/65-ext4.rules:
# extX-Dateisysteme automatisch mounten
SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="ext2|ext3|ext4|ext4dev|jbd", ENV{UDISKS_AUTO}="1" HTH
My box is an upgraded Daedalus with Cinnamon as DE. I use the original script as posted in answer #8. The system is upgraded to Excalibur and works fine. I got sound@cinnamon.org as mixer, and no issues. works for me in my setup. Volume stays at the last setting.
Sorry, can't help you.
On my ToDo list I still have the task to switch to the script as shown in the Excalibur release notes.
Ok, I am on conventional DSL here in Frankonia. No glas fibre yet directly to my home. They are working on that.
I use the standard Telekom DNS service and I at least currently have no issues with deb.devuan.org. And I have a Fritzbox bought on my own, no Speedport from Telekom any more.
Strangely enough, I am also from Germany and have the Deutsche Telekom as ISP. I know the issues you described in your inital post, had them a few times a while ago, but recently no issues at all. And I use the Telekom as DNS provider. Currently no issues, works flawlessly (somewhere in a village in the middle of Frankonia).
Known problem, issues with DNS resolution by the internet providers. There are various threads here in the forum about this issue. They do not like the deb.devuan.org which is not a single IP but a so called round robin of various servers (used for load distribution). You can't do anything really. Only thing to try is to use a different DNS resolver.
And I would skip the "de" and just use http://deb.devuan.org/.....
With Excalibur/Trixie a new kernel feature has been introduced. Some additional messages are coloured now.
Look if bootlogd is installed, if not install. Then you get a subset of what is logged during boot in /var/log/boot.
Just upgraded my workstation to Excalibur. Took 20mins, so far working perfectly.
Thanks to the Devuan team.
hddtemp is obsolete, depracated.
it gives me this error: talion is not in the sudoers file how do i fix that it?
During installation you have the choice: you either allow root login and enter a root password, then you have to use a root console for admin tasks. My preferred method. Or you don't do that then you automatically are assigned to the sudoers group and you have to use a sudo before each admin command. Don't try to mix.
Now you're talking about the 'card' drives that don't even use SATA connectors. Power usage doesn't seem to be linear there, either.
Generally spoken, there is not much difference between SATA SSDs in the typical 2,5" housing and these typical 2280 M2 cards as used for NVME drives. The power consumption on all of them are load frequency dependent.
And as a matter of fact, SSDs are in average of much lower power consumption as the spinning rust drives. Don't look at the rating, this is a max consumption value a drive rarely takes in in very extreme situations (and gets very hot and slows down to protect).
The power draw from any SSD is very much depending on the write/read load. The figures given are for full load at full speed plus a bit overhead. The average consumption will be very much lower.
But to be considered: PCIe3 consumes less than PCIe4, less than PCIe5.
The NVidea problem is their support for older hardware. They stop providing drivers for older cards and do not adapt them for newer kernels any more. In the last 10 years AMD support has moved into the kernel and is very reliable, also for older cards.
Everybody experienced would be very pleased if you could put any console output between code tags, including the command you have used. To write code tags use the button that is labelled code above the editing window, and paste the text between the starter and the end tag. Makes console outputs look like in a console, much more readable and more friendly for the contributors.
I will do this for you as an example by copying your last output and! adding line numbers like a reasonable text editor can do.
cat /etc/apt/sources.list
1 #deb cdrom:[Devuan GNU/Linux 6.0.0-rc1 excalibur amd64 - netinstall 20250913]/ excalibur contrib main non-free-firmware
2
3 deb http://deb.devuan.org/merged excalibur main contrib non-free non-free-firmware
4 deb http://deb.devuan.org/merged excalibur-security main contrib non-free non-free-firmware
5 deb http://deb.devuan.org/merged excalibur-updates main contrib non-free non-free-firmware
6
7 #deb http://deb.devuan.org/merged excalibur-backports main contrib non-free non-free-firmware
8
9 # excalibur-updates, to get updates before a point release is made;
10 # see https://www.debian.org/doc/manuals/debi … _backports
11 deb http://deb.devuan.org/merged excalibur-updates main non-free-firmware
12 deb-src http://deb.devuan.org/merged excalibur-updates main non-free-firmware
13
14 # This system was installed using removable media other than
15 # CD/DVD/BD (e.g. USB stick, SD card, ISO image file).
16 # The matching "deb cdrom" entries were disabled at the end
17 # of the installation process.
18 # For information about how to configure apt package sources,
19 # see the sources.list(5) manual.Your sources.list contains 19 lines of text.
Line 5 and line 11 are (partial) duplicates. Line 11 causes the error messages you are getting.
My advise: get rid of every past line 8 and try again. Attention: there has to be an empty line at the end of the file.
It would make sense if the OP would post a
cat /etc/apt/sources.listDon't get confused by tux_99's reply. What I gave you is a correct /etc/apt/sources.list for Excalibur. The traditional format.
Now what tux_99 has posted is the new DEB822 format replacing the sources.list in the future. For the time being I would recommend to stay with the traditional format.
A well defined sources.list looks like this.
No deb-src because this is only needed if you do coding and compiling code.
And no proposed-updates, not required for the normal user, and slightly risky, packages are coming in the release before testing is fully done. Only useful in very specific cases.
Backports is added but commented out. Only useful in very specific cases.
deb http://deb.devuan.org/merged excalibur main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged excalibur-security main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged excalibur-updates main contrib non-free non-free-firmware
#deb http://deb.devuan.org/merged excalibur-backports main contrib non-free non-free-firmwareAll my upgrades on my laptop and in my VMs, I am not missing any logs. Same with a new installation from the released netinstall in a VM. Maybe you used one of the testing editions, and there is something in the back of my mind that rsyslog was missed out on one or two of them.
Hello Steve, welcome in the galaxy.
Please have a close look at the spelling of excalibur, or have a look at the link present here on top of the page to Devuan.org.
goats advice to use pkgmaster is no good.
On the top of the forum is a link to the Devuan page. Its worth following the link. Here is something to read:
https://www.devuan.org/os/packages
A full blown correct sources entry should look like this:
deb http://deb.devuan.org/merged excalibur main contrib non-free non-free-firmwareBTW: to use
suto become root is also outdated.
You need to use
su - or the path setting will be incorrect.
Updated my travelling laptop to Excalibur a few days ago. The upgrade went well what Devuan is concerned, have got some BIOS-related UEFI-hickup. Sources have been modernized today.
The original sources.list reads like this:
deb http://deb.devuan.org/merged excalibur main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged excalibur-security main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged/ excalibur-updates main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged/ excalibur-backports main contrib non-free non-free-firmwareNo issues neither with apt nor apt-get.
Modernize generated two files in /etc/apt/sources.list.d with the following contents:
devuan.sources:
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur-security
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur-updates
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
devuan-backports.sources:
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur-backports
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpgBackports was missing the key, I just added the line from devuan.sources. As well apt as apt get work:
# apt update
OK:1 http://deb.devuan.org/merged excalibur InRelease
OK:2 http://deb.devuan.org/merged excalibur-security InRelease
OK:3 http://deb.devuan.org/merged excalibur-updates InRelease
OK:4 http://deb.devuan.org/merged excalibur-backports InRelease
Alle Pakete sind aktuell.
# apt-get update
OK:1 http://deb.devuan.org/merged excalibur InRelease
OK:2 http://deb.devuan.org/merged excalibur-security InRelease
OK:3 http://deb.devuan.org/merged excalibur-updates InRelease
OK:4 http://deb.devuan.org/merged excalibur-backports InRelease
Paketlisten werden gelesen… FertigThen I moved everything into one block in one file (devuan.sources) and set devuan-backports.sources to Enabled: no:
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur excalibur-security excalibur-updates excalibur-backports
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Same result with apt and apt.get as before, works fine.
I use geany to edit the files. And I avoid de.deb.devuan.org. I just use the general round robin. There were some problems a while ago, recently I haven't seen any issues.
# ls -l /etc/apt/sources.list*
-rw-r--r-- 1 root root 0 14. Sep 2022 /etc/apt/sources.list~
-rw-r--r-- 1 root root 545 6. Nov 18:58 /etc/apt/sources.list.bak
/etc/apt/sources.list.d:
insgesamt 8
-rw-rw-r-- 1 root root 237 8. Nov 17:50 devuan-backports.sources
-rw-rw-r-- 1 root root 731 8. Nov 17:50 devuan.sourcesI can't complain.
Look around in the "Devuan Deriviates" section. Maybe there is a deriviate using IceWM already.
... and AMD has long time support due to kernel drivers. Drivers do not drop out that fast as with NVidea.
Please read the Release Notes.