Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #187172 > unrolled thread

no sound on Lenovo Ideapad 110

Back to article view | Back to linux.debian.user

Contents

  no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-25 10:00 +0200
    Re: no sound on Lenovo Ideapad 110 "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-09-25 15:20 +0200
      Re: no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-25 20:20 +0200
        Re: no sound on Lenovo Ideapad 110 "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-09-25 22:30 +0200
          Re: no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-26 12:40 +0200
            Re: no sound on Lenovo Ideapad 110 "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-09-26 14:20 +0200
            Re: no sound on Lenovo Ideapad 110 Jimmy Johnson <field.engineer@gmail.com> - 2017-09-28 10:00 +0200
              Re: no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-28 10:40 +0200
                Re: no sound on Lenovo Ideapad 110 Curt <curty@free.fr> - 2017-09-28 14:00 +0200
                  Re: no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-28 14:50 +0200
                    Re: no sound on Lenovo Ideapad 110 Curt <curty@free.fr> - 2017-09-28 16:40 +0200
                      Re: no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-28 17:40 +0200
                    Re: no sound on Lenovo Ideapad 110 Patrick Bartek <nemommxiv@gmail.com> - 2017-09-28 19:20 +0200
                      Re: no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-28 20:40 +0200
                        Re: no sound on Lenovo Ideapad 110 Jimmy Johnson <field.engineer@gmail.com> - 2017-09-28 21:50 +0200
                          Re: no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-28 22:30 +0200
                            Re: no sound on Lenovo Ideapad 110 Jimmy Johnson <field.engineer@gmail.com> - 2017-09-29 10:50 +0200
                        Re: no sound on Lenovo Ideapad 110 Curt <curty@free.fr> - 2017-09-28 22:00 +0200
                          Re: no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-28 22:30 +0200
                        Re: no sound on Lenovo Ideapad 110 Patrick Bartek <nemommxiv@gmail.com> - 2017-09-28 23:00 +0200
                          Re: no sound on Lenovo Ideapad 110 "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-09-28 23:20 +0200
                            Re: no sound on Lenovo Ideapad 110 Patrick Bartek <nemommxiv@gmail.com> - 2017-09-29 02:30 +0200
                            Re: [solved] no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-29 09:30 +0200
                              Re: [solved] no sound on Lenovo Ideapad 110 "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-09-29 09:40 +0200
                                Re: [solved] no sound on Lenovo Ideapad 110 Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-29 14:10 +0200
                          Re: no sound on Lenovo Ideapad 110 Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-09-29 07:10 +0200
          Re: no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-26 18:10 +0200
            Re: no sound on Lenovo Ideapad 110 "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-09-26 19:10 +0200
        Re: no sound on Lenovo Ideapad 110 davidson <davidson@freevolt.org> - 2017-09-28 15:00 +0200
          Re: no sound on Lenovo Ideapad 110 Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-28 17:30 +0200

Page 1 of 2  [1] 2  Next page →

#187172 — no sound on Lenovo Ideapad 110

hi,
On my Lenovo Ideapad 110 laptop, with Debian Stretch, I have
sound neither with speaker nor headphone.
Here are some details:
- with WIndows 10, no problem, which means that the hardware is OK.
- with the Debian 9.1 kde live dvd, the sound works with the headphone,
   but not with the speaker.
- with the installed Debian 9.1 kde, no sound at all, with any program
   (including speaker-test)

I must add that pulseaudio runs correctly with the live dvd, but fails
on the installed system, although I copied the /etc/pulse content from
the dvd live.

    E: [pulseaudio] module.c: Failed to load module "module-alsa-sink" (argument: "device=default"): initialization failed.
    E: [pulseaudio] main.c: Module load failed.
    E: [pulseaudio] main.c: Failed to initialize daemon.


Googling gave me nothing useful. Has anybody an idea?

I find it abnormal that such a fundamental thing as sound is so
difficult to configure under Linux. It's that kind of problems which
makes difficult to convince people to abandon Windows for Linux.

