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:[email protected]] Verzonden: zondag 30 september 2012 12:44 Aan: Henk Smit CC: JF Straeten; [email protected] Onderwerp: Re: Need help with install Debian on INTEL SS4000-e On Sun, Sep 30, 2012 at 9:59 AM, Henk Smit <[email protected]> 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:[email protected]] Verzonden: zondag 30 september 2012 0:47 Aan: [email protected] 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 [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
