Arch Linux

Eddotan

Member

From: Colombia

Registered: 2010-08-19

Posts: 21

[solved]problems with my mp3 usbplayer

hiya~
i got a problem when my mp3 usbplayer is inserted, it isn't detected and thunar doesn't want mount it, which is weird because before it worked
my archlinux system has gvfs, gnome-vfs and thunar-volman installed and it doesn't work...
my mp3 player is a generic player: Gigatech by NOR-TEK GTMNI-4K140 4GB

someone have this problem with this mp3 player?
thanks and sorry for my bad english

Last edited by Eddotan (2011-04-06 00:04:41)

abarilla

Member

From: Colorado Springs, CO

Registered: 2006-12-06

Posts: 29

Re: [solved]problems with my mp3 usbplayer

Do you have Autofs setup?  This might be the problem: https://wiki.archlinux.org/index.php/Autofs

---

Sic gorgiamus allos subjectatos nunc

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,803

Re: [solved]problems with my mp3 usbplayer

Check the basics.

Starting with the device unplugged, plug it in and then look at (maybe post) dmesg | tail -20

Look to see if the device is identified, and if a device node (something like /dev/sdb is created in response to inserting it.  If so, then it is an automount problem.  If not, things get more interesting

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Eddotan

Member

From: Colombia

Registered: 2010-08-19

Posts: 21

Re: [solved]problems with my mp3 usbplayer

hmm nothing happens when i plug my mp3 player, but seems to be that it's detected according to dmesg | tail output

(eddotan!~)$ dmesg | tail
input: GENERIC INC. FUSB200 as /devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/input/input17
usbcore: registered new interface driver usbtouchscreen
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
hub 1-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
usb 1-1: USB disconnect, address 5
usb 1-1: new high speed USB device using ehci_hcd and address 6
input: GENERIC INC. FUSB200 as /devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/input/input18

but i don't see any device node in /dev/sd(tab)
then I type lsusb and in the last entry says "Unknown"

(eddotan!~)$ lsusb 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 013: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120
Bus 002 Device 003: ID 03eb:0902 Atmel Corp. 4-Port Hub
Bus 002 Device 004: ID 0ac8:305b Z-Star Microelectronics Corp. ZC0305 Webcam
Bus 002 Device 005: ID 0583:a000 Padix Co., Ltd (Rockfire) MaxFire G-08XU Gamepad
Bus 001 Device 006: ID 1234:5678 Unknown 
(eddotan!~)$ 

and indeed that is detected by the kernel according to usb-devices output

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  6 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1234 ProdID=5678 Rev=00.01
S:  Manufacturer=GENERIC INC.
S:  Product=FUSB200
S:  SerialNumber=01234567890G
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 Driver=usbtouchscreen

i dont know what to do

PS: AutoFS didn't work either

Last edited by Eddotan (2011-03-19 17:31:21)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,803

Re: [solved]problems with my mp3 usbplayer

Well, okay

Your system sees the USB device, and identifies it as a storage device.  Then something weird happens, the USB hub gets unhappy and the storage goes away. The driver re-enables it, after which things get ugly.

The manufacturer being 1234 and the device type being 5678 does not give me much hope.  It looks like the driver cannot talk to the device after re-enabling it, so it starts making things up.  Note that it is using the usbtouchscreen driver which (based on a short Google search) binds to 1234:5678.  Also, notice the serial number of the device.

The good news is that there may be nothing wrong with your automount mechanism

I think this may be a hardware problem.  It does not say so, but the hub may have tripped out due to an over current.  The messages indicate it may be EMI (Electomagnetic Interference).  While this may, or may not, be true, it is probably an indication there are problems with the communications. 

Does this device connect through a cable, or does it connect directly.  If it is a cable, try a different one or try plugging the device in directly.  You might see what happens if you try a powered external hub.  Try plugging the device in to the external hub, and then plug the hub into your computer, and vice-versa. 

I know you said it used to work, that is why I suspect the cable.  It could also be due to a change in the kernel.

You might try providing us with more lines at the tail of the dmesg output (it looks like some useful stuff may have been truncated)
I want to suggest posting the output of sudo lsusb -v  , but I fear it may be bogus data anyway.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Eddotan

Member

From: Colombia

Registered: 2010-08-19

Posts: 21

Re: [solved]problems with my mp3 usbplayer

after rebooting my pc, I've found something new, while thunar was running in console output appeared this:

EDIT: I just tried plug the device directly and the same happens

thunar-volman: Unsupported USB device type.
thunar-volman: Unsupported input device type.
thunar-volman: Unsupported input device type.
thunar-volman: Unsupported input device type.
thunar-volman: Unsupported USB device type.

here it is dmesg output with 'grep usb'

usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usb 2-2: new low speed USB device using ohci_hcd and address 2
input: Genius Optical Mouse as /devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.0/input/input6
generic-usb 0003:0458:003A.0001: input,hidraw0: USB HID v1.11 Mouse [Genius Optical Mouse] on usb-0000:00:02.0-2/input0
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usb 2-3: new full speed USB device using ohci_hcd and address 3
usb 2-4: new full speed USB device using ohci_hcd and address 4
usb 2-3.2: new low speed USB device using ohci_hcd and address 5
input: 2-Axis,8-Button  as /devices/pci0000:00/0000:00:02.0/usb2/2-3/2-3.2/2-3.2:1.0/input/input7
generic-usb 0003:0583:A000.0002: input,hidraw1: USB HID v1.10 Gamepad [2-Axis,8-Button ] on usb-0000:00:02.0-3.2/input0
input: zc3xx as /devices/pci0000:00/0000:00:02.0/usb2/2-4/input/input8
usbcore: registered new interface driver zc3xx
usb 1-1: new high speed USB device using ehci_hcd and address 5
input: GENERIC INC. FUSB200 as /devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/input/input9
usbcore: registered new interface driver usbtouchscreen
usbcore: registered new interface driver uas
usbcore: registered new interface driver usb-storage
usb 1-1: USB disconnect, address 5
usb 1-1: new high speed USB device using ehci_hcd and address 6
input: GENERIC INC. FUSB200 as /devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/input/input10
usb 1-1: USB disconnect, address 6
usb 1-1: new high speed USB device using ehci_hcd and address 7
input: GENERIC INC. FUSB200 as /devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/input/input11

and the dmesg output with tail -30:

vboxdrv: fAsync=0 offMin=0x4e3 offMax=0x95d
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.0.2 (interface 0x00160000).
Bluetooth: L2CAP ver 2.15
Bluetooth: L2CAP socket layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
eth0: no IPv6 routers present
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
usb 1-1: new high speed USB device using ehci_hcd and address 5
input: GENERIC INC. FUSB200 as /devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/input/input9
usbcore: registered new interface driver usbtouchscreen
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb 1-1: USB disconnect, address 5
usb 1-1: new high speed USB device using ehci_hcd and address 6
input: GENERIC INC. FUSB200 as /devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/input/input10
usb 1-1: USB disconnect, address 6
usb 1-1: new high speed USB device using ehci_hcd and address 7
input: GENERIC INC. FUSB200 as /devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/input/input11

and finally, here it is the lsusb output with -v option:
(obviously in the section of the device)

Bus 001 Device 005: ID 1234:5678 Unknown 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1234 Unknown
  idProduct          0x5678 
  bcdDevice            0.01
  iManufacturer          16 GENERIC INC.
  iProduct               32 FUSB200
  iSerial                96 01234567890Æ
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration         48 CONFIG STRING
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface             64 INTERFACE STRING
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               3
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

I hope that this information is useful, and thanks for your help

Last edited by Eddotan (2011-03-19 19:48:32)

blindfellian

Member

Registered: 2011-04-03

Posts: 1

Re: [solved]problems with my mp3 usbplayer

A had absolutely the same problem.
But when I load Ubuntu and tried to mount such a player, it was success!
So I formatted my player to FAT by Disk Utility and it started to work in ArchLinux too!

jackuess

Member

Registered: 2007-12-29

Posts: 6

Re: [solved]problems with my mp3 usbplayer

I have a device with the same Vendor Id and Product Id as Eddotans. Mine is too a generic mp3 player, but different brand. Now I've finally got it to appear as a USB mass storage device. I've done some other fiddling before so I don't know if this alone did it, but this is what I have to do in order to mount it:

modprobe -r usbtouchscreen
modprobe -r usb_storage
modprobe usb_storage

This is sort of a hack of course. If anyone else has a more permanent way of doing it it would be welcome.

Eddotan

Member

From: Colombia

Registered: 2010-08-19

Posts: 21

Re: [solved]problems with my mp3 usbplayer

@jackuess, hey, it works!
I could  do this automatically in a bash script executed by openbox at startup, idk if there is another way to do this instead.

(for now, this problem is solved)

thanks jackuess

Last edited by Eddotan (2011-04-06 00:05:15)

prokrypt

Member

Registered: 2006-04-06

Posts: 6

Re: [solved]problems with my mp3 usbplayer

The correct/cleaner solution would be to blacklist the usbtouchscreen module in rc.conf so that it doesn't load and try to take over your mp3 player's usb connection.