From owner-freebsd-questions@FreeBSD.ORG Wed Mar 18 00:29:58 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 96CA7F68 for ; Wed, 18 Mar 2015 00:29:58 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2C2827E6 for ; Wed, 18 Mar 2015 00:29:57 +0000 (UTC) Received: from r56.edvax.de (port-92-195-131-196.dynamic.qsc.de [92.195.131.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id EE66F276AB; Wed, 18 Mar 2015 01:29:48 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id t2I0Tmss002156; Wed, 18 Mar 2015 01:29:48 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Wed, 18 Mar 2015 01:29:47 +0100 From: Polytropon To: Sukhveer Yadav Subject: Re: USB mounting Message-Id: <20150318012947.bd900a37.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Mar 2015 00:29:58 -0000 On Tue, 17 Mar 2015 16:39:57 -0700, Sukhveer Yadav wrote: > Pls tell me that sir if rooted Micromax A177 supports USB mounting or not I have no idea. You should ask this question to the maintainers of the rooting tools. But you can already do many diagnostic steps on your FreeBSD system in order to see if all the involved parts are there: USB connection, mass storage access, direct access driver, file system support. If you follow the examples, you'll quickly find out if it supports USB mounting or not. Not all devices do... I'll provide an example, but I will use a normal USB (storage) stick for explanation purposes. When your smartphone has been configured to expose a comparable interface, the steps should be similar. I will trim the output a little, in order to emphasize the important lines. After plugging the device in and giving it few seconds to "settle", you check what the system has been recognizing. See the last lines of the "dmesg" output: # dmesg [...] ugen4.3: at usbus4 umass1: on usbus4 da3 at umass-sim1 bus 1 scbus4 target 0 lun 0 da3: Removable Direct Access SCSI-2 device da3: 40.000MB/s transfers da3: 3826MB (7835648 512 byte sectors: 255H 63S/T 487C) First, "ugen" (generic USB device) must be recognized. This indicates that the USB connection is there. Then "umass" is shown: a mass storage device. This device is then "connected" to the direct access driver: "da" is shown. You know that "ugen4.3" corresponds to your device. You can now request more information about its capabilities: # usbconfig -d 4.3 dump_device_desc ugen4.3: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x054c idProduct = 0x0243 bcdDevice = 0x0200 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 Good so far. You can verify now that the system has properly picked up a direct access media to mount: # camcontrol devlist at scbus4 target 0 lun 0 (da3,pass4) Now check if there are partitions to mount. You now use da3 (or with which number it hopefully appears on your system) as the device name. # gpart show da3 or # fdisk da3 will display the partitioning. You will have to mount /dev/da3 or /dev/da3s1, depending on partitioning scheme "applied". Maybe you can also configure that on the smartphone itself. To test, you do this: # mount -t msdosfs /dev/da3 /mnt or # mount -t msdosfs -o ro /dev/da3s1 /mnt and verify the output of # mount -a to list the device properly mounted: /dev/da3 will be mounted at /mnt. You may add more mount options for convenience, as well as set an entry in /etc/fstab. Here is an example on how to do this: /dev/da3 /media/micromax msdosfs rw,noauto,noatime,-m=644,-M=755 0 0 Now that you're done, unmount it again. # umount /mnt Now you can then simply use # mount /media/micromax Just make sure the mountpoint does exist and you have the proper permissions. To avoid permission-related issues, you can do the testing as root. If everything works, just set up the permissions for your regular user account. You can read more about how to do this in the handbook: https://www.freebsd.org/doc/en/books/handbook/usb-disks.html This chapter covers the neccessary parts of mounting USB media. > .if yes then tell me instructions for that as those given in site do not > seem to be work . Which site? Please be specific so list members can look it up. > I have es file manager .stickmount .pls help me I don't know about "es file manager". But for diagnostic purposes, which are the _first step_ you should take, no file manager is needed, just basic OS tools as shown above. For better help, please provide more detailed information on _what_ documentation you did follow, which steps you've taken (commands used), what the result was (output) and which additional troubleshooting you did (verifications and prequisites). For now, it's nothing more than wild guessing. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...