All of lore.kernel.org
 help / color / mirror / Atom feed
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 20:26:08 +0000	[thread overview]
Message-ID: <bug-9176-163-AALR9MO5iY@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9176-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9176

--- Comment #2 from CB <christophebricout@yahoo.fr> ---
Dear Ezequiel,

In order to clarify my issue, I made some additional test.
Please find here after the results 

SUMMARY: 

Using the default buildroot configuration paramaters, I am not able to mount an
external USB. For information, linux was booting sucessfully from SDcard.

So, I would like to know if I missed some steps/actions on buildroot
configuration in order to access an external USB drive .... 
Is that normal or a unix workaround is available.

Thanks in advance for your support.
I can make addionnal test.

Regards

Technical information: 

BUILDROOT VERSION:

I am using the last stable version of buildrppt (2016.05) and I am 
configuring  buildroot using minnowboard_max_defconfig file.

Note: The problem still exists with 2015.11.1


MINNOWBOARD MAX/TURBOT LOG FILE:

Here after, please find an extract of the screenshot.
The usb 2-1 device has been found but I am not able to mount it.

......       
usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd                      
fbcon: inteldrmfb (fb0) is primary device                                       
input: HDA Intel PCH HDMI/DP,pcm=3 as
/devices/pci0000:00/0000:00:1b.0/sound/ca4
input: HDA Intel PCH HDMI/DP,pcm=7 as
/devices/pci0000:00/0000:00:1b.0/sound/ca5
mmc2: new high speed SDHC card at address 0001                                  
mmcblk0: mmc2:0001 SD16G 14.6 GiB                                               
 mmcblk0: p1 p2  
Console: switching to colour frame buffer device 128x48                         
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device                          
EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities    
EXT4-fs (mmcblk0p2): couldn't mount as ext2 due to feature incompatibilities    
EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem             
EXT4-fs (mmcblk0p2): write access will be enabled during recovery               
clocksource: Switched to clocksource tsc                                        
EXT4-fs (mmcblk0p2): recovery complete                                          
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)    
VFS: Mounted root (ext4 filesystem) readonly on device 179:2.                   
devtmpfs: mounted                                                               
Freeing unused kernel memory: 808K (ffffffff81783000 - ffffffff8184d000)        
EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered                             
Starting logging: OK                                                            
Initializing random number generator... random: dd urandom read with 10 bits
ofe
done.    

Welcome to Buildroot                                                            
buildroot login: root   


MOUNT COMMAND :

# mount                                                                         
/dev/root on / type ext4 (rw,relatime,data=ordered)                             
devtmpfs on /dev type devtmpfs
(rw,relatime,size=975292k,nr_inodes=243823,mode=)
proc on /proc type proc (rw,relatime)                                           
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)                     
tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)                             
tmpfs on /tmp type tmpfs (rw,relatime)                                          
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)                    
sysfs on /sys type sysfs (rw,relatime)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2016-08-17 20:26 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 [this message]
2016-08-17 21:32 ` bugzilla at busybox.net
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-AALR9MO5iY@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.