Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not finding firmware #22

Open
fluffy-the-dragon opened this issue Oct 8, 2024 · 3 comments
Open

not finding firmware #22

fluffy-the-dragon opened this issue Oct 8, 2024 · 3 comments

Comments

@fluffy-the-dragon
Copy link

fluffy-the-dragon commented Oct 8, 2024

i did all the steps and downloaded the firmware but got this
fluffy-dragon@fluffy:~$ sudo dmesg | grep mt7902
[ 2.511568] mt7902_common: loading out-of-tree module taints kernel.
[ 2.511578] mt7902_common: module verification failed: signature and/or required key missing - tainting kernel
[ 3.554510] mt7902 0000:02:00.0: firmware own failed
[ 3.554599] mt7902: probe of 0000:02:00.0 failed with error -5
[ 453.427782] mt7902 0000:02:00.0: firmware own failed
[ 453.427923] mt7902: probe of 0000:02:00.0 failed with error -5

@BoskyWSMFN
Copy link

Turn off secure boot or sign these modules with kernel modules signature. This signature also must be enrolled in uefi.

@fluffy-the-dragon
Copy link
Author

I don't know how to do that.
My system is a Windows laptop dual-booting Ubuntu. It is an ASUS Vivobook Go 14-15 with Secure Boot disabled, and I have checked the locations using modinfo. It points to a Mediatek 7925 or something (I forgot), but the required files are there. I ran the get firmware script also still no luck

@samveen
Copy link
Owner

samveen commented Oct 9, 2024

@fluffy-the-dragon

  • https://wiki.ubuntu.com/UEFI/SecureBoot/ gives a decent beginning overview of what secureboot is and what needs to be done to allow loading for locally compiled modules.
  • From what I see in your log above, The module is loading as expected, so the issue isn't secure boot.
  • Please examine how the firmware script runs, and check against your environment to confirm that the script actually completes as expected, in case you suspect that the firmware is missing.
  • Lastly, my testing mt7902 is stuck in transit somewhere, and I have been unable to trace it, so my work has stalled here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants