Reorganize repo
This commit is contained in:
parent
eec670e464
commit
8cf3edd54d
56
README.md
56
README.md
|
|
@ -22,57 +22,7 @@ Intel Xe graphics are very recent, and so are the drivers. Regardless of platfor
|
|||
|
||||
Surprisingly that's mostly it. Keyboard, gamepad, ports, WiFi, Bluetooth and most other things just work as long as your kernel is recent enough.
|
||||
|
||||
# Main issues
|
||||
# Table of contents
|
||||
|
||||
## Ignored TDP
|
||||
|
||||
My GPD Win 3 mostly ignores the TDP set in the BIOS and runs with PL1 at 25W and PL2 at 28W regardless. I have not yet tested if it entirely disregards the TDP, or simply runs with TDP "Up" constantly. Needless to say, this wrecks battery life.
|
||||
|
||||
This can be fixed by manually setting this using `intel_rapl`. Which can be done by echoing wattage in µW to a /sys endpoint:
|
||||
|
||||
```
|
||||
# This example sets PL1/PL2 to 10W and 12W respectively
|
||||
echo 10000000 /sys/class/powercap/intel-rapl:0/constraint_0_power_limit_uw:100000000
|
||||
echo 12000000 /sys/class/powercap/intel-rapl:0/constraint_1_power_limit_uw:120000000
|
||||
```
|
||||
|
||||
The `tdp` script in this repo will automate/simplify this. But as of me writing this it's just boilerplate code. When I finish it, it will support commands such as `tdp check` and `tdp set 15` to check and set TDP using nice round numbers, and short commands that are easy to type on the GPD Win 3's keyboard.
|
||||
|
||||
## Sound does not work
|
||||
|
||||
Probably a very Ubuntu 21.04 specific bug, but sound does not work, the sound card is detected by ALSA out of the box, but PulseAudio only displays a "Dummy output". Thus most software does not output sound properly.
|
||||
|
||||
This was fixed by adding the following to a modprobe config file, for example `/etc/modprobe.d/alsa-base.conf`:
|
||||
|
||||
```
|
||||
options snd-hda-intel dmic_detect=0
|
||||
```
|
||||
|
||||
Which presumably disables mic output on the combo jack, but I have not tested if that's true. The built-in mic does still respond.
|
||||
|
||||
## Can't change screen settings
|
||||
|
||||
For whatever reason Ubuntu 21.04 didn't let me change display settings. It was stuck with 2x scaling and portrait orientation, which makes it nigh unusable. (Effective display width is only 360px, probaly about 280px after accounting for Ubuntu's dock.)
|
||||
|
||||
Fixed by manually setting scaling to 1 using gsettings:
|
||||
|
||||
```
|
||||
gsettings set org.gnome.desktop.interface scaling-factor 1
|
||||
```
|
||||
|
||||
I could then also rotate the display using the GUI, not sure why. Presumably orientation can also be fixed via gsettings if needed.
|
||||
|
||||
## Crappy Intel drivers
|
||||
|
||||
This is a platform-agnostic problem. Intel Xe drivers are in their infancy, so you will get graphical bugs and compatibility issues quite often. This happens both on Windows and on Linux.
|
||||
|
||||
When on Linux, the best way to negate the issue is to make sure your Mesa is as up-to-date as possible. For Ubuntu users there are PPAs for this:
|
||||
|
||||
- Latest stable Mesa: https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa
|
||||
- Latest unstable Mesa: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
|
||||
|
||||
Obviously these are 3rd party repos, so I can't guarrantee their stability or that they won't cause issues in the fugure. But updating Mesa is a fairly common thing on Ubuntu so the likelyhood of issues appearing should be very low.
|
||||
|
||||
I personally installed the latest stable, and accepted the fact that some games will just have the odd texture or shadow bug.
|
||||
|
||||
As Intel's Xe drivers mature, this issue should disappear on its own.
|
||||
- [Main Issues](docs/Main-issues.md)
|
||||
- [Quirks](docs/Quirks.md)
|
||||
|
|
|
|||
|
|
@ -0,0 +1,60 @@
|
|||
# Main issues
|
||||
|
||||
This is an overview of most "considerable" issues I encountered while installing Linux.
|
||||
|
||||
## Ignored TDP
|
||||
|
||||
My GPD Win 3 mostly ignores the TDP set in the BIOS and runs with PL1 at 25W and PL2 at 28W regardless. I have not yet tested if it entirely disregards the TDP, or simply runs with TDP "Up" constantly. Needless to say, this wrecks battery life.
|
||||
|
||||
This can be fixed by manually setting this using `intel_rapl`. Which can be done by echoing wattage in µW to a /sys endpoint:
|
||||
|
||||
```
|
||||
# This example sets PL1/PL2 to 10W and 12W respectively
|
||||
echo 10000000 /sys/class/powercap/intel-rapl:0/constraint_0_power_limit_uw:100000000
|
||||
echo 12000000 /sys/class/powercap/intel-rapl:0/constraint_1_power_limit_uw:120000000
|
||||
```
|
||||
|
||||
The `tdp` script in this repo will automate/simplify this. But as of me writing this it's just boilerplate code. When I finish it, it will support commands such as `tdp check` and `tdp set 15` to check and set TDP using nice round numbers, and short commands that are easy to type on the GPD Win 3's keyboard.
|
||||
|
||||
## Sound does not work
|
||||
|
||||
Probably a very Ubuntu 21.04 specific bug, but sound does not work, the sound card is detected by ALSA out of the box, but PulseAudio only displays a "Dummy output". Thus most software does not output sound properly.
|
||||
|
||||
This was fixed by adding the following to a modprobe config file, for example `/etc/modprobe.d/alsa-base.conf`:
|
||||
|
||||
```
|
||||
options snd-hda-intel dmic_detect=0
|
||||
```
|
||||
|
||||
Which presumably disables mic output on the combo jack, but I have not tested if that's true. The built-in mic does still respond.
|
||||
|
||||
## Can't change screen settings
|
||||
|
||||
For whatever reason Ubuntu 21.04 didn't let me change display settings. It was stuck with 2x scaling and portrait orientation, which makes it nigh unusable. (Effective display width is only 360px, probaly about 280px after accounting for Ubuntu's dock.)
|
||||
|
||||
Fixed by manually setting scaling to 1 using gsettings:
|
||||
|
||||
```
|
||||
gsettings set org.gnome.desktop.interface scaling-factor 1
|
||||
```
|
||||
|
||||
I could then also rotate the display using the GUI, not sure why. Presumably orientation can also be fixed via gsettings if needed.
|
||||
|
||||
## Crappy Intel drivers
|
||||
|
||||
This is a platform-agnostic problem. Intel Xe drivers are in their infancy, so you will get graphical bugs and compatibility issues quite often. This happens both on Windows and on Linux.
|
||||
|
||||
When on Linux, the best way to negate the issue is to make sure your Mesa is as up-to-date as possible. For Ubuntu users there are PPAs for this:
|
||||
|
||||
- Latest stable Mesa: https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa
|
||||
- Latest unstable Mesa: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
|
||||
|
||||
Obviously these are 3rd party repos, so I can't guarrantee their stability or that they won't cause issues in the fugure. But updating Mesa is a fairly common thing on Ubuntu so the likelyhood of issues appearing should be very low.
|
||||
|
||||
I personally installed the latest stable, and accepted the fact that some games will just have the odd texture or shadow bug.
|
||||
|
||||
As Intel's Xe drivers mature, this issue should disappear on its own.
|
||||
|
||||
## No touchscreen
|
||||
|
||||
My touchscreen does not work out of the box. I've heard it's possible to get it working if you install and configure the correct drivers for it. But I had little need for the touch screen, so I have not looked into this yet.
|
||||
|
|
@ -0,0 +1,15 @@
|
|||
# GPD Win 3 device quirks
|
||||
|
||||
This is an overview of quirks that you should be aware of while using the GPD Win 3, some are hardware and others are Linux-specific.
|
||||
|
||||
## Mouse/gamepad toggle "disconnects" gamepad
|
||||
|
||||
The GPD has a switch that let's you swap between mouse mode and gamepad mode.
|
||||
|
||||
Gamepad mode emulates an Xbox 360 gamepad, so most software should be very compatible.
|
||||
|
||||
However, the gamepad is "disconnected" when the switch is set to mouse mode. This means that software incapable of detecting new controllers while running may struggle with it.
|
||||
|
||||
For example the Dolphin emulator generally doesn't properly detect a reconnected gamepad. So you must keep the Win 3 in gamepad mode when starting Dolphin and using it. If you switch it to mouse mode, Dolphin will not detect the controller after you return to gamepad mode. You will have to restart Dolphin (while keeping the Win 3 in gamepad mode) for the controls to start working again.
|
||||
|
||||
The vast majority of software can handle you unplugging your gamepad and plugging it back in. But some software doesn't, and in those cases this might be a pain in the bum.
|
||||
Loading…
Reference in New Issue