From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9176] minnowboard : USB not mounted
Date: Wed, 17 Aug 2016 21:32:02 +0000 [thread overview]
Message-ID: <bug-9176-163-nLOwG5wC0U@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9176-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9176
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Christophe,
I'm a bit surprised that you say that you are "not able to mount an
external USB".
First, check that the partitions on the device are detected:
$ cat /proc/partitions
If not, then you are missing a driver in your kernel (unlikely as you
said it was "detected").
Next, can you actually mount your USB drive manually, e.g. with:
$ mkdir /tmp/test
$ mount /dev/sda1 /tmp/test
If not, you might be missing support for that filesystem in the kernel.
If something was not working so far, then you need to adapt your Linux
kernel configuration to enable additional support (be it a driver or a
filesystem or both):
$ make linux-menuconfig
(and then enable the missing pieces)
$ make
And then restart from the beginning.
If everything works so far, then it means you are missing to mount the
partitions dynamically. You have to know that block devices are never
automounted by the kernel; you need a userspace program for that.
Ezequiel provided a list of possible solution to make the partitions
mounted automatically.
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-08-17 21:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 17:31 [Buildroot] [Bug 9176] New: minnowboard : USB not detected bugzilla at busybox.net
2016-08-15 17:37 ` [Buildroot] [Bug 9176] minnowboard : USB not mounted bugzilla at busybox.net
2016-08-15 18:32 ` bugzilla at busybox.net
2016-08-17 20:26 ` bugzilla at busybox.net
2016-08-17 21:32 ` bugzilla at busybox.net [this message]
2016-08-18 20:55 ` bugzilla at busybox.net
2016-08-18 21:02 ` bugzilla at busybox.net
2016-08-21 12:34 ` bugzilla at busybox.net
2016-08-22 0:27 ` bugzilla at busybox.net
2016-08-22 17:16 ` bugzilla at busybox.net
2016-08-22 17:30 ` bugzilla at busybox.net
2016-08-22 17:32 ` bugzilla at busybox.net
2016-08-22 17:34 ` bugzilla at busybox.net
2016-09-11 21:30 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-9176-163-nLOwG5wC0U@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox