Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/pull_request_template.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,6 @@

- [ ] PR title follows the commit convention (e.g. `fix: correct nmcli command in eduroam guide`)
- [ ] Both EN and NL versions updated (if applicable)
- [ ] Images are in AVIF format (not PNG/JPG)
- [ ] Media is in AVIF format (not PNG/JPG)
- [ ] No broken image references (`/images/*.avif` all exist in `static/images/`)
- [ ] Tested locally with `hugo server`
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ I am not affiliated with, endorsed by, or acting on behalf of ASUS, NVIDIA, Micr
| **iGPU** | AMD Radeon 890M |
| **dGPU** | NVIDIA GeForce RTX 4060 Laptop (Max-Q) |
| **OS** | CachyOS (Arch) |
| **Kernel** | 6.19.3-2 |
| **Kernel** | 6.19.4-2 |
| **Display Server** | Wayland (GNOME 49) |
| **CPU Scheduler** | scx_lavd (sched_ext) |
| **Secure Boot** | Enabled |
Expand All @@ -38,7 +38,7 @@ I am not affiliated with, endorsed by, or acting on behalf of ASUS, NVIDIA, Micr
This documentation site is built with [Hugo](https://gohugo.io/) using the [Hextra](https://imfing.github.io/hextra/) theme. The theme is managed as a Hugo module (via Go modules — no git submodules).

**Prerequisites:**
- [Hugo extended](https://gohugo.io/installation/) v0.156.0 (built with this version)
- [Hugo extended](https://gohugo.io/installation/) v0.157.0 (built with this version)
- [Go](https://go.dev/dl/) (required for Hugo modules)
- Git

Expand Down
4 changes: 2 additions & 2 deletions README.nl.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Ik ben niet gelieerd aan, goedgekeurd door, of handelend namens ASUS, NVIDIA, Mi
| **iGPU** | AMD Radeon 890M |
| **dGPU** | NVIDIA GeForce RTX 4060 Laptop (Max-Q) |
| **OS** | CachyOS (Arch) |
| **Kernel** | 6.19.3-2 |
| **Kernel** | 6.19.4-2 |
| **Displayserver** | Wayland (GNOME 49) |
| **CPU-scheduler** | scx_lavd (sched_ext) |
| **Secure Boot** | Ingeschakeld |
Expand All @@ -38,7 +38,7 @@ Ik ben niet gelieerd aan, goedgekeurd door, of handelend namens ASUS, NVIDIA, Mi
Deze documentatiesite is gebouwd met [Hugo](https://gohugo.io/) en het [Hextra](https://imfing.github.io/hextra/)-thema. Het thema is opgenomen als Hugo module (via Go modules — geen git submodules).

**Vereisten:**
- [Hugo extended](https://gohugo.io/installation/) v0.156.0 (gebouwd met deze versie)
- [Hugo extended](https://gohugo.io/installation/) v0.157.0 (gebouwd met deze versie)
- [Go](https://go.dev/dl/) (vereist voor Hugo modules)
- Git

Expand Down
10 changes: 8 additions & 2 deletions content/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ toc: false
<div class="hx-mt-6"></div>

{{< callout type="info" >}}
**Personal documentation.** I'm not a developer or Linux expert, just someone who switched to Linux on this laptop and figured things out along the way. I share what worked for me so others don't have to start from scratch. Everything here is at your own risk. Feel free to reach out if something doesn't work; I'm happy to think along. Running kernel 6.19.3-2 on CachyOS (Arch).
**Personal documentation.** I'm not a developer or Linux expert, just someone who switched to Linux on this laptop and figured things out along the way. I share what worked for me so others don't have to start from scratch. Everything here is at your own risk. Feel free to reach out if something doesn't work; I'm happy to think along. Running kernel 6.19.4-2 on CachyOS (Arch).
{{< /callout >}}

## Current System Configuration
Expand All @@ -37,7 +37,7 @@ toc: false
| **iGPU** | AMD Radeon 890M |
| **dGPU** | NVIDIA GeForce RTX 4060 Laptop (Max-Q) |
| **OS** | CachyOS (Arch) |
| **Kernel** | 6.19.3-2 |
| **Kernel** | 6.19.4-2 |
| **Display Server** | Wayland (GNOME 49) |
| **CPU Scheduler** | scx_lavd (sched_ext) |
| **Secure Boot** | Enabled |
Expand Down Expand Up @@ -132,6 +132,12 @@ toc: false
icon="eye"
link="docs/virtualization/looking-glass-attempt"
>}}
{{< hextra/feature-card
title="WinBoat"
subtitle="Windows apps on Linux via Podman container, early beta"
icon="beaker"
link="docs/virtualization/winboat"
>}}
{{< /hextra/feature-grid >}}

---
10 changes: 8 additions & 2 deletions content/_index.nl.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ toc: false
<div class="hx-mt-6"></div>

{{< callout type="info" >}}
**Persoonlijke documentatie.** Ik ben geen developer of Linux-expert, gewoon iemand die overgestapt is naar Linux op deze laptop en dingen uitzoekend onderweg. Ik deel wat werkte zodat anderen niet helemaal opnieuw hoeven te beginnen. Alles is op eigen risico. Kom je ergens niet uit, laat het gerust weten; ik denk graag mee. Draait kernel 6.19.3-2 op CachyOS (Arch).
**Persoonlijke documentatie.** Ik ben geen developer of Linux-expert, gewoon iemand die overgestapt is naar Linux op deze laptop en dingen uitzoekend onderweg. Ik deel wat werkte zodat anderen niet helemaal opnieuw hoeven te beginnen. Alles is op eigen risico. Kom je ergens niet uit, laat het gerust weten; ik denk graag mee. Draait kernel 6.19.4-2 op CachyOS (Arch).
{{< /callout >}}

## Huidige Systeemconfiguratie
Expand All @@ -37,7 +37,7 @@ toc: false
| **iGPU** | AMD Radeon 890M |
| **dGPU** | NVIDIA GeForce RTX 4060 Laptop (Max-Q) |
| **OS** | CachyOS (Arch) |
| **Kernel** | 6.19.3-2 |
| **Kernel** | 6.19.4-2 |
| **Display Server** | Wayland (GNOME 49) |
| **CPU Scheduler** | scx_lavd (sched_ext) |
| **Secure Boot** | Ingeschakeld |
Expand Down Expand Up @@ -132,6 +132,12 @@ toc: false
icon="eye"
link="docs/virtualization/looking-glass-attempt"
>}}
{{< hextra/feature-card
title="WinBoat"
subtitle="Windows-apps op Linux via Podman container, vroege beta"
icon="beaker"
link="docs/virtualization/winboat"
>}}
{{< /hextra/feature-grid >}}

---
2 changes: 1 addition & 1 deletion content/docs/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ If something here helps you, great. If you run into something I haven't covered,
| **iGPU** | AMD Radeon 890M |
| **dGPU** | NVIDIA GeForce RTX 4060 Laptop (Max-Q) |
| **OS** | CachyOS (Arch) |
| **Kernel** | 6.19.3-2 |
| **Kernel** | 6.19.4-2 |
| **Display Server** | Wayland (GNOME 49) |
| **Secure Boot** | Enabled |

Expand Down
2 changes: 1 addition & 1 deletion content/docs/getting-started.nl.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Als iets hier je helpt: mooi. Loop je ergens tegenaan wat ik niet behandeld heb,
| **iGPU** | AMD Radeon 890M |
| **dGPU** | NVIDIA GeForce RTX 4060 Laptop (Max-Q) |
| **OS** | CachyOS (Arch) |
| **Kernel** | 6.19.3-2 |
| **Kernel** | 6.19.4-2 |
| **Display Server** | Wayland (GNOME 49) |
| **Secure Boot** | Ingeschakeld |

Expand Down
2 changes: 1 addition & 1 deletion content/docs/hardware/asusctl-rog-control.md
Original file line number Diff line number Diff line change
Expand Up @@ -298,7 +298,7 @@ Known issues and troubleshooting for asusctl & ROG Control Center are documented

### Kernel 6.19: asus-armoury driver lands in mainline

The `asus-armoury` driver has been [merged into Linux 6.19](https://www.phoronix.com/news/ASUS-Armoury-Driver-Linux-6.19). This new `platform/x86` driver replaces parts of the older `asus-wmi` with a cleaner sysfs-based API, enabling panel mode switching, APU memory allocation, PPT tuning, and more directly from the kernel. The driver is entirely community-developed by the [asus-linux team](https://asus-linux.org/), with no involvement from ASUS themselves. CachyOS ships kernel 6.19.3-2 which includes this driver and additional ASUS-specific patches.
The `asus-armoury` driver has been [merged into Linux 6.19](https://www.phoronix.com/news/ASUS-Armoury-Driver-Linux-6.19). This new `platform/x86` driver replaces parts of the older `asus-wmi` with a cleaner sysfs-based API, enabling panel mode switching, APU memory allocation, PPT tuning, and more directly from the kernel. The driver is entirely community-developed by the [asus-linux team](https://asus-linux.org/), with no involvement from ASUS themselves. CachyOS ships kernel 6.19.4-2 which includes this driver and additional ASUS-specific patches.

**Before**: basic asusctl controls without Armoury settings:

Expand Down
2 changes: 1 addition & 1 deletion content/docs/hardware/asusctl-rog-control.nl.md
Original file line number Diff line number Diff line change
Expand Up @@ -298,7 +298,7 @@ Bekende problemen en probleemoplossing voor asusctl & ROG Control Center staan o

### Kernel 6.19: asus-armoury driver in mainline Linux

De `asus-armoury` driver is [gemerged in Linux 6.19](https://www.phoronix.com/news/ASUS-Armoury-Driver-Linux-6.19). Deze nieuwe `platform/x86` driver vervangt delen van de oudere `asus-wmi` met een schonere sysfs-gebaseerde API, waarmee o.a. paneel modus wisselen, APU geheugentoewijzing, PPT tuning en meer mogelijk wordt direct vanuit de kernel. De driver is volledig door de community ontwikkeld door het [asus-linux team](https://asus-linux.org/), zonder enige betrokkenheid van ASUS zelf. CachyOS levert kernel 6.19.3-2, inclusief deze driver en aanvullende ASUS-specifieke patches.
De `asus-armoury` driver is [gemerged in Linux 6.19](https://www.phoronix.com/news/ASUS-Armoury-Driver-Linux-6.19). Deze nieuwe `platform/x86` driver vervangt delen van de oudere `asus-wmi` met een schonere sysfs-gebaseerde API, waarmee o.a. paneel modus wisselen, APU geheugentoewijzing, PPT tuning en meer mogelijk wordt direct vanuit de kernel. De driver is volledig door de community ontwikkeld door het [asus-linux team](https://asus-linux.org/), zonder enige betrokkenheid van ASUS zelf. CachyOS levert kernel 6.19.4-2, inclusief deze driver en aanvullende ASUS-specifieke patches.

**Voor**: basale asusctl-bediening zonder Armoury-instellingen:

Expand Down
30 changes: 28 additions & 2 deletions content/docs/known-issues.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,39 @@
---
title: "Known Issues"
weight: 7
prev: docs/virtualization/looking-glass-attempt
prev: docs/virtualization/winboat
---

Central reference for hardware and software issues on the ASUS ROG Zephyrus G16 GA605WV. Active issues are listed first. Resolved issues are kept as reference at the bottom.

## Active Issues

### WinBoat: container fails to start

**What's happening:**
WinBoat regularly gets stuck in an endless startup loop. The Podman container keeps trying to start but never succeeds — even after waiting indefinitely. The UI shows "WinBoat Guest API - Offline" and "Container - Exited". This is not limited to the first install — it happens on subsequent starts as well.

**Workaround:**
Resetting WinBoat and going through the initial configuration again gets it running again. This is not a sustainable fix.

**Status:**
Open. WinBoat is in beta and the project acknowledges instability. See the [WinBoat page]({{< relref "/docs/virtualization/winboat" >}}) for more context.

---

### WinBoat: application windows drift and shrink randomly

**What's happening:**
When WinBoat does start successfully and a Windows application (such as Microsoft Word) is opened, the window behaves erratically: it drifts to the right across the screen, scales down randomly, and keeps getting smaller until it is barely visible. This makes WinBoat effectively unusable for productivity applications.

**Workaround:**
None found. Restarting the application or WinBoat does not reliably fix it.

**Status:**
Open. Beta limitation.

---

### Brave Browser: touchpad scrolling too fast on Wayland

**What's happening:**
Expand Down Expand Up @@ -354,7 +380,7 @@ This issue has since resolved itself. Steam now launches normally; the `__GL_CON
ROG Control Center shows a warning that the `asus-armoury` kernel driver is not loaded. Some advanced features (PPT power limits, APU memory allocation, MUX switch control) are unavailable.

**Cause:**
The `asus-armoury` driver was merged into the Linux mainline kernel in version 6.19. CachyOS ships kernel 6.19.3-2 which includes this driver, so it should be available.
The `asus-armoury` driver was merged into the Linux mainline kernel in version 6.19. CachyOS ships kernel 6.19.4-2 which includes this driver, so it should be available.

**Fix:**
Verify the driver is loaded:
Expand Down
30 changes: 28 additions & 2 deletions content/docs/known-issues.nl.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,39 @@
---
title: "Bekende Problemen"
weight: 7
prev: docs/virtualization/looking-glass-attempt
prev: docs/virtualization/winboat
---

Centrale referentie voor hardware- en softwareproblemen op de ASUS ROG Zephyrus G16 GA605WV. Actieve problemen staan bovenaan. Opgeloste problemen staan onderaan als naslagwerk.

## Actieve Problemen

### WinBoat: container start niet op

**Wat er gebeurt:**
WinBoat raakt regelmatig verstrikt in een eindeloze opstartronde. De Podman-container blijft proberen op te starten maar slaagt daar nooit in — ook niet na eindeloos wachten. De UI toont "WinBoat Guest API - Offline" en "Container - Exited". Dit is niet beperkt tot de eerste installatie — het treedt ook op bij latere starts.

**Workaround:**
WinBoat resetten en de initiële configuratie opnieuw doorlopen zorgt dat het weer werkt. Dit is geen duurzame oplossing.

**Status:**
Open. WinBoat is in beta en het project erkent de instabiliteit. Zie de [WinBoat-pagina]({{< relref "/docs/virtualization/winboat" >}}) voor meer context.

---

### WinBoat: applicatievensters verschuiven en krimpen willekeurig

**Wat er gebeurt:**
Wanneer WinBoat wel succesvol start en een Windows-applicatie (zoals Microsoft Word) wordt geopend, gedraagt het venster zich grillig: het schuift naar rechts over het scherm, schaalt willekeurig kleiner, en wordt steeds kleiner totdat het nauwelijks nog zichtbaar is. Dit maakt WinBoat in de praktijk onbruikbaar voor productiviteitsapplicaties.

**Workaround:**
Geen gevonden. De applicatie of WinBoat herstarten lost het niet betrouwbaar op.

**Status:**
Open. Beta-beperking.

---

### Brave Browser: touchpad scrollt te snel op Wayland

**Wat er gebeurt:**
Expand Down Expand Up @@ -354,7 +380,7 @@ Dit probleem heeft zichzelf opgelost. Steam start nu gewoon op; de `__GL_CONSTAN
ROG Control Center toont een melding dat de `asus-armoury` kerneldriver niet is geladen. Geavanceerde functies (PPT-vermogensgrenzen, APU-geheugenallocatie, MUX-switchbesturing) zijn niet beschikbaar.

**Oorzaak:**
De `asus-armoury`-driver is samengevoegd in de Linux mainline-kernel in versie 6.19. CachyOS levert kernel 6.19.3-2 inclusief deze driver, dus hij zou beschikbaar moeten zijn.
De `asus-armoury`-driver is samengevoegd in de Linux mainline-kernel in versie 6.19. CachyOS levert kernel 6.19.4-2 inclusief deze driver, dus hij zou beschikbaar moeten zijn.

**Fix:**
Verifieer dat de driver is geladen:
Expand Down
2 changes: 1 addition & 1 deletion content/docs/virtualization/looking-glass-attempt.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Looking Glass B7: GPU Passthrough Attempt"
weight: 2
next: docs/known-issues
next: docs/virtualization/winboat
---

I wanted to try GPU passthrough with Looking Glass: running Windows in a VM but with the real NVIDIA GPU assigned to it, getting near-native performance. Spent a good few hours on it. It doesn't work on this laptop, and the reason is a hardware limitation that Looking Glass can't work around. I'm documenting the full attempt here so others can save themselves the time.
Expand Down
2 changes: 1 addition & 1 deletion content/docs/virtualization/looking-glass-attempt.nl.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Looking Glass B7: GPU Passthrough Poging"
weight: 2
next: docs/known-issues
next: docs/virtualization/winboat
---

Ik wilde GPU passthrough proberen met Looking Glass: Windows in een VM draaien maar met de echte NVIDIA GPU toegewezen, zodat je near-native performance hebt. Ik heb er een flink aantal uren aan besteed. Het werkt niet op deze laptop, en de reden is een hardwarebeperking waar Looking Glass niets aan kan doen. Ik documenteer de volledige poging hier zodat anderen die tijd kunnen besparen.
Expand Down
90 changes: 90 additions & 0 deletions content/docs/virtualization/winboat.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
---
title: "WinBoat: Windows via Podman Container"
weight: 3
next: docs/known-issues
---

WinBoat is an open-source project that runs Windows inside a Podman container on Linux. The goal is to have Windows applications show up as regular windows on your Linux desktop, without needing a full VM. I tested it using Podman.

> **Status: Beta.** WinBoat is in early beta. Tested on v0.9.0. Bugs are expected and the project says so itself.

![WinBoat feature overview from the project website](/images/winboat-features.avif)


## Installation

I got WinBoat from the CachyOS package repository:

```bash
sudo pacman -S winboat
```

Package source: [packages.cachyos.org — winboat](https://packages.cachyos.org/package/cachyos/x86_64/winboat)

The WinBoat website also lists an AUR package (`winboat-bin`) for other Arch-based distros. On CachyOS, the repo package is simpler.

![WinBoat download page showing Arch/AUR install options](/images/winboat-download.avif)


## Setup

When you first run WinBoat, it walks you through a setup wizard: install location, user credentials for the Windows account, and hardware allocation (CPU cores, RAM, disk size). From there it downloads and installs Windows 11 automatically through Podman. The install takes a while; you can follow the progress in your browser. The port can change between runs, so use this to get the current URL:

```bash
# Podman
podman port WinBoat | grep "8006" | awk '{print "http://" $3}'
# Docker
docker port WinBoat | grep "8006" | awk '{print "http://" $3}'
```

The demo below covers a full session: wizard, installation in progress, WinBoat coming up with Windows actually running, and then my attempts to open Notepad and File Explorer.

![WinBoat setup and first session — from wizard to Windows running, then the startup loop](/images/winboat-demo.avif)

After a clean setup, WinBoat does start. **WinBoat Guest API - Online** and **Container - Running** showed up in the interface, the Windows apps screen loaded, and a Windows 11 login screen appeared in the browser via FreeRDP. That part worked.

The problem is getting back to that state reliably without going through the full setup again.

## First launch

After installing, you can start WinBoat from the app menu or terminal. On first run it sets up a Windows 11 install through Podman automatically.

![WinBoat app — home screen with container status](/images/winboat-app.avif)

What I ran into most often: **WinBoat Guest API - Offline** and **Container - Exited**. Windows 11 Pro shows up in the interface but the container never reaches a running state.


## Bugs

The main issue: WinBoat gets stuck in a startup loop. The Podman container keeps trying to start but never gets there, no matter how long you wait. This happens regularly, not just on first setup.

Resetting WinBoat and going through the full setup again does get it running, but having to wipe and redo the setup every time is not a workable solution.

![WinBoat stuck in an endless startup loop — never reaches a running state](/images/winboat-startup-failure.avif)

Other things I ran into:

- The container exits unexpectedly ("Container - Exited")
- The Guest API never connects ("WinBoat Guest API - Offline")
- Windows apps don't reliably appear as windows on the desktop

When WinBoat does start, I tried something simple first: opening Notepad and File Explorer. I hadn't installed Microsoft 365 yet via `winget`, so I started small. Instead of those apps, I got weird boxes and glitches on screen. I rebooted the container and killed some processes, but that didn't help either. You can see this in the demo above.

{{< callout type="warning" >}}
WinBoat is in early beta. The project itself warns that users should be comfortable with troubleshooting. The current version is not representative of the final product.
{{< /callout >}}


## So, what now?

Honestly, this is one of the coolest app concepts I've seen in a while. Running Windows apps as regular desktop windows without a full VM is something Bottles and Wine can't do either, especially for Microsoft 365. I'd love to get this working properly.

But we're not there yet. For now the [KVM/QEMU VM setup]({{< relref "/docs/virtualization/vm-setup" >}}) with VirtIO and SPICE GL is still the more reliable option on this laptop. I'm hoping the next release addresses these kinds of issues. I'd like to give it another shot when it's more stable.


## References

- [WinBoat — Official website](https://winboat.app)
- [WinBoat — GitHub (TibixDev/winboat)](https://github.com/TibixDev/winboat)
- [WinBoat — CachyOS package](https://packages.cachyos.org/package/cachyos/x86_64/winboat)
- [WinBoat — AUR package (winboat-bin)](https://aur.archlinux.org/packages/winboat-bin)
Loading
Loading