Jump to content
syscl

[Guide] Fix issue of "Disk not ejected properly"

22 posts in this topic

Recommended Posts

Overview

On OS X/Mac OS X, some people may suffer from the issue that the external disk was not ejected properly after sleep. This problem dates back to the period of the coming of Mavericks, even on a real Mac!

post-950366-0-63441000-1458318999_thumb.png

 

 

Overview of the tools/solutions






AFAIK, there's two solutions to fix this problem till now: 

  • Install Jettison from Mac App Store.
  • Use sleepwatcher to unmount the external devices before system go to sleep.


But for me, install Jettison is not free of charge, and this application will place icon on the right corner of the statue bar once get installed, which is not a good solution from my point of view. 

The latter one is open source and free of charge, which means I can know clearly what this application/daemon has done and add as many functions I want to it. With the help of sleepwatcher, there's various script to unmount/mount disk upon sleep, but none of it is so easy to read and some require sleep time delay settings, that's really strange! That's the reason why I started to create my "own" version of script to fix this issue. I optimized the whole progress as well as the installation progress. No more wake/sleep delay time settings! No more complicated command line, no more wake script, just one sleep script for unmount the external devices, once you resume from sleep, all the external devices will mount by system spontaneously. After following this guide step-by-step, no more "Disk not ejected properly" error will occur upon sleep. 

 

Feel free to change whatever you want if you do not satisfy with my script: https://github.com/syscl/Fix-usb-sleep

 

How to use?

  • Download the latest fixUSB.sh by entering the following command in a terminal window:
git clone https://github.com/syscl/Fix-usb-sleep

Note: If it was the first you execute command "git", please install it by the tips from OS X online(Click "Install"), and then run the above command line again.

 

 

  • This will download the fixUSB.sh to your current folder (./) and the next step is to change the permissions of the file(add +x) so that it can be run:
chmod +x ~/Fix-usb-sleep/fixUSB.sh
  • Run the fixUSB.sh in a terminal window by:
cd ./Fix-usb-sleep
./fixusb.sh

If all this procedures have done correctly, you will see the following message in the terminal window

post-950366-0-25227200-1458318931_thumb.png

Hope you all enjoy this script and all feedbacks are welcome! Post issue on https://github.com/syscl/Fix-usb-sleep

 

Credit:

Bernhard Baehr (bernhard.baehr@gmx.de): without his great sleepwatcher, this project/script will not be created.

 

Share this post


Link to post
Share on other sites
Advertisement

My output doesn't seem to match yours... and it also seems to freeze after step 2 (been waiting 15 minutes).

See below. Any ideas?

 

 

iMac:~ xxxxxx$ git clone https://github.com/syscl/Fix-usb-sleep

Cloning into 'Fix-usb-sleep'...

remote: Counting objects: 132, done.

remote: Compressing objects: 100% (7/7), done.

remote: Total 132 (delta 0), reused 0 (delta 0), pack-reused 125

Receiving objects: 100% (132/132), 52.43 KiB | 39.00 KiB/s, done.

Resolving deltas: 100% (72/72), done.

Checking connectivity... done.

iMac:~ xxxxxx$ chmod +x ~/Fix-usb-sleep/fixUSB.sh

iMac:~ xxxxxx$ cd ./Fix-usb-sleep

iMac:Fix-usb-sleep xxxxxx$ ./fixusb.sh

Password:

OK  ]  Create /Users/simondavis/Fix-usb-sleep/tools/tools.

OK  ]  Download sleepwatcher.

Share this post


Link to post
Share on other sites

My output doesn't seem to match yours... and it also seems to freeze after step 2 (been waiting 15 minutes).

See below. Any ideas?

 

 

iMac:~ xxxxxx$ git clone https://github.com/syscl/Fix-usb-sleep

Cloning into 'Fix-usb-sleep'...

remote: Counting objects: 132, done.

remote: Compressing objects: 100% (7/7), done.

remote: Total 132 (delta 0), reused 0 (delta 0), pack-reused 125

Receiving objects: 100% (132/132), 52.43 KiB | 39.00 KiB/s, done.

Resolving deltas: 100% (72/72), done.

Checking connectivity... done.

iMac:~ xxxxxx$ chmod +x ~/Fix-usb-sleep/fixUSB.sh

iMac:~ xxxxxx$ cd ./Fix-usb-sleep

iMac:Fix-usb-sleep xxxxxx$ ./fixusb.sh

Password:

OK  ]  Create /Users/simondavis/Fix-usb-sleep/tools/tools.

