OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Usb Drives Not Supported With Angstrom On Beagleboard?
Doppelfrog
post Jul 15 2010, 12:47 AM
Post #1





Group: Members
Posts: 3
Joined: 14-July 10
Member No.: 80,526



Hi all,
I appreciate that this may be a BeagleBoard issue, but I'm having a small problem getting USB drives to work on a recent Angstom build (from: http://www.angstrom-distribution.org/demo/...rootfs.tar.bz2)

Whenever I plug in a drive (for example a USB flash drive) I get messages like:

[ 17.044708] usb 1-1.4: new full speed USB device using musb_hdrcand address3
[ 17.162994] usb 1-1.4: not running at top speed; connect to a highspeed hub
[ 17.173461] usb 1-1.4: device v090c p1000 is not supported
[ 17.179046] usb 1-1.4: New USB device found, idVendor=090c,idProduct=1000
[ 17.186004] usb 1-1.4: New USB device strings: Mfr=1, Product=2,SerialNumbe0
[ 17.193420] usb 1-1.4: Product: USB Flash Disk
[ 17.197906] usb 1-1.4: Manufacturer: General


But obviously the drive is not mounted. Any ideas on what do here?


As a 'confirmation' of sorts, the same hardware configuration works with an earlier version of Angstrom. (By "works" I mean, mounts the USB drive correctly). The earlier Angstrom is the one referenced here: http://beagleboard.org/demo/esc#esc-100


Thanks in advance!
Go to the top of the page
 
+Quote Post
utx
post Jul 15 2010, 01:43 AM
Post #2





Group: Members
Posts: 135
Joined: 27-June 05
From: Prague, Czech Republic, Europe
Member No.: 7,468



I don't see a line where kernel reports partitions found.

Level 1: Kernel. Kernel detects device insertion, scans for partitions and sends an event to udev.

Level 2: Udev. udev should parse kernel events, create dev /dev/sd?{number} and send event upper

Level 3: udev mount script

Level 4: Advanced desktops don't use udev mount script. but in level 3 udev only sends signal. Desktop daemons (e. g. gvfs volume monitors together with desktop utilities or hal in older distros) ask for mounting if desktop decides to do so.
Go to the top of the page
 
+Quote Post
Doppelfrog
post Jul 15 2010, 01:55 AM
Post #3





Group: Members
Posts: 3
Joined: 14-July 10
Member No.: 80,526



QUOTE(utx @ Jul 15 2010, 10:43 AM) *
I don't see a line where kernel reports partitions found.

Level 1: Kernel. Kernel detects device insertion, scans for partitions and sends an event to udev.

Level 2: Udev. udev should parse kernel events, create dev /dev/sd?{number} and send event upper

Level 3: udev mount script

Level 4: Advanced desktops don't use udev mount script. but in level 3 udev only sends signal. Desktop daemons (e. g. gvfs volume monitors together with desktop utilities or hal in older distros) ask for mounting if desktop decides to do so.


Thanks

For what it's worth, this the full set of messages that get displayed upon insertion:

[ 35.721740] usb 1-1.1: new full speed USB device using musb_hdrc and address 3
[ 35.839691] usb 1-1.1: not running at top speed; connect to a high speed hub
[ 35.851379] usb 1-1.1: device v13fe p1a00 is not supported
[ 35.857330] usb 1-1.1: New USB device found, idVendor=13fe, idProduct=1a00
[ 35.864532] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 35.872192] usb 1-1.1: Product: USB DISK 2.0
[ 35.876831] usb 1-1.1: Manufacturer:
[ 35.881561] usb 1-1.1: SerialNumber: 077B11A0094B
[ 35.897094] scsi0 : usb-storage 1-1.1:1.0
[ 40.987396] usb 1-1.1: reset full speed USB device using musb_hdrc and address 3
[ 41.190490] usb 1-1.1: reset full speed USB device using musb_hdrc and address 3
[ 41.393646] usb 1-1.1: reset full speed USB device using musb_hdrc and address 3
[ 41.596893] usb 1-1.1: reset full speed USB device using musb_hdrc and address 3

Go to the top of the page
 
+Quote Post
utx
post Jul 15 2010, 02:18 AM
Post #4





Group: Members
Posts: 135
Joined: 27-June 05
From: Prague, Czech Republic, Europe
Member No.: 7,468



QUOTE(Doppelfrog @ Jul 15 2010, 11:55 AM) *
For what it's worth, this the full set of messages that get displayed upon insertion:

[ 35.721740] usb 1-1.1: new full speed USB device using musb_hdrc and address 3
[ 35.839691] usb 1-1.1: not running at top speed; connect to a high speed hub
[ 35.851379] usb 1-1.1: device v13fe p1a00 is not supported
[ 35.857330] usb 1-1.1: New USB device found, idVendor=13fe, idProduct=1a00
[ 35.864532] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 35.872192] usb 1-1.1: Product: USB DISK 2.0
[ 35.876831] usb 1-1.1: Manufacturer:
[ 35.881561] usb 1-1.1: SerialNumber: 077B11A0094B
[ 35.897094] scsi0 : usb-storage 1-1.1:1.0
[ 40.987396] usb 1-1.1: reset full speed USB device using musb_hdrc and address 3
[ 41.190490] usb 1-1.1: reset full speed USB device using musb_hdrc and address 3
[ 41.393646] usb 1-1.1: reset full speed USB device using musb_hdrc and address 3
[ 41.596893] usb 1-1.1: reset full speed USB device using musb_hdrc and address 3


Something apparently went wrong.

Here is the correct log (on a standard desktop x86_64, but Beagleboard should do similar things).

As you can see, your driver failed to scan the disc and reset happened instead.

It looks like a hardware problem. Try another disk or USB flash. Try to use powered hub. It may be a hardware problem or the device does not reply in time, or it wants too much power to start. I have similar problems with some flash cards from A-Data.

[ 9339.026040] usb 2-4: new high speed USB device using ehci_hcd and address 3
[ 9339.140925] usb 2-4: New USB device found, idVendor=0781, idProduct=6100
[ 9339.140928] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 9339.140930] usb 2-4: Product: SanDisk SD Plus
[ 9339.140932] usb 2-4: Manufacturer: SanDisk Corporation
[ 9339.140934] usb 2-4: SerialNumber: {removed from log}
[ 9339.141523] scsi6 : usb-storage 2-4:1.0
[ 9340.141713] scsi 6:0:0:0: Direct-Access SanDisk SD Plus 1.0 PQ: 0 ANSI: 2
[ 9340.141882] sd 6:0:0:0: Attached scsi generic sg7 type 0
[ 9340.144613] sd 6:0:0:0: [sdg] 3970048 512-byte logical blocks: (2.03 GB/1.89 GiB)
[ 9340.145061] sd 6:0:0:0: [sdg] Write Protect is off
[ 9340.145064] sd 6:0:0:0: [sdg] Mode Sense: 03 00 00 00
[ 9340.145066] sd 6:0:0:0: [sdg] Assuming drive cache: write through
[ 9340.147316] sd 6:0:0:0: [sdg] Assuming drive cache: write through
[ 9340.147321] sdg: sdg1
[ 9340.150684] sd 6:0:0:0: [sdg] Assuming drive cache: write through
[ 9340.150688] sd 6:0:0:0: [sdg] Attached SCSI removable disk
Go to the top of the page
 
+Quote Post
Doppelfrog
post Jul 15 2010, 03:52 AM
Post #5





Group: Members
Posts: 3
Joined: 14-July 10
Member No.: 80,526



QUOTE(utx @ Jul 15 2010, 11:18 AM) *
...
Something apparently went wrong.

Here is the correct log (on a standard desktop x86_64, but Beagleboard should do similar things).

As you can see, your driver failed to scan the disc and reset happened instead.

It looks like a hardware problem. Try another disk or USB flash. Try to use powered hub. It may be a hardware problem or the device does not reply in time, or it wants too much power to start. I have similar problems with some flash cards from A-Data.
...


Hi, thanks for the response!
I have to admit that I'm not convinced that it's a hardware problem. smile.gif

Using exactly the same hardware config (powered USB 1.0 hub) but an earlier version of Ansgtrom (seems to be: Angstrom 2009.X-test-20090102 ) it all seems to work fine:

usb 1-1.4: new full speed USB device using musb_hdrc and address 8
usb 1-1.4: not running at top speed; connect to a high speed hub
usb 1-1.4: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
scsi 3:0:0:0: Direct-Access USB DISK 2.0 PMAP PQ: 0 ANSI: 0 CCS
sd 3:0:0:0: [sda] 8060928 512-byte hardware sectors (4127 MB)
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Assuming drive cache: write through
sd 3:0:0:0: [sda] 8060928 512-byte hardware sectors (4127 MB)
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Assuming drive cache: write through
sda:
sd 3:0:0:0: [sda] Attached SCSI removable disk
sd 3:0:0:0: Attached scsi generic sg0 type 0
Go to the top of the page
 
+Quote Post
utx
post Jul 15 2010, 03:26 PM
Post #6





Group: Members
Posts: 135
Joined: 27-June 05
From: Prague, Czech Republic, Europe
Member No.: 7,468



QUOTE(Doppelfrog @ Jul 15 2010, 01:52 PM) *
Using exactly the same hardware config (powered USB 1.0 hub) but an earlier version of Ansgtrom (seems to be: Angstrom 2009.X-test-20090102 ) it all seems to work fine:


Well, then it looks like a kernel or kernel config issue. You can try to ask in the relevant kernel mailing list (hardware specific or linux-usb).
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 20th November 2014 - 06:26 PM