best regards,
-- 
Pierre Frenkiel

[toc] | [next] | [standalone]

#187178

[Multipart message — attachments visible in raw view] — view raw

Probably some ALSA module or codec firmware is missing.
Look for errors in syslog and provide some information about what sound
codec is onboard your laptop mobo:
    $ sudo journalctl -b

Use "/" key to search for a string. Ex:
    /audio
    /hda
    /sound

On 25.09.2017 12:58, Pierre Frenkiel wrote:
> hi,
> On my Lenovo Ideapad 110 laptop, with Debian Stretch, I have
> sound neither with speaker nor headphone.
> Here are some details:
> - with WIndows 10, no problem, which means that the hardware is OK.
> - with the Debian 9.1 kde live dvd, the sound works with the headphone,
>   but not with the speaker.
> - with the installed Debian 9.1 kde, no sound at all, with any program
>   (including speaker-test)
>
> I must add that pulseaudio runs correctly with the live dvd, but fails
> on the installed system, although I copied the /etc/pulse content from
> the dvd live.
>
>    E: [pulseaudio] module.c: Failed to load module "module-alsa-sink"
> (argument: "device=default"): initialization failed.
>    E: [pulseaudio] main.c: Module load failed.
>    E: [pulseaudio] main.c: Failed to initialize daemon.
>
>
> Googling gave me nothing useful. Has anybody an idea?
>
> I find it abnormal that such a fundamental thing as sound is so
> difficult to configure under Linux. It's that kind of problems which
> makes difficult to convince people to abandon Windows for Linux.
>
> best regards,

[toc] | [prev] | [next] | [standalone]

#187196

[Multipart message — attachments visible in raw view] — view raw

On Mon, 25 Sep 2017, Alexander V. Makartsev wrote:

> Probably some ALSA module or codec firmware is missing.
> Look for errors in syslog and provide some information about what sound
> codec is onboard your laptop mobo:
>     $ sudo journalctl -b
>
> Use "/" key to search for a string. Ex:
>     /audio
>     /hda
>     /sound

the / is used in a lot of cases (editors, web browser,...)
I don't understand what search key you are talking of.

    nothing new in syslog
    here are the outputs for the journalctl calls
    Do you see there something interesting?
    For me, it's not very useful.

==================================================================
==> journalctl -b | grep -i audio

Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC233: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:    inputs:
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:      Internal Mic=0x1b
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:      Mic=0x19
Sep 24 14:21:11 pfr3 kernel: input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input13
Sep 24 14:21:11 pfr3 kernel: input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:14.2/sound/card1/input14
Sep 24 16:27:09 pfr3 pulseaudio[2698]: Failed to load module "module-alsa-sink" (argument: "device=default"): initialization failed.
Sep 24 16:27:09 pfr3 pulseaudio[2698]: Module load failed.
Sep 24 16:27:09 pfr3 pulseaudio[2698]: Failed to initialize daemon.
Sep 24 16:27:36 pfr3 pulseaudio[2733]: Failed to load module "module-alsa-sink" (argument: "device=default"): initialization failed.

==================================================================
==> journalctl -b | grep -i hda

Sep 24 14:21:11 pfr3 kernel: snd_hda_intel 0000:00:01.1: Force to non-snoop mode
Sep 24 14:21:11 pfr3 kernel: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/sound/card0/input11
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC233: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:    inputs:
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:      Internal Mic=0x1b
Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:      Mic=0x19
Sep 24 14:21:11 pfr3 kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2/sound/card1/input12
Sep 24 21:38:18 pfr3 kernel: snd_hda_intel 0000:00:01.1: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Sep 24 14:21:11 pfr3 kernel: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/sound/card0/input11
Sep 24 14:21:11 pfr3 kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2/sound/card1/input12
Sep 24 14:21:11 pfr3 kernel: input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input13
Sep 24 14:21:11 pfr3 kernel: input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:14.2/sound/card1/input14

==================================================================
==> journalctl -b | grep -i sound

