Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

New Dell Inspiron 15 3000 Series 3511 sound problem on Debian 11 Stable

452 views
Skip to first unread message

Default User

unread,
Feb 9, 2023, 8:00:06 PM2/9/23
to
Hello to all!

I just got a brand new Dell Inspiron 15 3000 Series 3511 laptop.  Came with Windows (ugh!) preinstalled.
My old Dell Inspiron 15 3000 Series 3542 laptop (made in 2014) just died.  So this one should work, right? 

No. 

Unfortunately the new 3511 is quite different from the old 3542.  It mostly "sort of" works. 
But the sound will not work at all on Debian.

Not wanting to immediately remove Windows and thus make it unreturnable, I have been trying to run it using a
Debian 11 "Live" install USB thumb drive (Cinnamon desktop).  No sound at all. 

But . . .  it DOES work when running the computer from a USB thumb drive of the most recent version of
SystemRescue!  So, it CAN work (somehow) on (some) Linux setups.

Note: System Rescue is now based upon Arch Linux.

Using the Debian 11 USB thumb drive, I was not able to do a complete update and upgrade - not enough room on the
USB thumb drive.  I was able to install the pavucontrol package, which I recall has sometimes helped in the past. 
But still no sound.

The dumbed-down make-believe BIOS on the new computer lists the Audio Controller as:
"Cirrus Logic CS8409". 

SystemRescue reports under PCI devices:
Intel Tiger Lake-LP Smart Sound Technology Audio Controller.  
"Driver in Use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl".

In Debian 11 "Live", lspci -nn reports:
"00:1f.3 Audio device [0403]: Intel Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)".

I poked around in the Debian wiki about fixing sound problems, but to be honest, much of it is over my head. 

So . . .  any advice on how to get sound to work on this computer?
Or, failing that, any suggestions for a good (preferable affordable) laptop that plays nice with Debian?

I guess I could try to use Arch or some other Linux distribution, but I have used Debian for many years, and would
really hate changing to something else. 


Timothy M Butterworth

unread,
Feb 9, 2023, 11:00:06 PM2/9/23
to

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

Anssi Saari

unread,
Feb 10, 2023, 7:40:05 AM2/10/23
to
Default User <hungupo...@gmail.com> writes:

> In Debian 11 "Live", lspci -nn reports:
> "00:1f.3 Audio device [0403]: Intel Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev
> 20)".

This isn't new sound hardware so should work in Debian 11.

With a quick look, you probably need the non-free package
firmware-sof-signed but that isn't included in the Debian 11 live. You
could try an image which contains those things from

https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/11.6.0-live+nonfree/amd64/iso-hybrid/

Or, if you're familiar in Debian, maybe you can install the
firmware-sof-signed pacakge in the live system you already have? I'm not
sure if that's possible there, I haven't used Debian Live in a while.

Default User

unread,
Feb 10, 2023, 5:00:06 PM2/10/23
to
[UPDATE:]

I did try Debian 11.6 "live" .  Again, No sound. 

BTW,
sudo apt show firmware-sof-signed
shows firmware-sof-signed as installed for both Debian Live 11.0
and Debian Live 11.6. :

----------

[From Debian 11.6]:
Package: firmware-sof-signed
Version: 1.7-1
Status: install ok installed
Priority: optional
Section: non-free/kernel
Source: firmware-sof
Maintainer: Mark Pearson <markp...@lenovo.com>
Installed-Size: 10.1 MB
Homepage: https://github.com/thesofproject/sof-bin
Download-Size: unknown
APT-Manual-Installed: yes
APT-Sources: /var/lib/dpkg/status
Description: Intel SOF firmware - signed
 Provides the Intel SOF audio firmware and topology needed for audio
 functionality on some Intel system.
 .
 This package contains the pre-built and signed binaries.

----------

I have not yet tried Bookworm, as I do not know where to find a "Live" image of that,
and again, I do not want to install it (yet) on the computer's internal SSD, since that
would make the computer unreturnable. 

Perhaps I could use the Bookworm weekly build to install to an external usb device,
and try running it from there, to verify that the sound does work on the computer, before
installing to the internal ssd. 

Is that feasible?

And of course recommendations for a current laptop (preferably reasonably priced)
that actual experience shows does work well with Debian would be welcome.


Charles Curley

unread,
Feb 10, 2023, 6:20:07 PM2/10/23
to
On Fri, 10 Feb 2023 21:49:58 +0000
Default User <hungupo...@gmail.com> wrote:

> And of course recommendations for a current laptop (preferably
> reasonably priced)
> that actual experience shows does work well with Debian would be
> welcome.

I recommend against the latest and greatest. Recent computers may use
hardware that Linux does not yet support. Unless you want to take up
supporting such hardware, of course. And Linux should be very usable on
almost any computer less than seven to ten years old.

You might look at others' experiences with hardware that interests you.
https://linux-hardware.org/

--
Does anybody read signatures any more?

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

Stefan Monnier

unread,
Feb 10, 2023, 9:00:06 PM2/10/23
to
> And of course recommendations for a current laptop (preferably
> reasonably priced) that actual experience shows does work well with
> Debian would be welcome.

If your main concerns are a good price and well supported by Debian,
then you're spelling "refurbished, or second hand".
The planet will also thank you for it.


Stefan "writing this on my 2015 desktop because my 2007 laptop
is in the backpack"

davidson

unread,
Feb 10, 2023, 11:40:06 PM2/10/23
to
On Fri, 10 Feb 2023 Default User wrote:
> Hello to all!

Hello.

Full disclosure: I know very little about audio troubleshooting.

> I just got a brand new Dell Inspiron 15 3000 Series 3511 laptop. Came with
> Windows (ugh!) preinstalled.
> My old Dell Inspiron 15 3000 Series 3542 laptop (made in 2014) just died.
> So this one should work, right?
>
> No.
>
> Unfortunately the new 3511 is quite different from the old 3542. It mostly
> "sort of" works.
> But the sound will not work at all on Debian.

How did you come to this conclusion?

Did you do something, take some action, expecting the result to be
audible, but obtained silence instead?

If so, what was that something?

What volume controls have you examined? Have you checked whether they
are muted?

Personally, one of the first things I usually do to get sound to work
(when I notice my media player makes no sound/youtube videos are
silent/etc) is run alsamixer (in package alsa-utils) and unmute all
the playback volume controls.

But I've never used your DE. And again, I'm no expert.

> Not wanting to immediately remove Windows and thus make it
> unreturnable, I have been trying to run it using a Debian 11 "Live"
> install USB thumb drive (Cinnamon desktop). No sound at all.

Throughout this thread, you report the result of "No sound", but never
do you specify what you are doing that results in unexpected silence.

> But . . . it DOES work when running the computer from a USB thumb
> drive of the most recent version of SystemRescue! So, it CAN work
> (somehow) on (some) Linux setups.
>
> Note: System Rescue is now based upon Arch Linux.
>
> Using the Debian 11 USB thumb drive, I was not able to do a complete
> update and upgrade - not enough room on the USB thumb drive. I was
> able to install the pavucontrol package, which I recall has
> sometimes helped in the past. But still no sound.

Still no indication of how you have arrived at this conclusion!

[snipped hardware info]
> I poked around in the Debian wiki about fixing sound problems, but
> to be honest, much of it is over my head.

Me too.

> So . . . any advice on how to get sound to work on this computer?

No matter the problem you want help troubleshooting, make sure your
report prominently specifies not only the unexpected behavior, but
also WHAT YOU DID that resulted in that unexpected behavior.

That will help people help you.

Good luck to you.

--
Ce qui est important est rarement urgent
et ce qui est urgent est rarement important
-- Dwight David Eisenhower

to...@tuxteam.de

