This was raised recently and the root cause was recently discussed during the
submission of the thunderbolt patch series by Mika Westerberg:
https://lkml.org/lkml/2017/5/25/288
It will need to be worked out with the PCIe subsystem maintainers yet.
--
You received this bug notification because y
Mika reproduced this on a a different TBT device too.
(so to be clear; this is not TB16 specific. This is a problem with Thunderbolt
devices + Linux currently)
** Summary changed:
- Dell TB16 USB is not working if connected during boot
+ Thunderbolt devices don't work if connected during boot
Mika has already consulted with the ACPI guys and has an idea, but it's
going to require changes outside of Linux first in ACPICA. So it
shouldn't be a very quick fix.
>There is also another PCI/ACPI related issue that Mario reported where
>we execute _INI() methods before the initial PCI scan on
@Kai Heng:
It should not be machine/chipset specific, but may have some BIOS
component to this due to BIOS sends the hotplug event. If the hotplug
event comes too soon (before enumeration is done) you should see this
behavior.
It's specific to PCIe tunnels of TBT devices. You won't for example
Fwiw you don't need to use those drivers with 4.11 (they're backport
drivers). This will eventually need to be backported to 4.4 too, but it
needs to be accepted upstream first. Upstream developers had some feedback
that will need to be addressed and it resubmitted first.
On Tue, Jun 13, 2017, 11:
v4 was resubmitted here (by a different author):
http://www.spinics.net/lists/linux-usb/msg158407.html
--
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/1667750
Title:
xhci_hcd: ERROR Trans
ASMedia submitted v5 here:
http://www.spinics.net/lists/linux-usb/msg158473.html
--
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/1667750
Title:
xhci_hcd: ERROR Transfer event TRB DMA ptr
@Iron Davey I believe that to be a separate issue and unrelated. The
issue reported here specifically is resolved from the patch. If you can
reproduce that problem again, please file a separate issue for it.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
FYI there are two separate issues. The first is the poor performance of
the ethernet on the TB16. That's the original reason this bug was
opened and has been fixed in kernel upgrades.
There is a second issue that a BIOS update causes problems with USB on the TB16
(such as corrupted packets). D
Can you please check if you're on the latest firmware for the 5520? There
was a recent issue on many laptops that was leading to instability
specifically with USB. BIOS has been released for many of them already.
On Fri, Sep 15, 2017, 10:36 Piotr Kołaczkowski
wrote:
> Also, I've read this on ano
>From what I can tell you're on BIOS 1.3.3. Please upgrade to 1.5.0.
It's available both for Ubuntu through fwupd
(https://fwupd.org/lvfs/device/34578c72-11dc-4378-bc7f-b643866f598c) or
can be updated from the F12 post menu by downloading from
support.dell.com
(https://www.dell.com/support/article
@Aron,
It looks like there is just one patch delta in Ubuntu right? Would you
mind to include that to Debian unstable too? Then we can sync zesty and
Debian and Ubuntu shouldn't have to carry anything.
--
You received this bug notification because you are a member of Kernel
Packages, which is
@happyaron
Maybe for now check if running on Ubuntu in lsb_release and only
activate the secure boot and shim stuff in Ubuntu and derivatives? We
do stuff like that in fwupdate right now.
Example:
https://anonscm.debian.org/cgit/uefi/fwupdate.git/tree/debian/rules#n7
--
You received this bug n
Yes it looks like it was refactored as a result of f2f6ecabe, but
following the refactor here is where it would go in a newer kernel.
diff --git a/drivers/net/wireless/ath/ath10k/mac.c
b/drivers/net/wireless/ath/ath10k/mac.c
index 3029f25..8441b33 100644
--- a/drivers/net/wireless/ath/ath10k/mac.
That sounds a little crazy that it can't reproduce in my opinion. When it
"did" reproduce was the brightness at one of the extremes? Eg full high on
shutdown or full low on shutdown?
On Thu, May 25, 2017, 03:21 Kai-Heng Feng
wrote:
> Mario, can you take a look?
>
> A quick summary:
> 1. Boot the
But so we're talking about the slider in the bios that adjusts keyboard
backlight right? That's not tied to display backlight.
On Fri, May 26, 2017, 00:31 Kai-Heng Feng
wrote:
> It can't be reproduced once you changed the brightness via slider in
> BIOS.
>
> It should be reproduceable if the bri
@acelan,
I'm unsure on where this patch first came from and also don't understand the
impact from calling this. I know it was discussed on some forums as a solution
to performance problems. The reason that the vendor hasn't submitted upstream
is they said there was discussion that this should
Public bug reported:
Using the current Ubuntu 17.04 image and selecting the unity8 session,
the XPS 9365 does not automatically switch modes.
When switching to tablet mode, the ACPI driver INT33D6 which is bound to
intel-vbtn will emit a few 0xcc events. When switching to desktop mode,
the same
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
** Changed in: linux (Ubuntu)
Status: Opinion => 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/1678200
https://github.com/torvalds/linux/blob/v4.11-rc5/drivers/platform/x86
/intel-vbtn.c#L38
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
** Changed in: linux-firmware (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1599154
Title:
Missing bluetooth firmware for Broadco
Per https://bugzilla.redhat.com/show_bug.cgi?id=1438969#c5 Broadcom is
not doing wireless cards anymore, this won't be fixed.
** Bug watch added: Red Hat Bugzilla #1438969
https://bugzilla.redhat.com/show_bug.cgi?id=1438969
--
You received this bug notification because you are a member of Ker
This landed in the USB maintainer's tree targeted to be pulled into 4.13-rcX,
and also CC'ed to stable..
https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/commit/?h=for-usb-linus&id=353a73c757c0b856bb95f5e73cf41b10b685258d
Can this be backported to Ubuntu now for the next SRU?
** B
The most important part is that there are no longer kernel oops, tracebacks
or errors when the USB host controller has been configured this way as is
in the patch.
On Tue, Jul 25, 2017, 08:58 Kai-Heng Feng
wrote:
> @imperia
> linux-...@vger.kernel.org
>
> @Bram
> Seems so. Probably there were ot
Public bug reported:
Recently it's been observed that mokutil is unable to make changes to
the various Mok* variables. It complains that "fails to request state"
when trying most actions or similar errors.
The root of these problems is because the variables have been set as immutable
after thi
Alternatively it seems that this might be fixed by moving to mokutil
0.3. Mokutil 0.3 has switched over to use libefivar
(https://github.com/lcp/mokutil/commit/7b49e834284659527c9f7cf554f223748c00564b).
libefivar has handling for immutable variables since version 0.22
(https://github.com/rhinstall
I have a linux task included because this can also be approached from a
kernel perspective (https://lkml.org/lkml/2016/3/22/733).
** Description changed:
Recently it's been observed that mokutil is unable to make changes to
the various Mok* variables. It complains that "fails to request sta
** Changed in: mokutil (Ubuntu)
Status: New => 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/1560764
Title:
"fails to request state" when trying to perform actions
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
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/1560764
Title:
"fails to request state" when trying to perform actions
** Description changed:
- The Broadwell XPS 13 (with touchpad in the more feature rich I2S mode
+ The Broadwell XPS 13 (with touchpad in the more feature rich I2C mode
that's used in OEM Ubuntu images and the default on newer kernels) and
other systems utilize a touchpad conforming to the Micr
I'm currently working on a patch set for Dell rbu and user space tools
that would allow it to work without userspace helper, but it's not yet
ready to go. Can you please wait until that's done to make this change
in Ubuntu?
Dell RBU is still in use.
--
You received this bug notification because
Also isn't there a second kernel module using this functionality still?
I seem to recall Dell RBU and something else both used it.
--
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/1575393
Ti
Public bug reported:
Thunderbolt hotplug is broken on type-c ports. Redhat already submitted
a patch for this that was accepted into upstream ACPICA, but it needs to
be backported into Ubuntu's kernel.
I've verified that the patch works properly using a type-C USB Ethernet
dongle as well as hot-
Public bug reported:
On the Dell TB15 and Dell WD15 docks, analogue audio output is
distorted. This is because of a missing driver quirk on docks.
It has been fixed upstream here.
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8
Ple
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Won't Fix => Confirmed
--
Yo
There aren't logs for this. it's a request to backport a patch.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
--
You
There aren't logs for this. it's a request to backport a patch.
--
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/1577898
Title:
thunderbolt hotplug is broken
Status in linux package in
Here is the patch as submitted to LKML from ACPICA:
http://www.spinics.net/lists/linux-acpi/msg65737.html
--
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/1577898
Title:
thunderbolt hotplu
Why do you have to wait for it to be in mainline to cherry pick? It's
already in rafael's linux-pm acpica-fixes branch with a CC to stable all
applicable.
https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-
pm.git/commit/?h=acpica-
fixes&id=93d68841a23a5779cef6fb9aa0ef32e7c5bd00da
--
You
Hi Joseph,
Yes, thank you. I just tested with a Dell USB Type-C ethernet adapter (PN#
96NP5). In the existing latest Xenial kernel hotplug did not work. Device
wasn't present in lsusb.
After installing that kernel i'm able to hotplug and device is present in
lsusb.
Thanks,
On Fri, May 6, 2016
*** This bug is a duplicate of bug 1577898 ***
https://bugs.launchpad.net/bugs/1577898
** This bug has been marked a duplicate of bug 1577898
thunderbolt hotplug is broken
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
Kyle,
Can you confirm from 'uname -a' what output you have?
That will confirm if you are booted into jsalisbury's kernel.
On Mon, May 9, 2016 at 5:10 PM Kyle Gochenour
wrote:
> I have duplicate bug #1571859 and tried the kernel above from jsalisbury
> and it did not work for me. However there i
You're still booted into the wrong one. His kernel would show a ~lp# in
the uname string. The one your are booted into is probably the one from the
archive that overwrote his on an apt update.
Install his again, don't do apt updates and try to boot into it.
On Mon, May 9, 2016, 18:05 Kyle Goc
Nothing else required from you. It's the Ubuntu kernel team SRU process
from here on out. Joseph might be able to comment better on the expected
timing this will land in a new kernel version.
On Mon, May 9, 2016 at 7:15 PM Kyle Gochenour
wrote:
> That was it, thanks Mario:
> Linux yeti 4.4.0-2
** Attachment added: "udev script"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1579984/+attachment/4659578/+files/dell_dock.sh
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Statu
Changing kernel to confirmed. This is a backport request for when that
patch lands upstream. It's still in discussions.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Based on comments #46-#50, closing out the linux kernel related tasks.
Thanks to Allen's in depth investigation it's clear that this is caused
by Unity.
** Also affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Triaged
Well there are really two problems here as I understand it.
I can however confirm that that the first problem (backlight turns on on it's
own at boot) is fixed by this patch. So that's a definite improvement.
The second problem (backlight turns on on it's own after unlock) I can still
reproduce
Sure. Here you go.
** Attachment added: "usd.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510344/+attachment/4661498/+files/usd.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
There has been some discussion about this.
Dell EMC systems don't require this setting anymore.
Dell client systems are not using it either.
I'm sending a patch to change the behavior of dell_rbu to LKML.
http://www.spinics.net/lists/kernel/msg2257436.html
Please feel free to change the config
Vitor,
Check and see if your BIOS is fully updated. If it's updated all the way
try COLD bolting a few times. It's key to be cold booting not rebooting.
On Fri, Apr 8, 2016, 20:15 Vitor Junior wrote:
> Hello! I'm a tottaly noob and new. I have a XPS 13 9343, and even after
> a LOT of restarts i
v3.9 and v3.10 final kernels both work as tested on an Optiplex 9020.
v3.11.0-12.19 from saucy fails. Black screen upon resume from S3.
--
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/1274
Also 3.11.10.3 fails on the 9020.
However kernels after that (3.12+) appear to work on the 9020, i'm not clear
whether the failure w/ 3.13-rc8 was only observed on laptop HSW hardware.
So at least on the desktop HW it's somewhere between 3.10 and 3.11 that the
failure was introduced and somewhe
paul, Benoît,
If you're happy with I2S, then I guess no worry. But if you want HDA
working make sure you are on BIOS A03.
--
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/1413446
Title:
** Changed in: dell-sputnik
Status: Fix Committed => Fix Released
--
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/1423413
Title:
[XPS 13 9343, Realtek ALC3263, Mic, Internal] No so
*** This bug is a duplicate of bug 1291969 ***
https://bugs.launchpad.net/bugs/1291969
** Package changed: linux-lts-utopic (Ubuntu) => linux (Ubuntu)
** This bug has been marked a duplicate of bug 1291969
No usb on resume from suspend
--
You received this bug notification because you ar
@cribari,
Have you cold booted twice since installing Ubuntu? Cold boot means
shutdown in the OS properly and then bootup to the login screen. Do
this twice.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
@Niels:
Are you updated to BIOS A03? Also it's not reboot, it needs to be
shutdown (as in power off properly from within Ubuntu).
--
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/1413446
T
@Jens,
Have you cold booted twice in a row into Ubuntu?
On Thu, Apr 30, 2015 at 7:35 AM Jens Grehl
wrote:
> My BIOS is updated (A03) but no sound.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1413446
>
> Title:
>
Great! It's the latter. There haven't been any updates to the kernel that
would have caused it to change behavior in 15.04.
On Thu, Apr 30, 2015 at 11:11 AM Niels Egberts
wrote:
> Mario: My sound is working now, awesome!
>
> Not sure if it was an update, of I just always rebooted instead of
>
@Jens,
No, no other changes are needed on the system. If you have the kernel
command line modified in any way, especially acpi_osi options that might
factor in. What kernel are you running? What OS version? Can you share
your dmesg?
The current 3.19 kernel in 15.04 and BIOS A03 has everything
@Jens,
According to your dmesg you aren't running the XPS 13 9343 from 2015,
that's the 9333 from 2014. So this is a separate issue you are having. I
would recommend you contact ProSupport for your issue so they can debug
further.
On Thu, Apr 30, 2015 at 3:05 PM Jens Grehl
wrote:
> @Mario
>
>
@Marc,
It's not a matter of reboots. It needs to be COLD boot. Shutdown
Windows. Boot Ubuntu. Shutdown Ubuntu. Boot Ubuntu.
On Thu, Apr 30, 2015 at 5:31 PM Marc wrote:
> Hi,
>
> mutliple reboot doesn't work for me (i'm dual booting ubuntu 15.04
> original kernel 3.19 and w8.1).
>
> There is
*** This bug is a duplicate of bug 1424676 ***
https://bugs.launchpad.net/bugs/1424676
** This bug has been marked a duplicate of bug 1424676
bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed
to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (f
*** This bug is a duplicate of bug 1424676 ***
https://bugs.launchpad.net/bugs/1424676
** This bug has been marked a duplicate of bug 1424676
bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed
to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (f
*** This bug is a duplicate of bug 1424676 ***
https://bugs.launchpad.net/bugs/1424676
** This bug has been marked a duplicate of bug 1424676
bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed
to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (f
*** This bug is a duplicate of bug 1424676 ***
https://bugs.launchpad.net/bugs/1424676
** This bug has been marked a duplicate of bug 1424676
bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed
to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (f
** Changed in: bcmwl (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1238217
Title:
bcmwl 6.30.223.141+bdcom-0ubuntu1 causes wpa_supplicant to
Based on posts at that community forum, it sounds like this should be
fixed in 3.16. Affected users can try to install linux-generic-lts-
utopic on 14.04 to see if it resolves the issue.
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
** Changed in: dell-sputnik
Status: New =>
Can someone please validate that 3.16 does fix it though? If not, there
are some other workarounds mentioned:
hda-verb /dev/snd/hwC1D0 0x0c SET_AMP_GAIN_MUTE 0x5180
hda-verb /dev/snd/hwC1D0 0x0c SET_AMP_GAIN_MUTE 0x6180
--
You received this bug notification because you are a member of Kernel
Pa
Seth Forshee from Canonical has proposed a patch to LKML to fix this
behavior.
http://lkml.kernel.org/r/1424454311-70750-1-git-send-email-
seth.fors...@canonical.com
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification b
It's been merged upstream. Canonical, can you pull this in for vivid?
https://github.com/torvalds/linux/commit/6d00f37e49d95e640a3937a4a1ae07dbe92a10cb
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The following two patches will resolve this issue:
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?h=for-next&id=e1e62b98ebddc3234f3259019d3236f66fc667f8
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?h=for-next&id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec
** Changed in: dell-sputnik
Status: Confirmed => 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/1416601
Title:
touchpad does not respond to tap-to-clicks in I2C mode
@all:
This was caused by a BIOS error in BIOS A01 that put the sound in an undefined
mode that wasn't really I2S and wasn't really HDA. This has been fixed by BIOS
A02 ( or later ).
There was an _REV patch that was proposed but not merged upstream. If
that (or something similar to it) does get
@Alessio, just some updates.
4.0-rc3 still doesn't have everything needed for this.
https://github.com/torvalds/linux/commit/2cc3f2347022969f00a429951ce489d35a9b4ea8
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-March/088724.html
are a start, but there are more pieces missing too.
--
Sorry i'm really consumed with other stuff right now too.
That sounds reasonable to me.
On 03/11/2015 05:48 AM, Alberto Milone wrote:
> Sorry, I've been busy with other work.
>
> @Mario: any ideas about this?
>
--
You received this bug notification because you are a member of Kernel
Packages, w
Rene, it shouldn't be your fault. Even with that collection of patches
microphone automatic switching won't work. There's still more to be
done.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
No audio still with kernel that was linked above (3.19rc5). The
behavior in dmesg output does change a bit though.
$ dmesg -t | egrep "(audio|snd|INT3438)"
dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
snd_hda_intel :00:03.0: enabling device ( -> 0002)
sst-acpi INT3438
Yes, it's a Realtek ALC3263. The real problem may be that it's trying to
use rt286 codec driver which doesn't actually have support for the ALC3263.
ALC3263 runs in dual mode HDA or I2S similar to rt286 though. When _OSI
test for "Windows 2013" returns TRUE the codec will be put into I2S mode on
Yes, nothing on 3.18
Originally I didn't test any of the stable releases for 3.18, it was the
standard 3.18, I believe the hash assigned to the tag 'v3.18'.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-vivid/
It would make sense to me if it was broken somewhere in between v3.18
and v3.18.
I didn't do a proper bisect, but I have a variety of mainline kernels
from the mainline PPA I tried.
v3.16 works properly
v3.17 some rc's are using ps2 mode due to some i2c failure, others work properly
v3.18 works properly
v3.19-rc1 fails
v3.19-rc5 fails
v3.19-rc6 fails
Whenever someone does a p
** Description changed:
Dell systems with Type-C ports support a feature called "MAC address" pass
through.
This feature allows systems to set a persistent system MAC address to be used
with the TB15, WD15 and Type-C ethernet adapter.
More information is available here:
http://www.del
Upstream hasn't flat out rejected this patch, but they also haven't been
openly accepting the patch.
As this is for enabling docks to properly work (as intended by OEM) in Ubuntu
can this be carried as Ubuntu SAUCE? The latest version of the patch and
discussion about it is available here:
http
David Miller applied this. Could it please be pulled into Ubuntu as
sauce now?
http://patchwork.ozlabs.org/patch/647157/
--
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/1579984
Title:
De
This is upstream now too.
https://github.com/torvalds/linux/commit/34ee32c9a5696247be405bb0c21f3d1fc6cb5729
--
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/1579984
Title:
Dell dock MAC Ad
This is actually a kernel bug where the PWM isn't saved. It affects the
specific display type in this machine. It's been fixed upstream
already, and was brought into Ubuntu 16.04 (See SRU
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625932).
The Precision 5510 however ships with Ubuntu
** Tags added: kernel-bug-exists-upstream
** 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/1645505
Title:
Screen doesn
Hi,
I verified the kernel in xenial works properly for hotplugging the TB15.
Linux test-Precision-5510 4.4.0-23-generic #41-Ubuntu SMP Mon May 16
23:04:25 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Does there really need to be a validation done on every other OS too or
this gets dropped from earlie
Does this need to be verified on trusty or it will be dropped? The fix
has been validated in the other releases and went to -stable.
--
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/1577905
I've adjusted the description for the alternate approach in doing this
entirely in the kernel. I've submitted a patch to LKML for this here.
https://patchwork.kernel.org/patch/9148319/
** No longer affects: network-manager (Ubuntu)
** No longer affects: systemd (Ubuntu)
** Description changed:
In trying to confirm bug 1619756 I encountered this using an earlier version of
4.4.0-*.
I can confirm that 4.4.0-41-generic #61 fixes this bug for NVMe on my system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1626894
Title:
nvme drive probe failure
Status in linu
I can confirm that 4.4.0-41-generic #61 provides these interfaces
properly.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Looks good to me:
$ dmesg | grep "Linux version\|r8152"
[0.00] Linux version 4.4.0-36-generic (buildd@lcy01-01) (gcc version
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #55-Ubuntu SMP Thu Aug 11
18:01:55 UTC 2016 (Ubuntu 4.4.0-36.55-generic 4.4.16)
[5.702293] usbcore: registered
Public bug reported:
Can you please backport these commits into xenial to allow manipulate
the DP aux registers of relevant devices in userspace?
https://github.com/torvalds/linux/commit/e94cb37b34eb8a88fe847438dba55c3f18bf024a
https://github.com/torvalds/linux/commit/36230cb5668c2633bee4ec87b589
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
Can you please backport these commits into xenial to allow manipulate
- the DP aux registers of relevant devices in userspace?
+ the DPCD registers of relevant devices in userspace?
https://github
*** This bug is a duplicate of bug 602071 ***
https://bugs.launchpad.net/bugs/602071
** This bug has been marked a duplicate of bug 602071
[0a5c:5801] Broadcom fingerprint reader not working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
To check if the symptoms are actually identical to bug 1413446, there are a few
ways to go about it debugging further.
The easiest thing you can do is to grab kernel 4.2 (rc5 or later) which
includes this commit:
https://github.com/torvalds/linux/commit/ea7d521569a70418aa9f6309a1d1916709818b62
** Also affects: linux-firmware (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this
101 - 200 of 624 matches
Mail list logo
