Loading ...
Sorry, an error occurred while loading the content.

fatten nlsu2 to 256Mo with mod Redboot (without Apex)

Expand Messages
  • nomore12357654
    Hi I would like to unterstand one (or more perhaps) thing. in this page http://www.nslu2-linux.org/wiki/HowTo/ModifyMemorySize I can read this: Update Nov 19
    Message 1 of 1 , May 2, 2007
    • 0 Attachment
      Hi I would like to unterstand one (or more perhaps) thing.

      in this page http://www.nslu2-linux.org/wiki/HowTo/ModifyMemorySize

      I can read this:
      "Update Nov 19 '06: I just used the information on "http://www.nslu2-
      linux.org/wiki/HowTo/BuildYourOwnRedBoot" to make a version of
      RedBoot that will boot my 64M slug. Actually I got a binary RedBoot
      by doing this on my other (Unslung) slug.
      |dd if=/dev/mtdblock0 of=redboot.bin|
      Then I used a hex editor to put the MAC address in (offset 0x3FFB0)
      and found & changed the instruction that sets up the memory
      controller (in my case offset 0x0020b0 changed from e3a01008 to
      e3a0100a; the last byte is what gets written to SDR_CONFIG). So now I
      have a Fatslug but I still have Redboot upgrade mode & TFTP."
      patch for redboot.bin = registry entry for SDR_CONFIG
      so > e3a01008 =32Mo default entry is 0x02000000 for 32M
      e3a0100A=64Mo 0x04000000 for 64M
      can I think e3a0100C=128Mo ? (or e3a0100E) 0x08000000 for 128M
      e3a0100E=256Mo ? (or e3a02005) 0x10000000 for 256M
      or I don't understand nothing?
      Can I change cmdline = tty0 ...................."mem=xxxMB@0x000000"
      without rebuild kernel (mod .bin to)?
      if I mod debianslug.bin (e3a0xxxx without change cmdline) the kernel
      compile itself with the correct value??
    Your message has been successfully submitted and would be delivered to recipients shortly.