OK so I have been using the SiLabs driver from
June 24, 2015 in conjunction with 10.11.2 when this problem refused to acknowledge the previous SiLabs driver v. 4.1.1, March 17, 2015 any longer.
SiLabs driver v. 4.1.1, March 17, 2015 is my nemesis and that was where all my current problems began, my puter will not recognise or load that driver whatsoever but I installed the newer driver back then on 10.11.2 and all was fine until 2 weeks ago.
Murphy's Law and I are the best of friends
![[banghead]](https://athena.trixology.com/Smileys/default/banghead.gif "Bang Head")
I'd also like to state that these are my personal problems and all comments I've made are pertaining to me and my personal situation/setup. I should have put more thought into the heading of the thread, and opened my first post with this line. I have seen a few others with this problem and they've troubleshot it with a hub. I'm thinking of buying a MeteoBridge if this happens to this extent again. I'm not a tech head and from what I struggled thru, everything is pointing to my computer and Apple deactivating any SiLabs kernel after 30 mins.
The
June 24, 2015 SiLabs Driver worked flawlessly for me after this happened even while I upgraded thru to 10.11.3 and 10.11.4 which I upgraded a week after their respective releases and without a single problem until 2 weeks ago. OH and this is why I upgraded to that driver, I forgot to mention that when this happened the first time while I was on 10.11.2, it actually did state in the SiLabs
release notes that 10.11 was included BUT that vanished very quickly, literally the next day, so that is why I installed and used the modified June 24, 2015 driver, it did not state it supported El Capitan though just the numbers 10.11, but hey, the timing? Returning to read up further once things were running smoothly the next day, I noticed that it was back to supporting 10.9 and 10.10 instead of 10.10 and 10.11?
? QUANDARY. .
Thanks to everyone who's listened to my non tech idiot ramblings, I really appreciate it. It's just that WC works so well for me I never really have a need to come in here. I do however desperately need help getting my station online but only for WC users. I'm not having a pity party or looking for ANY sympathy here either but this would never have been a problem for me until I fell I'll 6 years ago and it has messed with my cognition so badly that the simple things in life that I took for granted are now long arduous tasks. However my memory might be shot but like today I remembered this information above and I also just remember that why. That day I could not find a fresh copy of the SiLabs driver v. 4.1.1, March 17, 2015. I was told that once that if a kernel is rejected the root cert. is blocked and you need a new one (I conceded 100% that I have no idea how true this is so I dug around for my old Davis software to find the copy and that wouldn't work either. It was the original from that, that had failed)
Thanks for the 10.11.5 upgrade tip, I didn't know it was released yesterday and normally I'd wait a week or two just to see what might pop up.
WC is now running on 10.11.5 with
SiLabs Driver 4.10.7 Last Modified: 27/02/2016 and has been going strong for 9-HRS straight now. Aside from once since this happened the average cutoff time before my SiLabs Driver was switching off was 30-40 minutes max, but once I got 3HRS out of it. I'll keep you posted if it crashes again
Special thanks to all but especially xairbusdriver If I hadn't tried safe mode last week, I'd have lost more than a weeks data when it all began.
One clue is that things seem to work in Safe Mode. As you probably know, Safe Mode disables all non-Apple extensions/kernels and even some of Apple's own. That's one of its two main purposes.
Thank you so much, I didn't know that was the reason why it was allowing me to collect my data. That is one very, very valuable piece of information for me. xo
Since others here are not reporting this problem, even with 10.11.4, I'd say it's safe to say the problematic extensions are not from Apple; everyone else is operating with all of Apple's code with that OS, including me (I'm using v. 4.1.1, 3/17/15 of the SiLab driver).
Actually, not to be rude xairbusdriver, but there are others with this problem, but only on this one point. It also doesn't seem to matter which version of 10.11 they're running either, they have used a hub.
However, it is very likely that you have accidentally or intensionally installed an extension directly or installed a non-Apple app that then installed an extension that is causing this problem. The solution, then, is to find that app or extension.
The horror, seriously I'm not joking!
That may not be enjoyable, but it can be done with patience and attention to details.- Is there any critical software on that
mini(oops, I now see it's a MBP, probably lots of "critical software on it! )? - How much work are you willing to put into the effort?
[/b]
Hmmm the thought of going thru my software makes me feel violently ill. Is there somewhere in sys report or another way to collate data as to what software I have installed that is either hiding or is off aside from extensions? I have actually deleted loads of software, older versions of Aperture, Lightroom, Photoshop, Nikon, etc. . . and cleared my SSD of 750GB which was at 700GB down to 400GB to no avail. I'll just have to keep going.
LOL yes not
mini I have a 750GB SSD and 2x6TB LaCie LittleBig's and loads of critical photographic software, mostly Abode software, except for plug-ins and FCPX with plug-in's, which is finally cooking with gas after years upgrades. My Camera is a Nikon D800 and the Raw files are 80MB, if I shoot in tiff mode they're around 210MB each so doing time-lapse = massive memory. My computer fills up so quickly it's ridiculous and par for the course, things go haywire quickly when this happens but I just can't find what is causing
ONE out of so many kernels to keep shutting off.
HOWEVER, as I have been quite ill this last month the only things I have d/l'ed have been audiobooks, I had not downloaded a single thing for at least two weeks before this happened?
Cheers to all and thanks again.
Paul
