nvidia-persistenced has no real purpose unless you want to use CUDA.

If you don't need CUDA then you can just delete it, nvidia works fine without it.

There was (is still?) a bug in the code that dates back to 2014 that can lead to it not initialising properly.

See my post dating back to April 2020.

https://dev1galaxy.org/viewtopic.php?pid=20903#p20903

If you have Cinnamon then there an option Menu>Preferences>System Info that will tell you about your system.

Also in a console/terminal you can run neofetch, or for absolutely everything inxi -F (if not already installed both come in packages with the same names).

On my system neofetch provides this:

marjorie@grendel:~$ neofetch
   ..,,;;;::;,..                   marjorie@grendel 
           `':ddd;:,.              ---------------- 
                 `'dPPd:,.         OS: Devuan GNU/Linux 5 (daedalus) x86_64 
                     `:b$$b`.      Host: MS-7C56 1.0 
                        'P$$$d`    Kernel: 6.1.0-11-amd64 
                         .$$$$$`   Uptime: 1 day, 15 hours, 59 mins 
                         ;$$$$$P   Packages: 2892 (dpkg) 
                      .:P$$$$$$`   Shell: bash 5.2.15 
                  .,:b$$$$$$$;'    Resolution: 1920x1200 
             .,:dP$$$$$$$$b:'      DE: Cinnamon 5.6.8 
      .,:;db$$$$$$$$$$Pd'`         WM: Mutter (Muffin) 
 ,db$$$$$$$$$$$$$$b:'`             WM Theme: Blue-mint (Menta) 
:$$$$$$$$$$$$b:'`                  Theme: TraditionalGreen [GTK2/3] 
 `$$$$$bd:''`                      Icons: menta [GTK2/3] 
   `'''`                           Terminal: gnome-terminal 
                                   CPU: AMD Ryzen 5 5600G with Radeon Graphics (12) @ 3.900GHz 
                                   GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series 
                                   Memory: 5729MiB / 13876MiB 

Just surmising that there's no one here who:

1) has chosen Gnome as their DM and
2) has an Nvidia graphics card and
3) has chosen to try Wayland and has got it working successfully.

Bookworm is now on version 12.1 which is usually taken as a sign that initial bugs have been sorted and sysadmins. can safely upgrade.

So I would expect Daedalus, which exactly the same packages as Bookworm in most cases should equally be ready, apart from the installation isos which are still being tested.

Most security updates appear on Daedalus as soon as they appear on Bookworm since Devuan merges Bookworm packages with the very limited number of 'devuan modified' packages. For example the Zenbleed AMD firmware patch appeared very quickly.

For myself, having upgraded my desk PC from Chimaera to Daedalus a few weeks ago without issue I've now upgraded my two others machines, one a mail server and all seems good.

I'm assume that we will be providing a note on how to upgrade as well as how to install from new and how to convert from Debian.
So I thought it might be useful to document my experience and any trip hazards I encountered.

I upgraded just over a week ago, using the same steps as described above.
Where it asked about if I wanted to accept new default config files I chose to keep those I already had.
I was already using the most recent backported 6.1 kernel prior to the upgrade.
A simple replace edit of sources list is however not entirely sufficient as you should add the 'non-free firmware' to each line.
With that change I had no problems in the upgrade as such.

I use unattended-upgrades to install any security package updates daily.
I had to change the line  "o=Devuan,n=chimaera-security" to  "o=Devuan,n=daedalus-security" in /etc/apt/apt.conf.d/50unattended-upgrades.

My motherboard (a MSI B550) use a custom chip to monitor fan speeds in particular.
There is a corresponding kernel module but it was not loaded. I ran

sudo modprobe nct6687.ko

to load it and then sensors could see it.

Grub no longer runs osprober by default. If you have been using it to create grub menu items to boot to alternative OS on your machine you will need to as root restore it in the file /etc/default/grub by un-commenting the line

#GRUB_DISABLE_OS_PROBER=false

and then run update-grub as root.

Also relating to grub the menu on my PC now works with my usb keyboard (it didn't on Chimaera).

rsyslog creates fewer log files, such as /var/log/mail.{info,warn,err}. The messages are still there in /var/log/mail.log.
If you have another program reading any of these, e.g. fail2ban, you will need to get it to read /var/log/mail.log instead.
Similarly /var/log/{messages,debug,daemon.log} are also no longer being updated. Their messages are still there in /var/log/syslog.
All these (and their log-rotated counterparts) can now be removed.
Logrotate itself is working as expected on my PC.

Just for info. I run Cinnamon. After the upgrade Gnome programs (such as Evolution and System Monitor) now duplicate the Max/Min/Close symbols and Title that are in the Window Title Bar in the top line of the program. Nothing fatal but it looks odd.

There are some changes in Bookworm (and hence Daedelus) that don't affect my PC but might others e.g. the packages that set the system clock and reduced accessibility support.
Changes to Bookworm (and by default Daedulus) are covered in the release notes' Chapter 5 Issues to be aware of for bookworm https://www.debian.org/releases/bookwor … on.en.html

From the user Desktop (I use Cinnamon) Synaptic is authorised to open a root graphics session (gtk) through pkexec (which is what pops up the authorisation requester) and behind that is polkit.
Might be worth having a look in /var/log/auth.log to see if it's throwing errors.

On my PC a recent synaptic session was logged in /var/log/auth.log like this:

Jul  3 17:33:18 grendel polkitd(authority=local): Operator of unix-session:1 successfully authenticated as unix-user:marjorie to gain ONE-SHOT authorization for action com.ubuntu.pkexec.synaptic for unix-process:13922:214554138 [/bin/sh /usr/bin/synaptic-pkexec] (owned by unix-user:marjorie)
Jul  3 17:33:18 grendel pkexec: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
Jul  3 17:33:18 grendel pkexec[13925]: marjorie: Executing command [USER=root] [TTY=unknown] [CWD=/home/marjorie] [COMMAND=/usr/sbin/synaptic]

My software stack is:
Host: grendel
Kernel: 6.1.0-0.deb11.7-amd64 x86_64
compiler: gcc v: 10.2.1
Desktop: Cinnamon 4.8.6
tk: GTK 3.24.24
wm: muffin 4.8.1
dm: LightDM 1.26.0
Distro: Devuan GNU/Linux 4 (chimaera)

Hi,

You have posted the output of lshw as an image - the font is tiny and I, at least, find it unreadable, so it's hard to help you further.

This is my output of the same command on my PC posted  with code delimiters.

I'm running a AMD B550 motherboard with a AMD Ryzen 5 5600G with Radeon Graphics.

sudo lshw -C video
  *-display                 
       description: VGA compatible controller
       product: Cezanne
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:30:00.0
       version: c9
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi msix vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:37 memory:d0000000-dfffffff memory:e0000000-e01fffff ioport:e000(size=256) memory:fcb00000-fcb7ffff memory:c0000-dffff

Can you do the same, please?

Also it would be helpful if you can say what you are aiming for in video,

Hi Ralph. Yes, perhaps I'm just not very good at expressing my understanding of this.

The Debian wiki says:

So I suspect that in the default installation the fail2ban configuration assumes that iptables is installed, calls iptables and uses iptables-nft to translate.
Not quite the same thing as going nftables native.

Hence it seems that the simplest solution for the OP is, as you have said, to reinstall iptables.

Wondering if you've ended up with some form of hybrid iptables/nftables fail2ban config.

can you post the contents of your  /etc/fail2ban/jail.conf and /etc/fail2ban/jail.local file?

I used this guide to set up my mail system (with apache2 and postfix/dovecot support)
https://workaround.org/bullseye/firewal … igation-2/
I just needed translate the usual systemd systemctl call to sysvintit service calls.

I have a 5600G running Chimaera.
AMD issued fixes for the integrated graphics in the 5600G in backported kernel 5.15, this also fixed an issue I had with the lack of a driver for the sensor (nct6687) on my MSI B550 motherboard.
I have since attempted to install more recent backport kernels but I found that they have issues. In particular Signal Desktop (from the repositories) and Zoom (from Zoom) often almost froze when starting. It seems to be a graphics issue.
This may well have been fixed in newer kernels than the ones I tried but if you are still having issues having followed Rolfie's advice I suggest you try 5.15 (LTS until at least October 2023).
I still get freeze issues with 5.15 if I try to suspend and resume. Hibernate and resume works fine.

You could try this nftables.conf.

This is based on mine, which works, the only changes are that I've pruned the additional ports I've opened on mine for email, ntp, dns, monitoring.

#!/usr/sbin/nft -f
flush ruleset
table inet filter {
  chain input {
    type filter hook input priority 0; policy drop;

    iifname lo accept
    ct state established,related accept
    tcp dport ssh ct state new accept
    tcp dport http ct state new accept
    tcp dport https ct state new accept
    
     # ICMP: errors, pings
     ip protocol icmp icmp type { echo-request, echo-reply, destination-unreachable, time-exceeded, parameter-problem, router-solicitation, router-advertisement } accept
     # ICMPv6: errors, pings, routing
     ip6 nexthdr icmpv6 counter accept comment "accept all ICMP types"

     # Reject other packets
     ip protocol tcp reject with tcp reset
  }
}

In order to run nvidia video drivers the init will have to insert the nvidia kernel module, done by a modprobe. I have a pc (not my main pc) with an nvidia card and it invariably came up with an insert nvidia kernel module fail message early in the boot process though it would go on and succeed subsequently 'tainting the kernel'.

If you have deleted some 'modprobe nvidia files' you may have disabled this insertion.

When you change the kernel version the nvidia kernel module also needs to be recompiled and to do so requires that you have the matching kernel headers as well as the new kernel itself. If everything is present it does this automatically, however the PC will then need to be rebooted.