Did you find any good one?
I fell for the famous morrow list and bought this crap to use as a client as well. Doesn’t work OTB as claimed. Now I’m stuck with it and still not connected. Gonna try with this one wich was honorably mentioned by a user here in the forum. Hope it works OTB.
Linux kernel <> openwrt kernel, have you installed the packages requried, in openwrt ?
1 Like
Negative. Didn’t find them as a package, I had to compile. I am not gonna. That’s exactly why I bought that crap, because of people sharing that list in openwrt related posts. I assumed they worked OTB since openWRT is Linux. I know, my bad.
Idk AND do not want to learn to [compile] do it. Seems like too much of a hassle.
By the way, I see you are very active in this forum. Would you care to mention a cheap adapter that works As Client OTB? MediaTek [known for being cheap] or otherwise. Does the one I mentioned work OTB??
Let's keep trying the one you bought, 1st.
What's the PID and VID of the device ?
MT is recommended because they actually provide open source drivers.
0e8d:7961 MediaTek Inc. Wir
eless_Device
Already had this one. Wich also doesn’t work out of the box but somebody mentioned it working somewhere else. And it not working OTB was the reason I bought the Mediatek FENVI device.
0bda:881a Realtek 802.11n N
IC
PS: Not only it doesn’t work out of the box, it actually interferes with the net work proper functions. That’s the best words I can find. Because when I plug it in it [openWrt] often drops Internet connection.
Out of the box, on the RPi? None, because module packages aren't preinstalled for anything you might add via USB.
opkg update
opkg install kmod-mt7921u kmod-mt7921-firmware
2 Likes
- Multi-OS support: 32-bit and 64-bit Windows XP/Vista/7/8/10/11/2019/2022, MXLinux, EndeavourOS, Mint, Manjaro, Ubuntu, Lubuntu, Kubuntu, Pop!_OS, Fedora, Rocky, Debian, Arch Linux, openSUSE, Zorin, Kali Linux, Tails, Raspbian and Puppy. NO Mac support for Panda Wireless PAU0B.
- The Panda Wireless PAU0B adapter is designed to run on an Intel/AMD based PC or Raspberry Pi 0/1/2/3/4.
Panda says this works in Linux, and RPI; as do the reviews.
Great Product! Worked as advertised!!!
By DGTubbs in the United States on June 5, 2023I'm sure this will work plug and play on Ubuntu on Debian flavors of Linux. I used this for an OpenWrt based Raspberry Pi travel router. I had to build the driver support. But OpenWrt has numerous kmod packages for Panda's MediaTek chips. Just install kmod-mac80211 and then as many of the kmod-mt packages you need to until the device works.
Great job on the device!!! Love it!!! see less
And it is in the list KOA provided.
root@modem:~# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux 5.15.137 dwc2_hsotg DWC OTG Controller
Bus 001 Device 002: ID 0e8d:7612 MediaTek Inc. 802.11ac WLAN
Bus 001 Device 001: ID 1d6b:0002 Linux 5.15.137 dwc2_hsotg DWC OTG Controller
I have the same chip model and it works fine.
In OpenWRT, to keep everything as small as possible, all the non essential packages have to be installed later.
Yeah [as I said before] I didn’t find it as a package. Only a by version of it,
so I installed the bt-mt7921 just to try it and it didn’t work. And when I enter your provided command it gives me the same error ive been facing before, it is not found.
sts/openwrt_telephony
Collected errors:
* opkg_download: Failed to download https://mirro
rs.cloud.tencent.com/lede/snapshots/targets/armvir
t/64/packages/Packages.gz, wget returned 8.
root@router:~# opkg install knod-mt7921u
kmod-mt7921-firmware
Unknown package 'knod-mt7921u'.
Unknown package 'kmod-mt7921-firmware'.
Collected errors:
* opkg_install_cmd: Cannot install package knod-m
t7921u.
* opkg_install_cmd: Cannot install package kmod-m
t7921-firmware.
root@router:~# opkg install kmod-mt7921u
kmod-mt7921-firmware
Unknown package 'kmod-mt7921u'.
Unknown package 'kmod-mt7921-firmware'.
Collected errors:
* opkg_install_cmd: Cannot install package kmod-m
t7921u.
* opkg_install_cmd: Cannot install package kmod-m
t7921-firmware
Edit: btw I have a Ralink USB adapter wich works great OTB [but it’s not wifi5]
That’s what I mean by OTB.
Iknw
Care to help as how to install?
As I said before I know I have to install but I haven’t found it as a package for my build. I only find I have to compile, and I will not because I don’t know how and when I try to learn how, I find it to be too much of a hassle. That’s why [and I repeat] I want one working out of the box. One [wifi5] long known as working OTB In openwrt NOT only in Linux. I have 7 usb WiFi adapters,6 are Realtek two of them are wifi5 and they all work great in Linux none of them work in openwrt. Except for the 2.4ghz Ralink.
My answer was for 0e8d:7612 which is supported by kmod-mt76x2u package
what you got there ain't openwrt.
you will most probably run into the same issue with all wifi adapters you buy/try.
Yeah. It’s a fork based on lede. Sadly is the only one working for my hardware. Anyway, I didn’t mention it because it’s irrelevant for my question. That’s why, and I repeat, I want USB Wi-Fi 5 adapters long [drivers kernel embedded long ago] known to work out of the box. Because yeah, USB Wi-Fi adapters do work, as I already mentioned I have a 2.4ghz Ralink USB Wi-Fi adapter which is, working fine.
how can we know ?
you're running some 3rd party OS "based on" LEDE, we have no idea what they included in the build.
as @bahtsiz_bedevi already told you, additional kernel modules have to be installed later, or manually added to the build.
what the people who built your image included, we don't know.
if it was proper LEDE/Openwrt only the bare must have minimum would have been included.
It appears you are using firmware that is not from the official OpenWrt project.
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
You may find that the best options are:
- Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
- Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
- Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).
If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.
Then the answer would be how to check WHAT is included in the build. I’m only looking for tips pointers and help. I was Only saying, if a Wi-Fi adapter was included in the kernel of ooenwrt very long ago it will be in this one. Just as my Ralink is included.
So how can one check what’s included in a builds kernel?
cat /proc/modules
It's not irrelevant, because driver modules are built against specific kernel version, you didn't mention it, then people assuming you are running official OpenWrt and answers will be given according to their knowledge on the official stable version. Even running the official OpenWrt in master snapshot branch you will be facing the same issue due to constant changing kernel version.
Since the forked version uses different kernel, then you can only rely on the driver modules being built according to the forked kernel version, or the compiled-in driver (from what you described it looks like Ralink USB driver has compiled in kernel or as module that's why it works OTB). Looking at the error message you posted, the forked version didn't build that driver module that's why you cannot install. You have only 2 options: (1) Ask the one who forked to include driver into their build; (2) Get the whole source from them, compile the image by yourself to include whatever you want.
2 Likes
This doesn't show everything, because something can be compiled into kernel, not as module.