[ARMedslack] Dreamplug: ERROR: Root partition has already been mounted read-write. Cannot check!

[Florian Koch]

OK, now i think i catch the problem:

if i boot from the u-boot loader with "boot" on the cmd, all works as
expected, if i boot "normal, ist broken as describes, so the bootparms are
wrong"

her is my printenv,

> Marvell>> printenv
> bootcmd=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1;
> ${x_bootcmd_ethernet}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv
> bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
> bootdelay=3
> baudrate=115200
> x_bootcmd_ethernet=ping 192.168.2.1
> x_bootcmd_usb=usb start
> x_bootargs=console=ttyS0,115200
> ethaddr=F0:AD:4E:00:B0:6C
> eth1addr=F0:AD:4E:00:B0:6D
> x_bootcmd_kernel=fatload usb 0:1 0x6400000 uImage
> ethact=egiga0
> bootargs=console=ttyS0,115200 root=/dev/sda2 rootdelay=10 ro
> x_bootargs_root=root=/dev/sda2 rootdelay=10 ro
> stdin=serial
> stdout=serial
> stderr=serial
>
> Environment size: 590/4092 bytes
>


On Sun, Apr 8, 2012 at 2:57 PM, Florian Koch <
florian.koch1981 at googlemail.com> wrote:

>  Hm ok, forgot what i say about the ro, i get the error, and if i set ro
> on the uboot bootargs, the kernel boots and stops at:
>
>> dfc0: 00000000 00000000 00000000 c003274c 00000000 00000000 df05b800
>> 00000000
>> dfe0: de4cdfe0 de4cdfe0 df259d38 c00326c8 c00095a4 c00095a4 00000000
>> 00000000
>> [<c02e8f48>] (mmc_io_rw_direct+0x20/0x2c) from [<c02e9e88>]
>> (sdio_readb+0x3c/0x5c)
>> [<c02e9e88>] (sdio_readb+0x3c/0x5c) from [<bf12013c>]
>> (sbi_interrupt+0xa4/0x1e4 [uap8xxx])
>> [<bf12013c>] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) from [<c02ea738>]
>> (sdio_irq_thread+0x74/0x234)
>> [<c02ea738>] (sdio_irq_thread+0x74/0x234) from [<c003274c>]
>> (kthread+0x84/0x90)
>> [<c003274c>] (kthread+0x84/0x90) from [<c00095a4>]
>> (kernel_thread_exit+0x0/0x8)
>> Code: 1a000000 e7f001f2 e58d4008 e58dc00c (e5900000)
>> ---[ end trace b7bb87bd4d1b074c ]---
>> mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full
>> duplex, flow control disabled
>>
>
> i have to hit STRG+C and then the boot continues.
>
>
> On Sun, Apr 8, 2012 at 2:11 PM, Florian Koch <
> florian.koch1981 at googlemail.com> wrote:
>
>> Hi,
>>
>> yes i have set the wrong uboot var, but when i append ro to the right
>> var, the system won't boot, the services cannot start because of ro system.
>>
>> but forgot about this error, i have build a new minirootfs with the
>> buildscript, and installed the new rootfs to the dreamplug.
>>
>> I can boot into the system, no ro error , and i have not set the uboot
>> vars to ro.
>>
>> but  i get  a kernel oops during boot, and the boot hangs for some time.
>> (see attached oops.txt)
>> i think this come from missing modules.
>>
>>
>>
>> On Sun, Apr 8, 2012 at 10:53 AM, Davide <louigi600 at yahoo.it> wrote:
>>
>>>
>>> I'd bet on "ro" missing on cmdline.
>>>
>>>
>>>
>>> ------------------------------
>>> Il dom 8 apr 2012 10:21 CEST, Stuart Winter ha scritto:
>>>
>>> >
>>> >>
>>> >> What does this output?
>>> >>
>>> >>
>>> >> cat /proc/cmdline
>>> >>
>>> >
>>> >If this is the case, go into u-boot and do:
>>> >printenv
>>> >
>>> >and match the values found in /proc/cmdline and you should be able to
>>> >identify which u-boot variable needs altering.
>>> >
>>> >--
>>> >Stuart Winter
>>> >Slackware ARM: www.armedslack.org
>>> >_______________________________________________
>>> >ARMedslack mailing list
>>> >ARMedslack at lists.armedslack.org
>>> >http://lists.armedslack.org/mailman/listinfo/armedslack
>>>
>>> _______________________________________________
>>> ARMedslack mailing list
>>> ARMedslack at lists.armedslack.org
>>> http://lists.armedslack.org/mailman/listinfo/armedslack
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20120408/78d4c3e1/attachment-0001.html>