Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Without --allow-reinstall the same version of BIOS could still be updated by fwupd #1675

Closed
zongminl opened this issue Dec 27, 2019 · 16 comments
Assignees
Labels

Comments

@zongminl
Copy link

zongminl commented Dec 27, 2019

In Ubuntu 18.04, I found the same version of BIOS could still be updated by sudo fwupdmgr install d7baa890b5d2642ebc2eb40a7cb8f990b1f6e42c-Bandon_1.4.1.cab without --allow-reinstall.

fwupd 1.0.9 (in -update channel):
BIOS update would be blocked by fwupdmgr without --allow-reinstall.
fwupd 1.2.5:
BIOS update would NOT be blocked by fwupdmgr without --allow-reinstall.
fwupd 1.2.10 (in -proposed channel):
BIOS update would NOT be blocked by fwupdmgr without --allow-reinstall.
fwupd 1.3.5:
BIOS update would NOT be blocked by fwupdmgr without --allow-reinstall.

u@u-Latitude-5300:~/Downloads$ sudo fwupdmgr install d7baa890b5d2642ebc2eb40a7cb8f990b1f6e42c-Bandon_1.4.1.cab 
Decompressing…         [***************************************]
Specified firmware is already installed '0.1.4.1'
u@u-Latitude-5300:~/Downloads$ fwupdmgr --version
client version:	1.0.9
daemon version:	1.0.9
compile-time dependency versions
	appstream-glib:	0.7.7
	gusb:	0.2.11
	fwupdate:	10
	efivar:	34


//=================================================================================================
u@u-Latitude-5300:~/Downloads$ fwupdmgr --version
client version:	1.2.5
compile-time dependency versions
	gusb:	0.2.11
	efivar:	34
daemon version:	1.2.5
u@u-Latitude-5300:~/Downloads$ sudo fwupdmgr install d7baa890b5d2642ebc2eb40a7cb8f990b1f6e42c-Bandon_1.4.1.cab 
Decompressing…           [***************************************]
Authenticating…          [***************************************]
Installing on Latitude 5300 System Firmware…                     ]
Scheduling…              [***************************************]

An update requires a reboot to complete. Restart now? [Y|n]: 
@hughsie
Copy link
Member

hughsie commented Jan 2, 2020

Can you attach the output of fwupdmgr get-devices --verbose please.

@zongminl
Copy link
Author

zongminl commented Jan 3, 2020

u@u-Latitude-5300:~$ fwupdmgr --version
client version:	1.3.5
compile-time dependency versions
	gusb:	0.3.0
	efivar:	37
daemon version:	1.3.5

u@u-Latitude-5300:~$ sudo fwupdmgr get-devices --verbose
(fwupdmgr:3315): FuMain-DEBUG: 10:49:28.043: PC401 NVMe SK hynix 512GB
  DeviceId:             3743975ad7f64f8d6575a9ae49fb3a8856fe186f
  Guid:                 12c8974c-99cd-5f9a-b310-c28d565a47f8 <- NVME\VEN_1C5C&DEV_1527&REV_00
  Guid:                 2260c743-963b-566e-93f1-8223c3e6b87b <- NVME\VEN_1C5C&DEV_1527
  Guid:                 c28fdadd-607d-578c-b6ed-60ac49682904 <- PC401 NVMe SK hynix 512GB
  Serial:               MI88N047510608S6M
  Summary:              NVM Express Solid State Drive
  Plugin:               nvme
  Flags:                internal|updatable|require-ac|registered|needs-reboot|usable-during-update
  Vendor:               Intel Corporation
  VendorId:             NVME:0x1C5C
  Version:              80007E00
  VersionFormat:        plain
  Icon:                 drive-harddisk
  Created:              2020-01-03

(fwupdmgr:3315): FuMain-DEBUG: 10:49:28.043: System Firmware
  DeviceId:             b03588a447340830af90b63cd5830a54455504fb
  Guid:                 93634829-10b8-4098-a617-d52d056a4dd8
  Plugin:               uefi
  Flags:                internal|updatable|require-ac|supported|registered|needs-reboot|can-verify|usable-during-update
  Checksum:             SHA1(b922e3f0b7ed52b24bf0b121d1ac42478ca4bb)
  Checksum:             SHA256(36d565a688137160451ee25450afcaed7ad1c90185abde5baf440f403c33283c)
  Vendor:               Dell Inc.
  Version:              0.1.5.0
  VersionLowest:        0.1.5.0
  VersionFormat:        quad
  Icon:                 computer
  Created:              2020-01-03