Sep 24 14:21:11 pfr3 systemd[1]: Reached target Sound Card.
Sep 24 14:21:12 pfr3 systemd[1]: Starting Save/Restore Sound Card State...
Sep 24 14:21:13 pfr3 systemd[1]: Started Save/Restore Sound Card State.

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#187212

Yes. It looks like sound card was detected and initialized, but Pulse
Audio was unable to set it as "default" automatically.
Have you tried to list and use available cards from alsa perspective
(your device names may be different)?
    $ aplay -l | grep ALC
        card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog
[ALC887-VD Analog]
    $ aplay -L | grep CARD
        sysdefault:CARD=PCH
        front:CARD=PCH,DEV=0
        surround21:CARD=PCH,DEV=0
        ...
    $ speaker-test -D front -t wav -c 2
If speaker-test works, but without actual sound from speakers, be sure
to check if sound channels unmuted:
    $ alsamixer


On 25.09.2017 23:11, Pierre Frenkiel wrote:
>    nothing new in syslog
>    here are the outputs for the journalctl calls
>    Do you see there something interesting?
>    For me, it's not very useful.
>
> ==================================================================
> ==> journalctl -b | grep -i audio
>
> Sep 24 14:21:11 pfr3 kernel: snd_hda_codec_realtek hdaudioC1D0:
> autoconfig for ALC233: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker

[toc] | [prev] | [next] | [standalone]

#187233

On Tue, 26 Sep 2017, Alexander V. Makartsev wrote:

> Yes. It looks like sound card was detected and initialized, but Pulse
> Audio was unable to set it as "default" automatically.
> Have you tried to list and use available cards from alsa perspective
> (your device names may be different)?

   I'm not sure that this is the problem, as the sound works correctly
   with the headphone, even with  speaker-test !
   I already tried with the different devices given by "aplay -L",
   and of course checked the output levels with alsamixer.
   for example: "speaker-test -Dsysdefault:Generic -c 2 -t sine"
   but never got any sound through the speaker.
   I remind you that the hardware is not involved, as the sound works
   with Windows 10.

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#187241

[Multipart message — attachments visible in raw view] — view raw

Alsa seems to function correctly, so next you should assign available
profile for your sound card with PulseAudio.
You should be able to choose between speakers\headphones outputs.
Install "pavucontrol" package or\and "kmix" package since you using kde.
Go to Configuration tab in pavucontrol and set profile for your sound card.

Console utility for that is "pactl". This will give you index number of
your sound card.
    $ pactl list cards
This will set active profile for pulse audio on my system (You can use
"Tab" key to get help for the next list of parameters):
    $ pactl set-card-profile 1 output:analog-surround-51+input:analog-stereo
Pulse audio should remember that selection, between system restarts.
If audio sink wasn't created after that, restart pulseaudio if necessary:
    $ pulseaudio -k
    $ pulseaudio --start

To check sound from pulseaudio:
    $ speaker-test -D pulse -c 2 -t wav


On 26.09.2017 15:37, Pierre Frenkiel wrote:
> On Tue, 26 Sep 2017, Alexander V. Makartsev wrote:
>
>> Yes. It looks like sound card was detected and initialized, but Pulse
>> Audio was unable to set it as "default" automatically.
>> Have you tried to list and use available cards from alsa perspective
>> (your device names may be different)?
>
>   I'm not sure that this is the problem, as the sound works correctly
>   with the headphone, even with  speaker-test !
>   I already tried with the different devices given by "aplay -L",
>   and of course checked the output levels with alsamixer.
>   for example: "speaker-test -Dsysdefault:Generic -c 2 -t sine"
>   but never got any sound through the speaker.
>   I remind you that the hardware is not involved, as the sound works
>   with Windows 10.
>
> best regards,

[toc] | [prev] | [next] | [standalone]

#187346

