https://wiki.archlinux.org/api.php?action=feedcontributions&user=BeckersC&feedformat=atomArchWiki - User contributions [en]2024-03-29T11:21:24ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=HP_Envy_x360_13z-ag000&diff=582122HP Envy x360 13z-ag0002019-09-13T16:03:51Z<p>BeckersC: Minor word changes in the Audio subsection and added a missing checkmark in the Audio workaround pinout.</p>
<hr />
<div>[[Category:HP]]<br />
<br />
The HP Envy X360 13z-ag000 was released in 2018. It has variable processors/ram and displays, from a Ryzen Mobile 2300U to a 2700U, from 4GB RAM to 16GB RAM, and a 1080p display to a 4K display.<br />
<br />
The specs of my particular model are:<br />
<br />
* 2500U with 16GB RAM<br />
* 4K display<br />
* Realtek RTL8822BE wireless chip<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Model''' || '''Status''' || '''Modules'''<br />
|- <br />
| GPU || AMD Vega IGPU || style="color:green" | '''Working''' || xf86-video-amdgpu; Backlight works<br />
|-<br />
| Wifi || Realtek RTL8822BE || style="color:green" | '''Working''' || r8822be<br />
|-<br />
| Bluetooth || Realtek RTL8822BE || style="color:green" | '''Working'''|| btusb<br />
|-<br />
| Audio || ||style="color:green" | '''Working''' || snd_hda_intel<br />
|-<br />
| Touchpad || Synaptics || style="color:green" | '''Working''' || synaptics<br />
|-<br />
| Camera || Normal 1080p + IR 336x340 || style="color:green" | '''Working''' || uvcvideo<br />
|-<br />
| Sensors || STM Sensor hub || style ="color:red" | '''Not Working''' || On Windows used for orientation sensing and hard drive drop protection<br />
|-<br />
| USB C || AMD xHCI Host Controller || style="color:red" | '''Not Working''' || Data and DP working<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
This laptop has secure boot enabled by default. To start the installer you need to disable it in the UEFI. Then you can just boot the installer in UEFI mode and just install like a normal UEFI system.<br />
<br />
There appears to be an option to use your own Secureboot keys. I've not yet investigated that.<br />
<br />
== Battery and Power Management ==<br />
<br />
a 4 hour battery life because of the 4K display. Currently I'm running a patched 4.17 kernel; 4.18 might improve battery life somewhat.<br />
<br />
== Display, Video Card ==<br />
<br />
The integrated Vega GPU works with the AMDGPU drivers. `GDK_SCALE=2` is somewhat necessary for most applications.<br />
<br />
== Audio ==<br />
<br />
The"Bang & Olufsen" top-soundbar is by default disabled. You can activate it by using the "hdajackretask" utility provided by alsa-tools. More information can be found in this thread: https://bugzilla.kernel.org/show_bug.cgi?id=189331<br />
<br />
The exact pinout can be found in this attachment: https://bugzilla.kernel.org/attachment.cgi?id=282109&action=edit<br />
<br />
{{ic|<br />
Options : [x] Show unconnected<br />
[ ] Set model <nowiki> = </nowiki> auto<br />
[X] Advanced ovveride<br />
[ ] Parser hints<br />
<br />
Pin ID; 0x14 <br />
[x] Override<br />
Connectivity : Jack; Location : Internal; Device : Speaker; Jack : Other Analog<br />
Color : Unknown; Jack detection : Not present; Channel group : 5; Channel : Front<br />
<br />
Pin ID: 0x17<br />
[X] Override<br />
Connectivity : Jack; Location : Internal; Device : Speaker; Jack : Other<br />
Color : Unknown; Jack detection : Not present; Channel group : 5; Channel : Back<br />
}}<br />
<br />
{{Note|that the top-soundbar only fires when using close to the max volume.}}<br />
<br />
== Touchscreen and Stylus ==<br />
<br />
Kernel 4.19.5 or greater is needed. [https://bugzilla.kernel.org/show_bug.cgi?id=198715#c14] [https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.5]<br />
<br />
The built in ELAN digitizer doesn't use the wacom driver by default, but it can be configured to do so. Switching to the wacom driver allows easier configuration of the digitizer and pen through tools like xsetwacom. This can be achieved with the following xorg configuration file:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/99-ELAN-stylus.conf|<br />
Section "InputClass"<br />
Identifier "Elan driver override"<br />
MatchUSBID "04f3:*"<br />
MatchDevicePath "/dev/input/event*"<br />
MatchIsTablet "true"<br />
Driver "wacom"<br />
EndSection<br />
}}<br />
<br />
After a reboot xsetwacom should now correctly register the device.<br />
<br />
{{hc|xsetwacom --list devices|<br />
ELAN0732:00 04F3:262A stylus id: 13 type: STYLUS <br />
ELAN0732:00 04F3:262A eraser id: 18 type: ERASER<br />
}}<br />
<br />
You can use xinput to probe the different devices and find out what actions get triggered by which buttons. For instance the "wacom bamboo ink" pen triggers the eraser device while touching the screen while maintaining the second side button pressed.<br />
<br />
xinput test $deviceID<br />
<br />
The following simple example script will bind rightclick to the eraser device.<br />
<br />
device=$(xsetwacom --list | grep -i "eraser" | awk '{print $(NF-2)}') <br />
xsetwacom --set "$device" button 1 3<br />
<br />
<br />
== Orientation Sensor ==<br />
<br />
No `iio` sensors are enumerated as of 4.18-rc7, with all possible iio modules compiled. `iio-sensor-proxy` returns no sensors detected.<br />
<br />
== Wireless Networking ==<br />
<br />
Works out of the box. `aspm=0` seems to prevent the card from dropping offline as much, but also worsens battery life.<br />
<br />
== Bluetooth ==<br />
<br />
Works out of the box with Motorola Pulse Escape on kernel 4.19.5.<br />
<br />
== Hard Drive ==<br />
<br />
Built-in NVME drive works with advertised speed. Blockdevices are located at /dev/nvme0n1p*.<br />
<br />
== Dual Boot ==<br />
<br />
Untested, but there shouldn't any difficulties.</div>BeckersChttps://wiki.archlinux.org/index.php?title=HP_Envy_x360_13z-ag000&diff=582120HP Envy x360 13z-ag0002019-09-13T15:51:17Z<p>BeckersC: Added audio subsection and working for non working topspeakerbar</p>
<hr />
<div>[[Category:HP]]<br />
<br />
The HP Envy X360 13z-ag000 was released in 2018. It has variable processors/ram and displays, from a Ryzen Mobile 2300U to a 2700U, from 4GB RAM to 16GB RAM, and a 1080p display to a 4K display.<br />
<br />
The specs of my particular model are:<br />
<br />
* 2500U with 16GB RAM<br />
* 4K display<br />
* Realtek RTL8822BE wireless chip<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Model''' || '''Status''' || '''Modules'''<br />
|- <br />
| GPU || AMD Vega IGPU || style="color:green" | '''Working''' || xf86-video-amdgpu; Backlight works<br />
|-<br />
| Wifi || Realtek RTL8822BE || style="color:green" | '''Working''' || r8822be<br />
|-<br />
| Bluetooth || Realtek RTL8822BE || style="color:green" | '''Working'''|| btusb<br />
|-<br />
| Audio || ||style="color:green" | '''Working''' || snd_hda_intel<br />
|-<br />
| Touchpad || Synaptics || style="color:green" | '''Working''' || synaptics<br />
|-<br />
| Camera || Normal 1080p + IR 336x340 || style="color:green" | '''Working''' || uvcvideo<br />
|-<br />
| Sensors || STM Sensor hub || style ="color:red" | '''Not Working''' || On Windows used for orientation sensing and hard drive drop protection<br />
|-<br />
| USB C || AMD xHCI Host Controller || style="color:red" | '''Not Working''' || Data and DP working<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
This laptop has secure boot enabled by default. To start the installer you need to disable it in the UEFI. Then you can just boot the installer in UEFI mode and just install like a normal UEFI system.<br />
<br />
There appears to be an option to use your own Secureboot keys. I've not yet investigated that.<br />
<br />
== Battery and Power Management ==<br />
<br />
a 4 hour battery life because of the 4K display. Currently I'm running a patched 4.17 kernel; 4.18 might improve battery life somewhat.<br />
<br />
== Display, Video Card ==<br />
<br />
The integrated Vega GPU works with the AMDGPU drivers. `GDK_SCALE=2` is somewhat necessary for most applications.<br />
<br />
== Audio ==<br />
<br />
The"Bang & Olufsen" topspeakerbar is by default disabled. You can activate it by using the "hdajackretask" utility provided by alsa-tools. More information can be found in this thread: https://bugzilla.kernel.org/show_bug.cgi?id=189331<br />
<br />
The exact pinout can be found in this attachment: https://bugzilla.kernel.org/attachment.cgi?id=282109&action=edit<br />
<br />
{{ic|<br />
Options : [x] Show unconnected<br />
[ ] Set model <nowiki> = </nowiki> auto<br />
[X] Advanced ovveride<br />
[ ] Parser hints<br />
<br />
Pin ID; 0x14 <br />
[x] Override<br />
Connectivity : Jack; Location : Internal; Device : Speaker; Jack : Other Analog<br />
Color : Unknown; Jack detection : Not present; Channel group : 5; Channel : Front<br />
<br />
Pin ID: 0x17<br />
Override<br />
Connectivity : Jack; Location : Internal; Device : Speaker; Jack : Other<br />
Color : Unknown; Jack detection : Not present; Channel group : 5; Channel : Back<br />
}}<br />
<br />
{{Note|that the topspeaker only fires when using close to the max volume.}}<br />
<br />
== Touchscreen and Stylus ==<br />
<br />
Kernel 4.19.5 or greater is needed. [https://bugzilla.kernel.org/show_bug.cgi?id=198715#c14] [https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.5]<br />
<br />
The built in ELAN digitizer doesn't use the wacom driver by default, but it can be configured to do so. Switching to the wacom driver allows easier configuration of the digitizer and pen through tools like xsetwacom. This can be achieved with the following xorg configuration file:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/99-ELAN-stylus.conf|<br />
Section "InputClass"<br />
Identifier "Elan driver override"<br />
MatchUSBID "04f3:*"<br />
MatchDevicePath "/dev/input/event*"<br />
MatchIsTablet "true"<br />
Driver "wacom"<br />
EndSection<br />
}}<br />
<br />
After a reboot xsetwacom should now correctly register the device.<br />
<br />
{{hc|xsetwacom --list devices|<br />
ELAN0732:00 04F3:262A stylus id: 13 type: STYLUS <br />
ELAN0732:00 04F3:262A eraser id: 18 type: ERASER<br />
}}<br />
<br />
You can use xinput to probe the different devices and find out what actions get triggered by which buttons. For instance the "wacom bamboo ink" pen triggers the eraser device while touching the screen while maintaining the second side button pressed.<br />
<br />
xinput test $deviceID<br />
<br />
The following simple example script will bind rightclick to the eraser device.<br />
<br />
device=$(xsetwacom --list | grep -i "eraser" | awk '{print $(NF-2)}') <br />
xsetwacom --set "$device" button 1 3<br />
<br />
<br />
== Orientation Sensor ==<br />
<br />
No `iio` sensors are enumerated as of 4.18-rc7, with all possible iio modules compiled. `iio-sensor-proxy` returns no sensors detected.<br />
<br />
== Wireless Networking ==<br />
<br />
Works out of the box. `aspm=0` seems to prevent the card from dropping offline as much, but also worsens battery life.<br />
<br />
== Bluetooth ==<br />
<br />
Works out of the box with Motorola Pulse Escape on kernel 4.19.5.<br />
<br />
== Hard Drive ==<br />
<br />
Built-in NVME drive works with advertised speed. Blockdevices are located at /dev/nvme0n1p*.<br />
<br />
== Dual Boot ==<br />
<br />
Untested, but there shouldn't any difficulties.</div>BeckersChttps://wiki.archlinux.org/index.php?title=HP_Envy_x360_13z-ag000&diff=570201HP Envy x360 13z-ag0002019-03-30T20:44:00Z<p>BeckersC: Expanding Stylus configuration; How to switch the driver and configure buttons through xsetwacom</p>
<hr />
<div>[[Category:HP]]<br />
<br />
The HP Envy X360 13z-ag000 was released in 2018. It has variable processors/ram and displays, from a Ryzen Mobile 2300U to a 2700U, from 4GB RAM to 16GB RAM, and a 1080p display to a 4K display.<br />
<br />
The specs of my particular model are:<br />
<br />
* 2500U with 16GB RAM<br />
* 4K display<br />
* Realtek RTL8822BE wireless chip<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Model''' || '''Status''' || '''Modules'''<br />
|- <br />
| GPU || AMD Vega IGPU || style="color:green" | '''Working''' || xf86-video-amdgpu; Backlight works<br />
|-<br />
| Wifi || Realtek RTL8822BE || style="color:green" | '''Working''' || r8822be<br />
|-<br />
| Bluetooth || Realtek RTL8822BE || style="color:green" | '''Working'''|| btusb<br />
|-<br />
| Audio || ||style="color:green" | '''Working''' || snd_hda_intel<br />
|-<br />
| Touchpad || Synaptics || style="color:green" | '''Working''' || synaptics<br />
|-<br />
| Camera || Normal 1080p + IR 336x340 || style="color:green" | '''Working''' || uvcvideo<br />
|-<br />
| Sensors || STM Sensor hub || style ="color:red" | '''Not Working''' || On Windows used for orientation sensing and hard drive drop protection<br />
|-<br />
| USB C || AMD xHCI Host Controller || style="color:red" | '''Not Working''' || Data and DP working<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
This laptop has secure boot enabled by default. To start the installer you need to disable it in the UEFI. Then you can just boot the installer in UEFI mode and just install like a normal UEFI system.<br />
<br />
There appears to be an option to use your own Secureboot keys. I've not yet investigated that.<br />
<br />
== Battery and Power Management ==<br />
<br />
a 4 hour battery life because of the 4K display. Currently I'm running a patched 4.17 kernel; 4.18 might improve battery life somewhat.<br />
<br />
== Display, Video Card ==<br />
<br />
The integrated Vega GPU works with the AMDGPU drivers. `GDK_SCALE=2` is somewhat necessary for most applications.<br />
<br />
== Touchscreen and Stylus ==<br />
<br />
Kernel 4.19.5 or greater is needed. [https://bugzilla.kernel.org/show_bug.cgi?id=198715#c14] [https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.5]<br />
<br />
The built in ELAN digitizer doesn't use the wacom driver by default, but it can be configured to do so. Switching to the wacom driver allows easier configuration of the digitizer and pen through tools like xsetwacom. This can be achieved with the following xorg configuration file:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/99-ELAN-stylus.conf|<br />
Section "InputClass"<br />
Identifier "Elan driver override"<br />
MatchUSBID "04f3:*"<br />
MatchDevicePath "/dev/input/event*"<br />
MatchIsTablet "true"<br />
Driver "wacom"<br />
EndSection<br />
}}<br />
<br />
After a reboot xsetwacom should now correctly register the device.<br />
<br />
{{hc|xsetwacom --list devices|<br />
ELAN0732:00 04F3:262A stylus id: 13 type: STYLUS <br />
ELAN0732:00 04F3:262A eraser id: 18 type: ERASER<br />
}}<br />
<br />
You can use xinput to probe the different devices and find out what actions get triggered by which buttons. For instance the "wacom bamboo ink" pen triggers the eraser device while touching the screen while maintaining the second side button pressed.<br />
<br />
xinput test $deviceID<br />
<br />
The following simple example script will bind rightclick to the eraser device.<br />
<br />
device=$(xsetwacom --list | grep -i "eraser" | awk '{print $(NF-2)}') <br />
xsetwacom --set "$device" button 1 3<br />
<br />
<br />
== Orientation Sensor ==<br />
<br />
No `iio` sensors are enumerated as of 4.18-rc7, with all possible iio modules compiled. `iio-sensor-proxy` returns no sensors detected.<br />
<br />
== Wireless Networking ==<br />
<br />
Works out of the box. `aspm=0` seems to prevent the card from dropping offline as much, but also worsens battery life.<br />
<br />
== Bluetooth ==<br />
<br />
Works out of the box with Motorola Pulse Escape on kernel 4.19.5.<br />
<br />
== Hard Drive ==<br />
<br />
Built-in NVME drive works with advertised speed. Blockdevices are loacated at /dev/nvme0n1p*.<br />
<br />
== Dual Boot ==<br />
<br />
Untested, but there shouldn't any difficulties.</div>BeckersC