unread,
Feb 11, 2023, 2:10:06 AM2/11/23
to
On Fri, Feb 10, 2023 at 08:56:11PM -0500, Stefan Monnier wrote:
> > And of course recommendations for a current laptop (preferably
> > reasonably priced) that actual experience shows does work well with
> > Debian would be welcome.
>
> If your main concerns are a good price and well supported by Debian,
> then you're spelling "refurbished, or second hand".
> The planet will also thank you for it.

Dito. Refurbished Thinkpad X230 here (I prefer small ones: backpack and
that). Souped up to 16G RAM, still on spinning rust (back then, 1T
SSD was prohibitive). Bought end of 2018 (as a replacement of another
X230 which was crushed by a fire protection door: they aren't indestructible,
after all). Looking forward to its next upgrade (SSD).

Paid 400 EUR (incl. RAM), which in the US would be $400. You'll get more
computing for that these days.

New is only worth it if you specifically want some feature you won't
get otherwise.

Cheers
--
t
signature.asc

Anssi Saari

unread,
Feb 11, 2023, 6:10:06 AM2/11/23
to
Default User <hungupo...@gmail.com> writes:

> BTW,
> sudo apt show firmware-sof-signed
> shows firmware-sof-signed as installed for both Debian Live 11.0
> and Debian Live 11.6. :

OK, next step is to run

sudo dmesg | grep -i audio

in a terminal to see if there's any problem loading the driver or
firmware and what other messages there might be. And run aplay -l, does
that list any sound device?

Default User

unread,
Feb 11, 2023, 5:50:07 PM2/11/23
to
Here is the output of sudo dmesg | grep -i audio:

[    0.160240] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    7.598040] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    7.673391] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=1 (0x2c/0x0/0x0/0x0/0x0) type:speaker
[    7.673393] snd_hda_codec_generic hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    7.673394] snd_hda_codec_generic hdaudioC0D0:    hp_outs=1 (0x24/0x0/0x0/0x0/0x0)
[    7.673395] snd_hda_codec_generic hdaudioC0D0:    mono: mono_out=0x0
[    7.673396] snd_hda_codec_generic hdaudioC0D0:    inputs:
[14777.998904] Modules linked in: ctr ccm nls_ascii nls_cp437 vfat fat ext4 mbcache jbd2 ses enclosure scsi_transport_sas rfcomm cmac algif_hash algif_skcipher af_alg bnep x86_pkg_temp_thermal intel_powerclamp coretemp rtw88_8821ce btusb kvm_intel rtw88_8821c btrtl rtw88_pci btbcm rtw88_core btintel bluetooth kvm mac80211 jitterentropy_rng dell_laptop intel_rapl_msr irqbypass mei_hdcp cfg80211 drbg intel_cstate intel_uncore ansi_cprng dell_wmi dell_smbios ecdh_generic efi_pstore iTCO_wdt pcspkr serio_raw dcdbas rfkill intel_pmc_bxt ecc dell_wmi_descriptor sg libarc4 wmi_bmof joydev iTCO_vendor_support crc16 watchdog ee1004 hid_multitouch snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_sof_xtensa_dsp snd_sof snd_sof_intel_hda snd_hda_codec_hdmi snd_soc_hdac_hda snd_hda_ext_core snd_hda_codec_generic snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_hda_intel snd_intel_dspcfg soundwire_intel soc_button_array int3403_thermal soundwire_generic_allocation

And here is the output of aplay -l:

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: Generic Analog [Generic Analog]
  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 0: PCH [HDA Intel PCH], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 12: HDMI 6 [HDMI 6]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 13: HDMI 7 [HDMI 7]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 14: HDMI 8 [HDMI 8]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 15: HDMI 9 [HDMI 9]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 16: HDMI 10 [HDMI 10]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Not sure if that is any help. I don't know how to interpret that; maybe someone else can see
something informative there.

