[opensuse-support] fwupd problems on DELL XPS 13
Hi *, I got a new DELL XPS 13 9370 up and running with openSUE Tumbleweed. Because of problems with the Atheros wifi device I want to update the BIOS. Running "fwupdmgr get-devices" gives "/usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be found", though. The same messages occurs when restarting the fwupd daemon. Running the update with "fwupdmgr refresh" and "fwupdmgr update" gives: No upgrades for XPS 13 9370 Thunderbolt Controller, current is 33.00: 33.00=same, 28.00=older ignoring XPS 13 9370 System Firmware [8a21cacfb0a8d2b30c5ee9290eb71db021619f8b] as not updatable So the update of the Thunderbolt controller had succeeded in a previous run, but the firmware update itself does not run. I read a lot of things on the internet, but couldn't find a solution. One thing I read was to sign fwupdx64.efi with sbsign. This utility can be found in the sbsigntools package with was not included in one of the standard Tumbleweed repos. So I installed it from an openSUSE developer repo. Unfortunately I don't know what cert and key files to use for signing. So the questions are: 1. How to do a BIOS upgrade with fwupd in Tumbleweed the correct way? 2. If signing fwupdx64.efi is the correct way, what cert and key file to use? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hi again, should have mentioned, that secureboot is active!
Hi *,
I got a new DELL XPS 13 9370 up and running with openSUE Tumbleweed. Because of problems with the Atheros wifi device I want to update the BIOS.
Running "fwupdmgr get-devices" gives "/usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be found", though.
The same messages occurs when restarting the fwupd daemon.
Running the update with "fwupdmgr refresh" and "fwupdmgr update" gives:
No upgrades for XPS 13 9370 Thunderbolt Controller, current is 33.00: 33.00=same, 28.00=older ignoring XPS 13 9370 System Firmware [8a21cacfb0a8d2b30c5ee9290eb71db021619f8b] as not updatable
So the update of the Thunderbolt controller had succeeded in a previous run, but the firmware update itself does not run.
I read a lot of things on the internet, but couldn't find a solution. One thing I read was to sign fwupdx64.efi with sbsign. This utility can be found in the sbsigntools package with was not included in one of the standard Tumbleweed repos. So I installed it from an openSUSE developer repo. Unfortunately I don't know what cert and key files to use for signing.
So the questions are:
1. How to do a BIOS upgrade with fwupd in Tumbleweed the correct way? 2. If signing fwupdx64.efi is the correct way, what cert and key file to use?
TIA.
Bye. Michael. -- Michael Hirmke
-- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
17.12.2018 19:00, Michael Hirmke пишет:
Hi again,
should have mentioned, that secureboot is active!
Have your tried to disable it for FW update?
Hi *,
I got a new DELL XPS 13 9370 up and running with openSUE Tumbleweed. Because of problems with the Atheros wifi device I want to update the BIOS.
Running "fwupdmgr get-devices" gives "/usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be found", though.
Open bug report. fwupd expects file with name fwupdx64.efi.signed when secure boot is enabled, while fwupdate (which builds fwupdx64.efi) openSUSE build signs main binary fwupdx64.efi using OBS toolkit. Could you test ln -s fwupdx64.efi fwupdx64.efi.signed with SB enabled? That sounds like the simplest fix.
The same messages occurs when restarting the fwupd daemon.
Running the update with "fwupdmgr refresh" and "fwupdmgr update" gives:
No upgrades for XPS 13 9370 Thunderbolt Controller, current is 33.00: 33.00=same, 28.00=older ignoring XPS 13 9370 System Firmware [8a21cacfb0a8d2b30c5ee9290eb71db021619f8b] as not updatable
Are you sure there are updates for your system in the first place? I have Latitude E5450 and although it is recognized by fwupd, it does not show any available updates. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hi Andrei, thx for your answer.
17.12.2018 19:00, Michael Hirmke ?????:
Hi again,
should have mentioned, that secureboot is active!
Have your tried to disable it for FW update?
No, because I suspect, that I have to create a new boot entry with a non secure image, then. And I wanted to avoid that in the first place. [...]
Open bug report. fwupd expects file with name fwupdx64.efi.signed when secure boot is enabled, while fwupdate (which builds fwupdx64.efi) openSUSE build signs main binary fwupdx64.efi using OBS toolkit.
Ok.
Could you test
ln -s fwupdx64.efi fwupdx64.efi.signed
with SB enabled? That sounds like the simplest fix.
Good idea - I will try that. [...]
Are you sure there are updates for your system in the first place? I have Latitude E5450 and although it is recognized by fwupd, it does not show any available updates.
There was a much newer firmware than the original one my notebook had. Meanwhile I installed it via BIOS flash utility. But when I tried fwupd, the original/older firmware was still in place. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hi again, [...]
Could you test
ln -s fwupdx64.efi fwupdx64.efi.signed
with SB enabled? That sounds like the simplest fix.
Good idea - I will try that.
tried that - and there are no more error messages. Furthermore: _$fwupdmgr refresh Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***************************************] Less than one minute remaining… Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc _$fwupdmgr update No upgrades for XPS 13 9370 Thunderbolt Controller, current is 33.00: 33.00=same, 28.00=older No upgrades for XPS 13 9370 System Firmware, current is 0.1.6.3: 0.1.6.3=same, 0.1.5.1=older, 0.1.4.0=older, 0.1.3.3=older, 0.1.2.1=older, 0.1.2.0=older Of course it is not possible to check, if it would work to update to a newer firmare at the moment, because the latest firmware already is installed. Thx and bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am Montag, 17. Dezember 2018, 16:16:00 CET schrieb Michael Hirmke:
I got a new DELL XPS 13 9370 up and running with openSUE Tumbleweed. Because of problems with the Atheros wifi device I want to update the BIOS.
Does Dell offer BIOS updates as ISO/Raw image, based on freedos or similar? If so, bring them to a USB stick, boot from stick, update BIOS...done Just as an idea... Axel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
17.12.2018 19:38, Axel Braun пишет:
Am Montag, 17. Dezember 2018, 16:16:00 CET schrieb Michael Hirmke:
I got a new DELL XPS 13 9370 up and running with openSUE Tumbleweed. Because of problems with the Atheros wifi device I want to update the BIOS.
Does Dell offer BIOS updates as ISO/Raw image, based on freedos or similar?
Latitude E5450 supports direct BIOS update using EXE (downloaded from Dell support site) from within EFI boot menu. Just copy file anywhere it can be accessed by firmware (ESP is the most obvious place, could also be USB stick) and select file. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hi Andrei,
17.12.2018 19:38, Axel Braun ?????:
Am Montag, 17. Dezember 2018, 16:16:00 CET schrieb Michael Hirmke:
I got a new DELL XPS 13 9370 up and running with openSUE Tumbleweed. Because of problems with the Atheros wifi device I want to update the BIOS.
Does Dell offer BIOS updates as ISO/Raw image, based on freedos or similar?
Latitude E5450 supports direct BIOS update using EXE (downloaded from Dell support site) from within EFI boot menu. Just copy file anywhere it can be accessed by firmware (ESP is the most obvious place, could also be USB stick) and select file.
This way I updated the firmware in the meantime. But I'd like to find out how fwupd works. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (3)
-
Andrei Borzenkov
-
Axel Braun
-
mh@mike.franken.de