HP Dragonfly G4 (Costco)


No issues with installation. Used the latest kernel option, but not sure if it’s required.


Great keyboard, great build. good battery life (7+ Hours in my normal use). Couldn’t get S3 sleep to work. Wish there were more i7-1355u laptops out there that can be used with Qubes. or any that support S3!

Basic Input


  • Keyboard
  • Touch-pad
  • Touch-pad supports “tap as click” and scrolling with 2 fingers works
  • Display brightness change shortcuts
  • Sound volume shortcuts,
  • Keyboard led and keyboard brightness change shortcuts,
  • Keyboard and touchpad use PS/2


USB Mouse

Internet and bluetooth

  • No Ethernet Port
  • Wifi works out of the box
  • Wifi Stable
  • Bluetooth untested


Suspend does not work. Laptop exposes S3 support and will go to sleep. However, laptop takes 1-2 minutes to wake up and keyboard does not work when it does. I spent the good part of a day digging into this and couldn’t find a solution.


  • sound from speakers works fine. rest untested.


  • Fans silent during normal use.


  • Did not test Windows HVM
  • Boost appears to work (performance would be really bad without it on a u series chip). However, I’m unsure how to get real cpu frequency readings. My troubleshooting with past laptops lead me to believe that Xen will always lie to me.


  • HP Dragonfly G4 Customization Page
  • 1920x1080 (13.5" 3:2 Screen). 3000x2000 OLED screen also available
  • Max Memory - 32GB
  • PassMark CPU Score (Generic, not tested specific model): 15369
  • 4 USB Controllers. 2 USB-C Ports, 1 USB-A Port
  • Internal TPM

xinput --list

|⎡ Virtual core pointer                    |id=2|[master pointer  (3)]|
|⎜   ↳ Virtual core XTEST pointer              |id=4|[slave  pointer  (2)]|
|⎜   ↳ SYNA310F:00 06CB:CEA9 Mouse             |id=9|[slave  pointer  (2)]|
|⎜   ↳ SYNA310F:00 06CB:CEA9 Touchpad          |id=10|[slave  pointer  (2)]|
|⎜   ↳ ELAN2513:00 04F3:41A8                   |id=11|[slave  pointer  (2)]|
|⎣ Virtual core keyboard                   |id=3|[master keyboard (2)]|
|    ↳ Virtual core XTEST keyboard             |id=5|[slave  keyboard (3)]|
|    ↳ Power Button                            |id=6|[slave  keyboard (3)]|
|    ↳ Video Bus                               |id=7|[slave  keyboard (3)]|
|    ↳ Sleep Button                            |id=8|[slave  keyboard (3)]|
|    ↳ Intel HID events                        |id=12|[slave  keyboard (3)]|
|    ↳ Intel HID 5 button array                |id=13|[slave  keyboard (3)]|
|    ↳ AT Translated Set 2 keyboard            |id=14|[slave  keyboard (3)]|
|    ↳ HP WMI hotkeys                          |id=15|[slave  keyboard (3)]|


Qubes-HCL-HP-HP_Dragonfly_13_5_inch_G4_Notebook_PC-20240116-144719.yml (875 Bytes)


Oh, and for those wondering I get errors like this when I wake up the laptop:

ACPI: PM: Waking up from system sleep state S3
ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20221020/evregion-300)
ACPI Error: Timeout from EC hardware or EC device driver (20221020/evregion-310)
ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.ITLB due to previous error (AE_TIME) (20221020/psparse-529)
ACPI Error: Aborting method \HWAK due to previous error (AE_TIME) (20221020/psparse-529)
ACPI Error: Aborting method \_WAK due to previous error (AE_TIME) (20221020/psparse-529)
ACPI Error: AE_TIME, While executing method \_WAK (20221020/hwesleep-47)

I wasn’t able to get a DSDT table extracted that was compilable, so I gave up on it.

1 Like

Thanks for a detailed HCL report!

Wow, does it work?

Dunno, didn’t have one. I’ve taken a look at OLED screens on other laptops and they hurt my eyes. Probably a combination of reading text on the subpixel layout + the low PWM refresh rate.

ofc, I also try to avoid screen with more than 1920x1200 pixels due to the concern that software rendering will tax the CPU too much. (I couldn’t find much info on people using hidpi screen, so I’m not sure how many issues this causes)

Oh, and it doesn’t look like I can edit the original post anymore. I made a mistake with the resolution. it’s 1920x1280, not 1920x1200. Get an extra 80 pixels due to the 3:2 aspect ratio.

I see, you can Flag your post for moderator with a note to make these changes (I am not a moderator).

And is 3000x200 a really correct resolution? I thought it had some optional narrow LCD panel as a second display in the system, but maybe you meant main screen and made a typo in the resolution of it, too?

It should be 3200x2000. I’ll flag my post.

1 Like

Thanks for the HCL report. I just submitted a pull request to merge it.

1 Like