Re: sound cards locked, No Host
good point but no success. used top to find blender and kill. no improvement On 11/6/23 10:53, Marco M. wrote: Am 06.11.2023 um 10:26:53 Uhr schrieb Thomas George: alsactl says sound cards locked. There is a lock directory in var/lib/alsa/asound-state mpv song.ogg fails with message No Host There may be solutions in the debian-user archives. I am slowly reading these in search of a solution. Any help? Is any application using alsa? What about PulseAudio or Pipewire?
Re: sound cards locked, No Host
Am 06.11.2023 um 10:26:53 Uhr schrieb Thomas George: > alsactl says sound cards locked. There is a lock directory in > var/lib/alsa/asound-state > > mpv song.ogg fails with message No Host > > There may be solutions in the debian-user archives. I am slowly > reading these in search of a solution. > > Any help? Is any application using alsa? What about PulseAudio or Pipewire?
Re: Sound only as root
Am Mittwoch, 18. Oktober 2023, 13:16:32 CEST schrieb Greg Wooledge: Hi Greg, I get the same results as you got. So it is proven, that my system is in good condition and everything is well configured. This is an important point for my search! And no, this system is pure Debian (except that is been upgraded since many many years. I believe, the first installation was 2010 or so). Debian is so stable and reliable, so I did not need change much. Of course packages are uninstalled during that long time and things also changed (like alsa, then pulseaudio and now wireplumber / pipewire for example). And as a carefull user, I purged old configurations (using aptitude purge ~c) So, this is just clean Debian 12 stable. Hope, the vendor of the application will also have some hints. Fine is, I am now sure and it is proven, my system is set correctly. This is an important point for me. Thanks for the feedback. Best Hans > On Wed, Oct 18, 2023 at 11:25:51AM +0200, Hans wrote: > > I am in the group "audio". > > > > correct: > > > > /dev/snd = root:root , drwxr-xr-x > > > > All others below /dev/snd are set > > > > crw-rw--- = root:audio > > It would help if you pasted the actual "ls -l" output. Here's mine > for comparison: > > unicorn:~$ ls -l /dev/snd > total 0 > drwxr-xr-x 2 root root 60 Oct 7 08:49 by-id/ > drwxr-xr-x 2 root root 80 Oct 7 08:49 by-path/ > crw-rw+ 1 root audio 116, 10 Oct 7 08:49 controlC0 > crw-rw+ 1 root audio 116, 12 Oct 7 08:49 controlC1 > crw-rw+ 1 root audio 116, 8 Oct 7 08:49 hwC0D0 > crw-rw+ 1 root audio 116, 9 Oct 7 08:49 hwC0D2 > crw-rw+ 1 root audio 116, 3 Oct 7 08:50 pcmC0D0c > crw-rw+ 1 root audio 116, 2 Oct 7 08:57 pcmC0D0p > crw-rw+ 1 root audio 116, 4 Oct 7 08:49 pcmC0D2c > crw-rw+ 1 root audio 116, 5 Oct 7 08:50 pcmC0D3p > crw-rw+ 1 root audio 116, 6 Oct 7 08:50 pcmC0D7p > crw-rw+ 1 root audio 116, 7 Oct 7 08:50 pcmC0D8p > crw-rw+ 1 root audio 116, 11 Oct 7 08:50 pcmC1D0c > crw-rw+ 1 root audio 116, 1 Oct 7 08:49 seq > crw-rw+ 1 root audio 116, 33 Oct 7 08:49 timer > > You see those "+" signs at the ends of the permission strings? Those > are super important here. When you login to Debian, there's various > black magic that happens with "session" and "seats" and so on. One > of the things involved in that magic is adding your account to the > ACL on the audio devices. For instance, > > unicorn:~$ getfacl /dev/snd/hwC0D0 > getfacl: Removing leading '/' from absolute path names > # file: dev/snd/hwC0D0 > # owner: root > # group: audio > user::rw- > user:greg:rw- > group::rw- > mask::rw- > other::--- > > > If yours isn't doing that, then we have a problem. In fact, the very > first thing I wondered when I read your post was "Is this actually a > Debian system, or is it something like Devuan?" If you've altered the > login stuff, for example by trying to remove systemd, then you might > have broken the session/seat magic that sets up the ACLs.
Re: Sound only as root
On Wed, Oct 18, 2023 at 07:16:32AM -0400, Greg Wooledge wrote: [...] > You see those "+" signs at the ends of the permission strings? Those > are super important here. When you login to Debian, there's various > black magic that happens with "session" and "seats" and so on. One > of the things involved in that magic is adding your account to the > ACL on the audio devices. For instance, Thanks for that other POV, which is most probably relevant to Hans. I'm in the happy camp of not needing all those pluses. My laptop has no seats ;-) Cheers -- t signature.asc Description: PGP signature
Re: Sound only as root
On Wed, Oct 18, 2023 at 11:25:51AM +0200, Hans wrote: > I am in the group "audio". > correct: > > /dev/snd = root:root , drwxr-xr-x > > All others below /dev/snd are set > > crw-rw--- = root:audio It would help if you pasted the actual "ls -l" output. Here's mine for comparison: unicorn:~$ ls -l /dev/snd total 0 drwxr-xr-x 2 root root 60 Oct 7 08:49 by-id/ drwxr-xr-x 2 root root 80 Oct 7 08:49 by-path/ crw-rw+ 1 root audio 116, 10 Oct 7 08:49 controlC0 crw-rw+ 1 root audio 116, 12 Oct 7 08:49 controlC1 crw-rw+ 1 root audio 116, 8 Oct 7 08:49 hwC0D0 crw-rw+ 1 root audio 116, 9 Oct 7 08:49 hwC0D2 crw-rw+ 1 root audio 116, 3 Oct 7 08:50 pcmC0D0c crw-rw+ 1 root audio 116, 2 Oct 7 08:57 pcmC0D0p crw-rw+ 1 root audio 116, 4 Oct 7 08:49 pcmC0D2c crw-rw+ 1 root audio 116, 5 Oct 7 08:50 pcmC0D3p crw-rw+ 1 root audio 116, 6 Oct 7 08:50 pcmC0D7p crw-rw+ 1 root audio 116, 7 Oct 7 08:50 pcmC0D8p crw-rw+ 1 root audio 116, 11 Oct 7 08:50 pcmC1D0c crw-rw+ 1 root audio 116, 1 Oct 7 08:49 seq crw-rw+ 1 root audio 116, 33 Oct 7 08:49 timer You see those "+" signs at the ends of the permission strings? Those are super important here. When you login to Debian, there's various black magic that happens with "session" and "seats" and so on. One of the things involved in that magic is adding your account to the ACL on the audio devices. For instance, unicorn:~$ getfacl /dev/snd/hwC0D0 getfacl: Removing leading '/' from absolute path names # file: dev/snd/hwC0D0 # owner: root # group: audio user::rw- user:greg:rw- group::rw- mask::rw- other::--- If yours isn't doing that, then we have a problem. In fact, the very first thing I wondered when I read your post was "Is this actually a Debian system, or is it something like Devuan?" If you've altered the login stuff, for example by trying to remove systemd, then you might have broken the session/seat magic that sets up the ACLs.
Re: Sound only as root
On Wed, Oct 18, 2023 at 12:14:33PM +0200, Hans wrote: > Am Mittwoch, 18. Oktober 2023, 12:01:01 CEST schrieb Marco M: > Please read my mail: > > --- snip > > Environment: > > Debian stable with* pipewire*, window manager is plasma5 (but every other wm > shows the same problem). > > *I am in the group "audio".* Yes, you stated it in your original post. > What might first help, I would like to know, if the settings of /dev/snd/* > are > correct: > > /dev/snd = root:root , drwxr-xr-x They look about the same on my box. But note that I still use ALSA directly. > All others below /dev/snd are set > > crw-rw--- = root:audio You might try running the application under strace. With some luck and patience you might spot where it's trying to do things and failing. Cheers -- t signature.asc Description: PGP signature
Re: Sound only as root
Am Mittwoch, 18. Oktober 2023, 12:01:01 CEST schrieb Marco M: Please read my mail: --- snip Environment: Debian stable with* pipewire*, window manager is plasma5 (but every other wm shows the same problem). *I am in the group "audio".* What might first help, I would like to know, if the settings of /dev/snd/* are correct: /dev/snd = root:root , drwxr-xr-x All others below /dev/snd are set crw-rw--- = root:audio > Am Wed, 18 Oct 2023 11:25:51 +0200 > > schrieb Hans : > > Please note, that generally sound is working as a normal user, only > > this application needs root. > > Are you in the group "audio"? > Does the application use PipeWire or PulseAudio? > Check pavucontrol. Pipewire has a pulseaudio module. But before I tested with pulseaudio, both showed no difference and no success. Best Hans
Re: Sound only as root
Am Wed, 18 Oct 2023 11:25:51 +0200 schrieb Hans : > Please note, that generally sound is working as a normal user, only > this application needs root. Are you in the group "audio"? Does the application use PipeWire or PulseAudio? Check pavucontrol.
Re: Sound loses my analog speakers after suspend, and power settings don't affect monitor poweroff
On 8/12/23 01:05, Marco wrote: sudo dmesg | grep snd So I did that, and whether or not my analog audio was recognized, the output was: [ 4.199233] snd_pci_acp6x :66:00.5: enabling device ( -> 0002) [ 4.241643] snd_hda_intel :66:00.1: enabling device ( -> 0002) [ 4.241700] snd_hda_intel :66:00.1: Handle vga_switcheroo audio client [ 4.241952] snd_hda_intel :66:00.6: enabling device ( -> 0002) [ 4.291237] snd_hda_intel :66:00.1: bound :66:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [ 4.323237] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC256: line_outs=1 (0x21/0x0/0x0/0x0/0x0) type:hp [ 4.323241] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 4.323243] snd_hda_codec_realtek hdaudioC1D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 4.323244] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0 [ 4.323245] snd_hda_codec_realtek hdaudioC1D0: inputs: [ 4.323247] snd_hda_codec_realtek hdaudioC1D0: Mic=0x19 -Carl Fink
Re: Sound loses my analog speakers after suspend, and power settings don't affect monitor poweroff
Now run sudo dmesg | grep snd to see if any error in the kernel module occurs.
Re: Sound loses my analog speakers after suspend, and power settings don't affect monitor poweroff
On 8/10/23 02:54, Marco wrote: Am 09.08.2023 schrieb Carl Fink : I suspended my system from the System menu Monday night. When I woke it up Tuesday morning, sound was coming from the HDMI monitor. The Sound Settings didn't know about any other sound system. This sounds like a driver problem with the soundcard. HDMI is realized with the graphics card, analog with a onboard sound card, mostly integrated into the chipset. Run lspci -nnk when it works and when it doesn't work. Thanks. I did just that, and I attach the output of both commands here. I switched from Mate to xfce4, which didn't affect anything from my previous message. The sound subsystem still forgets the external speakers exist. No matter what power settings I use, they don't shut off the monitors. I am thinking this is likely to be related to the power management system, rather than the sound support built into the Ryzen 6800. -Carl Fink 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe Root Complex [1022:14b5] (rev 01) Subsystem: ASUSTeK Computer Inc. Family 17h-19h PCIe Root Complex [1043:8870] 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h IOMMU [1022:14b6] Subsystem: ASUSTeK Computer Inc. Family 17h-19h IOMMU [1043:8870] 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe Dummy Host Bridge [1022:14b7] (rev 01) 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe GPP Bridge [1022:14ba] Subsystem: ASUSTeK Computer Inc. Family 17h-19h PCIe GPP Bridge [1043:8870] Kernel driver in use: pcieport 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe Dummy Host Bridge [1022:14b7] (rev 01) DeviceName: Onboard IGD 00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe GPP Bridge [1022:14ba] Subsystem: ASUSTeK Computer Inc. Family 17h-19h PCIe GPP Bridge [1043:8870] Kernel driver in use: pcieport 00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe GPP Bridge [1022:14ba] Subsystem: ASUSTeK Computer Inc. Family 17h-19h PCIe GPP Bridge [1043:8870] Kernel driver in use: pcieport 00:02.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe GPP Bridge [1022:14ba] Subsystem: ASUSTeK Computer Inc. Family 17h-19h PCIe GPP Bridge [1043:8870] Kernel driver in use: pcieport 00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe GPP Bridge [1022:14ba] Subsystem: ASUSTeK Computer Inc. Family 17h-19h PCIe GPP Bridge [1043:8870] Kernel driver in use: pcieport 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe Dummy Host Bridge [1022:14b7] (rev 01) 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 19h USB4/Thunderbolt PCIe tunnel [1022:14cd] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 19h USB4/Thunderbolt PCIe tunnel [1022:1453] Kernel driver in use: pcieport 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe Dummy Host Bridge [1022:14b7] (rev 01) 00:04.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 19h USB4/Thunderbolt PCIe tunnel [1022:14cd] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 19h USB4/Thunderbolt PCIe tunnel [1022:1453] Kernel driver in use: pcieport 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h PCIe Dummy Host Bridge [1022:14b7] (rev 01) 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h Internal PCIe GPP Bridge [1022:14b9] (rev 10) Subsystem: Device [8870:1043] Kernel driver in use: pcieport 00:08.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h Internal PCIe GPP Bridge [1022:14b9] (rev 10) Subsystem: Device [8870:1043] Kernel driver in use: pcieport 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 71) Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller [1043:8870] Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) Subsystem: ASUSTeK Computer Inc. FCH LPC Bridge [1043:8870] 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Rembrandt Data Fabric: Device 18h; Function 0 [1022:1679] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Rembrandt Data Fabric: Device 18h; Function 1 [1022:167a] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Rembrandt Data Fabric: Device 18h; Function 2 [1022:167b] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Rembrandt Data Fabric: Device 18h; Function 3 [1022:167c] Kernel driver in use: k10temp Kernel modules:
Re: Sound loses my analog speakers after suspend, and power settings don't affect monitor poweroff
Am 09.08.2023 schrieb Carl Fink : > I suspended my system from the System menu Monday night. When I woke > it up Tuesday morning, sound was coming from the HDMI monitor. The > Sound Settings didn't know about any other sound system. This sounds like a driver problem with the soundcard. HDMI is realized with the graphics card, analog with a onboard sound card, mostly integrated into the chipset. Run lspci -nnk when it works and when it doesn't work.
Re: Sound
Gunnar Gervin wrote: > Hi again. Please help me get sound. > Installed Debian again in my 2,1 Macbook from 2017, works, but no sound in > internal speakers, or in headphones. > Plugged in external speakers, which worked, but then disappeared. > Pulse audio program is installed, but does not give response in the form > of sound.. > BR, > Gunnar G what always used to help was to start alsamixer for the right hardware (usually alsamixer -c0) and unmute the PCM device (or check some outputs for muted and unmute) -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Re: Sound
On Sun, Nov 21, 2021 at 12:03:20AM +0200, Gunnar Gervin wrote: > Hi again. Please help me get sound. > Installed Debian again in my 2,1 Macbook from 2017, works, but no sound in > internal speakers, or in headphones. > Plugged in external speakers, which worked, but then disappeared. > Pulse audio program is installed, but does not give response in the form of > sound.. > BR, > Gunnar G Hi Gunnar, OK. Not really enough information here to go on. 1. What version of Debian 2. What does Lspci report for the chipset / audio 3. Do you have a desktop environment loaded? 4. Shich one? 5. Does it have a settings app? 6. Does it work at all if you play, say, a YouTube video / has it ever worked? If you can help us with information, we may be better able to help you. All the very best, as ever, Andy Cater
Re: Sound input source detected but not capturing
On Fri, 2021-09-03 at 22:52 +0530, Pankaj Jangid wrote: > I have a fresh Bullseye installation on a laptop. Sound output is > working. But the input is not working. The device is detected. > > --8<---cut here---start->8--- > $ arecord -l > List of CAPTURE Hardware Devices > card 0: PCH [HDA Intel PCH], device 0: ALC236 Analog [ALC236 Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > --8<---cut here---end--->8--- > > In the gnome settings, input is showing built-in microphone but there > is > not movement in the capturing indicator. > > alsamixer is also showing the sound card (F6) - HDA Intel PCH. > Had the same problem, apt-get purge pipewire apt-get --purge autoremove did the job. According to several posts on this list, pipewire doesn't seem to work properly. Unfortunately there was no changelog warning when upgrading and pipewire's developers do not seem to care much about documentation.
Re: Sound input source detected but not capturing
On Sb, 04 sep 21, 12:58:14, Marko Randjelovic wrote: > On Sat, 04 Sep 2021 07:47:02 +0530 > Pankaj Jangid wrote: > > > > Output of ‘amixer -c0’ > > > > --8<---cut here---start->8--- > > $ cat /proc/asound/cards > > 0 [PCH]: HDA-Intel - HDA Intel PCH > > HDA Intel PCH at 0xb1328000 irq 137 > > > > $ amixer -c0 > > Simple mixer control 'Master',0 > > Capabilities: pvolume pvolume-joined pswitch pswitch-joined > > Playback channels: Mono > > Limits: Playback 0 - 87 > > Mono: Playback 87 [100%] [0.00dB] [on] > > Simple mixer control 'Headphone',0 > > Capabilities: pvolume pswitch > > Playback channels: Front Left - Front Right > > Limits: Playback 0 - 87 > > Mono: > > Front Left: Playback 0 [0%] [-65.25dB] [off] > > Front Right: Playback 0 [0%] [-65.25dB] [off] > > Simple mixer control 'Speaker',0 > > Capabilities: pvolume pswitch > > Playback channels: Front Left - Front Right > > Limits: Playback 0 - 87 > > Mono: > > Front Left: Playback 87 [100%] [0.00dB] [on] > > Front Right: Playback 87 [100%] [0.00dB] [on] > > Simple mixer control 'PCM',0 > > Capabilities: pvolume > > Playback channels: Front Left - Front Right > > Limits: Playback 0 - 255 > > Mono: > > Front Left: Playback 254 [100%] [-0.20dB] > > Front Right: Playback 254 [100%] [-0.20dB] > > Simple mixer control 'Mic Boost',0 > > Capabilities: volume > > Playback channels: Front Left - Front Right > > Capture channels: Front Left - Front Right > > Limits: 0 - 3 > > Front Left: 3 [100%] [30.00dB] > > Front Right: 3 [100%] [30.00dB] > > Simple mixer control 'IEC958',0 > > Capabilities: pswitch pswitch-joined > > Playback channels: Mono > > Mono: Playback [off] > > Simple mixer control 'IEC958',1 > > Capabilities: pswitch pswitch-joined > > Playback channels: Mono > > Mono: Playback [on] > > Simple mixer control 'IEC958',2 > > Capabilities: pswitch pswitch-joined > > Playback channels: Mono > > Mono: Playback [on] > > Simple mixer control 'IEC958',3 > > Capabilities: pswitch pswitch-joined > > Playback channels: Mono > > Mono: Playback [on] > > Simple mixer control 'IEC958',4 > > Capabilities: pswitch pswitch-joined > > Playback channels: Mono > > Mono: Playback [on] > > Simple mixer control 'Capture',0 > > Capabilities: cvolume cswitch > > Capture channels: Front Left - Front Right > > Limits: Capture 0 - 63 > > Front Left: Capture 63 [100%] [30.00dB] [on] > > Front Right: Capture 63 [100%] [30.00dB] [on] > > Simple mixer control 'Auto-Mute Mode',0 > > Capabilities: enum > > Items: 'Disabled' 'Enabled' > > Item0: 'Enabled' > > Simple mixer control 'Internal Mic Boost',0 > > Capabilities: volume > > Playback channels: Front Left - Front Right > > Capture channels: Front Left - Front Right > > Limits: 0 - 3 > > Front Left: 0 [0%] [0.00dB] > > Front Right: 0 [0%] [0.00dB] > > --8<---cut here---end--->8--- > > > > Your control 'Capture',0 is turned on and volume is at maximum, so > that's fine, but you don't have 'input source' control. On my machine > output of 'amixer -c0' gives among other controls the following: > > Simple mixer control 'Input Source',0 > Capabilities: cenum > Items: 'Rear Mic' 'Front Mic' 'Line' 'CD' > Item0: 'Rear Mic' > > I suppose this is the reason why your capture is not working, but don't > know how to fix it. Well, there's no "Internal Mic" and "Mic" to choose from, so maybe that's the problem. @Pankaj, do you have a microphone connected to the audio (combo) jack and/or maybe the internal microphone is disabled in EFI and/or from hotkeys? > You might try to install kernel 5.13 from > experimental or newest vanilla stable which is currently 5.14.1 (take > care not to make your system unbootable). Also you might try with newer > alsa userland software. Or this... Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Sound input source detected but not capturing
Marko Randjelovic writes: > Your control 'Capture',0 is turned on and volume is at maximum, so > that's fine, but you don't have 'input source' control. On my machine > output of 'amixer -c0' gives among other controls the following: > > Simple mixer control 'Input Source',0 > Capabilities: cenum > Items: 'Rear Mic' 'Front Mic' 'Line' 'CD' > Item0: 'Rear Mic' > > I suppose this is the reason why your capture is not working, but don't > know how to fix it. You might try to install kernel 5.13 from > experimental or newest vanilla stable which is currently 5.14.1 (take > care not to make your system unbootable). Also you might try with newer > alsa userland software. Hmm... I have returned from the macos world. I need to regain speed to do all that. It has been a couple of years now. ;-)
Re: Sound input source detected but not capturing
"Andrew M.A. Cater" writes: > Very new laptop? Does it need Intel firmware for the soundcard? > firmware-intel-sound from non-free? > > https://packages.debian.org/bullseye/firmware-intel-sound Thanks for the advice, Andy. I just tried it. But this did not work. I even rebooted the system after installing. That did not make any difference.
Re: Sound input source detected but not capturing
On Sat, 04 Sep 2021 07:47:02 +0530 Pankaj Jangid wrote: > Marko Randjelovic writes: > > > Did you make sure: > > > > 1. correct device is set to record from > > 2. recording is enabled > > 3. input volume is large enough > > I guess I have only one device so there is nothing to set. I meant 'input source'. On my machine it can be: 'Rear Mic' 'Front Mic' 'Line' 'CD' > > How is recording enabled? Do I need to add myself to some group? I am > member of followin groups: pankaj cdrom floppy sudo audio dip video > plugdev netdev bluetooth scanner. You are member of audio group, so that's fine. By 'recording enabled I meant on/off switch. > > I have tried to set input volume using various knobs in gnome settings > as well as alsamixer. It did not work. > > >> If you are not sure send the output of command 'amixer' so we can check. > > > > In fact, unless you have only one sound device, the command should > > be 'amixer -cN' where N is the number of your sound card and can change > > after reboot. So first you have to type 'cat /proc/asound/cards' to > > find your card number. > > Output of ‘amixer’ > > --8<---cut here---start->8--- > $ amixer > Simple mixer control 'Master',0 > Capabilities: pvolume pswitch pswitch-joined > Playback channels: Front Left - Front Right > Limits: Playback 0 - 65536 > Mono: > Front Left: Playback 64880 [99%] [on] > Front Right: Playback 64880 [99%] [on] > Simple mixer control 'Capture',0 > Capabilities: cvolume cswitch cswitch-joined > Capture channels: Front Left - Front Right > Limits: Capture 0 - 65536 > Front Left: Capture 65540 [100%] [on] > Front Right: Capture 65540 [100%] [on] > --8<---cut here---end--->8--- > > Output of ‘amixer -c0’ > > --8<---cut here---start->8--- > $ cat /proc/asound/cards > 0 [PCH]: HDA-Intel - HDA Intel PCH > HDA Intel PCH at 0xb1328000 irq 137 > > $ amixer -c0 > Simple mixer control 'Master',0 > Capabilities: pvolume pvolume-joined pswitch pswitch-joined > Playback channels: Mono > Limits: Playback 0 - 87 > Mono: Playback 87 [100%] [0.00dB] [on] > Simple mixer control 'Headphone',0 > Capabilities: pvolume pswitch > Playback channels: Front Left - Front Right > Limits: Playback 0 - 87 > Mono: > Front Left: Playback 0 [0%] [-65.25dB] [off] > Front Right: Playback 0 [0%] [-65.25dB] [off] > Simple mixer control 'Speaker',0 > Capabilities: pvolume pswitch > Playback channels: Front Left - Front Right > Limits: Playback 0 - 87 > Mono: > Front Left: Playback 87 [100%] [0.00dB] [on] > Front Right: Playback 87 [100%] [0.00dB] [on] > Simple mixer control 'PCM',0 > Capabilities: pvolume > Playback channels: Front Left - Front Right > Limits: Playback 0 - 255 > Mono: > Front Left: Playback 254 [100%] [-0.20dB] > Front Right: Playback 254 [100%] [-0.20dB] > Simple mixer control 'Mic Boost',0 > Capabilities: volume > Playback channels: Front Left - Front Right > Capture channels: Front Left - Front Right > Limits: 0 - 3 > Front Left: 3 [100%] [30.00dB] > Front Right: 3 [100%] [30.00dB] > Simple mixer control 'IEC958',0 > Capabilities: pswitch pswitch-joined > Playback channels: Mono > Mono: Playback [off] > Simple mixer control 'IEC958',1 > Capabilities: pswitch pswitch-joined > Playback channels: Mono > Mono: Playback [on] > Simple mixer control 'IEC958',2 > Capabilities: pswitch pswitch-joined > Playback channels: Mono > Mono: Playback [on] > Simple mixer control 'IEC958',3 > Capabilities: pswitch pswitch-joined > Playback channels: Mono > Mono: Playback [on] > Simple mixer control 'IEC958',4 > Capabilities: pswitch pswitch-joined > Playback channels: Mono > Mono: Playback [on] > Simple mixer control 'Capture',0 > Capabilities: cvolume cswitch > Capture channels: Front Left - Front Right > Limits: Capture 0 - 63 > Front Left: Capture 63 [100%] [30.00dB] [on] > Front Right: Capture 63 [100%] [30.00dB] [on] > Simple mixer control 'Auto-Mute Mode',0 > Capabilities: enum > Items: 'Disabled' 'Enabled' > Item0: 'Enabled' > Simple mixer control 'Internal Mic Boost',0 > Capabilities: volume > Playback channels: Front Left - Front Right > Capture channels: Front Left - Front Right > Limits: 0 - 3 > Front Left: 0 [0%] [0.00dB] > Front Right: 0 [0%] [0.00dB] > --8<---cut here---end--->8--- > Your control 'Capture',0 is turned on and volume is at maximum, so that's fine, but you don't have 'input source' control. On my machine output of 'amixer -c0' gives among other controls the following: Simple mixer control 'Input Source',0 Capabilities: cenum Items: 'Rear Mic' 'Front Mic' 'Line' 'CD' Item0: 'Rear Mic' I suppose this is the reason why your capture is not working, but don't know how to fix it. You might try to install kernel
Re: Sound input source detected but not capturing
On Fri, Sep 03, 2021 at 10:52:45PM +0530, Pankaj Jangid wrote: > I have a fresh Bullseye installation on a laptop. Sound output is > working. But the input is not working. The device is detected. > > --8<---cut here---start->8--- > $ arecord -l > List of CAPTURE Hardware Devices > card 0: PCH [HDA Intel PCH], device 0: ALC236 Analog [ALC236 Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > --8<---cut here---end--->8--- > > In the gnome settings, input is showing built-in microphone but there is > not movement in the capturing indicator. > > alsamixer is also showing the sound card (F6) - HDA Intel PCH. > Very new laptop? Does it need Intel firmware for the soundcard? firmware-intel-sound from non-free? https://packages.debian.org/bullseye/firmware-intel-sound All the very best, as ever, Andy Cater
Re: Sound input source detected but not capturing
Marko Randjelovic writes: > Did you make sure: > > 1. correct device is set to record from > 2. recording is enabled > 3. input volume is large enough I guess I have only one device so there is nothing to set. How is recording enabled? Do I need to add myself to some group? I am member of followin groups: pankaj cdrom floppy sudo audio dip video plugdev netdev bluetooth scanner. I have tried to set input volume using various knobs in gnome settings as well as alsamixer. It did not work. >> If you are not sure send the output of command 'amixer' so we can check. > > In fact, unless you have only one sound device, the command should > be 'amixer -cN' where N is the number of your sound card and can change > after reboot. So first you have to type 'cat /proc/asound/cards' to > find your card number. Output of ‘amixer’ --8<---cut here---start->8--- $ amixer Simple mixer control 'Master',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 65536 Mono: Front Left: Playback 64880 [99%] [on] Front Right: Playback 64880 [99%] [on] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch cswitch-joined Capture channels: Front Left - Front Right Limits: Capture 0 - 65536 Front Left: Capture 65540 [100%] [on] Front Right: Capture 65540 [100%] [on] --8<---cut here---end--->8--- Output of ‘amixer -c0’ --8<---cut here---start->8--- $ cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xb1328000 irq 137 $ amixer -c0 Simple mixer control 'Master',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback 0 - 87 Mono: Playback 87 [100%] [0.00dB] [on] Simple mixer control 'Headphone',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 87 Mono: Front Left: Playback 0 [0%] [-65.25dB] [off] Front Right: Playback 0 [0%] [-65.25dB] [off] Simple mixer control 'Speaker',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 87 Mono: Front Left: Playback 87 [100%] [0.00dB] [on] Front Right: Playback 87 [100%] [0.00dB] [on] Simple mixer control 'PCM',0 Capabilities: pvolume Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 254 [100%] [-0.20dB] Front Right: Playback 254 [100%] [-0.20dB] Simple mixer control 'Mic Boost',0 Capabilities: volume Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: 0 - 3 Front Left: 3 [100%] [30.00dB] Front Right: 3 [100%] [30.00dB] Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'IEC958',1 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'IEC958',2 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'IEC958',3 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'IEC958',4 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 63 Front Left: Capture 63 [100%] [30.00dB] [on] Front Right: Capture 63 [100%] [30.00dB] [on] Simple mixer control 'Auto-Mute Mode',0 Capabilities: enum Items: 'Disabled' 'Enabled' Item0: 'Enabled' Simple mixer control 'Internal Mic Boost',0 Capabilities: volume Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: 0 - 3 Front Left: 0 [0%] [0.00dB] Front Right: 0 [0%] [0.00dB] --8<---cut here---end--->8---
Re: Sound input source detected but not capturing
On Fri, 3 Sep 2021 20:48:52 +0200 Marko Randjelovic wrote: > If you are not sure send the output of command 'amixer' so we can check. In fact, unless you have only one sound device, the command should be 'amixer -cN' where N is the number of your sound card and can change after reboot. So first you have to type 'cat /proc/asound/cards' to find your card number.
Re: Sound input source detected but not capturing
On Fri, 03 Sep 2021 22:52:45 +0530 Pankaj Jangid wrote: > I have a fresh Bullseye installation on a laptop. Sound output is > working. But the input is not working. The device is detected. > > --8<---cut here---start->8--- > $ arecord -l > List of CAPTURE Hardware Devices > card 0: PCH [HDA Intel PCH], device 0: ALC236 Analog [ALC236 Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > --8<---cut here---end--->8--- > > In the gnome settings, input is showing built-in microphone but there is > not movement in the capturing indicator. > > alsamixer is also showing the sound card (F6) - HDA Intel PCH. > Did you make sure: 1. correct device is set to record from 2. recording is enabled 3. input volume is large enough If you are not sure send the output of command 'amixer' so we can check.
Re: Sound issue in bulleye with USB Headset and Internal Audio
On Mi, 07 apr 21, 23:49:46, deloptes wrote: > Rainer Dorsch wrote: > > > I have a bullseye system with an on-board Intel sound device and a > > Logitech USB headset. Everything works perfect, if I boot without the USB > > headset plugged in. Both devices are detected and I can switch between > > them as expected. If I boot with the USB headset plugged in, inxi still > > finds both devices, but pacmd list-cards outputs only the USB headset. I > > am wondering if that is a pulseaudio feature or a bug. > > don't know if it will help but it is always a good idea to give index > 0 to > usb audio > > $ cat /etc/modprobe.d/alsa-base.conf > options snd_hda_intel index=0 > options snd-usb-audio index=1 This is taken care of automatically for most cases: $ grep snd-usb-audio /lib/modprobe.d/aliases.conf options snd-usb-audio index=-2 Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Sound issue in bulleye with USB Headset and Internal Audio
On Mi, 07 apr 21, 20:38:46, Rainer Dorsch wrote: > Am Mittwoch, 7. April 2021, 19:47:47 CEST schrieb Andrei POPESCU: > > On Mi, 07 apr 21, 18:39:21, Rainer Dorsch wrote: > > > Hello, > > > > > > I have a bullseye system with an on-board Intel sound device and a > > > Logitech > > > USB headset. Everything works perfect, if I boot without the USB headset > > > plugged in. Both devices are detected and I can switch between them as > > > expected. If I boot with the USB headset plugged in, inxi still finds both > > > devices, but pacmd list-cards outputs only the USB headset. I am wondering > > > if that is a pulseaudio feature or a bug. > > > > Please post the output of 'aplay -l' in both cases. > > For me it looks identical, but see yourself: This is ok, at least there doesn't appear to be conflict at ALSA level. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Sound issue in bulleye with USB Headset and Internal Audio
Am Mittwoch, 7. April 2021, 20:38:46 CEST schrieb Rainer Dorsch: > Am Mittwoch, 7. April 2021, 19:47:47 CEST schrieb Andrei POPESCU: > > On Mi, 07 apr 21, 18:39:21, Rainer Dorsch wrote: > > > Hello, > > > > > > I have a bullseye system with an on-board Intel sound device and a > > > Logitech > > > USB headset. Everything works perfect, if I boot without the USB headset > > > plugged in. Both devices are detected and I can switch between them as > > > expected. If I boot with the USB headset plugged in, inxi still finds > > > both > > > devices, but pacmd list-cards outputs only the USB headset. I am > > > wondering > > > if that is a pulseaudio feature or a bug. > > > > Please post the output of 'aplay -l' in both cases. > > [...] Small update: I cannot really repro anymore that the on-board sound works, even if I boot w/o a headset, I saw this correlation several times in the past, but right now, pulseaudio always seems to be unhappy with on-board sound, e.g. if I boot without USB headset: rd@h370:~$ pacmd list-cards 0 card(s) available. rd@h370:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 rd@h370:~$ Any idea or hint is welcome. Regards Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Sound issue in bulleye with USB Headset and Internal Audio
Am Mittwoch, 7. April 2021, 19:47:47 CEST schrieb Andrei POPESCU: > On Mi, 07 apr 21, 18:39:21, Rainer Dorsch wrote: > > Hello, > > > > I have a bullseye system with an on-board Intel sound device and a > > Logitech > > USB headset. Everything works perfect, if I boot without the USB headset > > plugged in. Both devices are detected and I can switch between them as > > expected. If I boot with the USB headset plugged in, inxi still finds both > > devices, but pacmd list-cards outputs only the USB headset. I am wondering > > if that is a pulseaudio feature or a bug. > > Please post the output of 'aplay -l' in both cases. For me it looks identical, but see yourself: If USB headset is plugged at boot: rd@h370:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Headset [Logitech USB Headset], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 rd@h370:~$ If USB headset is not plugged at boot, before plugging the headset: rd@h370:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 rd@h370:~$ If USB headset is not plugged at boot, after plugging the headset: rd@h370:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Headset [Logitech USB Headset], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 rd@h370:~$ Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Sound issue in bulleye with USB Headset and Internal Audio
Rainer Dorsch wrote: > I have a bullseye system with an on-board Intel sound device and a > Logitech USB headset. Everything works perfect, if I boot without the USB > headset plugged in. Both devices are detected and I can switch between > them as expected. If I boot with the USB headset plugged in, inxi still > finds both devices, but pacmd list-cards outputs only the USB headset. I > am wondering if that is a pulseaudio feature or a bug. don't know if it will help but it is always a good idea to give index > 0 to usb audio $ cat /etc/modprobe.d/alsa-base.conf options snd_hda_intel index=0 options snd-usb-audio index=1
Re: Sound issue in bulleye with USB Headset and Internal Audio
On Mi, 07 apr 21, 18:39:21, Rainer Dorsch wrote: > Hello, > > I have a bullseye system with an on-board Intel sound device and a Logitech > USB headset. Everything works perfect, if I boot without the USB headset > plugged in. Both devices are detected and I can switch between them as > expected. If I boot with the USB headset plugged in, inxi still finds both > devices, but pacmd list-cards outputs only the USB headset. I am wondering if > that is a pulseaudio feature or a bug. Please post the output of 'aplay -l' in both cases. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Sound issue in bulleye with USB Headset and Internal Audio
On 4/8/21 12:39 AM, Rainer Dorsch wrote: system with an on-board Intel sound device and a Logitech USB headset. Everything works perfect, if I boot without the USB headset plugged in. Both devices are detected and I can switch between them a Try checking "dmesg --human" output, there maybe something from there . Try compare it for both situation -- Email : Robbi Nespu PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA PGP key : https://keybase.io/robbinespu/pgp_keys.asc
Re: Sound Issue
Thank you for your reply, Andrea. Am Samstag, 6. Februar 2021, 23:52:24 CET schrieb Andrea Borgia: > Il 06/02/21 20:53, Rainer Dorsch ha scritto: > > sound was working for years on my Debian System w/o any issue with > > pulseaudio. Since a few weeks I have problems with the on-board Intel > > sound, listed as > I'm having a similar issue and it might be because of this bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980836 I am on stable with 12.2-4+deb10u1 > > With this command I get the audio back, at least until the next reboot > or plug/unplug cycle: > > pacmd unload-module module-udev-detect && pacmd load-module > module-udev-detect > Does not work for me. Maybe that is the sign to upgrade to bullseye :-) Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Sound Issue
Il 06/02/21 20:53, Rainer Dorsch ha scritto: sound was working for years on my Debian System w/o any issue with pulseaudio. Since a few weeks I have problems with the on-board Intel sound, listed as I'm having a similar issue and it might be because of this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980836 With this command I get the audio back, at least until the next reboot or plug/unplug cycle: pacmd unload-module module-udev-detect && pacmd load-module module-udev-detect Regards, Andrea.
Re: Sound does not work on Debian 10
On 31.12.2020 18:06, Hassans Tech wrote: In addition, the output of aplay -l Is: List of PLAYBACK Hardware Devices card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytchtes8316 [bytcht-es8316], device 0: Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytchtes8316 [bytcht-es8316], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 haf@UNKNOWN:~$ It looks like sound card is detected, but enumerated in wrong order. Try to set card 1 as default [1] and see if that will solve your problem. If not send output from commands below: $ aplay -L | grep -e ':CARD' $ lshw -c multimedia [1] https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture#Set_the_default_sound_card -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Sound does not work on Debian 10
In addition, the output of aplay -l Is: List of PLAYBACK Hardware Devices card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytchtes8316 [bytcht-es8316], device 0: Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytchtes8316 [bytcht-es8316], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 haf@UNKNOWN:~$
Re: Sound does not work on Debian 10
Additional info that I forgot to add: The output of lspci -knn Is: 00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 36) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:7270] Kernel driver in use: iosf_mbi_pci 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [808 6:22b0] (rev 36) DeviceName: Onboard IGD Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] Kernel driver in use: i915 Kernel modules: i915 00:03.0 Multimedia controller [0480]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit [8086:22b8] (rev 36 ) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit [8086:7270] Kernel driver in use: intel_atomisp2_pm Kernel modules: intel_atomisp2_pm 00:0b.0 Signal processing controller [1180]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controll er [8086:22dc] (rev 36) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller [8086:7270] Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5] (rev 36 ) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:7270] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:1a.0 Encryption controller [1080]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [8086:2 298] (rev 36) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [8086:7270] 00:1f.0 ISA bridge [0601]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU [8086:229c] (rev 36) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU [8086:7270] Kernel driver in use: lpc_ich Kernel modules: lpc_ich again, thanks for your time.
Re: Sound (Alsa/PulseAudio) not working for ONE USER ONLY (addidional info)
On 9/23/20 10:02 PM, Marc Shapiro wrote: I am currently running Stretch, with alsa and pulseaudio. This box has three users. My wife and daughter both get sound through Firefox, as well as 'play filename.mp3'. Neither method works for my login. When using 'aplay filename.mp3' all users get static. Some background: A few months back, my /home partition was accidentally wiped. (It was mounted where I did not think it was. No backups. My bad. New external drive for backups, now.) Data recovery managed to get back my wife's and daughter's directories, but not mine. My guess is that there were configuration files that I no longer have under my login that are necessary for sound. An interesting note: I just tried playing a file (play filename.mp3) while displaying the PulseAudio Volume Meter. It says that sound is playing. Then I noticed that it is showing volume for the 'Loopback Analog Stero'. I did the same thing under my wife's and daughter's login and the sound was going to the 'Built-in Audio Analog Stereo' How do I tell Alsa/PulseAudio to use the Built-in sound device, and not the loopback device? Marc I can change the fallback to the Built-in sound device using pavucontrol, but then, when I try to play an mp3 file, 'play' just locks up. It displays the file data, and the line that shows its location in the file, but that line never changes. Even Ctrl-C does not exit the program. I have to close, and restart, LXTerminal. Marc
Re: Sound in Jitsi/BBB [was: dvice on encrypted filesystem]
On Thu, Jun 25, 2020 at 03:57:53PM +0200, Nicolas George wrote: > to...@tuxteam.de (12020-06-25): > > You don't use Pulseaudio? Current Firefoxen have ALSA enabled for Debian, > > but their ALSA support seems to have fallen prey to bitrot. I didn't > > manage to get them working. > > > > If you insist in not having Pulse (I do), there's apulse (the package > > is named likewise, I think). It plays LD_PRELOAD tricks to trick FF > > into believing it's talking to Pulseaudio. I had success with that. > > I use apulse, and Firefox is capable of producing sound on some sites (I > do not know why I bother to get it working: I do NOT want my web browser > to produce sound!). The microphone is the issue. Sound wasn't the problem for me. Microphone was. FWIW, I also detest the browser making noises -- but lockdown and things. And seeing people swarming to Zoom gave me the rest. I had both Jitsi and BBB, and micro worked (via apulse) with both. It took me some fiddling with amixer/alsamixer, though. Cheers -- t signature.asc Description: Digital signature
Re: Sound in Jitsi/BBB [was: dvice on encrypted filesystem]
to...@tuxteam.de (12020-06-25): > You don't use Pulseaudio? Current Firefoxen have ALSA enabled for Debian, > but their ALSA support seems to have fallen prey to bitrot. I didn't > manage to get them working. > > If you insist in not having Pulse (I do), there's apulse (the package > is named likewise, I think). It plays LD_PRELOAD tricks to trick FF > into believing it's talking to Pulseaudio. I had success with that. I use apulse, and Firefox is capable of producing sound on some sites (I do not know why I bother to get it working: I do NOT want my web browser to produce sound!). The microphone is the issue. Regards, -- Nicolas George signature.asc Description: PGP signature
Re: Sound issues on ThinkPad X220T (Lenovo)
Hi, For the record, I had the exact same problem on a computer running buster that I don't use very often. For sure, it was working fine even with timidity installed a few months ago. Many thanks to Andrei for the 'lsof | grep /dev/snd' command that pointed us in the right direction! Debugging these sound issues that appear spontaneously on a previously-working setup is not easy, especially now that PulseAudio is required everywhere. Regards -- Florent
Re: Sound issues on ThinkPad X220T (Lenovo)
riveravaldez wrote: > On 4/12/20, riveravaldez wrote: >> On 4/12/20, Andrei POPESCU wrote: >>> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo speaker-test -c2' works flawlessly. (The idea to check that came from [1].) >>> >>> Some program might be blocking the sound card, check also the output of >>> 'lsof | grep /dev/snd' (as root). >>> >>> Kind regards, >>> Andrei >> >> Thanks a lot for your answer and help, Andrei. >> I've got these: >> >> $ sudo lsof | grep /dev/snd/ >> timidity 644timidity mem CHR >> 116,213463 /dev/snd/pcmC0D0p >> timidity 644timidity3r CHR >>116,33 0t0 12547 /dev/snd/timer >> timidity 644timidity4u CHR >> 116,2 0t0 13463 /dev/snd/pcmC0D0p >> timidity 644timidity5u CHR >> 116,9 0t0 13479 /dev/snd/controlC0 >> timidity 644timidity6u CHR >> 116,1 0t0 12548 /dev/snd/seq >> alsamixer 2150thinkpad3u CHR >> 116,9 0t0 13479 /dev/snd/controlC0 >> >> Maybe a timidity configuration issue? > > Oh, mother-bugger... Problem - practically - solved. > IT is known issue with timidity. I did not know that sound can be played via root account though. We learned a bit more.
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/12/20, riveravaldez wrote: > On 4/12/20, Andrei POPESCU wrote: >> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: >>> >>> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >>> speaker-test -c2' works flawlessly. (The idea to check that came from >>> [1].) >> >> Some program might be blocking the sound card, check also the output of >> 'lsof | grep /dev/snd' (as root). >> >> Kind regards, >> Andrei > > Thanks a lot for your answer and help, Andrei. > I've got these: > > $ sudo lsof | grep /dev/snd/ > timidity 644timidity mem CHR > 116,213463 /dev/snd/pcmC0D0p > timidity 644timidity3r CHR >116,33 0t0 12547 /dev/snd/timer > timidity 644timidity4u CHR > 116,2 0t0 13463 /dev/snd/pcmC0D0p > timidity 644timidity5u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > timidity 644timidity6u CHR > 116,1 0t0 12548 /dev/snd/seq > alsamixer 2150thinkpad3u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > > Maybe a timidity configuration issue? Oh, mother-bugger... Problem - practically - solved. I did: $ sudo apt-get purge timidity Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Los siguientes paquetes se ELIMINARÁN: timidity* timidity-daemon* 0 actualizados, 0 nuevos se instalarán, 2 para eliminar y 9 no actualizados. Se liberarán 1.655 kB después de esta operación. ¿Desea continuar? [S/n] (Leyendo la base de datos ... 123466 ficheros o directorios instalados actualmente.) Desinstalando timidity-daemon (2.14.0-8) ... Desinstalando timidity (2.14.0-8) ... Procesando disparadores para mime-support (3.64) ... Procesando disparadores para man-db (2.9.1-1) ... Procesando disparadores para desktop-file-utils (0.24-1) ... (Leyendo la base de datos ... 123413 ficheros o directorios instalados actualmente.) Purgando ficheros de configuración de timidity-daemon (2.14.0-8) ... Purgando ficheros de configuración de timidity (2.14.0-8) ... Procesando disparadores para systemd (244.3-1) ... And everything came to work. Pavucontrol shows the devices, streams and configurations. All media-players (audacious, mplayer, firefox, audacity, etc.) work with default audio configuration, and even JACK is working flawlessly. In fact, tested JACK (qjackctl) with qsynt and vmpk and everything worked fine (maybe I don't even need timidity at all?). And then - testing if could reinstall - found the cause of the problem: $ sudo apt-get install timidity Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Paquetes sugeridos: fluid-soundfont-gs pmidi timidity-daemon Se instalarán los siguientes paquetes NUEVOS: timidity 0 actualizados, 1 nuevos se instalarán, 0 para eliminar y 9 no actualizados. Se necesita descargar 0 B/627 kB de archivos. Se utilizarán 1.582 kB de espacio de disco adicional después de esta operación. Obteniendo informes de fallo... Finalizado Analizando información Encontrada/Corregida... Finalizado Fallos critical del paquete timidity (→ 2.14.0-8) b1 - #901148 - timidity: upgrading to 2.14.0-2 broke sound via pulseaudio Fusionado con: 902330 904652 918522 Resumen: timidity(1 fallo) ¿Está seguro de que desea instalar/actualizar los paquetes mostrados anteriormente? [Y/n/?/...] n * ** Saliendo con error para detener la instalación. ** * E: El subproceso /usr/bin/apt-listbugs apt devolvió un código de error (10) E: Failure running script /usr/bin/apt-listbugs apt Don't know how that passed without me noticing it... Last messages from: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901148#147 > After many tests I have found the solution about the > bugs around timidity-daemon and pulseaudio. > > timidity-daemon installs an system-wide daemon. But > pulseaudio is a user-wide "daemon". I guess that explains the 'sudo works, non-sudo non-works'? > With my appended patch the system-wide daemon will be > removed and a xdg/autostart script will be installed. > > After that timidity together with pulseaudio runs > perfectly. > Now I have made new Debian packages for buster and testing > including my patch: That last's from 20 Feb 2020, maybe still not uploaded? Should I mark this as 'SOLVED' in some manner? Thanks a lot for everything. Andrei, you saved me. ^_^ (!)
Re: Sound issues on ThinkPad X220T (Lenovo)
On Du, 12 apr 20, 11:39:52, riveravaldez wrote: > > $ groups > thinkpad cdrom floppy sudo audio dip video plugdev netdev Ok. > $ speaker-test -c2 [Still not sound.] And no error... > $ sudo speaker-test -c2 [Sounds OK.] That would indicate that sound is handled differently for the regular user (e.g. via pulseaudio) vs. the root user. This could be either pulseaudio or an .asoundrc (do you have one in your home directory?). Try this as user: pasuspender -- speaker-test -c2 > $ sudo lsof | grep /dev/snd/ > timidity 644timidity mem CHR > 116,213463 /dev/snd/pcmC0D0p > timidity 644timidity3r CHR >116,33 0t0 12547 /dev/snd/timer > timidity 644timidity4u CHR > 116,2 0t0 13463 /dev/snd/pcmC0D0p > timidity 644timidity5u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > timidity 644timidity6u CHR > 116,1 0t0 12548 /dev/snd/seq > alsamixer 2150thinkpad3u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > > Maybe a timidity configuration issue? Try stopping / disabling it and see if that helps. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/12/20, deloptes wrote: > riveravaldez wrote: > >> But this not, even as sudo (and the error is similar to JACK one): >> $ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav >> aplay: main:830: audio open error: Device or resource bussy > > aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav Problem persists, no sound: $ aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav aplay: main:830: audio open error: Device or resource busy > read this > https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture I'll check it again. > > you should know what you are doing Yes, that's the idea. Any help? Thanks!
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/12/20, Andrei POPESCU wrote: > On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: >> >> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >> speaker-test -c2' works flawlessly. (The idea to check that came from >> [1].) > > Any error message? Is your user a member of group 'audio'? > > Some program might be blocking the sound card, check also the output of > 'lsof | grep /dev/snd' (as root). > > Kind regards, > Andrei Thanks a lot for your answer and help, Andrei. I've got these: $ groups thinkpad cdrom floppy sudo audio dip video plugdev netdev $ speaker-test -c2 [Still not sound.] speaker-test 1.2.2 Playback device is default Stream parameters are 48000Hz, S16_LE, 2 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 96 to 1048576 Period size range from 32 to 349526 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Time per period = 12,314270 0 - Front Left 1 - Front Right ^CTime per period = 12,317682 $ sudo speaker-test -c2 [Sounds OK.] speaker-test 1.2.2 Playback device is default Stream parameters are 48000Hz, S16_LE, 2 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 2048 to 16384 Period size range from 1024 to 1024 Using max buffer size 16384 Periods = 4 was set period_size = 1024 was set buffer_size = 16384 0 - Front Left 1 - Front Right Time per period = 5,644667 0 - Front Left ^CWrite error: -4,Llamada al sistema interrumpida xrun_recovery failed: -4,Llamada al sistema interrumpida Transfer failed: Llamada al sistema interrumpida [System is in Spanish, last lines mean, 'Interrupted system-call'.] $ sudo lsof | grep /dev/snd/ timidity 644timidity mem CHR 116,213463 /dev/snd/pcmC0D0p timidity 644timidity3r CHR 116,33 0t0 12547 /dev/snd/timer timidity 644timidity4u CHR 116,2 0t0 13463 /dev/snd/pcmC0D0p timidity 644timidity5u CHR 116,9 0t0 13479 /dev/snd/controlC0 timidity 644timidity6u CHR 116,1 0t0 12548 /dev/snd/seq alsamixer 2150thinkpad3u CHR 116,9 0t0 13479 /dev/snd/controlC0 Maybe a timidity configuration issue?
Re: Sound issues on ThinkPad X220T (Lenovo)
riveravaldez wrote: > But this not, even as sudo (and the error is similar to JACK one): > $ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav > aplay: main:830: audio open error: Device or resource bussy aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav read this https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture you should know what you are doing
Re: Sound issues on ThinkPad X220T (Lenovo)
On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: > > Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo > speaker-test -c2' works flawlessly. (The idea to check that came from > [1].) Any error message? Is your user a member of group 'audio'? Some program might be blocking the sound card, check also the output of 'lsof | grep /dev/snd' (as root). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/11/20, riveravaldez wrote: > On 4/11/20, riveravaldez wrote: >> Hi, >> >> I would like to know what's the proper way to solve this. I'm on an >> updated debian-testing installation (with pulseaudio installed and >> working, but the problem seems to be previous, i.e., in ALSA, because >> pavucontrol doesn't show the soundcard in its correspondent tab). >> >> I can get audio from audacity and audacious as long as I choose >> manually the proper soundcard in its options, but not from other >> programs (e.g., firefox, mplayer, etc.), which I suppose use the >> default soundcard. >> >> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >> speaker-test -c2' works flawlessly. (The idea to check that came from >> [1].) >> >> I already tested (following [2]): >> >> $ sudo alsactl init >> Found hardware: "HDA-Intel" "Conexant CX20590" >> "HDA:14f1506e,17aa21db,0013 HDA:80862805,80860101,0010" >> "0x17aa" "0x21db" >> Hardware is initialized using a generic method >> >> But nothing changed after reboot. (Though, the CX20590 is the working >> choice for audacious/audacity.) >> >> I have this info: >> >> $ cat /proc/asound/cards >> 0 [PCH]: HDA-Intel - HDA Intel PCH >> HDA Intel PCH at 0xf252 irq 35 >> >> $ lspci -v >> 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset >> Family High Definition Audio Controller (rev 04) >> Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition >> Audio Controller >> Flags: bus master, fast devsel, latency 0, IRQ 35 >> Memory at f252 (64-bit, non-prefetchable) [size=16K] >> Capabilities: >> Kernel driver in use: snd_hda_intel >> Kernel modules: snd_hda_intel >> >> Any other info I could provide? >> What should I do? >> >> BTW, JACK also fails to work, with these messages: >> >> 20:59:14.349 Reiniciar estadísticas. >> 20:59:14.356 Cambios en las conexiones ALSA. >> Cannot connect to server socket err = No existe el fichero o el >> directorio >> Cannot connect to server request channel >> jack server is not running or cannot be started >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> 20:59:31.365 JACK está iniciándose... >> 20:59:31.366 /usr/bin/jackd -v -dalsa -r48000 -p512 -n2 -Xseq -D >> -Chw:PCH,0 -Phw:PCH,0 >> Cannot connect to server socket err = No existe el fichero o el >> directorio >> Cannot connect to server request channel >> jack server is not running or cannot be started >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> 20:59:31.382 JACK se inició con PID=3144. >> no message buffer overruns >> no message buffer overruns >> no message buffer overruns >> jackdmp 1.9.12 >> Copyright 2001-2005 Paul Davis and others. >> Copyright 2004-2016 Grame. >> Copyright 2016-2017 Filipe Coelho. >> jackdmp comes with ABSOLUTELY NO WARRANTY >> This is free software, and you are welcome to redistribute it >> under certain conditions; see the file COPYING for details >> JACK server starting in realtime mode with priority 10 >> self-connect-mode is "Don't restrict self connect requests" >> Jack: JackPosixThread::StartImp : create non RT thread >> Jack: JackPosixThread::ThreadHandler : start >> Jack: capture device hw:PCH,0 >> Jack: playback device hw:PCH,0 >> Jack: apparent rate = 48000 >> Jack: frames per period = 512 >> Jack: JackDriver::Open capture_driver_name = hw:PCH,0 >> Jack: JackDriver::Open playback_driver_name = hw:PCH,0 >> Jack: Check protocol client = 8 server = 8 >> Jack: JackEngine::ClientInternalOpen: name = system >> Jack: JackEngine::AllocateRefNum ref = 0 >> Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = >> 0 >> Jack: JackEngine::NotifyAddClient: name = system >> Jack: JackGraphManager::SetBufferSize size = 512 >> Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 >> Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 >> Jack: JackDriver::SetupDriverSync driver sem in flush mode >> audio_reservation_init >> Acquire audio card Audio0 >> creating alsa driver ... >> hw:PCH,0|hw:PCH,0|512|2|48000|0|0|nomon|swmeter|-|32bit >> ATTENTION: The playback device "hw:PCH,0" is already in use. Please >> stop the application using it and run JACK again >> Jack: JackDriver::Close >> Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 >> Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 >> Jack: JackEngine::ClientInternalClose ref = 0 >> Jack: JackEngine::ClientCloseAux ref = 0 >> Jack: JackGraphManager::RemoveAllPorts ref = 0 >> Released audio card Audio0 >> audio_reservation_finish >> Jack: ~JackDriver >> Cannot initialize driver >> Jack: no message buffer overruns >> Jack: JackPosixThread::Stop >>
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/11/20, riveravaldez wrote: > Hi, > > I would like to know what's the proper way to solve this. I'm on an > updated debian-testing installation (with pulseaudio installed and > working, but the problem seems to be previous, i.e., in ALSA, because > pavucontrol doesn't show the soundcard in its correspondent tab). > > I can get audio from audacity and audacious as long as I choose > manually the proper soundcard in its options, but not from other > programs (e.g., firefox, mplayer, etc.), which I suppose use the > default soundcard. > > Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo > speaker-test -c2' works flawlessly. (The idea to check that came from > [1].) > > I already tested (following [2]): > > $ sudo alsactl init > Found hardware: "HDA-Intel" "Conexant CX20590" > "HDA:14f1506e,17aa21db,0013 HDA:80862805,80860101,0010" > "0x17aa" "0x21db" > Hardware is initialized using a generic method > > But nothing changed after reboot. (Though, the CX20590 is the working > choice for audacious/audacity.) > > I have this info: > > $ cat /proc/asound/cards > 0 [PCH]: HDA-Intel - HDA Intel PCH > HDA Intel PCH at 0xf252 irq 35 > > $ lspci -v > 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset > Family High Definition Audio Controller (rev 04) > Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition > Audio Controller > Flags: bus master, fast devsel, latency 0, IRQ 35 > Memory at f252 (64-bit, non-prefetchable) [size=16K] > Capabilities: > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > > Any other info I could provide? > What should I do? > > BTW, JACK also fails to work, with these messages: > > 20:59:14.349 Reiniciar estadísticas. > 20:59:14.356 Cambios en las conexiones ALSA. > Cannot connect to server socket err = No existe el fichero o el directorio > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > 20:59:31.365 JACK está iniciándose... > 20:59:31.366 /usr/bin/jackd -v -dalsa -r48000 -p512 -n2 -Xseq -D > -Chw:PCH,0 -Phw:PCH,0 > Cannot connect to server socket err = No existe el fichero o el directorio > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > 20:59:31.382 JACK se inició con PID=3144. > no message buffer overruns > no message buffer overruns > no message buffer overruns > jackdmp 1.9.12 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2016 Grame. > Copyright 2016-2017 Filipe Coelho. > jackdmp comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > JACK server starting in realtime mode with priority 10 > self-connect-mode is "Don't restrict self connect requests" > Jack: JackPosixThread::StartImp : create non RT thread > Jack: JackPosixThread::ThreadHandler : start > Jack: capture device hw:PCH,0 > Jack: playback device hw:PCH,0 > Jack: apparent rate = 48000 > Jack: frames per period = 512 > Jack: JackDriver::Open capture_driver_name = hw:PCH,0 > Jack: JackDriver::Open playback_driver_name = hw:PCH,0 > Jack: Check protocol client = 8 server = 8 > Jack: JackEngine::ClientInternalOpen: name = system > Jack: JackEngine::AllocateRefNum ref = 0 > Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0 > Jack: JackEngine::NotifyAddClient: name = system > Jack: JackGraphManager::SetBufferSize size = 512 > Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 > Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 > Jack: JackDriver::SetupDriverSync driver sem in flush mode > audio_reservation_init > Acquire audio card Audio0 > creating alsa driver ... > hw:PCH,0|hw:PCH,0|512|2|48000|0|0|nomon|swmeter|-|32bit > ATTENTION: The playback device "hw:PCH,0" is already in use. Please > stop the application using it and run JACK again > Jack: JackDriver::Close > Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 > Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 > Jack: JackEngine::ClientInternalClose ref = 0 > Jack: JackEngine::ClientCloseAux ref = 0 > Jack: JackGraphManager::RemoveAllPorts ref = 0 > Released audio card Audio0 > audio_reservation_finish > Jack: ~JackDriver > Cannot initialize driver > Jack: no message buffer overruns > Jack: JackPosixThread::Stop > Jack: JackPosixThread::ThreadHandler : exit > JackServer::Open failed with -1 > Jack: Succeeded in unlocking 82280346 byte memory area > Jack:
Re: Sound stoped unecpected
Michelle Konzack wrote: > Why does the ThinkPad crash or freeze, > if I have a power failure on the DockingStation... I assume you have the battery in the notebook - so it is perhaps something related to the power management - what dows your log say?
Re: Sound stoped unecpected
Hi, I rebooted (soft) the ThinkPad and nothing was working. Since we got a snowstorm yesterday evening (until this morning) my GSM/LTE Provider Telia was down and without internet I had to shutdown my ThinkPad. Just some minutes ago I switched on my Thinkpad and now anything is working again as expected, including sound! It seems, the hardware was crashed and could not even recover by soft rebooting the ThinkPad. Only a PowerOff will help! Now the only problem is: Why does the ThinkPad crash or freeze, if I have a power failure on the DockingStation... Thanks in advance Michelle Am 2019-02-12 hackte deb in die Tasten: > Hello Michelle. > > Just an obvious question -- do you have any way to ensure that the > actual speaker hardware was not fried in the hardware crash? > > Are you getting ANY sound from the speakers? > > > On 2/11/2019 4:37 PM, Michelle Konzack wrote: >> Good evening *, >> >> I have a ThinkPad T400 with Docking Station and whenever I have a >> power >> failer, the ThinkPad crash... I have Stretch with sysv-init running. >> >> However, I can hard reset the ThinkPad and thath it is. >> >> Today I got an unexpected result AFTER A HARD REBOOT. >> >> The sound stoped... >> >> If I run "Pulse Audio Volume Control" I see the streams from VLC, >> Audacity and Firefox, but no sound is comming out of the >> loudspeakers. >> >> Doe someone had a similar problem and know how to solv it? >> >> I have already called alsamixer and moved all settings arround, >> but noting helps. >> >> Thanks in advance >> > > -- -- Michelle Konzack 00372-54541400
Re: Sound stoped unecpected
Hello Michelle. Just an obvious question -- do you have any way to ensure that the actual speaker hardware was not fried in the hardware crash? Are you getting ANY sound from the speakers? On 2/11/2019 4:37 PM, Michelle Konzack wrote: Good evening *, I have a ThinkPad T400 with Docking Station and whenever I have a power failer, the ThinkPad crash... I have Stretch with sysv-init running. However, I can hard reset the ThinkPad and thath it is. Today I got an unexpected result AFTER A HARD REBOOT. The sound stoped... If I run "Pulse Audio Volume Control" I see the streams from VLC, Audacity and Firefox, but no sound is comming out of the loudspeakers. Doe someone had a similar problem and know how to solv it? I have already called alsamixer and moved all settings arround, but noting helps. Thanks in advance
Re: Sound suddenly not working.
On Sun, 4 Nov 2018 02:07:16 +0300 Abdullah Ramazanoğlu said: > I find Audacious quite better than timidity for playing midi pieces. And a small audacious/midi how to (just in case someone needs it): http://redmine.audacious-media-player.org/boards/1/topics/1143?r=1610 "The MIDI plugin requires some configuration before it will work. To get to the settings for it, go to File menu -> Preferences -> Plugins page -> Input tab. Select "AMIDI-Plug (MIDI Player)" in the list of plugins and click on the Preferences button at the bottom. This will bring up a new window. Select FluidSynth in the backend list. Now go to the FluidSynth tab on the left. There will be a list (probably empty) of SoundFont files. You can use whatever SoundFont you like, but I recommend that you install the fluid-soundfont-gm package (Debian and Fedora both provide it) and add /usr/share/soundfonts/FluidR3_GM.sf2 to the list (click on the "+" button on the right to get a file browser window). Then you should be good to go!" How I did it: ~# apt-get install audacious fluid-soundfont-gm fluid-soundfont-gs Go to audacious settings and add the following soundfont files as per the explanation above: Add: /usr/share/sounds/sf2/FluidR3_GM.sf2 Add: /usr/share/sounds/sf2/FluidR3_GS.sf2 That's all. Audacity should now be able to play midi files. Note that I have installed both fluid-soundfont-gm and fluid-soundfont-gs, but I believe "gm" supersedes "gs", so fluid-soundfont-gs is probably be redundant. -- Abdullah Ramazanoğlu - İstanbul, Türkiye
Re: Sound suddenly not working.
On Sat, Nov 3, 2018 at 3:08 PM Kent West wrote: > > > I have this issue on my Sid box. Turns out that on boot-up, Timidity > takes over the sound device at a lower level that the rest of the > audio-aware parts of my system, which prevents sharing the device with > those parts. > +1 When I disabled Timidity (too Timid for my tastes though I needed its ability to render MIDI files), then my Sound worked fine. Best regards, Kenneth Parker
Re: Sound suddenly not working.
On Sat, Nov 3, 2018 at 4:57 PM Brad Rogers wrote: > On Sat, 3 Nov 2018 16:37:21 -0400 > Default User wrote: > > Hello Default, > > >Thanks. > > YW. > > >I started to wade out into that, but then decided that it's probably > >better to just wait for the fix updates to be uploaded. > > Much of the time, I do the same as you. Occasionally though, I have to > bite the bullet and get back to a working state. It shouldn't be too > before an update in Sid, anyway. > > -- > Regards _ > / ) "The blindingly obvious is > / _)radnever immediately apparent" > Save me from everybody else > Prisoners - Judgement Centre > Note: sudo mv /etc/alsa/conf.d /etc/alsa/conf.d.bak followed by a reboot seems to be at least a temporary fix. Sound works now. Thanks to "Amy Kos" (see bug report #912721).
Re: Sound suddenly not working.
On Sat, 3 Nov 2018 16:37:21 -0400 Default User wrote: Hello Default, >Thanks. YW. >I started to wade out into that, but then decided that it's probably >better to just wait for the fix updates to be uploaded. Much of the time, I do the same as you. Occasionally though, I have to bite the bullet and get back to a working state. It shouldn't be too before an update in Sid, anyway. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Save me from everybody else Prisoners - Judgement Centre pgpIHbjOVmHEN.pgp Description: OpenPGP digital signature
Re: Sound suddenly not working.
Okay, Brad. Thanks. I started to wade out into that, but then decided that it's probably better to just wait for the fix updates to be uploaded. Just home it's sooner than libtracker-sparql-2.0-0 (bug #908800 merged with 3 others, since at least 2018-09-14, No end in sight!) On Sat, Nov 3, 2018 at 3:42 PM Brad Rogers wrote: > On Sat, 3 Nov 2018 15:14:59 -0400 > Default User wrote: > > Hello Default, > > >I hate to sound stupid, but how can I revert to an earlier package > >version? (I didn't think that could be done.) > > It can, but it's not supported. IOW, if anything breaks, you get to keep > all the pieces. > > To install removed packages, you need a new repo - Debian Snapshot. It > keeps all the old packages. An example config; > > deb http://snapshot.debian.org/archive/debian/20181007/ testing main > contrib non-free > > The number part is, obviously (I hope), the date you're interested in, > using a MMMDD format. Do a search for Debian snapshot, and you'll > be able to read up on the finer points. The official Debian page is at > https://snapshot.debian.org/ > > Note especially the section regarding going back more than a dozen days > - you'll have to tweak a setting or two for it to work. > > Once you've installed the old packages, I suggest you comment out the > snapshot. Then, if you need an old package again, you've only got to > alter the date part, and away you go. > > -- > Regards _ > / ) "The blindingly obvious is > / _)radnever immediately apparent" > I'm need of your help now > Burn - Judgement Centre >
Re: Sound suddenly not working.
On Sat, 3 Nov 2018 15:14:59 -0400 Default User wrote: Hello Default, >I hate to sound stupid, but how can I revert to an earlier package >version? (I didn't think that could be done.) It can, but it's not supported. IOW, if anything breaks, you get to keep all the pieces. To install removed packages, you need a new repo - Debian Snapshot. It keeps all the old packages. An example config; deb http://snapshot.debian.org/archive/debian/20181007/ testing main contrib non-free The number part is, obviously (I hope), the date you're interested in, using a MMMDD format. Do a search for Debian snapshot, and you'll be able to read up on the finer points. The official Debian page is at https://snapshot.debian.org/ Note especially the section regarding going back more than a dozen days - you'll have to tweak a setting or two for it to work. Once you've installed the old packages, I suggest you comment out the snapshot. Then, if you need an old package again, you've only got to alter the date part, and away you go. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" I'm need of your help now Burn - Judgement Centre pgpxd7dF1oc2p.pgp Description: OpenPGP digital signature
Re: Sound suddenly not working.
On Sat, Nov 3, 2018 at 1:50 PM Pascal Obry wrote: > I'm on Debian/sid too. > > An issue in libasound2 and libglibmm-2.4-1v5. You want to revert: > > libasound2, libasound2-data to 1.1.6-1 > libasound2-plugins to 1.1.6-1+b1 > libglibmm-2.4-1v5 to 2.56.0-2 > > And the sound is back. > > -- > Pascal Obry / Magny Les Hameaux (78) > > The best way to travel is by means of imagination > > http://www.obry.net > > gpg --keyserver keys.gnupg.net --recv-key F949BD3B > > I hate to sound stupid, but how can I revert to an earlier package version? (I didn't think that could be done.)
Re: Sound suddenly not working.
On 11/3/18 12:24 PM, Frank McCormick wrote: On 11/3/18 1:09 PM, Default User wrote: Hi. Running Debian, 64-bit Unstable, Cinnamon DE, on laptop. Not very knowledgeable about sound stuff. Sound okay last night. Today did updates, no sound at all. (When in doubt, blame updates.) Cinnamon sound settings applet shows "Dummy Output" as only output device, instead of "Speakers" as previously. What to check? Same here. Running Mate on Sid. I noticed libasound2 and libasound2-data were both upgraded yesterday and then my problem started. Maybe bug-filing time ?? I have this issue on my Sid box. Turns out that on boot-up, Timidity takes over the sound device at a lower level that the rest of the audio-aware parts of my system, which prevents sharing the device with those parts. I don't remember how I discovered this - some command like "fuser -v /dev/snd/*" probably, and I still haven't *fixed* it, but I work around it my just grepping for Timidity in a "ps ax" command and then killing the resulting Timidity processes. This wouldn't work if I needed Timidity, in which case I'd need to find a real fix, but this suffices for my needs for now. May not have any relevance for y'all, though. But then again, maybe. -- Kent
Re: Sound suddenly not working.
I'm on Debian/sid too. An issue in libasound2 and libglibmm-2.4-1v5. You want to revert: libasound2, libasound2-data to 1.1.6-1 libasound2-plugins to 1.1.6-1+b1 libglibmm-2.4-1v5 to 2.56.0-2 And the sound is back. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Re: Sound suddenly not working.
* Default User [2018-11-03 13:09 -0400]: > Hi. > > Running Debian, 64-bit Unstable, Cinnamon DE, on laptop. > > Not very knowledgeable about sound stuff. > > Sound okay last night. > > Today did updates, no sound at all. (When in doubt, blame updates.) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912721 Fix is prepared. Elimar -- Obviously the human brain works like a computer. Since there are no stupid computers humans can't be stupid. There are just a few running with Windows or even CE ;-)
Re: Sound suddenly not working.
On 11/3/18 1:09 PM, Default User wrote: Hi. Running Debian, 64-bit Unstable, Cinnamon DE, on laptop. Not very knowledgeable about sound stuff. Sound okay last night. Today did updates, no sound at all. (When in doubt, blame updates.) Cinnamon sound settings applet shows "Dummy Output" as only output device, instead of "Speakers" as previously. What to check? Same here. Running Mate on Sid. I noticed libasound2 and libasound2-data were both upgraded yesterday and then my problem started. Maybe bug-filing time ?? -- Frank McCormick
Re: Sound in Stretch [SOLVED]
On Thu, 13 Sep 2018 21:03:36 +0100 Brian wrote: > On Thu 13 Sep 2018 at 20:48:35 +0100, Joe wrote: > > > On Thu, 13 Sep 2018 19:47:01 +0200 > > deloptes wrote: > > > > > Jude DaShiell wrote: > > > > > > > For screen reader users with only usb sound available, this is a > > > > show stopper. > > > > > > I see it as a temporary resolution. I think this should be > > > reported and developers should come it a fix. Do we know that > > > other usb audio devices suffer the same? > > > > > > > I've submitted a bug report. > > Bug number? > 908750. I submitted it against the kernel, so reportbug included a great deal of irrelevant information. -- Joe
Re: Sound in Stretch [SOLVED]
On Thu 13 Sep 2018 at 20:48:35 +0100, Joe wrote: > On Thu, 13 Sep 2018 19:47:01 +0200 > deloptes wrote: > > > Jude DaShiell wrote: > > > > > For screen reader users with only usb sound available, this is a > > > show stopper. > > > > I see it as a temporary resolution. I think this should be reported > > and developers should come it a fix. Do we know that other usb audio > > devices suffer the same? > > > > I've submitted a bug report. Bug number? -- Brian.
Re: Sound in Stretch [SOLVED]
On Thu, 13 Sep 2018 19:47:01 +0200 deloptes wrote: > Jude DaShiell wrote: > > > For screen reader users with only usb sound available, this is a > > show stopper. > > I see it as a temporary resolution. I think this should be reported > and developers should come it a fix. Do we know that other usb audio > devices suffer the same? > I've submitted a bug report. -- Joe
Re: Sound in Stretch [SOLVED]
Jude DaShiell wrote: > For screen reader users with only usb sound available, this is a show > stopper. I see it as a temporary resolution. I think this should be reported and developers should come it a fix. Do we know that other usb audio devices suffer the same? regards
Re: Sound in Stretch [SOLVED]
For screen reader users with only usb sound available, this is a show stopper. On Thu, 13 Sep 2018, Joe wrote: > Date: Thu, 13 Sep 2018 06:34:23 > From: Joe > To: debian-user@lists.debian.org > Subject: Re: Sound in Stretch [SOLVED] > Resent-Date: Thu, 13 Sep 2018 10:34:40 + (UTC) > Resent-From: debian-user@lists.debian.org > > On Thu, 13 Sep 2018 09:12:33 +0100 > Joe wrote: > > > On Thu, 13 Sep 2018 08:36:20 +0200 > > deloptes wrote: > > > > > > Then I looked > > > at /etc/modprobe.d/alsa-base.conf file. I noticed the following at > > > end of file. > > > > > > # Keep snd-usb-audio from beeing loaded as first soundcard > > > options snd-usb-audio index=-2 > > I would guess that this is also a default somewhere else, maybe > hardcoded, because I don't have it but do have the problem. > > > > > > > I just caught the culprit. Basically these external USB sound > > > adapters are used as secondary audio device, the above setting > > > prohibits USB sound adapter being set as default device. In my case, > > > it is a primary audio device, so I set it?s index as 0 as shown > > > below. > > > > > > # Keep snd-usb-audio from beeing loaded as first soundcard > > > options snd-usb-audio index=0 > > > > > Well done, thank you for your time and effort. > > OK, nothing in /etc/modprobe.d (this was a clean minimal installation) > so I made a file, put in that line and rebooted. > > All OK now, speaker-test and alsamixer are working, I'll get around to > loading my sound player software when I have more time. Thank you again. > > I presume this is a minor bug, a USB card really should not be forced > not to be card 0 if there is no other candidate. > > --
Re: Sound in Stretch [SOLVED]
On Thu, 13 Sep 2018 09:12:33 +0100 Joe wrote: > On Thu, 13 Sep 2018 08:36:20 +0200 > deloptes wrote: > > > Then I looked > > at /etc/modprobe.d/alsa-base.conf file. I noticed the following at > > end of file. > > > > # Keep snd-usb-audio from beeing loaded as first soundcard > > options snd-usb-audio index=-2 I would guess that this is also a default somewhere else, maybe hardcoded, because I don't have it but do have the problem. > > > > I just caught the culprit. Basically these external USB sound > > adapters are used as secondary audio device, the above setting > > prohibits USB sound adapter being set as default device. In my case, > > it is a primary audio device, so I set it’s index as 0 as shown > > below. > > > > # Keep snd-usb-audio from beeing loaded as first soundcard > > options snd-usb-audio index=0 > > Well done, thank you for your time and effort. OK, nothing in /etc/modprobe.d (this was a clean minimal installation) so I made a file, put in that line and rebooted. All OK now, speaker-test and alsamixer are working, I'll get around to loading my sound player software when I have more time. Thank you again. I presume this is a minor bug, a USB card really should not be forced not to be card 0 if there is no other candidate. -- Joe
Re: Sound in Stretch
On Thu, 13 Sep 2018 08:36:20 +0200 deloptes wrote: > Joe wrote: > > > On Tue, 11 Sep 2018 08:23:58 +0200 > > deloptes wrote: > > I also found this > http://karuppuswamy.com/wordpress/2010/10/04/how-to-get-usb-sound-adapter-0d8c000c-working-as-primary-sound-card-in-debian-linux/ > > > When I googled, I was adviced to try without USB hub. So I directly > connected to Server without using external USB hub… but no > improvement. I don’t have any other audio device (not even internal > audio card). Debian Squeeze does not come with alsaconf utility to > detect and install the necessary modules. It is done automatically. > In my case it loads all modules and also there is no error message > while starting ALSA at startup. Then I looked > at /etc/modprobe.d/alsa-base.conf file. I noticed the following at > end of file. > > # Keep snd-usb-audio from beeing loaded as first soundcard > options snd-usb-audio index=-2 > > I just caught the culprit. Basically these external USB sound > adapters are used as secondary audio device, the above setting > prohibits USB sound adapter being set as default device. In my case, > it is a primary audio device, so I set it’s index as 0 as shown below. > > # Keep snd-usb-audio from beeing loaded as first soundcard > options snd-usb-audio index=0 > > Well done, thank you for your time and effort. So my wild guess was right, then? There was a clue in that the USB device was being allocated as sound card 1, with no sound card 0. As I posted a few weeks ago, it's probably a year or more since I had any sound trouble, and I'd forgotten that the count was 0-based. But it's good that there's an easier way than buying another sound card. I'm pushed for time right now, but I'll try this later today. -- Joe
Re: Sound in Stretch
Joe wrote: > On Tue, 11 Sep 2018 08:23:58 +0200 > deloptes wrote: I also found this http://karuppuswamy.com/wordpress/2010/10/04/how-to-get-usb-sound-adapter-0d8c000c-working-as-primary-sound-card-in-debian-linux/ When I googled, I was adviced to try without USB hub. So I directly connected to Server without using external USB hub… but no improvement. I don’t have any other audio device (not even internal audio card). Debian Squeeze does not come with alsaconf utility to detect and install the necessary modules. It is done automatically. In my case it loads all modules and also there is no error message while starting ALSA at startup. Then I looked at /etc/modprobe.d/alsa-base.conf file. I noticed the following at end of file. # Keep snd-usb-audio from beeing loaded as first soundcard options snd-usb-audio index=-2 I just caught the culprit. Basically these external USB sound adapters are used as secondary audio device, the above setting prohibits USB sound adapter being set as default device. In my case, it is a primary audio device, so I set it’s index as 0 as shown below. # Keep snd-usb-audio from beeing loaded as first soundcard options snd-usb-audio index=0
Re: Sound in Stretch
Joe wrote: > That's not on any compatibility list anywhere, but it has worked OK for > years on Wheezy on the same computer hardware. Anyway, USB is USB, and > there really shouldn't be compatibility issues for at least basic > playback. I'm not trying to record or use SPDIF. could be that support in the snd_usb_audio driver is not provided anymore for this device or is not working properly ... and BTW USB is not USB - there is USB1, USB2 and now USB3 I still think if you don't see the device, the card is unsupported in the usb audio driver So I looked for you in the kernel config - it looks like the hid you find are the audio jack controls, but I do not see the second one. I think it is a problem with the codec or you need to load SND_HDA_GENERIC and SND_HDA_CODEC_CMEDIA perhaps they are not autoloaded you could also try loading the intel hda driver, it should pull related (if it succeeds to load without hardware) regards Symbol: HID_CMEDIA [=n] â â Type : tristate â â Prompt: CMedia CM6533 HID audio jack controls â â Location: â â -> Device Drivers â â -> HID support â â -> HID bus support (HID [=y]) â â (1) -> Special HID drivers â â Defined at drivers/hid/Kconfig:225 â â Depends on: INPUT [=y] && HID [=y] â â â â â â Symbol: SND_HDA_CODEC_CMEDIA [=m] â â Type : tristate â â Prompt: Build C-Media HD-audio codec support â â Location: â â -> Device Drivers â â -> Sound card support (SOUND [=m]) â â -> Advanced Linux Sound Architecture (SND [=m]) â â (2) -> HD-Audio â â Defined at sound/pci/hda/Kconfig:189 â â Depends on: SOUND [=m] && !UML && SND [=m] && SND_HDA [=m] â â Selects: SND_HDA_GENERIC [=m]
Re: Sound in Stretch
On Tue, 11 Sep 2018 08:53:39 -0400 Greg Wooledge wrote: > > > does the command alsa-info give a clue? > > > > I didn't know about that one. It gives pages of stuff that look like > > what I used to find in /proc/asound, it certainly knows all about > > the USB device. No error messages, no suggestion as to what might be > > missing. > > Since it's USB, the obvious next step is "lsusb". > > Or, really, *any* information you can provide about this USB sound > device would be useful at this point. > OK, a bit more. After some crawling under furniture, I was able to plug the device into my netbook, running 32-bit Stretch. It works fine there. I did lsmod, and apart from some snd_hda_ modules for the built-in sound, there are no modules there that aren't also in the server. The codecs are all HDA. Back on the server: ~$ sudo lsusb . . Bus 004 Device 005: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound Device . . That's not on any compatibility list anywhere, but it has worked OK for years on Wheezy on the same computer hardware. Anyway, USB is USB, and there really shouldn't be compatibility issues for at least basic playback. I'm not trying to record or use SPDIF. ~$ sudo lshw -C sound *-usb:1 description: Audio device product: USB Sound Device vendor: C-Media Electronics, Inc. physical id: 5 bus info: usb@4:5 version: 0.10 capabilities: usb-1.10 audio-control configuration: driver=usbhid maxpower=500mA speed=12Mbit/s ~$ sudo lsmod | grep usbhid usbhid 53248 0 hid 122880 2 hid_generic,usbhid usbcore 253952 9 usbhid,snd_usb_audio,usb_storage,ehci_hcd,ohci_pci,snd_usbmidi_lib,uas,ohci_hcd,ehci_pci ~$ sudo lsmod | grep snd snd_usb_audio 180224 0 snd_usbmidi_lib28672 1 snd_usb_audio snd_hwdep 16384 1 snd_usb_audio snd_rawmidi32768 1 snd_usbmidi_lib snd_seq_device 16384 1 snd_rawmidi snd_pcm 110592 1 snd_usb_audio snd_timer 32768 1 snd_pcm snd86016 7 snd_hwdep,snd_usb_audio,snd_timer,snd_rawmidi,snd_usbmidi_lib,snd_seq_device,snd_pcm soundcore 16384 1 snd usbcore 253952 9 usbhid,snd_usb_audio,usb_storage,ehci_hcd,ohci_pci,snd_usbmidi_lib,uas,ohci_hcd,ehci_pci ~$ speaker-test speaker-test 1.1.3 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise ALSA lib confmisc.c:767:(parse_card) cannot find card '0' ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default Playback open error: -2,No such file or directory Presumably this is just a fancy way of saying that /proc/asound isn't there. I did the alsa-info, but that produces a really huge ream of stuff, and I can't see any errors or warnings in it. There was a warning flashed up for a millisecond or two during the gathering of data: pcilib: sysfs_read_vpd: read failed: input/output error but I'm not sure that is relevant. There is a long list of card capabilities produced, so there's communication going on. -- Joe
Re: Sound in Stretch
On Mon, 10 Sep 2018, arne wrote: > Date: Mon, 10 Sep 2018 17:26:56 > From: arne > To: deloptes > Cc: debian-user@lists.debian.org, sp113...@telfort.nl > Subject: Re: Sound in Stretch > Resent-Date: Mon, 10 Sep 2018 21:27:13 + (UTC) > Resent-From: debian-user@lists.debian.org > > On Mon, 10 Sep 2018 22:49:34 +0200 > deloptes wrote: > > > Joe wrote: > > > > > alsamixer > > > > > > cannot open mixer: No such file or directory > > > > > > I always used to start sound troubleshooting by looking > > > in /proc/asound to find out what the system thought my sound cards > > > were, but that directory no longer exists. > > > > you sure you have the driver loaded? > > > > ls -al /proc/asound/ > > total 0 > > dr-xr-xr-x 6 root root 0 Sep 10 19:50 . > > dr-xr-xr-x 253 root root 0 Sep 10 21:49 .. > > dr-xr-xr-x 8 root root 0 Sep 10 19:50 card0 > > dr-xr-xr-x 3 root root 0 Sep 10 19:50 card1 > > -r--r--r-- 1 root root 0 Sep 10 19:50 cards > > -r--r--r-- 1 root root 0 Sep 10 22:48 devices > > -r--r--r-- 1 root root 0 Sep 10 22:48 hwdep > > -r--r--r-- 1 root root 0 Sep 10 22:48 modules > > dr-xr-xr-x 2 root root 0 Sep 10 22:48 oss > > lrwxrwxrwx 1 root root 5 Sep 10 22:48 PCH -> card0 > > -r--r--r-- 1 root root 0 Sep 10 22:48 pcm > > dr-xr-xr-x 2 root root 0 Sep 10 22:48 seq > > -r--r--r-- 1 root root 0 Sep 10 22:48 timers > > -r--r--r-- 1 root root 0 Sep 10 22:48 version > > lrwxrwxrwx 1 root root 5 Sep 10 22:48 Webcam -> card1 > > > > stretch > > > > regards > > > > does the command alsa-info give a clue? > If that doesn't work, aplay -l may help. > --
Re: Sound in Stretch
> > does the command alsa-info give a clue? > > I didn't know about that one. It gives pages of stuff that look like > what I used to find in /proc/asound, it certainly knows all about the > USB device. No error messages, no suggestion as to what might be > missing. Since it's USB, the obvious next step is "lsusb". Or, really, *any* information you can provide about this USB sound device would be useful at this point.
Re: Sound in Stretch
Curt wrote: > curty@einstein:~$ /usr/sbin/alsa > alsabat-test alsactl alsa-info thanks - i didn't look in sbin regards
Re: Sound in Stretch
Joe wrote: > Is there conceivably an issue in Stretch of having USB sound but no > on-board sound? Is that causing the boot process not to build the sound > infrastructure properly? There is a spare PCIe slot, but it's tiny, and > I'm not sure I can get a cheap card that will physically fit. I do not think it is required to have any audio device. Your use case should work, but it might be a kernel/driver issue - don't have time to check now, but you can check if the device is supported in the kernel you have now. then it should work when plugged in (udev etc). many things changes since wheezy regards
Re: Sound in Stretch
On Tue, 11 Sep 2018 08:23:58 +0200 deloptes wrote: > Joe wrote: > > > On Mon, 10 Sep 2018 22:54:26 +0200 > > > > > OK, aplay -l as root sees my USB device as card 1. > > why as root - are you in the audio group? No users in audio yet apart from the original installation user. The ssh user doesn't need sound, which will only ever be used by www-data. But the infrastructure should be present without anyone logged in. In the past, I've always been able to see /proc/asound as root. It's just not there now. /dev sees the device. I do have a Stretch workstation, also a clean installation, but that has on-board Intel sound and is therefore a different beast. It certainly does have a /proc/asound. I also plugged in another USB sound device to the server, also as it happens a C-Media device, but a different, much older one. Exactly the same: syslog sees it being recognised, aplay -l sees it, but speaker-test still can't see it and no additional modules are loaded. Still no sign of /proc/asound, which I think is the main fault symptom. > > $ grep audio /etc/group > audio:x:29:abcdef,pulse,timidity > > > > > I have various sound modules loaded, including snd, soundcore and > > snd_usb_audio. I assume from this that my device driver has been > > found. > > > > Speaker-test is unable to find any sound cards. > > what is the sound card, mainboard etc.? It's a C-Media USB device, described by lsusb as a 'CM106 Like Sound Device'. I can't see any obvious problems with this sort of thing on the Net. The computer is a HP Proliant Microserver with AMD CPU and graphics. It doesn't appear to have any on-board sound, and lshw doesn't name the MB. Again, this computer and sound device did work under Wheezy. I've been using the device since before Wheezy, and bought it to replace the older C-Media device. That was a very cheap VOIP device and seemed a bit flaky, occasionally disconnecting from USB and immediately reconnecting. Both devices produced sound OK. Is there conceivably an issue in Stretch of having USB sound but no on-board sound? Is that causing the boot process not to build the sound infrastructure properly? There is a spare PCIe slot, but it's tiny, and I'm not sure I can get a cheap card that will physically fit. -- Joe
Re: Sound in Stretch
On Tue 11 Sep 2018 at 08:23:58 +0200, deloptes wrote: > Joe wrote: > > > On Mon, 10 Sep 2018 22:54:26 +0200 > > > > > OK, aplay -l as root sees my USB device as card 1. > > why as root - are you in the audio group? Having a user in the audio group is unnecessary. ACLs on the devices are used. brian@desktop:~$ ls -l /dev/snd/ total 0 drwxr-xr-x 2 root root 60 Jul 9 09:45 by-path crw-rw+ 1 root audio 116, 2 Jul 9 09:45 controlC0 crw-rw+ 1 root audio 116, 4 Aug 28 18:56 pcmC0D0c crw-rw+ 1 root audio 116, 3 Sep 10 20:45 pcmC0D0p crw-rw+ 1 root audio 116, 6 Jul 9 09:45 pcmC0D1c crw-rw+ 1 root audio 116, 5 Jul 9 09:45 pcmC0D1p crw-rw+ 1 root audio 116, 1 Jul 14 20:58 seq crw-rw+ 1 root audio 116, 33 Jul 14 20:58 timer brian@desktop:~$ getfacl /dev/snd/timer getfacl: Removing leading '/' from absolute path names # file: dev/snd/timer # owner: root # group: audio user::rw- user:brian:rw- group::rw- mask::rw- other::--- -- Brian.
Re: Sound in Stretch
On Tue 11 Sep 2018 at 08:27:02 +0200, deloptes wrote: > Brian wrote: > > > alsa-base > > in stretch there is no alsa-base That isn't in dispute. -- Brian.
Re: Sound in Stretch
On 2018-09-11, deloptes wrote: > arne wrote: > >> does the command alsa-info give a clue? > > what is alsa-info? > > $ alsa > alsabatalsa_inalsaloop alsamixer alsa_out alsatplg alsaucm > > regards > > > curty@einstein:~$ /usr/sbin/alsa alsabat-test alsactl alsa-info You're a hacker all right, bless your heart.
Re: Sound in Stretch
Brian wrote: > alsa-base in stretch there is no alsa-base $ dpkg -l | grep alsa ii alsa-utils 1.1.3-1 amd64Utilities for configuring and using ALSA ii gstreamer1.0-alsa:amd64 1.10.4-1 amd64GStreamer plugin for ALSA ii libsox-fmt-alsa:amd64 14.4.1-5+b2 amd64SoX alsa format I/O library ii libzita-alsa-pcmi0:amd640.2.0-4 amd64C++ wrapper around the ALSA API
Re: Sound in Stretch
Joe wrote: > On Mon, 10 Sep 2018 22:54:26 +0200 > > OK, aplay -l as root sees my USB device as card 1. why as root - are you in the audio group? $ grep audio /etc/group audio:x:29:abcdef,pulse,timidity > > I have various sound modules loaded, including snd, soundcore and > snd_usb_audio. I assume from this that my device driver has been found. > > Speaker-test is unable to find any sound cards. what is the sound card, mainboard etc.? For example here I have intel HD based card on the board and a web cam attached (the usb) and HDMI display link. You can ignore the midi. So good modules loaded look like this $ lsmod | grep snd snd_usb_audio 184320 2 snd_usbmidi_lib28672 1 snd_usb_audio snd_rawmidi32768 1 snd_usbmidi_lib snd_seq_device 16384 1 snd_rawmidi snd_hda_codec_hdmi 57344 1 snd_hda_codec_conexant20480 1 snd_hda_codec_generic77824 1 snd_hda_codec_conexant snd_hda_intel 32768 4 snd_hda_codec 118784 4 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel snd_hwdep 16384 2 snd_usb_audio,snd_hda_codec snd_hda_core 65536 5 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec snd_pcm 102400 5 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core snd_timer 32768 1 snd_pcm snd81920 24 snd_hda_codec_generic,snd_hda_codec_conexant,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_timer,snd_pcm,snd_rawmidi soundcore 16384 1 snd usbcore 221184 10 xhci_hcd,ehci_pci,snd_usb_audio,usbhid,snd_usbmidi_lib,uvcvideo,ehci_hcd,btusb,xhci_pci,uhci_hcd
Re: Sound in Stretch
Joe wrote: > It occurs to me that there are no snd_xxx_codec modules loaded. Is that > significant? yes - seems like - what is your sound card - manufacturer?
Re: Sound in Stretch
arne wrote: > does the command alsa-info give a clue? what is alsa-info? $ alsa alsabatalsa_inalsaloop alsamixer alsa_out alsatplg alsaucm regards
Re: Sound in Stretch
On 09/10/2018 04:22 PM, Greg Wooledge wrote: On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote: There's no alsa-base in Stretch. Should there be some other way of producing sounds? If you're looking for alsamixer, it's in alsa-utils. ALSA should just work out of the box for most users who skip the Desktop Environment during the installation (and therefore do not have to circumvent pulse). The only steps required for most people are to install alsa-utils, run alsamixer, unmute the master channels, and raise the volume of the master channels above zero. You have to do that even with pulse up and running. Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html
Re: Sound in Stretch
On Mon, 10 Sep 2018 22:50:30 +0100 Joe wrote: > On Mon, 10 Sep 2018 23:26:56 +0200 > arne wrote: > > > On Mon, 10 Sep 2018 22:49:34 +0200 > > deloptes wrote: > > > > > Joe wrote: > > > > > > > alsamixer > > > > > > > > cannot open mixer: No such file or directory > > > > > > > > I always used to start sound troubleshooting by looking > > > > in /proc/asound to find out what the system thought my sound > > > > cards were, but that directory no longer exists. > > > > > > you sure you have the driver loaded? > > > I have sound modules loaded, which I thought meant the driver must > have been found. > It occurs to me that there are no snd_xxx_codec modules loaded. Is that significant? -- Joe
Re: Sound in Stretch
On Mon, 10 Sep 2018 22:54:26 +0200 wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Mon, Sep 10, 2018 at 09:33:30PM +0100, Joe wrote: > > On Mon, 10 Sep 2018 16:22:38 -0400 > > Greg Wooledge wrote: > > > > > On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote: > > > > > > > > There's no alsa-base in Stretch. > > > > > > > > Should there be some other way of producing sounds? > > > > > > If you're looking for alsamixer, it's in alsa-utils. ALSA should > > > just work out of the box for most users who skip the Desktop > > > Environment during the installation (and therefore do not have to > > > circumvent pulse). > > > > > > The only steps required for most people are to install alsa-utils, > > > run alsamixer, unmute the master channels, and raise the volume > > > of the master channels above zero. > > > > > > > Thank you for an extremely prompt reply, but I've been there and > > done that: > > > > alsa-utils is already installed at the requested version (1.1.3-1) > > > > alsamixer > > > > cannot open mixer: No such file or directory > > You could try to list your cards and devices with aplay -l > > OK, aplay -l as root sees my USB device as card 1. I have various sound modules loaded, including snd, soundcore and snd_usb_audio. I assume from this that my device driver has been found. Speaker-test is unable to find any sound cards. -- Joe
Re: Sound in Stretch
On Mon, 10 Sep 2018 23:26:56 +0200 arne wrote: > On Mon, 10 Sep 2018 22:49:34 +0200 > deloptes wrote: > > > Joe wrote: > > > > > alsamixer > > > > > > cannot open mixer: No such file or directory > > > > > > I always used to start sound troubleshooting by looking > > > in /proc/asound to find out what the system thought my sound cards > > > were, but that directory no longer exists. > > > > you sure you have the driver loaded? I have sound modules loaded, which I thought meant the driver must have been found. > > > > ls -al /proc/asound/ > > total 0 > > dr-xr-xr-x 6 root root 0 Sep 10 19:50 . > > dr-xr-xr-x 253 root root 0 Sep 10 21:49 .. > > dr-xr-xr-x 8 root root 0 Sep 10 19:50 card0 > > dr-xr-xr-x 3 root root 0 Sep 10 19:50 card1 > > -r--r--r-- 1 root root 0 Sep 10 19:50 cards > > -r--r--r-- 1 root root 0 Sep 10 22:48 devices > > -r--r--r-- 1 root root 0 Sep 10 22:48 hwdep > > -r--r--r-- 1 root root 0 Sep 10 22:48 modules > > dr-xr-xr-x 2 root root 0 Sep 10 22:48 oss > > lrwxrwxrwx 1 root root 5 Sep 10 22:48 PCH -> card0 > > -r--r--r-- 1 root root 0 Sep 10 22:48 pcm > > dr-xr-xr-x 2 root root 0 Sep 10 22:48 seq > > -r--r--r-- 1 root root 0 Sep 10 22:48 timers > > -r--r--r-- 1 root root 0 Sep 10 22:48 version > > lrwxrwxrwx 1 root root 5 Sep 10 22:48 Webcam -> card1 > > > > stretch > > > > regards > > > > does the command alsa-info give a clue? > I didn't know about that one. It gives pages of stuff that look like what I used to find in /proc/asound, it certainly knows all about the USB device. No error messages, no suggestion as to what might be missing. -- Joe
Re: Sound in Stretch
On Mon 10 Sep 2018 at 21:19:09 +0100, Joe wrote: > > There's no alsa-base in Stretch. > > Should there be some other way of producing sounds? In jessie alsa-base has precisely two files: /usr/share/doc/alsa-base/changelog.gz /usr/share/doc/alsa-base/copyright It is doubtful either of these is invovloved in the production of sound. Also: https://metadata.ftp-master.debian.org/changelogs/main/a/alsa-base/alsa-base_1.0.27+1_changelog * The still-useful bits of alsa-base (kmod configuration files) have moved to kmod itself in version 17-1. There is nothing of use left in alsa-base, so for jessie, it'll just become a dummy package that helps cleaning up its old conffiles. It will be dropped after the jessie release. You obviously have some issue with sound but it is impossible to discover what it is. -- Brian.
Re: Sound in Stretch
On Mon, 10 Sep 2018 22:49:34 +0200 deloptes wrote: > Joe wrote: > > > alsamixer > > > > cannot open mixer: No such file or directory > > > > I always used to start sound troubleshooting by looking > > in /proc/asound to find out what the system thought my sound cards > > were, but that directory no longer exists. > > you sure you have the driver loaded? > > ls -al /proc/asound/ > total 0 > dr-xr-xr-x 6 root root 0 Sep 10 19:50 . > dr-xr-xr-x 253 root root 0 Sep 10 21:49 .. > dr-xr-xr-x 8 root root 0 Sep 10 19:50 card0 > dr-xr-xr-x 3 root root 0 Sep 10 19:50 card1 > -r--r--r-- 1 root root 0 Sep 10 19:50 cards > -r--r--r-- 1 root root 0 Sep 10 22:48 devices > -r--r--r-- 1 root root 0 Sep 10 22:48 hwdep > -r--r--r-- 1 root root 0 Sep 10 22:48 modules > dr-xr-xr-x 2 root root 0 Sep 10 22:48 oss > lrwxrwxrwx 1 root root 5 Sep 10 22:48 PCH -> card0 > -r--r--r-- 1 root root 0 Sep 10 22:48 pcm > dr-xr-xr-x 2 root root 0 Sep 10 22:48 seq > -r--r--r-- 1 root root 0 Sep 10 22:48 timers > -r--r--r-- 1 root root 0 Sep 10 22:48 version > lrwxrwxrwx 1 root root 5 Sep 10 22:48 Webcam -> card1 > > stretch > > regards > does the command alsa-info give a clue?
Re: Sound in Stretch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Sep 10, 2018 at 09:33:30PM +0100, Joe wrote: > On Mon, 10 Sep 2018 16:22:38 -0400 > Greg Wooledge wrote: > > > On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote: > > > > > > There's no alsa-base in Stretch. > > > > > > Should there be some other way of producing sounds? > > > > If you're looking for alsamixer, it's in alsa-utils. ALSA should just > > work out of the box for most users who skip the Desktop Environment > > during the installation (and therefore do not have to circumvent > > pulse). > > > > The only steps required for most people are to install alsa-utils, > > run alsamixer, unmute the master channels, and raise the volume of the > > master channels above zero. > > > > Thank you for an extremely prompt reply, but I've been there and done > that: > > alsa-utils is already installed at the requested version (1.1.3-1) > > alsamixer > > cannot open mixer: No such file or directory You could try to list your cards and devices with aplay -l Cheers - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAluW2gIACgkQBcgs9XrR2kb4nQCfX7n92ERILwZehpOfSPeBCQe2 9wcAnAjGPYoWMLBpyI9uu2OjVImBxICg =4GJO -END PGP SIGNATURE-
Re: Sound in Stretch
Joe wrote: > alsamixer > > cannot open mixer: No such file or directory > > I always used to start sound troubleshooting by looking in /proc/asound > to find out what the system thought my sound cards were, but that > directory no longer exists. you sure you have the driver loaded? ls -al /proc/asound/ total 0 dr-xr-xr-x 6 root root 0 Sep 10 19:50 . dr-xr-xr-x 253 root root 0 Sep 10 21:49 .. dr-xr-xr-x 8 root root 0 Sep 10 19:50 card0 dr-xr-xr-x 3 root root 0 Sep 10 19:50 card1 -r--r--r-- 1 root root 0 Sep 10 19:50 cards -r--r--r-- 1 root root 0 Sep 10 22:48 devices -r--r--r-- 1 root root 0 Sep 10 22:48 hwdep -r--r--r-- 1 root root 0 Sep 10 22:48 modules dr-xr-xr-x 2 root root 0 Sep 10 22:48 oss lrwxrwxrwx 1 root root 5 Sep 10 22:48 PCH -> card0 -r--r--r-- 1 root root 0 Sep 10 22:48 pcm dr-xr-xr-x 2 root root 0 Sep 10 22:48 seq -r--r--r-- 1 root root 0 Sep 10 22:48 timers -r--r--r-- 1 root root 0 Sep 10 22:48 version lrwxrwxrwx 1 root root 5 Sep 10 22:48 Webcam -> card1 stretch regards
Re: Sound in Stretch
On Mon, 10 Sep 2018 16:22:38 -0400 Greg Wooledge wrote: > On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote: > > > > There's no alsa-base in Stretch. > > > > Should there be some other way of producing sounds? > > If you're looking for alsamixer, it's in alsa-utils. ALSA should just > work out of the box for most users who skip the Desktop Environment > during the installation (and therefore do not have to circumvent > pulse). > > The only steps required for most people are to install alsa-utils, > run alsamixer, unmute the master channels, and raise the volume of the > master channels above zero. > Thank you for an extremely prompt reply, but I've been there and done that: alsa-utils is already installed at the requested version (1.1.3-1) alsamixer cannot open mixer: No such file or directory I always used to start sound troubleshooting by looking in /proc/asound to find out what the system thought my sound cards were, but that directory no longer exists. This, by the way, is a clean no-X installation of Stretch, running in hardware that previously ran Wheezy, with working sound. The sound 'card' is a cheap generic USB thing, which the kernel is seeing. Various sound modules are loaded. I presume I've got to install or configure something else, but I can't find the slightest clue on the Net. One Debian sound page refers to Sarge... -- Joe -- Joe
Re: Sound in Stretch
On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote: > > There's no alsa-base in Stretch. > > Should there be some other way of producing sounds? If you're looking for alsamixer, it's in alsa-utils. ALSA should just work out of the box for most users who skip the Desktop Environment during the installation (and therefore do not have to circumvent pulse). The only steps required for most people are to install alsa-utils, run alsamixer, unmute the master channels, and raise the volume of the master channels above zero.
Re: (solved) Re: sound card problem
David Christensen wrote: > I would expect personal computer sound card line-in and microphone > inputs to use the same design analog-to-digital converter. So, the > sampling rates and bit depths should be the same. > > > But, microphone inputs are usually monaural. So, if you use a stereo > patch cable from your television to your computer, you will only hear > the left channel. > > > And, microphone inputs usually have more analog gain. So, you will need > to turn the television volume down and/or reduce the microphone gain in > your mixer application. Either can reduce the signal quality. Failure > to do so will result in clipping. > > > You will get the best recording if you connect the television line-out > to the computer line-in and match the signal levels. He does not know what brand his PC is and no info on the card - it is hard to say where and how it should be plugged in. regards
Re: (solved) Re: sound card problem
On 09/05/2018 05:35 PM, Long Wind wrote: PS: is recording quality of mic same as linein? I would expect personal computer sound card line-in and microphone inputs to use the same design analog-to-digital converter. So, the sampling rates and bit depths should be the same. But, microphone inputs are usually monaural. So, if you use a stereo patch cable from your television to your computer, you will only hear the left channel. And, microphone inputs usually have more analog gain. So, you will need to turn the television volume down and/or reduce the microphone gain in your mixer application. Either can reduce the signal quality. Failure to do so will result in clipping. You will get the best recording if you connect the television line-out to the computer line-in and match the signal levels. David
Re: sound card problem
On Wed 05 Sep 2018 at 00:15:23 (+), Long Wind wrote: > sorry, this question isn't linux specific It's unspecific in several other ways. > TV audio output What sort of output? Intended for speakers, or headphones, or a line-style output. > is connected to linein of my sound card What sound card is that? Enumerate the inputs and outputs, how they are labelled, and which ones you are using. > speaker is connected to output of sound card What, directly? Full-size passive speakers, or active ones with some sort of amplification built into them. > tv sound can be heard even when pc is shut down How loud? Just as loud as when the PC is running with the mixers turned up, turned down, muted? Or just loud enough to be a distraction if you're, say, dozing/sleeping in the same room? > i have to turn off speaker, this isn't convenient You say "turn off" rather than "disconnect". Is that because the speakers are being run from an amplifier that's independent of the sound card? > i mute all in mixer before shutting down stretch, it doesn't help > is there any solution? Thanks! Dunno. But it helps to have the problem explained. We can't do house calls! Cheers, David.
Re: sound card problem
On 9/5/18, deloptes wrote: > Long Wind wrote: > >> Thank deloptes! >> >> i'm unable to find manual for motherboardand i browse thru BIOS menu, >> unable to find related option > > you hear sound even when you turn off and unplug your computer? That's what I'm imagining from the description, too. Sounds like all power's off to the computer... so I'm imagining that... The card doesn't need "power" to work? Apparently no. This is the first time I've ever thought about that aspect. That's a constant checkpoint for things like those CHEAP $5 external hard drive adapters that have no enclosures, but it's never been a factor for PCI'ish/plugs into the motherboard type hardware. Is there some kind of direct wiring going on between the linein and lineout points? Yeah, I know, never mind on that one. There has to be something like that for it to work even when the power switch is on. Something goes in and can only go back out if there is an unbroken line of connectivity somehow within the product. :) Those thoughts are coming from sitting here reading Long Wind's description while knowing that my speakers power on and off separate from the computer. Wish I had some way to (kicks 'n' giggles) test the same to see if mine duplicates the result. Afterthought: This is a stretch of the imagination, YES, but Is there any way it could be seen as an exploitable vulnerability where it's possible to interact within the computer even when it's turned off completely? Absolute worse, hopefully totally impossible scenario would be that the boogeyman burglar busts into your office one night, plants some bad mojo on that PCI card, you boot up your computer the next morning, and off that bad mojo goes running throughout the rest of the internal workings... Yes, I do understand that the card would have to be capable of certain [tasks]. If that card's not capable, maybe others are? > input/output might be shortened on the board - why would you look at BIOS? Hail Mary pass...? Apparently because it's that annoying a (dis)feature? :) Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with duct tape *
Re: sound card problem
Long Wind wrote: > Thank deloptes! > > i'm unable to find manual for motherboardand i browse thru BIOS menu, > unable to find related option you hear sound even when you turn off and unplug your computer? input/output might be shortened on the board - why would you look at BIOS? regards
Re: sound card problem
Long Wind wrote: > i mute all in mixer before shutting down stretch, it doesn't help > is there any solution? Thanks! why do you think it is a software issue? After machine is switched off the software is dead. Look at the description of the mainboard
