-
Notifications
You must be signed in to change notification settings - Fork 3
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
WARNING: No feed for package 'rtl8821ce-firmware' found #1
Comments
Oh, also I am using openwrt latest snapshot. |
So I removed the dependencies and it builds successfully. But 8811CU device won't work. |
Hi @dausruddin, for the missing firmware, you will need to add these two commits/patches to your tree: Pix13/rk3328-rock-pi-e@ef2915d and Pix13/rk3328-rock-pi-e@4026129 This will take care of having thr rtw88-usb package available in your OpenWRT tree. As for the driver itself, it does not work yet :) Please follow my issue here: ulli-kroll/rtw88-usb#12 and more importantly, the branch backports ( https://github.com/ulli-kroll/rtw88-usb/tree/backports ) which is the one that will/should work on OpenWRT |
Oh okay, thanks. Seems that I won't be able to do anything as it is out of my capability. Anyway, I want to mention that https://github.com/immortalwrt/immortalwrt is working fine, at least on my friend's R2S. He also tried https://github.com/quintus-lab/OpenWRT-R2S-R4S which can be seen pulling RTL8821CU driver source from immortalwrt repo, and got them working. |
Well i got the old driver working too, but it only works as a client wifi, not in access point ( because of the missing newest mac80211 api). I have hope, i'm badgering the new rt88-usb developper to have the driver working :) |
I'll keep an eye then. Thanks! |
Hi. After reading an interesting conversation in jayanta525/rk3328-rock-pi-e#1, I wanted to try it for my Nanopi R2S.
But I am getting this warning
Do I need
rtl8821ce-firmware
? If yes, where do I get them?I am just a casual user trying to build my own firmware, so treat me as a newbie :)
Thanks!
The text was updated successfully, but these errors were encountered: