* MMC not working reliably for Gumstix Overo Tide
@ 2011-12-10 0:45 Andre Puschmann
2011-12-10 1:24 ` Felipe Contreras
0 siblings, 1 reply; 3+ messages in thread
From: Andre Puschmann @ 2011-12-10 0:45 UTC (permalink / raw)
To: linux-omap
Hi list,
I've got a Gumstix Overo Tide (OMAP 3530) based board here which doesn't
have NAND and therefore needs the MMC to boot.
I've successfully built a kernel using Tony's master branch. The system
boots fine up to the point where the MMC driver loads (well, I guess
that is where the problem lies). I am using omap2plus_defconfig. The
weird thing is that sometimes the system hangs after printing "Waiting
for root device /dev/mmcblk0p2..." and sometimes after mounting the
rootfs. Any ideas? I've seen some probelms with MMC in the recent past,
could that be the cause?
Thanks in advance.
Cheers,
Andre
Kernel log:
[ 2.092224] Waiting for root device /dev/mmcblk0p2...
[ 2.271026] mmc0: host does not support reading read-only switch.
assuming write-enable.
[ 2.282379] mmc0: new high speed SDHC card at address b368
[ 2.292053] mmcblk0: mmc0:b368 USD 14.9 GiB
[ 2.303894] mmcblk0: p1 p2
[ 2.341644] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data
mode. Opts: (null)
[ 2.350891] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 2.358917] Freeing init memory: 208K
.. nothing happens here ..
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MMC not working reliably for Gumstix Overo Tide
2011-12-10 0:45 MMC not working reliably for Gumstix Overo Tide Andre Puschmann
@ 2011-12-10 1:24 ` Felipe Contreras
2011-12-10 13:41 ` Andre Puschmann
0 siblings, 1 reply; 3+ messages in thread
From: Felipe Contreras @ 2011-12-10 1:24 UTC (permalink / raw)
To: Andre Puschmann; +Cc: linux-omap
On Sat, Dec 10, 2011 at 2:45 AM, Andre Puschmann
<andre.puschmann@tu-ilmenau.de> wrote:
> I've got a Gumstix Overo Tide (OMAP 3530) based board here which doesn't
> have NAND and therefore needs the MMC to boot.
>
> I've successfully built a kernel using Tony's master branch. The system
> boots fine up to the point where the MMC driver loads (well, I guess
> that is where the problem lies). I am using omap2plus_defconfig. The
> weird thing is that sometimes the system hangs after printing "Waiting
> for root device /dev/mmcblk0p2..." and sometimes after mounting the
> rootfs. Any ideas? I've seen some probelms with MMC in the recent past,
> could that be the cause?
Have you tried this in the command line? rootwait rootdelay=1
--
Felipe Contreras
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MMC not working reliably for Gumstix Overo Tide
2011-12-10 1:24 ` Felipe Contreras
@ 2011-12-10 13:41 ` Andre Puschmann
0 siblings, 0 replies; 3+ messages in thread
From: Andre Puschmann @ 2011-12-10 13:41 UTC (permalink / raw)
To: linux-omap
On 12/10/2011 02:24 AM, Felipe Contreras wrote:
> On Sat, Dec 10, 2011 at 2:45 AM, Andre Puschmann
> <andre.puschmann@tu-ilmenau.de> wrote:
>> I've got a Gumstix Overo Tide (OMAP 3530) based board here which doesn't
>> have NAND and therefore needs the MMC to boot.
>>
>> I've successfully built a kernel using Tony's master branch. The system
>> boots fine up to the point where the MMC driver loads (well, I guess
>> that is where the problem lies). I am using omap2plus_defconfig. The
>> weird thing is that sometimes the system hangs after printing "Waiting
>> for root device /dev/mmcblk0p2..." and sometimes after mounting the
>> rootfs. Any ideas? I've seen some probelms with MMC in the recent past,
>> could that be the cause?
>
> Have you tried this in the command line? rootwait rootdelay=1
Jup, doesn't help, unfortunately.
-Andre
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-12-10 13:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-10 0:45 MMC not working reliably for Gumstix Overo Tide Andre Puschmann
2011-12-10 1:24 ` Felipe Contreras
2011-12-10 13:41 ` Andre Puschmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox