[Freedombox-discuss] Trouble getting freedom box running, u-boot_2012.04.01-2_armel.deb, freedombox-unstable_2012.1021/ dreamplug 1001
On 15 nov. 2012, at 04:05, Nick M. Daly <nick.m.daly at gmail.com> wrote:
> Johan, as you can see in the message included below, the errors X was
> receiving while booting its DreamPlug are precisely the same errors you
> had while booting your DreamPlug.
>
> This is the last conversation I had with X was after it updated its boot
> environment per the instructions in the Freedom-Maker README:
>
You are right, the boot environment was different. I updated the boot environment variables, and now it boots.
I had one remaining problem: Apparently the ethernet addresses are derived from the uboot environment, which apparently are flushed
when I updated to the latest uboot firmware, ifconfig gave:
eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
by setting ethaddr and eth1addr in the uboot environment, that got solved.
Example:
Marvell>> setenv ethaddr f0:ad:4e:01:xx:xx
Marvell>> setenv eth1addr f0:ad:4e:01:xx:xx
Marvell>> saveenv
Marvell>> reset
Just sent to the mailinglist so anybody else wont have to struggle.
>> I lied, I took another quick look and noticed that I did indeed have
>> to massage the boot environment. After setting the environment
>> variables mentioned in:
>>
>> https://github.com/NickDaly/freedom-maker/blob/master/README
>>
>> It now appears to be booting. (I really do have to run now, but it at
>> least made it through the first stage reboot.)
>
> Your error stack trace is exactly the same as X's was, as I confirmed
> below. So, try updating the boot environment (using a JTAG) according
> to FM's README and it should start booting. Apologies for the delay in
> the reply. If it still doesn't work for you, please reply to the list
> and join the IRC channel (#freedombox at irc.oftc.net), where someone
> should be available for interactive help. I'll try to be on IRC this
> weekend, in case this isn't figured out by then.
>
> Nick
>
> ----
>
> Nick Daly wrote:
>>
>> X, are these the errors you were seeing before you updated the boot
>> options on your DreamPlug? If so, I think we can fix Johan's problem:
>>
>> [ 5.905131] Initializing network drop monitor service
>> [ 5.910389] Waiting 10sec before mounting root device...
>> [ 15.916364] List of all partitions:
>> [ 15.919870] 1f00 512 mtdblock0 (driver?)
>> [ 15.924951] 1f01 64 mtdblock1 (driver?)
>> [ 15.930053] 1f02 64 mtdblock2 (driver?)
>> [ 15.935131] No filesystem could mount root, tried:
>> [ 15.940045] Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(0,0)
>> [ 15.948378] [<c0013664>] (unwind_backtrace+0x0/0xe0) from [<c02c2e14>]
>> (panic+0x50/0x194)
>> [ 15.956615] [<c02c2e14>] (panic+0x50/0x194) from [<c03e0be8>]
>> (mount_block_root+0x234/0x284)
>> [ 15.965104] [<c03e0be8>] (mount_block_root+0x234/0x284) from [<c03e0dc0>]
>> (prepare_namespace+0x124/0x184)
>> [ 15.974731] [<c03e0dc0>] (prepare_namespace+0x124/0x184) from [<c03e087c>]
>> (kernel_init+0x10c/0x140)
>> [ 15.983927] [<c03e087c>] (kernel_init+0x10c/0x140) from [<c000edf8>]
>> (kernel_thread_exit+0x0/0x8)
>
>
> X Wrote:
>>
>> Sorry for the delay in my reply. Yes, this looks similar to the error
>> messages I got before updating the boot environment:
>>
>> : [ 5.717252] Waiting 10sec before mounting root device...
>> : [ 15.723243] List of all partitions:
>> : [ 15.726751] 1f00 512 mtdblock0 (driver?)
>> : [ 15.731832] 1f01 64 mtdblock1 (driver?)
>> : [ 15.736934] 1f02 64 mtdblock2 (driver?)
>> : [ 15.742013] No filesystem could mount root, tried:
>> : [ 15.746926] Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(0,0)
>> : [ 15.755259] [<c0013664>] (unwind_backtrace+0x0/0xe0) from [<c02c2e14>]
>> (panic+0x50/0x194)
>> : [ 15.763497] [<c02c2e14>] (panic+0x50/0x194) from [<c03e0be8>]
>> (mount_block_root+0x234/0x284)
>> : [ 15.771984] [<c03e0be8>] (mount_block_root+0x234/0x284) from [<c03e0dc0>]
>> (prepare_namespace+0x124/0x184)
>> : [ 15.781612] [<c03e0dc0>] (prepare_namespace+0x124/0x184) from [<c03e087c>]
>> (kernel_init+0x10c/0x140)
>> : [ 15.790808] [<c03e087c>] (kernel_init+0x10c/0x140) from [<c000edf8>]
>> (kernel_thread_exit+0x0/0x8)
>>
>> Hope this helps!
>>
>> X
Johan Henselmans
johan at netsense.nl
Reply to: