Terminal command to refresh USB peripheral device

I'm running OS 10.7.5, and I have a recurring problem with the USB ports on my Mac mini. After several days of up-time, one or more of the ports will sometimes become non-responsive. This seems to be software related, because logging off and logging back into the machine always fixes the problem (as does a restart and a cold-reboot). I was thinking maybe the "checklist" of device filenames somehow gets corrupted over time, and needs to be recreated.
Does anyone know how to refresh the list of peripheral devices without restarting, rebooting, or logging off? Ideally a terminal command? I'm hoping not to have to keep shutting down the session each time this happens to get my list of connected devices back.
Thanks very much for your suggestions for the newbie.

Hi Korby,
If you are having difficulties with USB devices such as you describe, I would suggest resetting your Mac mini’s parameter RAM, as described in this article -
About NVRAM and PRAM
http://support.apple.com/kb/HT1379
Specifically -
Resetting NVRAM / PRAM
Shut down your Mac.
Locate the following keys on the keyboard: Command (⌘), Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.
Thanks for using Apple Support Communities.
Best,
Brett L

Similar Messages

What is the terminal command to list USB devices?

In Ubuntu Linux the command lsusb lists all devices connected to the usb ports. What is the equivalent command in OS-X? Thanks.

Linc:
Thanks. The new thread, if you want to comment on it is:
Activate/Deactivate USB connected device
If I am able to deactivate or unattach or disable the driver that is responsible for controlling the usb web cam that I have in my Mac mini, the virtualization program (VBox) would be able to capture it (already configured with the appropriate filter) for my guest OS. Now, I only get a message saying that the camera is busy from a previous request.
When I run your command, I get no response.

USB Peripheral Device Knocked out 2011 MacBook Pro

I connected an external fan to my brand new 2011 MacBook Pro (13 inch). A couple of times it shut the MBP's down, requiring a reboot.
The last time, it shut the computer down and it now will not restart at all. I have tried resetting the SMC, but it still will not start up.
The power plug indicator light (on the part that connects to the computer) very faintly blinks -- it's barely visible to the eye.
Any suggestions on fixes?
Many thanks!

Contact the manufacturer of the fan for their expertise.

The USB port on my 4th generation Airport Extreme does not recognize any peripheral devices whatsoever. In other words, it does not function at all. What can I do?

I have had my Airport Extreme for almost a year now. I have not been able to get it to work. It has never worked. I have tried everything in the apple manuals, my peripheral device manuals, and online help. My Airport Extreme Base Station has a completely dead USB port. The USB connector does have voltage and ground. Apparently there is no data transfer. I do not know how to test the data pinouts. I don't know if it is a software or driver problem, or if it is a hardware or wiring problem. My computer is a mid-2009 13" MacBook Pro. All of my external devices work well with the MacBook Pro. The USB functionality on the MacBook Pro has always performed without a glitch. It seems the problem with the Airport Extreme must either be a network communication problem or a hardware/hardwire problem. I bought the Airport Extreme to build a home inTRAnet network. I have a seperate 3rd party router for inTERnet. Contrary to what the manuals declare, the initial setup of my Airport Extreme requires inTERnet setup during the process. Even when the choice is made to limit the network access to LAN only, when I reach the end of the setup process, a prompts reads that the Airport Extreme may not function because I have not set it up for inTERnet with the WAN. Well, Dah... during the intial stages of the setup I told the machine to configure an inTRAnet only LAN setup. So... I went ahead and set it up for inTERnet and WAN. Either way, the USB port is not working. Then I set it up for the whole package, WAN, LAN, and everything. Still... no function out of the USB port. Any ideas?
P.S. The Ethernet works and so does the 802.11 tranceiver. The USB port is the only problem, but a major, major one for my needs. There is no peripheral functionality.

Okay so I figured it out. I inherited the Configurator already set up so I didn't realize that our former administrator was brilliant and set things up a little differently. To anyone else who finds themselves in this spot try this:
After you plug the iPad in and open Configurator instead of trying to 'Prepare' the device click 'Assign'
There should be groups of Users listed on the left hand side of the screen.
Select the group you want the ipad to be a part of, or make a new group. ***Note a group can be one person so this is a good feature for teachers to have individual app assignements for students.
After you select the user group click the little plus ( + ) button on the bottom of the screen under the second column of info where names and device serial numbers should appear.
Type the name of the person, group, whatever you want to identify that assignment by into the blank that pops up after you hit the plus ( + )
Then select the assignment you just made and tohe 'Check Our' button at the bottom. At this point a box will pop up with a window at the top listing all devices supervised by Configurator. There is a tiny down arrow button that opens a scroll down menu to the right of this box. Click that, then select the device connected by USB as the one to assign.
The name of the assignment you gave it will show on the lock screen now and you can assign apps and profiles to the device like you would any other device in your Configurator inventory.
Good Luck.

TS3002 My macbook pro 4,1 runs os x 10.6 but won't run my apple usb superdrive. One forum said that this is due to os x, not hardware. The terminal commands given were for Lion, but don't work in snow leopard. Help!

My macbook pro 4,1 runs os x 10.6 but won't run my apple usb superdrive. One forum said that this is due to os x, not hardware. The terminal commands given were for Lion, but don't work in snow leopard. Help!

I was able to get it to work!

Terminal command to get details on PCI devices?

What terminal command do I use to find out more details about PCI devices?
In Linux I use "lspci" and pipe it with "grep" to find out what is what.
It doesn't seem to be a Unix/MacOSX command.
Thanks.
Roger

I tried iorgeg -l | grep PCI and got a bunch of info. Thanks.

Usb - 6009 Device Recongition Problems

Hi,
I just got a USB-6009 DAQ. I have labview 7.0, drivers software and the supplied software installed with no problems. In the measurment nad automation explorer (MAX) the device is recongnised and declared problem free. I tried to test the device in labview using help tutorials which suggests the DAQ assitant block. After selecting Analogue input and then voltage I am told that no device is detected i.e. Where I should be selecting my terminal(s) I am not giving any options.
If anyone has had the same problems or know how to fix them I would be thankful of your help.
Kyle

Hi Kyle,
The USB-6009 device works on DAQmx base. This is a restricted version of NI-DAQmx which is used on some of our products. Unfortunetly it is incompatible with DAQmx and the DAQ Assistant uses DAQmx. Therefore you can't use the UDB-6009 with the DAQ Assistant.
To use the device, load up the USB-600x Interactive Control which should be located in the following directory.
C:\Program Files\National Instruments\LabVIEW 7.0\examples\daqmxbase
Take a look at this and figure out how the code works. If you want to configure it to do your own specific functions then I would suggest that you use this program as a base and customise it for your purposes.
Best regards,
Peter H.
Applications Engineer.
NIUK.

No sound on my Sony Bluetooth Headset because Windows 7 can't find Bluetooth peripheral device driver

SO, I am dealing this problem for the second day in a row and no working solution still. I own the latest iMac 2014 (though the model is exactly as 2013) 2,7 Ghz with Bluetooth 4.0, I've installed through Bootcamp Windows 7 x64. My bluetooth headset Sony DR-BTN200 http://store.sony.com/bluetooth-headphones-zid27-DRBTN200//cat-27-catid-All-Home -Theater-Headphones (which is on Bluetooth 3.0 and of 2013 year model) is working fine with Mavericks and Yosemite on my MBP, but not working as it should on iMac with Windows 7..
THE PROBLEM: I find the headset, connect it, but afterwards Windows writes that no drivers for Bluetooth peripheral device were found (3 or 4 encriptions like this, so, 3-4 drivers needed). The headset itself guarrantees fine working with Windows 8, the producer doesn't give any drivers to install, you won't find them on Sony's website - it should work as plug-n-play, they say those drivers are preinstalled on Windows 8.
WHAT I'VE TRIED: So, the problem, as I've read from many-many-many sources is common for everybody running Windows on Mac devices. In cases with notebooks it is easy to solve (if you know it) - download the Bluetooth software from Broadcom (the producer of Bluetooth adapters/receivers of Macs) http://www.broadcom.com/support/bluetooth/update.php - install, it finds the devices and istalls correct driver. This worked with my MacBook Pro 2010, on iMac it stucks on recognizing devices - nothing happens next, like it doesn't recognize any bluetooth device. Downloading many other drivers packages didn't help either, nor Toshiba Bluetooth helpers could detect Bluetooth headset to properly download the correct drivers (though it was already recognized by Windows, just couldn't connect properly), nor different other programs like Bluesoleil, Blue manager and so on.
On other notebooks and computers many try to install manually the drivers, usualy Microsoft Windows mobile-based device support. I've tried to install many drivers, all of the Broadcom drivers I've found (including the Broadcom Bluetooth 3.0 USB driver that makes the headset work on MBP), and I must say that Windows recognizes (doesnt show the yellow triangle next to the icon of the driver) only for the Microsoft Windows mobile-based device support driver. Though it's like that, the sound still is not playing out of my headset. On MBP after the drivers were installed, I chose the device in Printers and devices and there was an option of Control (maybe I remember the name wrong), it went first in the right-click menu, and aftewards there was a page were I could connect my headset through ticks/checks on different options. Nothing like this appears if I install any of the drivers on iMac (nor Broadcom, nor Win mobile-based). I must also mention, that some kind of package that I've downloaded from Toshiba or Acer's Broadcom Bluetooth kit, I don't remember, installed some bluetooth drivers (Bluetooth Audio, "receiver" if I recall it correctly and 2 more), that were recognized as right drivers for peripheral device when I connected my headset, but even then - no sound came out of the headset.
HELP ME: What shoud I do? I've tried all of the methods that are on the net. Sony store won't help me out, because the problem is not in the device - it's in the software/hardware of "your iMac". The headset works with Mac OS, should work fine with fully-Windows PCs, it just doesn't with iMacs on Bootcamp Windows. The interesting thing is that updating windows to Windows 8 might also not help, since Sony guarrantees only work on pre-shipped with Win 8 devices, not with the upgraded devices. I do think the problem is with drivers, that Mac's Bootcamp utility doesn't come with pre-installed Bluetooth drivers for connecting Bluetooth headsets, only for the Apple mouse and keyboard. I must also mention that I've tried to install manually many of the Broadcom drivers, all of which were for Bluetooth 3.0 or 4.0, they didn't help.
It's awfull that I've got the latest iMac, so the latest hardware and face such problems. I only think that a cheap 5-7$ bluetooth-usb adapter could help, maybe it could recognize the headset and therefor install its own drivers for its manufacturer. But I don't imagine how would it work and connect since iMac has a peinstalled Bluetooth receiver. Is there a software sollution? An app or driver?