OK  ]  Download sleepwatcher.

Try the latest one as my guide.

 

////

Share this post


Link to post
Share on other sites

Just wanted to say that this appears to have fixed the problem for me.  Thank you for putting this together!!!

 

 

10.11.6

Clover

GA-EP45-UD3P

Share this post


Link to post
Share on other sites

Just wanted to say that this appears to have fixed the problem for me.  Thank you for putting this together!!!

 

 

10.11.6

Clover

GA-EP45-UD3P

Feel free to star that project if it work then I can count how many people benefit from that project ;)

Share this post


Link to post
Share on other sites

Recent update log

 

2016-9-16

  • Fixed an issue that will potentially mount external EFI partitions see issue #5 by @brousseau6933
  • Fixed typo: "${gFrom}/tools" --> "${gFrom}"

2016-7-16

  • Switch to curl cmd instead of git clone cmd.

2016-5-26

  • Mount points at wake to fix MacBook issue #2 .

Share this post


Link to post
Share on other sites

Hey

I just tried this on my GA Z170X-Ultra Gaming and it doesn't seem to work. Mac Os Sierra 12.1

 

Share this post


Link to post
Share on other sites

Hey

I just tried this on my GA Z170X-Ultra Gaming and it doesn't seem to work. Mac Os Sierra 12.1

 

 

Hello, could you please provide some information under https://github.com/syscl/Fix-usb-sleep/issuesso that I can help you with your issue.

 

syscl

Recent update log

 

 

2016-12-08

 

  • credit ralexx's detail information such that I added patches to fix PCI/PCIe USB devices sleep issue

 

syscl

Share this post


Link to post
Share on other sites

Hey

I just tried this on my GA Z170X-Ultra Gaming and it doesn't seem to work. Mac Os Sierra 12.1

 

 

 

I too can confirm it does not work on Z170 Ggabyte Designaire.

Thanks for the feedback, please provide information like diskutil list when plug in external storage, I want to see what's wrong.

 

syscl

Share this post


Link to post
Share on other sites

Installed fine, but didn't work on my EliteBook. Sierra 10.12.2. diskutil list attached.

Thanks for the feedback, but I do not see there's possible issue.

 

Could you please provide more details, for example, diskutil info disk1, ioreg, something like that.

 

I may write a log version for your case to log out some information...

 

syscl

 

Share this post


Link to post
Share on other sites

Thanks for the feedback, but I do not see there's possible issue.

 

Could you please provide more details, for example, diskutil info disk1, ioreg, something like that.

 

I may write a log version for your case to log out some information...

 

syscl

 

 

Thanks. Files attached.

 

Console is a screenshot of console to see what happened when laptop went to sleep, not sure if that has any processes related to this, but the ones in it were the only ones that were related to disks.

 

ioreg.zip

install.rtf

console.zip

diskutil.rtf

Share this post


Link to post
Share on other sites

I will give it a try to find out if it resolved my issue with my USB external drive.

 

However if think that my problem is related to something other because , i want to boot from a multi partition external drive and get back all volumes after sleep.

 

If i boot from internal hd i have no trouble.

Share this post


Link to post
Share on other sites

I can also report that it is not working as intended on Sierra. When entering sleep on El Capitan, everything ejects and runs fine. However, on my separate installation of Sierra, I get the "Disk not ejected properly" warning that I had on El Capitan before I had installed this week. This and the Shiki Maxwell kext are the only things keeping me from switching to Sierra as my daily driver because El Capitan is so stable right now.

 

syscl, is there anything I can provide you that will help in diagnosing the problem? Specs are identical for installations because the machine is the same with two separate SSDs holding different Operating Systems. 

 

EDIT: CPU 6600K, GPU GTX 950, IGPU HD 530 (Disabled in BIOS), OS 10.11.6, 10.12.2

Share this post


Link to post
Share on other sites

@Amble @pippox0 @superchase9000 Thank you guys, I will see if there's something wrong. 

 

Though I don't know what change cause this disk eject issue on Sierra, but in my case(Dell Precision M3800 QHD+), there's no disk eject issue on Sierra 10.12.3.

 

If you have any clues, please don't hesitate to place here or place in my GitHub, I will look into it. But as for now, I am too busy refining 80.nvram script and some other stuff. 

 

I apology for my late reply.

 

Have a good day,

syscl

Share this post


Link to post
Share on other sites

great thank you, @syscl , working just perfectly on both, USB 2.0 and USB 3.0 drives in High Sierra 10.13.3. See my sig below for my rig.

However, I ran sudo ./fixusb.sh, then restarted because it did not work right away - restart was required (not sure if sudo was required, too, but obviously it did not hurt, either).

BIG THUMBS UP for you B)!

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 androidek
      Hi all,
      I am quite new to the Hackintosh world, but I have managed to complete my 1st project! I am running macOS 10.15.3 on Huawei Matebook X Pro and the whole experience is brilliant! I couldn't imagine it being so nice. However, there is one thing that keeps me away from perfection - Rewind, Play / Pause, Fast Forward function keys. Brightness (Up & down), mute, volume (up & down) all work.
       
      When I was trying to fix it, I followed this guide: https://www.insanelymac.com/forum/topic/330440-beginners-guide-fix-keyboard-hot-keys-functional-keys/. I have managed to read all of the key for their PS2 Scan Codes (see below my results). This the moment where it got weird - many keys showed key code for e077 (dead key): some showed e077 + sth else, some just showed e077, F8 showed ^ (e05b) + P (19) output (?). 
       
      Anyone knows what to do to fix it? I was trying to check info.plist in VoodoPS2Keyboard.kext, but i couldn't find anything abnormal.
      F1 default 21:00:16.749809+0200 kernel ApplePS2Keyboard::message: type=e0028010, provider=<private>, argument=<private>, argument=0405, cmp=e0028010 default 21:00:16.749830+0200 kernel ApplePS2Keyboard: sending key e005=6b down default 21:00:16.749851+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=bb192cd0, cmp=e0028010 default 21:00:16.749874+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=bb192cd0, cmp=e0028010 default 21:00:16.750025+0200 kernel ApplePS2Keyboard: sending key e005=6b up default 21:00:16.750047+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=bb1c3068, cmp=e0028010 default 21:00:16.750055+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=bb1c3068, cmp=e0028010 default 21:00:16.755856+0200 kernel ApplePS2Keyboard: sending key e077=80 down default 21:00:16.755872+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=bb74dccc, cmp=e0028010 default 21:00:16.755882+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=bb74dccc, cmp=e0028010 default 21:00:16.837083+0200 kernel ApplePS2Keyboard: sending key e077=80 up default 21:00:16.837109+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=c04b8af4, cmp=e0028010 default 21:00:16.837131+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=c04b8af4, cmp=e0028010 F2 default 21:02:31.795257+0200 kernel ApplePS2Keyboard::message: type=e0028010, provider=<private>, argument=<private>, argument=0406, cmp=e0028010 default 21:02:31.795277+0200 kernel ApplePS2Keyboard: sending key e006=71 down default 21:02:31.795295+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=2c6dda71, cmp=e0028010 default 21:02:31.795317+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=2c6dda71, cmp=e0028010 default 21:02:31.795480+0200 kernel ApplePS2Keyboard: sending key e006=71 up default 21:02:31.795495+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=2c70f7e2, cmp=e0028010 default 21:02:31.795514+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=2c70f7e2, cmp=e0028010 default 21:02:31.801352+0200 kernel ApplePS2Keyboard: sending key e077=80 down default 21:02:31.801367+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=2cc9fb61, cmp=e0028010 default 21:02:31.801382+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=2cc9fb61, cmp=e0028010 default 21:02:31.875499+0200 kernel ApplePS2Keyboard: sending key e077=80 up default 21:02:31.875513+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=31354dfb, cmp=e0028010 default 21:02:31.875521+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=31354dfb, cmp=e0028010 F3 default 21:02:48.417582+0200 kernel ApplePS2Keyboard: sending key e077=80 down default 21:02:48.417612+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=b305125, cmp=e0028010 default 21:02:48.417622+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=b305125, cmp=e0028010 default 21:02:48.483563+0200 kernel ApplePS2Keyboard: sending key e077=80 up default 21:02:48.483603+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=f1f656f, cmp=e0028010 default 21:02:48.483628+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=f1f656f, cmp=e0028010 F4 default 21:03:15.730716+0200 kernel ApplePS2Keyboard: sending key e020=4a down default 21:03:15.730731+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=672e63ea, cmp=e0028010 default 21:03:15.730742+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=672e63ea, cmp=e0028010 default 21:03:15.940107+0200 kernel ApplePS2Keyboard: sending key e020=4a up default 21:03:15.940135+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=73a8a99a, cmp=e0028010 default 21:03:15.940159+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=73a8a99a, cmp=e0028010 F5 default 21:03:32.144572+0200 kernel ApplePS2Keyboard: sending key e02e=49 down default 21:03:32.144602+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=3983a376, cmp=e0028010 default 21:03:32.144625+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=3983a376, cmp=e0028010 default 21:03:32.247670+0200 kernel ApplePS2Keyboard: sending key e02e=49 up default 21:03:32.247724+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=3faac337, cmp=e0028010 default 21:03:32.247747+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=3faac337, cmp=e0028010 F6 default 21:03:47.914743+0200 kernel ApplePS2Keyboard: sending key e030=48 down default 21:03:47.914772+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=e57ce68c, cmp=e0028010 default 21:03:47.914798+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=e57ce68c, cmp=e0028010 default 21:03:48.025031+0200 kernel ApplePS2Keyboard: sending key e030=48 up default 21:03:48.025069+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=ec1256ac, cmp=e0028010 default 21:03:48.025093+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=ec1256ac, cmp=e0028010 F7 default 21:04:01.788530+0200 kernel ApplePS2Keyboard: sending key e077=80 down default 21:04:01.788542+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=20702166, cmp=e0028010 default 21:04:01.788552+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=20702166, cmp=e0028010 default 21:04:01.878757+0200 kernel ApplePS2Keyboard: sending key e077=80 up default 21:04:01.878772+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=25d0aeb0, cmp=e0028010 default 21:04:01.878782+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=25d0aeb0, cmp=e0028010 F8 default 21:04:15.767036+0200 kernel ApplePS2Keyboard: sending key e05b=3a down default 21:04:15.767054+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=619edf64, cmp=e0028010 default 21:04:15.769768+0200 kernel ApplePS2Keyboard: sending key 19=23 down default 21:04:15.769787+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=61c94666, cmp=e0028010 default 21:04:15.769804+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=61c94666, cmp=e0028010 default 21:04:15.826931+0200 kernel ApplePS2Keyboard: sending key 19=23 up default 21:04:15.826961+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=65318160, cmp=e0028010 default 21:04:15.826976+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=65318160, cmp=e0028010 default 21:04:15.836602+0200 kernel ApplePS2Keyboard: sending key e05b=3a up default 21:04:15.836656+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=65c4971f, cmp=e0028010 F9 default 21:04:30.326219+0200 kernel ApplePS2Keyboard: sending key e077=80 down default 21:04:30.326246+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=c5680074, cmp=e0028010 default 21:04:30.326268+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=c5680074, cmp=e0028010 default 21:04:30.396501+0200 kernel ApplePS2Keyboard: sending key e077=80 up default 21:04:30.396529+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=c99a65fa, cmp=e0028010 default 21:04:30.396553+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=c99a65fa, cmp=e0028010 F10 default 21:04:52.887772+0200 kernel ApplePS2Keyboard: sending key e077=80 down default 21:04:52.887798+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=62edecb, cmp=e0028010 default 21:04:52.887820+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=62edecb, cmp=e0028010 default 21:04:52.957529+0200 kernel ApplePS2Keyboard: sending key e077=80 up default 21:04:52.957552+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=a57b252, cmp=e0028010 default 21:04:52.957576+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=a57b252, cmp=e0028010 F11 default 21:05:22.416218+0200 kernel ApplePS2Keyboard::message: type=e3ff8065, provider=<private>, argument=<private>, argument=4f5f1000, cmp=e0028010 default 21:05:22.416244+0200 kernel ApplePS2Keyboard::message: type=e3ff8064, provider=<private>, argument=<private>, argument=4f5f1000, cmp=e0028010 default 21:05:22.416265+0200 kernel ApplePS2Keyboard: sending key e037=0, 0=80 down default 21:05:22.416279+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=e6375744, cmp=e0028010 default 21:05:22.416296+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=e6375744, cmp=e0028010 default 21:05:22.517121+0200 kernel ApplePS2Keyboard: sending key e037=0, 0=80 up default 21:05:22.517139+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=ec3c1948, cmp=e0028010 default 21:05:22.517153+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=ec3c1948, cmp=e0028010 F12 default 21:05:47.899625+0200 kernel ApplePS2Keyboard: sending key e052=92 down default 21:05:47.899655+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=d5245c6d, cmp=e0028010 default 21:05:47.899678+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=d5245c6d, cmp=e0028010 default 21:05:47.991503+0200 kernel ApplePS2Keyboard: sending key e052=92 up default 21:05:47.991530+0200 kernel ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=da9f6ed4, cmp=e0028010 default 21:05:47.991554+0200 kernel ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=da9f6ed4, cmp=e0028010  
       
       
    • By Vyzantion
      I have just re-made the Catalina installer, with the updated OS. It could not install from it, like it could not copy. Then I have tried to reinstall Mojave, it worked pretty cleary last year the exact pen drive. It failed as well, saying something like: not package found, contact the system administrator. I was able to boot from USB pen drive Linux and install Windows from DVD. But no macOS from the pen drive, even from what worked fine before. I have reseted the BIOS several times, no succes. The first sign of something wrong was this: When I first tried to boot Catalina, it said something about BIOS (BIOS, not UEFI) reset and enter setup. I hapenned several times on my attempts. If something screwed in my hardware? The USB ports? The BIOS perhaps?
    • By Justin S
      I purchased two of these Sipolar 10 port USB 3.0 hubs with the thought I'd be able to plug in 20 iPads to do software restores simultaneously, but I only can get 12 to be recognized at any one time. Both hubs function properly with 10 iPads plugged in to each at once, but as soon as I connect both hubs I get a max of 12 iPads recognized by the OS. We're using Apple Configurator 2 to restore iPads, and I have a separate older/slower 32 port USB 2.0 charge/sync hub that works fine with all devices plugged in.
       
      Hub: https://www.alibaba.com/product-detail/Sipolar-new-a-423-10-port_62315150518.html?spm=a2700.icbuShop.41413.40.5aa8663dB1drT6
       
      I'm using a 2014 Mac Mini 7,1 running 10.15.3. I've tested the hubs with a few difference Macs and OS's and have had the same issue. From what I can tell these hubs use a RealTek USB chipset, but no drivers are offered by Realtek for them.
       
      I attempted to daisy chain them (not ideal) and still have the same issue. Has anybody run in to a similar issue using identical USB hubs connected to individual ports on a Mac?
    • By superdooper71
      Hi I wonder if you can help me out guys.
      I have few issues here
      • First
      when I boot the clover entry screen do not show the disk icons until i press enter
      (If I disconnect the keybord all is smooth, clover start, shows disk icons and boot from Mojave)
      • Second
      Randomly the keyboard and mouse become pretty unstable. The mouse cursor start flashing or the keyboard start to type repetedly <<<<<<<<<<< when i Press the spacebar or some other button
      (this behaviour is applied to all keyboard I have tried, actually 3 different ones)
      --------------------------------------------------------------------
      KB and Mouse are plugged on a USB 3.0 ports
      I have tried to reset the keyboard Pref but NO LUCK
      I have changed Keyboard - Same error
      --------------------------------------------------------------------
      I enclose IOREGregistry and config.plist
       
      MY CURRENT BUILD
      ASROCK Z270 PRO4
      i7 7700K
      32GB DDR4
      Gigabyte GTX 760
       
      I believe that there is some code conflict but I have no idea what is wrong
       
      Please HELP
      Cheers
      Franco
      config.plist
      iMac di imac27.ioreg.zip
    • By soumaxetuirk
      If you have a working Brightness Slider and you might be using Brightness slider or manual hotkeys to control brightness then this guide may help you to use your Native hotkeys of laptop.
       
      (All the Credits goes to @RehabMan     For OS-X-ACPI-Debug Kext and DSDT Patches.)
       
       
      This step assumes that you are using RehabMan's VoodooPS2Controller or Acidanthera's PS2Controller
      Install the kext: https://github.com/RehabMan/OS-X-ACPI-Debug Open MaciASL and click on patch.(Add rehab man repo) Apply "Add DSDT Debug Methods" and "Instrument EC Queries" that are under Brightness Fix. Save the DSDT and restart Look in Syslog as you press the key corresponding to brightness to determine which _QXX methods handle the keys (UPDATE: From Sierra Apple changed logging process. So you won't find ACPIdebug result using syslog command. Instead use following command )
      log show --last 5 | grep ACPIDebug 6. Then patch DSDT:
      into method label _Q1D replace_content begin // Brightness Down\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0205)\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0285)\n end; into method label _Q1C replace_content begin // Brightness Up\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0206)\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0286)\n end; Change the variable _Q1D/_Q1C as per the log. 

      7. Try compiling and check if it generates errors
      8. If it does, then change the PS2M to PS2X according to the one found in your DSDT
      9. Save and place the compiled DSDT.
      10. Now you should see that you have your corresponding keys to change your brightness 
       
       
       FOR  more detail and Queries,Check Out original Post of @RehabMan Here;
      http://www.insanelym...18#entry1997112
      Get Latest Version of  OS-X-ACPI-Debug kext here:
      https://bitbucket.org/RehabMan/os-x-acpi-debug/downloads
×