I booted the 4.17rc1 kernel.
In order to see output I connected an old TV to the DVI output, and that
output was successfully detected (through an DVI-HDMI adapter, if that
matters).
The output of /sys/class/drm/card0-HDMI-A-1 in this case:
dpms: Off
enabled: disabled
modes: (empty)
I'm not sure if you asked for the contents of these files from a working
or non-working kernel, but I'll take the working kernel since that's
obviously a lot easier.
The monitor, Dell U2415, is connected via its input source "HDMI (MHL)
2". The monitor name "DELL U2415" shows up in the edid
I don't think it is the same bug. I have a card with HDMI and DVI
connectors (XFX RX 460). The HDMI connector is connected to the monitor,
the DVI connector is unplugged.
// David
On 2018-04-30 17:40, Harry Wentland wrote:
> Replied on the ticket.
>
> If this is about non-functioning LVDS or
Kernel 4.15.0-15-generic #16~lp1761751v2: Boots normally
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
Status in linux package in
The test kernel (4.15.0-15-generic #16~lp1761751) boots normally.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
Status in linux
Yeah, so I doubt it's a whitespace fix in the rxrpc driver. However, a
diff between the configs on v415-rc2 and v415-rc3 has lots of
differences, the most interesting being this one:
$ diff -u config-4.15.0-041500rc2-generic config-4.15.0-041500rc3-generic
/* ... snip ... */
@@ -5675,9 +5677,9
Kernel 3d7682af228fd78dc46bc: Black screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
Status in linux package in Ubuntu:
In
Kernel 5fc62f6a139a7b06b027bf442cd4205619506f59: Black screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
Status in linux package
Kernel 282ef4729195c8503f7101d574acfb5e7c8a8209: Black screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
Status in linux package
Linux version 4.15.0-041500rc1-generic (jsalisbury@kathleen) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #201804181224: Black screen
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761751
There's nothing graphics related here:
$ git log v4.15-rc2..a0da456bbf95d2a9294799bb --oneline
a0da456 net: phy-micrel: check return code in flp center function
c7799c0 tipc: call tipc_rcv() only if bearer is up in tipc_udp_recv()
cfac7f8 tcp/dccp: block bh before arming time_wait timer
b484d8a
Kernel a0da456bbf95d2a9294799bb05c61bfb24736bb7: Black screen.
This is starting to feel a bit fishy but maybe git knows what it's
doing. :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Kernel af57b7fffaf74ff337e479abb19026d72065673b: Black screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
Status in linux package
Kernel 2391f0b4808e3d5af348324d69f5f45c56a26836: Black screen.
Kernel 4.17-rc1: Black screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD
> I built the first test kernel, up to the following commit:
You mean the second test kernel, I presume?
Kernel 6a5e05a47b6cb8e59bfad351444322b1e4012326: Black screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Kernel 4.15rc2+78d9b048446c3c0a83313444fb706f8f3bccdae7: Black screen.
Note: I installed the linux-image-...-generic deb only as the header
ones seemed to require libssl1.1...?
Anyway, I did some research on my own as well.
First, I had a look at the commits between 4.15rc2 and 4.15rc3. The
4.15.0-041500rc2-generic - Boots normally
4.15.0-041500rc3-generic - Black screen
4.15.0-041500rc4-generic - Not tested
So something between rc2 and rc3 it is then...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ - Boots
normally
v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ - Boots
normally
v4.15-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc5/ - Black
screen
v4.15-rc9:
Ok, so I found this message when trying to boot a faulty kernel without
workaround, if it helps:
[1.797127] [drm] Cannot find any crtc or sizes
[1.799000] [drm] Initialized amdgpu 3.23.0 20150101 for :23:00.0 on
minor 0
--
You received this bug notification because you are a member
** Description changed:
I've been running 16.04 + hwe kernel 4.15 for a while now and recently
I'm now having a black screen instead. I've also tried an 18.04 daily
live USB stick, which has the same issue.
It probably started during an upgrade this week or last week. As a start
I'm
** Description changed:
I've been running 16.04 + hwe kernel 4.15 for a while now and recently
I'm now having a black screen instead. I've also tried an 18.04 daily
live USB stick, which has the same issue.
It probably started during an upgrade this week or last week. As a start
I'm
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+attachment/5104013/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I've been running 16.04 + hwe kernel 4.15 for a while now and recently
I'm now having a black screen instead. I've also tried an 18.04 daily
live USB stick, which has the same issue.
It probably started during an upgrade this week or last week. As a start
I'm blaming the
** Description changed:
+ Note: Current workaround is to add pci=noaer to your kernel command
+ line:
+
+ 1) edit /etc/default/grub and and add pci=noaer to the line starting with
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
+ GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
+ 2) run
Btw, I reported mine upstream long ago and got response from upstream
that "I've thought about this problem a bit, but realistically I don't
have time to do the fix I'd like to do /.../ Anybody else who is
interested should feel free to take a crack at it."
See
Out of curiousity, do all of you have the combination of Skylake +
RTL8723BE, and second, do you experience (as I do) that wifi doesn't
work very well (often loses connections etc)?
...as the errors seem to indicate some kind of physical error between
the Skylake/Sunrise Point host controller and
Hi and thanks for spotting! My BIOS has been updated now.
1) Dmidecode now shows:
01.06.00
02/25/2016
2) The hotkey still does not work, but now there is a message in dmesg
when you press it:
dell_wmi: Unknown key with scancode 0xe008 pressed
or
dell_wmi: Unknown key 0xe008 pressed
The
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => David Henningsson (diwic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On 2016-02-25 09:29, Takashi Iwai wrote:
> On Thu, 25 Feb 2016 09:13:21 +0100,
> David Henningsson wrote:
>>
>> On one of the machines we enable, we found that the actual speaker volume
>> did not always correspond to the volume set in alsamixer. This patch
>> fixes
: https://bugs.launchpad.net/bugs/1549660
Co-Authored-By: Kailang <kail...@realtek.com>
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
sound/pci/hda/patch_realtek.c | 23 +--
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/s
/bugs/1549660
Co-Authored-By: Kailang <kail...@realtek.com>
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
sound/pci/hda/patch_realtek.c | 23 +--
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/sound/pci/hda/patch_realtek.c b/s
Public bug reported:
On one of the machines we enable, we found that the actual speaker
volume did not always correspond to the volume set in alsamixer.
This bug is for tracking purposes; please do not triage.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects:
Verified with mainline kernel 4.5.0-040500rc5-generic, problem present
there as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548844
Title:
Inspiron 13-7359: rfkill button has
Public bug reported:
Nothing happens when the button to enable/disable rfkill (a k a
"airplane mode" or "wifi/bluetooth disable") is pressed.
Most other buttons seems to work according to evtest although some of
them has no effect (and the "switch video mode" button generates Alt-P).
Some of the
bugs.launchpad.net/bugs/1540511
(cherry picked from commit 73e7d63efb4d774883a338997943bfa59e127085)
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
drivers/hid/hid-multitouch.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/drivers/hid/hid-multitouch.c b/drivers/
https://bugzilla.kernel.org/show_bug.cgi?id=108481
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1540511
Title:
Ok, I've now built and tested a kernel with 4.4 + the below commit and
can confirm that this commit fixes the touchpad issue for me.
commit 8a7fa6187191f005d4b6d29913de6e128cc778e2
Author: Benjamin Tissoires
Date: Tue Dec 1 12:41:38 2015 +0100
HID:
it bisect start
# new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1
git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d
# old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
git bisect old afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc
# old:
Tested kernels so far:
4.3.0-7 ubuntu - good (touchpad working)
4.5.0-040500rc3 - good (touchpad working)
4.4.0-4 ubuntu - bad (touchpad not working)
4.4.1-040401 - bad (touchpad not working)
4.5.0-040500rc1 - good (touchpad working)
Looks like a temporary regression in 4.4 - maybe we can bisect
A few more commits...
# new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1
git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d
# old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
git bisect old afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc
# old:
I'm working on it, here's the result so far:
$ git bisect log
git bisect start
# new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1
git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d
# old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
git bisect old
Public bug reported:
When running a dist-upgrade, I received the following warning:
Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section table?
Public bug reported:
When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
working. When booting 4.3 kernels, the touchpad is works.
Expected: When I move a finger touching the touchpad, an arrow should move
accordingly on the screen.
What happens instead: nothing.
I've tried
** Description changed:
When running a dist-upgrade, I received the following warning:
Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section
/db/?f=3088f82a0cf977855f92af9db8ad406c04f71efa
BugLink: https://bugs.launchpad.net/bugs/1529624
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
sound/pci/hda/patch_realtek.c | 8
1 file changed, 8 insertions(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/pat
** Bug watch removed: Linux Kernel Bug Tracker #109691
http://bugzilla.kernel.org/show_bug.cgi?id=109691
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected
Hi,
Indeed booting with pci=noaer (as suggested in the other bug) works
around this issue as well. I'll use that for the time being.
Thanks for working on it!
// David
On 2015-12-29 16:58, Bjorn Helgaas wrote:
> On Fri, Dec 18, 2015 at 11:30:33AM +0100, David Henningsson wrote:
>>
Public bug reported:
This is bug is for tracking purposes only, please do not triage.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Changed
These laptops support both headphone, headset and mic modes
for the 3.5mm jack.
Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1526330
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
sound/pci/hda/patch_realtek.c | 17 -
1 file c
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1526330
Title:
Fix mic-in mode for a few Dell laptops
Status in
The spam rate is 150 lines per second. With ~80 characters per line,
that's about 50 MB per hour. As a very rough measure.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
> Otherwise, the modules are not installed with a message saying that
they are included since 3.99 kernel (not sure of the version as I didn't
save the results)
Oops, a problem with the DKMS packaging. Thanks for the heads up, will
be fixed in the next build.
--
You received this bug
On the internal mic of the Packard Bell DOTS, one channel
has an inverted signal. Add a quirk to fix this up.
Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1523232
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
sound/pci/hda/patch_realtek.c |
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1523232
Title:
Packard Bell DOTS inverted internal microphone
I've tried upgrading BIOS to 1.2.0 (latest version on Dell website) and
also with the v4.4-rc3-wily kernel. The dmesg is still spammed with the
same error.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
My dmesg gets completely spammed with the following messages appearing
over and over again. It stops after one s3 cycle; it only happens after
reboot.
[ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
[ 5315.987249] pcieport :00:1c.0: can't
Well, if you have an external mic plugged in, that overrides the
internal mic and uses the external one instead.
Double-check that you don't have an external mic plugged in, and if you
still see a problem, please attach an alsa-info (
https://wiki.ubuntu.com/Audio/AlsaInfo ) with the DKMS
You should get notifications in this bug when that's about to happen.
I'd say everything from 2 weeks to 2 months depending on SRU cycle
timing.
Meanwhile using the DKMS packages (
https://www.ubuntu.com/Audio/UpgradingAlsa/DKMS ) should fix your issue.
--
You received this bug notification
** Changed in: alsa-driver (Ubuntu)
Status: New => In Progress
** Changed in: alsa-driver (Ubuntu)
Assignee: (unassigned) => David Henningsson (diwic)
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1504778
Title:
Lenovo G50-80 - Inverted Internal microphone
Hi Tim and thanks for taking care of it so far - for consistency, would
you mind adding two more:
commit d5f362a7b977bdfaf8a955f3d604a29267bd5464
Author: David Henningsson <david.hennings...@canonical.com>
Date: Thu Sep 3 11:51:35 2015 +0200
drm/i915: Add locks around audio componen
>From a private bug:
I have verified kernel 3.19.0-29.31~14.04.1 on , this issue
is fixed. The HDMI audio device is available and works fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
> On Skylake platform I encounter shutdown hang without HDMI plug issue
> the system stop at "init: wait-for-state (plymouth-shutdown lightdm)"
> Log attached
Thanks for testing. Can you confirm that this is an actual regression
with the patch set, i e, that it does not happen with the
On 2015-09-01 21:38, Brad Figg wrote:
> On Tue, Sep 01, 2015 at 12:04:05PM +0200, David Henningsson wrote:
>> This is a patch set fixing a long-standing bug for some Haswell, Broadwell
>> and most Skylake machines.
>>
>> When the HDA audio controller is in D3,
*** This bug is a duplicate of bug 1490895 ***
https://bugs.launchpad.net/bugs/1490895
** This bug has been marked a duplicate of bug 1490895
Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3
--
You received this bug notification because you are a member of Kernel
Packages,
*** This bug is a duplicate of bug 1490895 ***
https://bugs.launchpad.net/bugs/1490895
** This bug is no longer a duplicate of bug 1383997
HDMI audio hot-plug detection does not work well with laptop running on
battery with 14.04
** This bug has been marked a duplicate of bug 1490895
*** This bug is a duplicate of bug 1490895 ***
https://bugs.launchpad.net/bugs/1490895
** This bug is no longer a duplicate of bug 1383997
HDMI audio hot-plug detection does not work well with laptop running on
battery with 14.04
** This bug has been marked a duplicate of bug 1490895
without any testing. I could use Timo's assistance here so we
coordinate testing this with other i915 changes for the next SRU cycle.
And I could use Timo's help to make sure this applies equally to i915
and i915_bpo.
BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895
David
This callback will be called by the i915 driver to notify the hda
driver that its HDMI information needs to be refreshed, i e,
that audio output is now available (or unavailable) - usually as a
result of a monitor being plugged in (or unplugged).
Signed-off-by: David Henningsson <david.henni
When the audio codec is enabled or disabled, notify the audio driver.
This will enable the audio driver to get the notification at all times
(even when audio is in different powersave states).
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
drivers/gpu/drm/i915/i915
This lets the interested codec be notified when an i915 pin/ELD
event happens.
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
sound/pci/hda/hda_i915.c | 10 ++
sound/pci/hda/hda_intel.h | 5 +
2 files changed, 15 insertions(+)
diff --git a/sound/p
we get two callbacks from the same event,
one from the unsol event and one from the i915 driver, but this is
not harmful and can be optimised away in a later patch.
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
sound/pci/hda/patch_hdmi.c | 21 -
.
By having the i915 driver call directly into the hda driver, the HDA
driver is always notified that an HDMI hotplug event has happened.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Changed in: linux (Ubuntu)
Status
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1487345
Title:
Noises from CX20722 codec after reboot
Status in
is reinitialized again, such as in
BIOS setup or GRUB menus).
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Description changed:
This bug is meant
://bugs.launchpad.net/bugs/1487345
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_conexant.c | 23 ++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/sound/pci/hda/patch_conexant.c b/sound/pci/hda/patch_conexant.c
index f788a91..ca03c40
On 2015-08-21 10:26, Takashi Iwai wrote:
On Fri, 21 Aug 2015 09:42:35 +0200,
David Henningsson wrote:
On shutdown/reboot of CX20722, first shut down all EAPDs, then
shut down the afg node to D3.
Failure to do so can lead to spurious noises from the internal speaker
directly after reboot
Woodrow, did we ever get a quirk in for this one or not?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1477900
Title:
Headset mic support for a Dell desktop machine
Status in HWE
Public bug reported:
This bug is used for tracking only, please do not triage.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Changed in: linux
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1476987
Title:
Headset mic support for a Dell machine
Status in
Without this patch, the headset mic will not work on this machine.
BugLink: https://bugs.launchpad.net/bugs/1476987
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/sound/pci/hda
** Changed in: hwe-next
Status: New = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1454975
Title:
AMD Radeon HD 8570 / R7 240/340 OEM] [1002:6611] No DP
Comes from upstream stable, does not need verification.
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On 2015-05-28 09:18, Takashi Iwai wrote:
At Thu, 28 May 2015 09:15:46 +0200,
David Henningsson wrote:
When headphone mic boost is above zero, some 10 - 20 second delay
might occur before the headphone mic is operational.
Therefore disable the headphone mic boost control (recording gain
-in only mode.)
BugLink: https://bugs.launchpad.net/bugs/1454235
Suggested-by: Kailang Yang kail...@realtek.com
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/sound/pci/hda/patch_realtek.c b
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1454235
Title:
Fix headset jack on two Dell machines
Status in
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1454656
Title:
Add support for Conexant codecs CX20721, CX20722,
This patch adds support for Conexant HD Audio codecs
CX20721, CX20722, CX20723 and CX20724.
Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1454656
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_conexant.c | 12
1 file
Public bug reported:
These codecs can be trivially supported by adding the relevant id:s to
the right tables.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status
JFTR, it seems that upstream has agreed to revert the _REV change for
4.1, and develop a quirk system for 4.2 that would enable us to stay on
HDA mode for as many kernels as we like:
http://mailman.alsa-project.org/pipermail/alsa-
devel/2015-May/091958.html
--
You received this bug notification
Public bug reported:
This bug is for tracking purposes. Please do not triage.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Changed in: linux
ALC662 does not need any special verbs to change the jack functionality,
and enables mic in through the headphone jack mode by changing the
direction of the headphone pin node.
BugLink: https://bugs.launchpad.net/bugs/1454235
Signed-off-by: David Henningsson david.hennings...@canonical.com
This enables the headset microphone on Dell Inspiron 5548,
or at least some variants of it.
Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1452175
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 7 +++
1 file changed
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1452175
Title:
Add headset mic some variants of Dell Inspiron
This enables the headset microphone on Dell Inspiron 5548,
or at least some variants of it.
Cc: sta...@kernel.org
BugLink: https://bugs.launchpad.net/bugs/1452175
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 7 +++
1 file changed, 7
Public bug reported:
This bug is used for tracking purposes, please do not triage.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Changed
** Also affects: alsa-lib (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: pulseaudio (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in
Public bug reported:
This bug is used for tracking, please do not triage.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
** Changed
, it certainly isn't controlled by setting an
amp on 0x0b, so disable beep functionality (at least for now).
Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446517
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1446517
Title:
num_steps = 0 error on ALC256
Status in linux
1 - 100 of 294 matches
Mail list logo