I’m also running Debian 11 on my Framework. Here were the steps I required for installation:
The Intel AX210 wireless card requires non-free firmware and a newer (backported)
kernel. Debian can be installed using an ethernet adapter with the netinstall image, or
alternatively use the full DVD image and manually load the required firmware after
installation using another USB drive.
Modify /etc/apt/sources.list to include non-free and backports
The Framework laptop requires non-free firmware for the AX210 wireless card to
function properly, as well as a backported kernel.
deb https://deb.debian.org/debian bullseye main contrib non-free
deb-src https://deb.debian.org/debian bullseye main contrib non-free
deb https://deb.debian.org/debian-security/ bullseye-security main contrib non-free
deb-src https://deb.debian.org/debian-security/ bullseye-security main contrib non-free
deb https://deb.debian.org/debian bullseye-updates main contrib non-free
deb-src https://deb.debian.org/debian bullseye-updates main contrib non-free
deb https://deb.debian.org/debian bullseye-backports main contrib non-free
deb-src https://deb.debian.org/debian bullseye-backports main contrib non-free
Mine is also slower than expected. I initially only had 32GB of memory and later upgraded to 64GB. Boot time got slower - I can only imagine it’s doing some form of memory space enumeration before starting up.
I have seen similar comments about both 5.12 and 5.14 kernels. My plan after reading a bunch of posts here and on reddit, was to try 5.13. I’d like to run debian 11, if I can get everything to work nicely, but plan to try various distros for fun if nothing else. My device is scheduled to arrive in 2 days, so I can try this soon myself.
So my question is, has anyone here tried debian with 5.13? If so, are either of the sleep/Wifi issues an issue?
If anybody is having difficulty with getting Bluetooth to work, this comment on another thread worked for me. Unfortunately, it looks like a soft reboot borks bluetooth until you power the FW off all the way and turn it back on. Not the worst tradeoff, but something to be aware of.
I’m also using the backported kernel (at time of writing, 5.14.9-2) and all the non-free firmware packages.
Just joined the Framework/Debian 11 group yesterday. XFCE if anyone cares.
I found this thread because the wifi card was crashing my whole usb system after 20 minutes or so of uptime. Just upgraded to 5.14 and at least Im stable now. At home, I run wired through a usb 3.1 hub. I think Ill pick up a AC card soon and downgrade back to the LTS kernel. I dont think Ill run into a AX hotspot for quite awhile.
I dont care about the fingerprint reader.
I havent been able to get any external monitors working yet. I have 2 different usb c to hdmi dongles and neither work. I think Im going to have to bite the bullet and move up to a displayport or usb c monitor(s).
Any ideas on that?
Hello. Framework has the hdmi add-on card you could use, instead of using a separate dongle. As for the wifi, the one I’m using is the QCNFA222, which is supported in Debian via atheros 9k driver. So far it’s been working well, but I haven’t been able to get bluetooth working.
Is the expansion card known to work with linux?
Im in a little over my head on this one. My desktop ran debian for years with dual monitors, but that was through the graphics card that had dual out.
My research has lead me to believe that usb c to hdmi involves a converter chip in the dongle that requires a driver. Theres a company that sells dongles called displaylink that has linux drivers available, but I dont have that brand. I dont know. Im guessing a little. My dongles both work on my android tablet, which would suggest a driver exists somehwere. Displayport seems to be a much more native usb c spec. Its probably time to upgrade.
I tried the HDMI expansion card when I got it and it works just fine (Debian sid). Since HDMI is a standard, all of the conversions should be happening in the expansion card itself (and I don’t think there need to be any special drivers?). When I plugged in a monitor (a TV in my case, since that functions as a spare monitor to test this sort of stuff), everything ‘just worked’ (including HDMI audio routing).
The guy who wrote some kernel module code to get it to work, says some dongles just dont work. Ive tried all the stuff he mentions in that thread.
Ive actually got 3 dongles. Ones built into my hub. I really want dual 1080p monitors when Im home, so I have a dual hmdi out dongle. I dont to tie up 2 ports with single use cards. Finding that one unicorn dual hdmi dongle that works seems like too much of a scavenger hunt to me.
If I cant have dual monitors, Id rather upgrade from 1080p and just get a new setup that has something more modern that hdmi. I was just hoping a $20 dongle would work.