I just tried to mount a USB thumb drive with a newer kernel: 3.2.16 which
I
downloaded from:
http://downloads.angstrom-distribution.org/demo/beaglebone/
(I downloaded & installed:
Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.05.09.img.xz<http://downloads.angstrom-distribution.org/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.05.09.img.xz>
)
I get the same results as with 3.2.14 - there is no sda entries...
Has anyone made any progress on this?
Greg,
Did you ever get this issue resolved? I am having exactly the same
problem.
You can various examples on this page:
udev - ArchWiki
So, I've been working with an Angstrom image that refuses to mount my
thumb drive;
the kernel sees the drive, but doesn't make any /dev/sd* entries.
Here's the dmesg:
[169469.679812] usb 1-1: new high-speed USB device number 3 using
musb-hdrc
[169469.823073] usb 1-1: New USB device found, idVendor=13fe,
idProduct=3100
[169469.823123] usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[169469.823158] usb 1-1: Product: Patriot Memory
[169469.823184] usb 1-1: Manufacturer:
[169469.823210] usb 1-1: SerialNumber: 07B31D01590167E5
[169469.830216] scsi1 : usb-storage 1-1:1.0
Entries added in /dev:
crw-rw-r-- 1 root root 189, 2 May 12 02:24 /dev/bus/usb/001/003
lrwxrwxrwx 1 root root 12 May 12 02:24 /dev/char/189:2 ->
../usbdev1.3
crw------- 1 root root 189, 2 May 12 02:24 /dev/usbdev1.3
I'm assuming usb-storage should have been responsible for taking the
next
step and generating the block device ...
I'm pretty sure this is
Angstrom-Cloud9-*-v2012.05-beaglebone-2012.04.22.img,
no extra stuff crammed into (or ripped out of) the kernel from my
direction ...
beaglebone# uname -a
Linux beaglebone 3.2.14 #1 Sat Apr 21 10:00:05 CEST 2012 armv7l
GNU/Linux
beaglebone#
Any suggestions?
Walter,
One way of automounting USB drives is to add a udev rule. I believe
this is how Ubuntu does it. I *think* that in the past Ubuntu or
Angstrom
for the BB included such a rule by default, but I just checked a
couple of
recent builds and neither of them has it.
You can various examples on this page:
udev - ArchWiki
If you are using a USB drive that is always connected to the BB, then
an
alternative is to add an entry to /etc/fstab that automatically mounts
the
drive at boot time, like
/dev/sda1 /media/disk1 vfat auto,umask=0 0 0
Dan
Hi Rob,
Many thanks for your hint.
I did it like you have decribed and it works perfectly.
I am surprised, that the info about the stick is hidden in dmesg.
And Ubuntu on the PC mounts the stick automatically. No way to get
this
comfort on BB?
Best regards
Walter
Walter,
One way of automounting USB drives is to add a udev rule. I believe
this is how Ubuntu does it. I *think* that in the past Ubuntu or
Angstrom
for the BB included such a rule by default, but I just checked a
couple of
recent builds and neither of them has it.
You can various examples on this page:
udev - ArchWiki
If you are using a USB drive that is always connected to the BB, then
an
alternative is to add an entry to /etc/fstab that automatically mounts
the
drive at boot time, like
/dev/sda1 /media/disk1 vfat auto,umask=0 0 0
Dan
Hi Rob,
Many thanks for your hint.
I did it like you have decribed and it works perfectly.
I am surprised, that the info about the stick is hidden in dmesg.
And Ubuntu on the PC mounts the stick automatically. No way to get
this
comfort on BB?
Best regards
Walter
-- To join: http://beagleboard.org/discuss
To unsubscribe from this group, send email to:
beagleboard+unsubscribe@googlegroups.com
Frequently asked questions: Frequently Asked Questions - BeagleBoard
I also am having this same problem. Just built an Angstrom 3.2.16 kernel
for my Beagleboard xM and the flash drive mounts as expected, but the
kernel (3.2.16) for the Beaglebone does not work.
I've tried the udev rules discussed above, but no changes on the bone.
Still doesn't work.
This is the extent of the console message when the flash drive is inserted
on the bone:
[ 284.483367] usb 1-1: new high-speed USB device number 3 using musb-hdrc
[ 284.628479] usb 1-1: New USB device found, idVendor=13fe, idProduct=3623
[ 284.635498] usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 284.642944] usb 1-1: Product: USB DISK Pro
[ 284.647247] usb 1-1: Manufacturer:
[ 284.651611] usb 1-1: SerialNumber: 07AA0C0886E80C31
[ 284.658843] scsi1 : usb-storage 1-1:1.0
Here is the console message from the same unit using Angstrom 3.2.0+:
[ 60.230206] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[ 60.375260] usb 1-1: New USB device found, idVendor=13fe, idProduct=3623
[ 60.382293] usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 60.389736] usb 1-1: Product: USB DISK Pro
[ 60.394022] usb 1-1: Manufacturer:
[ 60.398386] usb 1-1: SerialNumber: 07AA0C0886E80C31
[ 60.405583] scsi0 : usb-storage 1-1:1.0
[ 61.440431] scsi 0:0:0:0: Direct-Access USB DISK Pro
PMAP PS
[ 61.455853] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 62.972304] sd 0:0:0:0: [sda] 31246336 512-byte logical blocks: (15.9
GB/14.)
[ 62.981806] sd 0:0:0:0: [sda] Write Protect is off
[ 62.987051] sd 0:0:0:0: [sda] No Caching mode page present
[ 62.992832] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 63.003027] sd 0:0:0:0: [sda] No Caching mode page present
[ 63.008768] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 63.040487] sda: sda1
[ 64.571768] sd 0:0:0:0: [sda] No Caching mode page present
[ 64.577504] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 64.583903] sd 0:0:0:0: [sda] Attached SCSI removable disk
All works fine with that kernel.
Thanks for any insight.
Ross