Re: Finalizing Intel NAS SS4000-E installation

[hans@lambermont.dyndns.org (H)]

H wrote on 20101219:
> H wrote on 20101217:
> ...
> > EM-7210 ver.T04 2005-12-12 (For ver.AA)
> > == 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.
> > 
> > And nothing more.
> > I assume this kernel is not configured for console=ttyS0,115200
> 
> Jose kindly helped me try this exec line instead :
> exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
> The system boots fine. So 4x1TB disks work OK in the SS4000-E.

I also tested a 2TB disk. It's detected fine :
[    6.490000] sd 2:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
And I could access it OK.

> What is the recommended way to boot Debian on Arm without having to
> interrupt RedBoot, paste the kernel command line and add -r 0x01800000 ?

I got no responses, so I decided to try the fconfig boot_script_data way :

RedBoot> fconfig -l -n
boot_script: true
boot_script_data:
.. fis load ramdisk.gz
.. fis load zImage
.. exec

boot_script_timeout: 1
bootp: false
bootp_my_gateway_ip: 10.9.9.1
bootp_my_ip: 10.9.9.1
bootp_my_ip_mask: 255.255.255.0
bootp_server_ip: 10.9.9.10
console_baud_rate: 115200
dns_ip: 0.0.0.0
gdb_port: 9000
info_console_force: false
net_debug: false

RedBoot> fconfig boot_script_data
boot_script_data:
.. fis load ramdisk.gz
.. fis load zImage
.. exec
Enter script, terminate with empty line
>> fis load ramdisk.gz
>> fis load zImage
>> exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
>>
Update RedBoot non-volatile configuration - continue (y/n)? y
... Unlock from 0xf1fc0000-0xf1fc1000: .
... Erase from 0xf1fc0000-0xf1fc1000: .
... Program from 0x0ffd2000-0x0ffd3000 at 0xf1fc0000: .
... Lock from 0xf1fc0000-0xf1fc1000: .

RedBoot> fconfig boot_script_timeout
boot_script_timeout: 5
Update RedBoot non-volatile configuration - continue (y/n)? y
... Unlock from 0xf1fc0000-0xf1fc1000: .
... Erase from 0xf1fc0000-0xf1fc1000: .
... Program from 0x0ffd2000-0x0ffd3000 at 0xf1fc0000: .
... Lock from 0xf1fc0000-0xf1fc1000: .

RedBoot> reset
... Resetting.
+No network interfaces found

EM-7210 ver.T04 2005-12-12 (For ver.AA)
== Executing boot script in 5.000 seconds - enter ^C to abort
RedBoot> fis load ramdisk.gz
RedBoot> fis load zImage
RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
Using base address 0x01008000 and length 0x00200000
Uncompressing Linux... done, booting the kernel.
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32-5-iop32x (Debian 2.6.32-29) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Fri Dec 10 19:47:27 UTC 2010
[    0.000000] CPU: XScale-80219 [69052e20] revision 0 (ARMv5TE), cr=0000397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Lanner EM7210
...

So it works great :) I no longer have to type the long exec line.

20101221_151219 hans@stor:~/ uname -a
Linux stor 2.6.32-5-iop32x #1 Fri Dec 10 19:47:27 UTC 2010 armv5tel GNU/Linux
20101221_151611 hans@stor:~/ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux testing (squeeze)
Release:        testing
Codename:       squeeze

-- Hans Lambermont