Honestly, and this is my approach to all distros - if it’s working and not going to be outdated/unsupported soon, I leave my working installs alone. I have a very happy install of Fedora 37 on a personal machine even though I work on Fedora 38 for example.
That said, we have not had time to properly vet 21.2 yet for community level compatibility. May be fine, outside of the known issues list here (some of which would give me pause).
But it “should” be fine. Just remember, backup first before trying anything and as always, clean installs always have a higher success rate than an upgrade path in my experience. Some will debate this, I’ve witnessed for over a decade as fact.
Tltr: If you feel strongly about upgrading and wish to do so, consider everything above and backup, backup and backup.
Hey, need support help if anyone is able to assist.
My wife just got her Framework 13 factory second with the intel 11th gen, and every once and a while the desktop will crash on her. From what she’s showed me:
the screen goes black
all wireless devices from WiFi to Bluetooth disconnects
we think the OS sometimes suspends since on occasion the keyboard goes black, and power button blinks
If the computer doesn’t suspend itself, it takes 30 seconds or so for the desktop to return and for her to reconnect everything. If it does suspend, then she needs to press the power button to get back into it.
I’ve looked at error logs in the “Logs” app, and searched around with Google with nothing helping narrow this issues down. It’s intermittent and sometimes can happen multiple times per day, while other times it’s good for a week or so. Just need help trying to trouble shoot this, as I’ve gone though the Guide and did everything I could, but nothing helped remedy this problem.
Easy check: make sure there are no magnets near the left side of the keyboard. There’s a sensor here which detects a magnet in the lid. When the lid is closed, it goes to sleep. Magnets and other laptops can trigger this.
As for the OS, support would have you check against a live USB of Ubuntu or Fedora. If it occurs while running Ubuntu or Fedora you should request support. But Linux Mint should still work well, and for 11th gen, it may not even need an advanced kernel. An updated kernel may help, though, and on Linux Mint it’s very easy to install and run a 6.5.0 kernel.
No magnets near the Laptop when it happens. We just swapped out the RAM and SSD, as they are from her old laptop, and did a fresh install and walkthrough of the community guide and the issue still happened.
New bios just dropped for her framework so trying that to see if it fixes it, if not then installing Ubuntu, and if that still doesn’t fix it, contacting Framework Support.
Thanks for the advice, and I really hope this isn’t a hardware issue.
OK, was able to solve it. My wife likes to have her e-reader near her laptop when she’s working. And the weak magnet for the latch was enough to put it to sleep when she was moving it above her keyboard.
I am shocked with how sensitive the sleep sensor on the Framework 13 is, especially since her previous HP wasn’t having this issue. But I am happy to know that the laptop is fine.
I have a hard time installing Mint on my Framework 13. I followed the community guide, had firmware updates already installed (Intel Ultra 1) via Ubuntu. Checksums are fine. I tried two different sticks, two different writers (onboard Mint boot drive writer and Balena), with Secure Boot disabled, and with (prefered) and without home directory encryption (I wouldn’t mind full disk encryption though). The result is always the same:
Latest Live Linux Mint boots fine
Installation works fine
Restart works fine
But when I shutdown and start new, the boot process halts with a black screen
When I shut down (pressing the start button), it shuts down fine though (meaning it shows briefly some logging and then shuts down)
No boot menu appears and I seem to not be able to get in one. I can go into the grub bash though.
What could be the problem (grub?) and how can I troubleshoot it?
Thank you very much for any help!
You can boot from USB and then run boot-repair from a terminal directly. It will fix the existing install (at least it did it for me).
The next time you restart, the grub menu hopefully appears. Instead of choosing an entry, just press e for edit, and change the linux mint line by removing splash and quiet. Afterwards it worked for me. Of course, you can test if the boot-repair already fixed it for you by first trying the Linux Mint entry from the grub menu.
Good luck!
When you edit the boot command-line by pressing e you are able to add or remove parameters that grub will pass through to the linux kernel when it starts up.
There are a large number of kernel parameters. Some have existed across kernels since the dawn of time; others are specific to a very narrow set of kernel versions. They are documented on kernel.org (below the root of the documentation tree at the path admin-guide/kernel-parameters.html).
The parameters splash and quiet control cosmetic behaviour at boot time. It is not necessary to remove either of them to fix anything. If your boot process is failing after grub passes control to the kernel, removing these parameters might be helpful in that any messages emitted by the booting kernel will be displayed on the Linux console and should be visible to you.
PS: pedantry requires that I point out that splash is not really a kernel parameter. It is interpreted to mean “display some kind of splash screen at boot time”. In my experience, just how that is achieved varies across distros and attached display hardware. If splash is present, whatever it does may mask kernel output. Removing it from the boot command-line ensures that masking cannot occur.
I only reported the steps I had to take to fix the booting issue for me. I agree that quiet is unlikely to change anything, but I could speculate that splash could result in the boot error (there are some reports on issues with HiDPI displays). I can only say that only running boot-repair wasn’t enough for me.
Akron – thank you. These steps seem to work. I did a fresh install. I ran the boot-repair utility off of a USB. When I use e to edit in the grub menu and remove splash & quiet and it ctrl-X it boots up.
However, the change is not permanent. I have to manually do this each time.
How do I make this change permanent so I don’t need to edit the grub file each time I boot up? Thank you.
