Issues installing usb driver in OSX
Posted by: Evan Scheele on 05 April 2018
Hello all,
I’ve never had any issues installing any of the previous updates in the past few years on my SuperUniti, UnitiQutes and 272 until today. I’m attempting to update my 272 from 4.4 to 4.6, and for some reason, I can’t get the driver to show up in the naim updater app or under OSX system report>hardware>usb. I’ve tried reinstalling the driver several times. I’m running OSX10.11.5 and have used this same machine to update my products in the past, though with earlier versions of the OSX operating system.
Any thoughts on what else I might try? Rather perplexed, as it’s always been so easy for me in the past.
Regards,
Evan
Are you using the same cable you used last time you successfully updated?
Also, have you rebooted your Mac after reinstalling the driver, and searched for the driver while the cable is connected?
Thanks for your response, CHRISSU. Yes, I always use the same usb to mini usb cable for updating. I haven’t rebooted my computer since installing the driver, but now it’s suddenly showing up under the OSX system report, so there’s progress! Only the naim updater app only shows one option for the serial port: ‘Bluetooth incoming port”. So I’m halfway there...
Thanks,
Evan
To clarify; the driver shows up in the operating system, but the naim installer app can’t see it in the serial port dialogue. I’ve rebooted the computer, trashed and reinstalled the naim updater app and unplugged the usb cable. Not sure what to try next..
Just tried a second usb cable from an external hard drive (which I know works) just to eliminate the remote possibility that the cable was bad. Still no luck, unfortunately.
I'd double check your network connections. I downloaded the installer and plugged in the usb cable - in doing so I think I'd dislodged the ethernet connection to the streamer - result no sign of the driver in the serial port dialogue. Eventually unplugged NDX and moved it next to Mac, plugged in the same connections (though different cables) and everything worked OK.
Thanks, MFAN. I thought of that and tried a different Ethernet cable and also tried a couple different Ethernet ports on the switch just to be thorough. Still no luck. Does anyone know if there’s any way to test continuity of the mini usb on the 272? It occurs to me that there could potentially be a problem there? (Hope not!)
Regards,
Evan
You need to start the Naim installer while the usb cable is connected to BOTH the Mac and the Naim streamer. Have you done that? I'm pretty sure I'm remembering this right...that if it's not ALL connected up when you run the Naim installer, you won't see the right port in the drop-down list in the Naim installer.
Hi,BART!
Yes, I’ve been doing that. The usb cable has been connected to both the 272 and the Mac the whole time. I’ve just tried unplugging and replugging the usb to see if that makes a difference. After I do that, I quit and relaunch the naim updater app with the cable connected to both the streamer and the Mac. No dice so far, unfortunately. Thanks for the suggestion, though! A bit of a mystery.
Best regards,
Evan
HI Evan,
Maybe try a SMC reset. It may help with USB connection/detections issues.
I cant really help as I had exactly the same issue and despite trying an imac and a macbook pro I couldn't get the drivers to be recognised. In the end I dug out an old windows laptop running Win 7. I cant say I am overly impressed with the process.
Having issues here too, but using RS232, I must have an old NDX (it has been upgraded to 192 compatibility) Using a MacBook Pro, RS232 recognized by the MacBook pro in about this mac as a serial controller but can never get any port in updater app other than bluetooth-incoming-port. I assume cable is ok as the usb driver doesn't show unless the cable is plugged in. Anyone done this successfully with RS232 on Mac ?
Evan Scheele posted:Hello all,
I’ve never had any issues installing any of the previous updates in the past few years on my SuperUniti, UnitiQutes and 272 until today. I’m attempting to update my 272 from 4.4 to 4.6, and for some reason, I can’t get the driver to show up in the naim updater app or under OSX system report>hardware>usb. I’ve tried reinstalling the driver several times. I’m running OSX10.11.5 and have used this same machine to update my products in the past, though with earlier versions of the OSX operating system.
Any thoughts on what else I might try? Rather perplexed, as it’s always been so easy for me in the past.
Regards,
Evan
Hi Evan Scheele,
See this post:
https://forums.naimaudio.com/to...06#75060766877326106
Hope it helps,
Will
Thanks, Will.
When I read your link, I was hopeful that this would solve it. Unfortunately, I have nothing listed under “disabled software” in the System Report.
I may just sit this one out, despite the improvements in sound quality. I now understand other’s frustration with the process in the past!
Regards,
Evan
Did you see the rest of my linked post, with the URL for the latest version of the driver and the bit about the .pkg?
The pack of an entry in System Report (which may only show up when the computer is connected to the 272) points to a problem before things get as far as disabled software.
It'd be a shame if you did forego the update, as it has met with particular acclaim from 272 owners, myself included.
There's always the last resort of taking it to a dealer - they should be able to sort it for you quickly & easily.
No, I didn’t see the bit about the latest version of the driver; where is it in the thread?
Just to clarify; the driver does show up in the system report, just not in the installer app.
I just decided to try again this time using my MacBook running OSX10.10 and successfully installed the driver, which shows up in the system report, nothing under ‘disabled software’ but the naim app doesn’t see it on this machine either.
I may try my son’s huge gaming PC, but I’d have to take the 272 out of the system to do so.
I don’t have a dealer in the Boston area, so that’s not a possibility.
Regards,
Evan
Evan Scheele posted:No, I didn’t see the bit about the latest version of the driver; where is it in the thread?
It's right there in the post that Will linked to, in the quoted part.
Unfortunately, if the software is showing up in System Report and nothing's been disabled, I'm not sure that it'd help. Worth a try though.
One other thought - in the driver download, there was the .pkg for the newest driver (which it sounds like you've installed), and also a folder called legacy drivers or something like that. ISTR that I went into that folder and installed those too. Don't know if that's what made the difference.
Unfortunately I'm no Mac wizard, so other than the above and probably some blind luck, that's as much help as I can offer.
Next stop must surely be Naim support.
Yes, I did see the legacy driver folder, and I installed that as well the regular one on the iMac, but I didn’t try installing it on the MacBook. Perhaps I’ll try tonight. Not very hopeful, really. It seems that the 272 doesn’t like the Mac version of the installer, whereas the SuperUniti had zero issues.
Really reluctant to power the system down when it’s sounding so good, only to potentially find it won’t install successfully via my son’s PC either.
Suppose I should contact Phil, but I’m getting sick of this and don’t really want to start over explaining the whole thing to him, to be honest.
Regards,
Evan
Evan - I'm with you on that. I installed a driver for my Rs232 cable which actually prevented the MacBook Pro from finishing its boot sequence. Have had to repair at the OS level to get the MacBook working again. I get the security on Mac's is tight, but some view from Naim on what drivers tested well for RS232 would have been appreciated. I work in tech but am reluctant to keep trying cables and drivers at random, especially after one MacBook Pro rebuild.
Anyone have success with RS232 ? which cable and driver were used ? Cheers.
I’ve used the RS232 interface successfully on two UnitiQute 1s in the past, but it’s been so long that I’ve forgotten the specifics re: the driver. I know that the cable had a chip in it and came from Amazon on the advice of forum members. Perhaps a search would yield the information.
Best,
Evan
Thanks for all of your suggestions, guys. But I’m giving up. Reached out to Phil for guidance, but really don’t have much faith that he can solve the issue remotely. The software is beyond flakey when some have zero issues and others have no success on the same platform, despite hours of troubleshooting.
Glad so many of you are having success with the update and are enjoying what is apparently a significant improvement in sound quality. Wish I was enjoying it with you!
Best regards,
Evan
OK, I am having the identical problem. I am running OS X 10.13.3 and it looks like the problem is that the usb serial converter is trying to install itself in /Library/Extensions, however the new operating systems require some subfolder. And you can't just copy the driver into that folder or it invalidates the installation. In the last update I was able to force it to work by opening a terminal window and typing: sudo kextunload SiLabsUSBDriver.kext/ which this time says:
(kernel) Kext com.silabs.driver.CP210xVCPDriver not found for unload request.
Failed to unload com.silabs.driver.CP210xVCPDriver - (libkern/kext) not found.
But with optimism in my heart and with true courage I entered:
sudo kextload -v 6 SiLabsUSBDriver.kext/
with the response
Kext user-space log filter changed from 0xff2 to 0xfff.
Kext kernel-space log filter changed from 0xff2 to 0xfff.
Requesting load of /Library/Extensions/SiLabsUSBDriver.kext.
/Library/Extensions/SiLabsUSBDriver.kext loaded successfully (or already loaded).
So it LOOKs like it is loaded. But when you check the system report is isn't listed. :-(
Now in answer to the inevitable questions from CHRISSU:
1) Yes I am using the same cable
2) No I didn't power cycle anything after installing the driver
3) No I didn't knock the cable.
I would really like to try the new update because I have been plagued by dropouts and I'm really hoping for a solution. I think the problem is that SiLabs claims to have a solution and Naim says to use that but it doesn't work. Naim will no doubt say that it isn't their problem but unfortunately we poor customers don't have any pull with SiLabs so could the people at Naim ask them for a solution on our behalf please (even though it isn't really your problem)?
Very interesting, Jack. Your knowledge far exceeds mine. But clearly, there is something wrong. Many of us are having issues updating via OSX, clearly. I’m curious, though; why are so many others on the Mac platform experiencing no issues with the update via the naim updater? Is it down to which version of OS X you happen to be running?
Ok, I have found something that works. Do each thing in this list exactly as I have typed it. Maybe print it out and cross each one off as you go.
1) Computer on and NDX on
2) cable between USB on computer and NDX
3) "Install" the usb driver from the Naim link (it won't work but we'll get to that)
4) Click on the little magnifying glass in the corner and when a window comes up type "Terminal" and return
5) shortly a little window will come up that you can type in
6) In the terminal window type "cd /Library/Extensions"
7) Type "sudo kextunload SiLabsUSBDriver.kext/"
8) It will ask you for the computer password, type it in (this gives it permission to do what you ask)
9) Type "sudo kextload -v 6 SiLabsUSBDriver.kext/" and it will respond with the helpful information that the driver is loaded
10) reboot the mac and power cycle the NDX (don't disturb the cable)
11) When both are up and running start the updater
12) This time the drop down list will show a third option for a USB driver
13) continue as per Naim instructions
You can close the command window but just to be safe just let the updater go about it's business, which for me took about 20 minutes
Good Luck!
There's no way people should be having such problems in updating their equipment. Who developed this mess to begin with? Was it Linn?
Silly question, have you tried Naim support? When I had an ND5XS I had a problem with an update, contacted them, and had a very quick response which got me going. Not saying my problem was the same as yours, but I’d ask them first.