Sponsored Content
Full Discussion: Device Names on Android
Operating Systems Linux Android Device Names on Android Post 302866827 by fedora18 on Tuesday 22nd of October 2013 06:18:47 PM
Old 10-22-2013
haha sorry, that was in another forum.

but so far no success. it definitely is a driver issue and so that is why no /dev/ttyUSB* populates in /dev upon plug in.

I have seen that some companies to provide drivers for these adapters so kind of exploring options there.

Also, a lot of people mention that you must OTG usb port....dont know why this would matter as my tablet has a usb2.0 port already.

updates as they come...
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Device Files names and location

HI there. I am studying System administration right now and am stuck on a question that I have failed to find the answer for in my book. The question is: Do device files need to be in the /dev directory and to they need to follow a naming convention? My answer (so far) is that since the... (7 Replies)
Discussion started by: Carl1976
7 Replies

2. Android

Android Scripting Environment: Shell Scripting and Android

I just upgraded to Android 2.2 from 2.1. The GPS issue that was troublesome in 2.1 seems to have been fixed. Some of web browsing seems faster, but it could just be my connection is better today ;) Flash works in some browsers but not very good and it is too slow for Flash apps designed for... (0 Replies)
Discussion started by: Neo
0 Replies

3. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

4. Android

Running only the Linux kernel of an Android device

I am looking for a way to run on top of the Linux kernel of an Android device. I want to use the existing configured Linux beneath Android rather than put a new Linux distribution onto a device. The article "The Android boot process from power on" (sorry, forum won't let me paste the link)... (0 Replies)
Discussion started by: raoulney
0 Replies

5. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies

6. UNIX for Beginners Questions & Answers

Android Device ID Changer shell script

this is worked "ANDROID NOUGAT" how can i use it for "ANDROID OREO" -plz help me... ------------------------------------------- echo " Ã-~-DEVICE ID CHANGINGÃ-~-" sleep 2 echo " " COUNT=1 while do ; echo "settings put secure android_id " | tr -d '\n' > X1... (4 Replies)
Discussion started by: f4is4l
4 Replies
scsimgr_fcd(7)						 Miscellaneous Information Manual					    scsimgr_fcd(7)

NAME
scsimgr_fcd - Fibre Channel interface driver fcd plug-in for scsimgr DESCRIPTION
The Fibre Channel interface driver plug-in for implements management operations specific to fibre channel HBA controllers bound to driver is the native HP-UX Fibre Channel interface driver that manages fibre channel devices. The plug-in handles the following operations for driver o Get, set and save per driver instance attributes. Commands The user can explicitly send the following commands to the driver plug-in by specifying the instance#> HBA controller hardware path> instance#> option: Displays information on attributes. Saves value of attributes in a persistent store. Sets values of attributes. Refer to scsimgr(1M) for the syntax of these commands. automatically invokes the plug-in to perform the driver specific part of the operation when the operation applies to per driver instances. Attributes The following table lists driver specific attributes. For details on the concept of attributes refer to scsimgr(1M). Note: The following conventions are used: o RO is Read Only. o RW is Read Write. o string is an array of characters. --------------------------------------------------------------------- Object Attribute Name RO/RW Type Description --------------------------------------------------------------------- Controller sym_port_name RW string Symbolic Port Name for fibre channel HBA con- troller Default: <host- name>_fcd<instance#> --------------------------------------------------------------------- sym_node_name RW string Symbolic Node Name for fibre channel HBA con- troller Default: <hostname>_HP- UX_<os release version> --------------------------------------------------------------------- EXAMPLES
Display all attributes for HBA controller with DSF /dev/fcd1: Get HBA controller symbolic port name for DSF /dev/fcd1: Get HBA controller symbolic node name for hardware path 0/2/1/0: Set HBA controller symbolic port name for DSF /dev/fcd1 to fcd1_port: Set HBA controller symbolic node name for class fc and instance 8 to fcd1_node: Save HBA controller symbolic port name for DSF /dev/fcd1 as fcd1_port: Save HBA controller symbolic node name for hardware path 0/2/1/0 as fcd1_node: AUTHOR
Fibre Channel interface driver plug-in for was developed by HP. SEE ALSO
scsimgr(1M), intro(7). scsimgr_fcd(7)
All times are GMT -4. The time now is 05:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy