on a standalone PC with external speakers (connected by USB and audio jack) I installed Lubuntu 21.04;
in the live-version the speakers didn’t work; but after the installation they worked;
then after the update, executed in the terminal, this is what I need to do to make the speakers work after every reboot:
click on the panel on the speaker-symbol; click on “Mixer”; click in the tabs on “Configuration”;
click the checkbox in the “Built-in Audio” “Profile” (Analog Stereo Output) to deactivate;
click again the checkbox in the “Built-in Audio” “Profile” (Analog Stereo Output) to activate
if you need more informations about the PC: sudo lshw -C sound:
*-multimedia
description: Audio device
product: Celeron/Pentium Silver Processor High Definition Audio
vendor: Intel Corporation
physical id: e
bus info: pci@0000:00:0e.0
version: 03
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:25 memory:a1310000-a1313fff memory:a1000000-a10fffff
Is there a way that I don’t need to deactivate and to activate the extenal speakers after every reboot?
Have anthing strange happening in your computer because the correct is always speaker be power on when starting Lubuntu.
You had tried connect in another USB port ?
I tried both possible USB ports. Same issue. No sound.
Is it because the speakers are very cheap (10 Euro)?
And there are more problems:
After a shutdown normally without speakers connected after 3 seconds the computer is off.
But with speakers connected, although the speakers do not work, after 3 seconds it takes another 10 seconds to be off, and afterwards there is a loud sound from the speakers, sometimes 2 times a loud sound from the speakers.
“Is it because the speakers are very cheap (10 Euro)?”
Not.
Try a test connecting the soeaker usb in cell battery charger and see if has the same issue.
Do you mean I go from the speaker with the audio jack in the computer, and from the speaker with the USB in the USB-slot of an USB-adapter that can be used for example to charge a tablet?
I connected the speaker with the audio jack in the computer, and from the speaker with the USB in the USB-slot of an USB-adapter that can be used for example to charge a tablet;
the result:
deactivating and activating is still needed
shutdown takes 10 seconds longer like before
there are no sounds after the shutdown, but if I take away the electricity then there is sound
Should I buy a speaker with only USB-connection, so no audio jack?
Is the computer the problem?
I not have much information about Linux, but the problem not is pointing to your speaker.
Perhaps related with drivers (not means being or not your sound device), a startup or and shutdown task needing timed processing.
You need post here startup and shutdown logs.
You need to acess the computer firmware BIOS (or UEFI) and see if has any setting about usb power saver.
Try for test access the BIOS and disable all cpu power saver settings and after finished tests return the settings to defaults.
If possible, please provide the output from the following command after experiencing the issue (with the speakers still connected):
dmesg | grep snd
I get the feeling @aug7744 might be on to something. It just might be the driver that’s loaded or it could be something else. Why performing an update to the system is causing this is still unknown to me but if you can please share the output text for the above command, I might get another clue.
Since today, I don’t need to deactivating and activating any more after a reboot!!!
Could it be because you changed some packages and because I made an update?
If so, thank you very much for your help!
But there is still a shutdown-problem:
instead of 3 seconds it still needs 13 seconds
there is still a loud noise in the second of the shutdown
And there is a new problem:
Since today on a notebook with Lubuntu 20.10 there is no sound at all. Yesterday it was working.
It seems to be that it happened after the update this morning.
I have no clue what updates are available. If you did an update and it fixed itself, then it gives me the impression that something present on the system is causing the driver to act buggy. The reason I say this is because it appears the notebook you have runs the same driver and suddenly its also having problems. The output for dmesg command kind of supports this but that is just my hunch. I still don’t know what pieces are involved but what I feel is currently the most suspicious is the driver.