Hello:

Doing some more digging found that, at some point and for reasons unknown, I did ...

# ldconfig -p
#

... which can only be executed with elevated priviliges.

From man ldconfig:

As it was just a print I tried it, with the result being a huge printout in the terminal:

[root@devuan ~]# ldconfig -p
1442 libs found in cache `/etc/ld.so.cache'
	libz3.so.4 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libz3.so.4
	libz3.so.4 (libc6) => /usr/lib/i386-linux-gnu/libz3.so.4 ...
--- snip ---
        ld-linux.so.2 (ELF) => /lib/ld-linux.so.2
	ld-linux-x86-64.so.2 (libc6,x86-64) => /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
Cache generated by: ldconfig (Debian GLIBC 2.36-9+deb12u14) stable release version 2.36
[root@devuan ~]# 

No idea as to how that got in the /root directory but I deleted it.
The cache itself is in /etc/ld.so.cache.

That's all I could find, so I guess I can mark it solved.

Best,

A.

Hello:

As you surely know, Mint is a systemd distribution and I cannot but wonder if HP UEFI just plays nicer with systemd present than when it is not.

Just a thought.

When you say "but wouldn't boot cleanly" I understand (like the Mint installer) that Devuan was installed and actually booted, albeit with something not being right.

Could you please tell us just what you are making reference to?

Best,

A.

Hello:

No, I'm afraid you have not understood.

Maybe it is a language problem, the answers posted somehow lost in translation?
No idea.

The answer to your question is really quite simple:

If you want to know why the hplip-3.25.8 package you downloaded (which is not a *.deb file) will not "install at Devuan" you will have to ask the maintainers:

https://sourceforge.net/projects/hplip/ … ip/3.25.8/

To be able to do that you have to join the sourceforge.org mailing list:

https://sourceforge.net/projects/hplip/lists/hplip-help

Once you have joined, you can log-in:

https://sourceforge.net/auth/

And post the question:

https://sourceforge.net/p/hplip/mailman/hplip-help/

Your argument [... debian repos always have unfresh old software.] is quite clearly not a valid one.
The hplip package in the Devuan repositories works as intended and (for the moment) is the only one available for Devuan.

I hope I have cleared up your doubts.

Best,

A.

Hello:

If your sources are the proper ones (Devuan), the firmware installed should be without any issues.

Maybe you purchased a counterfit Techno N150?
Your description of the packaging would seem (?) to point in that direction.

That said, a USB wi-fi adaptor with 'N150' in the label could be one of a great many brands using that Atheros chipset in different physical formats.

eg:
https://tehnoetic.com/tehnoetic-wireles … earch=N150
https://tehnoetic.com/tet-n150hga?search=N150

You may want to contact Tehnoetic to ask if what you purchased is genuine.
ie: send photos of the hardware, the packaging and a *.txt file with the terminal printout when you run:

~$ lsusb

Best,

A.

Hello:

Surprised? Not.

Best,

A.

Hello:

Bad practise. *

Best,

A.

* so is not looking at the date on the posts.  8^°

Hello:

Of course.

The pcmagos article made direct reference (~14 years ago) to "The Manner Of The Buntus" which, quite obviously subverted the way to use sudo properly and now RPiOS is catching up.

Best,

A.

Hello:

And we're baaaaaaaaack!
After rolling back on the previous 'not available' block, now you cannot see a YouTube video unless you sign in.
For the protection of our | their the community, obviously.

What were you thinking? 8^°

But Invidious still works.
For now.

Kudos to them.

Best,

A.

Hello:

I was wondering what became of your Z10. 8^°

No problem with that.

If you can upgrade system versions you should not have any issues doing what I suggested with your work machine.
Booting with a live *.iso is just that, it does not do anything to the existing system, configuration, data, etc. (unless you do it intentionally).

Running a live Excalibur for a few hours should give you a hint at what is going on.

Off the top of my head:

You could have a either memory or processor overheating problem.
Or both at the same time which is not frequent but not unheard of, particularly in workplace issued equipment which (in my experience) does not usually see proper maintenance.

So ...
You first have to try to isolate the problem.

To test the memory problem, run a long memtest from the live *.iso menu and see what happens. (check the man files)

If memtest finds a problem with the memory, the first thing to do is to remove the memory modules, clean the contacts, reseat them and run the test again in the same conditions. ie: close the box again, do not leave it open because you would be altering the test environment.

If memtest still finds a problem with the memory, run the test again with just one pair of modules and it if passes, add the next pair and so on till you find the offending pair.

If you have a spare matching module, do the same routine to find the offending module and then replace it.

If memtest does not find a problem with the memory and the machine still freezes, you most probably have a heat related problem which can be solved by checking the CPU / heatsink assembly.

Checking the CPU heatsink involves unmounting it, cleaning lint/dust from both the HS and the fan and then remounting it with fresh heatsink grease. You will also have to check that the fan turns freely and does not stall.

Goes without saying that at this point the inside of the box also needs to be checked for dust bunnies and be throughly cleaned up. (fans, nooks and crannies, etc.)

Please let us know how you fared.

Best,

A.