# \[RESPONDED\] Yet more Mediatek issues on AMD/Linux

**URL:** <https://community.frame.work/t/responded-yet-more-mediatek-issues-on-amd-linux/50039>\
**Category:** Linux\
**Tags:** manjaro, ubuntu\
**Created:** [April 30, 2024, 1:35am UTC](https://community.frame.work/t/responded-yet-more-mediatek-issues-on-amd-linux/50039 "2024-04-30T01:35:36Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![Konstantin\_Rannev](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/konstantin_rannev/32/24974_2.png) [@Konstantin\_Rannev](https://community.frame.work/u/Konstantin_Rannev)\
**Post date:** [August 30, 2024, 11:52am UTC](https://community.frame.work/t/responded-yet-more-mediatek-issues-on-amd-linux/50039/21 "2024-08-30T11:52:18Z")

</div>

I’ve provided a possible solution here:

> [@\[Framework 13 AMD on Arch\] Issues with wireless after resume](http://community.frame.work/t/framework-13-amd-on-arch-issues-with-wireless-after-resume/44597/33):
>
> Personally, to deal with this issue I created a Systemd service called “restart-wifi.service” that runs after hibernation and reinitializes the driver according to the solution [here](https://bbs.archlinux.org/viewtopic.php?pid=1769611#p1769611): [Unit] Description=Restart WiFi driver after hibernation After=hibernate.target [Service] Type=oneshot ExecStart=/bin/sh -c 'sleep 10 && modprobe -rv mt7921e && sleep 3 && modprobe -v mt7921e' User=root [Install] WantedBy=hibernate.target Place it in /etc/systemd/system/, and then run sudo systemctl daemon-reloa…

---

_[View the full topic](https://community.frame.work/t/responded-yet-more-mediatek-issues-on-amd-linux/50039)._