So, finally I found what worked for me: Re: Full Bluetooth functionality in Bootcamp (audio, A2DP, FTP, OBEX) third variant, none of first 2 worked.. The only trouble was to find the correct link since on Acer site there is no download link. I've googled for "Bluetooth_Atheros_7.4.0.96_W7x64_A.zip" since this is the archive the guy is actually talking about. The 4th link on google was http://www.laptop-software.com/Acerdriversdownload.php?GDFiles/Driver/Bluetooth/ Bluetooth_Atheros_7.4.0.96_W7x64_A.zip?acerid=634556349384706773&Step1=Notebook& Step2=Aspire&Step3=Aspire%204830Z&OS=721&LC=en&BC=Acer&SC=PA_6 and I chose to downlad from the first download link. Then the steps are:
1) unzip the folder
2) don't look for x64 or x32, there is only a one installer called "Bluetooth_Suite_win7"
3) install Bluetooth_Suite_win7
4) after it installs Windows starts downloading and recognizing drivers, I don't know how it actually works, but it also downloaded and recognized the unrecognized before drivers for my Bluetooth headset.
5) Restart Windows
6) Turn on headphones - they connect automatically, everything works and works great, the quality of sound is exactly the same as it was on Mac OS, nothing that would bother me.
****, it took me 2 full days... finally...

Generic "usb midi device" in 10.9 / Mavericks

