Need help with install Debian on INTEL SS4000-e

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Need help with install Debian on INTEL SS4000-e

Henk Smit

Hello my name is Henk Smit. I tried to rebuild my NAS (Intel SS4000-e, default with linux and proprietary IPSTOR NAS software) with a fresh Debian OS. This unfortunately failed and now I have an unusable system. Can someone tell me what to do, to make this system operational again? 
 
The steps that i have done.

First I enabled the SSH server on the default NAS software, and tried to update the system with the ss4000e.pkg software file (no changes to the system). Now I can connect the NAS throw putty terminal. Also I formatted all data from the hard disks (3x 1TB).

After this I downloaded the Debian installation files from the internet (initrd.zg and Zimage). With HyperTerminal and a serial cable connected to the NAS. The system reboots and I hit the control-C buttons to interrupt the system. To make a clean system I did erase the FIS memory by the fis inid command. The hard disk cannot be recognized at this moment and there is no connection possible via putty.
 
Below are the commands used to write the files in the flash memory:
 
- fis init (format all the flash apart from redboot)
- RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000
RedBoot config 0xF1FC0000 0xF1FC0000 0x00001000 0x00000000
FIS directory 0xF1FE0000 0xF1FE0000 0x00020000 0x00000000

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

- load -v -r -b 0x01800000 -m ymodem ramdisk.gz
- fis unlock -f 0xF0040000 -l 0x00400000
- fis create ramdisk.gz

- load -v -r -b 0x01008000 -m ymodem zImage
- fis unlock -f 0xF0040000 -l 0x00200000
- fis create zImage

After the commands I reset the system and hit the control-C buttons.

Now the fis list look like this
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000
RedBoot config 0xF1FC0000 0xF1FC0000 0x00001000 0x00000000
FIS directory 0xF1FE0000 0xF1FE0000 0x00020000 0x00000000
ramdisk.gz 0xF0040000 0x01800000 0x00440000 0x01800000
zImage 0xF0480000 0x01008000 0x00160000 0x01008000

 
To install the Debian OS I typed the following lines
- fis load ramdisk.gz
- fis load zImage
- exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000

Now the installation begins, after a while I get the following error message

 

+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 -w 5

Using base address 0x01008000 and length 0x0015ada0

Uncompressing Linux... done, booting the kernel.

[    0.000000] Initializing cgroup subsys cpuset

[    0.000000] Initializing cgroup subsys cpu

[    0.000000] Linux version 3.2.0-2-iop32x (Debian 3.2.18-1) ([hidden email]) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 Tue May 22 00:32:24 UTC 2012

