marcogaio,
> Clearly, i've double checked the package
> installed/upgraded, doing the dist-upgrade, and
> none was added.
That's why I want to see the /boot directory. I want to doublecheck what kernel uImage and uInitrd files are being used.
> a) there's no an upgraded uboot for the ix4-200d,
> but seems that the stock firmware can boot to HD.
Yes, stock u-boot can boot USB and HDD.
> b) there's a way to boot an ''intermediate
> bootloader'', but here i'm totally lost
Not needed.
> d) i need to ''map'' correctly the MTD to be able
> to use fw_printenv (and fw_* generally); also here
> i'm lost.
Correct. Look for the content of the file /etc/fw_env.config. In Reto's thread: http://forum.doozan.com/read.php?3,25120, there should be description of this. It needs to match what was in stock rootfs (in NAND flash).
> Clearly, i've double checked the package
> installed/upgraded, doing the dist-upgrade, and
> none was added.
That's why I want to see the /boot directory. I want to doublecheck what kernel uImage and uInitrd files are being used.
> a) there's no an upgraded uboot for the ix4-200d,
> but seems that the stock firmware can boot to HD.
Yes, stock u-boot can boot USB and HDD.
> b) there's a way to boot an ''intermediate
> bootloader'', but here i'm totally lost
Not needed.
> d) i need to ''map'' correctly the MTD to be able
> to use fw_printenv (and fw_* generally); also here
> i'm lost.
Correct. Look for the content of the file /etc/fw_env.config. In Reto's thread: http://forum.doozan.com/read.php?3,25120, there should be description of this. It needs to match what was in stock rootfs (in NAND flash).