Arch Linux on the Framework Laptop 16

Framework Laptop 16 Linux
25

I think it might be something driver related. Xorg has a handful of lines saying
`AMDGPU(#): [KMS] Kernel modesetting enabled’

26

@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.

27

Arch is running pretty smooth. Even fractional scaling on Wayland works fine.

Noticed only some minor things:

  1. 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
  2. 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)
  3. VRR is not reported correctly. See [ANNOUNCEMENT] Adaptive Sync / Freesync / VRR not working - #3 by Matt_Hartley
  4. PPD profile switching required custom udev rules. I’m guessing these are already present on Ubuntu and Fedora ?

EDIT:
Regarding harware monitoring:

  1. lm_sensors did not detect any sensor, but using ACPI fallback mostly works for temperatures
  2. CPU fan is not reported in ACPI “sensor”
  3. dGPU Fanspeed is not reported by amdgpu correctly: it is always 0 rpm, even in games
3 Likes
28

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. :man_shrugging:

1 Like
29

Anyone else experiencing their WiFi cutting out occasionally?

30

The command that worked for me was this:

sudo usermod -a -G uucp $(whoami)

Followed by a reboot. Logging out might work too, and hopefully someone sharper than I am will come along and enlighten us all on how to effect this without needing to reboot or logout. I tried running

newgrp uucp

but was still unable to connect. After rebooting (and having a moment when on first boot
/boot/efi was not found, but it worked on a subsequent reboot), I am able to connect to the LED spacers.

I hope this helps.Have a great day!

Edit to add tagging @DRACONIUM

Edited again to note - updating the fstab to use the uuid for the /boot/efi partition rather than /dev/nvme1n1p1 seems to have resolved things, Noted for future setups. This may be obvious to more savvy users, and something in the back of my mind is saying that I have run across it previously, but this time I wrote it down. Maybe one day when I grow up I can be a real boy.

1 Like
31

This sadly didn’t work for me, but I’m actually running Bluefin. I hope this works for the Arch users here though!

32

Try using group dialout rather than uucp. It looks like that might be the one that you need.

33

I must be having a “skill issue”. I’ve done sudo usermod -aG dialout $(whoami), and, even after rebooting, the groups command does not show me as a member of the dialout group :confused:

34

My apologies, I didn’t dig in on that distro. It looks like it’s an offshoot (or whatever one wishes to call it) of silverblue. Duckduckgo came up with this, it may help: Troubleshooting :: Fedora Docs

Best of luck!

1 Like
35

i was on the discord a while back and was actually pointed to the udev rules i was talking about, let me see if i can dig it up again, it’s on framework’s github somewhere.

1 Like
36
2 Likes
37

Mine will take a bit to come up after a boot, but it does come up, I’ve tried looking at the logs, but didn’t necessarily see anything out of the ordinary aside from the interface changing names (sometimes it’s wlp5s0 and other times it’s wlp2s0 though I’m suspecting that’s actually with and without the GPU module installed)

38

Thanks, now I am able to run the commands to change and update the led spacers without needing to use sudo. I currently have it showing the clock, but am thinking about doing something to get the current outside temperature and display that. Lots of ideas, little skill, sigh.

1 Like
39

I haven’t tried without the gpu yet. Mine might have been IPv6 related. I forced the network to use IPv4 and haven’t seen a drop yet.

40

Don’t you need $user$ instead of (whoami)?
I can’t remember off hand if you need the brackets.

41

the $() bit is basically interpolating in the value of the whoami command, which just spits our your username

42

also, has anyone had any issues with video playback occasionally freezing and stuttering (getting stuck on one frame for a few seconds) while the audio keeps playing? seems to happen with youtube for me occassionally

43

Awesome! This works for me as well on Bluefin. Thanks for finding this!!

1 Like
44

I’ll still see it not come up immediately on boot regardless of whether or not the GPU is installed. I’m just suspecting that the wlan0 interface renaming to wlp5s0 or wlp2s0 is impacted by the hardware configuration, and isn’t really a part of my issues not seeing the interface come up immediately on boot. I’m not an expert at reading those logs though.