The officially official Devuan Forum!

You are not logged in.

#51 Re: Installation » "target_home" dir after installation? » 2023-01-18 11:09:01

AFAIK (I've only used it as a live disk to test compatibility with my PC and then switched to using the full installer as I need something more complicated)  the live installer just does a basic job of reproducing the configuration that comes on the live iso. It installs everything to a single partition on the target disk, complete with / and /home, Not sure what it does about swap.
If you have an existing /home on another disk it will know nothing about that. If /home is on another partition but on the same disk it will remove it when if formats the disk.
After installing you can go into the new installation and remap its /etc/fstab to point /home to your existing /home partition.

#52 Re: Installation » [SOLVED] gparted missing » 2023-01-17 23:21:52

dcolburn wrote:

It should be trivial to just initiate an incremental backup when I make a substantive change - otherwise automate a routine incremental backup every night.

Thanks!

Be aware that Deja Dup is only intended to do an incremental back up of files in your /home directory.

e.g.. see https://gitlab.gnome.org/World/deja-dup:

"Déjà Dup focuses on ease of use and personal, accidental data loss. If you need a full system backup or an archival program, you may prefer other backup apps."

While in theory you could backup your entire system if you ran it as root that is not reliable as the backup may end up inconsistent - generally you should only backup your system files offline or if you have the tools to snapshot your mounted system.

#53 Re: Installation » [SOLVED] gparted missing » 2023-01-17 23:04:22

dcolburn wrote:

gparted isn't present in the menu, doesn't respond in root (prefixed or not with 'sudo'), and isn't present in Synaptic Package Manager.

(I ran 'reload' in SPM - in case it was a damaged repo list.)

Has it been removed or replaced, or do I just have yet-another bizarre local anomaly?

Devuan chimaera, xfce 4.16.0

I think its optional. Although its in the main repository, lots of useful utilities are optional. If it's there you should find it be searching for it in synaptic. If you find it just install it.

When I searched for it in synaptic history (file/history) I see that I installed it myself.

#54 Re: Other Issues » (Unattended-upgrades) Apparently I'm running Debian... Again. » 2023-01-17 21:30:36

steve_v wrote:

That's kinda my point WRT using ${distro_codename} instead of a hardcoded release. That's how Debian does it, and it allows unattended-upgrades to track the new release after a dist-upgrade with no manual changes to its configuration at all.

Ditto for the devuan-security line, I see no reason not to use ${distro_codename} there either, unless to create more packaging work.

Surely that would only make sense if I wanted to upgrade immediately 'testing' became 'stable'?
I'm far too conservative to want to do that - I'd rather wait a decent interval and let other find out for me what problems are surfaced.
Note the latest fubar with Windows ( https://www.theregister.com/2023/01/16/ … e_scripts/).
This is also why I only update security patches immediately.

#55 Re: Other Issues » (Unattended-upgrades) Apparently I'm running Debian... Again. » 2023-01-17 11:23:04

dice wrote:

I have never used unattended upgrades. Could the devuan 3.1 release notes shed a bit more light on this issue?

I use unattended upgrades to install security upgrades on both my main PC and my mail server.

I didn't find it that difficult to get working.

1. Install package

2. Consult man page

man unattended-upgrades

read the lines

CONFIGURATION
       The  configuration  is  done  via  the  apt  configuration  mechanism.  The  default  configuration  file can be found at
       /etc/apt/apt.conf.d/50unattended-upgrades

3. Open (as root/sudo) the file  /etc/apt/apt.conf.d/50unattended-upgrades and configure.
The file is largely self-documenting.

This includes changing the default distribution and package.

This is my fixed/working version. I suspect its unchanged (apart from changing ascii to chimaera in line 43) since I used ascii.

// Unattended-Upgrade::Origins-Pattern controls which packages are
// upgraded.
//
// Lines below have the format format is "keyword=value,...".  A
// package will be upgraded only if the values in its metadata match
// all the supplied keywords in a line.  (In other words, omitted
// keywords are wild cards.) The keywords originate from the Release
// file, but several aliases are accepted.  The accepted keywords are:
//   a,archive,suite (eg, "stable")
//   c,component     (eg, "main", "contrib", "non-free")
//   l,label         (eg, "Devuan", "Devuan-Security")
//   o,origin        (eg, "Devuan")
//   n,codename      (eg, "ascii", "ascii-updates")
//     site          (eg, "deb.devuan.org")
// The available values on the system are printed by the command
// "apt-cache policy", and can be debugged by running
// "unattended-upgrades -d" and looking at the log file.
//
// Within lines unattended-upgrades allows 2 macros whose values are
// derived from /etc/debian_version:
//   ${distro_id}            Installed origin.
//   ${distro_codename}      Installed codename (eg, "ascii")
Unattended-Upgrade::Origins-Pattern {
        // Codename based matching:
        // This will follow the migration of a release through different
        // archives (e.g. from testing to stable and later oldstable).
//      "o=Devuan,n=ascii";
//      "o=Devuan,n=ascii-updates";
//      "o=Devuan,n=ascii-proposed-updates";

        // Archive or Suite based matching:
        // Note that this will silently match a different release after
        // migration to the specified archive (e.g. testing becomes the
        // new stable).
//      "o=Devuan,a=stable";
//      "o=Devuan,a=stable-updates";
//      "o=Devuan,a=proposed-updates";

        // Activate *-security by default.
        // This will make it easier for Devuan derivatives.
        // "a=*-security";
	//
	"o=Devuan,n=chimaera-security";
};

// List of packages to not update (regexp are supported)
Unattended-Upgrade::Package-Blacklist {
//	"vim";
//	"libc6";
//	"libc6-dev";
//	"libc6-i686";
};

// This option allows you to control if on a unclean dpkg exit
// unattended-upgrades will automatically run 
//   dpkg --force-confold --configure -a
// The default is true, to ensure updates keep getting installed
//Unattended-Upgrade::AutoFixInterruptedDpkg "false";

// Split the upgrade into the smallest possible chunks so that
// they can be interrupted with SIGUSR1. This makes the upgrade
// a bit slower but it has the benefit that shutdown while a upgrade
// is running is possible (with a small delay)
//Unattended-Upgrade::MinimalSteps "true";

// Install all unattended-upgrades when the machine is shutting down
// instead of doing it in the background while the machine is running
// This will (obviously) make shutdown slower
//Unattended-Upgrade::InstallOnShutdown "true";

// Send email to this address for problems or packages upgrades
// If empty or unset then no email is sent, make sure that you
// have a working mail setup on your system. A package that provides
// 'mailx' must be installed. E.g. "user@example.com"
Unattended-Upgrade::Mail "root";

// Set this value to "true" to get emails only on errors. Default
// is to always send a mail if Unattended-Upgrade::Mail is set
//Unattended-Upgrade::MailOnlyOnError "true";

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies "true";

// Automatically reboot *WITHOUT CONFIRMATION* if
//  the file /var/run/reboot-required is found after the upgrade 
//Unattended-Upgrade::Automatic-Reboot "false";

// Automatically reboot even if there are users currently logged in.
//Unattended-Upgrade::Automatic-Reboot-WithUsers "true";

// If automatic reboot is enabled and needed, reboot at the specific
// time instead of immediately
//  Default: "now"
//Unattended-Upgrade::Automatic-Reboot-Time "02:00";

// Use apt bandwidth limit feature, this example limits the download
// speed to 70kb/sec
//Acquire::http::Dl-Limit "70";

// Enable logging to syslog. Default is False
Unattended-Upgrade::SyslogEnable "true";

// Specify syslog facility. Default is daemon
// Unattended-Upgrade::SyslogFacility "daemon";

It might be nicer if the Chimaera version included Devuan/Chimaera/security defaults (my line 43):

       "o=Devuan,n=chimaera-security"; 

But not sure its really worth pestering our admins to do this every time Debian change it upstream as there are other options in the config you might want to change anyway ( I don't do auto reboots or install non-security ungrades, I do ask it to email me when upgrades happen) though a mention in the release notes might help as at the very least you do need to change that line, or it's equivalent, to include 'chimaera' when upgrading.

I run apt both on my mail server and my main PC via 0anacron and apt-compat in /etc/cron.daily so it should check for updates daily. For a server you could just call it directly from cron, however as I often hibernate rather than reboot my main PC overnight I also get it to check for updates on resume (cron doesn't run jobs called when the computer is turned off at the designated time).

#56 Re: Hardware & System Configuration » Server lost changes and partially reverted » 2023-01-06 22:48:19

Backing up.

To backup my /home partition I would use something that supports incremental back where it's possible to restore individual files or directories. I use Déjà Dup which is just a wrapper around duplicity.

To backup my \root partition I use fsarchiver which does a whole partition backup. Although it is possible to backup a live partition (using the -A flag) it's much safer to unmount it and backup from another system (e.g one on a usb stick). If you the have LVM partitions (which I do, on top of RAID1) you can snapshot your live root partition.

#57 Re: Hardware & System Configuration » Server lost changes and partially reverted » 2023-01-06 13:53:39

I always understood 'fake' RAID/bios RAID doesn't work with Linux.

I do use mdadm RAID1 on my desktop machine, but not on my html/email server and it can help to cover disk failure and some forms of corruption but I would strongly recommend that you do an actual backup of your /root as well as your /home directories regularly to somewhere else. You may choose different solutions/frequencies for /root and /home.

However as you had finally got your nginx htmp server working that is when I would have made a backup of both.

The brtfs filesystem allows for snapshoting of your live system. You can also snapshot a ext4 system if it's inside a LVM2. There are also offline backup solutions where you boot from an alternative root system e.g. from a recovery disk on a usb drive and then run a backup of your unmounted filesystem from that.

#58 Re: Hardware & System Configuration » [SOLVED] Good nginx ssl instructions » 2023-01-03 17:35:55

Yes, me too.

I know that is from my apache/postfix guide but I think the steps for this stage (enabling https) will be very similar for nginx and it may prompt you to check the stages:
https://workaround.org/bullseye/tls-enc … rtificate/

#59 Re: Hardware & System Configuration » [SOLVED] Good nginx ssl instructions » 2023-01-03 17:09:16

Hi, yes that what I hoped to see: seems OK. Just wanted to check.
Needless to say I'm in the UK, age 71, wake at 7am GMT, so we're all time-shifted.
I went through a similar website setup process myself a few years ago (except I was also setting up a mail server), and using apache, but closely following the guide that I used meant it was relatively painless.
Still can't 'see' your website.

#60 Re: Hardware & System Configuration » [SOLVED] Good nginx ssl instructions » 2023-01-03 15:22:55

Just for clarity. You are doing lots of tests in /etc/nginx/sites-available.
Have you enabled the sites? i.e created links (http and https) in /etc/nginx/sites-enabled to the active website in site-available.

NB. Ralph will know this all better than me as he has nginx and I have apache2, but I assume this part works much the same. The simplest way to set these things up is to just follow a good step-by-step guide.

#61 Re: Hardware & System Configuration » [SOLVED] Good nginx ssl instructions » 2023-01-01 22:22:45

If I open my web browser on http://66.172.90.106 then, if I click through the warning about https: not enabled I see the webpage banner "Welcome to Realupnow.com!". So nginx is serving the index webpage to the internet.

However if I lookup realupdown,com with dig I still don't get the A record:

marjorie@grendel:~$ dig realupdown.com

; <<>> DiG 9.16.33-Debian <<>> realupdown.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3657
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;realupdown.com.			IN	A

;; AUTHORITY SECTION:
com.			599	IN	SOA	a.gtld-servers.net. nstld.verisign-grs.com. 1672611035 1800 900 604800 86400

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Jan 01 22:16:02 GMT 2023
;; MSG SIZE  rcvd: 116

It may just be a propagation issue. Or it maybe a real issue with the DNS. I do note that the servers in the AUTHORITY section have changed.

Also despite the apparent success of certbot https is not enabled yet.

#62 Re: Hardware & System Configuration » [SOLVED] Good nginx ssl instructions » 2023-01-01 11:16:27

I can now see an A record for unboundtest.com (165.227.59.74, which is on Digital Ocean).
I can't see one for realupnow.com.

Have you got a static IP or just a dynamic one assigned by your ISP? Dynamic IPs periodically change.
By default most ISPs only provide dynamic IPs for domestic users. Business users, who also pay more, usually get a static IP.
And of course you can also run a web and/or mail server in the cloud (such as Digital Ocean).
To run a website accessible on the internet you really need a static IP.

You can check that your ngingx website is running OK by opening it in your browser on its internal (NAT, IP4) network address e.g. http://192.168.50.4 .
I assume there is already a correctly configured index.html in ngingx : on my apache installation there is one there by default that says "Apache2 Debian Default Page: It works!".
I also assume you have opened any firewall on your server for ports 80 and 443.
For now you may need to disable or bypass any automatic redirection from http to https as https won't work until you have a certificate.
My recollection of how my apache server works is that I have automatic redirection set up except for a bypass for letsencrypts certbot, as that obviously needs to see a http site when doing a challenge.

You can then check that it works using its web IP e.g. http://66.172.90.106 (if that's your assigned IP for realudown.com). This doesn't require a DNS lookup.
At this stage you will need to have opened your router firewall for ports 80 and 443 for this to work. On my router I have 'virtual servers' enabled to direct any incoming traffic on posts 80 or 443 to tunnel through to my webserver.

And then you can check that the DNS lookup works OK http://realupnow.com ....

#63 Re: Hardware & System Configuration » [SOLVED] Good nginx ssl instructions » 2022-12-31 23:55:41

Doesn't look like you've set up an A record, or the record hasn't been propagated yet.

digging your website:

; marjorie@grendel:~$ dig realupnow.com

<<>> DiG 9.16.33-Debian <<>> realupnow.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56743
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 0
;; QUESTION SECTION:
;realupnow.com.			IN	A

;; AUTHORITY SECTION:
realupnow.com.		3599	IN	SOA	dns1.registrar-servers.com. hostmaster.registrar-servers.com. 1664668104 43200 3600 604800 3601

;; Query time: 71 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Dec 31 23:48:36 GMT 2022
;; MSG SIZE  rcvd: 112

While if I dig mine:

; <<>> DiG 9.16.33-Debian <<>> meeble.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62974
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;meeble.net.			IN	A

;; ANSWER SECTION:
meeble.net.		2399	IN	A	88.97.31.244

;; Query time: 99 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Dec 31 23:49:04 GMT 2022
;; MSG SIZE  rcvd: 55

#64 Re: Desktop and Multimedia » Chromium asking for 'keyring password'? » 2022-12-27 14:12:41

Head_on_a_Stick wrote:
Marjorie wrote:

can't recall having any keyring issues

Chromium tries to detect the desktop and it will only show that message if it thinks it's running in GNOME. If you're running Xfce I think it will fall back to basic for the --password-store option, which doesn't need the keyring.

FWIW I use Cinnamon (=gnome lite).

#65 Re: Desktop and Multimedia » Chromium asking for 'keyring password'? » 2022-12-27 14:04:16

Altoid wrote:

Hello:

I run Devuan Beowulf on a backported kernel [5.10]:

So ...
Just what #$%&'¿ does Chromium want with a keyring PW?

Any idea  as to what is going on?

Thanks in advance.

A.

I use Chimaera on a 5.15 kernel. Beowulf is a bit old now.

I've got ungoogled-chromium (also 108) installed as a backup for firefox-esr in case it can't render a website (though these days I never seem to need it) and can't recall having any keyring issues.

Is anyone else, who uses the devuan repository chromium on Beowulf, seeing this?

#66 Re: Desktop and Multimedia » [SOLVED] GUI mixer in Daedalus » 2022-12-16 17:05:31

By default Cinnamon uses the applet sound@cinnamon.org.
You'd install it into the panel by right clicking on the panel and choosing Applets then your choice of applet.
By default Cinnamon also uses pulseaudio as middleware on top of alsa.
I'm unclear if the sound applet depends on pulseaudio being installed - as it's not something I've tried to change.

#67 Re: Installation » [SOLVED] Is it possible to exclude a mirror? » 2022-12-07 11:28:00

You could just chose one mirror, from those in the roundrobin, that works for you.

The main purpose of the roundrobin is to spread the load, but if you have a specific need then one person fixing their choice of mirror won't be disruptive.
If lots of you were to need a particular mirror as it was the only one that serves ARM packages then that might be more of a problem, but I don't expect there are that many with that need and I gather than most mirrors would work ok.

I've done this in the past (as I wanted a https connection). It used to work so long as I wasn't trying to download when that site was offline for maintenance, maybe for updating the mirror.

#68 Re: Installation » [SOLVED] linux-image-6.* / Chimaera » 2022-11-22 22:24:52

Agree, the CPU on my 5600G worked fine with 5.10, the issues I had were in support for the integrated GPU. This was improved with new GPU commits from AMD in 5:15.
I also have a nct6687-isa-0a20 fans sensor on the MSI AMD B550 MPG Gaming Plus Motherboard that I needed the 5.15 kernel headers so I could compile in its kernel module.
On my system upgrading to kernels 5.18 and 5.19 caused graphical glitching with Signal Desktop and Zoom and issues with getting reliable hibernation.

#69 Re: Installation » [SOLVED] linux-image-6.* / Chimaera » 2022-11-22 17:28:30

Yes, linux-image-6.0.0.0 and corresponding headers are now available in Chimaera backports.

Do you have newer hardware that actually needs anything later than the stable 5.10 kernel (which is still being updated with security patches)?

In my case I did update from 5.10 to 5.15 when I updated my processor and motherboard to ones that weren't fully covered by 5.10  (AMD 5600G and a new sensors chip on my B550 motherboard) however I found that subsequent kernels 5.18 and 5.19 contained regressions which caused certain programs I use to glitch so I reverted to 5.15.

I might try 6.0 but it's quite possible the regressions are still there and I'll have to revert.

#70 Re: Desktop and Multimedia » Can you suggest some tips and tricks for speed up Devuan? » 2022-11-17 11:55:52

Devarch wrote:

To speed up devuan I've disabled anacron. Sometimes it slows down shutdown.

This strikes me as odd.

Anacron is useful on personal PCs that  you turn on and off so that scheduled cron jobs run just after startup (you can set a possibly randomised delay). This avoids  cron jobs not being run because your machine would be turned off at the time set for the cron job. On an alway-on server you would typically run such jobs in the small hours.

The jobs run by anacron are those in /etc/cron.hourly/, /etc/cron.daily/, /etc/cron.weekly/ and /etc/cron.monthly. If a job is unnecessary for you then remove it from the respective /etc/cron.*. If you think it's using too much resource consider doing it less frequently.

As I mostly hibernate rather than shut down my personal PC overnight I've also set it up so that it also checks if anacron needs to run any daily, weekly or monthly when its woken.

I can't think of any reason why anacron should delay shutdown.

#71 Re: Other Issues » [SOLVED] Zoom in Devuan » 2022-10-14 15:00:27

Just to update: the issue I was having running Zoom and Signal Desktop on my AMD 5600G with Chimaera and a backported 5:18 kernel, seems to have been addressed and solved in kernel 5.19.

Correction: it seems it still isn't fixed in 5.19, at least if I'd had the system running for a while/been hibernated. So have reverted to kernel 5:15 again.

#72 Re: Hardware & System Configuration » [SOLVED] TP-Link AX3000 (Archer TX3000E) PCIe WiFi card not working on Refracta » 2022-10-10 16:48:23

Having checked your AX210 is a wi-fi 6E card, while my AX200 is only wi-fi 6.

The AX210 is only supported by linux kernels >= 5.10, i.e. the standard Chimaera kernel.

https://wireless.wiki.kernel.org/en/use … rs/iwlwifi

Nevertheless, even though you say its Beowulf based Linux refracta 5.10.0-0.deb10.16-amd64 is presumably a 5:10 kernel.

#73 Re: Hardware & System Configuration » [SOLVED] TP-Link AX3000 (Archer TX3000E) PCIe WiFi card not working on Refracta » 2022-10-10 09:54:55

Which iwlwifi and kernel versions are you using? This is quite a new wifi card compared to beowulf. You may need a backported kernel as well or even an upgrade to Chimaera.

I have a working AX200 card (earlier than yours, which is AX210) on  Chimaera. My ifwlwifi is version 20210315-3.

This is from my dmesg:

dmesg |grep iwlwifi
[    5.797902] iwlwifi 0000:21:00.0: firmware: failed to load iwlwifi-cc-a0-66.ucode (-2)
[    5.797969] iwlwifi 0000:21:00.0: Direct firmware load for iwlwifi-cc-a0-66.ucode failed with error -2
[    5.797979] iwlwifi 0000:21:00.0: firmware: failed to load iwlwifi-cc-a0-65.ucode (-2)
[    5.798003] iwlwifi 0000:21:00.0: Direct firmware load for iwlwifi-cc-a0-65.ucode failed with error -2
[    5.798010] iwlwifi 0000:21:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2)
[    5.798034] iwlwifi 0000:21:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2
[    5.798041] iwlwifi 0000:21:00.0: firmware: failed to load iwlwifi-cc-a0-63.ucode (-2)
[    5.798064] iwlwifi 0000:21:00.0: Direct firmware load for iwlwifi-cc-a0-63.ucode failed with error -2
[    5.801899] iwlwifi 0000:21:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-62.ucode
[    5.801904] iwlwifi 0000:21:00.0: api flags index 2 larger than supported by driver
[    5.801910] iwlwifi 0000:21:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[    5.802068] iwlwifi 0000:21:00.0: loaded firmware version 62.49eeb572.0 cc-a0-62.ucode op_mode iwlmvm
[    5.802081] iwlwifi 0000:21:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    5.870642] iwlwifi 0000:21:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    6.000186] iwlwifi 0000:21:00.0: Detected RF HR B3, rfid=0x10a100
[    6.065031] iwlwifi 0000:21:00.0: base HW address: dc:21:48:57:1b:5b
[12516.990241] (NULL device *): firmware: direct-loading firmware iwlwifi-cc-a0-62.ucode

I note that I finally get my slightly older card running on iwlwifi-cc-a0-62.ucode, which is a higher number than any your system tries to load: iwlwifi-ty-a0-gf-a0-59.ucode down to iwlwifi-ty-a0-gf-a0-39.ucode.

#74 Re: Other Issues » [SOLVED] Zoom in Devuan » 2022-10-03 21:44:54

Well I've no reason to believe that appimage would solve the issue.
And I wouldn't want to start using appimage just to solve this issue given all the issues that all such similar solutions (appimage, flatpack, etc.) bring.

Remember I'm on Chimaera. I only upgraded to backports in the first instance to handle my newish hardware (AMD Zen3 5600G, B550 motherboard) and some issues with suspend/hibernate. If 5.15 works why upgrade further to a newer kernel if that has a regression?

But I an happy to try and pinpoint what that regression is, so that when I do move to a stable Daedalus and no doubt even newer kernel it has been solved.

#75 Re: Other Issues » [SOLVED] Zoom in Devuan » 2022-10-03 18:08:37

Not keen on using appimage.

I did try HOS's suggestion to disable hardware acceleration. That didn't solve the problem.

What does seem to have solved the problem is downgrading my kernel to 5:15 from 5:18 (I needed a backported 5:15+ image as stable 5:10 doesn't address some amdgpu and motherboard chip recognition issues I had).

I can't see any relevant kernel bug reports in 5:16/5:18 or 5:18 so may attempt to at least identify in which kernel the regression occurred and then report it.

I've also found a 'signature' in syslog that occurs while the kernel is glitching:

Sep 19 17:08:35 grendel kernel: [91634.237980] amdgpu 0000:30:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
Sep 19 17:08:56 grendel kernel: [91655.526407] amdgpu 0000:30:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6

This was previously reported in association with a resume bug back in kernel 5:05 that was then solved.

Board footer

Forum Software