Fwiw, WiFi works fine for me in 5.13 for me (on Arch, not Fedora). Bluetooth doesn’t.
I am on Fedora 34 with kernel 5.13.4; wifi and bluetooth both work for me.
$ uname -r
5.13.4-200.fc34.x86_64
$ lshw -C net
WARNING: you should run this program as super-user.
*-network
description: Wireless interface
product: Wi-Fi 6 AX210/AX211/AX411 160MH
1 Like
@nrp Same behavior on ubuntu 21.04 (I’m currently using the KDE respin for Fedora 34), I can follow-up on the support email I sent with the images of the microphone/bezel that were requested. Sorry all for the unrelated noise on the thread!
1 Like
I’m not brave enough to try running 5.13 but from what I’ve read on some of the links discussing the regression, wifi does work on 5.13, and bluetooth reports that the modules are loaded on 5.13 but no hardware actually exists when you try to connect devices.
1 Like
It sounds like bluetooth support might have regressed between 5.13.4 and 5.13.6? I am able to add/remove/use a bluetooth mouse without any problems. I might have to try the .6 release later and see what happens…
2 Likes
Okay, here’s where I found it: @mbernhard posted a link in Linux users: Use kernel >=5.13.10 to avoid WFi/BT issues - #3 by mbernhard to Bluetooth via AX210 fails with Linux 5.13.4-1, but works with 5.12.19-1 - Support - Manjaro Linux Forum where the OP there posts that bluetooth didn’t work using Manjaro Linux Pahvo 21.1.0 (stable) but didn’t mention what kernel version this uses (beyond 5.13).
For the touchpad libinput bug, I just filed the following issue ticket on Fedora Bugzilla to ask to apply a patch of the upstream commit to the Fedora 34 libinput RPM. I updated this thread’s wiki too.
Framework laptop: touchpad right-click doesn’t work
https://bugzilla.redhat.com/show_bug.cgi?id=1989738
1 Like
Hey guys, do any of you guys have any idea about what to do when updating fedora? Currently on 5.13.5 and I tried updating to 5.13.6 from gnome software as well as from my terminal just for both to give me a boot error of “systelctl status initrd-switch-root.service” ( initrd-switch-root.service failing). I look up the issue online but there are different options to try and the two that I tried didnt work. Do you guys have any idea? It seems people have this issue with Fedora when updating. Currently, I’m back on my 5.13.5 install but my grub still has the two installs that don’t work.
I’m also having moments where I’ll restart my computer and use it for a while and then everything gets really slow, and when I’ll suspend my computer my closing the lid and then reopening it causing everything to be slow and it’ll say my CPU usage is high. Any ideas about that?
EDIT: Like right now after just browsing the internet, listening to Spotify, and in a call on discord, my OS just decides to slow down and all everything gets super slow. I’m not even doing anything super intensive, and I can’t even see what is using all of my CPU or whats causing me to throttle. I just restarted and after a couple of minutes of a slow install (which normally doesn’t happen) it went somewhat back to normal. A couple of animations are still slow and all.
Hi folks, I’m struggling to get the fingerprint reader working on Fedora 34. I got all hardware working 100% on Ubuntu 21.04 yesterday, but decided to switch to Fedora 34 due to the much better trackpad gesture support (3-finger desktop switching was a must for me!).
As recommended, I installed from the latest respin of Fedora 34. I’ve got libfprint-1.90.7-3.fc34.x86_64 installed, but every time I try to enroll a fingerprint, I immediately get an error and it gives up. Some reading on fprintd suggests this is usually a driver error. Here’s what the error looks like:
[sawaba@fedora ~]$ fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-unknown-error
Is that the right device?
I can’t find anything in /var/log that gives any more details and all my Googling hasn’t revealed anything useful. I also tried pulling from the Fedora 35 repo, but it just gives me the same version of libfprint that seems to be working for everyone else…
1 Like
There is Ubuntu thread, and others, suggesting that libfprint must be version 1.92 1 for the fingerprint sensor to work.
I haven’t managed to get a successful compile yet, always some package not found.
@Edward_Gray you shouldn’t need to compile, you can just install from rawhide: Community reviews - #9 by Michael_Lingelbach
1 Like
I’m currently running Fedora 34 on my Framework and fprintd worked out of the box.
Here is further information, if curious:
CPU: Quad Core 11th Gen Intel Core i7-1185G7 (-MT MCP-) speed/min/max: 1242/400/4800 MHz Kernel: 5.13.7-200.fc34.x86_64 x86_64
Up: 55m Mem: 4624.4/31880.5 MiB (14.5%) Storage: 3.64 TiB (19.4% used) Procs: 347 Shell: Zsh inxi: 3.3.06
It is suggested above to follow the procedure for Ubuntu (Ubuntu 21.04 on the Framework Laptop - #8 by jeshikat), but that says to run the command sudo update-grub, which doesn’t seem to exist in Fedora. This page, Equivalent of update-grub for RHEL/Fedora/CentOS systems? - Unix & Linux Stack Exchange, has an answer that says that the Fedora 33 guide says to run sudo grub2-mkconfig --output=/boot/grub2/grub.cfg. Does that seem right for Fedora 34? The current guide GRUB 2 - Fedora Project Wiki seems to confirm this, but I’m still a little confused.
And now that I look at that page more, I wonder if the correct advice might be to use grubby, per GRUB 2 - Fedora Project Wiki. However, looking at the grubby man page leaves me as confused as ever. Not being intimately familiar with the various parts of the Grub2 subsystem, I’m not clear what options in grubby would accomplish changing the setting.
I finally did the following, and it seems to have worked, as shown:
Before configuring /etc/default/grub to enable deep sleep:
[jeremy@fedora ~]$ cat /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rhgb quiet"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
[jeremy@fedora ~]$
After configuring /etc/default/grub to enable deep sleep::
[jeremy@fedora ~]$ cat /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rhgb quiet mem_sleep_default=deep"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
[jeremy@fedora ~]$
Running the script to invoke the grub incantation:
[root@fwfedora ~]# cat /sys/power/mem_sleep
[s2idle] deep
[root@fwfedora ~]# cat doit.sh
grub2-mkconfig -o /etc/grub2.cfg
grub2-mkconfig -o /etc/grub2-efi.cfg
[root@fwfedora ~]# . doit.sh
Generating grub configuration file ...
Adding boot menu entry for UEFI Firmware Settings ...
done
Generating grub configuration file ...
Adding boot menu entry for UEFI Firmware Settings ...
done
[root@fwfedora ~]# ls -l /etc/grub2.cfg /etc/grub2-efi.cfg
lrwxrwxrwx. 1 root root 22 Jun 15 11:41 /etc/grub2.cfg -> ../boot/grub2/grub.cfg
lrwxrwxrwx. 1 root root 22 Jun 15 11:41 /etc/grub2-efi.cfg -> ../boot/grub2/grub.cfg
[root@fwfedora ~]# diff /etc/grub2.cfg /etc/grub2-efi.cfg
[root@fwfedora ~]#
(reboot)
[root@fwfedora ~]# cat /sys/power/mem_sleep
s2idle [deep]
[root@fwfedora ~]#
6 Likes
@Jeremy_Schneider before you dive too deep into grub, if you haven’t checked to see whether you need to, you can run this command:
cat /sys/power/mem_sleep
If the result is [s2idle] deep, you don’t need to mess with grub to enable deep sleep, it’s already enabled.
I was deep into troubleshooting on my Fedora 34 system before realizing it was already enabled for me. Also worth mentioning - I installed Fedora 34 using the respin from August 2nd, which reportedly already had a lot of this stuff fixed.
2 Likes
@Alex_S The only difference here is that I’ve got the i7 chip just below yours - the i7-1165G7. I can’t imagine how that would make a difference though - the fingerprint reader isn’t part of the Intel chipset…
@Adrian_Sanabria Thank you. It is indeed already set. I used to be very grub-literate in my Gentoo days ;-).
[jeremy@fwfedora ~]$ cat /sys/power/mem_sleep
[s2idle] deep
[jeremy@fwfedora ~]$
Oh, by the way, I also installed from a respin – maybe that’s why I have it.
My battery seems to drain unreasonably fast when the machine is asleep – not like my Google Pixelbook – I can close it and return days later to a machine at practically the same charge level.
I’m looking forward to enhancements in the access to the firmware charging limits and other battery-related customizations.
@Jeremy_Schneider Same! I remember the days when I had the time and patience to do Stage 1 Gentoo installs 
Yes, one of the main reason to use the Fedora respins is that the Framework folks got them to include some of these fixes!
And I’m sure they’ll get us some good firmware updates that fix some of these issues, though overall, I’m pretty happy.
The output is saying that it’s not set. You want “deep” to be selected. But s2idle is.
1 Like