Hello:

Apparently so.

From what I can see his last post was on 2024-07-06, over a month ago.
Drop him an email, he'll show up eventually.
Maybe he's on vacation. (?)

Best,

A.

Hello:

I see.

Yes, me too.
I found it to be the best of all the network applications back in the time and I still think it is, by a good measure.

[OT]
I once contacted all (9) active members of the 'Wicd-devel' team to ask about what their plans were or to at least (instead of posting ambiguities) make it clear that the project was abandoned/dead in the water and ask for someone to take over but to no avail. My emails were not well received so I gave up.
Other people here have tried to get it up and running but something happened on the way there and they gave up/were not able to do much, don't know why.
[/OT]

Best,

A.

Hello:

Indeed.

You do know that Devuan Excalibur is a testing suite, unlike Devuan Daedalus which is a stable suite, yes?

Getting from testing to stable takes time.
And (needless to say) a lot of work from the developers/maintainers.
ie: many, many updates and tests to run, rinse / repeat, etc.

So yes, I fully agree with you.
Expecting a testing suite to work without any issues is asking too much.

That said, my old Sun Ultra 24 workstation (ca. 2007) runs on Devuan Daedalus with a pair of old Nvidia Quadro FX580 (ca. 2009) using nouveau2/stable 2.4.114-1+b1 and picom/stable 9.1-1 (much better than compton) to feed tree old 19" monitors: a pair of SyncMaster 940n and a Dell 1914S.

~$ cat /var/log/Xorg.0.log | grep -i glamor
[    32.394] (II) Loading sub module "glamoregl"
[    32.394] (II) LoadModule: "glamoregl"
[    32.394] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[    32.404] (II) Module glamoregl: vendor="X.Org Foundation"
[    33.104] (II) modeset(0): glamor X acceleration enabled on NV96
[    33.104] (II) modeset(0): glamor initialized
[    33.293] (II) Loading sub module "glamoregl"
[    33.293] (II) LoadModule: "glamoregl"
[    33.293] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[    33.293] (II) Module glamoregl: vendor="X.Org Foundation"
[    33.303] (II) modeset(G0): glamor X acceleration enabled on NV96
[    33.303] (II) modeset(G0): glamor initialized
~$ 

Best,

A.

Hello:

Seems that part is working properly.

But, being a touch thingy, if you don't/cannot [touch] you are in a pickle.

At least with phones running (?) Android > 4.4.4 (aka KitKat).
Note: I have an old Android 4.4.4 phone with no carrier access that does not do this.

That said, when I connect an Android 11 phone to my workstation, dmesg will declare* this:

--- snip ---
[ 1360.748466] usb 6-1: USB disconnect, device number 2
[ 3637.412472] usb 5-1.2: new high-speed USB device number 4 using xhci_hcd
[ 3637.539257] usb 5-1.2: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 2.23
[ 3637.539265] usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3637.539269] usb 5-1.2: Product: SAMSUNG_Android
[ 3637.539272] usb 5-1.2: Manufacturer: SAMSUNG
[ 3637.539274] usb 5-1.2: SerialNumber: RXXRXXXXXXX   
[ 3637.594388] cdc_acm 5-1.2:1.1: ttyACM0: USB ACM device
[ 3637.594978] usbcore: registered new interface driver cdc_acm
[ 3637.594983] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

* make sure your USB cable is sound, a bad cable may/will not work properly and the file manager will complain about missing/bad data.

At the same time, in [Places] my file manager shows two icons:

mtp and SAMSUNG Android.   

Attempting to list/access the phone's files gets the phone's screen to show a pop-up:

So that is the catch ... 
If you don't touch Allow, you will not see anything in the file manager.

There is probably a way to access the phone via adb, at least the files that do not require rooting the device to acess them.
ie: Android Debug Bridge version 1.0.41, find it in the Devuan repository.

eg:

~$ adb devices -l 
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
RXXXXXXXXXX            device usb:7-6 product:a02ub model:SM_A022M device:a02 transport_id:1
~$ 

I think that you can (?), if you know how to use it, do some [not-root rquired] file transfer/recovery:

~$ adb help
Android Debug Bridge version 1.0.41
Version 29.0.6-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
--- snip ---
file transfer:
 push [--sync] LOCAL... REMOTE
     copy local files/directories to device
     --sync: only push files that are newer on the host than the device
 pull [-a] REMOTE... LOCAL
     copy files/dirs from device
     -a: preserve file timestamp and mode
 sync [all|data|odm|oem|product|system|system_ext|vendor]
     sync a local build from $ANDROID_PRODUCT_OUT to the device (default all)
     -l: list files that would be copied, but don't copy them
--- snip ---

For the rest [of whatever you may be able to do] you'll have to look up the pertinent instructions on the web.
I don't know more that this at the moment.

I don't like Android.
As far as I am concerned it is a POS on wheels, a Google infested meta-harversting device.
Unfortunately, these things run on it.

Good luck with your phone.
Please let us know how you fared with this, it may be useful to others in your situation.

Best,

A.

Hello gl:

Howsyadoin'?

Indeed ...
But then you are a force of nature. 8^)

Basically, the problem is that my bucket list long and complicated.
ie: too many things in the air and too little time to tend to them while life happens.

But thanks for the link.

Best,

A.

Hello:

Don't know if appropriated would be the proper term to use.
After all, Ubuntu is derived from Debian ie: it is a Debian based distribution, composed of free / open-source software.
Which the Debian packages you mention also are.

Hmm ...
Could not say, I'm sure there's a reason for that.
That said, let's not forget how under-staffed and over-worked the Devuan crew maintaining this heroic effort acually is.

Thanks for your input.

Best,

A.

Hello:

Ahh ...

Tried it but GDebi asks for scrcpy-server_1.25-1_all.deb which I downloaded and installed from the same repository.
Seems to work properly and now I have to see if I can find the right version of the GUI for this application as there it looks like there is more than one.

If I find that it does what I want it to do, I will explore the possibility of building the latest version with the source provided by the author.

Many thanks to all those who pitched in.
Much appreciated.

Best,

A.

Hello:

Playing with fire comes to mind.  8^D

I strive to be very (very) careful with what I do to my Devuan and try, above all things, to avoid risking havok.
Yes, I do have daily backups but still ...

That said, thanks for the tip.
It may come in handy should I want to experiment with a VM.

Best,

A.

Hello:

Thank you very much for taking the time to write that up.
Much appreciated.

But I would rather avoid having to do something like that.

Yes, I had thought of that.

But no.
GDebi will not install any of the three as there are unmet dependencies for all of them.
Seems that dependency hell is at the gates.  8^°

Thank you both for your input.

Best,

A.

Hello:

This world-wide foobar is related to the use of CrowdStrike Falcon security platform software.
Not something you would find in any home computer.

What has happened clearly illustrates the lack of common sense on behalf of a great many global/critical IT players who (besides using Windows based systems), put all their security/redundancy eggs in the same basket with, as is quite evident, no exit/recovery solution in case of failure.

When (not if) this happens again, it will be much worse.

Best,

A.

Hello:

A bit late to the party but finally found the key to this.

It seems that the nouveau driver looks for a /lib/firmware/nvidia directory containing 28 directories with firmware for supported Nvidia cards neeeding non-free firmware files to work properly. ie: gaxxx, gkxxx, gmxxx, gpxxx, tegraxxx and tuxxx.

Not finding the directory, it prints out the warning.
Makes sense but should this not be part of the installation/ upgrade process?

If your Nvidia hardware is not on that list, you obviously do not need those firmware files in your system (~4.5MiB on disk).
So you either learn to live with the warning (shows up with every kernel and initramfs upgrade) or install the firmware-misc-nonfree package.

No idea why the nouveau driver looks for firmware it clearly does not need.
Is it not aware of the installed hardware to check against the supported cards that need firmware?

eg:

:~$ lspci                                 
--- snip ---
01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] (rev a1)
--- snip ---
:~$

Best,

A.