Jump to content
rodrigocunha

[USB Wifi] Updated Ralink/Mediatek RT2870/ RT2770/ RT3X7X/ RT537X/ RT5572

315 posts in this topic

Recommended Posts

Advertisement

Has anyone managed to get this kext to work on an RT5360? Or is that significantly different from those supported by this kext (besides being that the one I mentioned ran off the PCI bus)?

Share this post


Link to post
Share on other sites

Has anyone managed to get this kext to work on an RT5360? Or is that significantly different from those supported by this kext (besides being that the one I mentioned ran off the PCI bus)?

 

This is a USB driver kext, i think it do not work for PCI devices...  :unsure:

Share this post


Link to post
Share on other sites

I am using rt2870 in yosemite with the above mentioned method, it connects but after 5-10 minutes there is no internet connectivity though it remains connected to the network...

Share this post


Link to post
Share on other sites

It doesn't work with my ASUS USB-N11 (VID: 0x1761   PID:  0x0b05) on Yosemite DP6

 

What I have done:

 

1. Copy prefPane

2. Copy kext

3. Run Kext Utility (it repair permissions and rebuild kext cache)

4. Reboot

5: ...... No Wireless Device Attached (((((

qogfx0.png

What I am doing wrong?

Share this post


Link to post
Share on other sites

It doesn't work with my ASUS USB-N11 (VID: 0x1761   PID:  0x0b05) on Yosemite DP6

 

What I have done:

 

1. Copy prefPane

2. Copy kext

3. Run Kext Utility (it repair permissions and rebuild kext cache)

4. Reboot

5: ...... No Wireless Device Attached (((((

qogfx0.png

What I am doing wrong?

 

Boot with "kext-dev-mode=1"

 

Copy mavericks kext to /System/Library/Extensions

 

Repair permissions and rebuild kext cache.

 

Reboot

 

Try to connect.

 

hint: Use this script to repair and rebuild: repairrebuild.zip

Share this post


Link to post
Share on other sites

So,
 
1) I found that command

sudo nvram boot-args="kext-dev-mode=1"

 
2) Reboot
3) Check that "kext-dev-mode=1" is ON
 

nvram -p

 
4) Copy Ralink-kext to /S/L/E
5) ....and see message: "The system extension cannot be use" after few seconds.
6) Sorry ((
 

Share this post


Link to post
Share on other sites

So,

 

1) I found that command

sudo nvram boot-args="kext-dev-mode=1"

 

2) Reboot

3) Check that "kext-dev-mode=1" is ON

 

nvram -p

 

4) Copy Ralink-kext to /S/L/E

5) ....and see message: "The system extension cannot be use" after few seconds.

6) Sorry ((

 

 

You are almost there! :)

 

Now repair permissions, rebuild kext cache and reboot! 

Share this post


Link to post
Share on other sites

repair permissions:

 

sudo chown -R 0:0 /System/Library/Extensions/*

sudo chmod -R 755 /System/Library/Extensions/*

sudo chown root:admin /

 

rebuild kext caches:

 

sudo kextcache -system-prelinked-kernel

sudo kextcache -system-caches

Share this post


Link to post
Share on other sites

I have a TP-link WN727N (RT5370) and Yosemite DP6 done everything here except I am using Clover injector and it isn't detected by the prefPanel utility, nor the Wifi icon appears, however its LED is blinking before this it was off.

 

Thanks

post-767483-0-44168800-1409646482_thumb.png

Share this post


Link to post
Share on other sites

I have a Tenda USB Wifi with RT5370.

 

I can confirm this drivers are working with Yosemite DP7, installed the kext using kextwizard and connected using the provided pref pane.

 

 

Getting 50mbps down 30mbps up.

Share this post


Link to post
Share on other sites

I have lion 10.7.3 and install with kextwizard in s/l/e, repair permissions and rebuild cache, but is off.

Muy product id is 0x7601

I buy un china without trademark...only i know that it's rt5370 ralink

Share this post


Link to post
Share on other sites

hey, this stuff works perfectly on yosemite dp8. thx a lot!

 

is there any way to set up connection to a specific network at start?

as there are some open networks in my area and it connect automatically to one of them and after every start I have to manually change networks.. 

Share this post


Link to post
Share on other sites

Yes you are right ! Thanks for the eye !

 

And it is working with OSX 10.10 DP8 automatically ( with profil drawer/connect order of my SSID) with my Dlink DWA 140 rev B1  USB dongle  !   :thumbsup_anim:

 

post-305243-0-34609300-1411771035_thumb.png

 

How it works for me:

  1. I took Dlink Utility prefpane v 2.6.4 from latest  "DWA-140_drv_RevD1_MACOS_4-2-9-4_UI_2-6-4-0_all_en_20140806.zip"
  2. Installed with Pacifist : Statup items folder in S/L/StartupItems

 

Then took with Pacifist :

  1. RT2870USBWirelessDriver.kext v 5.01.09 from  "MT7610U_D5.0.1.09_SDK1.0.2.10_UI5.0.0.15_20140822.dmg" from here http://www.mediatek.com/en/downloads/     and installed it with Kext Wizard
  2. And took RaWLAPI.framework and put it in S/L/Frameworks
  3. Rebuild cache and permissions with Kext Wizard v 3.7.10

    ;)

attachicon.gifDWA-140_drv_RevD1_MACOS_4-2-9-4_UI_2-6-4-0_all_en_20140806.zip

 

Share this post


Link to post
Share on other sites

thanks works perfectly by using kext utility

Share this post


Link to post
Share on other sites

Good with my USB Buffalo WLI-UC-G300N on yosemite with VID:0411/PID:016F, i much change hex to dec PID:016F to 367, i was edit info.plist.

 

Thanks!

Share this post


Link to post
Share on other sites

This works great. Thank you!!

 

I did notice that after you restart the machine, the wireless does not connect automatically.

Any way to fix that?

 

Thanks!

Share this post


Link to post
Share on other sites

 

Any way to fix that?

In System preferences you should have the D-link Utility preferencepane !

 

If so, ok , you open it and clik "Open Profile Drawer"

 

In "Connect Order" window which slides left you click on +

Chose your default SSID Wifi network

Authentification and security:

Chose your Authentication Type

and password

click ok

 

Now you should ( wich is my case ) have automatically at every reboot connecton on your default SSID Wifi network !

 

Good luck

Share this post


Link to post
Share on other sites

This solution works great.

 

I have one query: how can I disable/re-enable the Wifi or disconnect from a connection, without rebooting or unplugging the USB Wifi dongle?

Share this post


Link to post
Share on other sites

In System preferences you should have the D-link Utility preferencepane !

 

If so, ok , you open it and clik "Open Profile Drawer"

 

In "Connect Order" window which slides left you click on +

Chose your default SSID Wifi network

Authentification and security:

Chose your Authentication Type

and password

click ok

 

Now you should ( wich is my case ) have automatically at every reboot connecton on your default SSID Wifi network !

 

Good luck

That's actually what I did when I first set it up but no luck... I still have to activate the profile every time I reboot. 

Maybe I just didn't install the drivers properly? 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MikixIT
      Salve a tutti ho installato OSX, Sierra 10.12.6 (16G29), grazie a questo forum
      Ho installato tutti i Kext necessari da Nvidia a quelli per l'audio HDMI,ethernet ecc..
      L'unico problema che  Mouse e tastiera USB collegati ad un hub FUNZIONANO, mentre senza hub usb non funzionano nelle altre porte, NELLE ALTRE PORTE PERO' FUNZIONANO PEN DRIVE USB,ho provato vari kext in rete mentre il Forum era in manutenzione
      Ma non riesco a farli funzionare su altre porte,vi allego La mia EFI( http://www.mediafire.com/file/mimomvp1on4ys58/EFI-MikixIT 12%3A03%3A2018.zip) E vari screen del mio OSX con info varie




    • By ITzTravelInTime
      Questo è il thread in italiano dedicato alla mia app TINU, l'app open source che ho creato per creare chiavetta di installazione di mac utilizzando il metodo "createinstallmedia".
      Il nome è l'acronimo di TINU Is Not U (Per le regole del forum devo censurare, ma la U si riferisce ad un programma che piu o meno svolge lo stesso scopo che per buoni motivi è bandita su questo sito, il punto del metterlo nel nome sta nel sottolineare che la mia app è totalmente diversa)
      L'app è pensata per essere molto semplice ed immediata da usare (con un interfaccia grafica progettata con criteri e metodi usati in ambito professionale per lo sviluppo di applicazioni utente) e per essere molto solida e stabile che funziona sempre al primo colpo (a differenza di altri tool che conosciamo ...)
       
      A livello funzionale quest'app non è altro che un interfaccia grafica per il metodo da terminale "createinstallmedia" che viene sfrutatto dalla stessa per creare la chiavetta, quindi le chiavette create con TINU sono chiavette al 100% vanilla come se le aveste create dal terminale, l' applicazione, rispatto al metodo da terminale, aggiunge però funzioni utili come il controllo ed il riconoscimento di errori nel processo, la formattazione automatica della chiavetta USB che si sceglie di usare in formato Mac OS Extended (journaled) (detto anche HFS+) con mapatura di partizione GUID, ed anche altre opzioni personalizzabili o disattivabili come l'applicare un icona alla chiavetta di instalalzione.
      Tra gli altri vantaggi troviamo il fatto che permette di creare chiavette utilizzando qualunque applicazione di mac che contiene l'eseguibile "createinstallmedia" inclusi installer delle beta ed installer appena rilasciati, e non richiede di fare cose particolari prima come formattare la chiavetta e cambiare lingua al sistema e puo utilizzare applicazioni di mac che si trovano in varie directory nel sistema e non solo quelle che stanno nella cartella delle applicazioni ed hanno un nome specifico (nota che l'applicazione di installazione di mac deve essere quella interacche pesa diversi gb e non quella da pochi mb che l'app store puo scaricare alcune volte e che non contiene tutto quello che serve per permettere a createinstallmedia di funzionare)
       
      Tra l;e altre cose quest'app è l'unica app di questo genere sviluppata e che continua ad essere sviluppata in Italia ed è anche l'unica completamente open source.
       
      Trovate qui alcuni link utili:
       - Scarica l'app:                                                  https://github.com/ITzTravelInTime/TINU/releases
       - Codice sorgente dell'app:                                 https://github.com/ITzTravelInTime/TINU
       
       - FAQs (Domande fatte di frequente, in inglese):   https://github.com/ITzTravelInTime/TINU/wiki/FAQs
       
       - Thread in inglese su tinu (English thread about TINU): http://www.insanelymac.com/forum/topic/326959-tinu-the-macos-install-media-creation-tool-mac-app/
       
      Qui invece ci sono un paio di guide (Anche se l'app è molto facile da usare):
       - Piccola guida su come usare TINU per un hackintosh:                                   https://www.youtube.com/watch?v=Ug1yBZybpD4
       - Piccola guida su come usare TINU per creare cheiavette per Mac "originali":    https://www.youtube.com/watch?v=fZOZOUt2ErM
       
       
      Pianifico molte altre nuove funzioni per future versioni dell'app (vedi il thread in inglese per saperne di più)
       
       
      Il supporto a clover in TINU è pianificato per una versione futura, anche se dei protipi a livvello codice per renderlo possibile, sono gia stati sperimentati con successo.
       
      Spero che anche voi del forum italiano aprezzerete questa app come gli utenti del forum inglese, per idee e suggerimenti, siete liberi di esprimervi :-)
       

    • By ITzTravelInTime
      Hi guys, this thread is to show you a new and open source app, created by me, that I called TINU:
       
      The name means: TINU Is Not #####, the U refers to a popular software that is used to create Mac OS hackintosh installers (that for good reasons is banned on this forum), but the aim of the name is to explain that this app is a totally different thing from that software and works in a totally different way.
       
      This app basically is a graphical interface for the createinstallmedia executable that is inside the Mac OS installer apps, it is capable to create a Mac OS installer on a drive completely vanilla like what you do using the command line method, and also this method is recommended by apple itself. In addition to this, this app provvides also to you some customization features and a better management of the hall macOS isntall media creation process
       
      Allows you to create easily a macOS install media without messing around with command line stuff and without using disk utility, all you need to do is use the app and then install clover on the usb drive once TINU has finished or leave it as is you want to use it on a Mac.
       
      Features:
        - Simple to use UI that allows you to easily start the macOS install media creation process
        - It can work with every Mac OS installer app that has the createinstallmedia executable inside of it's resources folder (including also beta and newly released installers)
        - You can use any drive or partition you want that can be erased and is at least 7 GB of size
        - Works on Mac OS recovery, so you can create a macOS install media from a bootable macOS installer or from the macOs recovery, and you can use TINU to install macOS too.
        - All vanilla, the macOS install medias created with this tool are 100% vanilla, just like you created them using the command line "createinstallmedia" method in the terminal, with also some extra optiona features
        - Open source, you will know what this program does on your computer and also you can create your own version by downloading and playing with the source code
        - Does not requires to do anything of special first, just open the program
        - No need to go in disk utility first, TINU can format your drive for you
        - Uses recent and more modern APIs and SDKs and Swift 3 language
        - Transparent graphics style available (use alt + s on the keyboard or View->Use transparent style)
        - Works using the latest versions of macOS and will also support newer Mac installers out of the box without needing for an update
        - Advanced section, to customize your macOS install media
        - Installer customization: Kernelcache/prelinkedknerel and boot files replacement (a feature that can be handy while dealing with old Macs or with beta installers when you need to mod or change the boot files some times)
        - Clover EFI folder installer
       
        Features that are planned for some future versions:
        - Integrated EFI partition mounter tool (TINU can already mount EFI partitions from version 2.0, but a dedicated section which allows to mount every EFI partition in the system will be added)
        - Install clover and configure clover
        - Install kexts inside the kexts folder of clover
        - Clover drivers customization
        - Use custom dsdt in clover
        - integrated pre-made clover config templates database from a remote and open repository
        - Support for other languages, at least Italian   Rquirements:  - A computer that runs Mac OS X Yosemite or a more recent version (Mac OS X El Capitan is required to use TINU in a macOS recovery or installer)  - A drive or a free partition of at least 7 GB that you want to turn into a macOS/Mac OS X installer  - A copy of a macOS/Mac OS X installer app (Maveriks or newer versions are supported) in the /Applications folder or in the root of any storage device in your machine (excepted the drive or volume you want to turn into your macOS install media)   Note that this app is under the GNU GPL v3 license so any reuse of the source code must follow the license's terms   Latest stable TINU release:   Download the app:                                https://github.com/ITzTravelInTime/TINU/releases   View the source code:                            https://github.com/ITzTravelInTime/TINU       Frequently asked questions about TINU:  https://github.com/ITzTravelInTime/TINU/wiki/FAQs     NOTE: if you have problems with your USB installer of 10.13.4 or newer version not being detected by clover you have to use the latest clover and if it still does not detectets your usb installer you have to remove the invivible file called .IAPhysicalMedia located into the root of the usb installer. This issue is caused by a changement in the apple's createinstallmedia, don't blame TINU for that, TINU does only uses the installer creation method from apple, which has been changed by appleitself, causing this problem for hackintosh users some times, this issue should be resolved in the latest versions of clover which will no longer require that you do changements to let your usb dive to be detected, a setting to do this fix automatically in tinu is also present TINU in the adavnced settings, starting from the version 2.0 of the app. I leave also some screenshots as well
       
       
       
       
       
       
       
       

    • By rio2
      I recently installed High Sierra on my Ryzen system, just to find out how crappy the USB situation really is on AMD systems. The only choice is basically most of your ports flat out not working or GenericUSBXHCI crashing every time you pull out a thumbdrive. So after some trial and error here are my findings.
      The USB ports controlled by the XHCI controller on the SoC worked fine, but the ones attached to the chipset XHCI controller didn't.
      That's when I looked at the log and saw these lines:
      PTXH@00000000: AppleUSBXHCIPCI::createPorts: port 1 unsupported protocol USB 03.10 PTXH@00000000: AppleUSBXHCIPCI::createPorts: failed to allocate port 1 It turns out that for some reason the AppleXHCIPCI driver doesn't support the first two ports on the B350 chipset (made by ASMedia) USB controller. And after the driver fails to allocate port 1 it just stops and doesn't even look at the rest of the ports. So I first tried commenting out the first two ports from the DSDT and that worked and made all the other ports show app in the IOService tree. Than I quickly tested all the USB ports and it turns out that the 2 problematic ports aren't even wired to anything. But instead of editing the DSDT I wanted a cleaner solution, because I don't want to re-edit my DSDT every time I update the BIOS or change some BIOS settings.
       
      So here is my small SSDT that disables the stock PTXH device and adds a new device XHCI, that has all the ports needed for my board (ASUS PRIME B350-PLUS).
      DefinitionBlock ("SSDT-PRIME-B350-PLUS.aml", "SSDT", 1, "APPLE", "tinySSDT", 0x00000006) { External (\_SB_.PCI0.GPP2, DeviceObj) External (\_SB_.PCI0.GPP2.PTXH, DeviceObj) Scope (\_SB_.PCI0.GPP2.PTXH) { Name (_STA, Zero) } Scope (\_SB_.PCI0.GPP2) { Device (XHCI) { Name (_ADR, Zero) Device (RHUB) { Name (_ADR, Zero) // USB3.1 back panel Device (PRT1) { Name (_ADR, 0x5) Name (_UPC, Package (0x04) { 0xFF, 0x03, Zero, Zero }) } Device (PRT2) { Name (_ADR, 0x6) Name (_UPC, Package (0x04) { 0xFF, 0x03, Zero, Zero }) } // USB3.0 front panel Device (PRT3) { Name (_ADR, 0x7) Name (_UPC, Package (0x04) { 0xFF, 0x03, Zero, Zero }) } Device (PRT4) { Name (_ADR, 0x8) Name (_UPC, Package (0x04) { 0xFF, 0x03, Zero, Zero }) } // USB2.0 Device (PRT5) { Name (_ADR, 0x9) Name (_UPC, Package (0x04) { 0xFF, Zero, Zero, Zero }) } Device (PRT6) { Name (_ADR, 0xa) Name (_UPC, Package (0x04) { 0xFF, Zero, Zero, Zero }) } Device (PRT7) { Name (_ADR, 0xb) Name (_UPC, Package (0x04) { 0xFF, Zero, Zero, Zero }) } Device (PRT8) { Name (_ADR, 0xc) Name (_UPC, Package (0x04) { 0xFF, Zero, Zero, Zero }) } Device (PRT9) { Name (_ADR, 0xd) Name (_UPC, Package (0x04) { 0xFF, Zero, Zero, Zero }) } Device (PRTA) { Name (_ADR, 0xe) Name (_UPC, Package (0x04) { 0xFF, Zero, Zero, Zero }) } } } } } Please note that this is just an example and it most likely needs to be changed for your board.
    • By LarryKu
      Hi everyone,
      I am new, I hope I am posting in the correct forum.
      My specs:
      Processor: Core i5 6500 Skylake 3.2ghz
      Mobo: Gigabyte h170-d3h
      M2SSD: WD Black 256gb PCIe (Mac OSx)
      SSD: Samsung 860 Evo (WIndows 10)
      HDD: WD Blue 1TB
      GPU: Radeon RX 480
      Monitor: BenQ RL2460 24"


      I was able to install High Sierra on a new m2 drive, that I added to the above configuration with windows 10 already installed.
      I had a few issues during install, including the monitor turning off at boot screen.

      Unfortunately, this persists even now. It turns off at about 60% of the progress bar, and to turn it on again I have to unplug/plug back my hdmi.
      Additionally, while all of the usb ports worked during install and while running it out of the clover I had on the usb stick, only the rear ones appear to work now.
      The audio doesn't work either, though I added the correct patch according to my mobo

      Lastly, my other drives are not recognized in the bios anymore. They run fine from boot override but they don't show up in the boot priority (while multiple entries of mac OS do, and they seem to increase in number at every reboot)

      Thanks in advance for the help
×