What does Mavericks need to use the product string from the USB descriptor as the name of the MIDI port? I have an assortment of USB Audio Class 2.0 compliant audio + MIDI interfaces. Some behave as they do in Mountain Lion and earlier: If manufacturer Foo makes a product Bar with audio and MIDI interfaces, then the Audio Midi Setup windows will show an audio interface named Bar, and a MIDI port named Bar. If you double-click on the MIDI port, it shows the Model, "Bar," and additional information, including the manufacturer Foo, as retrieved from the USB descriptor. This is expected and desired, especially with devices that unlock features in non-free software.
However, with Mavericks, some devices (staying with the Foo/Bar example), though the audio interface gets named Bar, show up in the MIDI Studio window of AMS as "USB MIDI Device," and double-clicking reveals the manufacturer and model to be "Generic" and "USB MIDI Device," respectively. If you use the drop down menu at the top of this window to switch to a different configuration, or define a new one, while the device is connected, it appears in the second configuration as Bar, with the correct manufacturer.
Now, according to https://developer.apple.com/library/mac/technotes/tn2274/_index.html, the Interface Association Descriptor needs to group all the audio descriptors together, they need to be contiguous, and they need to be ordered by Audio Control, then Audio Streaming, then MIDI streaming. The device that isn't coming up correctly meets those criteria, so I wonder what else is missing.
Here's a dump:
Information for device Bar (VID=0x0f00 PID=0x0baa):
Connection Information:
Connection status: Device connected
Device actual bus speed: High
Device is hub: No
Device address: 0x0001
Current configuration value: 0x01
Number of open pipes: 5
Device Descriptor:
0x12    bLength
0x01    bDescriptorType
0x0200    bcdUSB
0xEF    bDeviceClass   (Miscellaneous device)
0x02    bDeviceSubClass
0x01    bDeviceProtocol
0x40    bMaxPacketSize0   (64 Bytes)
0x0f00    idVendor
0x0baa    idProduct
0x0010    bcdDevice
0x01    iManufacturer   "Foo"
0x03    iProduct   "Bar"
0x00    iSerialNumber
0x02    bNumConfigurations
Device Qualifier Descriptor:
0x0A    bLength
0x06    bDescriptorType
0x0200    bcdUSB
0x00    bDeviceClass
0x00    bDeviceSubClass
0x00    bDeviceProtocol
0x40    bMaxPacketSize0   (64 Bytes)
0x01    bNumConfigurations
0x00    bReserved
Configuration Descriptor:
0x09    bLength
0x02    bDescriptorType
0x0169    wTotalLength
0x05    bNumInterfaces
0x01    bConfigurationValue
0x00    iConfiguration
0x80    bmAttributes   (Bus-powered Device)
0xFA    bMaxPower   (500 mA)
Interface Association Descriptor:
0x08    bLength
0x0B    bDescriptorType
0x00    bFirstInterface
0x04    bInterfaceCount
0x01    bFunctionClass   (Audio Device Class)
0x00    bFunctionSubClass
0x20    bFunctionProtocol
0x00    iFunction
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x00    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x01    bInterfaceSubClass   (Audio Control Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AC Interface Header Descriptor:
0x09    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x0200    bcdADC
0x08    bCategory
0x0087    wTotalLength
0x00    bmControls
AC Clock Source Descriptor:
0x08    bLength
0x24    bDescriptorType
0x0A    bDescriptorSubtype
0x29    bClockID
0x03    bmAttributes
0x07    bmControls
0x00    bAssocTerminal
0x0E    iClockSource   "Foo Internal Clock"
AC Clock Selector Descriptor:
0x08    bLength
0x24    bDescriptorType
0x0B    bDescriptorSubtype
0x28    bClockID
0x01    bNrInPins
0x29    baCSourceID(1)
0x03    bmControls
0x0D    iClockSelector   "Foo Clock Selector"
AC Input Terminal Descriptor:
0x11    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x02    bTerminalID
0x0101    wTerminalType   (USB Streaming)
0x00    bAssocTerminal
0x28    bCSourceID
0x04    bNrChannels
0x00000000    bmChannelConfig
0x12    iChannelNames
0x00    bmControls
0x06    iTerminal   "Bar "
AC Feature Unit Descriptor:
0x1A    bLength
0x24    bDescriptorType
0x06    bDescriptorSubtype
0x0A    bUnitID
0x02    bSourceID
0x0000000F    bmaControls(0)
0x0000000F    bmaControls(1)
0x0000000F    bmaControls(2)
0x0000000F    bmaControls(3)
0x0000000F    bmaControls(4)
0x00    iFeature
AC Output Terminal Descriptor:
0x0C    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x14    bTerminalID
0x0301    wTerminalType   (Speaker)
0x00    bAssocTerminal
0x0A    bSourceID
0x28    bCSourceID
0x0000    bmControls
0x00    iTerminal
AC Input Terminal Descriptor:
0x11    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bTerminalID
0x0201    wTerminalType   (Microphone)
0x00    bAssocTerminal
0x28    bCSourceID
0x04    bNrChannels
0x00000000    bmChannelConfig
0x16    iChannelNames
0x00    bmControls
0x00    iTerminal
AC Feature Unit Descriptor:
0x1A    bLength
0x24    bDescriptorType
0x06    bDescriptorSubtype
0x0B    bUnitID
0x01    bSourceID
0x0000000F    bmaControls(0)
0x0000000F    bmaControls(1)
0x0000000F    bmaControls(2)
0x0000000F    bmaControls(3)
0x0000000F    bmaControls(4)
0x00    iFeature
AC Output Terminal Descriptor:
0x0C    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x16    bTerminalID
0x0101    wTerminalType   (USB Streaming)
0x00    bAssocTerminal
0x0B    bSourceID
0x28    bCSourceID
0x0000    bmControls
0x07    iTerminal   "Bar "
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x01    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x01    bInterfaceNumber
0x01    bAlternateSetting
0x02    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AS Interface Descriptor:
0x10    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x02    bTerminalLink
0x00    bmControls
0x01    bFormatType
0x00000001    bmFormats
0x04    bNrChannels
0x00000000    bmChannelConfig
0x12    iChannelNames
AS Format Type 1 Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bFormatType
0x04    bSubslotSize
0x18    bBitResolution   (24 Bits/sample)
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x01    bEndpointAddress   (OUT Endpoint)
0x05    bmAttributes    (Transfer: Isochronous / Synch: Asynchronous / Usage: Data)
0x00D0    wMaxPacketSize   (208 Bytes)
0x01    bInterval
AS Isochronous Data Endpoint Descriptor:
0x08    bLength
0x25    bDescriptorType
0x01    bDescriptorSubtype
0x00    bmAttributes
0x00    bmControls
0x02    bLockDelayUnits   (Decoded PCM samples)
0x0008    wLockDelay
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x81    bEndpointAddress   (IN Endpoint)
0x11    bmAttributes    (Transfer: Isochronous / Synch: None / Usage: Feedback)
0x0004    wMaxPacketSize   (4 Bytes)
0x04    bInterval
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x02    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x02    bInterfaceNumber
0x01    bAlternateSetting
0x01    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AS Interface Descriptor:
0x10    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x16    bTerminalLink
0x00    bmControls
0x01    bFormatType
0x00000001    bmFormats
0x04    bNrChannels
0x00000000    bmChannelConfig
0x16    iChannelNames
AS Format Type 1 Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bFormatType
0x04    bSubslotSize
0x18    bBitResolution   (24 Bits/sample)
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x82    bEndpointAddress   (IN Endpoint)
0x05    bmAttributes    (Transfer: Isochronous / Synch: Asynchronous / Usage: Data)
0x00D0    wMaxPacketSize   (208 Bytes)
0x01    bInterval
AS Isochronous Data Endpoint Descriptor:
0x08    bLength
0x25    bDescriptorType
0x01    bDescriptorSubtype
0x00    bmAttributes
0x00    bmControls
0x02    bLockDelayUnits   (Decoded PCM samples)
0x0008    wLockDelay
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x03    bInterfaceNumber
0x00    bAlternateSetting
0x02    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x03    bInterfaceSubClass   (MIDI Streaming Interface)
0x00    bInterfaceProtocol
0x00    iInterface
MS Interface Header Descriptor:
0x07    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x0100    bcdMSC
0x0041    wTotalLength
MS MIDI IN Jack Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bJackType
0x01    bJackID
0x00    iJack
MS MIDI IN Jack Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x02    bJackType
0x02    bJackID
0x00    iJack
MS MIDI OUT Jack Descriptor:
0x09    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x01    bJackType
0x03    bJackID
0x01    bNrInputPins
0x02    baSourceID(1)
0x01    baSourcePin(1)
0x00    iJack
MS MIDI OUT Jack Descriptor:
0x09    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x02    bJackType
0x04    bJackID
0x01    bNrInputPins
0x01    baSourceID(1)
0x01    baSourcePin(1)
0x00    iJack
Endpoint Descriptor (Audio/MIDI):
0x09    bLength
0x05    bDescriptorType
0x02    bEndpointAddress   (OUT Endpoint)
0x02    bmAttributes    (Transfer: Bulk / Synch: None / Usage: Data)
0x0200    wMaxPacketSize   (512 Bytes)
0x00    bInterval
0x00    bRefresh
0x00    bSynchAddress
MS Bulk Data Endpoint Descriptor:
0x05    bLength
0x25    bDescriptorType
0x01    bDescriptorSubtype
0x01    bNumEmbMIDIJack
0x01    baAssocJackID(1)
Endpoint Descriptor (Audio/MIDI):
0x09    bLength
0x05    bDescriptorType
0x83    bEndpointAddress   (IN Endpoint)
0x02    bmAttributes    (Transfer: Bulk / Synch: None / Usage: Data)
0x0200    wMaxPacketSize   (512 Bytes)
0x00    bInterval
0x00    bRefresh
0x00    bSynchAddress
MS Bulk Data Endpoint Descriptor:
0x05    bLength
0x25    bDescriptorType
0x01    bDescriptorSubtype
0x01    bNumEmbMIDIJack
0x03    baAssocJackID(1)
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x04    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0xFE    bInterfaceClass   (Application Specific)
0x01    bInterfaceSubClass
0x01    bInterfaceProtocol
0x0F    iInterface   "Foo DFU"
Configuration Descriptor:
0x09    bLength
0x02    bDescriptorType
0x0169    wTotalLength
0x05    bNumInterfaces
0x01    bConfigurationValue
0x00    iConfiguration
0x80    bmAttributes   (Bus-powered Device)
0xFA    bMaxPower   (500 mA)
Interface Association Descriptor:
0x08    bLength
0x0B    bDescriptorType
0x00    bFirstInterface
0x04    bInterfaceCount
0x01    bFunctionClass   (Audio Device Class)
0x00    bFunctionSubClass
0x20    bFunctionProtocol
0x00    iFunction
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x00    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x01    bInterfaceSubClass   (Audio Control Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AC Interface Header Descriptor:
0x09    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x0200    bcdADC
0x08    bCategory
0x0087    wTotalLength
0x00    bmControls
AC Clock Source Descriptor:
0x08    bLength
0x24    bDescriptorType
0x0A    bDescriptorSubtype
0x29    bClockID
0x03    bmAttributes
0x07    bmControls
0x00    bAssocTerminal
0x0E    iClockSource   "Foo Internal Clock"
AC Clock Selector Descriptor:
0x08    bLength
0x24    bDescriptorType
0x0B    bDescriptorSubtype
0x28    bClockID
0x01    bNrInPins
0x29    baCSourceID(1)
0x03    bmControls
0x0D    iClockSelector   "Foo Clock Selector"
AC Input Terminal Descriptor:
0x11    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x02    bTerminalID
0x0101    wTerminalType   (USB Streaming)
0x00    bAssocTerminal
0x28    bCSourceID
0x04    bNrChannels
0x00000000    bmChannelConfig
0x12    iChannelNames
0x00    bmControls
0x06    iTerminal   "Bar "
AC Feature Unit Descriptor:
0x1A    bLength
0x24    bDescriptorType
0x06    bDescriptorSubtype
0x0A    bUnitID
0x02    bSourceID
0x0000000F    bmaControls(0)
0x0000000F    bmaControls(1)
0x0000000F    bmaControls(2)
0x0000000F    bmaControls(3)
0x0000000F    bmaControls(4)
0x00    iFeature
AC Output Terminal Descriptor:
0x0C    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x14    bTerminalID
0x0301    wTerminalType   (Speaker)
0x00    bAssocTerminal
0x0A    bSourceID
0x28    bCSourceID
0x0000    bmControls
0x00    iTerminal
AC Input Terminal Descriptor:
0x11    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bTerminalID
0x0201    wTerminalType   (Microphone)
0x00    bAssocTerminal
0x28    bCSourceID
0x04    bNrChannels
0x00000000    bmChannelConfig
0x16    iChannelNames
0x00    bmControls
0x00    iTerminal
AC Feature Unit Descriptor:
0x1A    bLength
0x24    bDescriptorType
0x06    bDescriptorSubtype
0x0B    bUnitID
0x01    bSourceID
0x0000000F    bmaControls(0)
0x0000000F    bmaControls(1)
0x0000000F    bmaControls(2)
0x0000000F    bmaControls(3)
0x0000000F    bmaControls(4)
0x00    iFeature
AC Output Terminal Descriptor:
0x0C    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x16    bTerminalID
0x0101    wTerminalType   (USB Streaming)
0x00    bAssocTerminal
0x0B    bSourceID
0x28    bCSourceID
0x0000    bmControls
0x07    iTerminal   "Bar "
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x01    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x01    bInterfaceNumber
0x01    bAlternateSetting
0x02    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AS Interface Descriptor:
0x10    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x02    bTerminalLink
0x00    bmControls
0x01    bFormatType
0x00000001    bmFormats
0x04    bNrChannels
0x00000000    bmChannelConfig
0x12    iChannelNames
AS Format Type 1 Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bFormatType
0x04    bSubslotSize
0x18    bBitResolution   (24 Bits/sample)
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x01    bEndpointAddress   (OUT Endpoint)
0x05    bmAttributes    (Transfer: Isochronous / Synch: Asynchronous / Usage: Data)
0x00D0    wMaxPacketSize   (208 Bytes)
0x01    bInterval
AS Isochronous Data Endpoint Descriptor:
0x08    bLength
0x25    bDescriptorType
0x01    bDescriptorSubtype
0x00    bmAttributes
0x00    bmControls
0x02    bLockDelayUnits   (Decoded PCM samples)
0x0008    wLockDelay
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x81    bEndpointAddress   (IN Endpoint)
0x11    bmAttributes    (Transfer: Isochronous / Synch: None / Usage: Feedback)
0x0004    wMaxPacketSize   (4 Bytes)
0x04    bInterval
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x02    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x02    bInterfaceNumber
0x01    bAlternateSetting
0x01    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AS Interface Descriptor:
0x10    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x16    bTerminalLink
0x00    bmControls
0x01    bFormatType
0x00000001    bmFormats
0x04    bNrChannels
0x00000000    bmChannelConfig
0x16    iChannelNames
AS Format Type 1 Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bFormatType
0x04    bSubslotSize
0x18    bBitResolution   (24 Bits/sample)
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x82    bEndpoin

Hi,
I have same issue with my device, but what's strange is that it's correctly detected under Yosemite but not under 10.9.4,
It's always detected as Generic Midi device under 10.9.4
Do you find the reason ?
Thx

How do I back up the music and apps etc. I restored my computer and I reinstalled iTunes, I was told something about a terminal command line, what does that mean? Please help

How do I back up the music and apps etc. I restored my computer and I reinstalled iTunes, I was told something about a terminal command line, what does that mean? Please help

- Transfer iTunes purchases to the computer by:
iTunes Store: Transferring purchases from your iOS device or iPod to a computer
- Transfer any other music by using a third-party program like one of those discussed here:
Copy music
- Connect the iPod to the computer and make a backup by right clicking on the iPod under Devices in iTunes and select Back Up
- Restore the iPod from that backup. The restore will also update the iOS.
Note that the backup that iTunes makes does not include synced media like apps and music
Are you sure you have a 3G iPod? A 1G iPod can only go to iOS 3.1.3
See:
Identifying iPod models

Can't seem to sync my phone with iCal because I get a message that says:No writable calendar. I tried the suggestions I found in Help including a Terminal command to no avail.

Can't seem to sync my phone with iCal because I get a message that says:No writable calendar. I tried the suggestions I found in Help including a Terminal command to no avail.

I can only suggest you now need to somehow link your mobile to sync with the new calendar 'On my Mac'.
I have a work Blackberry whose calendar I sync with an iCal calendar 'On my Mac' using a usb lead and the Blackberry Desktop Manager for Mac. This free piece of software from Blackberry, automatically starts up as soon as I connect the usb to the iMac and it then prompts me to select which calendar 'On the iMac', which is writable, that I want my Blackberry to sync to.

Latest Initrd not recognising USB storage devices?

Just installed 2.6.30 with all the necessary files. Everything seemed fine, except for one thing: my external USB hard drive is no longer recognised on boot. Here is my fstab and my mkinitcpio.conf.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs rw,noexec,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=139cf76d-425a-4c40-a5b1-bbbf22533d9a /boot ext4 defaults 0 1
UUID=4eddd177-23f6-49ab-a8ad-d3e1303133e0 / ext4 defaults 0 1
UUID=ED83-B8D4 /media/flash vfat rw,user,noauto 0 0
#UUID=ac46c6ae-d9eb-47d4-809b-19a2484b3133 /iomega ext4 rw,noexec,nosuid 0 1
UUID=ac46c6ae-d9eb-47d4-809b-19a2484b3133 /media/iomega ext4 rw,user,noauto 0 0
UUID=da9e741f-3525-47c6-8c7f-edf1ded00e7a swap swap defaults 0 0
As you can see from this, I originally had my external usb drive mounted on /iomega @ boot. However, since that no longer works, I have changed it to /media/iomega and let HAL mount it automatically when I fire up GNOME (the same way I have my flash drive set up). I used the original line with 2.6.29 with no problems.
The strange thing is, the device is there, because, when it fails, I go into single user mode, remount / read-write and then run mount -a and the device appears with no errors. If I change the line so it doesn't do an fsck on boot, it doesn't mount the device, but I do get an error saying the device is not there. I can then mount it manually at the command prompt.
The device is shown in /etc/blkid.tab and in /dev/disk/by-uuid.
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata usb keymap filesystems"
# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
This is essentially the same as I had it in 2.6.29. I did initially use LZMA, since that gives slightly faster compression & decompression, but changed it back in case it was a timing issue (and rebuilt initrd). No joy. I also tried usbdelay=10 on boot, but again no difference.
This isn't exactly a "show-stopper", since the device functions normally otherwise and everything else is fine, but it is annoying. I would much rather have this device available automatically on boot, so that it gets checked when the max mount count comes up.

This was the bug update I received today:
FS#15282 - [mkinitcpio] Latest initrd not recognising usb storage devices?
User who did this - Thomas Bächler (brain0)
You can never rely on external hard drives to show up "in time".
The difference was that adding the "usb" hook to mkinitcpio used to add a 6 second delay on boot by default, this doesn't happen anymore. I think external drives simply don't belong in fstab, because there's too many possible race conditions. If you insist, you can try to force the usb storage driver to scan for devices sooner after detection, see the delay_use parameter to the usb-storage module.
You're going to have to modify the delay_use parameter to get it to work. Be prepared for race conditions, though. I didn't bother myself as it wasn't a show stopper for me, so I've advised that it can be closed as a non-bug.
ETA: usbdelay=10 doesn't work as that flag is apparently no longer recognised for some reason.
ETTA: I've always used UUID in the fstab because udev can remap devices on boot (I've had fstab not recognising devices because of this).
In case some people don't know, to see what the uuid for a device is, use the following:
sudo tune2fs -l <device-name>
Last edited by jamesbannon (2009-06-28 18:30:23)

Bluetooth Peripheral Device driver failure in Windows Vista

I've linked my computer and my Palm Centro using a Bluetooth connection and now I keep getting an error message that says...
"Device driver was not successfully installed...Bluetooth Peripheral Device - Failed"
It tries to search the computer to find the driver and when it can't it asks me to put in the CD that came with the phone. I do that and it still can't find the driver.
Does anyone know where I can find this mystery driver??? Please help!! Thanks
Post relates to: Centro (Sprint)

I am having the same problem with a new RocketFish Bluetooth adapter. I did NOT have this problem when I was using a Kensington USB Bluetooth adapter. One big difference that I notice between the two adapters is that the Kensington adapter came with an updated version of the Toshiba Bluetooth Stack software which contained its own DUN drivers. However, the new RocketFish Bluetooth 2.0 EDR USB adapter does not seem to work with the Toshibal BT Stack.
Maybe this helps. Maybe it doesn't. Either way, I don't care. It's how I roll. I'm a smart ass.
I will check back for any additions to this thread. I hope we can figure it out! I will also post more Prose of Indifference.
Post relates to: Centro (AT&T)

Bluetooth Peripheral Device driver failure in Windows Vista and Windows 7 (solved)

I had problems setting up Bluetooth HotSync. Following the directions for pairing the device resulted in a "Bluetooth Peripheral Device" missing driver in Device Manager. I finally figured out how to setup HotSync and am able to sync over Bluetooth to Windows 7 64-bit.
On the PC
Right-click on the Bluetooth icon and select Show Bluetooth Devices
Delete the Palm Phone
Right-click on the Bluetooth icon again and select Bluetooth settings
Turn Discovery on for the PC
On the Palm Device
Select Bluetooth
Turn Bluetooth On
Set Visibility to Hidden (if desired)
Select Setup Devices on the Bluetooth screen
Select HotSync Setup
Click Next
Select your PC
This is the important part: Click Next 3 times (don't do what the screens tell you -- just click Next, Next, Next)
Click Launch HotSync
Viola!
On the PC
Right-click on the Bluetooth icon again and select Bluetooth settings
Turn Discovery off for the PC (if desired)
Post relates to: Centro (AT&T)

I am having the same problem with a new RocketFish Bluetooth adapter. I did NOT have this problem when I was using a Kensington USB Bluetooth adapter. One big difference that I notice between the two adapters is that the Kensington adapter came with an updated version of the Toshiba Bluetooth Stack software which contained its own DUN drivers. However, the new RocketFish Bluetooth 2.0 EDR USB adapter does not seem to work with the Toshibal BT Stack.
Maybe this helps. Maybe it doesn't. Either way, I don't care. It's how I roll. I'm a smart ass.
I will check back for any additions to this thread. I hope we can figure it out! I will also post more Prose of Indifference.
Post relates to: Centro (AT&T)

Is there a terminal command that will close quicktime player once a video is finished?

I'm running a python program that uses subprocess.call(['open', '-a', "Quicktime Player", filename]) to open a video and defaults write com.apple.QuickTimePlayerX MGPlayMovieOnOpen 1 starts it automatically. I'm wondering if there's a terminal way or a python way to close the video once it's finished.

Hi, Thanks for the reply, I appreciate it.
What do you mean by "pick up"?
I mean to show what the DNS numbers are that the router is using.
They are not entered in the DNS server field in Networks, TCP/IP tab.
If you mean refresh the client settings, the DNS settings are obtained as part of the DHCP lease (or PPP connection in the case of PPP).
The user/ OP is actually using PPPoA, when i googled PPPoA.. seems he is using Cisco perhaps.
http://en.wikipedia.org/wiki/Point-to-PointProtocol_overATM (Asynchronous Transfer Mode)
"PPPOA or PPPoA, Point-to-Point Protocol (PPP) over ATM, is a network protocol for encapsulating PPP frames in ATM AAL5. It is used mainly with cable modem, DSL and ADSL services.
It offers standard PPP features such as authentication, encryption, and compression. If it is used as the connection encapsulation method on an ATM based network it can reduce overhead slightly (around 0.58%) in comparison to PPPoE".
Essentially the original poster removed the OpenDNS #s from his DNS server field in the TCP/IP tab (b/c they seem to make Adobe.com inaccessible to him)
removing them & allowing his router to "pick them up from the ISP" seems to solved his problem.
However he can not, find what the numbers are that are being utilized,
b/c they are not entered as usual in the Network, & part of the DHCP lease,
or in Airport admin Utility.
I/ we wondered, if there was a Terminal command that will show what the
numbers are that are being used .
Does that help clarify what I mean? Sorry to be so long winded.
Eme '~[ )♥♪

Terminal command to refresh USB peripheral device

Similar Messages

Maybe you are looking for