The following procedures describe how to manage USB mass storage devices without vold running. The device nodes are created under the /dev/rdsk directory for character devices and under the /dev/dsk directory for block devices. For more information, see scsa2usb(7D).

How to Mount or Unmount a USB Mass Storage Device With vold Running

1. Display device aliases for all removable mass storage devices, including USB mass storage devices.

   $ eject -n . . . rmdisk0 -> /vol/dev/rdsk/c4t0d0/clik40 (Generic USB storage) cdrom0 -> /vol/dev/rdsk/c0t6d0/audio_cd (Generic CD device) zip1 -> /vol/dev/rdsk/c2t0d0/fat32 (USB Zip device) zip0 -> /vol/dev/rdsk/c1t0d0/zip100 (USB Zip device) jaz0 -> /vol/dev/rdsk/c3t0d0/jaz1gb (USB Jaz device)

2. Mount a USB mass storage device by using the device aliases listed previously.

   $ volrmmount -i device-alias

   This example shows how to mounts USB Jaz drive (/rmdisk/jaz0).

   $ volrmmount -i jaz0

3. Unmount a USB mass storage device.

   $ volrmmount -e device-alias

   This example shows how to unmount a USB Zip drive (/rmdisk/zip0).

   $ volrmmount -e zip0

4. Eject a USB device from a generic USB drive.

   $ eject device-alias

   For example:

   $ eject rmdisk0

   ---

   Note - The eject command also unmounts the device if it is not unmounted already. The command also terminates any active applications that access the device.

   ---

How to Mount or Unmount a USB Mass Storage Device Without vold Running

1. Become superuser.

2. Mount a USB mass storage device.

   # mount -F fs-type /dev/dsk/cntndnsn /mount-point

   This command might fail it the device is read-only. Use the following command for CD-ROM devices.

   # mount -F fs-type -o ro /dev/dsk/cntndnsn /mount-point

   For example:

   # mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /mnt

3. Unmount a USB mass storage device.

   # umount /mount-point

4. Eject the device.

   # eject /dev/[r]dsk/cntndnsn

How to Add a Hot-Pluggable USB Camera

Use this procedure to add a hot-pluggable USB camera.

1. Become superuser.

2. Plug in and turn on the USB camera.

   The USB subsystem and the SCSA subsystem create a logical device for the camera. After the camera is plugged in, output is written to the /var/adm/messages file.

3. Examine the output written to the /var/adm/messages file.

   Examining this output enables you to determine what logical device was created so that you can then use that device to access your images. The output will look similar to the following:

   # more /var/adm/messages Jul 15 09:53:35 buffy usba: [ID 349649 kern.info] OLYMPUS, C-3040ZOOM, 000153719068 Jul 15 09:53:35 buffy genunix: [ID 936769 kern.info] scsa2usb1 is /pci@0,0/pci925,1234@7,2/storage@2 Jul 15 09:53:36 buffy scsi: [ID 193665 kern.info] sd3 at scsa2usb1: target 0 lun 0

4. Mount the USB camera file system.

   The camera's file system is most likely a PCFS file system. In order to mount the file system on the device created, the slice that represents the disk must be specified. The slice is normally s0 for a SPARC system, and p0 for an Intel system.

   For example, to mount the file system on an Intel system, execute the following command:

   # mount -F pcfs /dev/dsk/c3t0d0p0:c /mnt

   To mount the file system on a SPARC system, execute the following command:

   # mount -F pcfs /dev/dsk/c3t0d0s0:c /mnt

   For information on mounting file systems, see "Mounting and Unmounting File Systems (Tasks)" in System Administration Guide: Basic Administration.

   For information on mounting different PCFS file systems, see mount_pcfs(1M).

5. Verify that the image files are available.

   For example:

   # ls /mnt/DCIM/100OLYMP/ P7220001.JPG* P7220003.JPG* P7220005.JPG* P7220002.JPG* P7220004.JPG* P7220006.JPG*

6. View and manipulate the image files created by the USB camera.

   # /usr/dt/bin/sdtimage &

7. Unmount the file system before disconnecting the camera.

   For example:

   # umount /mnt

8. Turn off and disconnect the camera.

Using USB Audio Devices (Task Map)

Using USB Audio Devices

This Solaris release provides USB audio support which is implemented by a pair of cooperating drivers, usb_ac and usb_as. The audio control driver, usb_ac, a USBA (Solaris USB Architecture) compliant client driver provides the controlling interface to user applications. The audio streaming driver, usb_as, is provided to process audio data messages during play and record and set sample frequency, precision, and encoding requests from the usb_ac drive.

Both drivers comply to the USB audio class 1.0 specification.

Solaris supports external USB audio devices that are play-only or record-only. Onboard USB audio devices are not supported. For supported audio data format information, see usb_ac(7D).

• Only USB audio devices with one volume, bass, or treble control are supported. See the USB audio class specification for more information at http://www.usb.org.

• USB audio devices are supported on SPARC Ultra and Intel platforms that provide USB connectors.

• Hot-plugging USB audio devices is supported.

• USB audio devices must support a continuous sample rate of between 8000 and 48000 Hz or must support a 48000 Hz sample rate to play or record on the Solaris 8 10/01, Solaris 8 2/02, or Solaris 9 release.

The primary audio device is /dev/audio. You can verify that /dev/audio is pointing to USB audio by using the following command:

% mixerctl
Device /dev/audioctl:
  Name    = USB Audio
  Version = 1.0
  Config  = external

Audio mixer for /dev/audioctl is enabled