[    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

[    0.000000] Memory policy: ECC disabled, Data cache writeback

[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024

[    0.000000] Kernel command line: console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000

[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)

[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

[    0.000000] Memory: 256MB = 256MB total

[    0.000000] Memory: 251600k/251600k available, 10544k reserved, 0K highmem

[    0.000000] Virtual kernel memory layout:

[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)

[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

[    0.000000]     vmalloc : 0xd0800000 - 0xfe000000   ( 728 MB)

[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)

[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)

[    0.000000]       .text : 0xc0008000 - 0xc0377f18   (3520 kB)

[    0.000000]       .init : 0xc0378000 - 0xc0397000   ( 124 kB)

[    0.000000]       .data : 0xc0398000 - 0xc03c81a0   ( 193 kB)

[    0.000000]        .bss : 0xc03c81c4 - 0xc040eb24   ( 283 kB)

[    0.000000] NR_IRQS:32

[    0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms

[    0.000000] Console: colour dummy device 80x30

[    0.000409] Calibrating delay loop... 398.13 BogoMIPS (lpj=1990656)

[    0.050061] pid_max: default: 32768 minimum: 301

[    0.050382] Security Framework initialized

[    0.050556] Mount-cache hash table entries: 512

[    0.051539] Initializing cgroup subsys cpuacct

[    0.051597] Initializing cgroup subsys memory

[    0.051664] Initializing cgroup subsys devices

[    0.051687] Initializing cgroup subsys freezer

[    0.051708] Initializing cgroup subsys net_cls

[    0.051730] Initializing cgroup subsys blkio

[    0.051786] Initializing cgroup subsys perf_event

[    0.051969] CPU: Testing write buffer coherency: ok

[    0.052759] hw perfevents: enabled with xscale1 PMU driver, 3 counters available

[    0.056226] devtmpfs: initialized

[    0.059305] print_constraints: dummy:

[    0.059934] NET: Registered protocol family 16

[    0.065550] PCI: bus0: Fast back to back transfers disabled

[    0.067915] pci 0000:00:01.0: BAR 0: assigned [mem 0x80000000-0x8001ffff]

[    0.067973] pci 0000:00:01.0: BAR 0: set to [mem 0x80000000-0x8001ffff] (PCI address [0x80000000-0x8001ffff])

[    0.068015] pci 0000:00:01.0: BAR 1: assigned [mem 0x80020000-0x8003ffff]

[    0.068055] pci 0000:00:01.0: BAR 1: set to [mem 0x80020000-0x8003ffff] (PCI address [0x80020000-0x8003ffff])

[    0.068098] pci 0000:00:01.0: BAR 6: assigned [mem 0x80040000-0x8005ffff pref]

[    0.068134] pci 0000:00:02.0: BAR 0: assigned [mem 0x80060000-0x8007ffff]

[    0.068175] pci 0000:00:02.0: BAR 0: set to [mem 0x80060000-0x8007ffff] (PCI address [0x80060000-0x8007ffff])

[    0.068216] pci 0000:00:02.0: BAR 1: assigned [mem 0x80080000-0x8009ffff]

[    0.068256] pci 0000:00:02.0: BAR 1: set to [mem 0x80080000-0x8009ffff] (PCI address [0x80080000-0x8009ffff])

[    0.068299] pci 0000:00:02.0: BAR 6: assigned [mem 0x800a0000-0x800bffff pref]

[    0.068337] pci 0000:00:03.0: BAR 0: assigned [mem 0x800c0000-0x800c0fff 64bit]

[    0.068381] pci 0000:00:03.0: BAR 0: set to [mem 0x800c0000-0x800c0fff 64bit] (PCI address [0x800c0000-0x800c0fff])

[    0.068423] pci 0000:00:05.0: BAR 0: assigned [mem 0x800c1000-0x800c1fff]

[    0.068464] pci 0000:00:05.0: BAR 0: set to [mem 0x800c1000-0x800c1fff] (PCI address [0x800c1000-0x800c1fff])

[    0.068505] pci 0000:00:05.1: BAR 0: assigned [mem 0x800c2000-0x800c2fff]

[    0.068545] pci 0000:00:05.1: BAR 0: set to [mem 0x800c2000-0x800c2fff] (PCI address [0x800c2000-0x800c2fff])

[    0.068587] pci 0000:00:05.2: BAR 0: assigned [mem 0x800c3000-0x800c30ff]

[    0.068627] pci 0000:00:05.2: BAR 0: set to [mem 0x800c3000-0x800c30ff] (PCI address [0x800c3000-0x800c30ff])

[    0.068668] pci 0000:00:01.0: BAR 2: assigned [io  0x90000000-0x9000003f]

[    0.068708] pci 0000:00:01.0: BAR 2: set to [io  0x90000000-0x9000003f] (PCI address [0x90000000-0x9000003f])

[    0.068749] pci 0000:00:02.0: BAR 2: assigned [io  0x90000040-0x9000007f]

[    0.068789] pci 0000:00:02.0: BAR 2: set to [io  0x90000040-0x9000007f] (PCI address [0x90000040-0x9000007f])

[    0.074657] bio: create slab <bio-0> at 0

[    0.076266] vgaarb: loaded

[    0.077784] Switching to clocksource iop_timer1

[    0.136565] NET: Registered protocol family 2

[    0.137107] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

[    0.139136] TCP established hash table entries: 8192 (order: 4, 65536 bytes)

[    0.139686] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

[    0.139967] TCP: Hash tables configured (established 8192 bind 8192)

[    0.139991] TCP reno registered

[    0.140033] UDP hash table entries: 256 (order: 0, 4096 bytes)

[    0.140096] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

[    0.140767] NET: Registered protocol family 1

[    0.142014] Unpacking initramfs...

[    1.433579] Initramfs unpacking failed: read error

[    1.467388] Freeing initrd memory: 4096K

[    1.467420] NetWinder Floating Point Emulator V0.97 (double precision)

[    1.469341] audit: initializing netlink socket (disabled)

[    1.469475] type=2000 audit(1.460:1): initialized

[    1.484779] VFS: Disk quotas dquot_6.5.2

[    1.485051] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

[    1.485437] msgmni has been set to 499

[    1.487401] alg: No test for stdrng (krng)

[    1.487948] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)

[    1.487997] io scheduler noop registered

[    1.488018] io scheduler deadline registered

[    1.488118] io scheduler cfq registered (default)

[    1.508096] iop-adma iop-adma.0: Intel(R) IOP: ( cpy intr )

[    1.528070] iop-adma iop-adma.1: Intel(R) IOP: ( cpy intr )

[    1.529417] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled

[    1.551939] serial8250.0: ttyS0 at MMIO 0xfe800000 (irq = 28) is a 16550A

[    2.128885] console [ttyS0] enabled

[    2.135109] physmap platform flash device: 02000000 at f0000000

[    2.141980] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000089 Chip ID 0x00891c

[    2.152423] Intel/Sharp Extended Query Table at 0x010A

[    2.157607] Intel/Sharp Extended Query Table at 0x010A

[    2.162815] Intel/Sharp Extended Query Table at 0x010A

[    2.168023] Intel/Sharp Extended Query Table at 0x010A

[    2.173234] Intel/Sharp Extended Query Table at 0x010A

[    2.178469] Using buffer write method

[    2.182144] Using auto-unlock on power-up/resume

[    2.186780] cfi_cmdset_0001: Erase suspend on write enabled

[    2.192681] Searching for RedBoot partition table in physmap-flash.0 at offset 0x1fe0000

[    2.327232] 5 RedBoot partitions found on MTD device physmap-flash.0

[    2.333736] Creating 5 MTD partitions on "physmap-flash.0":

[    2.339375] 0x000000000000-0x000000040000 : "RedBoot"

[    2.347736] 0x000000040000-0x000000480000 : "ramdisk.gz"

[    2.356682] 0x000000480000-0x0000005e0000 : "zImage"

[    2.365242] 0x000001fc0000-0x000001fc1000 : "RedBoot config"

[    2.371058] mtd: partition "RedBoot config" doesn't end on an erase block -- force read-only

[    2.382951] 0x000001fe0000-0x000002000000 : "FIS directory"

[    2.393584] mousedev: PS/2 mouse device common for all mice

[    2.399486] i2c /dev entries driver

[    2.408563] rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6

[    2.421820] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0

[    2.434412] TCP cubic registered

[    2.437683] NET: Registered protocol family 17

[    2.442343] Registering the dns_resolver key type

[    2.447178] XScale DSP coprocessor detected.

[    2.453160] registered taskstats version 1

[    2.460227] rtc-rs5c372 0-0032: setting system clock to 2112-09-25 19:00:08 UTC (209305912)

[    2.468840] Initializing network drop monitor service

[    2.475118] List of all partitions:

[    2.478788] 1f00             256 mtdblock0  (driver?)

[    2.483889] 1f01            4352 mtdblock1  (driver?)

[    2.489010] 1f02            1408 mtdblock2  (driver?)

[    2.494104] 1f03               4 mtdblock3  (driver?)

[    2.499216] 1f04             128 mtdblock4  (driver?)

[    2.504301] No filesystem could mount root, tried:

[    2.509244] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

[    2.517604] [<c001374c>] (unwind_backtrace+0x0/0xe0) from [<c02707cc>] (panic+0x50/0x194)

[    2.525871] [<c02707cc>] (panic+0x50/0x194) from [<c0378be8>] (mount_block_root+0x234/0x284)

[    2.534382] [<c0378be8>] (mount_block_root+0x234/0x284) from [<c0378dc0>] (prepare_namespace+0x124/0x184)

[    2.544015] [<c0378dc0>] (prepare_namespace+0x124/0x184) from [<c0378880>] (kernel_init+0x100/0x130)

[    2.553228] [<c0378880>] (kernel_init+0x100/0x130) from [<c000edf8>] (kernel_thread_exit+0x0/0x8)


I think the Debian installation crashes when mounting the HDDs. The HDDs are
formatted, and therefore I do not know what the root directory must be
installed (also no HDD connection and SSH possible).

 

I hope someone can help me with this problem.

Kind regards,
Henk Smit

 

 

Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

Maciej Soltysiak-2
Hi Henk,
 
I don't think the .pkg file is of any use. It didn't seem to change anything for me.
 
I believe I've had the same result when I used the netboot images (http://d-i.debian.org/daily-images/armel/daily/iop32x/netboot/ss4000e/)
I then tried with netconsole images and it worked fine:
 
p.s. I didn't check your redboot commands, mine were a bit different: I didn't do any unlocking or creating.
 
Good luck!
Maciej

On Thu, Sep 27, 2012 at 9:59 PM, Henk Smit <[hidden email]> wrote:

Hello my name is Henk Smit. I tried to rebuild my NAS (Intel SS4000-e, default with linux and proprietary IPSTOR NAS software) with a fresh Debian OS. This unfortunately failed and now I have an unusable system. Can someone tell me what to do, to make this system operational again? 
 
The steps that i have done.

First I enabled the SSH server on the default NAS software, and tried to update the system with the ss4000e.pkg software file (no changes to the system). Now I can connect the NAS throw putty terminal. Also I formatted all data from the hard disks (3x 1TB).

After this I downloaded the Debian installation files from the internet (initrd.zg and Zimage). With HyperTerminal and a serial cable connected to the NAS. The system reboots and I hit the control-C buttons to interrupt the system. To make a clean system I did erase the FIS memory by the fis inid command. The hard disk cannot be recognized at this moment and there is no connection possible via putty.
 
Below are the commands used to write the files in the flash memory:
 
- fis init (format all the flash apart from redboot)
- RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000
RedBoot config 0xF1FC0000 0xF1FC0000 0x00001000 0x00000000
FIS directory 0xF1FE0000 0xF1FE0000 0x00020000 0x00000000

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

- load -v -r -b 0x01800000 -m ymodem ramdisk.gz
- fis unlock -f 0xF0040000 -l 0x00400000
- fis create ramdisk.gz

- load -v -r -b 0x01008000 -m ymodem zImage
- fis unlock -f 0xF0040000 -l 0x00200000
- fis create zImage

After the commands I reset the system and hit the control-C buttons.

Now the fis list look like this
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000
RedBoot config 0xF1FC0000 0xF1FC0000 0x00001000 0x00000000
FIS directory 0xF1FE0000 0xF1FE0000 0x00020000 0x00000000
ramdisk.gz 0xF0040000 0x01800000 0x00440000 0x01800000
zImage 0xF0480000 0x01008000 0x00160000 0x01008000

 
To install the Debian OS I typed the following lines
- fis load ramdisk.gz
- fis load zImage
- exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000

Now the installation begins, after a while I get the following error message

 

+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 -w 5

Using base address 0x01008000 and length 0x0015ada0

Uncompressing Linux... done, booting the kernel.

[    0.000000] Initializing cgroup subsys cpuset

[    0.000000] Initializing cgroup subsys cpu

[    0.000000] Linux version 3.2.0-2-iop32x (Debian 3.2.18-1) ([hidden email]) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 Tue May 22 00:32:24 UTC 2012

[    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

[    0.000000] Memory policy: ECC disabled, Data cache writeback

[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024

[    0.000000] Kernel command line: console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000

[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)

[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

[    0.000000] Memory: 256MB = 256MB total

[    0.000000] Memory: 251600k/251600k available, 10544k reserved, 0K highmem

[    0.000000] Virtual kernel memory layout:

[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)

[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

[    0.000000]     vmalloc : 0xd0800000 - 0xfe000000   ( 728 MB)

[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)

[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)

[    0.000000]       .text : 0xc0008000 - 0xc0377f18   (3520 kB)

[    0.000000]       .init : 0xc0378000 - 0xc0397000   ( 124 kB)

[    0.000000]       .data : 0xc0398000 - 0xc03c81a0   ( 193 kB)

[    0.000000]        .bss : 0xc03c81c4 - 0xc040eb24   ( 283 kB)

[    0.000000] NR_IRQS:32

[    0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms

[    0.000000] Console: colour dummy device 80x30

[    0.000409] Calibrating delay loop... 398.13 BogoMIPS (lpj=1990656)

[    0.050061] pid_max: default: 32768 minimum: 301

[    0.050382] Security Framework initialized

[    0.050556] Mount-cache hash table entries: 512

[    0.051539] Initializing cgroup subsys cpuacct

[    0.051597] Initializing cgroup subsys memory

[    0.051664] Initializing cgroup subsys devices

[    0.051687] Initializing cgroup subsys freezer

[    0.051708] Initializing cgroup subsys net_cls

[    0.051730] Initializing cgroup subsys blkio

[    0.051786] Initializing cgroup subsys perf_event

[    0.051969] CPU: Testing write buffer coherency: ok

[    0.052759] hw perfevents: enabled with xscale1 PMU driver, 3 counters available

[    0.056226] devtmpfs: initialized

[    0.059305] print_constraints: dummy:

[    0.059934] NET: Registered protocol family 16

[    0.065550] PCI: bus0: Fast back to back transfers disabled

[    0.067915] pci 0000:00:01.0: BAR 0: assigned [mem 0x80000000-0x8001ffff]

[    0.067973] pci 0000:00:01.0: BAR 0: set to [mem 0x80000000-0x8001ffff] (PCI address [0x80000000-0x8001ffff])

[    0.068015] pci 0000:00:01.0: BAR 1: assigned [mem 0x80020000-0x8003ffff]

[    0.068055] pci 0000:00:01.0: BAR 1: set to [mem 0x80020000-0x8003ffff] (PCI address [0x80020000-0x8003ffff])

[    0.068098] pci 0000:00:01.0: BAR 6: assigned [mem 0x80040000-0x8005ffff pref]

[    0.068134] pci 0000:00:02.0: BAR 0: assigned [mem 0x80060000-0x8007ffff]

[    0.068175] pci 0000:00:02.0: BAR 0: set to [mem 0x80060000-0x8007ffff] (PCI address [0x80060000-0x8007ffff])

[    0.068216] pci 0000:00:02.0: BAR 1: assigned [mem 0x80080000-0x8009ffff]

[    0.068256] pci 0000:00:02.0: BAR 1: set to [mem 0x80080000-0x8009ffff] (PCI address [0x80080000-0x8009ffff])

[    0.068299] pci 0000:00:02.0: BAR 6: assigned [mem 0x800a0000-0x800bffff pref]

[    0.068337] pci 0000:00:03.0: BAR 0: assigned [mem 0x800c0000-0x800c0fff 64bit]

[    0.068381] pci 0000:00:03.0: BAR 0: set to [mem 0x800c0000-0x800c0fff 64bit] (PCI address [0x800c0000-0x800c0fff])

[    0.068423] pci 0000:00:05.0: BAR 0: assigned [mem 0x800c1000-0x800c1fff]

[    0.068464] pci 0000:00:05.0: BAR 0: set to [mem 0x800c1000-0x800c1fff] (PCI address [0x800c1000-0x800c1fff])

[    0.068505] pci 0000:00:05.1: BAR 0: assigned [mem 0x800c2000-0x800c2fff]

[    0.068545] pci 0000:00:05.1: BAR 0: set to [mem 0x800c2000-0x800c2fff] (PCI address [0x800c2000-0x800c2fff])

[    0.068587] pci 0000:00:05.2: BAR 0: assigned [mem 0x800c3000-0x800c30ff]

[    0.068627] pci 0000:00:05.2: BAR 0: set to [mem 0x800c3000-0x800c30ff] (PCI address [0x800c3000-0x800c30ff])

[    0.068668] pci 0000:00:01.0: BAR 2: assigned [io  0x90000000-0x9000003f]

[    0.068708] pci 0000:00:01.0: BAR 2: set to [io  0x90000000-0x9000003f] (PCI address [0x90000000-0x9000003f])

[    0.068749] pci 0000:00:02.0: BAR 2: assigned [io  0x90000040-0x9000007f]

[    0.068789] pci 0000:00:02.0: BAR 2: set to [io  0x90000040-0x9000007f] (PCI address [0x90000040-0x9000007f])

[    0.074657] bio: create slab <bio-0> at 0

[    0.076266] vgaarb: loaded

[    0.077784] Switching to clocksource iop_timer1

[    0.136565] NET: Registered protocol family 2

[    0.137107] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

[    0.139136] TCP established hash table entries: 8192 (order: 4, 65536 bytes)

[    0.139686] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

[    0.139967] TCP: Hash tables configured (established 8192 bind 8192)

[    0.139991] TCP reno registered

[    0.140033] UDP hash table entries: 256 (order: 0, 4096 bytes)

[    0.140096] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

[    0.140767] NET: Registered protocol family 1

[    0.142014] Unpacking initramfs...

[    1.433579] Initramfs unpacking failed: read error

[    1.467388] Freeing initrd memory: 4096K

[    1.467420] NetWinder Floating Point Emulator V0.97 (double precision)

[    1.469341] audit: initializing netlink socket (disabled)

[    1.469475] type=2000 audit(1.460:1): initialized

[    1.484779] VFS: Disk quotas dquot_6.5.2

[    1.485051] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

[    1.485437] msgmni has been set to 499

[    1.487401] alg: No test for stdrng (krng)

[    1.487948] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)

[    1.487997] io scheduler noop registered

[    1.488018] io scheduler deadline registered

[    1.488118] io scheduler cfq registered (default)

[    1.508096] iop-adma iop-adma.0: Intel(R) IOP: ( cpy intr )

[    1.528070] iop-adma iop-adma.1: Intel(R) IOP: ( cpy intr )

[    1.529417] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled

[    1.551939] serial8250.0: ttyS0 at MMIO 0xfe800000 (irq = 28) is a 16550A

[    2.128885] console [ttyS0] enabled

[    2.135109] physmap platform flash device: 02000000 at f0000000

[    2.141980] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000089 Chip ID 0x00891c

[    2.152423] Intel/Sharp Extended Query Table at 0x010A

[    2.157607] Intel/Sharp Extended Query Table at 0x010A

[    2.162815] Intel/Sharp Extended Query Table at 0x010A

[    2.168023] Intel/Sharp Extended Query Table at 0x010A

[    2.173234] Intel/Sharp Extended Query Table at 0x010A

[    2.178469] Using buffer write method

[    2.182144] Using auto-unlock on power-up/resume

[    2.186780] cfi_cmdset_0001: Erase suspend on write enabled

[    2.192681] Searching for RedBoot partition table in physmap-flash.0 at offset 0x1fe0000

[    2.327232] 5 RedBoot partitions found on MTD device physmap-flash.0

[    2.333736] Creating 5 MTD partitions on "physmap-flash.0":

[    2.339375] 0x000000000000-0x000000040000 : "RedBoot"

[    2.347736] 0x000000040000-0x000000480000 : "ramdisk.gz"

[    2.356682] 0x000000480000-0x0000005e0000 : "zImage"

[    2.365242] 0x000001fc0000-0x000001fc1000 : "RedBoot config"

[    2.371058] mtd: partition "RedBoot config" doesn't end on an erase block -- force read-only

[    2.382951] 0x000001fe0000-0x000002000000 : "FIS directory"

[    2.393584] mousedev: PS/2 mouse device common for all mice

[    2.399486] i2c /dev entries driver

[    2.408563] rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6

[    2.421820] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0

[    2.434412] TCP cubic registered

[    2.437683] NET: Registered protocol family 17

[    2.442343] Registering the dns_resolver key type

[    2.447178] XScale DSP coprocessor detected.

[    2.453160] registered taskstats version 1

[    2.460227] rtc-rs5c372 0-0032: setting system clock to 2112-09-25 19:00:08 UTC (209305912)

[    2.468840] Initializing network drop monitor service

[    2.475118] List of all partitions:

[    2.478788] 1f00             256 mtdblock0  (driver?)

[    2.483889] 1f01            4352 mtdblock1  (driver?)

[    2.489010] 1f02            1408 mtdblock2  (driver?)

[    2.494104] 1f03               4 mtdblock3  (driver?)

[    2.499216] 1f04             128 mtdblock4  (driver?)

[    2.504301] No filesystem could mount root, tried:

[    2.509244] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

[    2.517604] [<c001374c>] (unwind_backtrace+0x0/0xe0) from [<c02707cc>] (panic+0x50/0x194)

[    2.525871] [<c02707cc>] (panic+0x50/0x194) from [<c0378be8>] (mount_block_root+0x234/0x284)

[    2.534382] [<c0378be8>] (mount_block_root+0x234/0x284) from [<c0378dc0>] (prepare_namespace+0x124/0x184)

[    2.544015] [<c0378dc0>] (prepare_namespace+0x124/0x184) from [<c0378880>] (kernel_init+0x100/0x130)

[    2.553228] [<c0378880>] (kernel_init+0x100/0x130) from [<c000edf8>] (kernel_thread_exit+0x0/0x8)


I think the Debian installation crashes when mounting the HDDs. The HDDs are
formatted, and therefore I do not know what the root directory must be
installed (also no HDD connection and SSH possible).

 

I hope someone can help me with this problem.

Kind regards,
Henk Smit

 

 


Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

hans (Bugzilla)-10
In reply to this post by Henk Smit
Hoi Henk,

I followed
http://d-i.alioth.debian.org/manual/en.armel/ch05s01.html#boot-firmware-ss4000e

Henk Smit wrote on 20120927:
> +No network interfaces found

This is OK, see http://em7210.kwaak.net/cgi-bin/trac.cgi/wiki/DebianInstall

Did you try these ?
http://d-i.debian.org/daily-images/armel/daily/iop32x/network-console/ss4000e/

> [    2.504301] No filesystem could mount root, tried:
> [    2.509244] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(1,0)
>
> I think the Debian installation crashes when mounting the HDDs.

I think it is too early to boot from the HDDs, I think you first need to
install Debian there. I don't think you can keep the HDD contents. If
this is not correct I hope someone will jump in.

-- Hans


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/20120928204857.GG5400@...

Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

JF Straeten

LO,

On Fri, Sep 28, 2012 at 10:48:57PM +0200, Hans wrote:

> Henk Smit wrote on 20120927:
> > +No network interfaces found
>
> This is OK, see http://em7210.kwaak.net/cgi-bin/trac.cgi/wiki/DebianInstall

No, I think it's not good at all. Henk as nuked the 'rammode' of the
nas, which initialise the network interfaces (he as erased the
original flash...).

 

> Did you try these ?
> http://d-i.debian.org/daily-images/armel/daily/iop32x/network-console/ss4000e/
>
> > [    2.504301] No filesystem could mount root, tried:
> > [    2.509244] Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(1,0)
> >
> > I think the Debian installation crashes when mounting the HDDs.
>
> I think it is too early to boot from the HDDs, I think you first need to
> install Debian there. I don't think you can keep the HDD contents. If
> this is not correct I hope someone will jump in.

Aren't these lines relatives to the mounting of the inirtd, before
mounting the normal root filesystem ?

I will take the original message, to see what can be done...

A+

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/20120929174600.GA29989@...

Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

JF Straeten
In reply to this post by Henk Smit

LO Henk,


On Thu, Sep 27, 2012 at 09:59:14PM +0200, Henk Smit wrote:

[...]

> First I enabled the SSH server on the default NAS software, and
> tried to update the system with the ss4000e.pkg software file (no
> changes to the system).

(Not usefull/relevant. IIRC, the ss4000e.pkg is intented to be loaded
through the origial web interface of the device.)

 
> After this I downloaded the Debian installation files from the
> internet (initrd.zg and Zimage). With HyperTerminal and a serial
> cable connected to the NAS. The system reboots and I hit the
> control-C buttons to interrupt the system. To make a clean system I
> did erase the FIS memory by the fis inid command. The hard disk
> cannot be recognized at this moment and there is no connection
> possible via putty.

You shouldn't delete anything at first to install Debian on it, and by
doing this, I think you've deleted the 'rammode' of the device, which
is necessary to get access to the network for installation :-(

   
> Below are the commands used to write the files in the flash memory:
>  
> - fis init (format all the flash apart from redboot)

Sorry, but not a good idea. You need 'rammode' to install Debian...


[...]
> Now the installation begins, after a while I get the following error message
>
> +No network interfaces found

By doing 'fis load rammode', you'll have gained access to the
network...


[...]
> RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000"
> -r 0x01800000 -w 5
[...]

> [    2.504301] No filesystem could mount root, tried:
>
> [    2.509244] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(1,0)

If I understand right, Debian installer boots correctly, but the root
FS is not in ram anymore (root=/dev/ram) since you wrote it on the
flash, but I'm unsure...



> I hope someone can help me with this problem.

I've several ideas to get you back on the right side, but unsure of
the result.

So I will state them at first, and if nobody objects (perhaps Arnaud
has a better idea ?), you can try them in order :

1. alter the boot exec line to mention the correct root=<device>
   instead of /dev/ram.

   Your initrd should be on one of the mtdblockX listed by d-i :

[    2.475118] List of all partitions:
[    2.478788] 1f00             256 mtdblock0  (driver?)
[    2.483889] 1f01            4352 mtdblock1  (driver?)
[    2.489010] 1f02            1408 mtdblock2  (driver?)
[    2.494104] 1f03               4 mtdblock3  (driver?)
[    2.499216] 1f04             128 mtdblock4  (driver?)


   My guess is for the second one, if creation of the blocks follows
   the before list in same order :

[    2.333736] Creating 5 MTD partitions on "physmap-flash.0":
[    2.339375] 0x000000000000-0x000000040000 : "RedBoot"
[    2.347736] 0x000000040000-0x000000480000 : "ramdisk.gz"
[    2.356682] 0x000000480000-0x0000005e0000 : "zImage"
[snip]

   Ramdisk seems to be the second one.

   So try to issue the following exec line :

RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/mtd1 mem=256M@0xa0000000" -r 0x01800000

   But : a) I'm not sure at all it will work (the partition /dev/mtdX
   doesn't seem to be recognized from the list above which state
   '1f0X')

   b) trying also the other ones won't hurt (mtd[0-4]), just in case ;


2. reinstall the IPStor crap, with the supplied CD-Rom, and restart
   cleanly from there.

   You'll need a Window$ machine and in theory, the software on this
   CD should be able to detect the misfunctionning of the nas and
   restore the missing files on the flash.


3. simply copy a original rammode file (and perhaps other files too)
   from another same nas ?
   
   You seem to be confident with fis unlock/create commands and can
   perhaps restore manualy the content of the flash, to go from a
   known and clean state ?



It's just some ideas...

The 1 can be tried. At worst, it won't work.

But for the 2 et 3, since they alter the flash, my advice is to wait a
couple or hours for possible comments from the list before trying
anything.

Hih though,

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/20120929182910.GB29989@...

Reply | Threaded
Open this post in threaded view
|

RE: Need help with install Debian on INTEL SS4000-e

Henk Smit
Hi JFS,

Thanks for your advice. That's right i deleted the complete flash memory.
I only have redboot without rammode installed
I'm going to try the first proposal. I will let you know if it worked.

Gr. Henk

-----Oorspronkelijk bericht-----
Van: JF Straeten [mailto:[hidden email]]
Verzonden: zaterdag 29 september 2012 20:29
Aan: [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e


LO Henk,


On Thu, Sep 27, 2012 at 09:59:14PM +0200, Henk Smit wrote:

[...]

> First I enabled the SSH server on the default NAS software, and tried
> to update the system with the ss4000e.pkg software file (no changes to
> the system).

(Not usefull/relevant. IIRC, the ss4000e.pkg is intented to be loaded
through the origial web interface of the device.)

 
> After this I downloaded the Debian installation files from the
> internet (initrd.zg and Zimage). With HyperTerminal and a serial cable
> connected to the NAS. The system reboots and I hit the control-C
> buttons to interrupt the system. To make a clean system I did erase
> the FIS memory by the fis inid command. The hard disk cannot be
> recognized at this moment and there is no connection possible via
> putty.

You shouldn't delete anything at first to install Debian on it, and by doing
this, I think you've deleted the 'rammode' of the device, which is necessary
to get access to the network for installation :-(

   
> Below are the commands used to write the files in the flash memory:
>  
> - fis init (format all the flash apart from redboot)

Sorry, but not a good idea. You need 'rammode' to install Debian...


[...]
> Now the installation begins, after a while I get the following error
> message
>
> +No network interfaces found

By doing 'fis load rammode', you'll have gained access to the network...


[...]
> RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/ram
mem=256M@0xa0000000"
> -r 0x01800000 -w 5
[...]

> [    2.504301] No filesystem could mount root, tried:
>
> [    2.509244] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(1,0)

If I understand right, Debian installer boots correctly, but the root FS is
not in ram anymore (root=/dev/ram) since you wrote it on the flash, but I'm
unsure...



> I hope someone can help me with this problem.

I've several ideas to get you back on the right side, but unsure of the
result.

So I will state them at first, and if nobody objects (perhaps Arnaud has a
better idea ?), you can try them in order :

1. alter the boot exec line to mention the correct root=<device>
   instead of /dev/ram.

   Your initrd should be on one of the mtdblockX listed by d-i :

[    2.475118] List of all partitions:
[    2.478788] 1f00             256 mtdblock0  (driver?)
[    2.483889] 1f01            4352 mtdblock1  (driver?)
[    2.489010] 1f02            1408 mtdblock2  (driver?)
[    2.494104] 1f03               4 mtdblock3  (driver?)
[    2.499216] 1f04             128 mtdblock4  (driver?)


   My guess is for the second one, if creation of the blocks follows
   the before list in same order :

[    2.333736] Creating 5 MTD partitions on "physmap-flash.0":
[    2.339375] 0x000000000000-0x000000040000 : "RedBoot"
[    2.347736] 0x000000040000-0x000000480000 : "ramdisk.gz"
[    2.356682] 0x000000480000-0x0000005e0000 : "zImage"
[snip]

   Ramdisk seems to be the second one.

   So try to issue the following exec line :

RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/mtd1
RedBoot> mem=256M@0xa0000000" -r 0x01800000

   But : a) I'm not sure at all it will work (the partition /dev/mtdX
   doesn't seem to be recognized from the list above which state
   '1f0X')

   b) trying also the other ones won't hurt (mtd[0-4]), just in case ;


2. reinstall the IPStor crap, with the supplied CD-Rom, and restart
   cleanly from there.

   You'll need a Window$ machine and in theory, the software on this
   CD should be able to detect the misfunctionning of the nas and
   restore the missing files on the flash.


3. simply copy a original rammode file (and perhaps other files too)
   from another same nas ?
   
   You seem to be confident with fis unlock/create commands and can
   perhaps restore manualy the content of the flash, to go from a
   known and clean state ?



It's just some ideas...

The 1 can be tried. At worst, it won't work.

But for the 2 et 3, since they alter the flash, my advice is to wait a
couple or hours for possible comments from the list before trying anything.

Hih though,

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact
[hidden email]
Archive: http://lists.debian.org/20120929182910.GB29989@...



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/002801cd9e7a$da6bd0b0$8f437210$@quicknet.nl

Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

Maciej Soltysiak-2
If things go worse for any reason I've made a copy of all mtd blocks shown in /proc/mtd by dd'ing that from /dev/mtdX to a file. If you ever need anything from that let me know.

root@Koryto:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00040000 00020000 "RedBoot"
mtd1: 00020000 00020000 "log"
mtd2: 00040000 00020000 "rammode"
mtd3: 00020000 00020000 "naskey"
mtd4: 00200000 00020000 "zImage"
mtd5: 00400000 00020000 "ramdisk.gz"
mtd6: 01880000 00020000 "vendor"
mtd7: 00080000 00020000 "wmdata"
mtd8: 00001000 00020000 "RedBoot config"
mtd9: 00020000 00020000 "FIS directory"

BTW. Did you erase other mtd blocks to make more space for a bigger kernel image? What was the motivation?

Regards,
Maciej

On Sat, Sep 29, 2012 at 9:44 PM, Henk Smit <[hidden email]> wrote:
Hi JFS,

Thanks for your advice. That's right i deleted the complete flash memory.
I only have redboot without rammode installed
I'm going to try the first proposal. I will let you know if it worked.

Gr. Henk

-----Oorspronkelijk bericht-----
Van: JF Straeten [mailto:[hidden email]]
Verzonden: zaterdag 29 september 2012 20:29
Aan: [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e


LO Henk,


On Thu, Sep 27, 2012 at 09:59:14PM +0200, Henk Smit wrote:

[...]

> First I enabled the SSH server on the default NAS software, and tried
> to update the system with the ss4000e.pkg software file (no changes to
> the system).

(Not usefull/relevant. IIRC, the ss4000e.pkg is intented to be loaded
through the origial web interface of the device.)


> After this I downloaded the Debian installation files from the
> internet (initrd.zg and Zimage). With HyperTerminal and a serial cable
> connected to the NAS. The system reboots and I hit the control-C
> buttons to interrupt the system. To make a clean system I did erase
> the FIS memory by the fis inid command. The hard disk cannot be
> recognized at this moment and there is no connection possible via
> putty.

You shouldn't delete anything at first to install Debian on it, and by doing
this, I think you've deleted the 'rammode' of the device, which is necessary
to get access to the network for installation :-(


> Below are the commands used to write the files in the flash memory:
>
> - fis init (format all the flash apart from redboot)

Sorry, but not a good idea. You need 'rammode' to install Debian...


[...]
> Now the installation begins, after a while I get the following error
> message
>
> +No network interfaces found

By doing 'fis load rammode', you'll have gained access to the network...


[...]
> RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/ram
mem=256M@0xa0000000"
> -r 0x01800000 -w 5
[...]

> [    2.504301] No filesystem could mount root, tried:
>
> [    2.509244] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(1,0)

If I understand right, Debian installer boots correctly, but the root FS is
not in ram anymore (root=/dev/ram) since you wrote it on the flash, but I'm
unsure...



> I hope someone can help me with this problem.

I've several ideas to get you back on the right side, but unsure of the
result.

So I will state them at first, and if nobody objects (perhaps Arnaud has a
better idea ?), you can try them in order :

1. alter the boot exec line to mention the correct root=<device>
   instead of /dev/ram.

   Your initrd should be on one of the mtdblockX listed by d-i :

[    2.475118] List of all partitions:
[    2.478788] 1f00             256 mtdblock0  (driver?)
[    2.483889] 1f01            4352 mtdblock1  (driver?)
[    2.489010] 1f02            1408 mtdblock2  (driver?)
[    2.494104] 1f03               4 mtdblock3  (driver?)
[    2.499216] 1f04             128 mtdblock4  (driver?)


   My guess is for the second one, if creation of the blocks follows
   the before list in same order :

[    2.333736] Creating 5 MTD partitions on "physmap-flash.0":
[    2.339375] 0x000000000000-0x000000040000 : "RedBoot"
[    2.347736] 0x000000040000-0x000000480000 : "ramdisk.gz"
[    2.356682] 0x000000480000-0x0000005e0000 : "zImage"
[snip]

   Ramdisk seems to be the second one.

   So try to issue the following exec line :

RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/mtd1
RedBoot> mem=256M@0xa0000000" -r 0x01800000

   But : a) I'm not sure at all it will work (the partition /dev/mtdX
   doesn't seem to be recognized from the list above which state
   '1f0X')

   b) trying also the other ones won't hurt (mtd[0-4]), just in case ;


2. reinstall the IPStor crap, with the supplied CD-Rom, and restart
   cleanly from there.

   You'll need a Window$ machine and in theory, the software on this
   CD should be able to detect the misfunctionning of the nas and
   restore the missing files on the flash.


3. simply copy a original rammode file (and perhaps other files too)
   from another same nas ?

   You seem to be confident with fis unlock/create commands and can
   perhaps restore manualy the content of the flash, to go from a
   known and clean state ?



It's just some ideas...

The 1 can be tried. At worst, it won't work.

But for the 2 et 3, since they alter the flash, my advice is to wait a
couple or hours for possible comments from the list before trying anything.

Hih though,

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact
[hidden email]
Archive: http://lists.debian.org/20120929182910.GB29989@...



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/002801cd9e7a$da6bd0b0$8f437210$@quicknet.nl


Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

JF Straeten

Re,

On Sat, Sep 29, 2012 at 09:54:34PM +0200, Maciej Soltysiak wrote:

> If things go worse for any reason I've made a copy of all mtd blocks
> shown in /proc/mtd by dd'ing that from /dev/mtdX to a file. If you
> ever need anything from that let me know.

Fine, if you've got a SS4000-E.

I can also take a copy of mine if needed.

 

> root@Koryto:~# cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00040000 00020000 "RedBoot"
> mtd1: 00020000 00020000 "log"
> mtd2: 00040000 00020000 "rammode"
> mtd3: 00020000 00020000 "naskey"
> mtd4: 00200000 00020000 "zImage"
> mtd5: 00400000 00020000 "ramdisk.gz"
> mtd6: 01880000 00020000 "vendor"
> mtd7: 00080000 00020000 "wmdata"
> mtd8: 00001000 00020000 "RedBoot config"
> mtd9: 00020000 00020000 "FIS directory"
>
> BTW. Did you erase other mtd blocks to make more space for a bigger
> kernel image? What was the motivation?

Henk want a (bit too) clean system... :-/

But his nas is not yet bricked ; we have some ressources to explore.

A+

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/20120929224635.GA6815@...

Reply | Threaded
Open this post in threaded view
|

RE: Need help with install Debian on INTEL SS4000-e

Henk Smit
Thank you guys that you want to help me solve this problem. I do not know
what to do anymore.
Is install of rammode needed to install debian?? Or is it possible to
install debian with the two files (ramdisk.gz and zImage).
I don't have a rammode file to install on the NAS. If I can get a copy of
your files is it possible to install it with redboot because I can't connect
the NAS throw putty (SSH).

Gr. Henk


-----Oorspronkelijk bericht-----
Van: JF Straeten [mailto:[hidden email]]
Verzonden: zondag 30 september 2012 0:47
Aan: [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e


Re,

On Sat, Sep 29, 2012 at 09:54:34PM +0200, Maciej Soltysiak wrote:

> If things go worse for any reason I've made a copy of all mtd blocks
> shown in /proc/mtd by dd'ing that from /dev/mtdX to a file. If you
> ever need anything from that let me know.

Fine, if you've got a SS4000-E.

I can also take a copy of mine if needed.

 

> root@Koryto:~# cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00040000 00020000 "RedBoot"
> mtd1: 00020000 00020000 "log"
> mtd2: 00040000 00020000 "rammode"
> mtd3: 00020000 00020000 "naskey"
> mtd4: 00200000 00020000 "zImage"
> mtd5: 00400000 00020000 "ramdisk.gz"
> mtd6: 01880000 00020000 "vendor"
> mtd7: 00080000 00020000 "wmdata"
> mtd8: 00001000 00020000 "RedBoot config"
> mtd9: 00020000 00020000 "FIS directory"
>
> BTW. Did you erase other mtd blocks to make more space for a bigger
> kernel image? What was the motivation?

Henk want a (bit too) clean system... :-/

But his nas is not yet bricked ; we have some ressources to explore.

A+

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact
[hidden email]
Archive: http://lists.debian.org/20120929224635.GA6815@...



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/000001cd9ee1$893f4e30$9bbdea90$@quicknet.nl

Reply | Threaded
Open this post in threaded view
|

RE: Need help with install Debian on INTEL SS4000-e

Henk Smit
In reply to this post by JF Straeten
JF Straeten and Maciej Soltysiak

I have changed/reinstall the installation files to a network console type
(suggestion Maciej Soltysiak)

Option 1 (a+b), doesn't make a change to install debian on the NAS.
I get the same error message

I tried the following commands:

exec -c "console=ttyS0,115200 rw root=/dev/mtd0 mem=256M@0xa0000000" -r
0x01800000
exec -c "console=ttyS0,115200 rw root=/dev/mtd1 mem=256M@0xa0000000" -r
0x01800000
exec -c "console=ttyS0,115200 rw root=/dev/mtd2 mem=256M@0xa0000000" -r
0x01800000
exec -c "console=ttyS0,115200 rw root=/dev/mtd3 mem=256M@0xa0000000" -r
0x01800000
exec -c "console=ttyS0,115200 rw root=/dev/mtd4 mem=256M@0xa0000000" -r
0x01800000


Option 2: I don't have the supplied CD-Rom anymore to reinstall the IPStor
software.

So I think that option 3 is now the best option??? Can someone help me to
get these files??
Thanks for the effort.

Gr. Henk



 

-----Oorspronkelijk bericht-----
Van: JF Straeten [mailto:[hidden email]]
Verzonden: zaterdag 29 september 2012 20:29
Aan: [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e


LO Henk,


On Thu, Sep 27, 2012 at 09:59:14PM +0200, Henk Smit wrote:

[...]

> First I enabled the SSH server on the default NAS software, and tried
> to update the system with the ss4000e.pkg software file (no changes to
> the system).

(Not usefull/relevant. IIRC, the ss4000e.pkg is intented to be loaded
through the origial web interface of the device.)

 
> After this I downloaded the Debian installation files from the
> internet (initrd.zg and Zimage). With HyperTerminal and a serial cable
> connected to the NAS. The system reboots and I hit the control-C
> buttons to interrupt the system. To make a clean system I did erase
> the FIS memory by the fis inid command. The hard disk cannot be
> recognized at this moment and there is no connection possible via
> putty.

You shouldn't delete anything at first to install Debian on it, and by doing
this, I think you've deleted the 'rammode' of the device, which is necessary
to get access to the network for installation :-(

   
> Below are the commands used to write the files in the flash memory:
>  
> - fis init (format all the flash apart from redboot)

Sorry, but not a good idea. You need 'rammode' to install Debian...


[...]
> Now the installation begins, after a while I get the following error
> message
>
> +No network interfaces found

By doing 'fis load rammode', you'll have gained access to the network...


[...]
> RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/ram
mem=256M@0xa0000000"
> -r 0x01800000 -w 5
[...]

> [    2.504301] No filesystem could mount root, tried:
>
> [    2.509244] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(1,0)

If I understand right, Debian installer boots correctly, but the root FS is
not in ram anymore (root=/dev/ram) since you wrote it on the flash, but I'm
unsure...



> I hope someone can help me with this problem.

I've several ideas to get you back on the right side, but unsure of the
result.

So I will state them at first, and if nobody objects (perhaps Arnaud has a
better idea ?), you can try them in order :

1. alter the boot exec line to mention the correct root=<device>
   instead of /dev/ram.

   Your initrd should be on one of the mtdblockX listed by d-i :

[    2.475118] List of all partitions:
[    2.478788] 1f00             256 mtdblock0  (driver?)
[    2.483889] 1f01            4352 mtdblock1  (driver?)
[    2.489010] 1f02            1408 mtdblock2  (driver?)
[    2.494104] 1f03               4 mtdblock3  (driver?)
[    2.499216] 1f04             128 mtdblock4  (driver?)


   My guess is for the second one, if creation of the blocks follows
   the before list in same order :

[    2.333736] Creating 5 MTD partitions on "physmap-flash.0":
[    2.339375] 0x000000000000-0x000000040000 : "RedBoot"
[    2.347736] 0x000000040000-0x000000480000 : "ramdisk.gz"
[    2.356682] 0x000000480000-0x0000005e0000 : "zImage"
[snip]

   Ramdisk seems to be the second one.

   So try to issue the following exec line :

RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/mtd1
RedBoot> mem=256M@0xa0000000" -r 0x01800000

   But : a) I'm not sure at all it will work (the partition /dev/mtdX
   doesn't seem to be recognized from the list above which state
   '1f0X')

   b) trying also the other ones won't hurt (mtd[0-4]), just in case ;


2. reinstall the IPStor crap, with the supplied CD-Rom, and restart
   cleanly from there.

   You'll need a Window$ machine and in theory, the software on this
   CD should be able to detect the misfunctionning of the nas and
   restore the missing files on the flash.


3. simply copy a original rammode file (and perhaps other files too)
   from another same nas ?
   
   You seem to be confident with fis unlock/create commands and can
   perhaps restore manualy the content of the flash, to go from a
   known and clean state ?



It's just some ideas...

The 1 can be tried. At worst, it won't work.

But for the 2 et 3, since they alter the flash, my advice is to wait a
couple or hours for possible comments from the list before trying anything.

Hih though,

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact
[hidden email]
Archive: http://lists.debian.org/20120929182910.GB29989@...



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/001c01cd9ef8$7d10bf60$77323e20$@quicknet.nl

Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

Maciej Soltysiak-2
In reply to this post by Henk Smit
On Sun, Sep 30, 2012 at 9:59 AM, Henk Smit <[hidden email]> wrote:
Is install of rammode needed to install debian?? Or is it possible to
install debian with the two files (ramdisk.gz and zImage).
I believe so. I only used these 2 files from:
http://d-i.debian.org/daily-images/armel/daily/iop32x/network-console/ss4000e/

Then loaded them with:

load -v -r -b 0x01800000 -m ymodem ramdisk.gz
load -v -r -b 0x01008000 -m ymodem zImage
exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000

This started the installer. After the installer I believe I had to make this a permanent boot script so again in redboot I did:

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

Yes, I have /dev/ram and it works.

Important thing to note is that whenever you copy/paste these commands make sure the double quotes/apostrophes are correct ", not anything else. And note that sometimes the 'x' might not be x, but some character resembling x.

So it's best to type them

I don't have a rammode file to install on the NAS. If I can get a copy of
your files is it possible to install it with redboot because I can't connect
the NAS throw putty (SSH).
rammode from my SS4000-E:
https://www.dropbox.com/s/d08q8s7sptn5jw1/rammode

I really hope this works for you. I've been lost with this system too :-)

Gr. Henk

Maciej
 

-----Oorspronkelijk bericht-----
Van: JF Straeten [mailto:[hidden email]]
Verzonden: zondag 30 september 2012 0:47
Aan: [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e


Re,

On Sat, Sep 29, 2012 at 09:54:34PM +0200, Maciej Soltysiak wrote:

> If things go worse for any reason I've made a copy of all mtd blocks
> shown in /proc/mtd by dd'ing that from /dev/mtdX to a file. If you
> ever need anything from that let me know.

Fine, if you've got a SS4000-E.

I can also take a copy of mine if needed.


> root@Koryto:~# cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00040000 00020000 "RedBoot"
> mtd1: 00020000 00020000 "log"
> mtd2: 00040000 00020000 "rammode"
> mtd3: 00020000 00020000 "naskey"
> mtd4: 00200000 00020000 "zImage"
> mtd5: 00400000 00020000 "ramdisk.gz"
> mtd6: 01880000 00020000 "vendor"
> mtd7: 00080000 00020000 "wmdata"
> mtd8: 00001000 00020000 "RedBoot config"
> mtd9: 00020000 00020000 "FIS directory"
>
> BTW. Did you erase other mtd blocks to make more space for a bigger
> kernel image? What was the motivation?

Henk want a (bit too) clean system... :-/

But his nas is not yet bricked ; we have some ressources to explore.

A+

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact
[hidden email]
Archive: http://lists.debian.org/20120929224635.GA6815@...



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/000001cd9ee1$893f4e30$9bbdea90$@quicknet.nl


Reply | Threaded
Open this post in threaded view
|

RE: Need help with install Debian on INTEL SS4000-e

Henk Smit

Maciej

Oke, now i see that you have loaded the rammode.

I'm going to try this now. I'll keep you informed.

 

Gr. Henk

 

Van: Maciej Soltysiak [mailto:[hidden email]]
Verzonden: zondag 30 september 2012 12:44
Aan: Henk Smit
CC: JF Straeten; [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e

 

On Sun, Sep 30, 2012 at 9:59 AM, Henk Smit <[hidden email]> wrote:

Is install of rammode needed to install debian?? Or is it possible to
install debian with the two files (ramdisk.gz and zImage).

I believe so. I only used these 2 files from:
http://d-i.debian.org/daily-images/armel/daily/iop32x/network-console/ss4000e/

Then loaded them with:

load -v -r -b 0x01800000 -m ymodem ramdisk.gz
load -v -r -b 0x01008000 -m ymodem zImage
exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000

This started the installer. After the installer I believe I had to make this a permanent boot script so again in redboot I did:

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

Yes, I have /dev/ram and it works.

Important thing to note is that whenever you copy/paste these commands make sure the double quotes/apostrophes are correct ", not anything else. And note that sometimes the 'x' might not be x, but some character resembling x.

So it's best to type them

I don't have a rammode file to install on the NAS. If I can get a copy of
your files is it possible to install it with redboot because I can't connect
the NAS throw putty (SSH).

rammode from my SS4000-E:
https://www.dropbox.com/s/d08q8s7sptn5jw1/rammode

I really hope this works for you. I've been lost with this system too :-)

Gr. Henk


Maciej
 


-----Oorspronkelijk bericht-----
Van: JF Straeten [mailto:[hidden email]]

Verzonden: zondag 30 september 2012 0:47

Aan: [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e

Re,

On Sat, Sep 29, 2012 at 09:54:34PM +0200, Maciej Soltysiak wrote:

> If things go worse for any reason I've made a copy of all mtd blocks
> shown in /proc/mtd by dd'ing that from /dev/mtdX to a file. If you
> ever need anything from that let me know.

Fine, if you've got a SS4000-E.

I can also take a copy of mine if needed.


> root@Koryto:~# cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00040000 00020000 "RedBoot"
> mtd1: 00020000 00020000 "log"
> mtd2: 00040000 00020000 "rammode"
> mtd3: 00020000 00020000 "naskey"
> mtd4: 00200000 00020000 "zImage"
> mtd5: 00400000 00020000 "ramdisk.gz"
> mtd6: 01880000 00020000 "vendor"
> mtd7: 00080000 00020000 "wmdata"
> mtd8: 00001000 00020000 "RedBoot config"
> mtd9: 00020000 00020000 "FIS directory"
>
> BTW. Did you erase other mtd blocks to make more space for a bigger
> kernel image? What was the motivation?

Henk want a (bit too) clean system... :-/

But his nas is not yet bricked ; we have some ressources to explore.

A+

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact
[hidden email]
Archive: http://lists.debian.org/20120929224635.GA6815@...



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Archive: http://lists.debian.org/000001cd9ee1$893f4e30$9bbdea90$@quicknet.nl

 

Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

JF Straeten
In reply to this post by Henk Smit

Re,

On Sun, Sep 30, 2012 at 09:59:31AM +0200, Henk Smit wrote:

> Thank you guys that you want to help me solve this problem. I do not know
> what to do anymore.

> Is install of rammode needed to install debian??

To get access to the network in Redboot, yes.

So, if you load d-i via tftp or http, you'll need it.

If you go with {X,Y,Z}modem to load, perhaps it will work without it.
(Unsure ; done mine through tftp...).

In the archives of the m-l, you'll find a detailled brain dump of what
I do to get Debian on it.

Hih,
 

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/20120930121303.GA1282@...

Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

Maciej Soltysiak-2
In reply to this post by Henk Smit
On Sun, Sep 30, 2012 at 12:54 PM, Henk Smit <[hidden email]> wrote:

Maciej

Oke, now i see that you have loaded the rammode.

I'm going to try this now. I'll keep you informed.

Hm, it might be that it worked for me with these images, not the d-i... If you fail with previous images try the ones from here:
http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-armel/current/images/iop32x/network-console/ss4000e/

I'm pretty sure all you need is working redboot, 2 right files and 3 commands in redboot. And use ymodem.

That might maybe explain why I had squeeze installed, not wheezy, which I tried but didn't do it.
Good thing is that after installing squeeze, you can add backports and install a 3.2 kernel, which works very smoothly, just apt-get and reboot.

Regards,
Maciej

Reply | Threaded
Open this post in threaded view
|

RE: Need help with install Debian on INTEL SS4000-e

Henk Smit

Hello again,

 

I have done the follow steps:

-       Install rammode (no change of the error)

-       Install different ramdisk.gz and zImage (from link below)

-       I tried the following exec commands

exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000

exec -c "console=ttyS0,115200 rw root=/dev/md0 mem=256M@0xa0000000" -r 0x01800000

exec -c "console=ttyS0,115200 rw root=/dev/mtd0 mem=256M@0xa0000000" -r 0x01800000

exec -c "console=ttyS0,115200 rw root=/dev/mtd1 mem=256M@0xa0000000" -r 0x01800000

exec -c "console=ttyS0,115200 rw root=/dev/mtd2 mem=256M@0xa0000000" -r 0x01800000

exec -c "console=ttyS0,115200 rw root=/dev/mtd3 mem=256M@0xa0000000" -r 0x01800000

exec -c "console=ttyS0,115200 rw root=/dev/mtd4 mem=256M@0xa0000000" -r 0x01800000

 

Unfortunately nothing has helped and still got the same error.

Is the exec command correct?

Perhaps it is best to have the original software (IPStor) to restore?

Does anyone have more suggestions for installing debian on the NAS?

 

Gr. Henk

 

 

Van: Maciej Soltysiak [mailto:[hidden email]]
Verzonden: zondag 30 september 2012 16:34
Aan: Henk Smit
CC: JF Straeten; [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e

 

On Sun, Sep 30, 2012 at 12:54 PM, Henk Smit <[hidden email]> wrote:

Maciej

Oke, now i see that you have loaded the rammode.

I'm going to try this now. I'll keep you informed.

Hm, it might be that it worked for me with these images, not the d-i... If you fail with previous images try the ones from here:
http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-armel/current/images/iop32x/network-console/ss4000e/

I'm pretty sure all you need is working redboot, 2 right files and 3 commands in redboot. And use ymodem.

That might maybe explain why I had squeeze installed, not wheezy, which I tried but didn't do it.
Good thing is that after installing squeeze, you can add backports and install a 3.2 kernel, which works very smoothly, just apt-get and reboot.

Regards,
Maciej

 

Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

JF Straeten

Hi Henk,


On Sun, Sep 30, 2012 at 08:10:39PM +0200, Henk Smit wrote:


> -       Install rammode (no change of the error)

To go to RAM mode, you should launch it with 'fis load rammode', and
then 'g'.

But wait... If you load kernel and ramdisk via {z,y,x}modem, perhaps
you don't need it since access to the network will not be needed from
inside Redboot...


See this link :

http://www.debian.org/releases/stable/armel/ch05s01.html.fr#boot-firmware

(Loading rammode seems to be there just as an option to get kernel and
initrd in the device's RAM.)

So let's try without it at first...



> -       Install different ramdisk.gz and zImage (from link below)

Can you try once with the 'netboot' one instead of the
'network-console' ? ('netboot' was the one I used, 'network-console'
is for remote installation via ssh, IISC.)

Here is the link :

http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-armel/current/images/iop32x/netboot/ss4000e/


After that, try :

load -v -r -b 0x01800000 -m ymodem initrd.gz
load -v -r -b 0x01008000 -m ymodem zImage
exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000


And ? Better ?

I'll cross the fingers ;)


--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/20120930185919.GA5445@...

Reply | Threaded
Open this post in threaded view
|

RE: Need help with install Debian on INTEL SS4000-e

Henk Smit
JFS,

It's finally working!!!! :-) I'm so happy

load -v -r -b 0x01800000 -m ymodem initrd.gz <-- this is different than
ramdisk.gz (I think that was the problem)
load -v -r -b 0x01008000 -m ymodem zImage
exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r
0x01800000

I'm doing this for several months and finally I can install debian. thank
you very much for the recommendations!!!
Without help, I would not have found it.

Gr. Henk


-----Oorspronkelijk bericht-----
Van: JF Straeten [mailto:[hidden email]]
Verzonden: zondag 30 september 2012 20:59
Aan: [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e


Hi Henk,


On Sun, Sep 30, 2012 at 08:10:39PM +0200, Henk Smit wrote:


> -       Install rammode (no change of the error)

To go to RAM mode, you should launch it with 'fis load rammode', and then
'g'.

But wait... If you load kernel and ramdisk via {z,y,x}modem, perhaps you
don't need it since access to the network will not be needed from inside
Redboot...


See this link :

http://www.debian.org/releases/stable/armel/ch05s01.html.fr#boot-firmware

(Loading rammode seems to be there just as an option to get kernel and
initrd in the device's RAM.)

So let's try without it at first...



> -       Install different ramdisk.gz and zImage (from link below)

Can you try once with the 'netboot' one instead of the 'network-console' ?
('netboot' was the one I used, 'network-console'
is for remote installation via ssh, IISC.)

Here is the link :

http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-armel/current/i
mages/iop32x/netboot/ss4000e/


After that, try :

load -v -r -b 0x01800000 -m ymodem initrd.gz load -v -r -b 0x01008000 -m
ymodem zImage exec -c "console=ttyS0,115200 rw root=/dev/ram
mem=256M@0xa0000000" -r 0x01800000


And ? Better ?

I'll cross the fingers ;)


--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact
[hidden email]
Archive: http://lists.debian.org/20120930185919.GA5445@...



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/000301cda019$eb490470$c1db0d50$@quicknet.nl

Reply | Threaded
Open this post in threaded view
|

Re: Need help with install Debian on INTEL SS4000-e

JF Straeten

Hi Henk,

On Mon, Oct 01, 2012 at 11:15:44PM +0200, Henk Smit wrote:


> It's finally working!!!! :-) I'm so happy

Wonderfull, and congrats !

 
> load -v -r -b 0x01800000 -m ymodem initrd.gz <-- this is different than
> ramdisk.gz (I think that was the problem)

Yes, maybe.


> load -v -r -b 0x01008000 -m ymodem zImage
> exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r
> 0x01800000
>
> I'm doing this for several months and finally I can install debian. thank
> you very much for the recommendations!!!
> Without help, I would not have found it.

Well, it's what mailing lists are for :-)

A+

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/20121001215053.GA2794@...

Reply | Threaded
Open this post in threaded view
|

RE: Need help with install Debian on INTEL SS4000-e

chris wilkinson-3
In reply to this post by Henk Smit
Just out of interest, what does your Flash map look like now since I think
you said you deleted everything at the beginning ($> fis list at the Redboot
prompt if I recall correctly).

Chris

-----Original Message-----
From: Henk Smit [mailto:[hidden email]]
Sent: Monday, October 01, 2012 5:16 PM
To: 'JF Straeten'; [hidden email]
Subject: RE: Need help with install Debian on INTEL SS4000-e

JFS,

It's finally working!!!! :-) I'm so happy

load -v -r -b 0x01800000 -m ymodem initrd.gz <-- this is different than
ramdisk.gz (I think that was the problem)
load -v -r -b 0x01008000 -m ymodem zImage
exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r
0x01800000

I'm doing this for several months and finally I can install debian. thank
you very much for the recommendations!!!
Without help, I would not have found it.

Gr. Henk


-----Oorspronkelijk bericht-----
Van: JF Straeten [mailto:[hidden email]]
Verzonden: zondag 30 september 2012 20:59
Aan: [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e


Hi Henk,


On Sun, Sep 30, 2012 at 08:10:39PM +0200, Henk Smit wrote:


> -       Install rammode (no change of the error)

To go to RAM mode, you should launch it with 'fis load rammode', and then
'g'.

But wait... If you load kernel and ramdisk via {z,y,x}modem, perhaps you
don't need it since access to the network will not be needed from inside
Redboot...


See this link :

http://www.debian.org/releases/stable/armel/ch05s01.html.fr#boot-firmware

(Loading rammode seems to be there just as an option to get kernel and
initrd in the device's RAM.)

So let's try without it at first...



> -       Install different ramdisk.gz and zImage (from link below)

Can you try once with the 'netboot' one instead of the 'network-console' ?
('netboot' was the one I used, 'network-console'
is for remote installation via ssh, IISC.)

Here is the link :

http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-armel/current/i
mages/iop32x/netboot/ss4000e/


After that, try :

load -v -r -b 0x01800000 -m ymodem initrd.gz load -v -r -b 0x01008000 -m
ymodem zImage exec -c "console=ttyS0,115200 rw root=/dev/ram
mem=256M@0xa0000000" -r 0x01800000


And ? Better ?

I'll cross the fingers ;)


--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact
[hidden email]
Archive: http://lists.debian.org/20120930185919.GA5445@...



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact
[hidden email]
Archive: http://lists.debian.org/000301cda019$eb490470$c1db0d50$@quicknet.nl


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/000001cda030$7cbb81b0$76328510$@net

Reply | Threaded
Open this post in threaded view
|

RE: Need help with install Debian on INTEL SS4000-e

Henk Smit
In reply to this post by JF Straeten
JFS,

Now i have installed Debian. And the system reboots.
It goes automatic to the Redboot command. What should I do to get the system
to boot with debian.

Mine fis list is the same as before:

EM-7210 ver.T04 2005-12-12 (For ver.AA)
== Executing boot script in 5.000 seconds - enter ^C to abort
RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xF0000000  0xF0000000  0x00040000  0x00000000
RedBoot config    0xF1FC0000  0xF1FC0000  0x00001000  0x00000000
FIS directory     0xF1FE0000  0xF1FE0000  0x00020000  0x00000000
ramdisk.gz        0xF01E0000  0x01800000  0x003E0000  0x01800000
zImage            0xF0040000  0x01008000  0x00140000  0x01008000
RedBoot>

Gr. Henk

-----Oorspronkelijk bericht-----
Van: JF Straeten [mailto:[hidden email]]
Verzonden: maandag 1 oktober 2012 23:51
Aan: [hidden email]
Onderwerp: Re: Need help with install Debian on INTEL SS4000-e


Hi Henk,

On Mon, Oct 01, 2012 at 11:15:44PM +0200, Henk Smit wrote:


> It's finally working!!!! :-) I'm so happy

Wonderfull, and congrats !

 
> load -v -r -b 0x01800000 -m ymodem initrd.gz <-- this is different
> than ramdisk.gz (I think that was the problem)

Yes, maybe.


> load -v -r -b 0x01008000 -m ymodem zImage exec -c
> "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r
> 0x01800000
>
> I'm doing this for several months and finally I can install debian.
> thank you very much for the recommendations!!!
> Without help, I would not have found it.

Well, it's what mailing lists are for :-)

A+

--

JFS.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact
[hidden email]
Archive: http://lists.debian.org/20121001215053.GA2794@...



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/000001cda05a$d9156050$8b4020f0$@quicknet.nl

12