I am having problems with Fedora 36 KDE. After waking from hibernation I receive this message: Message from syslogd@Framework at Jul 12 20:21:40 …
kernel:Uhhuh. NMI received for unknown reason 30 on CPU 0.
Message from syslogd@Framework at Jul 12 20:21:40 …
kernel:Dazed and confused, but trying to continue
This does not help much, if you don’t use laptop for a day it will be dead. This is super annoying, especially if you used Mac for years before. The only solution is to keep it always plugged in when you at home and turn it off if you going to travel
The coming BIOS 3.10 might help you. You can watch the thread: 11th Gen BIOS 3.09 Beta release. We were testing the 3.09 that improves the battery life, but as the 3.09 has a bug, we are waiting for the 3.10.
When installing Fedora 36 on the new Framework laptop with 12th Gen i5, I was repeatedly hitting “dracut-initqueue timeout” issues because the live USB was not being detected despite the fact I just booted from it.
The fix for this in my case was to boot from the USB, then remove and re-insert the USB after the GRUB screen.
Note: I’d also disabled secure boot as part of my troubleshooting and that may or may not also be a requirement to get the boot to succeed.
After almost a year of using Manjaro Xfce on my Framework, I decided to distro hop to Fedora 36 this weekend (changed my avatar and everything) for a variety of reasons.
The installation was smooth. I ran into the problem with the fingerprint reader holding onto the print that I registered in Manjaro, but I found the answer here on the forum right away.
I think it will take a while to get used to GNOME, and there are a couple things I wish I could change, but I’ve always been impressed with how well put together it seems. It feels right to be on a distro and desktop environment that prioritizes and contributes to the development of the latest things like Wayland and PipeWire and Flatpak (although I’m not entirely sure what to make of that one yet). I’m happy that I can enable Secure Boot too.
I’m impressed with how up-to-date Fedora’s packages are, which I didn’t expect on a point release distro. Some might even be newer than on Manjaro since they hold them back from the stable branch for a couple weeks. I hit a bug when running any kernel beyond 5.15 with Manjaro, and now I’m happily running 5.18 on Fedora.
@tim300 curious, how was running Manjaro on the Framework? What are the reasons you decided to hop? Rolling pains?
For context, recently got my FW and running Fedora36 w/GNOME on it. Have been running Manjaro GNOME on a desktop for a few years and Manjaro Sway on a Thinkpad for a little less than a year… almost just went for it again on the FW but wanted to try something new. But, I am curious, were there particular things that felt not so great w/ Manjaro on the FW?
[ Hope this Q is not so off-topic - it feels related enough to Fedora in the sense of comparing it to other options people might be used to. But can move it elsewhere if this is a derailment ]
Been using Fedora 36 since its release in May, but have had ongoing issues with USB 3 storage devices (external HDD, SDD and flash drive) not being recognized when plugged into USB-A expansion cards. Has anyone else has had similar issues with USB 3 devices not being recognized in this way?
I’ve been in dialogue with the support team (thanks to them for helping to investigate), but after some research may have hit on what’s been causing this.
The Linux kernel has a USB autosuspend function, and I wonder if this function has got confused between the USB-A expansion card plugged into a USB-C bay in the Framework and the device plugged into the expansion card, so that when a device is removed, the autosuspend function “auto-suspends” the expansion card? It’s a thought.
I found that the USB autosuspend function can be turned off in the boot parameters by adding “usbcore.autosuspend=-1” to GRUB_CMDLINE_LINUX_DEFAULT in the etc/default/grub file.
Having done this and then updating grub (sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg) a few hours ago, all my devices are behaving so far.
@LDW Are you runing tlp setting to save the battery life? In my case, I see that my disk expansion card doesn’t recognize when starting the Fedora 36. It was recognized in a different port in the past. I suspect it is because of the tlp setting to auto-suspend the USB.
Fedora 36 is working reasonably ok on my Framework laptop (upgraded Intel 12th gen).
The only issues that I found were:
FN keys from (F7 to F10) do no work. They worked fine on Ubuntu. But I have to use the Gnome applet to update the brightness.
Intel Wifi (AX210) is very finicky and I need to disable power management to stop getting hung.
If I use s2idle instead of deep the battery drains around 1% per hour while sleeping. (I wish there was a LPDDR4/5 version of the laptop). However on 12th gen Intel, the laptop wakes up much quicker than the 11th gen.
I am also getting this (on my 12th gen laptop) but I don’t really see any other issues and I guess Fedora 36 doesn’t officially support hibernation. I’m glad that it’s probably not a hardware fault given you see it as well.
I think this is fixed by adding module_blacklist=hid_sensor_hub to the kernel arguments as per the Fedora 36 setup guide. At least it works fine for me.
I am still having some pretty serious problems with my wifi card. Over the last 2 weeks I get from 0-15 minutes after a restart before the wifi driver crashes and I have to restart before wifi will work again.
The last handful of system logs I get before wifi fails are:
btrfs/zram hibernation (which I’ve been running successfully with 64GB ram), and
a hibernation resumption issue that popped up a few months ago and my solution.
For those of you that haven’t seen it, there’s a great article on how to setup hibernation with btrfs/zram:
It started from this wonderful GitHub Gist:
I have hibernation/suspend-then-hibernate setup on my system where it will first S0ix sleep and then 2 hours later hibernate. Also hibernates at I believe 7% battery. It’s been working flawlessly since Fedora 35-36 until a few months ago, where sometimes on hibernation resumption, the system would freeze on a black screen. I troubleshooted today, and here’s my comment/solution:
If you have hibernation resumption issues, I recommend reading that, but to summarize so these words are populated in this forums search:
I added this to my kernel parameters to see debug logs upon system/kernel boot and hibernation resumption:
ignore_loglevel=1 initcall_debug=1
And saw that with resumption, my system froze here:
intel_ish_ipc 0000:00:12.0: [ishtp-ish]: Timed out waiting for FW-initiated reset
intel_ish_ipc 0000:00:12.0: ISH: hw start failed.
initcall ish_driver_init+0x0/0x1000 [intel_ish_ipc] returned 0 after 219091 usecs
To fix the issue, I simply blacklisted the intel_ish_ipc module by adding this to the kernel parameter:
modprobe.blacklist=intel_ish_ipc
Though it should also work by adding this to e.g. /etc/modprobe.d/blacklist.conf (or best-practice-naming as /etc/modprobe.d/intel_ish_ipc.conf) + rebooting:
blacklist intel_ish_ipc
After blacklisting, finally my system no longer freezes on that module and resumes normally!
Though it seems that the intel_ish_ipc module still loads afterwards since it’s a dependent module for intel_ishtp:
lsmod | grep ish
intel_ishtp 61440 2 intel_ishtp_hid,intel_ish_ipc
@ the Framework team
I’m still not sure if my issue was caused by a kernel regression, a Framework BIOS update, a Fedora update, or something else. These all kind of happened around the time this issue popped up. But I do remember this started happening right around upgrading to BIOS 3.09/3.10.
Just took a look at your post and saw that your BIOS version is quite old. I don’t think there were any BIOS fixes regarding wifi, but might want to update for other reasons.
I can confirm that I haven’t had any issues with the Intel AX210 on 5.19.6-200.fc36.x86_64.
Here are some troubleshooting questions:
When did the issues start happening? Did anything change around then? Try to remember to pinpoint the cause.
Has this been working fine before? This would mean that likely a software change/update is causing the issue.
Did this start after a kernel update (this would mean a new bug/kernel regression)?
You can downgrade your kernel (Fedora also has the 3 most recent kernel versions in GRUB so you can try booting a previous version. I’d try earlier minor versions, e.g. problems on 5.19.x? Try 5.18.x, 5.17.x, etc. to see if the issue persists.
Any updates to your wireless drivers?
You can try earlier driver versions much like the aforementioned kernel versions.
Is some power management utility like TLP messing with your wireless?
Are you absolutely sure it’s not your wireless router? Are your other devices okay? If possible, you can try your wifi card in another computer. Etc.
You can also try another wifi card in your Framework (preferably another brand/model) to pinpoint if it’s your card. And another of the same brand/model to verify if you have a dud. Etc.
I just quickly typed/threw out a bunch of steps I usually run through in my head, and it can get deeper than that, so if @Freemasen have any questions lmk since I might be missing something.
I have never been able to get my laptop to have stable wifi (longest I’ve gone w/o losing the connection is 30 minutes). I tried updating the bios today and the problem persists. I also tried a fresh install of Ubuntu 22.04 and manually placing the intel driver into /lib/firmware, also no change.
I don’t have any problems with any of the other devices I have connected to my wifi.
Unfortunately I do not have another laptop or wifi card to test either option out (though I might buy a new wifi card this weekend since I don’t have a lot of use for a laptop w/o wifi).
@Freemasen sure thing!
Issue persists on a fresh install of Ubuntu as well as using another driver version? If the issue persists on a fresh install of Fedora and Ubuntu, I wouldn’t think it’s due to software unless you’re running into an issue that spans the two kernel/driver versions.
You can also try a Windows installation to rule out Linux as the cause.
If it also happens in Windows, then I’d think it’s likely a hardware issue (unless it’s just an incompatibility with your wireless router).
If you haven’t already, ensure the physical antennas are hooked up properly to the wifi chip.
But yeah testing with a new wifi card’s an easy way to shed some serious light into the issue.
Yup! A laptop without wifi? Ahhhhhh that’s scary, goodspeed!
Edit: quick searching around for the error message in your log
Got it working on my FW 12th gen in Fedora 36 without a hitch.
Note: you do give up the ability to hibernate with this from my understanding (or at least makes it much more difficult). Personally, I felt like this was something I wanted a little more (versus hibernation). I’m sure there are some security pros that would say this is a bad idea versus typing in a password at boot to decrypt in addition to your account. I wanted a linux experience that was closer to what I was coming from with Windows and macOS where you only do your login.