Hello:

You're welcome.

All the hardware works properly?

Yes, I'd say those are more or less standard.
Like this one I have in my box:

[ 1.324984] acpi PNP0A08:00: ignoring host bridge window [mem 0x000d0000-0x000dffff window] (conflicts with Adapter ROM [mem 0x000ce000-0x000d3bff])
[ 1.327999] pci 0000:00:1f.0: quirk: [io  0x0800-0x087f] claimed by ICH6 ACPI/GPIO/TCO

This type of memory conflict is due (so I have had explained to me) to a badly written BIOS.

As the kernel evolves, these messages/warnings also evolve/change.
In time, some messages end up going away.

This is all crud generated by the fact that OEMs and BIOS writers are ruled by what MS wants and nothing else.

But this should not happen, much less in a box like mine, a Sun Microsystems Ultra24 WS which was released 15 years ago (10/2007) with the most basic configuration going for ~ US$1.000, a very hefty price tag at the time. (I purchased it used in 2011, of course)

OEMs (Sun included) didn't/don't give a monkey's toss if the BIOS they slapped together from bits and pieces of other older ones does or does not comply with what ACPI says in their specifications, as long as it certifies for hardware that ships with Windows OSs.

And if they have to do it the MS way because the ACPI way does not play ball with the currently shipping Windows OS, they just do it.
Otherwise their hardware will not be "Windows Certified", which means that it won't sell.

That's about it, you have to endure it.
Till we get open source BIOSes and that will be the end of it.

But I really don't see it coming any time soon.

Best,

A.

Hello:

If everything works properly ...  8^°

But just for curiosity's sake, you can have a good look at your dmesg printout and see if there are any ACPI errors.
Run this and see what you get:

sudo dmesg | grep -i "error\|warning\|fail\|segfault\|fatal"

Bear in mind that some ACPI errors are a permenent fixture in older boards but the kernel takes care of it:

user@devuan:~$ sudo dmesg | grep -i "error\|warning\|fail\|segfault\|fatal"
--- snip ---
[  0.021101] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 128/64 (20200925/tbfadt-569)
[  1.318080] ACPI BIOS Error (bug): Could not resolve symbol [\_SB._OSC.SUPP], AE_NOT_FOUND (20200925/psargs-330)
[  1.318088] ACPI Error: Aborting method \_SB._OSC due to previous error (AE_NOT_FOUND) (20200925/psparse-531)
--- snip ---
user@devuan:~$ 

I don't use suspend or hibernate and as my Sun Ultra 24's BIOS is an absolute POS, I have to bear an ocassional, totally random and non-reproducible shutdown issue which I think is related to some internal temp sensor and how it interacts with the box's ventilation.

Best,

A.

Hello:

Besides following HoaS' instructions, to may find this link (or parts of it) useful.

Best,

A.

Hello:

No ...
Gods forbid.  8^°

In my opinion, the term obsolete is a (highly) relative one.

And like many other things in life, it all depends.

eg:
I have heard my (much younger) colleagues say that if you don't know CAD (I refused to ever use it) you are obsolete as an architect.
Somehow they have developed the idea that if you know how to use CAD, not only it turns you into an architect but a good one at that.

But what happens when power goes down, their software goes south just because liucence or whatever or they lose their day's work due to HDD problems?

I'll keep drawing free-hand or with my wooden T-square, triple scale and squares on my drafting table.   
And quickly draw up a set of multi direction internal/aerial views of the project, something which they never learnt how to do without CAD.

I will be able to see and explain the whole project, not just a small sector on a screen, and anyone with a set of eyes will be able to understand it.

So ...
Just who became obsolete in an instant?  8^\*

But I digress ...

Indeed, here.(?)
Some backgound also.

Seems like very good quality work, had not seen it before.
IMO, if at all possible, it would be great to add a strictly Devuan version (a meta package?) to the repository as a tool to set up Openbox/Tint2 as the default Devuan desktop.

ie: for those of us who appreciate obsolete things for their true value.

Best,

A.

Hello:

Indeed ...

It only fixes (not a fix, just a way of avoiding it) the having screwed things up by using CSE in the first place.
There are so many things they could be dedicating time to fix.
But no, skinny bars and CSE it is.

--> Seems they have their own Poeterings at xfce HQ's.

O.

Hello:

If you are referring to Devuan, I doubt it will die.

