[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2019-01-08 Thread Stephan Coertzen
Issue has returned with Kernel 4.15 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1609211 Title: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2018-02-28 Thread Ricardo Ramírez
I uploaded this video showing how to fix the problem: https://www.youtube.com/watch?v=Se1NDgPhteg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1609211 Title:

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2018-02-28 Thread Ricardo Ramírez
1. In terminal, enter the command "alsamixer". 2. An ASCI UI will open, use the right arrow key to find the item: "HP/speaker Auto Detect". it will say "Off" next to it. 3. Press M and the "Off" tag will disappear. 4. Re-plug your headphones. Enjoy! -- You received this bug notification

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2017-05-05 Thread Sagar B Hathwar
After making the required settings in alsamixer, do `sudo alsactl store 0`. This will make your settings persistent on reboot. By the way, this bug is fixed by one of the 4.4 kernels itself in 16.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2017-05-05 Thread Dmitry
and update: I was able to make earphone working by starting alsamixer and setting `HP/Speaker` to `off`, and `HP/Speaker Auto Detect` to `on`. However the change does not survive a reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2017-05-05 Thread Dmitry
The bug persists for me (Ubuntu 17.04, kernel 4.10.0-20-generic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1609211 Title: [Alienware 17 R3, Creative CA0132,

Re: [Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2017-01-26 Thread jetbent
The sound works now but the microphone slot doesn't for me. On Thu, Jan 26, 2017 at 9:10 PM, Arnulf Hansen <1609...@bugs.launchpad.net> wrote: > Updated to Ubuntu 16.10 x64 and the issue remains the same > > -- > You received this bug notification because you are subscribed to the bug > report.

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2017-01-26 Thread Arnulf Hansen
Updated to Ubuntu 16.10 x64 and the issue remains the same -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1609211 Title: [Alienware 17 R3, Creative CA0132, Headphone

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2017-01-09 Thread Sagar B Hathwar
Just updates to kernel 4.9.2 and headphones work perfectly fine now. Bug fixed! Not sure if any older kernel version itself fixed the bug. If anyone can check that out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

Re: [Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2016-10-22 Thread jetbent
I believe it has to do with the proprietary drivers that come with the Alienware. It seems that Soundblaster does not have good linux compatibility since it's not one of their priorities. On Thu, Oct 20, 2016 at 6:24 PM, adin wrote: > Updated to Ubuntu 16.10, and the problem

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2016-10-20 Thread adin
Updated to Ubuntu 16.10, and the problem persists. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1609211 Title: [Alienware 17 R3, Creative CA0132, Headphone Out,

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2016-10-03 Thread Sagar B Hathwar
Any idea on what is causing this problem and when we might expect a fix for this? Since I have the necessary hardware to help in fixing this, I could try and experiment it out with any patches to the alsa drivers Thank you -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2016-10-03 Thread Sagar B Hathwar
Any idea on what is causing this problem and when we might expect a fix for this? Since I have the necessary hardware to help in fixing this, I could try and experiment it out with any patches to the alsa drivers Thank you -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2016-08-30 Thread Alberto Salvia Novella
** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1609211 Title: [Alienware 17 R3, Creative

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2016-08-29 Thread jetbent
Using hdajackretest to override Orange Headphone, Front side Pin ID: 0x10 with "Headphone" causes ubuntu to recognize when headphones are plugged in (correctly per original pin designation IAW windows), however, no sound output results. By default, ubuntu/alsa thinks that the original microphone

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2016-08-28 Thread jetbent
I also tried to modify /etc/modprobe.d/alsa-base.conf with: options snd-hda-intel model=alienware and options snd-hda-intel model=dell-eq but neither worked. These options also have a tendency to kill the sound card leaving dummy-output only. From what I can tell, the issue is sound blaster

[Touch-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2016-08-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.