I’m looking into OS for my Framework 13 Ryzen AI 7 350. I was wondering if anyone put Ubuntu 24.04 onto their device?
It is not on the list of known working linux editions yet for certain. Framework | Linux Compatibility on the Framework Laptop
I did attempt to put 24.04.02 on mine and it seemed to work on the boot USB. However, after instal all networking (wifi and ethernet dongle) no longer functioned and a few other irritations as well. I suspect 24.04 won’t be viable until later kernel versions are released.
I upgraded my 13" yet again, this time from Intel gen12 to AI 9 HX 370.
I have Ubuntu 24.04.2 LTS installed and a lot of work is happening, so I was kinda forced to proceed with existing distribution.
To enable wifi and networking I upgraded to most recent linux-generic-hwe-24.04 package that brought the 6.11 kernel.
Aside of that, everything seems to work now with one exception.
The only issue I have right now is that AX210 WiFi breaks after suspend/resume cycle and then system became nearly unusable and a lot of errors are printed in the system log.
Also on gen12 resume takes 1 second whereas for AI300 it takes about 7 seconds after I hit spacebar to bring the system back from black screen to screen on with image.
Ok, I’ve just found a workaround to resolve the issue.
If I do sudo modprobe -r iwlwifi before I put the system to sleep, then it resumes successfully.
Afterwards I’m able to bring the wifi back using sudo modprobe iwlwifi.
So indeed, the issue was with the driver not handling resume properly.
Probably need to put this line into suspend/resume scripts.
Update: For some reason that workaround worked only yesterday and today everything broke in another fashion.
Now the system boots, but wifi fails to get back from the state with the message similar to:
iwlwifi 0000:01:00.0: Unable to change power state from D3COLD to D0, device inaccessible
In the end I resolved the issue by disabling power PCIe management using kernel argument pcie_port_pm=off
I was now able to bring the system from the sleep without messing with the modules, and wifi worked.
Obviously the workaround would probably negatively affect the battery life.
Update 2: Nope, still no luck. The trick with pcie_port_pm=off works, but only once.
The first suspend/resume cycle works as intended, but then the second one breaks NVMe access, so even ls in a terminal causes Input/Output error.
Sigh.
Update 3: I gave up and swapped the WiFi card to a non-intel one (RTL8822BE).
But even then I had the same device inaccessible message. That makes me think that the issue is not caused by the driver, but the mainboard itself.
Finally (?) solved by disabling PM using driver setting:
echo "options rtw_pci disable_aspm=Y" | sudo tee /etc/modprobe.d/rtw_pci.conf
Ok, a few days later I can say that RTL8822BE almost works.
It survied a few standby/resume cycles, but today I got the following error, again:
[48359.557206] rtw_8822be 0000:c0:00.0: Unable to change power state from D3cold to D0, device inaccessible
[48359.558578] rtw_8822be 0000:c0:00.0: mac power on failed
[48359.558583] rtw_8822be 0000:c0:00.0: failed to power on mac
[48359.558585] rtw_8822be 0000:c0:00.0: failed to setup chip efuse info
[48359.558586] rtw_8822be 0000:c0:00.0: failed to setup chip information
[48359.559154] rtw_8822be 0000:c0:00.0: Firmware version 27.2.0, H2C version 13
[48359.576812] rtw_8822be 0000:c0:00.0: probe with driver rtw_8822be failed with error -114
So this has definitely something to do with the mainboard and PCI power management.