What is dead to me and (from what I have read) quite a few xfce users is xfce in any form after 4.12.2.
The path the developers have taken, the useless bloat and all the unfixed issues (compositor leading the way) made me decide not to upgrade further.
Not to mention the Poetteringesque attitude from the developers.

https://forum.xfce.org/viewtopic.php?pid=56141#p56141
https://forum.xfce.org/viewtopic.php?pid=56143#p56143
https://forum.xfce.org/viewtopic.php?pid=56144#p56144

Still have to decide what to use, the strongest/more suitable option I see being Openbox if and when I upgrade to Chimaera.

I think it should be the default Devuan desktop from Chimaera onwards.
ie: with a desktop as similar as possible to what Philip Newborough's CrunchBang project was.

Unfortunately, CrunchBang developement was ended by it's developer back in 02/2015. It was (YMMV) one of the best distributions at the time.

Best,

A.

Hello:

The same stuff I have.
A Sun Ultra24 and an Asus 1000HE with 2Gb RAM and 500Gb HDD.

I see.

Please excuse my ignorance in this specific matter (there are others but I digress ...)

I have gnome-keyring in my U24's Devuan installation but I see that I also have a few other keyrings.

debian-archive-keyring
devuan-keyring
python-keyring
python-keyrings.alt
python3-keyring
python3-keyrings.alt

Until my issues with Back-in-Time, all this keyring thing had always been transparent to me, to the extent that I don't really know what it does.

The cron job running BiT sends a warning every so often (can't reproduce) but the job gets done with no problems and that is why I'm looking at gnome-keyring now.

I have read that BiT has to see at least one of these is installed: python-keyring-kwallet, python-secretstorage and python-gnomekeyring.

Of those three, my installation has python-secretstorage but has a problem if gnome-keyring is not there. 

Maybe I should purge gnome-keyring and install python-gnomekeyring?

Not really bother, just that with the exception of gnome-disks which I use every so often, I am sort of allergic to gnome so I'd rather avoid it.
But gnome-disks does not depend on gnome-keyring.

Thank you for your input.

Best,

A.

Hello:

No, not for me.

Don't use that one, at least for the time being.

Thanks for your input.

Best,

A.

Hello:

I have thought about it and have not found reason (save the pcmanfm recomends) for having gnome-keyring installed.
Same for gvfs-backends for that matter.

ie: my basic reasoning is that they are not dependencies, just pcmanfm recommends.
And I have seen that recommends can sometimes be silently problematic.

On a hunch, I wondered if this problem isn't being caused by having too many ***-keyring instances?

user@devuan:~$ apt list | grep installed | grep keyring
--- snip ---
debian-archive-keyring/oldstable,oldstable,now 2019.1+deb10u1 all [installed]
devuan-keyring/oldstable,oldstable,now 2022.09.04 all [installed]
gir1.2-gnomekeyring-1.0/now 3.12.0-1+b2 amd64 [installed,local]
libgnome-keyring-common/now 3.12.0-1 all [installed,local]
libgnome-keyring0/now 3.12.0-1+b2 amd64 [installed,local]
python-keyring/oldstable,oldstable,now 17.1.1-1 all [installed,automatic]
python-keyrings.alt/oldstable,oldstable,now 3.1.1-1 all [installed,automatic]
python3-keyring/oldstable,oldstable,now 17.1.1-1 all [installed,automatic]
python3-keyrings.alt/oldstable,oldstable,now 3.1.1-1 all [installed,automatic]
user@devuan:~$ 

There's one sure way to find out: purge both gnome-keyring and gvfs-backends, which I did at noon today.

I have observed no ill effects after three or four reboots, mounting/unmounting of Palm T|Xs, external USB HDs and six hours uptime.
Now I'll just wait to see if I get any more mail in my mbox regarding BiT or whatever keyring.

Any suggestions?
Tests to do?

I'll post back if I get another message or in a fortnight, whatever comes first.

Best,

A.

Hello:

It is the chaps at Pi-Hole that consider Devuan a fringe OS.
The Discourse chaps have PaleMoon as unsupported.

Thanks to both for the input.  8^)
I'll try it out and see how it goes.

Best,

A.

Hello:

Yes.
Right before I ripped it open to see the contacts in bad shape.

I wanted to recover the quality cable/ferrite filter/USB plug combo I rescued from an old Palm IV base and grafted on to it when the original cable went bad.

It is USB 1.1 or 2.0 but worth keeping, it is like new.
They really don't make stuff like they used to.  8^|

Best,

A.