kao Wrote:
-------------------------------------------------------
> how hard it is to get Debian running on NSA325v2?
> Or, better yet - will I be able to do that?
Since you already installed Debian on QNAP NAS, I think you already know pretty much of the hard stuff.
> I probably would be able to attach serial console should it be necessary.
I definitely suggest to have one ready as it simplifies a lot the debug.
I personally bought mine from e*Bay, it's a PL2303 serial 3.3 ttl usb.
> But I don't have skills to compile my own kernel
Thanks to Bodhi, it's not really needed: he already set up both a working Kernel and RootFS.
I can report that ArchLinuxArm works, too... but I still prefer Debian :D
> Just as an example, the initial instructions in the first post "in uboot type resetenv then reset
> the device" confuse me. How would I do get "in uboot"?
U-Boot it's the boot loader program of many NAS/embedded devices.
It resides on NAS flash storage (usually on initial blocks)
There exist "stock" and "upstream" versions: stock are the ones customized by the Vendor - so there exist "Marvel U-boot", "Lacie U-boot", etc - while native are re/compiled version of upstream version which support a broader range of features (eg: scripting, reliable usb booting, etc).
So to get "in uboot" [console], you generally need a serial cable, while you may use also a network console (upstream has support for it, some stock versions, too - eg Lacie's).
U-boot "environment" describe how and where it should boot from (usb, ide, flash, etc).
You can change env. from within u-boot console itself, or from OS (but if you may brick it and end up needing a serial cable).
> (haven't bought the actual device yet, as with stock firmware it won't fit my requirements).
No doubts, but it surprises me that a QNAP user hungers for more... maybe I just overvalued those devices?
Bye!
-------------------------------------------------------
> how hard it is to get Debian running on NSA325v2?
> Or, better yet - will I be able to do that?
Since you already installed Debian on QNAP NAS, I think you already know pretty much of the hard stuff.
> I probably would be able to attach serial console should it be necessary.
I definitely suggest to have one ready as it simplifies a lot the debug.
I personally bought mine from e*Bay, it's a PL2303 serial 3.3 ttl usb.
> But I don't have skills to compile my own kernel
Thanks to Bodhi, it's not really needed: he already set up both a working Kernel and RootFS.
I can report that ArchLinuxArm works, too... but I still prefer Debian :D
> Just as an example, the initial instructions in the first post "in uboot type resetenv then reset
> the device" confuse me. How would I do get "in uboot"?
U-Boot it's the boot loader program of many NAS/embedded devices.
It resides on NAS flash storage (usually on initial blocks)
There exist "stock" and "upstream" versions: stock are the ones customized by the Vendor - so there exist "Marvel U-boot", "Lacie U-boot", etc - while native are re/compiled version of upstream version which support a broader range of features (eg: scripting, reliable usb booting, etc).
So to get "in uboot" [console], you generally need a serial cable, while you may use also a network console (upstream has support for it, some stock versions, too - eg Lacie's).
U-boot "environment" describe how and where it should boot from (usb, ide, flash, etc).
You can change env. from within u-boot console itself, or from OS (but if you may brick it and end up needing a serial cable).
> (haven't bought the actual device yet, as with stock firmware it won't fit my requirements).
No doubts, but it surprises me that a QNAP user hungers for more... maybe I just overvalued those devices?
Bye!