Skip to main content

Fedora Proart Tips

I’ve been a Linux user for a long time, and historically my comfort zone has been “hands-on” distributions: Slackware, Gentoo, Debian, Arch Linux.

I also virtualize heavily. I started back in the day with OpenVZ, then moved to VMware Workstation… until I got fed up with the constant “you must patch your kernel” routine to keep things working smoothly.

Recently I got an Asus ProArt P16 (AMD Ryzen 9 + NVIDIA GPU). Great machine—until I tried to install my usual favorite Linux distributions.

To my surprise, none of them handled the hardware properly (or at least not enough to reliably use the laptop day-to-day). I then tried Fedora 43, and it immediately handled the basics out of the box — the minimum needed to actually use the system.

After a bit more digging, I realized I needed to explicitly enable the NVIDIA dGPU. The fix was simple once you know it:

supergfxctl --mode Hybrid

Then came the “random Google search” moment: I searched for a Fedora derivative that would handle the Asus ProArt P16 well, and the recommendation that kept appearing was Bazzite — which I had never even heard of.

So I installed Bazzite… and honestly, it was a pleasant surprise:

  • Everything hardware-wise worked out of the box
  • The only thing not perfectly supported (for now) is the touchpad corner slide gesture to enable the touchpad bezel — which I can live with

The biggest change for me: Bazzite is an OSTree-based system, so it forced me to learn a different way of managing the OS. It feels like starting from zero compared to the classic “mutable distro” workflow.

But here’s the part that really matched my needs as a virtualization-heavy user: enabling KVM/QEMU with a good setup was basically trivial. For virt-manager, it boiled down to running:

  • ujust setup-virtualization (once to enable it)
  • ujust setup-virtualization again (to set up USB passthrough)

That’s it.

So, conclusion: if you have an Asus ProArt P16, I strongly recommend Bazzite. I’ve also heard good things about CachyOS, but after the time I already spent experimenting, I can’t afford another round right now. I need to focus on work—and maybe in 3–6 months I’ll give CachyOS a try.

If anyone else is running Linux on the ProArt P16, I’d love to compare notes (especially around NVIDIA + power management + ergonomics).

Popular posts from this blog

Undefined global vim

Defining vim as global outside of Neovim When developing plugins for Neovim, particularly in Lua, developers often encounter the "Undefined global vim" warning. This warning can be a nuisance and disrupt the development workflow. However, there is a straightforward solution to this problem by configuring the Lua Language Server Protocol (LSP) to recognize 'vim' as a global variable. Getting "Undefined global vim" warning when developing Neovim plugin While developing Neovim plugins using Lua, the Lua language server might not recognize the 'vim' namespace by default. This leads to warnings about 'vim' being an undefined global variable. These warnings are not just annoying but can also clutter the development environment with unnecessary alerts, potentially hiding other important warnings or errors. Defining vim as global in Lua LSP configuration to get rid of the warning To resolve the "Undefined global vi...

wget maven ntlm proxy

How to make wget, curl and Maven download behind an NTLM Proxy Working on CentOS, behind an NTLM proxy: yum can deal without problem with a NTLM Proxy wget, curl and Maven cannot The solution is to use " cntlm ". " cntlm " is a NTLM client for proxies requiring NTLM authentication. How it works Install "cntlm" Configure "cntlm"  by giving it your credentials by giving it the NTLM Proxy Start "cntlm" deamon (it listens to "127.0.0.1:3128") Configure wget, curl and Maven to use "cntlm" instead of using directly the NTLM Proxy Note: You will have then a kind of 2 stages Proxy : cntlm + the NTLM proxy Configure CNTLM After installing cntlm, the configuration file is in "cntlm.conf". You must have your domain (in the Windows meaning), proxy login and  proxy password. Mine are respectively: rktmb.org, mihamina, 1234abcd (yes, just for the example) You must have you NTLM Proxy Hostnama or IP ...

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo...