On Fri, Feb 12, 2016 at 9:38 AM, Martin Michlmayr <t...@cyrius.com> wrote: > * Roger Shimizu <rogershim...@gmail.com> [2016-02-11 16:28]: >> Now it's clear, since in d-i, file >> build/pkg-lists/netboot/network-console/armel/orion5x.cfg >> >> oldsys-preseed >> # sata and ext2/ext3 modules are needed by oldsys-preseed to read the disk >> # -> disable due to size problems > > That doesn't explain what you're seeing. If oldsys-preseed cannot > read the disk on Buffalo devices, it should still generate a preseed > file with DHCP and a fallback IP address (as well as the lowmem > override). > > Please debug why (and what) is not working for you.
Thanks for your guide! Now I trace to the following file: - https://anonscm.debian.org/cgit/d-i/oldsys-preseed.git/tree/oldsys-preseed It seems I need to write a block for device tree based Linkstation. >> I think maybe it's necessary to split "orion5x" as: >> - orion5x with serial console support, which keeps current config, so >> as kuroboxpro can be supported >> - orion5x without serial console support, re-enable sata and ext4, but >> disable jffs2 and micro-evtd >> >> What's your idea? > > "with serial console support" would be the netboot image. So you're > suggesting that Kurobox Pro should use the netboot image whereas other > Buffalo devices should use network-console. I think network-console is a special variant of netboot. And serial console install works well on network-console image. > I don't know if Kurobox Pro all have a serial console. I used to have > such a device but I cannot remember anything about it. I owned a Kurobox Pro long time ago, but I don't have it anymore. I now it's simply Linkstation Pro (LS-GL) + one additional NAND flash + external SATA interface. For d-i, we can treat Kurobox Pro the same thing as Linkstation Pro. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
