 Usb Drives Not Supported With Angstrom On Beagleboard? |
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > Angstrom & OpenZaurus  |
 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 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! |
 |
 
|
|
Jul 15 2010, 01:43 AM
Post
#2
|
|
|
Group: Members Posts: 131 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. |
|
|
|
|
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 |
|
|
|
|
Jul 15 2010, 02:18 AM
Post
#4
|
|
|
Group: Members Posts: 131 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 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 |
|
|
|
|
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.  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 |
|
|
|
|
Jul 15 2010, 03:26 PM
Post
#6
|
|
|
Group: Members Posts: 131 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). |
|
|
|
|
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:
|
Lo-Fi Version | Time is now: 25th May 2013 - 10:48 AM |