BTW, the sound DOES work fine using an Ubuntu 22.4.1 (LTS) "live" install disk, in "live" mode.
I *could* run the same two commands previously mentioned, while running the Ubuntu 22.4.1 (LTS) "live" install disk, perhaps to compare the output from the Debian 11.6 "live" session.

I did try using alsamixer, but using F6 to choose "default", which shows both card and chip as "PulseAudio" and then F5 to "show all controls", did nothing. Both the Master and Capture controls were set to 100. Below the Master scale, it showed "OO" (not muted). Below the Capture scale, it did not have a similar "block" to show either "OO" or "MM" (muted).

Using F6 to choose "0 HDA Intel PCH", which shows card as "HDA Intel PCH" and chip as "Cirrus Logic Generic", then F5 to "show all controls", also did nothing. The "PCM" control was set to 100. The "PCM" control scale did not have a "block" to show either "OO" or "MM" (muted). Also visible were entries for "S/PDIF, then "S/PDIF 1", "S/PDIF 2" and so on through "S/PDIF 10" , all of which had a "block" showing "OO", but no "scale". And, when selected with F6, the "HDA Intel PCH" choice showed, after hitting F5, the message "This sound device does not have any capture controls."

I then (again) installed pavucontrol 4.0-2 by:
"sudo apt install pavucontrol".

Then I tried the Pulse Audio Volume Control GUI. No luck.
Under the "Configuration" menu, "Profile" drop-down menu", all "Digital" choices were marked as "unavailable". The three "analog" choices and "off" all produce no sound.

What is this, 2023 or 2003?

Anyway, thanks for the suggestions regarding computer hardware.







Dan Ritter

unread,
Feb 11, 2023, 6:40:06 PM2/11/23
to
Default User wrote:
> [ 0.160240] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
> [ 7.598040] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops
> i915_audio_component_bind_ops [i915])
> [ 7.673391] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic:
> line_outs=1 (0x2c/0x0/0x0/0x0/0x0) type:speaker
> [ 7.673393] snd_hda_codec_generic hdaudioC0D0: speaker_outs=0
> (0x0/0x0/0x0/0x0/0x0)
> [ 7.673394] snd_hda_codec_generic hdaudioC0D0: hp_outs=1
> (0x24/0x0/0x0/0x0/0x0)
> [ 7.673395] snd_hda_codec_generic hdaudioC0D0: mono: mono_out=0x0
> [ 7.673396] snd_hda_codec_generic hdaudioC0D0: inputs:

The kernel is happy with the sound card.

> And here is the output of aplay -l:
>
> **** List of PLAYBACK Hardware Devices ****
> card 0: PCH [HDA Intel PCH], device 0: Generic Analog [Generic Analog]
> 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

ALSA believe that there are two audio systems: a motherboard
audio jack and a video-card HDMI that can play audio that way.

Here's a laptop that I have:

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 2: VT1802 Alt Analog [VT1802
Alt Analog]
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 1: AUDIO [SMSL USB AUDIO], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

You can see that it has a first set of jacks, an alternate set,
an HDMI output, and a USB-attached sound card (DAC).


> I did try using alsamixer, but using F6 to choose "default", which shows
> both card and chip as "PulseAudio" and then F5 to "show all controls", did
> nothing. Both the Master and Capture controls were set to 100. Below the
> Master scale, it showed "OO" (not muted). Below the Capture scale, it did
> not have a similar "block" to show either "OO" or "MM" (muted).

Capture is for the recording side. That's normal.

> Using F6 to choose "0 HDA Intel PCH", which shows card as "HDA Intel PCH"
> and chip as "Cirrus Logic Generic", then F5 to "show all controls", also
> did nothing. The "PCM" control was set to 100. The "PCM" control scale did
> not have a "block" to show either "OO" or "MM" (muted). Also visible were
> entries for "S/PDIF, then "S/PDIF 1", "S/PDIF 2" and so on through "S/PDIF
> 10" , all of which had a "block" showing "OO", but no "scale".

