I want to store my logging data on an USB memory stick. But as newcomer, I was not able to mount it.
The 8 GB-stick has one ext2 and one Fat32 partition of 4 GB each. I tried it under Angstroem and Ubuntu
without success. I tried a 1 GB stick as well.
ubuntu@omap:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 64MB QDI U2 DISK
The device has been detected properly, but it has not been mounted, as it did on my Ubuntu-PC.
This is just my SD-card.
Does the USB-host of BB support memory sticks? In the docu, I read only about Wifi-, Bluetooth-dongles, keyboard,
but not memory sticks.
Or must I install for this a dedicated software?
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?
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.
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
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
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#
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
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.
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.
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?
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
For what its worth, yesterday (5/23/12) there was some discussion on the IRC channel about this problem and I think that it is going to be fixed in the next release. Stay tuned…
I just built (6/5/12 18:00 PDT) a fresh Angstrom Beaglebone systemd-image which generated a 3.2.18 kernel and this problem still exists. Is there an existing fix, or will a future update resolve this issue?