On 09/26/2017 03:37 AM, Pierre Frenkiel wrote:
> On Tue, 26 Sep 2017, Alexander V. Makartsev wrote:
> 
>> Yes. It looks like sound card was detected and initialized, but Pulse
>> Audio was unable to set it as "default" automatically.
>> Have you tried to list and use available cards from alsa perspective
>> (your device names may be different)?
> 
>    I'm not sure that this is the problem, as the sound works correctly
>    with the headphone, even with  speaker-test !
>    I already tried with the different devices given by "aplay -L",
>    and of course checked the output levels with alsamixer.
>    for example: "speaker-test -Dsysdefault:Generic -c 2 -t sine"
>    but never got any sound through the speaker.
>    I remind you that the hardware is not involved, as the sound works
>    with Windows 10.
> 
> best regards,


I've seen that problem before, the mini plug was not pushed in all the 
way and there was no sound.  I hope your problem is that simple.
-- 
Jimmy Johnson

Debian Stretch - KDE Plasma 5.8.6 - AMD A8-7600 - EXT4 at sda6
Registered Linux User #380263

[toc] | [prev] | [next] | [standalone]

#187349

[Multipart message — attachments visible in raw view] — view raw

On Thu, 28 Sep 2017, Jimmy Johnson wrote:

> I've seen that problem before, the mini plug was not pushed in all the way and 
> there was no sound.  I hope your problem is that simple.

   Hi Jimmy,
   it seems you missed these lines:
                                                 the sound works correctly
       with the headphone, even with  speaker-test !

    So, the problem is not with the plug, as generally it must unplugged
    to get the sound through the speaker.

best regards,
-- 
Pierre Frenkiel 
>

[toc] | [prev] | [next] | [standalone]

#187354

On 2017-09-28, Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote:
>
>     So, the problem is not with the plug, as generally it must unplugged
>     to get the sound through the speaker.
>

I suppose it is possible that the sensing circuitry or switch (?) in the
headphone jack is faulty or failing so that when you pull the headphone plug
out of the jack socket the audio signal isn't being switched to the speakers,
the plug's absence failing to be detected (or its presence continuing to
be).

I wonder if this hypothesis could be tested in software; it seems you can
do something like

 cat /proc/asound/card1/codec#0 | grep Pin-ctls
(if your sound card is card1 as mine is)

and look for values of "Pin-ctls=in" or "Pin-ctls=out" 

I obtain these values:


  Pin-ctls: 0x40: OUT
  Pin-ctls: 0x20: IN
  Pin-ctls: 0x20: IN
  Pin-ctls: 0x24: IN VREF_80
  Pin-ctls: 0x24: IN VREF_80
  Pin-ctls: 0x20: IN
  Pin-ctls: 0xc0: OUT HP VREF_HIZ
  Pin-ctls: 0x20: IN
  Pin-ctls: 0x20: IN
  Pin-ctls: 0x40: OUT

But they remain the same whether I have my headphones plugged in or not
(I have no speakers).

Anyhow, this is probably a very wild goose chase and a waste of our
precious time.

-- 
"A simpering Bambi narcissist and a thieving, fanatical Albanian dwarf."
Christopher Hitchens, commenting shortly after the nearly concurrent deaths 
of Lady Diana and Mother Theresa.

[toc] | [prev] | [next] | [standalone]

#187357

On Thu, 28 Sep 2017, Curt wrote:

> On 2017-09-28, Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote:
>>
>>     So, the problem is not with the plug, as generally it must unplugged
>>     to get the sound through the speaker.
>>
>
> I suppose it is possible that the sensing circuitry or switch (?) in the
> headphone jack is faulty or failing so that when you pull the headphone plug
> out of the jack socket the audio signal isn't being switched to the speakers,
> the plug's absence failing to be detected (or its presence continuing to
> be).

    I said, in a previous post, that on Windows, the sound works for the
    speaker and the headphone...

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#187365

