@junaruga I believe the issues in that thread are unrelated to the issue that I am experiencing. I am currently running 5.14.12-200.fc34.x86_64 but I have seen the problem on multiple kernel versions. I’m not sure how to format the information below as a table but it is the kernel version, the firmware version, and the number of firmware crashes/resets I had.
Linux 5.13.4-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 10 crashes
Linux 5.13.6-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 4 crashes
Linux 5.13.7-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 32 crashes
Linux 5.13.10-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 2 crashes
Linux 5.13.12-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 2 crashes
Linux 5.13.13-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 9 crashes
Linux 5.13.14-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 7 crashes
Linux 5.13.16-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 6 crashes
Linux 5.13.19-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 13 crashes
Linux 5.14.9-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 2 crashes
Linux 5.14.10-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 3 crashes
Linux 5.14.11-200.fc34.x86_64 : 63.c04f3485.0 ty-a0-gf-a0-63.ucode : 5 crashes
@junaruga I opened BZ#1991752 back in August but it hasn’t seen any movement yet. That’s why I figured I would post here to see if anyone else has had similar issues or not.
OK. I emailed the Bugzilla ticket URL and this thread’s URL to a person I know who tested Framework Laptop on Fedora in the past. It might also be a good idea to ping on the Bugzilla ticket. Because I see there are many “NEW” state tickets for the kernel RPM. The maintainers might miss it. It might also be a good idea to email on the Fedora kernel group’s mailing list if you like.
@Kevin_Anderson Yes and it’s easily and reliably reproducible with iperf and a rescan. I opened a bug report for iwlwifi. Hoping that maybe once Kernel 5.15 is out and the new firmware is usable that it will be resolved, but not holding my breath.
Interesting… reboots were still resulting in no bluetooth controllers found for me on Arch/5.14.14 yesterday. Updated to 5.14.15 today (via pacman), still no dice. Cold boots are still working fine.
After updating to the latest 5.14.16 kernel on Arch, bluetooth stopped working after both cold and warm boots. Rolling back to 5.14.15 at least got me functioning bluetooth again after a cold boot.
This is out of the box running Pop OS Non-LTS, but I did actually upgrade to the beta version released a few days ago to see if it would fix the fingerprint reader (it did).
I can consistently get about 450Mbps up and down for speed test services hosted in Japan. My Macbook Pro seems to get slower (like 230) on average, but occasionally over 500.
Certainly more than 15 anyway.
(My connection is supposedly 2Gbps, but no WiFi can handle that…)
Oh, bluetooth is working in the sense that devices show up in a bluetooth scan, but I haven’t had the desire to actually pair anything yet.
shiruba@framework:~$ uname -a
Linux framework 5.13.0-7620-generic #20~1634827117~21.10~874b071 SMP Thu Oct 21 16:32:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
shiruba@framework:~$ cat /etc/os-release
NAME="Pop!_OS"
VERSION="21.10"
I’m on 5.15.2 and the bluetooth warm boot issue is still here. The newer comments in that thread seem to suggest the same.
The last post seem to indicate there’s a patch that works. It would be nice if it made it in 5.15 at some point, but my money’s on it being released with 5.16.
I rebuilt a custom Arch 5.15.2 kernel with this patch and I can confirm bluetooth is now working properly for me, I was never able to get bluetoothctl to find a controller at all until this patch, warm boot, cold boot, didn’t matter. I’m using the vPro version of the AX210 as well.
Unfortunately I do not yet have a Framework (perhaps once it will be available in my country, and with a larger screen and more I/O), however as I generally upgrade my WiFi with modules I order from Fenvi’s AliExpress store (they also sell on Amazon and Newegg, to my country it just makes more sense to order these from AliExpress), I am currently rocking an AX210 on my Lenovo IdeaPad 300-15ISK, an AX200 with Fenvi’s FV-102 M.2 to standard PCIe adapter on my desktop (Asus Z97 Pro-Gamer at the moment), and the rest of the family are using 9260 modules on their laptops and desktops (the latter with FV-102 adapters).
I use Solus, and I can confirm from my testing that when the regressions occurred, it affected everything from the 9260 to the AX210 (there were both WiFi and Bluetooth issues, not necessarily at the same time, and not necessarily the same exact issues between the different models), at least on Solus, and currently on 5.14.16 on Solus, there are no issues currently with any of them.
Well, for what it’s worth, I’m running Arch and used this AUR package to build a kernel off the latest linux-next sources, which have picked up the change. I tested sleep/wake and bluetooth works fine! Hopefully it’ll be in a regular kernel soon, but till then, I think this works.
Follow-up from my earlier posts about microcode errors during rescan under load: I’ve managed to workaround by setting modprobe config options iwlwifi disable_11ax=Y. Doing so I’m getting no errors and performance is as expected, but obviously 802.11ax (aka WiFi 6) is disabled, but 802.11ac works.
