Hello:

From what I have read on-line, this seems to have been general opinion from the start, then morphed into common knowledge.

Which begs the question: why bother with it al all?

I have been using X-Server from when I installed my first Linux many years ago.
Never had an issue that could not be diagnosed with the /var/log/Xorg.0.log printout and proper research, to be later solved with judicious editing of the /etc/X11xorg.conf.

The same perfectly working *.conf has been in use (with virtually the same three/four monitor setup) through no less than four different distributions and multiple Devuan dist-upgrades. All that since mid 2018 (IIRC).

But I digress.
Have a read here.

Best,

A.

Hello:

Hmm ...
Yes, that is what I get with my Intel Quad Q9550.

But what do you get when you do chcpu -r with the live CD?

and ...

What does uname -a get you with your local configuration and then with the live cd?

Best,

A.

Hello:

You're welcome.
Please let us know how you fared with this.

Best,

A.

Hello:

Don't think so.
I certainly won't, find them both to be quite useful.

Can't really say.
If it has, I think that it may probably be by a relatively insignificant amount.

That said, there's always fstrim running with cron.weekly.
And /var/log/trim.log to check and see that it is working properly.

No need to logrotate it.
Started 01/04/2021 and it is only 600 lines long / 30K.

Best,

A.

Hello:

You're welcome.

Please do.
From what I have seen on-line, what you want to do is not and has not ever been a straightforward affaire, so your update will be useful to have. 

Indeed ...
I (and a great many here) can easily relate to that.

Best,

A.

Hello:

No.
My apologies for the confusion.  8^°

When I say "... only seen these once, long ago ... " I am referring to these type of modems.
ie: cellular network based USB modems using SIM chips as opposed to land line modems using copper.

My comment with respect to the 14.4 USR Sportster dial-up modem (a ca. 1994 a land line modem) was only to illustrate your present situation.
ie: the fact that the issues you are having seem to be the same ones I had over 30 years ago.
And how much many things have not changed.

Before purchasing another one of these modems, you may want to consider getting in touch with the telco that will actually provide the cellular phone service for you and ask them if they can provide voice service with a USB modem+SIM chip or not and and if so, if they offer one or can suggest a brand/model.

Bear in mind that different telcos may offer different services/options/rates.
eg: a telco may offer voice and (maybe) tethering with a cellphone/smartphone but only data (and not voice) with a USB modem.

Also bear in mind that different telcos may offer different services/options/rates.

If they do, get the brand/model/etc. and try to find out all you can about it before you purchase it.
Specifically any on-line reports/reviews that can give you some information on how to get it to work reliably under Linux.

Edit

Forgot to add this, cannot say how acccurate this information is:

Best,

A.

Hello:

Indeed ...
Similar to what happened when attempting to use my trusty Motorola StarTAC to reach my ISP via a serial dongle/PCMCIA 33.6kbit modem combo on my HP 200LX palmtop.

It worked* but ...   The local carrier was not having any of that sorcery when they could charge you a hefty extra for 'data' transmission.
* the modem would start the handshake, negotiate a speed but drop the line right before connection.

But I digress.

@TCH:
Check these links, I think they may have some answers for you.

https://stackoverflow.com/questions/163 … sb-dongles
https://unix.stackexchange.com/question … gsm-modems
https://bochinche.github.io/it/linux/hu … mands.html

Best,

A.

Hello:

No apologies needed.
None whatsoever.

No scratches registered either. 
All's well ...

I was just taking the piss.  8^°

But we are far from the original thread subject now.
So just to clarify.

One WiCD package (1.7.4+tb2-6+devuan1.1) uses python-wicd and should work if you have python 2.7.16-1 installed.
Another WiCD package (1.7.4+tb2-6+devuan2) is the one that I previously referred to, the transitional package.

With respect to the other WiCD package (1.7.4+tb2+2019.09.18git2e0ba579-1) the changelog.Debian file reads:

If it actually runs in Deadalus, it will be as any software running on unstable, prone to have problems.

The WiCD package (1.7.4+tb2-6+devuan2) actually starts whatever you have decided to install (ie: network-manager-gnome | network-manager, etc.), so stopping it and starting WiCD would start the transitioned package again.

No matter, I still have time to think up something else.

Thanks for your input.

Best,

A.

Hello:

Indeed ...
Could be.

I have not used WiFi in my box for the longest while now, only with my Asus 1000HE when there is some issue with my telco's ADSL and I get to borrow my next door neighbour's WiFi to check something.

Like many here, I have used WiCD for quite a few years now, quickly became second nature to do so.
Its main feature being that it is light, fast and, in all hese years, it always worked properly and never caused me the sort of grief I read about with other connection managers.

Not using WiFi in my box, maybe I should resort to something even simpler, such as a CLI start/stop connection
I recall a couple of frequent posters (not seen for a while now) speaking wonders of that approach.

I'll have to think about it.

Thanks for your input.

Best regards,

A.

Hello:

Hmm ...
Don't sell your self short ...  8^P

Thanks for the heads up.
I'll have a look at it.

Best,

A.

Hello:

No need to purge xfce4.
Just the xfce4-power-manager package which is (apparently) an important part of the problem you are having. 

But before we continue, please add the necessary 'code' tags so that the printouts can be seen as code.
ie: white lettering on black background.

It is easier to see and analyse that way.

Like this:

[code]
Like this ...
[/code]

You can do it manually or select/paint the text and click on the |code block| section.

Thanks.

A.