I don’t think I’ve ever had the issue with my FW13. 
does anyone have udev rules for interacting with the led matrix? i was able to use the qmk rules in order to get access to the keyboard and numpad
So far, so good. I was able to install Hyperland (Wayland wm).
The only gotcha is that I did enable “game” mode in the bios setting for embedded GPU. I’m using two 4K monitors, and default 0.5GB VRAM is not enough for that 
P.S. I did not encounter any framework-specific issues, only Wayland’s issues 
1 Like
Update: This is an issue with Hyperland. It is working fine using Sway.
Did anyone experience video stuttering issues while using Firefox on an integrated GPU?
I’m using Wayland session with a dual 4K monitor setup. The Integrated GPU has 4GB of memory. My total system memory is 64GB.
Firefox commands (integrated GPU):
MOZ_ENABLE_WAYLAND=1 MOZ_DRM_DEVICE=/dev/dri/renderD128 firefox
Firefox command (7700S):
MOZ_ENABLE_WAYLAND=1 MOZ_DRM_DEVICE=/dev/dri/renderD129 firefox
1 Like
Wanted to first say, welcome Arch users!
Please, please do what you can to help the Arch community by populating the wiki (using Arch contribution rules of course).
If you have a useful tip, please see about getting it shared there as well,.
9 Likes
You shouldn’t need this anymore. Wayland was enabled by default in Firefox as of a few weeks or so ago.
1 Like
The Firefox did not use hardware acceleration otherwise 
But it is an issue with Hyperland.
I switched to “sway”, and it works fine. The current version of Hyperland has performance issues. My GPU load is 25% idle, causing Framework to run with 50-55C temps And the steam client doesn’t like it (too many bugs and glitches)
Maybe related to: GPU spikes after enable/disable `mouse_move_enables_dpms` · Issue #4670 · hyprwm/Hyprland · GitHub
P.S. The sway is stable so far.
Just got my FW 16, I needed to disable secure boot in order to use my migrated SSD, but other than that I’ve had no immediate issues.
1 Like
Update: It would appear that 0% backlight translates into a very visible image on the screen. I’m not sure if this is working as intended and is some sort of hardware limitation for how low the display can go, but my other laptops basically turn off at 0% (granted the pixels are still updating). It could also be due to technology differences with IPS panels, or a software glitch on my install, I’m really not sure. Just something to be aware of.
I’m on KDE Plasma and using their built in brightness management.
1 Like
Turning off at 0% is actually the wrong functionality. It is a bug in certain graphics modules:
https://bugs.kde.org/show_bug.cgi?id=430439
Oh now that’s interesting. This is the same install/SSD as the one that exhibited that behavior on my Thinkpad, so I wonder why the behavior was different. Oh well, it gets dim enough so I guess it’s a non-issue. Just odd.
Replying here so I remember to come back for useful tips and get updates :3
Thanks everyone!
I have the same question. I haven’t been able to get the ledmatrix.frame.work tool to work, presumably due to this.
Has anybody else seen weird behavior with the numpad and a yubikey? For some reason whenever I plug in my yubikey, the enter key and the + key on the numpad start to behave as if numlock is turned off. For those who don’t know, when numlock is off, + and enter are used to cycle the backlight states. This is becoming really annoying because whenever I plugin the yubikey, I usually need to enter a pin with it, but instead of the enter key submitting the pin, it just starts cycling the backlight. I can fix it by turning numlock off and then back on again, but I’d like to know if I need to add some kind of qmk config to fix this? Is this a firmware bug in the numpad? It only happens when I plugin a yubikey, not any other kind of usb device, though I’ve only tried a flashdrive. It also doesn’t matter which side I plug it into. I have 2 usb A modules, one on either side.
I think I may have figured out part of the problem. I was watching the journal logs and noticed that the yubikey was being detected like a keyboard, which makes sense because it does emulate a keyboard to enter a one time password. After I saw that, I tried plugging in another keyboard and it did the same thing the yubikey did, but the main difference is that the keyboard has a numlock LED. When I first plugged in the external keyboard, the numlock LED was on, but the enter key on the framework numpad was still cycling the backlight. If I cycle the numlock off and then back on again, the framework numpad starts behaving normally again. I don’t know if its the operating system or the numpad firmware that controls the behavior of the numpad. I still haven’t tried any QMK configuration, so maybe it can be fixed with that? I’m using KDE with a setting to turn numpad on when I login, but I don’t think it should change the keyboard behavior when a keyboard is plugged in.
1 Like
Anyone running Xorg still?
I’m having issues with my xorg.conf and I was wondering if anyone had a working one.
Trying to set up bspwm and it’s been a long time since I’ve done the initial Xorg setup.
My Xorg file generated with like 5 monitors and screens and when I try to open up a terminal or something it doesn’t show. I’m thinking maybe it’s hidden on a different ‘monitor/screen’ somewhere.
I think it might be something driver related. Xorg has a handful of lines saying
`AMDGPU(#): [KMS] Kernel modesetting enabled’
@Shahan_Studios I’m not running xorg anymore, but when I was I gave up on making my own config. I just deleted the config and let it auto configure. Have you tried that?
Note: renaming the config also works, and is safer.
Arch is running pretty smooth. Even fractional scaling on Wayland works fine.
Noticed only some minor things:
- Wifi throughput seems too low: although connection reports >1 gig link, e.g. Steam only reaches ~160 mbps when using local file transfer via 1gig / 10gig LAN backbone
- Firefox seems to randomly pick iGPU / dGPU (may also depende on power power profile or if on battery / AC power, need to observe it more)
- VRR is not reported correctly. See [ANNOUNCEMENT] Adaptive Sync / Freesync / VRR not working - #3 by Matt_Hartley
- PPD profile switching required custom udev rules. I’m guessing these are already present on Ubuntu and Fedora ?
EDIT:
Regarding harware monitoring:
- lm_sensors did not detect any sensor, but using ACPI fallback mostly works for temperatures
- CPU fan is not reported in ACPI “sensor”
- dGPU Fanspeed is not reported by amdgpu correctly: it is always 0 rpm, even in games
3 Likes
Letting Xorg auto configure worked. Thanks!
It was probably working before I thought it was broken and messed with it.
I tried using the conf generated by X -configure and that’s what gave me the multiple monitor / screens issue. 
1 Like