what's your /etc/fstab file?do you install linux in another partition instead of the first partitionand mount your first partition in /boot?in this situation,you should remove /boot/,just leave uImage as this

this is, as far as I can tell, an identical hdd setup as I have on my LSPro V1 ... later today I could try to open up the V1, take its known good hdd out and put it in the v2 ... to see if I see the same error on the V2 w/ the V1's hdd ... of course the v1's uboot is different ...

right now I am reflashing the V2 w/ stock uboot via jtag ...

I am thinking that I may drop the netconsole uboot work for a few days, back up to the buffalo109 (1.1.1) source and try just getting it to boot foonas (which has no initrd) ... maybe there is something I missed in porting it from uboot 1.1.1 to 1.1.4 ...

btw, I have not tried the following yet:1. just disabling the env resets

2. just disabling the switch to tftp mode

3. using a truly stock partition to run foonas on ... though the only difference is that I have now an ext3 partition, and IIRC the stock format is ext2 ... it shouldn't make a difference there, though... but maybe there is something in the code that prevents ext3 from working?

the lsprostockuboot.bin that jonli left behind was a version 1.01 - probably from a lsprov1 ... it works w/ foonas just fine, even on the lsprov2... you can see the version string below ( buffalo_ver=BOOTVER=1.01 )... the only change that is needed between V1 and V2 is that the v2 needs 0:1 ...

the version 109 stuff for sure does have some sort of blocks built in that either by intent or otherwise make it difficult to use w/ anything other than stock OS ... a fresh build of version 109 makes it impossible to start up automatically... the tftp alarm comes on, since it looks for initrd in partition 1 and can't find it...

but if you change the env var "initrd" to have the value "boot/uImage" it does overcome this obstacle... and does boot automatically into foonas...

I'll try this again w/ the netconsole version again tomorrow... but maybe with the non-netconsole 1.1.4 uboot source first, to see if perhaps there was some minor change in 1.1.4 that we need to patch...

EDIT2: there are some differences in ext2 stuff, so this may be why the ext2 command set wasn't working right... the ide commands seem to work correctly though ...

...found the problem, it was just a minor change that I needed to backup to ... in common/cmd_ext2.c, so the ext2* commands in uboot work again...

this gives us currently:- basic netconsole (comes up by default)- will work with both stock OS from Buffalo, or foonas (from hdd or em)- fuller command set (everything in LNI's except the nfs stuff)- changes to env var bootcmd and def_tftp can now be persistent, so the user can define which files/image to tftp load and boot automatically if no valid hdd rootfs is found (ie, you can set it up to look for/boot a foonas-em image on a local tftp server in case your hdd has a problem)- switching back to serial console is possible by issuing "run ser" in uboot ...

still to do:- test in a LSProV1 and see if it will autodetect/find the correct hdd & partition on the V1 (1:1)- set up either autodetect or a hardware switch/button for changing to serial console instead of netconsole - add in the nfs stuff - make a few minor changes to the network/tftp timeouts so that the startup time is right around 15-20 seconds- disable the irritating Hi-Lo tftp alarm again...

from my experience, it will stay up (forever) as long as it has successfully found whatever the env var "initrd" is defined as ... I have it set to be 'uImage"

if it hasn't found this file on the hdd, it will indeed die out after 5 min or so... this can be dangerous if one is flashing something to ROM and the timer expires, so it would be nice to disable it completely ... (!)

It would be nice if it could be as simple as disabling it in include/configs/db88f5181.h, but it seems that it already is ... ?

Code:

.../* which initialization functions to call for this board */#define CONFIG_MISC_INIT_R 1 /* after relloc initialization*/#undef CONFIG_DISPLAY_MEMMAP /* at the end of the bootprocess show the memory map*/

#define CONFIG_ENV_OVERWRITE /* allow to change env parameters */

#undef CONFIG_WATCHDOG /* watchdog disabled */

/* Cache */...#define CFG_CACHELINE_SIZE 32

will look into this further...

EDIT: tiamo, after some talk on the irc, bbradley tipped me to checking out the micon commands ...issuing:

Code:

micon -0x35 -0xff

kept it up and running - it didn't die after 5 minutes... though this may have not been the exact command we were looking for ... probably

Code:

micon -0x01 -0x35

was the sought after one... maybe just about any micon command issued will do the trick...

Now we just need to code this in so that it will issue the proper micon command to keep it alive regardless of whether it found the initrd... this is important because it safeguards against the box automatically powering down - which would be disasterous (jtag!) if a user was flashing something to ROM while it shutdown automatically...

I'm wondering if it may be something that is called in case... the file specified in the env var initrd is not found... haven't had a chance to chase this down, but in board/mv88fxx81/Soc/uart/mvUart.c one can see how micon commands are sent... so maybe this shed light on how to tell micon to keep it up and running...

I am hopeful that it can be used either as is, with just changes to env vars, or with a bit of tweaking of the source code. It would be useful to have a single uboot that would work in either LSPro or the TeraStation... For that reason, I want to be careful to minimize any changes that would undercut it working in the TS-arm...

EDIT: something to add in - some prefigured scripts as uboot env vars that one could run to set it up for default boots into foonas or genlink:

ie: run foonasvars would set up def_tftp and bootcmd for automatic foonas booting , etc. run stockbootvars would do the same for restoring default boot vars for stockware or jtymod, etc.

just confirmed that the latest version that I built works in both the V1 and V2 LSPro - the serch_boot does indeed find the uImage correctly and boot it, regardless of it being on 0:1 or 1:1 (!) ... and it ought to (ehrr ... might) work on the TeraStation rev5, as well ... (the code shows it as a supported board, along with the lcd stuff)

boots my lsprov1 w/ foonas, seems to work well, with the fallback to tftp-em changed to pull in a foonas-em image... can finally work unfettered on foonas lsarm w/ netconsole which was my reason for doing this, anyway ... (and hopefully this will be one of the last times I have to open/close the case on my V1 )

...will work on making sure this is all just right for stock firmware, as well ... test this in both boxes for another week or so, code in persistent commands/scripts for:

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum