@junaruga – thank you. is there any way for me to continue editing this? i was planning to add some details about deep sleep here but can’t seem to edit any longer.
We can ask @nrp to add the wiki function to this thread. My guess is when Framework people changed the thread’s category systematically recently, they didn’t change the owner info of the thread properly. As a result, you cannot edit your 1st content on this thread any more, even when you are the owner of the thread.
1 Like
Restoring the EFI entries is as easy as running these from live boot:
mount /dev/<rootpart> /mnt
mount /dev/<efipart> /mnt/boot/efi
for i in /dev /sys /proc; do mount --bind $i /mnt$i; done
chroot /mnt
sudo grub-install
sudo update-grub
for anybody wanting to upgrade BIOS after installing any linux distro.
I have made the first post a wiki. Let us know if you would like to merge threads.
2 Likes
Just installed debian testing on my new framework, on dual-boot with windows (still need it at tax time, sigh…). My main difficulty was not realizing that windows does not properly turn the wireless card off when restarting, which means it does not get recognized by the netinstall software. One needs a real shutdown + power-on. Or better, make windows behave, following en:users:drivers:iwlwifi [Linux Wireless]
@khimaros - beyond the wireless issue mentioned above, another issue worth discussing in your list on top may be that the problems with overly large power drain after S2idle can be solved with a kernel parameter – see Linux battery life tuning - #156 by technical27
1 Like
Hello from my Framework 12th Gen on Debian testing (I think)!
As soon as I booted into GNOME I got crazy graphical glitches. Wayland is used by default and X11 stabilized things a lot so I’m using that at the moment. I’d like to use Wayland.
I noticed that Settings - About - Graphics says “Software Rendering” which I’m guessing is a problem. Why is Debian not using the graphics hardware? Thank you!
I found this. I had to download a couple of missing firmware files (adlp_dmc_ver2_16.bin and adlp_guc_70.1.1.bin). I have hardware rendering and Wayland now!
1 Like
I’ve been using Xfce with Debian Testing for a couple months and just started having glitches with the trackpad and graphics under the latest kernel 6.0.0.4. If I move the cursor around for a few seconds, it will freeze and then the display will glitch/reset. Booting back to 6.0.0.2 fixes things. Anyone else seeing this? Seems like a regression, no real problems until now.
Looks like this is fixed with the latest apt upgrade. I’m guessing the newer i915/display firmware fixed it (firmware-misc-nonfree) since there wasn’t another kernel upgrade (still 6.0.0-4 / 6.0.8-1).
Report back:
I installed from Debian testing (bookworm, not rolling) from a netinst image with non-free firmware (weekly from 14th?). I ‘cc net.iso /dev/sda’ as root to a USB-A flashdrive, and booted from it.
The Debian installed picked up the wireless fine, then installed without issue. I’ve had a few minor glitches (freezing mainly) when testing Gnome Classic and Gnome Flashback, but since using Gnome “normal”, mostly fine. The screen does freeze sometimes, briefly, but then comes back after a couple of seconds or so.
Regarding brightness: I found the default automatic brightness too bright, so I worked around that by covering the light sensor, then turning off automatic brightness in Gnome. Then, to get the brightness keys to work I disabled the automatic light sensor (ALS) (put in file </etc/modprobe.d/framework-als-blacklist.conf> “blacklist hid_sensor_hub” (no quotes)), and then I /also/ had to run command “update-initramfs -u”, as just blacklisting the hid thing didn’t work.
I haven’t got around to messing with suspend yet, and can’t comment on power use at the minute. I also haven’t looked at the fingerprint reader or tested the microphone. Bluetooth works for what I tested.
Overall, most of my issues have been Gnome related (who’s stupid idea was it to make scroll, scroll the wrong way?!), rather than hardware. I haven’t messed with the default scaling, which I think is 200%.
While I’m running testing, when it goes stable, I’m staying with Bookworm.
If anyone has any questions, I’ll try to answer them.
1 Like
Just following this thread, thanks everyone.
I installed debian-bookworm-DI-alpha2-amd64-netinst.iso on my 12th gen Framework Laptop after having running Ubuntu 22.04 since October 2022. Some details:
- Non-graphical install
- Wifi identified and used for install
- No disk partitioning; re-used existing partitions
- Installed base system (no desktop, no ssh or http servers)
- After reboot everything worked, including wifi network connection although text size was quite small.
- performed apt-get update/upgrade; reboot
- Used tasksel to install desktop and gnome; reboot
- System worked as expected, including wifi network connection
However, gnome utilities for managing the wifi network report, “No Wi-Fi Adapter Found”. Which is strange since the wifi network connection is working, and has worked throughout the entire installation process.
My wifi issue is resolved. The file /etc/network/interfaces contained a block that defined a network connection for the wifi adapter. Deleting that block and rebooting resulted in the desired behavior: the usual gnome utilities for managing wifi network connections see the wifi adapter and function as desired.
I just received my DIY 12th gen i5 today, installed RAM and SSD I got separately, and installed bookworm from ISO. It worked nicely, wifi got picked up immediately, no problems to report. But after rebooting, I had very bad screen freezes. The display would freeze for 10-20 seconds at a time, keyboard and mouse would appear frozen but actually buffer input, and the screen would magically update after that long period. Input works for 5-10s, then freezes again. Obviously this made the machine unusable.
However, the strange thing is that if I played a video (like anything from YT in firefox), the screen stopped freezing.
This was on bookworm at first, then upgraded to unstable, and both had the same issue. I had upgraded BIOS to 3.06 before upgrading debian.
I’m not using wayland.
I’m using past tense because I’ve rebooted and added i915.enable_psr=0 to the kernel command line. This seems to have fixed the problem. Not sure how this is going to affect battery life, but at least I can use the computer 
Curious to know if this is the “official” fix for such a problem or if there’s something better to do?
Hi @Laurent, great to hear that it works now with i915.enable_psr=0 as kernel paramater, so doing okay with Xorg at the moment yes? we officially support Ubuntu and Fedora for now, but inputs like yours along with OP’s guide to make debian testing workable is really appreciated. please do keep us updated.
1 Like
@Loell_Framework yes, I don’t mind missing out on wayland for now, my goal is just to have the same system as before, plain boring Debian sid, that just works 
I’ll do more testing today with actual work and report back if I find anything useful. Thanks for being on it!
Hello, thank you for this guide.
Could you just update the power management and precise it’s Intel only ? It seems AMD only has s2idle and not deep S3. I was lost for a moment… !
Thank you very much.
1 Like