Those are almost certainly on/off controls for the various HDMI
outputs. Do you really have 10 physical HDMI or DisplayPort outputs?

I would say your problems are related to PulseAudio and mixer
controls. Most likely PulseAudio is trying to send sound via one of the
HDMI outputs, or it's otherwise confused about where to send audio.

-dsr-

Max Nikulin

unread,
Feb 11, 2023, 10:10:06 PM2/11/23
to
On 12/02/2023 05:46, Default User wrote:
> [14777.998904] Modules linked in: ctr ccm nls_ascii nls_cp437 vfat fat
> ext4 mbcache jbd2 ses enclosure scsi_transport_sas rfcomm cmac
> algif_hash algif_skcipher af_alg bnep x86_pkg_temp_thermal
> intel_powerclamp coretemp rtw88_8821ce btusb kvm_intel rtw88_8821c btrtl
> rtw88_pci btbcm rtw88_core btintel bluetooth kvm mac80211
> jitterentropy_rng dell_laptop intel_rapl_msr irqbypass mei_hdcp cfg80211
> drbg intel_cstate intel_uncore ansi_cprng dell_wmi dell_smbios
> ecdh_generic efi_pstore iTCO_wdt pcspkr serio_raw dcdbas rfkill
> intel_pmc_bxt ecc dell_wmi_descriptor sg libarc4 wmi_bmof joydev
> iTCO_vendor_support crc16 watchdog ee1004 hid_multitouch snd_sof_pci
> snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common
> snd_sof_xtensa_dsp snd_sof snd_sof_intel_hda snd_hda_codec_hdmi
> snd_soc_hdac_hda snd_hda_ext_core snd_hda_codec_generic
> snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_hda_intel
> snd_intel_dspcfg soundwire_intel soc_button_array int3403_thermal
> soundwire_generic_allocation

I may be wrong, but this line may be a sign of kernel crash causing
arbitrary following failures. I would inspect output of journalctl
around "Modules linked in" lines. Perhaps --boot=-1 (and -2, -3, etc.)
may be added to filter logs for previous boots.

David Wright

