HP Laptop 15-da3xxx
| Hardware | PCI/USB ID | Working? |
|---|---|---|
| Bluetooth | 0bda:b00a |
Yes |
| Webcam | 05c8:03d2 |
Yes |
| Wi-Fi | 10ec:c821 |
Yes |
| Ethernet | 10ec:8168 |
Yes |
| GPU | 8086:8a56 |
Yes |
| Touchpad | Yes | |
| Keyboard | Yes | |
| TPM | Untested | |
| SD-card reader | Untested | |
| Audio | 8086:34c8 |
Yes |
The HP Laptop 15-da3xxx1 features a 39.6 cm (15.6") diagonal HD display and Intel® Core™ i3-1005G1 with integrated graphics (ICL GT1).
- This is the model as reported by
dmidecode -t1under "Product Name". However, the exact model is going to be different as the last three digits are variable, and can be found by entering the "Serial Number" on HP's laptop support site. The base model is HP Laptop PC 15-da3000.
Installation
The Realtek RTL8821CE Wifi card and the Intel iGPU require linux-firmware to be installed.
During installation, its possible that the keyboard and touchpad will suddenly stop working due to a bug discussed below. Use external keyboard and mouse, or use the fix below.
Accessibility
The UEFI setup is a simple, text-based interface, navigated with a keyboard. It does not expose many options apart from the standard time/date settings and boot configurations.
To show a list of all available menus, press Esc.
To access the UEFI setup, press F10.
To access the boot menu, press F9.
Power Management
The idle battery drain is around 3-4 watts with TLP defaults. Under moderate browser use (10-15 tabs), it can last for up to 4 hours.
Wifi driver crash when waking from powersave state
The wifi driver, rtw88, can crash due to failure to wake from powersave state. This can cause sudden degradation in wifi performance.
The fix is to disable wifi powersave:
iw wlan0 set power_save off
This gets reset after reboot so its necessary to execute this on every boot or disable it in TLP.
Suspend-to-RAM
The laptop faces a number of issues when waking from suspend to RAM. The supported methods are:
$ cat /sys/power/mem_sleep
s2idle [deep]
Thus, both Suspend-to-RAM and suspend-to-idle are supported. The issues below have been noticed when using Suspend-to-RAM but might also be present when using suspend-to-idle.
Lag after waking
After waking from suspend, there is an input lag for up to 10 seconds. No input is accepted during this time. Fix has not yet been found.
There is also lag in waking from suspend, up to 20 seconds.
Integrated Keyboard and Touchpad not working after waking
After waking up, keyboard and mouse will not work. The precise fix for this is not known but the combination of the following kernel flags are known to fix the issue:
psmouse.synaptics_intertouch=1 i8042.nopnp=1 i8042.reset
Its possible not all of these flags are required so further testing is suggested to pinpoint the exact combination.
USB connected peripherals stop working after waking
The xHCI host is non responsive after waking up. The following kernel errors are logged:
xhci_hcd 0000:00:14.0: Timeout waiting for reset device command xhci_hcd 0000:00:14.0: Timeout waiting for reset device command xhci_hcd 0000:00:14.0: Timeout waiting for reset device command xhci_hcd 0000:00:14.0: Timeout waiting for reset device command xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead xhci_hcd 0000:00:14.0: HC died; cleaning up
This causes all USB peripherals to stop working.
The temporary fix is to unbind and rebind the xHCI host (change the ID if different):
echo -n "0000:00:14.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind
echo -n "0000:00:14.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind
To fix this permanently, use the quirk XHCI_RESET_ON_RESUME, using the kernel arg xhci_hcd.quirks=2. This has been tested to work.
But if for some reason that doesn't work, turning off USB Autosuspend might help. Either pass the additional kernel arg usbcore.autosuspend=-1 or configure it in TLP.
Function keys
By default, keys F1-F12 perform their alternative functions, and Fn+Fx is needed to press Fx, but there is a UEFI option to change this behavior. The following table assumes the default behavior (i.e., for F1, need to press Fn+F1, and so on).
| Key | Visible?1 | Marked?2 | Effect3 |
|---|---|---|---|
F1 |
Yes | Yes |
KEY_LEFTMETA (125), Shows Help
|
F2 |
Yes | Yes |
KEY_BRIGHTNESSDOWN (224)
|
F3 |
Yes | Yes |
KEY_BRIGHTNESSUP (225)
|
F4 |
Yes | Yes |
KEY_LEFTMETA (125), Changes Display Output
|
F5 |
No | No | No effect |
F6 |
Yes | Yes |
KEY_MUTE (113)
|
F7 |
Yes | Yes |
KEY_VOLUMEDOWN (114)
|
F8 |
Yes | Yes |
KEY_VOLUMEUP (115)
|
F9 |
Yes | Yes |
KEY_VOLUMEUP (115)
|
F10 |
Yes | Yes |
KEY_PLAYPAUSE (164)
|
F11 |
Yes | Yes |
KEY_NEXTSONG (163)
|
F12 |
Yes | Yes |
KEY_RFKILL (247)
|
- The key is visible to
wevand similar tools. - The physical key has a symbol on it, which describes its function.
- All effects as output by
libinput debug-events.
Firmware
fwupd does not support this device.
fwupdmgr update output:
Devices with no available firmware updates: • 0000:00:1f.5 • System Firmware No updatable devices
Kernel errors
The following ACPI errors are visible on boot:
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.DGPV], AE_NOT_FOUND (20250404/psargs-332) ACPI Error: Aborting method \_SB.PCI0.RP05.PCRP._ON due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
Additionally, the following warnings are also present:
hpet_acpi_add: no address or irqs in _CRS spi-nor spi0.0: supply vcc not found, using dummy regulator hp_wmi: query 0x4c returned error 0x6 r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
And when the laptop is shutting down, watchdog fails to stop leading to this (critical) error:
watchdog: watchdog0: watchdog did not stop!
However, these errors have had no noticeable impact on the system.
See also
- Generic HP laptop support page (for finding exact model): https://support.hp.com/us-en/products/la
- Support page for base model: https://support.hp.com/us-en/product/details/hp-laptop-pc-15-da3000/37526479