Hello, I m after some help.
I ve got an Allwinner A20 tv box, it worked fine for a few months then one day, after being on (but idle) for a few hours, I noticed the screen was blank but the light on the front was blue (indicating it was on, red is standby). It would not respond to the remote control or to anything, so I unplugged it and since then it will not boot and the screen is blank, the red light will light up but that is it. I ve eliminated the remote controller not working, but I cant boot the device.
So I ve tried connecting via ADB (with Ubuntu) but I cant get the device to show up after typing "adb devices".
I can get the vendor id and device id and I ve added it and the manufacturer to udev/modeswitch devices, but when I type "sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W"
I get the following error:
~/Android/sdk/platform-tools$ sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.1.1 (C) Josua Dietze 2014
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1f3a
DefaultProduct= 0xefe8
SierraMode=1
NeedResponse=0
Look for default devices ...
found USB ID 048d:1336
found USB ID 1d6b:0002
found USB ID 19a8:2036
found USB ID 1f3a:efe8
vendor ID matched
product ID matched
found USB ID 1d6b:0001
found USB ID 062a:0102
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 004 on bus 003
Current configuration number is 1
Use interface number 0
USB description data (for identification)
-------------------------
Manufacturer: not provided
Product: not provided
Serial No.: not provided
-------------------------
Send Sierra control message
Error: Sierra control message failed (error -7). Abort
I ve searched Google for the error code but I cannot find anything.
The device was rooted and USB debugging was on.
Any help would really be appreciated.
Thanks
Related
Not really a development question, but I still think this section of the forum suites best.
My device (Acer A500 tab) is not recognized by Eclipse when I plug it in via USB (USB debugging is set, ofc). It is, however, recognized by OS as a valid USB device - I can see it with lsusb.
Any suggestions?
Thanks in advance.
P.S. I never had such a problem on Windows. I can't beleive Linux cannot be use for development.
Sorry, my bad. The device couldn't connect via USB because it was already connected over Wi-Fi, and I forgot about it
Please close the topis.
Connecting via USB to Linux (Ubuntu)
I could not get my Ubuntu machines to recognize the tablet when I plugged in the USB cable. Bummer.
Digging around I found a similar issue experienced by Xoom owners. The original article describing the fix is here. The steps listed there are for the Xoom, not the Acer, although the fix is almost the same.
I am posting the slightly modified instructions again here for clarity and brevity.
I did this fix on both Ubuntu 10.10 (Maverick) and 11.04 (Natty). Your mileage may vary.
1. Get the mtpfs package installed on your machine.
Code:
sudo apt-get install mtpfs
2. In the tablet, go to Settings->Applications->Development and turn USB Debugging on (check the box). For me, this was required for file transfers to work.
3. Plug your USB cable into the tablet and your Ubuntu machine.
4. Open your Terminal app on the Ubuntu machine.
5. Use the lsusb command to get the vendor id. Type "lsusb" in Terminal.
6. The output should look something like this:
Code:
[email protected]:~$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 006: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 003 Device 005: ID 05af:0802 Jing-Mold Enterprise Co., Ltd
Bus 003 Device 002: ID 03eb:3301 Atmel Corp. at43301 4-Port Hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0502:3325 Acer, Inc.
Bus 001 Device 003: ID 04f2:b16b Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The line with "Acer, Inc." in it tells you the VendorID. In the example above, it's 0502.
** Disconnect the USB cable at this point **
7. Create a UDEV rule file. Use your editor of choice, mine is nano.
Code:
sudo nano /etc/udev/rules.d/51-android.rules
The file should contain this line when you are finished:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
8. Create a mount point and make yourself the owner.
Code:
sudo mkdir /media/a500
sudo chown user:user /media/a500
IMPORTANT: Replace user:user with your user name and default group on your Ubuntu machine. For most people it will be your login name. If your login is "bob", then replace user:user with bob:bob, capice?
9. Add the mount point to fstab.
Code:
sudo nano /etc/fstab
At the bottom of the file, type this stuff:
Code:
# mount point for Acer A500
mtpfs /media/a500 fuse user,noauto,allow_other 0 0
10. Modify fuse.conf. Uncomment user_allow_other.
Code:
sudo nano /etc/fuse.conf
Look for #user_allow_other and remove the #.
11. Add yourself to the fuse group.
Code:
sudo nano /etc/group
Look for the line starting with "fuse" and put your login at the end of that line (if it's not already there).
12. Reboot.
You should see your mount point in Nautilus when you open it. After plugging in the USB cable, you can click the a500 entry under Places to mount the tablet.
Has anyone managed to connect their S2 using MTP when running Ubuntu? Obviously I know that it's a very simple tast to just connect via mass storage instead, but I'm interested to know.
I think that Samsung have some weird implementation of MTP because I was able to connect and copy files when I was running CM9 but not on stock ICS. I always get the error message:
Unable to mount SAMSUNG_Android
Error initialising camera: -60: Could not lock the device
Though it does mount and I can see the root of both SDCards, all the folders are empty and I can't copy any files to the cards from the computer as I get a error message reading:
There was an error copying the file into gphoto2://[usb:001,010]/store_00020002.
The same happens whether I try to use MTP or PTP.
I think the problem lies in that libmtp-1.1.3 contains fixes for the S2 but that version isn't included with 11.10 or 12.04
hint
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
alpike said:
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
Click to expand...
Click to collapse
That's connecting via USB mass storage, not mtp. But thanks for trying.
Sent from my GT-I9100 using XDA
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
what I have found out that mtpfs is unable to preserve timestamps of the files at least on my install.
gphoto2 backend worked fine on CM9 now wile testing CM10 its a bit buggy, I can get the list of files but I am unable to read or rename them.
Most likelly it will improve as development of CM10 progresses rapidly.
Mounting my Galaxy S3 when connected via USB to my Ubuntu computer
D4rKn3sSyS said:
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
Click to expand...
Click to collapse
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
slubkin said:
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
Click to expand...
Click to collapse
Ubuntu 13.04 is a drastic improvement for MTP support. I have not got around to trying my S II but I successfully managed a family friends Galaxy TAB 2 with MTP with zero manual modifications to Ubuntu. Everything worked perfect plug and play out of the box.
I have also tried old versions to know how bad they were compared to 13.04.
No luck with S2 and Ubuntu 13.04
I'm on Android 4.1.2 and trying to connect via USB to Ubuntu 13.04. Error I get is that my device is not an MTP device, which it's not as its using USB
Issue is that I don't see the mounted android partitions. To make this worse, it works every now and then. Following is the syslog and the outpu of lsusb
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Aug 26 23:04:00 ml kernel: [134718.425536] usb 1-5: new high-speed USB device number 11 using ehci-pci
Aug 26 23:04:00 ml kernel: [134718.558636] usb 1-5: New USB device found, idVendor=04e8, idProduct=685b
Aug 26 23:04:00 ml kernel: [134718.558647] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Aug 26 23:04:00 ml kernel: [134718.558655] usb 1-5: Product: SAMSUNG_Android
Aug 26 23:04:00 ml kernel: [134718.558661] usb 1-5: Manufacturer: SAMSUNG
Aug 26 23:04:00 ml kernel: [134718.558666] usb 1-5: SerialNumber: 001964815b817e
Aug 26 23:04:05 ml kernel: [134723.546077] usb 1-5: can't set config #1, error -110
Aug 26 23:04:05 ml mtp-probe: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5"
Aug 26 23:04:05 ml mtp-probe: bus: 1, device: 11 was not an MTP device
[email protected]:~$ lsusb
Bus 001 Device 011: ID 04e8:685b Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (mass storage mode)
Bus 003 Device 002: ID 046d:c52e Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
HTML:
Hey all,
So after successfully going S-off on my own phone, I was unable to do so on a friends. The problem now it seems is my linux box does not see the phone as /dev/ttyusb0 when plugged in.
lsusb shows as:
Code:
Bus 001 Device 016: ID 05c6:9008 Qualcomm, Inc.
But I am unable to complete the LazyPanda Unbricker because it does not see my phone. ADB devices does not show it either.
I have run modprobe qcserial many many times, as well as plug and unplug, hold power for 30 seconds etc etc to no avail but no /dev/ttyusb0.
So what are my options here? Any advice would be greatly appreciated. Really frustrated.
Upon further investigation the Qualcomm USB modem is registering
Code:
[11087.431154] usbcore: registered new interface driver usbserial_generic
[11087.431160] usbserial: USB Serial Driver core
[11087.434594] USB Serial support registered for Qualcomm USB modem
[11087.434839] usbcore: registered new interface driver qcserial
For the archives:
I was able to get the unbricker to work finally by using a different distro. Apparently older versions of Ubuntu server don't work. You must unplug any usb to serial converters as well because they will be bound to /dev/ttyUSB0.
run
Code:
sudo modprobe -r qcserial
Plug your phone in then run
Code:
modprobe qcserial
type dmesg and look to see if your phone is bound to /dev/ttyUSB0
if it is, you are good to go.
Hope this helps anyone who had the same issue as I did.
The Android device in question is a Micromax A87(a relatively unknown brand in global market but I hope that should'nt matter).
In Ubuntu, I have double checked the udev rules. They all look perfect. (I cross checked using another phone too). The USB debug mode doesn't show up no matter what. And I have the adb_usb.ini in the right place. I have tried running all possible combinations of running
adb, adb start-server as root. But
Code:
adb devices
shows no devices at all.
However, with the USB debugging option enabled on phone, it worked on Win7 after windows installed a Common handset driver.
Now the interesting part.
If I go back to Ubuntu without disconnecting the cable and do
Code:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[B]1234567890ABCDEF[/B] device
The product id is 1234567890ABCDEF and I am able to see it and everthing works fine!!
But the moment I disconnect the USB cable, its gone.
So I guess it's not the development machine that is at fault. The device seems to be setting a property while in Windows which stays latched till the usb connection goes off.
What could be a way to get this to work? (Besides developing on Windows :silly: )
Btw the
Code:
/data/property/persist.service.adb.enable
is 1 too.
What is your computer setup? Are you using a Windows machine, with Ubuntu in a vm? Dual-boot? Other?
My setup:
Dual boot.
Ubuntu 12.04 and Windows 7.
Ok, how about if you plug in the USB with the computer's power off, then boot into Ubuntu?
i have the clone of this phone. mine is Mito A78.
lsusb command shows it as 1c9e:9e08
so idVendor =1c9e and idProduct = 9e08
for now, what you say (plugin to windows and reboot to ubuntu without unplug the phone) is the solution.
i will see if lsusb output still the same.
okay, have checked on windows pc, it should be switched to idVendor =1c9e and idProduct = 9e18
anyway, what you say is a clue that the solution may be around usb_modeswitch and modem manager
further search on usb_modeswitch 1c9e 9e08 found the solution here: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=1351
have tried, but not yet switched to idVendor =1c9e and idProduct = 9e18
have to find the correct rules on /etc/usb_modeswitch.d/1c9e:9e08
Code:
########################################################
# Mito A78
DefaultVendor=0x1c9e
DefaultProduct=0x9e08
TargetVendor=0x1c9e
TargetProduct=0x9e18
SierraMode=1
CheckSuccess=20
NoDriverLoading=1
found it.
after writing the rules, insert
Code:
# Mito A78
ATTR{idVendor}=="1c9e", ATTR{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
to /lib/udev/rules.d/40-usb_modeswitch.rules
i than have to run
Code:
sudo usb_modeswitch -v 0x1c9e -p 0x9e08 -S -R -W
and then the phone switched to idVendor =1c9e and idProduct = 9e18 and adb can access the phone.
:good: :good: :good:
I-mobile IQ 5.1 has same issue, but adb still can't see device
The usb_modeswitch is exactly the same for this phone (same usb vid/pid). However adb still doesn't find the phone under Windows and Ubuntu. lsusb shows the product id switch did work and it all looks right.
Under windows it spins up a cdrom device from the phone so you can install the windows drivers (this lives as an *.iso file under /system); after the driver install, you get the adb device in device manager and two com ports,with all devices having a pid of 9e18 (original 9e08). However adb does not see the device!
I recon there is something wrong on the phone side. This is a very new phone (only release about 5 days ago), so I suspect this is one of the early release bugs...
Since I don't even have a custom recovery for it (CWM, etc) I can even backup my phone and try and do a factory reset.
Looks like a low level USB issue
Switched on tracing on adbd on the phone side. Looks like a phone/usb low level issue:
Code:
--- adb starting (pid 14270) ---
system/core/adb/adb.c::main():Handling main()
system/core/adb/adb.c::adb_main():Local port disabled
system/core/adb/usb_linux_client.c::usb_init():failed to open /dev/android_adb_enable
system/core/adb/usb_linux_client.c::usb_init():[ usb_init - starting thread ]
system/core/adb/adb.c::adb_main():adb_main(): pre init_jdwp()
system/core/adb/jdwp_service.c::jdwp_control_init():jdwp control socket started (5)
system/core/adb/adb.c::adb_main():adb_main(): post init_jdwp()
system/core/adb/adb.c::adb_main():Event loop starting
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - opening device ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ opening device succeeded ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - registering device ]
system/core/adb/transport.c::register_usb_transport():transport: 0x11364a0 init'ing for usb_handle 0x1136410 (sn='')
system/core/adb/transport_usb.c::init_usb_transport():transport: usb
system/core/adb/transport.c::register_transport():transport: (null) registered
system/core/adb/transport.c::transport_registration_func():transport: (null) (10,11) starting
system/core/adb/transport.c::output_thread():(null): starting transport output thread on fd 11, SYNC online (2)
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::transport_socket_events():transport_socket_events(fd=10, events=0001,...)
system/core/adb/transport.c::dump_packet():fd=10: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/adb.c::handle_packet():handle_packet() SYNC
system/core/adb/transport.c::dump_packet():fd=10: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::output_thread():(null): data pump started
system/core/adb/usb_linux_client.c::usb_read():about to read (fd=9, len=24)
system/core/adb/transport.c::input_thread():(null): starting transport input thread, reading from fd 11
system/core/adb/transport.c::dump_packet():fd=11: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::input_thread():(null): transport SYNC online
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11279 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11325 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11818 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13994 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13951 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13913 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13856 to jdwp process list
system/core/adb/usb_linux_client.c::usb_read():ERROR: fd = 9, n = -1, errno = 5 (I/O error)
system/core/adb/transport_usb.c::remote_read():remote usb: read terminated (message)
system/core/adb/transport.c::output_thread():(null): remote read failed for transport
system/core/adb/transport.c::output_thread():(null): SYNC offline for transport
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=0 arg1=0 (len=0)
system/core/adb/transport.c::output_thread():(null): transport output thread is exiting
system/core/adb/usb_linux_client.c::usb_kick():usb_kick
---------- Post added at 04:31 AM ---------- Previous post was at 04:27 AM ----------
I also tried the Chainfire adbd insecure and its exactly the same in the debugging.
Now working on win7 64!
Followed this link and managed to get it working. The PID value was set to 9e18. In essence the andriod usb driver was missing (install via the andriod.bat andriod package manager).
Also works in virtualbox winxp vm on Linux (ubuntu 12.10; actually Mint 14). Just mapped in my win7 64 partition to get access to the andriod sdk/usb driver.
Now that I know its not a handset issue, can return to trying to get the Linux side working.
Now working under Linux!
You need the vendor id in adb_usb.ini:
Code:
cat ~/.android/adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1c9e
If you will run adb as root, make sure you also create the file for root too.
Tip: You will be logged into the phone as the 'shell' user. Try and 'su -' to get root access, and then click on your su dialog on the phone to grant access.
Final issue is that plugging in the device should do the switch automatically; I will update you on that when I have that fixed.
udev sorted on ubuntu
Ok, we are rocking on udev on ubuntu 12.10. Seems like udev doesn't like ATTR keywords, although ATTRS makes everything burst into life (man page says ATTR is useable). Steps that worked for me:
Code:
# cp /lib/udev/rules.d/40-usb_modeswitch.rules /etc/udev/rules.d/usb_modeswitch.rules
# vi /etc/udev/rules.d/usb_modeswitch.rules
Add the following entry near the bottom under the last entry:
Code:
# I-Mobile IQ5.1
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
Create /etc/usb_modeswitch.d/1c9e:9e08 as described earlier by jurban.
Unplug the phone. Plug it in. Do an lsusb. Firstly shows up as dev 1c9e:9e08. Enter lsusb again. Shows up as 1c9e:9e18. Now adb will show the device as jurban shows above. All good to go!
Hi, suddenly (without any ROM flash attempt) my IAIWAI AW920 tablet got in a bootloop.
IIRC it's a RK3066 but the RKAndroidTool/Finn Flash Tool didn't recognized the tablet with either PWR Vol+ or PWR Vol- boot modes.
In the past I got the tablet successfully rooted through some tools, so in some past era I was able to communicate with ADB from the Android SDK (Linux Mint Kernel +3.10) but before it got soft-bricked I had not the USB debugging bridge set and due a failing HDD I lost that environment setup.
While being connected to my laptop through USB cable I can access two modes:
USB + PWR + Vol+: Blank black screen but I detect a USB device with VID: 10d6 PID: 10d6 that doesn't seems to be an adb client.
USB + PWR + Vol-: Appears a Fastboot kind of picture (Android mascot laying in the floor with his chest open and a Red Warning Symbol ) but no output whatsoever in [dmesg] or [udev monitor]
In neither these modes adb or fastboot detect something
---- For the Vol+ mode with the 10d6:10d6 device ----
I can't get adb or fastboot to work, even with adb_usb.ini edited in windows or linux or several different udev rules
The only udev rule I could trigger was
#IAIWAI
SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="10d6", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"
Click to expand...
Click to collapse
But it seems android_usb is not a link to a proper block device (the last number increases on each test)
ls -l /dev/
android_adb -> bus/usb/001/010
Click to expand...
Click to collapse
Or at least I can't make it work with
adb -p /dev/android_adb devices
or
fastboot -s /dev/android_adb devices
Extra information of the device found in Vol+ mode
lsusb:
Bus 001 Device 003: ID 10d6:10d6 Actions Semiconductor Co., Ltd
dmesg:
[11102.331560] usb 1-2: new high-speed USB device number 10 using ehci-pci
[11102.464620] usb 1-2: New USB device found, idVendor=10d6, idProduct=10d6
[11102.464633] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
udevadm monitor:
KERNEL[8596.157794] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
KERNEL[8596.158995] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
UDEV [8596.167280] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
UDEV [8596.171388] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
P: /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVPATH=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVTYPE=usb_interface
E: ID_VENDOR_FROM_DATABASE=Actions Semiconductor Co., Ltd
E: INTERFACE=255/255/255
E: MODALIAS=usb:v10D6p10D6d0100dc00dsc00dp00icFFiscFFipFFin00
E: PRODUCT=10d6/10d6/100
E: SUBSYSTEM=usb
E: TYPE=0/0/0
E: USEC_INITIALIZED=434099056
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 --attribute-walk:
looking at device '/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0':
KERNEL=="1-2:1.0"
SUBSYSTEM=="usb"
DRIVER==""
ATTR{bInterfaceClass}=="ff"
ATTR{bInterfaceSubClass}=="ff"
ATTR{bInterfaceProtocol}=="ff"
ATTR{bNumEndpoints}=="02"
ATTR{supports_autosuspend}=="1"
ATTR{bAlternateSetting}==" 0"
ATTR{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1/1-2':
KERNELS=="1-2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="2"
ATTRS{idVendor}=="10d6"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="4"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="128mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0100"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="6"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="removable"
ATTRS{idProduct}=="10d6"
ATTRS{bDeviceClass}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="5"
ATTRS{bcdDevice}=="0313"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:12.2"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="91"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.13.0-37-generic ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:12.2':
KERNELS=="0000:00:12.2"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="17"
ATTRS{subsystem_vendor}=="0x1179"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{enabled}=="1"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
ATTRS{device}=="0x4396"
ATTRS{uframe_periodic_max}=="100"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-1"
ATTRS{vendor}=="0x1002"
ATTRS{subsystem_device}=="0xff1e"
ATTRS{numa_node}=="0"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
Click to expand...
Click to collapse