From: Maxim Mikityanskiy <maxtram95@gmail.com>
To: Richard Hughes <hughsient@gmail.com>
Cc: "Lopez, Jorge A (Security)" <jorge.lopez2@hp.com>,
"Alex Hung" <alexhung@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Mark Gross" <markgross@kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Barnabás Pőcze" <pobrn@protonmail.com>,
"Rishit Bansal" <rishitbansal0@gmail.com>,
"Enver Balalic" <balalic.enver@gmail.com>
Subject: Re: Firmware upgrade broke SW_TABLET_MODE on HP Dragonfly G2
Date: Wed, 8 Feb 2023 23:43:04 +0200 [thread overview]
Message-ID: <Y+QXXXX1u33Eyf4E@mail.gmail.com> (raw)
In-Reply-To: <CAD2FfiFUEMupUBoWj2hq9ep=R0Sk-xgBscXqMPefAipvoCg8eg@mail.gmail.com>
On Wed, Feb 08, 2023 at 08:09:16PM +0000, Richard Hughes wrote:
> On Wed, 8 Feb 2023 at 19:27, Lopez, Jorge A (Security)
> <jorge.lopez2@hp.com> wrote:
> > Please do ahead and demote the firmware for me.
>
> Okay, now I'm double confused; the only HP Elite Dragonfly G2 firmware
> on the LVFS has never been in any stable branch.
This is the firmware on LVFS, it's marked as stable:
https://fwupd.org/lvfs/devices/com.hp.laptop.system.T90.firmware
dmidecode says:
Handle 0x0001, DMI type 0, 26 bytes
BIOS Information
Vendor: HP
Version: T90 Ver. 01.09.01
Release Date: 05/05/2022
> Maxim -- are you sure
> you got the firmware from the LVFS (and not automatically through
> Windows Update)
Yes, I'm pretty sure, I don't have any Windows, and I used fwupdmgr to
upgrade (and then downgrade).
> and if so can you please send me the output of
> "fwupdmgr get-devices" off-list please.
Sure, will send in a few minutes.
>
> Richard.
next prev parent reply other threads:[~2023-02-08 21:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 14:07 Firmware upgrade broke SW_TABLET_MODE on HP Dragonfly G2 Maxim Mikityanskiy
2023-02-07 16:14 ` Lopez, Jorge A (Security)
2023-02-07 16:49 ` Maxim Mikityanskiy
2023-02-08 17:32 ` Richard Hughes
[not found] ` <PH0PR84MB1953825BC90B268904C6C7E5A8D89@PH0PR84MB1953.NAMPRD84.PROD.OUTLOOK.COM>
2023-02-08 20:09 ` Richard Hughes
2023-02-08 21:43 ` Maxim Mikityanskiy [this message]
2023-04-24 10:37 ` Richard Hughes
2023-04-24 14:18 ` Lopez, Jorge A (Security)
2023-04-25 15:05 ` Lopez, Jorge A (Security)
2023-04-27 16:36 ` Maxim Mikityanskiy
2023-04-27 19:26 ` Lopez, Jorge A (Security)
2023-05-01 13:58 ` Maxim Mikityanskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+QXXXX1u33Eyf4E@mail.gmail.com \
--to=maxtram95@gmail.com \
--cc=alexhung@gmail.com \
--cc=balalic.enver@gmail.com \
--cc=hdegoede@redhat.com \
--cc=hughsient@gmail.com \
--cc=jorge.lopez2@hp.com \
--cc=kai.heng.feng@canonical.com \
--cc=mario.limonciello@amd.com \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.com \
--cc=rishitbansal0@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox