Re: SOLVED: Re: Glitchy sound in Steam games after hard drive upgrade

[eben]

On 4/24/24 00:46, Charlie Gibbs wrote:

On 2024-04-22 16:50, Jeffrey Walton wrote:


What are the old and new hard drive model numbers and specs?


Correction: the 4TB drive is a Western Digital WD40EFPX.  I was reading
it by shining a flashlight through a gap in the frame and squinting from
a wide angle because I didn't want to take the box apart yet again.


Note for the future: hdparm -i can give you that info.  If you think that's
changed since boot, hdparm -I reads it from the drive.

SOLVED: Re: Glitchy sound in Steam games after hard drive upgrade

[Charlie Gibbs]

On 2024-04-22 16:50, Jeffrey Walton wrote:


What are the old and new hard drive model numbers and specs?


Correction: the 4TB drive is a Western Digital WD40EFPX.  I was reading
it by shining a flashlight through a gap in the frame and squinting from
a wide angle because I didn't want to take the box apart yet again.

I've trying several of the suggestions people have kindly posted here.
The /etc directory on the new drive was getting messed up badly enough
that I decided to try copying the 500GB drive's root partition to the
4TB drive using dd.  The machine hung partway through the subsequent
boot.  So I wiped the root partition and re-installed Debian from
scratch, leaving the /home partition intact.

But the real magic was the re-installation of the Steam launcher.
Since my Portal icons were on my desktop, and clicking them made it
run (sort of), I was fooled into thinking everything was still there.
But I found a detailed set of instructions for installing Steam at
https://wiki.debian.org/Steam and followed them.  This installed or
overlaid the missing or broken parts and presto! my sound is now clean.

Many thanks to everyone for your help.  This a good lesson to not take
too many things for granted, and also to be a bit more adventurous.
(A full Debian re-install really doesn't take that long...)

--
/~\  Charlie Gibbs  |  You can't save the earth
\ /|  unless you're willing to
 X   I'm really at ac.dekanfrus |  make other people sacrifice.
/ \  if you read it the right way.  |-- Dogbert the green consultant

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Thanks, I tried it but it turns out to be a wifi/usb problem I think.

Jan Krapivin  writes:

> Have you tried a LIVE-version of another Linux distribution? It will
> be interesting to compare.
>
> вс, 7 апр. 2024 г. в 22:30, Richmond :
>
> Richmond  writes:
>
> > Richmond  writes:
> >
> >> When playing videos in a web browser, and sending the sound to
> a
> >> bluetooth speaker (amazon echo) I get playback problems;
> stuttering,
> >> sound quality reduction to AM radio level or lower). These
> things can
> >> clear up after a minute or two, or be reduced.
> >>
> >> When playing from nvlc however I get no such problems. (I
> haven't
> >> tried vlc so I am not sure if it is just that it is a command
> line).
> >>
> >> I have tried google-chrome and firefox-esr.
> >>
> >> Perhaps there is some other browser which will work? Maybe I
> need to
> >> isolate the process from the browser? I tried pop-out picture
> on you
> >> tube and it improved but there was still stuttering.
> >
> > I installed Falkon and Konqueror. I tried Falkon and it worked
> fine, no
> > sound problems. But then I tried Google-chrome again and that
> was
> > working fine too, and so was Firefox-esr. The problems have
> gone away
> > and even rebooting doesn't bring them back. Maybe one of those
> browsers
> > brought a better library with it.
>
> These problems have come back again. I have tried rebooting. I
> tried
> sending the same audio from an android phone and it works fine.
> How do I
> find out what the problems is? I cannot see errors in journalctl
>

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Lee  writes:

> On Sun, Apr 7, 2024 at 3:30 PM Richmond wrote:
>>
>> Richmond writes:
>>
>> > Richmond writes:
>> >
>> >> When playing videos in a web browser, and sending the sound to a
>> >> bluetooth speaker (amazon echo) I get playback problems;
>> >> stuttering, sound quality reduction to AM radio level or
>> >> lower). These things can clear up after a minute or two, or be
>> >> reduced.
>> >>
>> >> When playing from nvlc however I get no such problems. (I haven't
>> >> tried vlc so I am not sure if it is just that it is a command
>> >> line).
>> >>
>> >> I have tried google-chrome and firefox-esr.
>> >>
>> >> Perhaps there is some other browser which will work? Maybe I need
>> >> to isolate the process from the browser? I tried pop-out picture
>> >> on you tube and it improved but there was still stuttering.
>> >
>> > I installed Falkon and Konqueror. I tried Falkon and it worked
>> > fine, no sound problems. But then I tried Google-chrome again and
>> > that was working fine too, and so was Firefox-esr. The problems
>> > have gone away and even rebooting doesn't bring them back. Maybe
>> > one of those browsers brought a better library with it.
>>
>> These problems have come back again.
>
> So unless you've updated or installed new hardware or software it's
> probably not a firmware/software issue.
>
>> I have tried rebooting. I tried sending the same audio from an
>> android phone and it works fine. How do I find out what the problems
>> is? I cannot see errors in journalctl
>
> It's possible that wifi or usb 3.0 could be interfering with your
> bluetooth speakers - eg
> https://www.zdnet.com/article/usb-3-and-usb-c-devices-can-cause-problems-with-wi-fi-and-bluetooth-connections-but-theres-a-solution/

Thanks, I think this is the answer! I was having no problems today but
noticed that the PC was connected to 5Ghz. Sometimes it connects at
2.4Ghz. When I disabled 5Ghz and forced the PC to use 2.4Ghz the problem
came back. So now all I need to do is seperate those services and/or tie
the PC to 5Ghz.

The PC is a laptop but I never move it from the desktop. I am using a
USB mouse and USB keyboard adapter to an old IBM keyboard.

> https://sortatechy.com/spot-and-fix-bluetooth-interference-with-wifi/
>
> If your PC is using wireless and can use a 5Ghz channel, try moving
> your PC wireless to a 5Ghz channel first.  If you PC only supports
> 2.4Gh wireless you can install linssid
> https://packages.debian.org/bookworm/linssid and pick a relatively
> unused channel for your PC wireless.  Or just try channels 1, 6 and 11
> and see if any of those makes a difference..
>
> If you're using a USB 3.0 device on your PC try turning it off or
> moving it to a USB 2.0 port and see if that fixes the bluetooth
> interference.
>
> Regards, Lee

Re: Bluetooth sound problems playing from a web browser

[Lee]

On Sun, Apr 7, 2024 at 3:30 PM Richmond wrote:
>
> Richmond writes:
>
> > Richmond writes:
> >
> >> When playing videos in a web browser, and sending the sound to a
> >> bluetooth speaker (amazon echo) I get playback problems; stuttering,
> >> sound quality reduction to AM radio level or lower). These things can
> >> clear up after a minute or two, or be reduced.
> >>
> >> When playing from nvlc however I get no such problems. (I haven't
> >> tried vlc so I am not sure if it is just that it is a command line).
> >>
> >> I have tried google-chrome and firefox-esr.
> >>
> >> Perhaps there is some other browser which will work? Maybe I need to
> >> isolate the process from the browser? I tried pop-out picture on you
> >> tube and it improved but there was still stuttering.
> >
> > I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
> > sound problems. But then I tried Google-chrome again and that was
> > working fine too, and so was Firefox-esr. The problems have gone away
> > and even rebooting doesn't bring them back. Maybe one of those browsers
> > brought a better library with it.
>
> These problems have come back again.

So unless you've updated or installed new hardware or software it's
probably not a firmware/software issue.

> I have tried rebooting. I tried
> sending the same audio from an android phone and it works fine. How do I
> find out what the problems is? I cannot see errors in journalctl

It's possible that wifi or usb 3.0 could be interfering with your
bluetooth speakers - eg
https://www.zdnet.com/article/usb-3-and-usb-c-devices-can-cause-problems-with-wi-fi-and-bluetooth-connections-but-theres-a-solution/
https://sortatechy.com/spot-and-fix-bluetooth-interference-with-wifi/

If your PC is using wireless and can use a 5Ghz channel, try moving
your PC wireless to a 5Ghz channel first.
If you PC only supports 2.4Gh wireless you can install linssid
  https://packages.debian.org/bookworm/linssid
and pick a relatively unused channel for your PC wireless.  Or just
try channels 1, 6 and 11 and see if any of those makes a difference..

If you're using a USB 3.0 device on your PC try turning it off or
moving it to a USB 2.0 port and see if that fixes the bluetooth
interference.

Regards,
Lee

Re: Bluetooth sound problems playing from a web browser

[Jan Krapivin]

Have you tried a LIVE-version of another Linux distribution? It will be
interesting to compare.

вс, 7 апр. 2024 г. в 22:30, Richmond :

> Richmond  writes:
>
> > Richmond  writes:
> >
> >> When playing videos in a web browser, and sending the sound to a
> >> bluetooth speaker (amazon echo) I get playback problems; stuttering,
> >> sound quality reduction to AM radio level or lower). These things can
> >> clear up after a minute or two, or be reduced.
> >>
> >> When playing from nvlc however I get no such problems. (I haven't
> >> tried vlc so I am not sure if it is just that it is a command line).
> >>
> >> I have tried google-chrome and firefox-esr.
> >>
> >> Perhaps there is some other browser which will work? Maybe I need to
> >> isolate the process from the browser? I tried pop-out picture on you
> >> tube and it improved but there was still stuttering.
> >
> > I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
> > sound problems. But then I tried Google-chrome again and that was
> > working fine too, and so was Firefox-esr. The problems have gone away
> > and even rebooting doesn't bring them back. Maybe one of those browsers
> > brought a better library with it.
>
> These problems have come back again. I have tried rebooting. I tried
> sending the same audio from an android phone and it works fine. How do I
> find out what the problems is? I cannot see errors in journalctl
>
>

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Richmond  writes:

> Richmond  writes:
>
>> When playing videos in a web browser, and sending the sound to a
>> bluetooth speaker (amazon echo) I get playback problems; stuttering,
>> sound quality reduction to AM radio level or lower). These things can
>> clear up after a minute or two, or be reduced.
>>
>> When playing from nvlc however I get no such problems. (I haven't
>> tried vlc so I am not sure if it is just that it is a command line).
>>
>> I have tried google-chrome and firefox-esr.
>>
>> Perhaps there is some other browser which will work? Maybe I need to
>> isolate the process from the browser? I tried pop-out picture on you
>> tube and it improved but there was still stuttering.
>
> I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
> sound problems. But then I tried Google-chrome again and that was
> working fine too, and so was Firefox-esr. The problems have gone away
> and even rebooting doesn't bring them back. Maybe one of those browsers
> brought a better library with it.

These problems have come back again. I have tried rebooting. I tried
sending the same audio from an android phone and it works fine. How do I
find out what the problems is? I cannot see errors in journalctl

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Richmond  writes:

> When playing videos in a web browser, and sending the sound to a
> bluetooth speaker (amazon echo) I get playback problems; stuttering,
> sound quality reduction to AM radio level or lower). These things can
> clear up after a minute or two, or be reduced.
>
> When playing from nvlc however I get no such problems. (I haven't
> tried vlc so I am not sure if it is just that it is a command line).
>
> I have tried google-chrome and firefox-esr.
>
> Perhaps there is some other browser which will work? Maybe I need to
> isolate the process from the browser? I tried pop-out picture on you
> tube and it improved but there was still stuttering.

I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
sound problems. But then I tried Google-chrome again and that was
working fine too, and so was Firefox-esr. The problems have gone away
and even rebooting doesn't bring them back. Maybe one of those browsers
brought a better library with it.

Re: Bluetooth sound problems Debian 12 GNOME

[Charles Curley]

On Mon, 18 Mar 2024 13:32:18 +0300
Jan Krapivin  wrote:

> Small problem is that LTS Kernel 6.1 doesn’t support this device, so
> I have used Liquorix kernel, which I have installed earlier. Though,
> I don’t need this kernel, as it haven’t helped me with sound
> interrupts, which was my hope at first.

I'm glad you reached a solution. You might also check the backports
kernel, which is currently linux-image-6.6.13+bpo-amd64
6.6.13-1~bpo12+1.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

Good news. Looks like I have solved the problem. As a last resort I have
bought another one wi-fi receiver, third one. It has *Realtek RTL8763BW*
chip

and *two antennas*. And finally all works fine. I have spent some hours,
using Bluetooth headphones, waiting for problems, but they hadn’t occur.
Small problem is that LTS Kernel 6.1 doesn’t support this device, so I have
used Liquorix kernel, which I have installed earlier. Though, I don’t need
this kernel, as it haven’t helped me with sound interrupts, which was my
hope at first. So… I bought more old Wi-fi receiver with *Realtek
RTL8761BUV* chip with antenna and it also works fine, and also works with
stable 6.1 kernel.

I am glad that situation found its resolution, though it is strange for me
that USB-dongle Bluetooth receiver (I don’t know the exact model) and
receiver on an internal wi-fi adapter (AX 210) have worked so poorly both.
Though I was in the distance not more than 2 meters from receiver.

Thanks for help

пт, 15 мар. 2024 г. в 05:21, Max Nikulin :

> On 14/03/2024 19:06, Jan Krapivin wrote:
> >
> > What do you think about QUANT parameter in */pw-top/*? Can it influence
> > sound quality? I wasn't able to change it with
> >
> > pw-metadata -n settings 0 clock.force-quantum 2048
>
> Sorry, my experience with tuning PipeWire is limited to switching audio
> profiles (A2DP codecs, HSF) from UI.
>
> I think in you case it would be more productive to enable debug logs
> either in bluetoothd or PipeWire to find either the host or the device
> drops or lost connections causing pauses till reconnect.
>
>
>

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 14/03/2024 19:06, Jan Krapivin wrote:


What do you think about QUANT parameter in */pw-top/*? Can it influence 
sound quality? I wasn't able to change it with


pw-metadata -n settings 0 clock.force-quantum 2048


Sorry, my experience with tuning PipeWire is limited to switching audio 
profiles (A2DP codecs, HSF) from UI.


I think in you case it would be more productive to enable debug logs 
either in bluetoothd or PipeWire to find either the host or the device 
drops or lost connections causing pauses till reconnect.

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

> You may try to discriminate hardware/software issues when you comparing
> different laptops by booting various live images (GNOME, xfce, etc.).
>

 I will try... Thank you.

What do you think about QUANT parameter in *pw-top*? Can it influence sound
quality? I wasn't able to change it with

*pw-metadata -n settings 0 clock.force-quantum 2048*

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 13/03/2024 17:43, Jan Krapivin wrote:
While watching */pactl subscribe /*command output, i have noticed that 
there was a change from sink 414 to sink 213 when sound interrupt occurred


"Event 'change' on sink-input #414

Can this information be of any help?


It is expected due to


Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) event25 - Haylou W1 
(AVRCP): device removed
Mar 11 23:14:11 deb pipewire-pulse[1359]: mod.protocol-pulse: client 
0x58b39dbbea40 [GNOME Settings]: ERROR command:-1 (invalid) tag:358 error:25 
(Input/output error)
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) config/udev: 
removing device Haylou W1 (AVRCP)


journalctl running with root privileges may provide more details.

You may try to discriminate hardware/software issues when you comparing 
different laptops by booting various live images (GNOME, xfce, etc.). I 
admit that it is inconvenient since it may require at least a half of an 
hour to test each variant and regular working environment is unavailable.

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

> Run the command as root, but you already have enough keywords to search
> in bug reports and discussions related to PipeWire and pulseaudio. The
> latter may have some workarounds for specific models of headphones.


Thanks, i will try to research this topic.


> PipeWire mailing list or forum may be a better place to discuss the issue.
>

OK

While watching *pactl subscribe *command output, i have noticed that there
was a change from sink 414 to sink 213 when sound interrupt occurred

"Event 'change' on sink-input #414
Event 'change' on sink-input #414
Event 'change' on sink-input #414
Event 'change' on sink-input #213
Event 'change' on sink-input #213
Event 'change' on sink-input #213"

Can this information be of any help?

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 12/03/2024 03:48, Jan Krapivin wrote:


"Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem 
not available: AT+XIAOMI=1,1,102,85,88,27,174"


Just a wild guess, unlikely it is true. Headphones might report battery 
charge level using a vendor protocol extension. 85 and 88 are decreasing 
in later messages.


Sound stream may be interrupted when headphones decide to balance 
battery discharge by switching device that communicates with laptop.


Perhaps messages related to input devices are different because it is 
Wayland session while I use KDE with X11 session, so in my case 
messages are "Watching system buttons" instead of "KEYBOARD...".


You may use --since and --until journalctl options to get system logs 
for the same time intervals you posted.

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 12/03/2024 03:48, Jan Krapivin wrote:


As for journald i have a lot of such errors, but they don't influence 
the audio quality:


"Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem 
not available: AT+XIAOMI=1,1,102,85,88,27,174"


Headphones might expect some response to some of these command and might 
drop connection otherwise.



journalctl -f
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.


Run the command as root, but you already have enough keywords to search 
in bug reports and discussions related to PipeWire and pulseaudio. The 
latter may have some workarounds for specific models of headphones.



Mar 11 23:14:11 deb gsd-media-keys[1744]: Unable to get default sink
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) event25 - Haylou W1 
(AVRCP): device removed
Mar 11 23:14:11 deb gsd-media-keys[1744]: Unable to get default sink
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) event25 - Haylou W1 
(AVRCP): device removed
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (**) Option "fd" "78"
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) UnloadModule: 
"libinput"
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) systemd-logind: 
releasing fd for 13:89
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (EE) systemd-logind: 
failed to release device: Device not taken
Mar 11 23:14:12 deb wireplumber[1357]: set volume 74 failed for transport 
/org/bluez/hci0/dev_9C_19_C2_1B_A7_25/sep4/fd1 (No such property 'Volume')
Mar 11 23:14:14 deb /usr/libexec/gdm-x-session[1449]: (II) config/udev: Adding 
input device Haylou W1 (AVRCP) (/dev/input/event25)
Mar 11 23:14:14 deb /usr/libexec/gdm-x-session[1449]: (**) Haylou W1 (AVRCP): Applying 
InputClass "libinput keyboard catchall"
Mar 11 23:14:14 deb /usr/libexec/gdm-x-session[1449]: (II) Using input driver 
'libinput' for 'Haylou W1 (AVRCP)'


So device disappears for some reason. Perhaps driver receives something 
unexpected, perhaps headphone do not receive something they expect.



Mar 11 23:24:28 deb /usr/libexec/gdm-x-session[1449]: (II) XINPUT: Adding extended input 
device "Haylou W1 (AVRCP)" (type: KEYBOARD, id 20)


Check if similar lines are logged on Mint. KEYBOARD looks a bit strange, 
but perhaps it is normal for GNOME.


PipeWire mailing list or forum may be a better place to discuss the issue.

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

It is strange. I can see in a Debian mailing list an answer

- *From*: Ottavio Caruso 
- *Date*: Mon, 11 Mar 2024 16:50:45 +

"Not sure if this is your case, I had the same problem but I upgraded from
11 to 12. The transition from pulse to pipewire was not smooth. So I nuked
anything *pulse* and *bluetooth* and reinstalled from scratch using the
Debian guide:

https://wiki.debian.org/PipeWire

Is this a brand new installation or an upgrade?"

But i can't see it in my mailbox


*ANSWER*


No, this is a clean new installation. And it looks like i have the
same problem on another laptop with Debian 12 XFCE (Pulseaudio).

But the problem is with *TWO* headsets, so i am in question whats
happening with Debian, because Linux Mint and Android works fine...





пн, 11 мар. 2024 г. в 23:48, Jan Krapivin :

> Hello again. I have used *pactl subscribe *command and i think that in
> the moment of sound interrupt there are the corresponding lines:
>
> "Event 'remove' on sink-input #353
> Event 'new' on sink-input #358
> Event 'change' on sink-input #358"
>
> As for journald i have a lot of such errors, but they don't influence the
> audio quality:
>
> "Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem
> not available: AT+XIAOMI=1,1,102,85,88,27,174"
>
> There are some other mentions of the bluetooth/headphones, but they don't
> meet the moment of sound issues. Full journald -f log is in an attachment.
>
> I must say that i had an opportunity today to test a laptop with Debian 12
> XFCE laptop with Pulseaudio and the problem is the same there. But, as i
> said, on a laptop with Linux Mint XFCE everything is fine. That's strange.
> What is the main difference between Linux Mint and Debian here..?
>
> I also tried Liquorix 6.7 kernel but it didn't help.
>
> Thanks.
>

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

Hello again. I have used *pactl subscribe *command and i think that in the
moment of sound interrupt there are the corresponding lines:

"Event 'remove' on sink-input #353
Event 'new' on sink-input #358
Event 'change' on sink-input #358"

As for journald i have a lot of such errors, but they don't influence the
audio quality:

"Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem
not available: AT+XIAOMI=1,1,102,85,88,27,174"

There are some other mentions of the bluetooth/headphones, but they don't
meet the moment of sound issues. Full journald -f log is in an attachment.

I must say that i had an opportunity today to test a laptop with Debian 12
XFCE laptop with Pulseaudio and the problem is the same there. But, as i
said, on a laptop with Linux Mint XFCE everything is fine. That's strange.
What is the main difference between Linux Mint and Debian here..?

I also tried Liquorix 6.7 kernel but it didn't help.

Thanks.
journalctl -f
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.
  Pass -q to turn off this notice.
Mar 11 21:28:16 deb wireplumber[1357]: RFCOMM receive command but modem not 
available: AT+BTRH?
Mar 11 21:28:16 deb wireplumber[1357]: RFCOMM receive command but modem not 
available: AT+XIAOMI=1,1,102,100,100,27,174
Mar 11 21:29:21 deb systemd[1331]: Started 
app-gnome-gnome\x2dterminal-6829.scope - Application launched by gsd-media-keys.
Mar 11 21:29:21 deb dbus-daemon[1367]: [session uid=1000 pid=1367] Activating 
via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.131' (uid=1000 pid=6829 
comm="gnome-terminal")
Mar 11 21:29:21 deb systemd[1331]: Starting gnome-terminal-server.service - 
GNOME Terminal Server...
Mar 11 21:29:22 deb dbus-daemon[1367]: [session uid=1000 pid=1367] Successfully 
activated service 'org.gnome.Terminal'
Mar 11 21:29:22 deb systemd[1331]: Started gnome-terminal-server.service - 
GNOME Terminal Server.
Mar 11 21:29:22 deb systemd[1331]: Started 
vte-spawn-82cf01f4-467e-44e1-b0e3-19af9cb02a2a.scope - VTE child process 6864 
launched by gnome-terminal-server process 6834.
Mar 11 21:30:27 deb systemd[1331]: Started 
app-gnome-gnome\x2dterminal-7042.scope - Application launched by gsd-media-keys.
Mar 11 21:30:27 deb systemd[1331]: Started 
vte-spawn-6e59a663-467e-40c5-9553-ad6b513aeecb.scope - VTE child process 7048 
launched by gnome-terminal-server process 6834.
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Changing 
wallpaper...
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Current wallpaper 
"a2.jpg"
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Wallpapers in 
queue: 8
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Next slide in 600 
seconds.
Mar 11 21:41:51 deb gnome-shell[1624]: JS ERROR: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 
“IconAccessibleDesc”
   
_promisify/proto[asyncFunc]/

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

пн, 11 мар. 2024 г. в 07:50, Max Nikulin :

>
> Are there anything in journalctl output (executed as root) around these
> events?
>

I guess that no, but i will recheck.


> Is XFCE configured to use pulseaudio or PipeWire as GNOME?
>

Pulseaudio


> Another option might be LC3 codec from Bluetooth LE (5.2 Basic Audio
> Profile) if it is supported by the headphones.
>

Unfortunately it's not supported.


> Either a software/hardware bug or some piece of software disables power
> saving for handsfree/headset profiles to achieve low latency, but for
> A2DP device tries to sleep after some period of time.
>

 Hm, i will try to research that, thank you.

Arch Linux wiki pages have long troubleshooting sections.
>

Yes, I saw but found nothing relatable to my view.

Last resort might be dumping bluetooth traffic, but perhaps it is better
> to ask in some mailing list or forum more close to Bluetooth stack
> developers.
>

I have installed Wireshark, but somehow i can't find bluetooth connection
to capture
(https://forums.debian.net/viewtopic.php?p=795020#p795020)

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

Please, respond to the mailing list.

On 11/03/2024 11:50, Max Nikulin wrote:

https://wiki.debian.org/BluetoothUser/a2dp

Last resort might be dumping bluetooth traffic


The link above has an example

dumpcap -i bluetooth0

Another tool is

hcidump -w /tmp/bt.pcap

However at first I would check logs using journalctl. Maybe debug should 
be enabled for bluez and PipeWire.

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 10/03/2024 21:07, Jan Krapivin wrote:
Hello! I have a problem with sound quality when using bluetooth 
headphones on Debian 12 GNOME.


Every ~20 minutes, sometimes less, sometimes more, sound interrupts for 
a 1-5 seconds with complete silence.


Are there anything in journalctl output (executed as root) around these 
events?


At first I thought that problem can be in the headphones, though it have 
worked fine with Android phone and Linux Mint XFCE on a other laptop.


Is XFCE configured to use pulseaudio or PipeWire as GNOME?

So I bought another headphones with support of different codecs: SBC, 
AAC, and AptX.


Another option might be LC3 codec from Bluetooth LE (5.2 Basic Audio 
Profile) if it is supported by the headphones.


Though in mSBC there are no interruptions. I wonder why mSBC works fine 
and SBC no..?


Either a software/hardware bug or some piece of software disables power 
saving for handsfree/headset profiles to achieve low latency, but for 
A2DP device tries to sleep after some period of time. At least SBC 
allows to decrease bitrate if connection is unreliable. I have read 
somewhere that current drivers can not increase bitrate without 
reconnection. It is just speculations, do not take it too serious.


Arch Linux wiki pages have long troubleshooting sections. Debian ones 
are partially outdated:

https://wiki.debian.org/BluetoothUser
https://wiki.debian.org/BluetoothUser/a2dp

Last resort might be dumping bluetooth traffic, but perhaps it is better 
to ask in some mailing list or forum more close to Bluetooth stack 
developers.

Re: no sound

[Gareth Evans]

> On 19 Jan 2024, at 05:56, Maureen L Thomas  wrote:
> 
> … I used Lucky Backup but I cannot figure out how to restore.  I read the 
> book and it is confusing …

Do you mean this?

https://luckybackup.sourceforge.net/manual.html#restore

If not, is it helpful?

Best wishes,
Gareth

Re: no sound

[David Christensen]

On 1/18/24 21:56, Maureen L Thomas wrote:
I had a1T drive that has my backup on it.  I used Lucky Backup but I 
cannot figure out how to restore.  I read the book and it is confusing. 
I can't just more them over from that HD to the one that is in the 
computer because they are locked.  I will be dragging all future backups 
as you have said.  So much easier. Thank You



What is the make and model of the 1 TB disk?  It is installed in your 
computer?  Is it mounted?  Can you list its contents?



David

Re: no sound

[Maureen L Thomas]

I had a1T drive that has my backup on it.  I used Lucky Backup but I 
cannot figure out how to restore.  I read the book and it is confusing.  
I can't just more them over from that HD to the one that is in the 
computer because they are locked.  I will be dragging all future backups 
as you have said.  So much easier. Thank You


On 1/19/24 12:34 AM, David Christensen wrote:

On 1/18/24 20:08, Maureen L Thomas wrote:
I answered all your questions.  I believe I am using wayland.  I 
appreciate your help.;



YW.  :-)



On 1/18/24 1:12 AM, David Christensen wrote:

On 1/17/24 17:40, Maureen L Thomas wrote:
Well I did a back-up, that didn't work, but I didn't know it at the 
time, 


The back up failed?  :-(

Do you need help with data recovery? 

>

Too late for that.



Ouch.


Please get started doing some kind of backups.  Simple approaches 
include:


1.  Connect a USB drive (flash, HDD, SSD, whatever).  Hopefully, the 
desktop environment will display a pop-up dialog with to mount the USB 
drive file system and display it in a file manager.  Then open another 
file manager.  Drag and drop files from your hard disk drive or solid 
state drive to the USB drive to back up.  Drag them the other way to 
restore.  It helps to create folders with year, month, day-of-month 
names (e.g. 20240118) on the USB drive, so that you can back up the 
same file repeatedly and retain older copies.  Then put the USB drive 
off-site, get another USB drive, and continue with backups.  Every 
month or so, swap the on-site and off-site USB drives.


2.  If your computer has a CD/DVD/BD burner drive, buy a spindle of 
blank discs.  Look for a CD/DVD/BD burner application via your Start 
menu (or whatever it is called).  Burn important files to an optical 
disc periodically, and as needed.  Keep the burned discs off-site.



Another useful strategy is to put your operating system on one HDD/SSD 
and put your data on a second HDD/SSD.  When you need to re-install 
your operating system, you can shut down, disconnect the data drive 
SATA cable, boot installer media, and install the operating system.  
When the new operating system is working, you shutdown, connect the 
data disk SATA cable, boot, and configure the system to mount the data 
drive.



Did you install a graphical desktop?  If so, which one? 


I installed Gnome for the desk top



Okay.



What backport package(s) did you require?


deb https://ftp.debian.org/debian/ bookworm-backports contrib main 
non-free non-free-firmware



Okay.


I now have a system that works but I cannot find any utility to fix 
the top bar the way I want it. Any hints?


If you are using Xfce, right click on a blank area of any panel and 
choose Panel -> Panel Preferences.  This will give you a multi-tab 
app that you can use to customize all the panels.



I use Xfce and am unfamiliar with Gnome.  Perhaps another reader who 
uses the Gnome desktop can provide instructions for customizing the 
desktop interface.



David

Re: no sound

[David Christensen]

On 1/18/24 20:08, Maureen L Thomas wrote:
I answered all your questions.  I believe I am using wayland.  I 
appreciate your help.;



YW.  :-)



On 1/18/24 1:12 AM, David Christensen wrote:

On 1/17/24 17:40, Maureen L Thomas wrote:
Well I did a back-up, that didn't work, but I didn't know it at the 
time, 


The back up failed?  :-(

Do you need help with data recovery?   

>

Too late for that.



Ouch.


Please get started doing some kind of backups.  Simple approaches include:

1.  Connect a USB drive (flash, HDD, SSD, whatever).  Hopefully, the 
desktop environment will display a pop-up dialog with to mount the USB 
drive file system and display it in a file manager.  Then open another 
file manager.  Drag and drop files from your hard disk drive or solid 
state drive to the USB drive to back up.  Drag them the other way to 
restore.  It helps to create folders with year, month, day-of-month 
names (e.g. 20240118) on the USB drive, so that you can back up the same 
file repeatedly and retain older copies.  Then put the USB drive 
off-site, get another USB drive, and continue with backups.  Every month 
or so, swap the on-site and off-site USB drives.


2.  If your computer has a CD/DVD/BD burner drive, buy a spindle of 
blank discs.  Look for a CD/DVD/BD burner application via your Start 
menu (or whatever it is called).  Burn important files to an optical 
disc periodically, and as needed.  Keep the burned discs off-site.



Another useful strategy is to put your operating system on one HDD/SSD 
and put your data on a second HDD/SSD.  When you need to re-install your 
operating system, you can shut down, disconnect the data drive SATA 
cable, boot installer media, and install the operating system.  When the 
new operating system is working, you shutdown, connect the data disk 
SATA cable, boot, and configure the system to mount the data drive.



Did you install a graphical desktop?  If so, which one?  


I installed Gnome for the desk top



Okay.



What backport package(s) did you require?


deb https://ftp.debian.org/debian/ bookworm-backports contrib main non-free 
non-free-firmware



Okay.


I now have a system that works but I cannot find any utility to fix 
the top bar the way I want it. Any hints?


If you are using Xfce, right click on a blank area of any panel and 
choose Panel -> Panel Preferences.  This will give you a multi-tab app 
that you can use to customize all the panels.



I use Xfce and am unfamiliar with Gnome.  Perhaps another reader who 
uses the Gnome desktop can provide instructions for customizing the 
desktop interface.



David

Re: no sound

[Maureen L Thomas]

I answered all your questions.  I believe I am using wayland.  I 
appreciate your help.;


On 1/18/24 1:12 AM, David Christensen wrote:

On 1/17/24 17:40, Maureen L Thomas wrote:
Well I did a back-up, that didn't work, but I didn't know it at the 
time, 



The back up failed?  :-(


Do you need help with data recovery?   Too late for that.


and did a reinstallation from scratch. 



Did you install using debian-12.4.0-amd64-netinst.iso?


Did you install a graphical desktop?  If so, which one?  I installed 
Gnome for the desk top



I now have my sound back 



Good.  :-)


after I added back ports to my repositories. 



Do you mean backports?

https://backports.debian.org/





What backport package(s) did you require? deb 
https://ftp.debian.org/debian/ bookworm-backports contrib main 
non-free non-free-firmware



I now have a system that works but I cannot find any utility to fix 
the top bar the way I want it. Any hints?



If you are using Xfce, right click on a blank area of any panel and 
choose Panel -> Panel Preferences.  This will give you a multi-tab app 
that you can use to customize all the panels.



David

Re: no sound

[David Christensen]

On 1/17/24 17:40, Maureen L Thomas wrote:
Well I did a back-up, that didn't work, but I didn't know it at the 
time, 



The back up failed?  :-(


Do you need help with data recovery?


and did a reinstallation from scratch.  



Did you install using debian-12.4.0-amd64-netinst.iso?


Did you install a graphical desktop?  If so, which one?


I now have my sound back 



Good.  :-)


after I added back ports to my repositories. 



Do you mean backports?

https://backports.debian.org/


What backport package(s) did you require?


I now have a system that 
works but I cannot find any utility to fix the top bar the way I want 
it.  Any hints?



If you are using Xfce, right click on a blank area of any panel and 
choose Panel -> Panel Preferences.  This will give you a multi-tab app 
that you can use to customize all the panels.



David

Re: No Sound With Bookworm

[Valerio Vanni]

Il 27/12/2023 02:04, Thomas George ha scritto:
> Pulseaudio Volume control shows a strong signal audio output but nothing
> reaches the speakers.
>
> This must be a well known problem but I can't find the answer.
I found the same issue. For me, the issue was that timidity-daemon was 
taking exclusive access to audio ports.

And uninstalling timidity-daemon didn't help.

Try this:
-look at control panel ->audio, see the available outputs / profiles
-find pipewire processes and kill them
-after some second, open again control panel -> audio and see if more 
profiles appear
-if they appear, try to select them. For me, it was "analog stereo 
output" profile and "line out" device. Perhaps it's not the same text, 
my install is not in english language".

Re: No Sound With Bookworm

[Pocket]

On 12/26/23 20:04, Thomas George wrote:
Pulseaudio Volume control shows a strong signal audio output but 
nothing reaches the speakers.


This must be a well known problem but I can't find the answer.

Please help

Tom George

I had the same issue with bookworm also. I am using LXQT and pav was not 
setup to output sound to the proper device.


On my system it had two output devices one to send audio through the 
sound card and another to use HDMI.  My speaker are connected to the 
HDMI so I needed to use that. Also make sure the proper audo device is 
not set as backup.





--
Hindi madali ang maging ako

Re: No Sound With Bookworm

[Dan Ritter]

Thomas George wrote: 
> Pulseaudio Volume control shows a strong signal audio output but nothing
> reaches the speakers.
> 
> This must be a well known problem but I can't find the answer.

Check the volume control's tabs for Output Device and
Configuration; frequently PA decides there is no output or it
should go to a recently-plugged-in device with no speakers or
headphones attached, or a muted physical volume control.

Re: no sound on Debian 12

[Michel Verdier]

On 2023-07-25, Bruce Byfield wrote:

> Last week, I installed Debian 12. Since then I've had no sound. I've 
> consulted 
> various pages on the Debian wiki, and found no solution, either with 
> pulseaudio or pipewire. Built-in speakers,  and external features (including 
> bluetooth ones, which are definitely connected) don't work. Any suggestions?

pulseaudio is provided by pipewire-pulse if you use pipewire. And you
should have wireplumber for your user. Check packages and systemd
services.

Re: no sound on Debian 12

[Andreas Rönnquist]

On Tue, 25 Jul 2023 14:54:26 -0700,
Bruce Byfield wrote:

>Last week, I installed Debian 12. Since then I've had no sound. I've consulted 
>various pages on the Debian wiki, and found no solution, either with 
>pulseaudio or pipewire. Built-in speakers,  and external features (including 
>bluetooth ones, which are definitely connected) don't work. Any suggestions?

Are you sure you have no sound at all, and not just have really really
low volume?

I have a similar problem where I need to raise the volume in alsamixer
between each boot (or switch between different users) - I have posted
about it here on debian-user, but no replies yet. 

-- Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net

Re: no sound after installing pulseaudio

[Joe B]

What worked for me was running alsamixer from the terminal and unmuteing the 
main control and turning the volume all the way up. rebooted then tested with 
pavucontrol..

Hope this helps

> On Dec 23, 2022, at 5:42 AM, lou  wrote:
> 
> Christoph, your "pactl list" command didn't work because i didn't reboot 
> buster after installing pulseaudio, Thanks anyway!
> 
> 

Re: no sound after installing pulseaudio

[Jude DaShiell]

I'm living on the command line most of the time.  If sound doesn't work
over here for me since I need to use a screen reader, the computer becomes
a paperweight.  I'm glad that fix worked for you and I should have told
you to do that command as root.  If that command ever fails, alsa got
locked up and you need to locate alsa.lck in the lock directory and delete
it then run the amixer command again.  I've had that happen earlier myself
from time to time and figure it's a good bit of information to have as a
back out method.



Jude  "There are four boxes to be used in
defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.

On Fri, 23 Dec 2022, lou wrote:

> Thank Jude!
>
> i try your command anyway though i have said i give up
>
> i install pulseaudio again and have to reboot to get it to work
>
> then i run your command, it solves my problem, Thanks!
>
>
>

Re: no sound after installing pulseaudio

[lou]

Christoph, your "pactl list" command didn't work because i didn't reboot 
buster after installing pulseaudio, Thanks anyway!

Re: no sound after installing pulseaudio

[lou]

Thank Jude!

i try your command anyway though i have said i give up

i install pulseaudio again and have to reboot to get it to work

then i run your command, it solves my problem, Thanks!

Re: no sound after installing pulseaudio

[Jude DaShiell]

Alternatively,
amixer set Master 100% unmute



Jude 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.

On Fri, 23 Dec 2022, Christoph Brinkhaus wrote:

> Am Fri, Dec 23, 2022 at 09:12:28AM +0800 schrieb lou:
>
> Hello Lou,
>
> > i am running buster and install pulseaudio
> > to let pulseaudio take effect i have to reboot
> > but there's no sound though pavucontrol seems ok
> > (pavucontrol shows sound is playing properly)
> > to get sound back, i have to remove pulseaudio and reboot
>
> With "pactl list" or "pcctl list short" you can identify some cryptic
> address of your sound card.
>
> With something as (taken from my system)
> "pactl set-sink-volume alsa_output.pci-_00_14.2.analog-stereo +2%"
> you can adjust the volume.
>
> Or you simple try alsamixer which comes with some ncurses looking GUI.
>
> Kind regards,
> Christoph
>

Re: no sound after installing pulseaudio

[lou]

Thank Christoph and Andrew!

i can use stretch if i need pulseaudio

my problem is so strange that i give up

ps: Andrew, my experience shows that new isn't always better than old. 
many wifi adapter makers on Chinese market today support Windows XP for 
their new products

Re: no sound after installing pulseaudio

[Christoph Brinkhaus]

Am Fri, Dec 23, 2022 at 06:08:01PM +0800 schrieb lou:
> Thank Jude and Christoph!

Hi Lou.
 
> i run "pactl list":
> 
> Connection failure: Connection refused
> pa_context_connect() failed: Connection refused

I have no idea why the message comes from but also how pulseaudio
communicates with the rest of the system.

Please check if pulseaudio is really running by checking with ps.
If the communication is running via dbus check if dbus is running.
If the communication is via TCP or UPD and localhost please check if
there is no firewall rule which blocks the traffic.

> but in stretch, pulseaudio works after i install it

For me its has been working using Bullseye out fo the box, too.

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.

Re: no sound after installing pulseaudio

[Andrew M.A. Cater]

On Fri, Dec 23, 2022 at 06:08:01PM +0800, lou wrote:
> Thank Jude and Christoph!
> 
> i run "pactl list":
> 
> Connection failure: Connection refused
> pa_context_connect() failed: Connection refused
> 
> but in stretch, pulseaudio works after i install it
> 
>

Hi Lou,

As always, you may be better working with the most up to date stable Debian
release. Stretch is getting very old now, buster is oldstable and the
next major release is due in a few months.

Please consider updating to at least Debian 11 (bullseye).

With every good wish, as ever,

Andy Cater

Re: no sound after installing pulseaudio

[lou]

Thank Jude and Christoph!

i run "pactl list":

Connection failure: Connection refused
pa_context_connect() failed: Connection refused

but in stretch, pulseaudio works after i install it

Re: no sound after installing pulseaudio

[Christoph Brinkhaus]

Am Fri, Dec 23, 2022 at 09:12:28AM +0800 schrieb lou:

Hello Lou,

> i am running buster and install pulseaudio
> to let pulseaudio take effect i have to reboot
> but there's no sound though pavucontrol seems ok
> (pavucontrol shows sound is playing properly)
> to get sound back, i have to remove pulseaudio and reboot

With "pactl list" or "pcctl list short" you can identify some cryptic
address of your sound card.

With something as (taken from my system)
"pactl set-sink-volume alsa_output.pci-_00_14.2.analog-stereo +2%"
you can adjust the volume.

Or you simple try alsamixer which comes with some ncurses looking GUI.

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.

Re: no sound after installing pulseaudio

[Jude DaShiell]

It's necessary to unmute resources in pulseaudio and I don't know how to
do that.  No problem with alsa but pulseaudio given naming conventions for
me was opaque.  You may have good luck with pipewire but be prepared to
install wireplumber if necessary.


Jude 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.

On Fri, 23 Dec 2022, lou wrote:

> i am running buster and install pulseaudio
>
> to let pulseaudio take effect i have to reboot
>
> but there's no sound though pavucontrol seems ok
>
> (pavucontrol shows sound is playing properly)
>
> to get sound back, i have to remove pulseaudio and reboot
>
> Thanks!
>
>
>

Re: Bluetooth sound problems

[Peter von Kaehne]

> On 9 Nov 2022, at 15:12, Charles Curley  
> wrote:
> 
> On Wed, 9 Nov 2022 09:52:15 +
> Peter von Kaehne  wrote:
> 
>> My laptop (Thinkpad Yoga11e first gen) on Debian Sid is showing for
>> last few months diverse and variable sound problems.l, particularly
>> with using Bluetooth speakers, but also with Airplay. 
> 
> You might see what tips or tricks you can find at
> https://www.thinkwiki.org/wiki/ThinkWiki and at
> https://linux-hardware.org.
> 

Thank you. Both of these have no relevant information. Also, things _did_ work, 
they do not now, but drivers are present and working, 

My question is how to approach debugging the nexus of Bluetooth, Pipewire, 
Pulseaudio and whatever controls permissions to access here. 

Peter
> 
> -- 
> Does anybody read signatures any more?
> 
> https://charlescurley.com
> https://charlescurley.com/blog/
> 

Re: Bluetooth sound problems

[Charles Curley]

On Wed, 9 Nov 2022 09:52:15 +
Peter von Kaehne  wrote:

> My laptop (Thinkpad Yoga11e first gen) on Debian Sid is showing for
> last few months diverse and variable sound problems.l, particularly
> with using Bluetooth speakers, but also with Airplay. 

You might see what tips or tricks you can find at
https://www.thinkwiki.org/wiki/ThinkWiki and at
https://linux-hardware.org.



-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: USB sound device present but visible in ‘alsamixer’

[Pankaj Jangid]

Nicholas Geovanis  writes:

>> I am trying to make it work; so here is the update.
>>
>> I tried to experiment with my machine and found that if I plug-out and
>> plug-in the USB sound card again, it is not shown by "aplay -l" command
>> as normal user. But when I do "sudo aplay -l" it lists the USB
>> device. But I am part of "audio" group. "groups" command output:
>>
>> --8<---cut here---start->8---
>> ankaj@anant:~$ groups
>> pankaj cdrom floppy sudo audio dip video plugdev netdev bluetooth scanner
>> docker
>> --8<---cut here---end--->8---
>>
>> I don’t know what other configuration is required to list my card using
>> "aplay -l" as a normal user?
>
>
> You may need to give normal users added privileges. Or it may be that you
> need to set your running group or user identity to something else in order
> to use aplay effectively. Could that be the group named audio?
>
> See help for the newgrp command. Or just as you have done, try to craft the
> right sudo command to invoke it the way you want. Then you could add a
> shorthand to it in sudoers or create a shell alias accordingly.
>
> Or, not recommended, you could change the aplay executable or front-end to
> it in order to make it a set[ug]id executable.
>

It just upgraded my kernel using "make deb-pkg" in the upstream kernel
and installed it. The sound problem is gone.

Re: USB sound device present but visible in ‘alsamixer’

[Nicholas Geovanis]

On Sun, Feb 6, 2022, 9:42 AM Pankaj Jangid  wrote:

> Pankaj Jangid  writes:
>
> > When I boot system afresh, the card is visible in the ‘alsamixer’ and in
> > Gnome settings as well. Shown as “Blue” S/PDIF input and output
> > devices. But when system wakes up from sleep (suspended), it doesn’t
> > show the devices.
> >
> > However, ‘lsusb’ shows it and ‘/proc/asound/cards’ has an entry. But
> > these devices (mic and speaker) are not taking any input or producing
> > sound. Because they are not visible to Gnome and ‘alsamixer’.
> >
> > pankaj@anant:~$ lsusb
> > ...
> > Bus 001 Device 003: ID 046d:0ab7 Logitech, Inc. Blue Microphones
> > ...
> > pankaj@anant:~$ cat /proc/asound/cards
> > ...
> >  3 [Microphones]: USB-Audio - Blue Microphones
> >   Generic Blue Microphones at usb-:2a:00.1-2,
> high speed
> > ...
>
> I am trying to make it work; so here is the update.
>
> I tried to experiment with my machine and found that if I plug-out and
> plug-in the USB sound card again, it is not shown by "aplay -l" command
> as normal user. But when I do "sudo aplay -l" it lists the USB
> device. But I am part of "audio" group. "groups" command output:
>
> --8<---cut here---start->8---
> ankaj@anant:~$ groups
> pankaj cdrom floppy sudo audio dip video plugdev netdev bluetooth scanner
> docker
> --8<---cut here---end--->8---
>
> I don’t know what other configuration is required to list my card using
> "aplay -l" as a normal user?


You may need to give normal users added privileges. Or it may be that you
need to set your running group or user identity to something else in order
to use aplay effectively. Could that be the group named audio?

See help for the newgrp command. Or just as you have done, try to craft the
right sudo command to invoke it the way you want. Then you could add a
shorthand to it in sudoers or create a shell alias accordingly.

Or, not recommended, you could change the aplay executable or front-end to
it in order to make it a set[ug]id executable.

It lists the card when I reboot the
> machine. But not when I plug-out and plug-in again. Any hints for this?
>
> This could be root cause of my original problem i.e. no sound after
> sleep and wake-up.
>
>
>

Re: No sound in Flatpaks

[gene heskett]

On Sunday, February 6, 2022 7:15:55 AM EST A_Man_Without_Clue wrote:
> On 2/6/22 01:23, c. marlow wrote:
> > On Saturday 05 February 2022 06:23:47 am gene heskett wrote:
> >> That, in the case of firefox is not a flatpack issue, debians latest
> >> is the same, every video played has muted sound until you find the
> >> gd mixer and unmute and bring up the gain of that channel, even if
> >> you reload the page to play it again, you have to unmute and slide
> >> the gain back up, by then the gd video is over in many cases. Are
> >> they trying to protect us from what MSMnews considers a lie?  Acts
> >> like censorship to me,  And I am about to chattr +i whatever
> >> controls that if I can find it.
> > 
> > lol.
> > 
> > Chris
> 
> I'm not using Telegram or firefox Flatpak version but I use Flatpak
> version of Wire and Signal apps and they are working just fine with
> audio.
> 
> I also do not have any problem with audio with Firefox available from
> Debian Bullseye repo.
> 
> A.M.W.C.
> 
That is where I got this firefox-esr, and its a genuine PITA.
The good browser has been discoed, diseenter. Firefox-esr seems to think 
its reason to exist is to make sure all the popups work so they can count 
more clicks, it for sure is not to please the user.
> .


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: USB sound device present but visible in ‘alsamixer’

[Pankaj Jangid]

Pankaj Jangid  writes:

> When I boot system afresh, the card is visible in the ‘alsamixer’ and in
> Gnome settings as well. Shown as “Blue” S/PDIF input and output
> devices. But when system wakes up from sleep (suspended), it doesn’t
> show the devices.
>
> However, ‘lsusb’ shows it and ‘/proc/asound/cards’ has an entry. But
> these devices (mic and speaker) are not taking any input or producing
> sound. Because they are not visible to Gnome and ‘alsamixer’.
>
> pankaj@anant:~$ lsusb
> ...
> Bus 001 Device 003: ID 046d:0ab7 Logitech, Inc. Blue Microphones
> ...
> pankaj@anant:~$ cat /proc/asound/cards
> ...
>  3 [Microphones]: USB-Audio - Blue Microphones
>   Generic Blue Microphones at usb-:2a:00.1-2, high 
> speed
> ...

I am trying to make it work; so here is the update.

I tried to experiment with my machine and found that if I plug-out and
plug-in the USB sound card again, it is not shown by "aplay -l" command
as normal user. But when I do "sudo aplay -l" it lists the USB
device. But I am part of "audio" group. "groups" command output:

--8<---cut here---start->8---
ankaj@anant:~$ groups
pankaj cdrom floppy sudo audio dip video plugdev netdev bluetooth scanner docker
--8<---cut here---end--->8---

I don’t know what other configuration is required to list my card using
"aplay -l" as a normal user? It lists the card when I reboot the
machine. But not when I plug-out and plug-in again. Any hints for this?

This could be root cause of my original problem i.e. no sound after
sleep and wake-up.

Re: No sound in Flatpaks

[A_Man_Without_Clue]

On 2/6/22 01:23, c. marlow wrote:



On Saturday 05 February 2022 06:23:47 am gene heskett wrote:


That, in the case of firefox is not a flatpack issue, debians latest is
the same, every video played has muted sound until you find the gd mixer
and unmute and bring up the gain of that channel, even if you reload the
page to play it again, you have to unmute and slide the gain back up, by
then the gd video is over in many cases. Are they trying to protect us
from what MSMnews considers a lie?  Acts like censorship to me,  And I am
about to chattr +i whatever controls that if I can find it.



lol.

Chris




I'm not using Telegram or firefox Flatpak version but I use Flatpak 
version of Wire and Signal apps and they are working just fine with audio.


I also do not have any problem with audio with Firefox available from 
Debian Bullseye repo.


A.M.W.C.

Re: No sound in Flatpaks

[c. marlow]

On Saturday 05 February 2022 06:23:47 am gene heskett wrote:

> That, in the case of firefox is not a flatpack issue, debians latest is
> the same, every video played has muted sound until you find the gd mixer
> and unmute and bring up the gain of that channel, even if you reload the
> page to play it again, you have to unmute and slide the gain back up, by
> then the gd video is over in many cases. Are they trying to protect us
> from what MSMnews considers a lie?  Acts like censorship to me,  And I am
> about to chattr +i whatever controls that if I can find it.


lol.

Chris

Re: No sound in Flatpaks

[gene heskett]

On Saturday, February 5, 2022 7:07:18 AM EST c. marlow wrote:
> Fresh install of Debian 11 ( installed yesterday)
> TDE 14 ( Trinity Desktop)
> 
> Hi,
> 
> I am having problems with flatpak installations.
> 
> Firefox, VLC, and Telegram has no sound at all when you try to play
> something.
> 
> But reverting back to the repo version of Firefox ESR and VLC, the
> sound works fine.
> 
> I need to keep Telegram as a flatpak because the repo version when you
> sign into it, it will ask you to enter the code that they texted you
> and then as soon as you enter it, it will say that, that version of
> Telegram is too old and is no longer supported and that I need to
> update it.
> 
> How do I fix this?
> 
> I tried googling this issue, but I can't find anything about flatpaks
> not having any sound in TDE.
> 
That, in the case of firefox is not a flatpack issue, debians latest is 
the same, every video played has muted sound until you find the gd mixer 
and unmute and bring up the gain of that channel, even if you reload the 
page to play it again, you have to unmute and slide the gain back up, by 
then the gd video is over in many cases. Are they trying to protect us 
from what MSMnews considers a lie?  Acts like censorship to me,  And I am 
about to chattr +i whatever controls that if I can find it.
> Thanks,
> Chris
> 
> .


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: USB sound device present but NOT visible in ‘alsamixer’

[Jude DaShiell]

When you stop pulseaudio, you did a good thing.  since pulseaudio was
started again, you're probably going to have to mess around in pactl to
get this fixed if that will even be possible.


On Mon, 31 Jan 2022, Pankaj Jangid wrote:

> Andrei POPESCU  writes:
>
> >> Thanks Andrei. I followed the following steps:
> >>
> >> 1. Found that it is pulseaudio that is blocking the module unload.
> >> 2. systemctl --user stop pulseaudio.socket
> >> 3. systemctl --user stop pulseaudio.service
> >> 4. Verified that now nothing is blocking snd_usb_audio (using lsof)
> >> 5. Unloaded module using "modprobe -r"
> >> 6. Loaded again using "modeprob"
> >> 7. Started pulseaudio again
> >>
> >> Still the device is not listed in alsamixer and hence cannot play.
> >>
> >> "alsactl init" also producing same errors as before.
> >
> > Try also unplugging the device after removing the module.
> >
>
> After step 5, I unplugged the device and plugged it again and then
> followed 6, 7. Now the interval sound card is also not visible; that was
> showing as generic usb.
>
> Regards ~Pankaj
>
>
>

Re: USB sound device present but NOT visible in ‘alsamixer’

[Pankaj Jangid]

Andrei POPESCU  writes:

>> Thanks Andrei. I followed the following steps:
>> 
>> 1. Found that it is pulseaudio that is blocking the module unload.
>> 2. systemctl --user stop pulseaudio.socket
>> 3. systemctl --user stop pulseaudio.service
>> 4. Verified that now nothing is blocking snd_usb_audio (using lsof)
>> 5. Unloaded module using "modprobe -r"
>> 6. Loaded again using "modeprob"
>> 7. Started pulseaudio again
>> 
>> Still the device is not listed in alsamixer and hence cannot play.
>> 
>> "alsactl init" also producing same errors as before.
>
> Try also unplugging the device after removing the module.
>

After step 5, I unplugged the device and plugged it again and then
followed 6, 7. Now the interval sound card is also not visible; that was
showing as generic usb.

Regards ~Pankaj

Re: USB sound device present but NOT visible in ‘alsamixer’

[Andrei POPESCU]

On Du, 30 ian 22, 14:58:29, Pankaj Jangid wrote:
> Andrei POPESCU  writes:
> 
> > Something is keeping the module busy, but according to lsmod it's not 
> > another module.
> >
> > In case you get any output from
> >
> > lsof | grep /dev/snd
> >
> > (this needs root or sudo)
> >
> > try stopping the applications listed in the first column (the second 
> > column is the process number).
> 
> Thanks Andrei. I followed the following steps:
> 
> 1. Found that it is pulseaudio that is blocking the module unload.
> 2. systemctl --user stop pulseaudio.socket
> 3. systemctl --user stop pulseaudio.service
> 4. Verified that now nothing is blocking snd_usb_audio (using lsof)
> 5. Unloaded module using "modprobe -r"
> 6. Loaded again using "modeprob"
> 7. Started pulseaudio again
> 
> Still the device is not listed in alsamixer and hence cannot play.
> 
> "alsactl init" also producing same errors as before.

Try also unplugging the device after removing the module.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: USB sound device present but NOT visible in ‘alsamixer’

[Pankaj Jangid]

Andrei POPESCU  writes:

> Something is keeping the module busy, but according to lsmod it's not 
> another module.
>
> In case you get any output from
>
> lsof | grep /dev/snd
>
> (this needs root or sudo)
>
> try stopping the applications listed in the first column (the second 
> column is the process number).

Thanks Andrei. I followed the following steps:

1. Found that it is pulseaudio that is blocking the module unload.
2. systemctl --user stop pulseaudio.socket
3. systemctl --user stop pulseaudio.service
4. Verified that now nothing is blocking snd_usb_audio (using lsof)
5. Unloaded module using "modprobe -r"
6. Loaded again using "modeprob"
7. Started pulseaudio again

Still the device is not listed in alsamixer and hence cannot play.

"alsactl init" also producing same errors as before.

Regards ~Pankaj

Re: USB sound device present but NOT visible in ‘alsamixer’

[Pankaj Jangid]

Jude DaShiell  writes:

> rm /var/lock/asound.state.lock
>
>
As I stated in a previous reply, I had tried to remove this file and
then did "alsactl init" but no positive result. Just this output

--8<---cut here---start->8---
pankaj@anant:~$ sudo alsactl init
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA 
ATI HDMI at 0xfca6 irq 118)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use 
case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" 
"0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA 
ATI HDMI at 0xfce6 irq 120)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:1 use 
case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" 
"0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model 
(HD-Audio Generic at 0xfcd0 irq 122)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use 
case configuration -6
Found hardware: "HDA-Intel" "" "" "0x1462" "0xed54"
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:3 use 
case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB046d:0ab7" "" ""
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:4 use 
case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB0db0:a073" "" ""
Hardware is initialized using a generic method
--8<---cut here---end--->8---

Regards ~Pankaj

Re: USB sound device present but NOT visible in ‘alsamixer’

[Jude DaShiell]

rm /var/lock/asound.state.lock


On Sun, 30 Jan 2022, Pankaj Jangid wrote:

> Jude DaShiell  writes:
>
> > alsactl init I think will find everything.
> >
>
> Then there is something else that is not letting "alsactl init" to
> function properly; lock file as you suggested. But I couldn?t find
> anything other than "/var/lock/asound.state.lock".
>
>
>

Re: USB sound device present but NOT visible in ‘alsamixer’

[Andrei POPESCU]

On Du, 30 ian 22, 12:47:27, Pankaj Jangid wrote:
> Andrei POPESCU  writes:
> 
> >> During the boot process, the system detects everything. So there must be
> >> something in the init sequence that I can trigger manually.
> >
> > You can try to unload and reload the corresponding kernel module. Check 
> > the output of
> >
> > lsmod | grep snd
> >
> > (it's probably snd-usb-audio)
> >
> > If it works it might be possible to add the module to some list so that 
> > it is removed on suspend and loaded on resume.
> 
> Thanks Andrei.
> 
> "lsmod|grep snd" results in,
> 
> --8<---cut here---start->8---
> pankaj@anant:~$ sudo lsmod |grep snd
> snd_usb_audio 315392  3
> snd_usbmidi_lib40960  1 snd_usb_audio
> snd_rawmidi45056  1 snd_usbmidi_lib
> snd_seq_device 16384  1 snd_rawmidi
> mc 61440  1 snd_usb_audio
> snd_hda_codec_hdmi 73728  2
> snd_hda_intel  57344  3
> snd_intel_dspcfg   28672  1 snd_hda_intel
> soundwire_intel45056  1 snd_intel_dspcfg
> snd_soc_core  315392  1 soundwire_intel
> snd_compress   32768  1 snd_soc_core
> snd_hda_codec 172032  2 snd_hda_codec_hdmi,snd_hda_intel
> snd_hda_core  110592  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
> snd_hwdep  16384  2 snd_usb_audio,snd_hda_codec
> snd_pcm   135168  8 
> snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,soundwire_intel,snd_compress,snd_soc_core,snd_hda_core
> snd_timer  49152  1 snd_pcm
> snd   110592  24 
> snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi
> soundcore  16384  1 snd
> usbcore   323584  6 
> xhci_hcd,snd_usb_audio,usbhid,snd_usbmidi_lib,btusb,xhci_pci
> --8<---cut here---end--->8---
> 
> when I say "modprobe -r snd_usb_audio". It says "Module snd_usb_audio is
> in use". I tried with "-f" option as well. Still cannot unload. Then I
> tried to it again after "alsactl kill quit"; but still cannot unload.

Something is keeping the module busy, but according to lsmod it's not 
another module.

In case you get any output from

lsof | grep /dev/snd

(this needs root or sudo)

try stopping the applications listed in the first column (the second 
column is the process number).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: USB sound device present but NOT visible in ‘alsamixer’

[Pankaj Jangid]

Andrei POPESCU  writes:

>> During the boot process, the system detects everything. So there must be
>> something in the init sequence that I can trigger manually.
>
> You can try to unload and reload the corresponding kernel module. Check 
> the output of
>
> lsmod | grep snd
>
> (it's probably snd-usb-audio)
>
> If it works it might be possible to add the module to some list so that 
> it is removed on suspend and loaded on resume.

Thanks Andrei.

"lsmod|grep snd" results in,

--8<---cut here---start->8---
pankaj@anant:~$ sudo lsmod |grep snd
snd_usb_audio 315392  3
snd_usbmidi_lib40960  1 snd_usb_audio
snd_rawmidi45056  1 snd_usbmidi_lib
snd_seq_device 16384  1 snd_rawmidi
mc 61440  1 snd_usb_audio
snd_hda_codec_hdmi 73728  2
snd_hda_intel  57344  3
snd_intel_dspcfg   28672  1 snd_hda_intel
soundwire_intel45056  1 snd_intel_dspcfg
snd_soc_core  315392  1 soundwire_intel
snd_compress   32768  1 snd_soc_core
snd_hda_codec 172032  2 snd_hda_codec_hdmi,snd_hda_intel
snd_hda_core  110592  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_hwdep  16384  2 snd_usb_audio,snd_hda_codec
snd_pcm   135168  8 
snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,soundwire_intel,snd_compress,snd_soc_core,snd_hda_core
snd_timer  49152  1 snd_pcm
snd   110592  24 
snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi
soundcore  16384  1 snd
usbcore   323584  6 
xhci_hcd,snd_usb_audio,usbhid,snd_usbmidi_lib,btusb,xhci_pci
--8<---cut here---end--->8---

when I say "modprobe -r snd_usb_audio". It says "Module snd_usb_audio is
in use". I tried with "-f" option as well. Still cannot unload. Then I
tried to it again after "alsactl kill quit"; but still cannot unload.

Also "alsactl init" is producing some errors also. I shared in my
previous email. Copying here again for the context.

--8<---cut here---start->8---
pankaj@anant:~$ sudo alsactl init
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA 
ATI HDMI at 0xfca6 irq 102)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use 
case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" 
"0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA 
ATI HDMI at 0xfce6 irq 120)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:1 use 
case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" 
"0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model 
(HD-Audio Generic at 0xfcd0 irq 122)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use 
case configuration -6
Found hardware: "HDA-Intel" "" "" "0x1462" "0xed54"
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:3 use 
case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB046d:0ab7" "" ""
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:4 use 
case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB0db0:a073" "" ""
Hardware is initialized using a generic method
--8<---cut here---end--->8---

What other options may I try?


Regards ~Pankaj

Re: USB sound device present but NOT visible in ‘alsamixer’

[Andrei POPESCU]

On Du, 30 ian 22, 11:02:34, Pankaj Jangid wrote:
> Jude DaShiell  writes:
> 
> > alsactl --init
> > may help.
> > However alsa makes .lock files in /var/lock/alsa and you may find it
> > helpful to delete the lock file first then once card is set run alsactl
> > store.  Those lock files sometimes prevent alsa from doing a proper
> > detection and change.
> >
> Thanks Jude, for the reply.
> 
> On my installation there is no ‘--init’ option. But it has ‘init’
> command. I just tried that ‘alsactl init’. And there is no
> ‘/var/lock/alsa’ directory. But there is
> ‘/var/lock/asound.state.lock’. I removed this and tried with ‘alsactl
> init’ again. But no positive results in both cases.
> 
> During the boot process, the system detects everything. So there must be
> something in the init sequence that I can trigger manually.

You can try to unload and reload the corresponding kernel module. Check 
the output of

lsmod | grep snd

(it's probably snd-usb-audio)

If it works it might be possible to add the module to some list so that 
it is removed on suspend and loaded on resume.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: USB sound device present but NOT visible in ‘alsamixer’

[Pankaj Jangid]

Pankaj Jangid  writes:

> Jude DaShiell  writes:
>
>> alsactl init I think will find everything.
>>
>
> Then there is something else that is not letting "alsactl init" to
> function properly; lock file as you suggested. But I couldn’t find
> anything other than "/var/lock/asound.state.lock".

I should have attached this before as well. The "alsactl init" command
is producing error messages as well. See this,

--8<---cut here---start->8---
pankaj@anant:~$ sudo alsactl init
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA 
ATI HDMI at 0xfca6 irq 102)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use 
case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" 
"0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA 
ATI HDMI at 0xfce6 irq 120)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:1 use 
case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" 
"0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model 
(HD-Audio Generic at 0xfcd0 irq 122)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use 
case configuration -6
Found hardware: "HDA-Intel" "" "" "0x1462" "0xed54"
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:3 use 
case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB046d:0ab7" "" ""
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:4 use 
case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB0db0:a073" "" ""
Hardware is initialized using a generic method
--8<---cut here---end--->8---

Re: USB sound device present but NOT visible in ‘alsamixer’

[Pankaj Jangid]

Jude DaShiell  writes:

> alsactl init I think will find everything.
>

Then there is something else that is not letting "alsactl init" to
function properly; lock file as you suggested. But I couldn’t find
anything other than "/var/lock/asound.state.lock".

Re: USB sound device present but NOT visible in ‘alsamixer’

[Jude DaShiell]

alsactl init I think will find everything.


On Sun, 30 Jan 2022, Pankaj Jangid wrote:

> Jude DaShiell  writes:
>
> > alsactl --init
> > may help.
> > However alsa makes .lock files in /var/lock/alsa and you may find it
> > helpful to delete the lock file first then once card is set run alsactl
> > store.  Those lock files sometimes prevent alsa from doing a proper
> > detection and change.
> >
> Thanks Jude, for the reply.
>
> On my installation there is no ?--init? option. But it has ?init?
> command. I just tried that ?alsactl init?. And there is no
> ?/var/lock/alsa? directory. But there is
> ?/var/lock/asound.state.lock?. I removed this and tried with ?alsactl
> init? again. But no positive results in both cases.
>
> During the boot process, the system detects everything. So there must be
> something in the init sequence that I can trigger manually.
>
> Regards ~Pankaj
>
>

Re: USB sound device present but NOT visible in ‘alsamixer’

[Pankaj Jangid]

Jude DaShiell  writes:

> alsactl --init
> may help.
> However alsa makes .lock files in /var/lock/alsa and you may find it
> helpful to delete the lock file first then once card is set run alsactl
> store.  Those lock files sometimes prevent alsa from doing a proper
> detection and change.
>
Thanks Jude, for the reply.

On my installation there is no ‘--init’ option. But it has ‘init’
command. I just tried that ‘alsactl init’. And there is no
‘/var/lock/alsa’ directory. But there is
‘/var/lock/asound.state.lock’. I removed this and tried with ‘alsactl
init’ again. But no positive results in both cases.

During the boot process, the system detects everything. So there must be
something in the init sequence that I can trigger manually.

Regards ~Pankaj

Re: USB sound device present but NOT visible in ‘alsamixer’

[Jude DaShiell]

alsactl --init
may help.
However alsa makes .lock files in /var/lock/alsa and you may find it
helpful to delete the lock file first then once card is set run alsactl
store.  Those lock files sometimes prevent alsa from doing a proper
detection and change.


On Sun, 30 Jan 2022, Pankaj Jangid wrote:

> "Andrew M.A. Cater"  writes:
>
> >> Pankaj Jangid  writes:
> >>
> >> > When I boot system afresh, the card is visible in the ?alsamixer? and in
> >> > Gnome settings as well. Shown as ?Blue? S/PDIF input and output
> >> > devices. But when system wakes up from sleep (suspended), it doesn?t
> >> > show the devices.
> >> >
> > It might be nothing more than the power handling, sleep modes and USB
> > enumeration after a laptop goes to sleep.
> >
> > If you unplug/replug the USB plug which is the external sound card, is
> > it magically recognised again?
>
> Thanks Andy, for the reply. I really appreciate this gesture.
>
> And I am sorry I wasn?t complete in the original email. I had tried to
> unplug and replug. But that also doesn?t list the device in ?alsamixer?
> and hence doesn?t work after a suspend/wakeup operation.
>
> Is there a way to force the scan of USB sound devices manually if that
> is not happening automatically? As I had posted earlier that ?lsusb? and
> ?cat /proc/asound/cards? do list the device. It is just that ALSA is not
> seeing it.
>
>
> Regards ~Pankaj
>
>

Re: USB sound device present but NOT visible in ‘alsamixer’

[Pankaj Jangid]

"Andrew M.A. Cater"  writes:

>> Pankaj Jangid  writes:
>> 
>> > When I boot system afresh, the card is visible in the ‘alsamixer’ and in
>> > Gnome settings as well. Shown as “Blue” S/PDIF input and output
>> > devices. But when system wakes up from sleep (suspended), it doesn’t
>> > show the devices.
>> >
> It might be nothing more than the power handling, sleep modes and USB 
> enumeration after a laptop goes to sleep.
>
> If you unplug/replug the USB plug which is the external sound card, is
> it magically recognised again?

Thanks Andy, for the reply. I really appreciate this gesture.

And I am sorry I wasn’t complete in the original email. I had tried to
unplug and replug. But that also doesn’t list the device in ‘alsamixer’
and hence doesn’t work after a suspend/wakeup operation.

Is there a way to force the scan of USB sound devices manually if that
is not happening automatically? As I had posted earlier that ‘lsusb’ and
‘cat /proc/asound/cards’ do list the device. It is just that ALSA is not
seeing it.


Regards ~Pankaj

Re: USB sound device present but NOT visible in ‘alsamixer’

[Andrew M.A. Cater]

On Sat, Jan 29, 2022 at 10:28:32PM +0530, Pankaj Jangid wrote:
> Sorry for the Wrong subject line earlier.
> 
> Pankaj Jangid  writes:
> 
> > I have setup a new system. Apart from the display related issue, that I
> > had posted in another thread, I am facing an issue related to my
> > external ‘Yeti Blue’ sound card. I use it as Mic and Monitor audio.
> >
> > pankaj@anant:~$ lsb_release -a
> > No LSB modules are available.
> > Distributor ID: Debian
> > Description:Debian GNU/Linux 11 (bullseye)
> > Release:11
> > Codename:   bullseye
> > pankaj@anant:~$ uname -a
> > Linux anant 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 
> > GNU/Linux
> >
> >
> > When I boot system afresh, the card is visible in the ‘alsamixer’ and in
> > Gnome settings as well. Shown as “Blue” S/PDIF input and output
> > devices. But when system wakes up from sleep (suspended), it doesn’t
> > show the devices.
> >
> > However, ‘lsusb’ shows it and ‘/proc/asound/cards’ has an entry. But
> > these devices (mic and speaker) are not taking any input or producing
> > sound. Because they are not visible to Gnome and ‘alsamixer’.
> >
> > pankaj@anant:~$ lsusb
> > Bus 006 Device 002: ID 2109:0813 VIA Labs, Inc. VL813 Hub
> > Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > Bus 005 Device 002: ID 2109:2813 VIA Labs, Inc. VL813 Hub
> > Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
> > Bus 003 Device 002: ID 0db0:a073 Micro Star International USB Audio
> > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > Bus 001 Device 007: ID 1462:7d54 Micro Star International MYSTIC LIGHT 
> > Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
> > Bus 001 Device 005: ID 1b1c:1b75 Corsair CORSAIR HARPOON RGB PRO Gaming 
> > Mouse
> > Bus 001 Device 015: ID 8087:0032 Intel Corp. 
> > Bus 001 Device 003: ID 046d:0ab7 Logitech, Inc. Blue Microphones
> > Bus 001 Device 002: ID 13ba:0018 PCPlay Barcode PCP-BCG4209
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > pankaj@anant:~$ cat /proc/asound/cards
> >  0 [HDMI_1 ]: HDA-Intel - HDA ATI HDMI
> >   HDA ATI HDMI at 0xfca6 irq 102
> >  1 [HDMI   ]: HDA-Intel - HDA ATI HDMI
> >   HDA ATI HDMI at 0xfce6 irq 104
> >  2 [Generic]: HDA-Intel - HD-Audio Generic
> >   HD-Audio Generic at 0xfcd0 irq 106
> >  3 [Microphones]: USB-Audio - Blue Microphones
> >   Generic Blue Microphones at usb-:2a:00.1-2, high 
> > speed
> >  4 [Audio  ]: USB-Audio - USB Audio
> >   Generic USB Audio at usb-:2a:00.3-5, high speed
> >
> > I have tried to restart just the sound subsystem using
> > ‘/etc/init.d/asound restart’. But it did not lead to any good
> > results.
> >
> > Can somebody tell me what could be wrong at my end?
> >
> > Regards ~Pankaj


Hi Pankaj,

It might be nothing more than the power handling, sleep modes and USB 
enumeration after a laptop goes to sleep.

If you unplug/replug the USB plug which is the external sound card, is
it magically recognised again?

All the very best, as ever,

Andy Cater
> 

Re: USB sound device present but NOT visible in ‘alsamixer’

[Pankaj Jangid]

Sorry for the Wrong subject line earlier.

Pankaj Jangid  writes:

> I have setup a new system. Apart from the display related issue, that I
> had posted in another thread, I am facing an issue related to my
> external ‘Yeti Blue’ sound card. I use it as Mic and Monitor audio.
>
> pankaj@anant:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID:   Debian
> Description:  Debian GNU/Linux 11 (bullseye)
> Release:  11
> Codename: bullseye
> pankaj@anant:~$ uname -a
> Linux anant 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 
> GNU/Linux
>
>
> When I boot system afresh, the card is visible in the ‘alsamixer’ and in
> Gnome settings as well. Shown as “Blue” S/PDIF input and output
> devices. But when system wakes up from sleep (suspended), it doesn’t
> show the devices.
>
> However, ‘lsusb’ shows it and ‘/proc/asound/cards’ has an entry. But
> these devices (mic and speaker) are not taking any input or producing
> sound. Because they are not visible to Gnome and ‘alsamixer’.
>
> pankaj@anant:~$ lsusb
> Bus 006 Device 002: ID 2109:0813 VIA Labs, Inc. VL813 Hub
> Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 005 Device 002: ID 2109:2813 VIA Labs, Inc. VL813 Hub
> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
> Bus 003 Device 002: ID 0db0:a073 Micro Star International USB Audio
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 007: ID 1462:7d54 Micro Star International MYSTIC LIGHT 
> Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
> Bus 001 Device 005: ID 1b1c:1b75 Corsair CORSAIR HARPOON RGB PRO Gaming Mouse
> Bus 001 Device 015: ID 8087:0032 Intel Corp. 
> Bus 001 Device 003: ID 046d:0ab7 Logitech, Inc. Blue Microphones
> Bus 001 Device 002: ID 13ba:0018 PCPlay Barcode PCP-BCG4209
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> pankaj@anant:~$ cat /proc/asound/cards
>  0 [HDMI_1 ]: HDA-Intel - HDA ATI HDMI
>   HDA ATI HDMI at 0xfca6 irq 102
>  1 [HDMI   ]: HDA-Intel - HDA ATI HDMI
>   HDA ATI HDMI at 0xfce6 irq 104
>  2 [Generic]: HDA-Intel - HD-Audio Generic
>   HD-Audio Generic at 0xfcd0 irq 106
>  3 [Microphones]: USB-Audio - Blue Microphones
>   Generic Blue Microphones at usb-:2a:00.1-2, high 
> speed
>  4 [Audio  ]: USB-Audio - USB Audio
>   Generic USB Audio at usb-:2a:00.3-5, high speed
>
> I have tried to restart just the sound subsystem using
> ‘/etc/init.d/asound restart’. But it did not lead to any good
> results.
>
> Can somebody tell me what could be wrong at my end?
>
> Regards ~Pankaj

Re: Default sound level always zero for externally plugged usb sound system

[Jude DaShiell]

Needing sound as much as I do and having used usb sound systems, I'll add
one more suggested precaution to this info.  Sometimes alsa makes .lock
files in /var/lock and these will block alsactl from working.  So check
for those and delete as necessary then run alsactl store and alsa will
make those lock files for you again but with your desired settings in
place.


On Sat, 15 Jan 2022, to...@tuxteam.de wrote:

> On Sat, Jan 15, 2022 at 06:51:28PM +0100, Andrei POPESCU wrote:
> > On Sb, 15 ian 22, 10:30:50, Stefan Monnier wrote:
> > > > Try `alsactl store`
> > >
> > > Didn't know that one, thanks.  Do you happen to know if they deliver to 
> > > Canada?
> > >
> > > > (might need root).
> > >
> > > Hmm... I only have dollars and francs :-(
> >
> > As far as I know it takes only altairian dollars, but you might get away
> > with reciting some Vogon poetry instead (if you're not thrown out
> > first).
>
> But, but.
>
> If you're sudo [1] anyway, it might even take crypto. Or NFT.
>
> Cheers
>
> [1] https://xkcd.com/149/
>
>

Re: Default sound level always zero for externally plugged usb sound system

[tomas]

On Sat, Jan 15, 2022 at 06:51:28PM +0100, Andrei POPESCU wrote:
> On Sb, 15 ian 22, 10:30:50, Stefan Monnier wrote:
> > > Try `alsactl store`
> > 
> > Didn't know that one, thanks.  Do you happen to know if they deliver to 
> > Canada?
> > 
> > > (might need root).
> > 
> > Hmm... I only have dollars and francs :-(
> 
> As far as I know it takes only altairian dollars, but you might get away 
> with reciting some Vogon poetry instead (if you're not thrown out 
> first).

But, but.

If you're sudo [1] anyway, it might even take crypto. Or NFT.

Cheers

[1] https://xkcd.com/149/

-- 
t


signature.asc
Description: PGP signature

Re: Defaulting sound output to HDMI port

[Andrei POPESCU]

On Vi, 07 ian 22, 11:43:34, Charlie Gibbs wrote:
> I have a computer in the living room which is hooked up to our TV
> via an HDMI cable.  I use it to play MP3s, videos, and games.
> Our TV is hooked to our stereo system to get good-quality sound.
> However, audio isn't passing through the HDMI connection from the
> computer; to get sound I've run a separate cable from the computer's
> headphone jack to an auxiliary input on the stereo system, and I have
> to switch the stereo to this input to get sound.  It's not the end of
> the world, but it would be nice to send the audio via HDMI so I can
> just switch the TV's input and leave the stereo set to the TV.
> 
> I'm running Buster with xfce.  Here's some system information:
> 
> cjg@dragon:~$ uname -a
> Linux dragon 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
> x86_64 GNU/Linux
> cjg@dragon:~$ cat /proc/asound/cards
>  0 [Intel  ]: HDA-Intel - HDA Intel
>   HDA Intel at 0xe532 irq 27
>  1 [NVidia ]: HDA-Intel - HDA NVidia
>   HDA NVidia at 0xe500 irq 17
>  2 [IVTV1  ]: CX2341[56] - IVTV-1
>   CX2341[56] #1 WinTV PVR 500 (unit #2) TV/FM
> Radio/Line-In Capture
>  3 [IVTV0  ]: CX2341[56] - IVTV-0
>   CX2341[56] #0 WinTV PVR 500 (unit #1) TV/FM
> Radio/Line-In Capture
> cjg@dragon:~$ aplay -l
>  List of PLAYBACK Hardware Devices 
> card 0: Intel [HDA Intel], device 0: STAC9271D Analog [STAC9271D Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: Intel [HDA Intel], device 1: STAC9271D Digital [STAC9271D Digital]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> 
> After searching the web and mpv's man page, I found that the following
> command would play sound through the computer's HDMI port:
> 
> cjg@dragon:~$ mpv --audio-device=alsa/hdmi:CARD=NVidia,DEV=0 foo.mp3
> 
> Obviously there's nothing wrong with my hardware.  Is there any
> setting that will make audio output default to the HDMI port?

From memory, there are actually several ways to do this.

My preferred method is via kernel module options. E.g. for a system 
where I had the opposite problem (sound would default to HDMI instead of 
the on-board sound, both handled by the snd-hda-intel module) I have 
this:

$ cat /etc/modprobe.d/snd-hda-intel-index.conf 
# change order of devices
options snd-hda-intel index=1,0

(a rebuild of the initramfs and a reboot is required as far as I recall)

There are various other values possible, including negative (e.g. if a 
specific device should always have lower priority).


The same should be possible by (re-)defining the 'default' output in 
ALSA, usually with some /etc/asound.conf or ~/.asoundrc magic (a quick 
search points to the same entries you already tried), though I'm not 
sure how that will interact with PulseAudio and/or various applications 
using ALSA directly.


Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Default sound level always zero for externally plugged usb sound system

[Andrei POPESCU]

On Sb, 15 ian 22, 10:30:50, Stefan Monnier wrote:
> > Try `alsactl store`
> 
> Didn't know that one, thanks.  Do you happen to know if they deliver to 
> Canada?
> 
> > (might need root).
> 
> Hmm... I only have dollars and francs :-(

As far as I know it takes only altairian dollars, but you might get away 
with reciting some Vogon poetry instead (if you're not thrown out 
first).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Default sound level always zero for externally plugged usb sound system

[Andrei POPESCU]

On Jo, 30 dec 21, 19:48:41, Pankaj Jangid wrote:
> 
> Is there a way to tell Debian to save the previous volume level of
> externally plugged-in device?

Try `alsactl store` (might need root).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Defaulting sound output to HDMI port

[David]

On Sat, 8 Jan 2022 at 07:06, Charlie Gibbs  wrote:

> I have a computer in the living room which is hooked up to our TV
> via an HDMI cable.  I use it to play MP3s, videos, and games.
> Our TV is hooked to our stereo system to get good-quality sound.
> However, audio isn't passing through the HDMI connection from the
> computer; to get sound I've run a separate cable from the computer's
> headphone jack to an auxiliary input on the stereo system, and I have
> to switch the stereo to this input to get sound.  It's not the end of
> the world, but it would be nice to send the audio via HDMI so I can
> just switch the TV's input and leave the stereo set to the TV.

[snip details]

> Any suggestions as to where to go from here?

linux-audio-u...@lists.linuxaudio.org

Re: No sound after bullseye install

[Daniel Haude]

On Tue, 5 Oct 2021 09:52:12 +0300
Andrei POPESCU  wrote:

> > Yeah, that was it. I hadn't installed ALSA at all. I wasn't aware
> > that pulseaudio sits on top of ALSA.  
> 
> Because PulseAudio "sits on top of" ALSA it also depends on it. Some 
> command-line tools for ALSA are not installed by default though (e.g. 
> the package alsa-tools).

Right. And I needed alsactl from alsa-tools to find out that my
speakers were muted.

Re: No sound after bullseye install

[Andrei POPESCU]

On Lu, 04 oct 21, 17:10:39, Bob Latest wrote:
> On Mon, 04 Oct 2021 07:35:28 +0200
> deloptes  wrote:
> 
> > you have 
> > 
> > hardware -> kernel driver -> alsa -> pulseaudio -> application
> > 
> > - kernel driver utilizes the hardware
> > - alsa utilizes the kernel driver
> > - PA utilizes ALSA and provides a unified interface + capabilities
> > 
> > so it could be anything in the chain - check if you need firmware for
> > example if ALSA works (aplay etc) then check the next in the chain
> 
> Yeah, that was it. I hadn't installed ALSA at all. I wasn't aware that
> pulseaudio sits on top of ALSA.

Because PulseAudio "sits on top of" ALSA it also depends on it. Some 
command-line tools for ALSA are not installed by default though (e.g. 
the package alsa-tools).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: No sound after bullseye install

[Bob Latest]

On Mon, 04 Oct 2021 07:35:28 +0200
deloptes  wrote:

> you have 
> 
> hardware -> kernel driver -> alsa -> pulseaudio -> application
> 
> - kernel driver utilizes the hardware
> - alsa utilizes the kernel driver
> - PA utilizes ALSA and provides a unified interface + capabilities
> 
> so it could be anything in the chain - check if you need firmware for
> example if ALSA works (aplay etc) then check the next in the chain

Yeah, that was it. I hadn't installed ALSA at all. I wasn't aware that
pulseaudio sits on top of ALSA.

Thanks!

Re: No sound after bullseye install

[Alexander V. Makartsev]

On 04.10.2021 10:10, Bob Latest wrote:

Hi,

after installing Debian bullseye I can't get sound to work. I'm using
lightdm + dwm, and I have pulseaudio installed. "pavucontrol" ist stuck
on the message "Establishing connection to PulseAudio. Please wait..."

I don't understand zilch about how sound on Linux works, but my
previous version of Debian on the same hardware worked.

NB, this is a fresh install, not an upgrade from buster (?).


I've sent a reply to you already. [1]
It's best to subscribe to the list, so you can see new messages.


[1] https://lists.debian.org/debian-user/2021/10/msg00106.html

--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: No sound after bullseye install

[deloptes]

Bob Latest wrote:

> after installing Debian bullseye I can't get sound to work. I'm using
> lightdm + dwm, and I have pulseaudio installed. "pavucontrol" ist stuck
> on the message "Establishing connection to PulseAudio. Please wait..."
> 

perhaps the pulseaudio server is not running - you can check

> I don't understand zilch about how sound on Linux works, but my
> previous version of Debian on the same hardware worked.

you have 

hardware -> kernel driver -> alsa -> pulseaudio -> application

- kernel driver utilizes the hardware
- alsa utilizes the kernel driver
- PA utilizes ALSA and provides a unified interface + capabilities

so it could be anything in the chain - check if you need firmware for
example if ALSA works (aplay etc) then check the next in the chain


-- 
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

Re: No sound after bullseye install

[Alexander V. Makartsev]

On 02.10.2021 18:06, Daniel Haude wrote:

Hi,

after installing Debian bullseye I can't get sound to work. I'm using
lightdm + dwm, and I have pulseaudio installed. "pavucontrol" ist stuck
on the message "Establishing connection to PulseAudio. Please wait..."

I don't understand zilch about how sound on Linux works, but my
previous version of Debian on the same hardware worked.

NB, this is a fresh install, not an upgrade from buster (?).

You have to tell us more about your system. My crystal ball says you 
probably missing some firmware for a sound adapter from Intel.
Install firmware package from a 'non-free' section and see if that will 
help:

    # apt install firmware-intel-sound alsa-utils
To test the audio use 'speaker-test' utility:
    $ speaker-test -c2 -t wav
Also check if any channels were accidentally muted using 'alsamixer' 
utility.


If you still don't have any sound, send output from commands below with 
your next message:

    $ lspci -knnv | grep -A6 Audio
    $ aplay -l
    $ aplay -L | grep -A1 ^hw:
    # journalctl -b -g pulse

--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Setup sound for zoom conferencing

[Gary L. Roach]

On 7/18/20 4:52 PM, Bob Weber wrote:

On 7/18/20 6:46 PM, Gary L. Roach wrote:

Installed Alsa, asound

OS Debian 10

Hi all,

I have standard alsa sound installed in my system and it works fine 
for most things. Recently I started using Zoom, have installed a 
Logitech C920 webcam with stereo microphones and a Sennheiser 
HD4.50BTNC headphones with stereo microphones. I now have a conflict 
between the mic inputs from the two devices. The bluetooth 
connections is through a dongle plugged into one of my usb ports. The 
Logitech also plugs into one of my usb ports.


I want to use the mics from the HD4.50 and shut down the mics on the 
Logitech. I also want to shut down the speaker bar on my monitor and 
just use the headphones. How do I do this.


Another want is to have a graphic equalizer in the chain. I can't 
seem to find any software that would do this.


All help will be sincerely appreciated.


Gary R.


Have you tried pulseaudio?

If the devices are visible to pulse then pavucontrol can connect and 
control volumes of all the devices. pulseaudio even has many modules 
like a loop device to extend pulseaudio.


--


*...Bob*


Yes I have pulseaudio, pulseaudio volume and any other associated 
package that I could find. The problem seems to be that pulseaudio does 
not recognize my headset microphones. They don't show up in the device 
list.


I also find it a bit confusing when the volume panel lists front and 
back microphones when there is no back microphone. The front one seems 
to be the mic's on my webcam. The back one ???



Gary R.

Re: No Sound

[riveravaldez]

On 4/19/20, Bernd Gruber  wrote:
> Thomas George wrote:
>
>> systemctl status sound-card1.device
>>
>>  sound-card1.device - /sound/card1
>>
>>  Loaded: Loaded
>>
>>  Active: inactive (dead)
>>
>> System is Buster Debian 4.19.98-1
>>
>> Upon reboot to Strectch Debian 4.9.38-2 sound works fine. Where should I
>> look to correct the problem in Buster?
>
> remove timidity / timidity-daemon

For more details on that you can check:

https://lists.debian.org/debian-user/2020/04/msg00511.html

Follow from there.

Best regards.

Re: No Sound

[Bernd Gruber]

Thomas George wrote:

> systemctl status sound-card1.device
> 
>  sound-card1.device - /sound/card1
> 
>  Loaded: Loaded
> 
>  Active: inactive (dead)
> 
> System is Buster Debian 4.19.98-1
> 
> Upon reboot to Strectch Debian 4.9.38-2 sound works fine. Where should I
> look to correct the problem in Buster?

remove timidity / timidity-daemon

Greetings
Bernd

Re: cracking sound from left channel

[Bhasker C V]

The problem however comes back when i suspend and resume. I have a
written a systemd thingy to remove the module and reload it during
resume and it fixes the problem for now ...
Still no joy.

On 3/29/20, Bhasker C V  wrote:
> Dear Dan,
>
> I came across a website which said to use the index parameter
> Hence I create this in /etc/modprobe.d/snd_amd.conf
> with content
>
> options snd_hda_intel power_save=1 index=1,0
>
> The sound is infintely better now and there is no more fluttering
> sound and no leaking of right channel into left which had caused the
> distructive interference like audio.
> Thanks
>
> On 3/28/20, Dan Ritter  wrote:
>> Bhasker C V wrote:
>>> Thanks Dan,
>>> The audio cracking comes up only after a suspend resume or reboot when
>>> done on its own
>>> If I boot into windows, reboot the system (without switchoff) into
>>> linux, the sound is fine. The next time i reboot into linux the issue
>>> comes back.
>>>
>>> The sound is as if the speaker paper of an old speaker is torn. The
>>> fluttering sound when there is high bass on the headphones. The sound is
>>> clear
>>> and fine when on windows and when on linux when immediately booted after
>>> windows.
>>>
>>> This to my limited knowledge feels like windows writes something to the
>>> config registers or downloads a firmware which makes sound card work
>>> fine but then when cold booted into linux, linux is missing to do
>>> something. ... may be I am wrong.
>>
>> I would guess that Windows is setting internal mixer parameters
>> differently.
>>
>> Try killing pulseaudio, running alsamixer, and seeing if you can
>> change the behavior with any of the available switches or
>> internal mutes.
>>
>> -dsr-
>>
>

Re: cracking sound from left channel

[Bhasker C V]

Dear Dan,

I came across a website which said to use the index parameter
Hence I create this in /etc/modprobe.d/snd_amd.conf
with content

options snd_hda_intel power_save=1 index=1,0

The sound is infintely better now and there is no more fluttering
sound and no leaking of right channel into left which had caused the
distructive interference like audio.
Thanks

On 3/28/20, Dan Ritter  wrote:
> Bhasker C V wrote:
>> Thanks Dan,
>> The audio cracking comes up only after a suspend resume or reboot when
>> done on its own
>> If I boot into windows, reboot the system (without switchoff) into
>> linux, the sound is fine. The next time i reboot into linux the issue
>> comes back.
>>
>> The sound is as if the speaker paper of an old speaker is torn. The
>> fluttering sound when there is high bass on the headphones. The sound is
>> clear
>> and fine when on windows and when on linux when immediately booted after
>> windows.
>>
>> This to my limited knowledge feels like windows writes something to the
>> config registers or downloads a firmware which makes sound card work
>> fine but then when cold booted into linux, linux is missing to do
>> something. ... may be I am wrong.
>
> I would guess that Windows is setting internal mixer parameters
> differently.
>
> Try killing pulseaudio, running alsamixer, and seeing if you can
> change the behavior with any of the available switches or
> internal mutes.
>
> -dsr-
>

Re: cracking sound from left channel

[Dan Ritter]

Bhasker C V wrote: 
> Thanks Dan,
> The audio cracking comes up only after a suspend resume or reboot when
> done on its own
> If I boot into windows, reboot the system (without switchoff) into
> linux, the sound is fine. The next time i reboot into linux the issue
> comes back.
> 
> The sound is as if the speaker paper of an old speaker is torn. The
> fluttering sound when there is high bass on the headphones. The sound is
> clear
> and fine when on windows and when on linux when immediately booted after
> windows.
> 
> This to my limited knowledge feels like windows writes something to the
> config registers or downloads a firmware which makes sound card work
> fine but then when cold booted into linux, linux is missing to do
> something. ... may be I am wrong.

I would guess that Windows is setting internal mixer parameters
differently.

Try killing pulseaudio, running alsamixer, and seeing if you can
change the behavior with any of the available switches or
internal mutes.

-dsr-

Re: cracking sound from left channel

[Bhasker C V]

Thanks Dan,
The audio cracking comes up only after a suspend resume or reboot when
done on its own
If I boot into windows, reboot the system (without switchoff) into
linux, the sound is fine. The next time i reboot into linux the issue
comes back.

The sound is as if the speaker paper of an old speaker is torn. The
fluttering sound when there is high bass on the headphones. The sound is
clear
and fine when on windows and when on linux when immediately booted after
windows.

This to my limited knowledge feels like windows writes something to the
config registers or downloads a firmware which makes sound card work
fine but then when cold booted into linux, linux is missing to do
something. ... may be I am wrong.


On 27/03/2020 13:37, Dan Ritter wrote:
> Bhasker C V wrote: 
>> Hi,
>>
>> ??I am on debian bullseye x86_64 (K5.6.0-rc6).
>>
>> ??03:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD]
>> Raven/Raven2/FireFlight/Renoir Audio Processor
>>
>> I have windows booting on another partition. After windows boots, and
>> then I reboot into linux, the sound is fine. All clear on both channels.
>> But once i reboot into linux or suspend/resume, I get a cracking sound
>> along with audio on the left channel. I am not sure how to troubleshoot.
>> Is this a known issue ? Please could someone point me in the right
>> direction on fix or how to troubleshoot ?
> Does this happen with every playback format and program, or just
> some?
>
> Check all mixer settings: it's possible that the motherboard's
> audio amplifier is being overdriven, or that there are inputs
> which should be muted but aren't.
>
> Can you describe the sound more specifically?
>
> -dsr-


-- 
Bhasker C V
Secure Mails: http://keys.gnupg.net/pks/lookup?op=get=0x4D05FEEC54E47413
Registered Linux User: #306349 

Re: cracking sound from left channel

[Dan Ritter]

Bhasker C V wrote: 
> Hi,
> 
> ??I am on debian bullseye x86_64 (K5.6.0-rc6).
> 
> ??03:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD]
> Raven/Raven2/FireFlight/Renoir Audio Processor
> 
> I have windows booting on another partition. After windows boots, and
> then I reboot into linux, the sound is fine. All clear on both channels.
> But once i reboot into linux or suspend/resume, I get a cracking sound
> along with audio on the left channel. I am not sure how to troubleshoot.
> Is this a known issue ? Please could someone point me in the right
> direction on fix or how to troubleshoot ?

Does this happen with every playback format and program, or just
some?

Check all mixer settings: it's possible that the motherboard's
audio amplifier is being overdriven, or that there are inputs
which should be muted but aren't.

Can you describe the sound more specifically?

-dsr-

Re: No sound with Pulseaudio

[deloptes]

Yoann LE BARS wrote:

> As a root:
> 
> # fuser -v /dev/snd/*
> UTIL.       PID ACCÈS  COMMANDE
> /dev/snd/controlC0:  root        591 f alsactl
> timidity    856 F timidity
> /dev/snd/pcmC0D0p:   timidity    856 F...m timidity
> /dev/snd/seq:        timidity    856 F timidity
> /dev/snd/timer:      timidity    856 f timidity
> 
> Well, back to what has been seen before.

you were instructed to disable timidity, no?

Re: No sound with Pulseaudio

[Yoann LE BARS]

Hello everybody out there!

On 2020/01/19 6:19 pm, Yoann LE BARS wrote:
>   On the laptop:
> 
> $ fuser -v /dev/snd/*

As a root:

# fuser -v /dev/snd/*
 UTIL.   PID ACCÈS  COMMANDE
/dev/snd/controlC0:  root591 f alsactl
 timidity856 F timidity
/dev/snd/pcmC0D0p:   timidity856 F...m timidity
/dev/snd/seq:timidity856 F timidity
/dev/snd/timer:  timidity856 f timidity

Well, back to what has been seen before.

Best regards.

-- 
Yoann LE BARS
http://le-bars.net/yoann/
Diaspora* : yleb...@framasphere.org

Re: No sound with Pulseaudio

[Yoann LE BARS]

Hello everybody out there!

Sorry, once again I have been busy on so many other things.

On 2020/01/09 10:12 pm, Georgi Naplatanov wrote:
> something is wrong on that computer.

Indeed.

> This is output of mine:
> 
> 
> $ fuser -v /dev/snd/*
>  USERPID ACCESS COMMAND
> /dev/snd/controlC0:  gosho  2067 F pulseaudio
> /dev/snd/controlC1:  gosho  2067 F pulseaudio
> /dev/snd/controlC2:  gosho  2067 F pulseaudio
> /dev/snd/pcmC1D0p:   gosho  2067 F...m pulseaudio

On the laptop:

$ fuser -v /dev/snd/*

I have not forgotten anything when copy-pasting, there is simply no 
output.

> Try this:
>  - run as root
>   # alsactl init
>  - restart the computer
>  - then start alsamixer as ordinary user and tune all channels

It did not change anything: there is still nothing but a virtual output
in PAVUControl.

Really, the problem seems to be lying on Pulsaudio configuration, not
in Alsa. Still, I do not know what to do to make a clean configuration
for Pulseaudio.

Best regards.

-- 
Yoann LE BARS
http://le-bars.net/yoann/
Diaspora* : yleb...@framasphere.org

Re: No sound with Pulseaudio

[Georgi Naplatanov]

On 1/9/20 6:56 PM, Yoann LE BARS wrote:
> 
> Hello everybody out there!
> 
>   My apologies for having been silent so long, I have had some other
> obligations. Anyway.
> 
> Le 06/01/2020 à 11:44, Selim T. Erdoğan a écrit :
>> Try "systemctl stop timidity.service"
> 
>   Well, I have done this and it seems Timidity has indeed stopped:
> 
> # lsof | grep /dev/snd/
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
>   Output information may be incomplete.
> alsactl573   root4r  CHR
> 116,7   0t0  17199 /dev/snd/controlC0
> 
>   But the soundcard still does not appear in Pavucontrol. Therefore, I am
> not so certain the problem comes from Timidity.
> 

Hi,

something is wrong on that computer. This is output of mine:


$ fuser -v /dev/snd/*
 USERPID ACCESS COMMAND
/dev/snd/controlC0:  gosho  2067 F pulseaudio
/dev/snd/controlC1:  gosho  2067 F pulseaudio
/dev/snd/controlC2:  gosho  2067 F pulseaudio
/dev/snd/pcmC1D0p:   gosho  2067 F...m pulseaudio

Try this:
 - run as root
# alsactl init
 - restart the computer
 - then start alsamixer as ordinary user and tune all channels

HTH

Kind regards
Georgi

Re: No sound with Pulseaudio

[Yoann LE BARS]

Hello everybody out there!

My apologies for having been silent so long, I have had some other
obligations. Anyway.

Le 06/01/2020 à 11:44, Selim T. Erdoğan a écrit :
> Try "systemctl stop timidity.service"

Well, I have done this and it seems Timidity has indeed stopped:

# lsof | grep /dev/snd/
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
alsactl573   root4r  CHR
116,7   0t0  17199 /dev/snd/controlC0

But the soundcard still does not appear in Pavucontrol. Therefore, I am
not so certain the problem comes from Timidity.

Best regards.

-- 
Yoann LE BARS
http://le-bars.net/yoann/
Diaspora* : yleb...@framasphere.org

Re: No sound with Pulseaudio

[Mindaugas Celiešius]

Hello. You can check this documentations about pulse audio.

https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/

2020-01-06, pr, 23:00 deloptes  rašė:

> Dan Ritter wrote:
>
> > I have found, in troubleshooting complex systems, that blaming
> > all the working things for the failure of the non-working thing
> > doesn't lead to good results.
>
> I am not sure what you mean exactly, but everyone is allowed to have his or
> her point of view.
>
>

Re: No sound with Pulseaudio

[deloptes]

Dan Ritter wrote:

> I have found, in troubleshooting complex systems, that blaming
> all the working things for the failure of the non-working thing
> doesn't lead to good results.

I am not sure what you mean exactly, but everyone is allowed to have his or
her point of view.

Re: No sound with Pulseaudio

[Dan Ritter]

deloptes wrote: 
> Jude DaShiell wrote:
> 
> > Can you have pulseaudio on your system to make desktop environments happy
> > and disable pulseaudio and run using alsa and jack? ??I got information
> > uninstalling pulseaudio is not an option with gnome but disabling
> > pulseaudio may work.
> 
> I think all modern applications should use pulse (PA) as interface to the
> audio system. The problems with some applications are due to the fact that
> they are not using PA as an interface - as far as I know. Depends which
> application is started first, it can and will block the audio system.


I have found, in troubleshooting complex systems, that blaming
all the working things for the failure of the non-working thing
doesn't lead to good results.

-dsr-

Re: No sound with Pulseaudio

[deloptes]

Jude DaShiell wrote:

> Can you have pulseaudio on your system to make desktop environments happy
> and disable pulseaudio and run using alsa and jack?  I got information
> uninstalling pulseaudio is not an option with gnome but disabling
> pulseaudio may work.

I think all modern applications should use pulse (PA) as interface to the
audio system. The problems with some applications are due to the fact that
they are not using PA as an interface - as far as I know. Depends which
application is started first, it can and will block the audio system.

Re: No sound with Pulseaudio

[Curt]

On 2020-01-06, Jude DaShiell  wrote:
> Can you have pulseaudio on your system to make desktop environments happy
> and disable pulseaudio and run using alsa and jack?  I got information
> uninstalling pulseaudio is not an option with gnome but disabling
> pulseaudio may work.
>

The wiki claims you can "dynamically" disable pulseaudio without
uninstalling it.

https://wiki.debian.org/PulseAudio#Dynamically_enable.2Fdisable

-- 
"J'ai pour me guérir du jugement des autres toute la distance qui me sépare de
moi." Antonin Artaud

Re: No sound with Pulseaudio

[Jude DaShiell]

Can you have pulseaudio on your system to make desktop environments happy
and disable pulseaudio and run using alsa and jack?  I got information
uninstalling pulseaudio is not an option with gnome but disabling
pulseaudio may work.



--