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

Mercury MW150US V2 has some issues with this driver #15

Closed
fevenor opened this issue Oct 2, 2013 · 4 comments
Closed

Mercury MW150US V2 has some issues with this driver #15

fevenor opened this issue Oct 2, 2013 · 4 comments

Comments

@fevenor
Copy link

fevenor commented Oct 2, 2013

First of all, under the Ubuntu 13.04, OS can't display the signal strength.
Then, I can't use 'airmon-ng start wlan0' to make wireless card switch to monitor mode.One of possible reasons is that airmon-ng can't recognize the chipset because of the driver.
These problems can be resolved?
Thank you for your work!

@lwfinger
Copy link
Owner

lwfinger commented Oct 2, 2013

I do not use Ubuntu so I cannot replicate your strength issue. Where does the signal strength not show up? Using the kernel veersion of the driver as found in kernel 3.12, NetworkManager shows the strength.

It is known that monitor mode does not work. For me, that is a very low priority problem. If you find the fix, please send it to me; however, I will not be working on this problem.

@oldsharp
Copy link

My device is Mercury mw150us v2 too. It workd like a charm on my Ubuntu 13.04 desktop.

@jewsuscn
Copy link

My device is Mercury mw150us v2 too, when i up the interface wlan0 , Occurs error:
SIOCSIFFLAGS: Operation not permitted.

Ubuntu 13.08
Kernel: 3.8.13

@jewsuscn
Copy link

Anymore, I can not config the Mercury mw150us v2 work an a AP using hostapd in this website.

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

4 participants