Which Framework Laptop 13 model are you using? (AMD Ryzen™ AI 300 Series)
Since Arch was not working for me, I decided to go with the Fedora Desktop version. It installed fine, and wifi worked. Once booted into a working Fedora 42, it told me updates were available. So I updated. Now WIFI is borked, broken dead.
I am pretty close to chucking my new Framework Ryzen in the garbage and sucking up the very expensive $3500 loss. I get it that me having played with Linux since 1994 or so makes me nothing but a poser, and that having installed and run it maybe 300 times in all that time makes me nothing but a rank amateur… but I honestly naively thought my Framework would just work!!!
Apparently not. Anyone want my junk Framework machine? I am tired of this thing already. Not only did I have to put it together, but it fails to just work… Makes me sad I am so bad at this game…
Sorry to hear your troubles…have you tried a kernel regression? It may have something to do with the latest kernel. I know with my experiences so far that it takes a minute (figuratively) for new hardware to get baked in (ironed out). You may also want to reach out to support because something could be physically wrong with it.
I also understand the frustration of it just not working considering the price point, I’ve been there.
seeing you have a similar issue here , is there any chance the common thing being Linux kernel 6.15 (Or backported patches)? I’m on 6.14.8 (Gentoo) and wifi works.
What is the update diff?
but I honestly naively thought my Framework would just work
The wireless controller is really new, it isn’t yet properly in PCI databases.
So nice of Framework to trick this thing out with hardware few ever use, and even better litter the website with Happy Faces that it just works fine. I am not asking for much, a working laptop in 2025 seems reasonable. Framework is a total scam IMO, and I feel suckered for falling for the hype. Kernel 6.14.6 and a Mediatek device 0717 just does not work.
WTF… I feel so dirty… I understood when my 2015 Broadcom device was a little touch and go, but this is pathetic…
kernel 6.14.6 should not exactly be killing a brand new laptop… I mean, sure, I can always go back to 2022 and Linux 5 even, but honestly, I was expecting some care and concern from a company like Framework that their plastic and silicon Taiwan stuff would JUST WORK… and not require me to use software that does not apparently even exist yet. Yay.
I can login to my SSID fine. Asks for a password, I provide it. However, there is still no connection to anything as DHCP is not enabled in this most basic Arch scenario. Tried using the built in DHCP and got nowhere… it is like the install is conspiring to make sure networking is as manual and hard as possible to do. How hard would it have been to just let arch install with DHCP !! Too hard I guess.
Are you on Arch or Fedora? Your OP stated Fedora, but this post is all about arch. Two very different Linux distros. Regarding DHCP on arch, you should re-visit the installation wiki’s networking configuration section, which explains setting up networking. Arch is all about choice, so you have to choose what you want to use from all the available options based on your desired setup. Arch will not choose for you.
If you need most basic things done for you and you prefer the Arch ecosystem, try another related distro such as Manjaro or EndeavourOS.
I am using Arch. My problem is, arch install comes to life with no DNS and hence it dies before installation. I can connect to my wifi SSID fine, but there is no DNS. Trying to configure DNS to work has not worked at all. No idea why it is so hard to do, but basically there is no default route, and nothing can therefore be done to install Arch, until I can get this Mediatek card talking to the Internet. So frustrating!
Let me get a better picture: you get connected to wifi, you get an IP address from DHCP, the only thing missing is DNS?
what does resolvectl say? What is your ip route status?
Have you tried forcing the DNS in /etc/resolv.conf (after disabling systemd-resolved), at least for basic install until you get NetworkManager up and running?
I can connect to wifi. Yes. I do not get an IP from DHCP. Therefore, I cannot continue with any install. Hope that is clear. Sorry for the confusion. It seems the install fails simply because this mediatek driver for wifi is not getting an IP address.
I will try that, maybe, but the point seems to be the hardware I just unboxed from Framework, with the MT wifi card, is indeed broken in kernels less than 6.14.8 and since I am trying 6.14.4 I am doomed.
I will try not to throw this thing in the garbage… I know one day it will work.
What are you using to manage the connection? manual wpa_supplicant? netctl? As I said, I come from Gentoo, so I have no experience with netctl…
If you could find wpa_supplicant (netctl uses it too) logs, just to confirm you get properly associated, that would be great.
And I suppose you have done cold boots in between attempts?
If you can ping, disable systemd-resolved, manually force DNS into /etc/resolv.conf, and set up default route. ip route add default via $router_address dev $wireless_device
Then you can install the system, and networkmanager. hopefully that will make stuff easier.
I lied. I cannot ping my router. I am gonna shut down, throw the framework in the garbage and do something else in life. I wasted too much time on this to get any value and a loss of $3500 compounded with another day of mental health wasted, is bad.
Do you have a possibility to use a wired network, at least temporarily for the installation?
I actually remember having to delay updating to 6.14 series on a different machine, because (mediatek?) wifi was very broken… I don’t know which minor version it started to work. My logs say I updated to 6.14.6
