** Changed in: linux (Ubuntu Disco)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu Eoan)
Status: Incomplete => Triaged
** Also affects: linux via
https://bugs.freedesktop.org/show_bug.cgi?id=110604
Importance: Unknown
Status: Unknown
--
You received this b
Definitely support uefi capsule update.
2.10 is posted here:
https://fwupd.org/lvfs/device/com.dell.uefi5ffdbc0d.firmware
Are you installed in uefi mode? If so, capsule update might be turned
off in bios setup.
If you are installed in legacy mode you'll have to manually download exe
and place in
You won't be able to update the BIOS from Ubuntu (this time or in the
future) in legacy mode.
Unfortunately it's not possible to convert a stock Ubuntu install to
UEFI mode. So you'll need to switch modes and reinstall.
So it probably comes down to a question of whether that's important to you in
It's not in support.dell.com either for Windows as I can tell. Latest version
is 40.
https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverid=c25p2&oscode=wt64a&productcode=xps-13-9380-laptop
--
You received this bug notification because you are a member of Kernel
Packages, wh
*** This bug is a duplicate of bug 1793965 ***
https://bugs.launchpad.net/bugs/1793965
** This bug has been marked a duplicate of bug 1793965
Firmware update daemon resets displays connected to Dell TB16 dock soon
after every first login
--
You received this bug notification because you
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1822633
Title:
Pairing failure with BLE 4.0
Status in bluez pa
** Project changed: snappy-hwe-snaps => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1822633
Title:
Pairing failure with BLE 4.0
Status in bluez package in Ubuntu:
Ne
With most machines they have a security level set in BIOS. The default
security level means you need to authorize the thunderbolt device using
bolt or thunderbolt-tools, did you do that?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thu
This is a bug in the amdgpu kernel module.
When trying to access the DP aux channel it is causing system hangs.
At least in upstream fwupd there is a recently committed workaround:
https://github.com/hughsie/fwupd/commit/57816a7907e5f56c2136af31a4f1ae5186d87565
For now you can do the following:
1
This is definitely a kernel bug, but it's exaggerated by userspace.
So whether it should be worked around in userspace or fixed in the kernel space
is debatable.
For now, I believe you can employ that workaround to keep your system
stable, but I would ask the following.
1) Can you please follow
FWIW a few other messages pop up to me in the above logs as suspicious
to the described symptoms, especially with keyboard working in
cryptsetup.
Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client
bug: timer event25 debounce: offset negative (-111ms)
Mar 31 10:34:45 tapl
So this issue needs to be reported upstream to AMD @FDO.
https://bugs.freedesktop.org
Having the very simple replicator should be good to include it too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
That's interesting to me. Yes the EC will emulate an PS2 mouse until the
OS brings up the I2C controller. I would think you can accomplish a
similar result by blacklisting psmouse potentially.
Is this discussion in IRC or a mailing list?
--
You received this bug notification because you are a me
dptfxtract should be upgraded to 1.4.2 at the same time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1838590
Title:
Update thermald to 1.9 release
Status in dptfxtract package in
Public bug reported:
The thermald 1.9 release was just tagged, and has potential to help
quite a bit with platform performance on some newer platforms when run
with kernel 5.3. It would be nice to update eoan to this new release.
> - The major change in this version is the active power limits adj
It's carried in multiverse for that reason.
On Mon, Aug 5, 2019, 05:20 Colin Ian King <1838...@bugs.launchpad.net>
wrote:
> @Srinivas, dptfxtract is a binary, so it can't be packaged in
> debian/ubuntu. Is there source?
>
> --
> You received this bug notification because you are subscribed to th
Reviewing the package in your PPA I do have a few comments that should
be addressed.
1) It looks like the standards version has been downgraded. If being modified
at all it should be bumped up to match standards version in Eoan. This should
also be mentioned in debian/changelog
2) VCS-Git and
Can you check if you have intel-vbtn or intel-hid driver loaded? I would
think intel-vbtn.
Whichever it is a good experiment with the above comment is to blacklist
the module, rebuild initramfs and reboot. See if this helps.
If it does then it's likely a situation of this driver starting in wrong
Looking at the dmesg from #30, it's actually intel-hid. Here is how to
blacklist: https://askubuntu.com/questions/110341/how-to-blacklist-
kernel-modules
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
@frio:
S3? Did you manually switch /sys/power/mem_sleep from s2idle to deep?
By default it should be going into suspend to idle (s2idle) not 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/
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1813537
Title:
Wifi + bluetooth adapters are gone after sleep/wake
Statu
I have to agree with Paul. This is a separate issue.
Issues like this often have a firmware component (such as the BIOS ACPI
primitives or touchpad firmware). Even if the messages are the same I
wouldn't categorize the error messages from another identically with the
problems from this specific
XPS 9575 isn't (currently) available for purchase with Ubuntu. So yes,
it's below the radar for something that is typically tested, tracked, or
fixed from a BIOS or validation team perspective.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
5530 2-in-1 also isn't available for purchase with Ubuntu, so same boat.
It's (confusingly) a very different system than 5530 which /is/
available with Ubuntu.
** Summary changed:
- [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530] laptop keyboard &
touchpad not working at gdm screen af
> Is there any comment on why this issue only happened on the config
from customer, but not on our configs.
I would recommend to compare CPU stepping, perhaps a regression only
present in later CPU stepping after pre-production samples.
--
You received this bug notification because you are a mem
Alternatively this commit I suspect should help:
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=1ffdb51f28e8ec6be0a2b812c1765b5cf5c44a8f
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/1760106
Title:
Enable configuring resume offset via sysfs
St
Public bug reported:
In 4.17 a new attribute is introduced to configure the hibernation
resume offset. Since Ubuntu enables a swapfile by default this attribute
is important to be able to make hibernation work "out of the box".
The patch in the kernel is here:
https://git.kernel.org/pub/scm/linux
** 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/1760106
Title:
Enable configuring resume offset via sysfs
Status in l
** Also affects: klibc (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
In 4.17 a new attribute is introduced to configure the hibernation
resume offset. Since Ubuntu enables a swapfile by default this attribute
is important to be able to make hibernation work "o
** Summary changed:
- Enable configuring resume offset via sysfs
+ FFe: Enable configuring resume offset via sysfs
--
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/1760106
Title:
FFe: Ena
@Andy,
The systemd changes are approved, just waiting for CI to pass and
they'll be merged.
--
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/1760106
Title:
FFe: Enable configuring resume
regarding klibc upstream is MIA for a long time. There are patches that
have been posted before mine, but no activity since:
commit 4d19974d7020488f63651244e1f9f51727c3f66c
Author: H. Peter Anvin
Date: Mon Feb 1 13:26:01 2016 -0800
[klibc] fwrite: fix typo in comment
Fix typo in comm
> Did I get the interpretation of these rules correct?
At a glance it looks like what you thought, but dig a little deeper.
1. The rule calls tbtacl add
(https://github.com/intel/thunderbolt-software-user-space/blob/master/tbtacl/tbtacl.rules.in#L2)
2. tbtacl add calls authorize:
https://github.c
@xnox in order to coordinate the systemd upload in case you have
anything in flight, here's a debdiff:
** Patch added: "backported fix from upstream"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1760106/+attachment/5110809/+files/systemd-offsets.debdiff
--
You received this bug not
@Kai Heng,
I believe this should help:
Can you please apply
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/media/usb/uvc?h=v4.17-rc1&id=e96cdc9a0aa2fcaa276a76e8ffa86fc10a1d3d99
to a test kernel?
Or alternatively can someone affected please test 4.17-rc1 (it's
i
@Walter Garcia-Fontes,
Sorry, I missed that comment of yours. Thank you for confirming that
4.17-rc1 didn't adequately resolve the issue.
I believe what this is coming down to is that there are still aspects
from UVC 1.5 that are missing in the kernel then.
@Kai Heng,
There is no plugin curren
@Kat,
Can you please confirm the particular Ubuntu kernel that you are still
encountering the need to run this command? As I understood this patch
(that effectively does what that command does) is backported into all
the latest Ubuntu kernels, so if it's still happening that is important
informat
All,
The patch has been submitted here:
https://lkml.org/lkml/2018/5/8/1117
--
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/1763748
Title:
Integrated Webcam Realtek Integrated_Webcam_HD
@Kai Heng,
Can you share a test kernel with that patch for folks in this thread
affected?
--
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/1763748
Title:
Integrated Webcam Realtek Integra
@Josef,
Glad to hear that confirmation. It may be useful to respond with a Tested-by
to the patch upstream.
https://patchwork.kernel.org/patch/10388043/
@Stefano
No need to upgrade again. You can stay at 1.0 and it's functionally
just fine with Ubuntu.
Thanks,
--
You received this bug noti
Only if you have userspace that uses other 1.5 features, which doesn't
exist today in Linux. The patch and fw 1.0 should be functionally
equivalent for Linux.
On Fri, May 11, 2018, 17:01 alkemyst <1763...@bugs.launchpad.net> wrote:
> @Mario
> Well, 1.0 already works without any patch. It'just dow
The first 2 I have no concerns, but would like to see a tested-by
submitted back to that patch to encourage it to land upstream.
The third patch, there has been a second submission (and will likely be a 3rd
based on feedback).
https://patchwork.kernel.org/patch/10522375/
Conceptually I have no c
Thanks for the response. There is quite a lot going on here.
First off - The XPS 9570 is a CFL system.
The going black in the first place is an artifact what fwupd does to
query the firmware on the MST hubs in the dock. What it does is "wakes"
the MST hubs by putting them into a higher power mo
>With :
>$ sudo sh -c 'echo mem > /sys/power/state'
>$ sudo sh -c 'echo deep > /sys/power/mem_sleep'
>the problem disappears.
This is changing how the system goes to sleep in a significant way.
With this, the BIOS turns off all devices except RAM when going to
sleep. With the way that it works by
Can you please test without your adapter plugged in prior to the sleep
cycle? Due to the way suspend to idle works this may cause the PCH to
remain in a higher power state burning a lot more battery.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Package changed: linux-hwe-edge (Ubuntu) => linux (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/1687413
Title:
MST display setup show shifted, flickering picture in second h
There has been a lot of work upstream in the graphics stack around MST, but not
all of it has been merged yet. Would you be able to test with drm-next to see
if the problem is resolved there?
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/current/
If it's resolved there, there will need
** 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/1687413
@macat,
OK thanks for confirming. This is likely an upstream issue then. Can you
please file it here:
https://01.org/linuxgraphics/documentation/how-report-bugs
and leave a link back to this bug?
Thanks,
--
You received this bug notification because you are a member of Kernel
Packages, whic
** Changed in: dell-sputnik
Status: New => 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/1687397
Title:
Kernel freeze when plugging in external monitor via USB-C->DP-Ad
To anyone who has been affected - there is a discussion going on the
kernel mailing lists regarding this issue and it would be helpful if you
can provide an acpidump. You can attach it to this bug (or file a
kernel bugzilla and attach it there).
Desired would be the 1.2.0 firmware (which some peo
Thanks Joe! By chance can you upgrade to current BIOS too and get that
dump again? There is that workaround now (blacklist intel-vbtn) which
you should be able to use now if you have no other problems with current
firmware.
--
You received this bug notification because you are a member of Kerne
Thanks so much!
--
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/1822394
Title:
[Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
laptop keyboard & touchpad not working at
KH: Agree it looks like IOMMU bug, this needs to get raised up to the
Intel IOMMU guys. They are tracking something specific to i915 in ICL
and TGL, but this is not as new.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
In the issue reported upstream it was concluded not to be a fwupd
problem, nor a WD19TB problem. The same issue occurs trying to read the
NVM from the host. So kernel issue TBT FW issue, or HW issue.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received th
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
--
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/1908322
Title:
Dell WD19 upgrade issue
Status in fwupd package in Ubuntu:
In
** Bug watch added: Linux Kernel Bug Tracker #210761
https://bugzilla.kernel.org/show_bug.cgi?id=210761
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=210761
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
I'm marking eoan as fixed, as it has 1.2.10 which contains the
workaround to avoid using synaptics mst on amdgpu devices.
The kernel tasks is still open as this is still a real kernel problem.
** Changed in: fwupd (Ubuntu Eoan)
Status: Triaged => Fix Released
** Changed in: fwupd (Ubuntu
@Dave:
I was glancing at r8152 driver and notice that it has some special handling for
ipv6. Is this issue reproducing only in ipv6 for you?
https://github.com/torvalds/linux/commit/6128d1bb30748d0ff56a63898d14f312126e404c
--
You received this bug notification because you are a member of Kerne
** Bug watch added: Red Hat Bugzilla #1460789
https://bugzilla.redhat.com/show_bug.cgi?id=1460789
** Also affects: linux (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1460789
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
Public bug reported:
Hi,
When 4.15 is brought into Ubuntu bionic I wanted to make sure that a few
configure options were selected to compile as module (as they won't come
by default):
1) Intel WMI thunderbolt driver
2) Dell SMBIOS WMI driver
3) Dell SMBIOS SMM driver
** Affects: linux (Ubuntu)
Not relevant for this bug.
** 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/1734761
Title:
enable new configure option
At the time Colin and I discussed getting thunderbolt-tools into Debian
and then eventually into Ubuntu (& of course main via this MIR) bolt's
GUI wasn't available yet and bolt was still under some pretty heavy
development.
>From a client (general purpose laptop or desktop) system perspective
it's
A few questions:
1)It looks like you did test 4.15 final correct? This happens identically
with both 4.13 and 4.15?
2) Can you please install fwupd from proposed and start fwupd in verbose
mode and share the output?
/use/lib/fwupd/fwupd -v
3) did you try changing thunderbolt security levels aft
Thanks for sharing. It looks like you're on latest BIOS and thunderbolt
controller isn't running in native mode.
Can you also share fwupdmgr get-devices output with a Thunderbolt device
plugged in?
On Tue, Jan 30, 2018, 08:05 Joseph Borg <1745...@bugs.launchpad.net>
wrote:
> Ciao Marino,
>
> Yes
OK so that's an older Thunderbolt NVM. It wouldn't hurt to upgrade to
the latest to see if it helps.
Unfortunately it's not yet on LVFS yet, but if you want to try to build it and
flash it yourself here are the pieces you need:
http://www.dell.com/support/home/us/en/04/drivers/driversdetails?dri
Actually here you go:
https://fwupd.org/downloads/2ab30ba0769a84029af4e055270444f9391c71c8-3H3DP_NVM28.00.cab
See if that helps.
--
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/1745747
Titl
I wouldn't recommend to waste time investigating the lag mentioned in the
past few comments.
Due to the way that Thunderbolt works while enumerating in BIOS assist mode
(also known as legacy mode) I would expect a small lag like that. In native
mode the enumeration is handled by the OS ACPI hotplu
@Joseph,
After you upgrade NVM if you can still reproduct can you please share
more information on which USB-C (non TBT devices) and which TBT devices
you are testing with?
Also for the ones that are not TBT can you please try them in the other
USB-C ports? As Kai Heng mentioned the XPS 9370 doe
@Joseph,
Hmm, OK. So you may already know this but USB and Thunderbolt devices
are handled differently. I would treat these as two distinct separate
issues.
Do you have any TBT devices that are not eGPU? It would be good to know
if the problems are specific to eGPU.
--
You received this bug n
There's a lot of reports of failures when using dongles with that chip.
Some people have had success when switching to HDMI cables with better
shielding.
On Fri, Feb 2, 2018, 01:40 Kai-Heng Feng
wrote:
> @Mario,
>
> The device I mentioned is a USB Type-C to HDMI UHD dongle, it uses a NXP
> PTN50
Logs N/A for this type of bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** Package changed: linux (Ubuntu) => thunderbolt-tools (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thunderbolt-tools in Ubuntu.
Matching subscriptions: Kernel Packages
https://bugs.launchpad.net/bugs/1748157
Title:
[MIR]
Public bug reported:
XPS 9360 (KBL)
I was running a newer kernel on xenial userspace and noticed the
following in syslog:
i915 :00:02.0: Direct firmware load for i915/kbl_dmc_ver1_01.bin failed
with error -2
i915 :00:02.0: Failed to load DMC firmware
[https://01.org/linuxgraphics/downl
btw - Noticed the same error on the 4.4 kernel with i915 BPO.
[1.074319] i915_bpo :00:02.0: Direct firmware load for
i915/kbl_dmc_ver1.bin failed with error -2
[1.074322] i915_bpo :00:02.0: Failed to load DMC firmware
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares],
This is not a hardware failure.
When a proper fix is developed I'd expect it to come in the form of a
patch to XHCI driver to adjust internally how ASMedia host controller
operates.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This particular issue is that TPM updates are being offered even if the
TPM is owned. It's been fixed upstream already
(https://github.com/hughsie/fwupd/commit/736be7440fdee3f5339f3b1dc193f674a6191696
#diff-a60e5446a876ad45a9fd10a068b50816) and that version is available in
bionic-proposed. It has
There was a problem I found a little while back with hooking up dock to
artful where gnome would crash. That was fixed recently, but I haven't seen
anything else either (both wd15 and tb16 with XPS 9350)
On Thu, Oct 19, 2017, 23:15 Kai-Heng Feng
wrote:
> Uh, I meant "I cannot reproduce the issue
Here's more detail, the gnome-shell fix came with this bug:
https://launchpad.net/bugs/1722811
The apparmor problem with 4.14 is described here:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278
So please do share if you're encountering issues after upgrading to that
newer version o
Those 3 patches were backported to 4.13.13.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.13.y&id=dcd2b010f17d64f19ac6a1f7cc77d85faf29196a
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.13.y&id=d055d4161c9354cd5
*** This bug is a duplicate of bug 1717431 ***
https://bugs.launchpad.net/bugs/1717431
Looks like those made it to artful too:
https://bugs.launchpad.net/intel/+bug/1717431
** This bug has been marked a duplicate of bug 1717431
[Bug] Thunderbolt-patches: Fixes the issue regarding the orde
That file is not shipped with standard Ubuntu. Was this an OEM shipped
machine and it came in an oem package? Or was that something you added
yourself?
You can check:
dpkg -S /etc/modprobe.d/blacklist_i2c_hid.conf
On Thu, Dec 14, 2017, 12:55 Kevin Dalley <1737...@bugs.launchpad.net>
wrote:
> And
So for what it's worth looking at adopting libinput would likely improve
your touchpad experience.
You should investigate if you are using that after upgrade. It's the
default with 17.10 fresh install but I don't know what would happen with
upgrade.
PS2 mode doesn't support as many features as I2
It looks like you don't have the associated xorg package installed with it.
https://launchpad.net/ubuntu/+source/xserver-xorg-input-libinput
You should check your Xorg log to see if libinput is active.
Given this initial issue is resolved (touchpad stopped working) I'm going to
close this kernel
That particular commit actually breaks proper s2idle. Because of it S3
should be used instead on 9360.
It was intentionally broken because of some reported regression by one guy
with an nvme SSD of a particular vendor.
Can you please check which SSD you have? Nvme info command on it can be
helpfu
Did you manually set s2idle? That policy shouldn't have been picked unless
you were on 4.14.
On Sat, Dec 16, 2017, 17:55 Jeffrey Bouter <1738...@bugs.launchpad.net>
wrote:
> Kai-Heng,
>
> A cat on /sys/power/mem_sleep already shows:
>
> [s2idle] deep
>
> --
> You received this bug notification be
Thunderbolt NVM isn't on LVFS stable but it's on testing. Either turn on
fwupd LVFS testing remote or install manually from this file:
https://fwupd.org/lvfs/device/dfd51125-338f-56ff-b721-fa3bea8e534e
On Tue, Dec 19, 2017, 02:45 Kai-Heng Feng
wrote:
> I can't reproduce the issue on the XPS 936
Information isn't available on what has changed between NVM releases from
Intel. It generally improves performance and resolves issues with the ICM
stack. Those could lead to for example the controller not going to sleep
when it should.
On Wed, Dec 20, 2017, 11:26 Jeffrey Bouter <1738...@bugs.laun
FWIW this bug was fixed upstream already.
https://github.com/torvalds/linux/commit/d9018976cdb6eefc62a7ba79a405f6c9661b08a7
https://bugzilla.kernel.org/show_bug.cgi?id=195951
** Bug watch added: Linux Kernel Bug Tracker #195951
https://bugzilla.kernel.org/show_bug.cgi?id=195951
** Also affec
Since you're on artful can you please use fwupdmgr to check the version
of the Thunderbolt NVM? I wonder if your thunderbolt controller is in
safe mode. If so you won't be seeing a version in fwupd. Please share
your fwupdmgr devices output.
--
You received this bug notification because you are a
There is an updated NVM for the 9360. It's posted to LVFS testing remote.
You can manually download it from here.
https://fwupd.org/lvfs/device/dfd51125-338f-56ff-b721-fa3bea8e534e
Can you install that and see if if helps at all perhaps?
On Mon, Dec 25, 2017, 13:25 wdoekes <1715...@bugs.launchpa
Also don't use pm-utils. It did a few over zealous actions.
It's been removed from Ubuntu installs now but you may still have it from an
upgrade. You should use systemctl to invoke the suspend.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Well it's good to hear the Thunderbolt update did clear things up with
the initial issue. Just to probe a little more on the update process
though:
When you say thunderbolt enabled in setup can you be more specific which
Thunderbolt options you're referring to? That first error is confusing
to me
Yeah it does go to sleep after no use with those settings activated. It's
supposed to disappear from fwupd as a result too so I expected a different
error than that. But if you went really really fast I suppose that's a
possibility.
On Tue, Dec 26, 2017, 05:55 wdoekes <1715...@bugs.launchpad.net>
Closing as reported fixed by user. If you can reproduce it again please
re-open.
** No longer affects: linux (Ubuntu)
** Changed in: fwupd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
> So, does the touchpad use a firmware, and, if yes, how can the firmware
> version be queried?
All touchpads have firmware, this one is no different. You can read the HID
descriptor as described in the HID over I2C protocol specification. As
described in the specification the firmware version
FYI for those who are not subscribed to the issue filed to the kernel bugzilla:
Benjamin T. suspects this may be a userspace issue, not a kernel issue.
When someone reproduces this again please do the following:
1) # sudo rmmod i2c-hid
2) # sudo modprobe i2c-hid debug=1
3) Capture dmesg output a
This is an issue with the host controller. The vendor (ASMedia) has submitted a
patch here that fixes the issue:
http://www.spinics.net/lists/linux-usb/msg157958.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
*** This bug is a duplicate of bug 1667750 ***
https://bugs.launchpad.net/bugs/1667750
This is an issue with the host controller. The vendor (ASMedia) has submitted
a patch here that fixes the issue:
http://www.spinics.net/lists/linux-usb/msg157958.html
** This bug has been marked a duplica
1 - 100 of 624 matches
Mail list logo