On 2017-09-28, Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote:
> On Thu, 28 Sep 2017, Curt wrote:
>
>> On 2017-09-28, Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote:
>>>
>>>     So, the problem is not with the plug, as generally it must unplugged
>>>     to get the sound through the speaker.
>>>
>>
>> I suppose it is possible that the sensing circuitry or switch (?) in the
>> headphone jack is faulty or failing so that when you pull the headphone plug
>> out of the jack socket the audio signal isn't being switched to the speakers,
>> the plug's absence failing to be detected (or its presence continuing to
>> be).
>
>     I said, in a previous post, that on Windows, the sound works for the
>     speaker and the headphone...

I missed that detail. Dual boot, is that it? Turn the volume way up in
Windows and use the function keys to make sure the speakers are turned
on and functioning before booting into Debian. Turn off hybrid shutdown,
or fast startup, or whatever it's called, as I've heard that can leave
hardware components in a hideous state. I'm not sure what you've tried
so far and I'm not going back to reread the entire thread so good luck.

> best regards,


-- 
"A simpering Bambi narcissist and a thieving, fanatical Albanian dwarf."
Christopher Hitchens, commenting shortly after the nearly concurrent deaths 
of Lady Diana and Mother Theresa.

[toc] | [prev] | [next] | [standalone]

#187374

On Thu, 28 Sep 2017, Curt wrote:

> I missed that detail. Dual boot, is that it?
   yes

>                                              Turn the volume way up in
> Windows and use the function keys to make sure the speakers are turned
> on and functioning before booting into Debian.

   After booting on Windows, I could hear the sound from the speakers, so
   they were actually turned on.
   After that, I did a normal reboot, and booted to Debian...and no sound
   on speakers. The most surprising is that even speaker-test gives a
   sound through the headphone.

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#187380

On Thu, 28 Sep 2017 14:48:27 +0200 (CEST) Pierre Frenkiel
<pierre.frenkiel@gmail.com> wrote:

> On Thu, 28 Sep 2017, Curt wrote:
> 
> > On 2017-09-28, Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote:
> >>
> >>     So, the problem is not with the plug, as generally it must
> >> unplugged to get the sound through the speaker.
> >>
> >
> > I suppose it is possible that the sensing circuitry or switch (?)
> > in the headphone jack is faulty or failing so that when you pull
> > the headphone plug out of the jack socket the audio signal isn't
> > being switched to the speakers, the plug's absence failing to be
> > detected (or its presence continuing to be).
> 
>     I said, in a previous post, that on Windows, the sound works for
> the speaker and the headphone...

I don't know if this will help, but I read a post somewhere (don't
remember where) of someone who had troubles with the Ideapad 110S
-- sound, touchpad, suspend, etc. -- after replacing Windows 10 with
Stretch.  Installing a newer kernel from Stretch-Backports rectified
those issues along with non-free firmware in the Stretch Repos and/or
proprietary drivers.

I'm interested in any solutions you discover.  I'm looking at the 110S
as a light, compact "travel" notebook.

B

[toc] | [prev] | [next] | [standalone]

#187384

On Thu, 28 Sep 2017, Patrick Bartek wrote:

> I don't know if this will help, but I read a post somewhere (don't
> remember where) of someone who had troubles with the Ideapad 110S
> -- sound, touchpad, suspend, etc. -- after replacing Windows 10 with
> Stretch.  Installing a newer kernel from Stretch-Backports rectified
> those issues along with non-free firmware in the Stretch Repos and/or
> proprietary drivers.
  I have already the latest kernel version, but I would be interested
   having some details about these non-free firmware and drivers.
   Up to now, googling gave me nothing about that.

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#187387

On 09/28/2017 11:38 AM, Pierre Frenkiel wrote:
> On Thu, 28 Sep 2017, Patrick Bartek wrote:
> 
>> I don't know if this will help, but I read a post somewhere (don't
>> remember where) of someone who had troubles with the Ideapad 110S
>> -- sound, touchpad, suspend, etc. -- after replacing Windows 10 with
>> Stretch.  Installing a newer kernel from Stretch-Backports rectified
>> those issues along with non-free firmware in the Stretch Repos and/or
>> proprietary drivers.
>   I have already the latest kernel version, but I would be interested
>    having some details about these non-free firmware and drivers.
>    Up to now, googling gave me nothing about that.
> 
> best regards,

