Hi Martin, Sure. It may take me a few days to get some time, but I'll give it a try and let you know how it goes.
Mike On Sat, Jul 30, 2016 at 7:23 PM, Martin Michlmayr <t...@cyrius.com> wrote: > Mike, can you please give these instructions a go? This is what I > intend to post to the mv2120 list. > > -- > > Mike Thompson reported that Debian stretch (the upcoming Debian 9) > doesn't boot on the HP mv2120 anymore. I don't know how many Debian > users are left who run Debian on their mv2120. I gave away my device > several years ago. Recently I bought an mv2120 from eBay in order to > debug this issue. > > While I found a solution, it requires users to change a setting on their > device. Please make sure to make this change, otherwise your device > will no longer boot when you upgrade to Debian 9. > > The new settings are compatible with Debian 8 (jessie) and Debian 9 > (stretch), so I suggest you make the changes now. > > If you have serial console access to the mv2120, you can run some > commands in u-boot. Simply interrupt the boot process by pressing a key > and type the following: > > setenv loadAddr 0x0600000 > setenv bootcmd 'bootext2 0,1:1,2 0x0600000 /boot/uImage /dev/sda > /dev/sdb' > saveenv > > If you don't have a serial console, you can make the changes from within > Debian. Run the following commands: > > cat >/etc/fw_env.config <<EOF > /dev/mtd0 0x00000 0x1000 0x20000 > EOF > > fw_setenv loadAddr 0x0600000 > fw_setenv bootcmd "bootext2 0,1:1,2 0x0600000 /boot/uImage /dev/sda > /dev/sdb" > > This will create a config file so you can modify the u-boot environment > and use fw_setenv to update two boot variables. > > Once you made the changes, upgrades to Debian 9 should work fine and you > can also use the Debian installer if you want to perform a new > installation. > > Please note that Debian 9 will be the last release to support the HP > mv2120. > > -- > > Note that the installer from > > https://d-i.debian.org/daily-images/armel/daily/orion5x/network-console/hp/mv2120/netboot.img > will not boot right now with these settings. However, you can change the > loadAddr to 0x0500000 and it should work. I just commited a fix in Git so > it should work in a day or so with 0x0600000. > > -- > Martin Michlmayr > http://www.cyrius.com/ >
