Posted: 4/25/2017 4:27:34 PM EDT
|
I'm sitting in a course for work 1800 miles away from home in Vancouver and my FUCKING USB ports decided to go on strike!!!! they will provide power but will not read anything. Ive tried multiple USB devices in both ports.
I've tried.... shift-control-option command-option-P-R they do nothing Macbook Pro, Sierra with no updates outstanding Ideas? |
.
|
This may be a dumb question, but what format are those USB thumb drives? FAT32? EXFAT? NTFS?
Are they even formatted? Are they known good? ETA Mount and Unmount Drives in MacOS Using a Terminal |
|
Quoted:
No I tried multiple times and it would not work Plug it in to power. Shut the machine off. Off-off. They actually take a while to totally shut down in some cases. On the left hand side of the keyboard, press and hold the shift, control, and option keys. Put your eyeballs on the power plug light, and press the power button solidly for a good second or two. The power cord light should change color. If the cord light doesn't change color, the SMC is not reset. |
|
Quoted:
OK, it's a weird thing to do, the machine is really picky about the way it wants it done. Sometimes it takes a few tries even when I know I'm doing it right, maybe it's the machine, maybe it's me. Dunno. Plug it in to power. Shut the machine off. Off-off. They actually take a while to totally shut down in some cases. On the left hand side of the keyboard, press and hold the shift, control, and option keys. Put your eyeballs on the power plug light, and press the power button solidly for a good second or two. The power cord light should change color. If the cord light doesn't change color, the SMC is not reset. |
| I will check this out when I'm done today |
|
Quoted:
I will check this out when I'm done today Quoted:
I will check this out when I'm done today It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. |
|
Quoted:
No real reason to do that, and it wouldn't fix the problem anyway. It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. I'm walking to the Apple Store after this is over today if I can get there on time |
| I'm all mac at home, but PC at work. I've never seen that on a Macbeth have seen on a PC. We have had iissues at work where older devices that have 1.1 ports do not communicate with the 3.0 ports on the newer PC's. Call apple, they have helped me and I don't pay for AppleCare. |
|
Quoted:
No real reason to do that, and it wouldn't fix the problem anyway. It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. Quoted:
Quoted:
I will check this out when I'm done today It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. If the issue is in the firmware, rolling back often band-aids the issue. |
|
Quoted:
Compatibility issues happen with "major" osx updates all the time. Google Sierra and USB drives and start reading the dev forum posts. If the issue is in the firmware, rolling back often band-aids the issue. Quoted:
Quoted:
Quoted:
I will check this out when I'm done today It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. If the issue is in the firmware, rolling back often band-aids the issue. Like I said, I fixed this just a couple of weeks ago on a mac, it wasn't the OS. |
|
Quoted:
Firmware has nothing to do with the version of OSX running on the machine. Like I said, I fixed this just a couple of weeks ago on a mac, it wasn't the OS. Quoted:
Quoted:
Quoted:
Quoted:
I will check this out when I'm done today It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. If the issue is in the firmware, rolling back often band-aids the issue. Like I said, I fixed this just a couple of weeks ago on a mac, it wasn't the OS. |
|
Quoted:
And if the SMC and PRAM aren't the issue, but the system utility sees the USB ports are occupied, there is something going on in the software. I know firmware updates are separate, but rolling back the os can make the issue go away. I've done it. Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
I will check this out when I'm done today It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. If the issue is in the firmware, rolling back often band-aids the issue. Like I said, I fixed this just a couple of weeks ago on a mac, it wasn't the OS. |
|
Quoted:
That's attempting to attack a small fly with an artillery cannon. Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
I will check this out when I'm done today It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. If the issue is in the firmware, rolling back often band-aids the issue. Like I said, I fixed this just a couple of weeks ago on a mac, it wasn't the OS. There's no sense in sending someone down every gopher hole when you can just flood the thing out. Rolling back or reinstalling an os is the the "have you tried turning it off and back on again?" of diagnostics. |
|
Quoted:
There's no loss of data if done properly just like an update. There's no sense in sending someone down every gopher hole when you can just flood the thing out. Rolling back or reinstalling an os is the the "have you tried turning it off and back on again?" of diagnostics. Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
I will check this out when I'm done today It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. If the issue is in the firmware, rolling back often band-aids the issue. Like I said, I fixed this just a couple of weeks ago on a mac, it wasn't the OS. There's no sense in sending someone down every gopher hole when you can just flood the thing out. Rolling back or reinstalling an os is the the "have you tried turning it off and back on again?" of diagnostics. No, it isn't. I've never once rolled back a Mac to a previous version, and I can't remember the last time I reloaded an OS on a Mac. |
|
The Apple System Profiler shows two things
1: are you getting voltage to the device through the port and if so: 2: does the device respond back with the correct ID. If the computer physically sees the device but it doesn't show up, take a look in the disk utility to see it it shows an unmounted disk. I didnt read thru the whole thread to see if has been suggested, resetting the smc as suggested is a good step but if the system sees all other USB devices (I.e. You can type on the keyboard) that isn't likely the problem. |
|
Quoted:
Lulz. No, it isn't. I've never once rolled back a Mac to a previous version, and I can't remember the last time I reloaded an OS on a Mac. Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
I will check this out when I'm done today It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. If the issue is in the firmware, rolling back often band-aids the issue. Like I said, I fixed this just a couple of weeks ago on a mac, it wasn't the OS. There's no sense in sending someone down every gopher hole when you can just flood the thing out. Rolling back or reinstalling an os is the the "have you tried turning it off and back on again?" of diagnostics. No, it isn't. I've never once rolled back a Mac to a previous version, and I can't remember the last time I reloaded an OS on a Mac. https://www.google.com/search?q=rolling+back+os+x |
|
Quoted:
Oh sure, all these articles, forum threads and actual Apple support posts must follow your personal experience. https://www.google.com/search?q=rolling+back+os+x Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
I will check this out when I'm done today It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. If the issue is in the firmware, rolling back often band-aids the issue. Like I said, I fixed this just a couple of weeks ago on a mac, it wasn't the OS. There's no sense in sending someone down every gopher hole when you can just flood the thing out. Rolling back or reinstalling an os is the the "have you tried turning it off and back on again?" of diagnostics. No, it isn't. I've never once rolled back a Mac to a previous version, and I can't remember the last time I reloaded an OS on a Mac. https://www.google.com/search?q=rolling+back+os+x If you want to pretend you're working on Windows 95 and apply those troubleshooting methods to modern computing, you go right on ahead and live in the dark ages. The rest of us over here will actually do real shit with real computers. I've got four Macs within arms reach and OSX running in two VMs, and that's just on my desk and my wife's desk next to me. I think I have some perspective on this issue. And obtw, I fixed another Mac that was doing exactly what the OP's Mac was doing just a few weeks ago. Without "rolling back" the operating system. |
|
Quoted:
Dude. If you want to pretend you're working on Windows 95 and apply those troubleshooting methods to modern computing, you go right on ahead and live in the dark ages. The rest of us over here will actually do real shit with real computers. I've got four Macs within arms reach and OSX running in two VMs, and that's just on my desk and my wife's desk next to me. I think I have some perspective on this issue. And obtw, I fixed another Mac that was doing exactly what the OP's Mac was doing just a few weeks ago. Without "rolling back" the operating system. Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
I will check this out when I'm done today It's the firmware responding to what it sees as a faulty device, as far as I can tell from the one I did the other day. SMC/PRAM reset should fix it. If the issue is in the firmware, rolling back often band-aids the issue. Like I said, I fixed this just a couple of weeks ago on a mac, it wasn't the OS. There's no sense in sending someone down every gopher hole when you can just flood the thing out. Rolling back or reinstalling an os is the the "have you tried turning it off and back on again?" of diagnostics. No, it isn't. I've never once rolled back a Mac to a previous version, and I can't remember the last time I reloaded an OS on a Mac. https://www.google.com/search?q=rolling+back+os+x If you want to pretend you're working on Windows 95 and apply those troubleshooting methods to modern computing, you go right on ahead and live in the dark ages. The rest of us over here will actually do real shit with real computers. I've got four Macs within arms reach and OSX running in two VMs, and that's just on my desk and my wife's desk next to me. I think I have some perspective on this issue. And obtw, I fixed another Mac that was doing exactly what the OP's Mac was doing just a few weeks ago. Without "rolling back" the operating system. |