Installing package firmware-linux in Stretch will pull in all the 
firmware, free, non-free, etc.
-- 
Jimmy Johnson

Ubuntu 16.04 LTS - KDE Plasma 4.8.5 -AMD A8-7600 - EXT4 at sda5
Registered Linux User #380263

[toc] | [prev] | [next] | [standalone]

#187390

On Thu, 28 Sep 2017, Jimmy Johnson wrote:

> Installing package firmware-linux in Stretch will pull in all the firmware, 
> free, non-free, etc.

    they are already installed, but only firmware-linux-free is not empty,
    and I don't see something useful (for me) in it.

[toc] | [prev] | [next] | [standalone]

#187404

On 09/28/2017 01:25 PM, Pierre Frenkiel wrote:
> On Thu, 28 Sep 2017, Jimmy Johnson wrote:
> 
>> Installing package firmware-linux in Stretch will pull in all the 
>> firmware, free, non-free, etc.
> 
>     they are already installed, but only firmware-linux-free is not empty,
>     and I don't see something useful (for me) in it.

And you have the microcode for your machine installed too?

I'm only a User, but I have a combo that always works for me on all my 
machines and all my Debian/Ubuntu systems and that is PulseAudio and 
Gstreamer + Gstreamer and Phonon, I install pavucontrol too and I remove 
all VLC and it just works, I use Mplayer + Smplayer for playback of 
audio and video, system sounds work, internet audio works and it just 
works with HDMI too.  Sorry if if its not useful.
-- 
Jimmy Johnson

Ubuntu 16.04 LTS - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda5
Registered Linux User #380263

[toc] | [prev] | [next] | [standalone]

#187388

On 2017-09-28, Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote:
> On Thu, 28 Sep 2017, Patrick Bartek wrote:
>
>> I don't know if this will help, but I read a post somewhere (don't
>> remember where) of someone who had troubles with the Ideapad 110S
>> -- sound, touchpad, suspend, etc. -- after replacing Windows 10 with
>> Stretch.  Installing a newer kernel from Stretch-Backports rectified
>> those issues along with non-free firmware in the Stretch Repos and/or
>> proprietary drivers.
>   I have already the latest kernel version, but I would be interested
>    having some details about these non-free firmware and drivers.
>    Up to now, googling gave me nothing about that.
>
> best regards,


Realtek offers a proprietary driver for linux (last updated 2014).

Looks like you have to compile it.

http://airbornesurfer.com/2015/04/how-to-install-realtek-hd-audio-driver-in-linux/

-- 
"A simpering Bambi narcissist and a thieving, fanatical Albanian dwarf."
Christopher Hitchens, commenting shortly after the nearly concurrent deaths 
of Lady Diana and Mother Theresa.

[toc] | [prev] | [next] | [standalone]

#187389

On Thu, 28 Sep 2017, Curt wrote:

> Realtek offers a proprietary driver for linux (last updated 2014).
>
> Looks like you have to compile it.
>
> http://airbornesurfer.com/2015/04/how-to-install-realtek-hd-audio-driver-in-linux/

thanks Curt for this information. I'll look at it to-morrow

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#187391

On Thu, 28 Sep 2017 20:38:13 +0200 (CEST) Pierre Frenkiel
<pierre.frenkiel@gmail.com> wrote:

> On Thu, 28 Sep 2017, Patrick Bartek wrote:
> 
> > I don't know if this will help, but I read a post somewhere (don't
> > remember where) of someone who had troubles with the Ideapad 110S
> > -- sound, touchpad, suspend, etc. -- after replacing Windows 10 with
> > Stretch.  Installing a newer kernel from Stretch-Backports rectified
> > those issues along with non-free firmware in the Stretch Repos
> > and/or proprietary drivers.
>   I have already the latest kernel version, but I would be interested
>    having some details about these non-free firmware and drivers.
>    Up to now, googling gave me nothing about that.

4.9?  Or 4.11 or 4.12?

B

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web