unread,
Feb 12, 2023, 12:20:06 AM2/12/23
to
On Sat 11 Feb 2023 at 22:46:17 (+0000), Default User wrote:
> And here is the output of aplay -l:
>
> **** List of PLAYBACK Hardware Devices ****
> card 0: PCH [HDA Intel PCH], device 0: Generic Analog [Generic Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0

This is the device you want to concentrate on if you've got speakers.

> 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

These devices, and the rest, might be useful if you have an HDMI
output that you can connect to, say, a TV.

> I did try using alsamixer, but using F6 to choose "default", which shows
> both card and chip as "PulseAudio" and then F5 to "show all controls", did
> nothing. Both the Master and Capture controls were set to 100. Below the
> Master scale, it showed "OO" (not muted). Below the Capture scale, it did
> not have a similar "block" to show either "OO" or "MM" (muted).

It's a bit difficult to follow this narrative. Useful is to list the
options when you press F6. I don't know anything about pulseaudio except
that it can both a help and a hindrance. Sorry.

> Using F6 to choose "0 HDA Intel PCH", which shows card as "HDA Intel PCH"
> and chip as "Cirrus Logic Generic", then F5 to "show all controls", also

That choice should correspond to:

> card 0: PCH [HDA Intel PCH], device 0: Generic Analog [Generic Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0

above. You want the F3 controls for Playback. Ignore the S/PDIF
controls as that's all digital stuff. You should have Slider controls
for Master, Headphone, Speaker, Mic, possibly PCM, and perhaps more.
Make sure Master and Speaker are turned up and have OO, not MM, at the
bottom. (PCM doesn't matter, and don't worry if there's no Speaker.)

> did nothing. The "PCM" control was set to 100. The "PCM" control scale did
> not have a "block" to show either "OO" or "MM" (muted). Also visible were
> entries for "S/PDIF, then "S/PDIF 1", "S/PDIF 2" and so on through "S/PDIF
> 10" , all of which had a "block" showing "OO", but no "scale". And, when
> selected with F6, the "HDA Intel PCH" choice showed, after hitting F5, the
> message "This sound device does not have any capture controls."

Once you've got those settings, either quit with Escape, or move to a
different VC or window or xterm or whatever, and run (from alsa-utils):

$ speaker-test -D hw:0,0 -c 2

The first zero is the card, and the second is the device. I assume
you've got stereo. (Many things won't work with mono, funnily enough.)
You should get hissing noises from Left and Right speakers alternately.

As I said, it's not easy to follow what you wrote above. If you can't
get a display in alsamixer that has sliders for Master etc, and has
Generic at the top (IOW if everything I've written seems the wrong way
round), then I personally would uninstall pulse* and pavu*, and get
things working with just ALSA. Pulseaudio can play some clever tricks
once you've got things working, but it adds another layer of complexity.
If it adds ten extra fancy controls, then you've got ten extra ways of
losing the audio output.

Cheers,
David.

Anssi Saari

unread,
Feb 12, 2023, 8:00:06 AM2/12/23
to
Default User <hungupo...@gmail.com> writes:

> The dumbed-down make-believe BIOS on the new computer lists the Audio Controller as:
> "Cirrus Logic CS8409".

So it looks like this is the actual sound hardware that's in use, not
the Tiger Lake stuff. A quick search found
https://www.phoronix.com/news/Cirrus-Dolphin-Linux-Audio which says
shows support was added in Linux kernel 5.15.

Not available for Debian 11 except as a backport, which is easily added
to an existing installation, even on USB media. There doesn't seem to be
live images for the upcoming Debian 12 currently.

Default User

unread,
Feb 12, 2023, 10:30:06 AM2/12/23
to


xserver-xorg-video-cirrus_1.5.3-1+b3_amd64.deb for Debian Stable (Bullseye) does seem to be at
deb http://ftp.de.debian.org/debian bullseye main 
but that is not a backport. 

When I look at https://packages.debian.org and search "bullseye-updates" and "bullseye-backports" 
I get this: 

"You have searched for packages that names contain cirrus in suite(s) bullseye-backports, all sections, and all architectures.

Sorry, your search gave no results".


Searching "bookworm" (testing) does show:

xserver-xorg-video-cirrus_1.5.3-1+b5_amd64.deb
but I don't know if I can use that with my Debian 11.6 "live" usb stick.

I hate to sound stupid, but could someone please tell me how to add that to the
Debian 11.6 "live" usb stick? 

I know how to enable the bullseye backports repository in
/etc/apt/sources.list, but then I dont know how to "get to" and use backports; I've never had to do that before.


David Wright

unread,
Feb 12, 2023, 2:40:06 PM2/12/23
to
On Sun 12 Feb 2023 at 10:23:59 (-0500), Default User wrote:
> On Sun, Feb 12, 2023 at 7:58 AM Anssi Saari <a...@sci.fi> wrote:
> > Default User <hungupo...@gmail.com> writes:
> >
> > > The dumbed-down make-believe BIOS on the new computer lists the Audio
> > Controller as:
> > > "Cirrus Logic CS8409".
> >
> > So it looks like this is the actual sound hardware that's in use, not
> > the Tiger Lake stuff. A quick search found
> > https://www.phoronix.com/news/Cirrus-Dolphin-Linux-Audio which says
> > shows support was added in Linux kernel 5.15.
> >
> > Not available for Debian 11 except as a backport, which is easily added
> > to an existing installation, even on USB media. There doesn't seem to be
> > live images for the upcoming Debian 12 currently.
>
> Thanks for the pointer to
> https://www.phoronix.com/news/Cirrus-Dolphin-Linux-Audio.
> <https://www.phoronix.com/news/Cirrus-Dolphin-Linux-Audio>
>
> According to https://packages.debian.org,
>
> xserver-xorg-video-cirrus_1.5.3-1+b3_amd64.deb for Debian Stable (Bullseye)
> does seem to be at
>
> deb http://*ftp.de.debian.org/debian
> <http://ftp.de.debian.org/debian>* bullseye main
>
> but that is not a backport.
>
> When I look at https://packages.debian.org and search
> "bullseye-updates" and "bullseye-backports"
>
> I get this:
>
> "You have searched for packages that names contain cirrus in suite(s)
> bullseye-backports, all sections, and all architectures.
>
> Sorry, your search gave no results".
>
>
> Searching "bookworm" (testing) does show:
>
> xserver-xorg-video-cirrus_1.5.3-1+b5_amd64.deb
>
> but I don't know if I can use that with my Debian 11.6 "live" usb stick.
>
> I hate to sound stupid, but could someone please tell me how to add that to
> the
> Debian 11.6 "live" usb stick?
>
> I know how to enable the bullseye backports repository in
> /etc/apt/sources.list, but then I dont know how to "get to" and use
> backports; I've never had to do that before.

I don't see why the solution to a sound problem should lie with an
xserver. Sound should work without X running at all. That's why
I wrote:

Once you've got those [alsamixer] settings, either quit with Escape,
or move to a different VC or window or xterm or whatever, and run
↑↑↑↑↑↑↑↑↑↑↑↑
$ speaker-test -D hw:0,0 -c 2

IOW you can perform the commands I gave after logging in at the
console, with no DMs, DEs, WMs or anything else.

But you may need a kernel more up-to-date than 5.10: there are
5.18 kernels in bullseye-backports, and these contain:

* HD audio interface patch for Cirrus Logic CS8409 HDA bridge chip

Cheers,
David.

Anssi Saari

unread,
Feb 13, 2023, 7:00:06 AM2/13/23
to
Default User <hungupo...@gmail.com> writes:

> xserver-xorg-video-cirrus_1.5.3-1+b3_amd64.deb for Debian Stable (Bullseye) does seem to be at
> deb http://ftp.de.debian.org/debian bullseye main
> but that is not a backport.

It's also not a Linux kernel and not relevant to your sound HW. Just
some video support for ancient video hardware. I don't think Cirrus
Logic has done video HW since the 90s.

> I hate to sound stupid, but could someone please tell me how to add that to the
> Debian 11.6 "live" usb stick?
>
> I know how to enable the bullseye backports repository in
> /etc/apt/sources.list, but then I dont know how to "get to" and use backports; I've never had to do that before.

Just need to give -t repo option to apt:

apt install -t bullseye-backports linux-image-amd64

Although, I don't think you can install a new kernel in a live system
with apt. Don't know for sure though. That's why I said it'd be easy to
add to an installed system.

I don't know if enabling persistence with the live system would allow
booting with a new kernel, it's been a while since I last played with
anything live. But that too needs some figuring out as I recall.

So, install on a USB thing or resize the Windows partition in your
laptop and install in the newly freed space.

Default User

unread,
Mar 20, 2023, 10:20:06 AM3/20/23
to
The sound now works on this machine running Debian Stable (Bullseye).

The solution was to install was, as suggested, to do:
install Debian Stable Gnome (Ugh!) 10.0
upgrade to Debian Stable 11.6 (linux-image-5.10.0-21-amd64)
apt install -t bullseye-backports linux-image-amd64,
which installed linux-image-5.10.0-21-amd64.

Note:
upgrade to Debian Stable 11.6 (linux-image-5.10.0-21-amd64)
was not sufficient by itself. 

Thanks to all for the help!

Jeffrey Walton

unread,
Mar 20, 2023, 11:00:07 AM3/20/23
to
On Thu, Feb 9, 2023 at 7:55 PM Default User <hungupo...@gmail.com> wrote:
>
> I just got a brand new Dell Inspiron 15 3000 Series 3511 laptop. Came with Windows (ugh!) preinstalled.
> My old Dell Inspiron 15 3000 Series 3542 laptop (made in 2014) just died. So this one should work, right?
>
> No.

Also see https://linux-hardware.org/ . It is a database of supported hardware.

I think it includes the minimum kernel version for support of a
particular chipset, once you drill in.

Jeff

Timothy M Butterworth

unread,
Mar 20, 2023, 11:10:07 AM3/20/23
to
 If you are missing drivers or firmware then I recommend installing Debian 12 Bookworm. You can download the live installer from: https://get.debian.org/images/weekly-live-builds/amd64/iso-hybrid/ Debian 11 is old and does not work with the latest hardware without installing from debian backports which I do not recommend. Debian 12 is already frozen for release testing. I have been running Debian 12 for over a year now and only ran into one problem yesterday. I was having problems installing mariadb-server. I made a work around hack today and got it to install.

Tim

Default User

unread,
Mar 20, 2023, 11:40:06 AM3/20/23
to
1)
My old machine (now torn apart) was listed there.
My new machine does not seem to be listed there. Not surprising, since manufactured in 2023-January.

2)
I did try a fresh install to the old machine of a Bookworm daily build about a month ago. It almost all the way through the non-graphical, expert-mode install, only to hard fail at refusing to install grub.  More than once.

