This bug was fixed in the package fwupd - 1.0.9-0ubuntu2
---
fwupd (1.0.9-0ubuntu2) bionic; urgency=medium
* Restrict libsmbios-dev to x86 architectures (LP: #1791999, #1768627,
#1719797)
-- Mario Limonciello Tue, 23 Oct 2018
11:35:36 -0500
** Changed in: fwupd (Ubuntu Bionic)
Same here after upgrading to 1.0.9-0ubuntu2. Shows up as version 21.00.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
Update loop for Thunderbolt NVM for Xps notebook 9360.
I've tested that the controller doesn't show up as 00.00 any more after
upgrading to 1.0.9-0ubuntu2.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Hello Andrei, or anyone else affected,
Accepted fwupd into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/fwupd/1.0.9-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- Software & Updates keeps notifying me there is a new update available
- related to Thunderbolt NVM for Xps notebook 9360, from version 00.00 to
- version 21.00. See the attached screenshot.
+ The fix for this particular issue is tracked in SRU bug
+
** Also affects: fwupd (Ubuntu Cosmic)
Importance: Medium
Status: Confirmed
** Also affects: fwupd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: fwupd (Ubuntu Cosmic)
Status: Confirmed => Fix Released
** Changed in: fwupd (Ubuntu Bionic)
The fix is contained in
https://github.com/hughsie/fwupd/commit/60c845627d3b5ad0beb56d85fbe5bdd47ad7d70e
for the 1_0_X branch and will be in the 1.0.9 release of fwupd and
master
(https://github.com/hughsie/fwupd/commit/25d51d14297713b4817ef9644f83e07e71344b0a)
which will be in the 1.2.0 release
Great!
I do see this:
15:14:06:0715 Thunderbolt Attempt 0: Failed to read NVM version
Which means it did use the new logic. Please leave a comment in the PR
on GitHub to assist in it getting accepted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
with the file ;-)
** Attachment added: "fwupd_journal2.txt"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1768627/+attachment/5169606/+files/fwupd_journal2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is the log of today
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
Update loop for Thunderbolt NVM for Xps notebook 9360. Installed
version is not recognized (00.00)
To manage
That's good to hear. Would you mind confirming that in your debug log it
is trying to read a second time? When you have verbose mode activated it
will log a message indicating it retried.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Mario, at the moment with the last PR #29 it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
Update loop for Thunderbolt NVM for Xps notebook 9360. Installed
version is
https://github.com/hughsie/fwupd/pull/609
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
Update loop for Thunderbolt NVM for Xps notebook 9360. Installed
version is not recognized
If you can please test this branch instead to see if it helps for you.
Same thing provide the debug log if it isn't helping still.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
@Mauro,
Okay, perfect thanks. So from this debug log we can tell for sure that this
isn't caused by thunderbolt power, but rather the value read from the kernel
immediately is invalid.
This tells me that this is probably a case of fwupd racing with the kernel
based off the uevent that came
Thank you for the patience.
As attachment the output of the journal.
** Attachment added: "fwupd_journal.txt"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1768627/+attachment/5167776/+files/fwupd_journal.txt
--
You received this bug notification because you are a member of Ubuntu
@Mauro,
Thanks for checking, that's unfortunate that it's still happening.
To modify that file open it with an editor as root. For example:
sudo nano /lib/systemd/system/fwupd.service
or
sudo gedit /lib/systemd/system/fwupd.service
To view output from the journal:
journalctl -u fwupd.service
Hi Mario,
after installing the new version of fwupd (generated with docker). Like
the post #17, i still have the problem. I would like to do the other
steps proposed in #21, but I have some trouble (sorry I'm not a
specialist) to exec them.
Can you please explain me (like a dummies), thank's.
This was built in docker? Or built locally? That's odd if in docker
since CI ran the same test just fine.
One solution can be to turn off unit tests (locally add to the environment
DEB_BUILD_OPTIONS=nocheck)
http://www.ducea.com/2008/12/07/deb_build_optionsnocheck/
To do this with docker you
Hi Mario, I am not a Git specialist and software engineer. But with some
help from my girlfriend I have made almost all the points.
During the generation of the Deb package I receive an error at the point
fu-self-test (3/13 fu-self-test FAIL 4.36 s (killed by signal 6
SIGABRT)) log is in
So I think I might have a PR that will help this bug. Can you please try this
PR?
https://github.com/hughsie/fwupd/pull/605#issuecomment-407097175
You can generate Ubuntu 18.04 packages following instructions here:
https://github.com/hughsie/fwupd/tree/master/contrib
If it persists, can you
I have the same problem I installed update 28.00, but after reboot it detects
00.00.
How can I help you to solve the problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
Update
I have found I way to reproduce the problem.
1) boot with a thunderbolt device connected
2) sudo fwupdmgr get-devices get version 26.1
3) restart without thunderbolt device
4) sudo fwupdmgr get-devices get version 00.00
The attached file is the output of the #12 procedure, result of step 2 is
OK. So is it happening reproducibly like every boot for you now?
If so, can you please try to do the steps in #12 I listed above, but
please make sure that step 2 is included? That's what I'm most
interested to see.
--
You received this bug notification because you are a member of Ubuntu
After some days of reboot and work I still have the message of upgrading
the Thunderbolt. The message is like before, actual version is 00.00.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Thank's Mario for the super fast response. I have made the update to the
version 26, after a reboot is ok. But it was the same situation with
version 21.
I will wait for some days to check if it still ok with 26.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Mauro,
It looks like you skipped step 2.
Would you please upgrade to NVM 26 and see if it's still happening? It's
available here:
https://github.com/dell/thunderbolt-nvm-linux/issues/11
** Bug watch added: github.com/dell/thunderbolt-nvm-linux/issues #11
** Changed in: fwupd (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
Update loop for Thunderbolt NVM for Xps notebook 9360. Installed
Hi, I have the same bug and regular I receive the notification of new
firmware version.
I have made the steps in the post #12. Is possible to reopen the bug?
** Attachment added: "output.txt"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1768627/+attachment/5162948/+files/output.txt
[Expired for fwupd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: fwupd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
OK can you both please do the following:
0) Observe where the end of your current dmesg output is
1) Manually turn on force power
# echo 1 | sudo tee
/sys/bus/wmi/devices/86CCFD48-205E-4A77-9C48-2021CBEDE341/force_power
2) Check in /sys/bus/thunderbolt/devices/0-0/ and read the NVM version
The problem persists on my side.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
Update loop for Thunderbolt NVM for Xps notebook 9360. Installed
version is not recognized (00.00)
i have the same problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
Update loop for Thunderbolt NVM for Xps notebook 9360. Installed
version is not recognized (00.00)
To manage
Nothing was connected to the Type-C port. I don't have any thunderbolt
devices...
I am connecting my mobile phone (Nexus 6P) using the Type-C port and
works fine.
Here is what I have in syslog related to thunderbolt:
May 3 09:32:07 xps13 kernel: [ 2015.028567] thunderbolt :03:00.0: NHI
During this boot that you collected this information did you have
anything plugged into the Type-C port? If so, was it a Thunderbolt
device? Do you have any thunderbolt devices that you can connect and
see if they work properly?
Can you please check your syslog for anything related to
Sorry, but /sys/bus/thunderbolt/devices is empty.
/sys/bus/thunderbolt/devices$ ll
total 0
drwxr-xr-x 2 root root 0 May 5 00:07 ./
drwxr-xr-x 4 root root 0 May 5 00:07 ../
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the output of get-devices:
XPS13 9360 Thunderbolt Controller
DeviceId: 590e67e817585cbde0a07e8562d13d0d3a06776d
Guid: 4d86f168-e1cc-5995-afd3-ae9df6a14f5e
Guid: dfd51125-338f-56ff-b721-fa3bea8e534e
Summary: Unmatched
That's odd, I don't see that the thunderbolt in safe mode. Can you
please show the fwupdmgr get-devices output? It's still showing 0.00
there too?
Can you please check in /sys/bus/thunderbolt/devices and find your
controller there. is it also showing the same under nvm_version?
--
You
The thunderbolt works fine, the driver is functional.
It's just a problem with updating the package... the system see the
installed version as 00.00 and wants to updated it to 21.00.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached.
** Attachment added: "log"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1768627/+attachment/5132762/+files/fw.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
40 matches
Mail list logo
