[Freedombox-discuss] Trouble getting freedom box running, u-boot_2012.04.01-2_armel.deb, freedombox-unstable_2012.1021/ dreamplug 1001

2012-11-09 Thread Johan Henselmans
Hello, I am having trouble getting a freedom box image running. I have per instructions on https://freedomboxfoundation.org/ubootUpgradeInstructions/index.en.html downloaded the latest version of uboot, which happened to be u-boot_2012.04.01-2_armel.deb, and put that on the dreamplug via the

Re: [Freedombox-discuss] Trouble getting freedom box running, u-boot_2012.04.01-2_armel.deb, freedombox-unstable_2012.1021/ dreamplug 1001

2012-11-10 Thread Nick M. Daly
Johan Henselmans writes: > Hello, > > I am having trouble getting a freedom box image running. > > I have per instructions on > https://freedomboxfoundation.org/ubootUpgradeInstructions/index.en.html > downloaded the latest version of uboot, which happened to be > u-boot_2012.04.01-2_armel.deb,

Re: [Freedombox-discuss] Trouble getting freedom box running, u-boot_2012.04.01-2_armel.deb, freedombox-unstable_2012.1021/ dreamplug 1001

2012-11-14 Thread Nick M. Daly
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-M

Re: [Freedombox-discuss] Trouble getting freedom box running, u-boot_2012.04.01-2_armel.deb, freedombox-unstable_2012.1021/ dreamplug 1001

2012-11-15 Thread Johan Henselmans
On 15 nov. 2012, at 04:05, Nick M. Daly 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 update

Re: [Freedombox-discuss] Trouble getting freedom box running, u-boot_2012.04.01-2_armel.deb, freedombox-unstable_2012.1021/ dreamplug 1001

2012-11-15 Thread Nick M. Daly
Johan Henselmans writes: > 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 set