Since I now have a working setup, I think I will just patiently wait  a few months until soon after the official release of Bookworm Stable, then either upgrade or fresh install then.

Jeffrey Walton

unread,
Mar 20, 2023, 12:10:06 PM3/20/23
to
> On Thu, Feb 9, 2023 at 7:55 PM Default User <hungupo...@gmail.com> wrote:
> [...]
> My new machine does not seem to be listed there. Not surprising, since manufactured in 2023-January.

Components used in the machine may be listed.

I got lucky on a HP laptop with an Ice Lake processor
(https://linux-hardware.org/?probe=1686ba2df4). The device ELAN0712:00
(04F3:30FD Mouse) was not listed in the database, and the vendor is
Unknown (https://linux-hardware.org/?device_vendor=Unknown+%2830FD%29&device_type=touchpad),
but it was supported by the kernel.

> I did try a fresh install to the old machine of a Bookworm daily build about a month ago. It almost all the way through the non-graphical, expert-mode install, only to hard fail at refusing to install grub. More than once.

As a test, you might try a Fedora Live ISO. F37 currently provides the
6.1.18-200 kernel. Fedora is about as recent as you can get, short of
compiling your own kernel.

If you find sound works with Fedora 37, then you may need to look for
a distro that provides a 6.x kernel.

Jeff

Timothy M Butterworth

unread,
Mar 20, 2023, 12:50:06 PM3/20/23
to
On Mon, Mar 20, 2023 at 12:07 PM Jeffrey Walton <nolo...@gmail.com> wrote:
> On Thu, Feb 9, 2023 at 7:55 PM Default User <hungupo...@gmail.com> wrote:
> [...]
> My new machine does not seem to be listed there. Not surprising, since manufactured in 2023-January.

Components used in the machine may be listed.

I got lucky on a HP laptop with an Ice Lake processor
(https://linux-hardware.org/?probe=1686ba2df4). The device ELAN0712:00
(04F3:30FD Mouse) was not listed in the database, and the vendor is
Unknown (https://linux-hardware.org/?device_vendor=Unknown+%2830FD%29&device_type=touchpad),
but it was supported by the kernel.

> I did try a fresh install to the old machine of a Bookworm daily build about a month ago. It almost all the way through the non-graphical, expert-mode install, only to hard fail at refusing to install grub.  More than once.

As a test, you might try a Fedora Live ISO. F37 currently provides the
6.1.18-200 kernel. Fedora is about as recent as you can get, short of
compiling your own kernel.

Debian Bookworm has the 6.1.15 kernel currently.
 

If you find sound works with Fedora 37, then you may need to look for
a distro that provides a 6.x kernel.

Jeff

0 new messages