RZ608 MT7921K WiFi Support for Aya Neo Pro/Retro Power

[pastaq]

The Aya Neo Pro and Retro Power come with a newer revision of the WiFi/BT module than the standard version. The RZ608 MT7921K uses the same driver, but the alias for the revision is not in the kernel driver that is shipped in the latest release. As network connectivity is required for the install to complete, this prevents install of ChimeraOS on this version of the device.

Possible Solutions:
Implement the module patch that adds support in the kernel from here: https://patchwork.kernel.org/project/linux-wireless/patch/84ab45bf42f57fd0301c156ffc11d0fe330ff1f8.1636857817.git.deren.wu@mediatek.com/

Implement a udev/modprobe rule as specified in the following thread: https://askubuntu.com/questions/1376871/rz608-mt7921k-wireless-lan-driver-is-not-supported-on-ubuntu-18-04

relevant portions, two files will be needed:
/etc/modprobe.d/rz608.conf
alias pci:v000014C3d00000608svsdbcsci* mt7921e

/etc/udev/rules.d/99-rz608.rules
SUBSYSTEM=="drivers", DEVPATH=="/bus/pci/drivers/mt7921e", ATTR{new_id}="14c3 0608"

I have been able to install Manjaro on the AN Pro using the udev/modprobe method, but the installer for chimeraos doesn't show any networks after implementing a temp alias via echo 14c3 0608 > /sys/bus/pci/drivers/mt7921e/new_id or with the files method above.

I am willing to test and/or help implement a fix via a PR. I will just need direction from the community which of these two methods, or an additional one I haven't mentioned here, would be best for the project.

[alkazar]

I was hoping this would be in the 5.16 kernel, but looks like it won't be (https://github.com/torvalds/linux/blob/v5.16-rc7/drivers/net/wireless/mediatek/mt76/mt7921/pci.c#L18).

We don't have the infrastructure/setup for custom building the kernel or kernel modules.

I think the options are:

• wait for kernel support
• implement the udev/modprobe rules

[Samsagax]

Why not starting with the modprobe+udev rule and when the kernel keeps up just remove it?

[alkazar]

Why not starting with the modprobe+udev rule and when the kernel keeps up just remove it?

That makes sense, assuming the workaround can be made to work, which we haven't yet been able to confirm.

[pastaq]

Workaround had to be implemented in both the installer-media and ChimeraOS repo's. I was able to connect to WiFi and install with these changes.

[alkazar]

@pastaq amazing, thank you!

[alkazar]

@pastaq Do you happen to know if this change also enables bluetooth to work?

[pastaq]

@pastaq Do you happen to know if this change also enables bluetooth to work?

It doesn't as far as I can tell. No BT device shows up in the BT menu. I believe this is an issue with all the versions of this device driver. From the Arch Wiki it shows BT not working on all devices. https://wiki.archlinux.org/title/AYA_NEO_2021

Edit: Nevermind, it seems to be working. After a reboot my headset showed up and I was able to connect. Seems like the wiki needs to be updated.

[Susurrus]

I've been trying to maintain the Arch wiki page and did a little cleanup today: https://wiki.archlinux.org/title/AYA_NEO_2021. Feel free to let me know if there's any extra details I should add.

[pastaq]

I've been trying to maintain the Arch wiki page and did a little cleanup today: https://wiki.archlinux.org/title/AYA_NEO_2021. Feel free to let me know if there's any extra details I should add.

The only thing I would change is the PRO BT module requires the same workaround that the WiFi module does, as its the same physical card/driver.

[Susurrus]

Added, thanks!