[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: Cannot boot Freestor 4020 (SS-4000E)


I found that the fis config was wrong. The ramdisk.gz entry point was not
set the same as the -r value in the exec command. I fixed that by inserting
a fis create after each load

I also had to change the boot script with fconfig to be the full exec
command line as below, accepting the other defaults.

The files I used were from

load -v -r -b 0x01800000 -m ymodem ramdisk.gz
fis create ramdisk.gz
load -v -r -b 0x01008000 -m ymodem zImage
fis create zImage

and then to be sure

fis load ramdisk.gz
fis load zImage
exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r

and it boots to the d-i

-----Original Message-----
From: JF Straeten [mailto:jfstraeten@scarlet.be] 
Sent: Saturday, July 14, 2012 7:10 PM
To: debian-arm@lists.debian.org
Subject: Re: Cannot boot Freestor 4020 (SS-4000E)


On Fri, Jul 13, 2012 at 01:08:44PM -0400, Chris Wilkinson wrote:


> Does anyone know if 7220/4020 versions are available anywhere?

I don't believe it, but the SS4000E version seems to work, at least to
a large extend.

> It hangs on boot but boots from the console using fis load, exec.
> There is one disk is inserted which is disk1/4 of what was the RAID5
> set.
> Not sure what to try next to get it to boot on its own.

Perhaps to modify the boot script ?

Could you report here what's in it for now ?

You should play a bit in redboot to find the command to report its

> EM-438/EM-7220 ver.AG0 2006-05-23
> == Executing boot script in 1.000 seconds - enter ^C to abort
> RedBoot> fis load ramdisk.gz
> RedBoot> fis load zImage
> RedBoot> exec
> Using base address 0x01008000 and length 0x00200000
> Uncompressing Linux... done, booting the kernel.
> <<hangs here>>

How are you sure that it hangs ?

It can also be that it doesn't report anything to the serial console

If the < console=ttyS0,115200 > part is not in the exec cmdline, you
will see nothing on the serial console...

(But you should see the login prompt at the end of the boot process,

> If I start from the console it boots. So it seems the fis images are
> OK.


> RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/ram
> -r 0x01800000 -w 5

Your machine seems to boot normally with this exec cmdline.

So the idea is to put this line in the boot script.




To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Archive: 20120714231024.GA25889@jones.jfs.dt">http://lists.debian.org/20120714231024.GA25889@jones.jfs.dt

Reply to: