I can understand it making sense in the context of a server with
multiple interfaces. We used to have occasional problems with ethernet
enumeration when we were using recycled PCs as gateway routers. I just
don't see why that kind of corner case drove adoption for a problem
that didn't exist for
Just some thoughts... If I'm reading the document on freedesktop.org
correctly then this new system does not actually solve the problem it
claims to be solving. Specifically this part here:
"...The following different naming schemes for network interfaces are
now supported by udev natively:
I too have never figured out what was gained by going to
"predictable names" as far as I am concerned it is the
definition of oxymoron. I always knew what eth0 or eth1
or whatever the original names were, these things though
on a given machine will USUALLY come up the same but
they change from
On Sun, 14 Feb 2021, Rich Shepard wrote:
Where to look? How to diagnose?
Of course, I found what I think is the problem immediately after sending
this message.
At least with audacity. Audacity has a drop down combobox with output
options. The default is, "HD-Audio Generic: ALC1220 digital
I'm looking for suggestions on identifying why I can no longer play sound
files (.wav, generally) produced with the AudioTechnia AT2500USB condenser
microphone and Focusrite Scarlett Solo pre-amp.
Regardless of tool used to produce the audio file (pacat -r, audacity,
vokoscreenNG) playback