(fwupdmgr:3315): FuMain-DEBUG: 10:49:28.043: TPM 2.0
  DeviceId:             f205eb1376813f00b3e909a97c54cbbcd4199369
  Guid:                 670b5381-3fd0-5653-8610-f446d2bedd10 <- 08b7-2.0
  Guid:                 73730635-f6c2-53da-9df2-948bb5ac1022 <- DELL-TPM-2.0-STM-
  Summary:              Platform TPM device
  Plugin:               uefi
  Flags:                internal|require-ac|registered
  Vendor:               Dell Inc.
  Version:              0.74.0.8
  VersionFormat:        quad
  Icon:                 computer
  Created:              2020-01-03
  UpdateError:          Updating disabled due to TPM ownership

(fwupdmgr:3315): FuMain-DEBUG: 10:49:28.047: lvfs has no RemoteURI
(fwupdmgr:3315): FuMain-DEBUG: 10:49:28.047: no unreported devices

@hughsie
Copy link
Member

hughsie commented Jan 6, 2020

Version:              0.1.5.0
VersionLowest:        0.1.5.0
VersionFormat:        quad

I did expect to see "VersionFormat: dell" there for 1.3.5... Are you using the snap to get that?

@zongminl
Copy link
Author

zongminl commented Jan 6, 2020

I installed fwupd from apt.

@hughsie
Copy link
Member

hughsie commented Jan 6, 2020

I did expect to see "VersionFormat: dell" there for 1.3.5

Urgh, dell-bios was added in 1.3.6 --- could you install 1.3.6 and see if the issue is fixed there? Thanks.

@superm1
Copy link
Member

superm1 commented Jan 6, 2020

If it helps, 1.3.6 is in the snap stable channel now and once an Ubuntu archive administrator releases it, it will be in the proposed channel for Ubuntu focal (https://launchpad.net/ubuntu/+source/fwupd/1.3.6-1)

@superm1
Copy link
Member

superm1 commented Jan 6, 2020

@hughsie is 1fbcb1a enough to backport to 1_2_X for this you think?

@superm1 superm1 added the bug label Jan 6, 2020
@hughsie
Copy link
Member

hughsie commented Jan 6, 2020

Not sure; I hadn't thought too much about the non-legacy backport. I think you'd need quite a few more if you want the default per device verfmt on the standalone cab install.

@superm1
Copy link
Member

superm1 commented Jan 7, 2020

I've filed a backport here: #1694. That seems like it should be enough for me from the quick testing I did. ^ @ltmvic51

@ycheng
Copy link
Contributor

ycheng commented Jan 8, 2020

with #1694 applied to 1.2.10, build test failed on "3/15 fu-self-test"

check the below link for detail.

https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd-1.2.10-same-version-install/+build/18530288

@superm1
Copy link
Member

superm1 commented Jan 8, 2020

Can you check if functionality is okay though? I just didn't backport the self test fix. I'll do that tomorrow.

@zongminl
Copy link
Author

zongminl commented Jan 8, 2020

I verified fwupd 1.3.6, it can check the version in BIOS capsule and block BIOS update accordingly now.

ubuntu@Latitude-5300:~/Downloads$ fwupd.fwupdmgr --version
client version:	1.3.6
compile-time dependency versions
	gusb:	0.2.11
	efivar:	34
daemon version:	1.3.6
ubuntu@Latitude-5300:~/Downloads$ sudo fwupd.fwupdmgr install ffbf931509f73fd26b410ff8358b51f3eaa20e7f-firmware.cab 
Decompressing…           [***************************************]
Specified firmware is already installed '1.5.0'

@ycheng
Copy link
Contributor

ycheng commented Jan 8, 2020

Sorry not manage to test patch today. Will do tomorrow.

@superm1
Copy link
Member

superm1 commented Jan 8, 2020

#1694 was merged to the 1_2_X branch to backport this fix from 1.3.6.

@superm1 superm1 closed this as completed Jan 8, 2020
@superm1 superm1 self-assigned this Jan 8, 2020
@ycheng
Copy link
Contributor

ycheng commented Jan 10, 2020

for the record, test passed with the first three patch on merged #1694 applied to 1.2.10 on ubuntu bionic.

@superm1
Copy link
Member

superm1 commented Jan 10, 2020

@ycheng you might consider to also include 1f579d8 and
a5df5b0 and fa5274a

for fixing SRU https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1858590 as well as the cleanup behavior that you observed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

4 participants