NSLU2-Linux
view · edit · print · history

HowTo.FattenYourSlug History

Hide minor edits - Show changes to markup

June 27, 2008, at 12:04 PM by Mattia -- work made on mine
Changed lines 89-95 from:

On Newegg.com they sell SODIMMS (for Laptops) I was able to find PC133 Modules that are 256MB - 4 chips, the configuration is listed on the manufacturers web site as 32M X 64bits, CAS 2 the model I found is Crucial 256MB 144-Pin SO-DIMM PC 133 Notebook Memory Model CT32M64S8W7E and is about $30US plus $5 shipping as of 12/2007. (**Caution, I received a module which has 8x MT48LC16M16A2BG, which is a 256Mb part. --hjames)

to:

On Newegg.com they sell SODIMMS (for Laptops) I was able to find PC133 Modules that are 256MB - 4 chips, the configuration is listed on the manufacturers web site as 32M X 64bits, CAS 2 the model I found is Crucial 256MB 144-Pin SO-DIMM PC 133 Notebook Memory Model CT32M64S8W7E and is about $30US plus $5 shipping as of 12/2007. (**Caution, I received a module which has 8x MT48LC16M16A2BG, which is a 256Mb part. --hjames)


Comments on type of chips - Mattia
I have mount 4 chips of Samsung K4S511632D?-UC75? (8M x 16bit x 4 Banks) and work fine with 256M of ram. Desoldering with hot air solder next masked near SMD components and remove PTH components (like capacitors, buzzer...).

April 28, 2008, at 11:48 AM by Paul Brandt --
Added line 76:
April 28, 2008, at 11:48 AM by Paul Brandt --
Added line 77:
Added line 84:
April 28, 2008, at 11:45 AM by Paul Brandt --
Added line 81:
Deleted line 82:
April 28, 2008, at 11:44 AM by Paul Brandt --
Changed line 76 from:
to:

\\

Changed line 78 from:

These DMA errors are reported to occur for upgrades to 128 and 256MB only. Please confirm or negate my following conclusions:

to:

\\These DMA errors are reported to occur for upgrades to 128 and 256MB only. Please confirm or negate my following conclusions:

Added line 82:
April 28, 2008, at 11:43 AM by Paul Brandt -- Questions towards usefullnes of 128 and 256 MB upgrades
Added lines 77-81:

Question on usefullnes of upgrades > 64 MB These DMA errors are reported to occur for upgrades to 128 and 256MB only. Please confirm or negate my following conclusions:

  • Doubling your memory to 64MB doesn't pose other problems than actually doing it, whilst quadrupling or octadrupling (is that valid English terminology?) to 128 or 256MB result in crashes when using 100% physical memory.
  • Those crashes can't be circumvented, hence if you want to remain a stable slug one shouldn't fatten it more than 64MB

-- Paul Brandt, April 29, 2008

January 10, 2008, at 07:29 PM by fcarolo -- fixed false wikilink
Changed line 80 from:

On Newegg.com they sell SODIMMS (for Laptops) I was able to find PC133 Modules that are 256MB - 4 chips, the configuration is listed on the manufacturers web site as 32M X 64bits, CAS 2 the model I found is Crucial 256MB 144-Pin SO-DIMM PC 133 Notebook Memory Model CT32M64S8W7E and is about $30US plus $5 shipping as of 12/2007. (**Caution, I received a module which has 8x MT48LC16M16A2BG?, which is a 256Mb part. --hjames)

to:

On Newegg.com they sell SODIMMS (for Laptops) I was able to find PC133 Modules that are 256MB - 4 chips, the configuration is listed on the manufacturers web site as 32M X 64bits, CAS 2 the model I found is Crucial 256MB 144-Pin SO-DIMM PC 133 Notebook Memory Model CT32M64S8W7E and is about $30US plus $5 shipping as of 12/2007. (**Caution, I received a module which has 8x MT48LC16M16A2BG, which is a 256Mb part. --hjames)

January 09, 2008, at 09:50 PM by hjames -- observation on CT32M64S8W7E SODIMM (256Mb parts)
Changed line 80 from:

On Newegg.com they sell SODIMMS (for Laptops) I was able to find PC133 Modules that are 256MB - 4 chips, the configuration is listed on the manufacturers web site as 32M X 64bits, CAS 2 the model I found is Crucial 256MB 144-Pin SO-DIMM PC 133 Notebook Memory Model CT32M64S8W7E and is about $30US plus $5 shipping as of 12/2007.

to:

On Newegg.com they sell SODIMMS (for Laptops) I was able to find PC133 Modules that are 256MB - 4 chips, the configuration is listed on the manufacturers web site as 32M X 64bits, CAS 2 the model I found is Crucial 256MB 144-Pin SO-DIMM PC 133 Notebook Memory Model CT32M64S8W7E and is about $30US plus $5 shipping as of 12/2007. (**Caution, I received a module which has 8x MT48LC16M16A2BG?, which is a 256Mb part. --hjames)

January 08, 2008, at 12:34 PM by fcarolo -- fixed false wikilinks
Changed line 80 from:

On Newegg.com they sell SODIMMS (for Laptops) I was able to find PC133? Modules that are 256MB - 4 chips, the configuration is listed on the manufacturers web site as 32M X 64bits, CAS 2 the model I found is Crucial 256MB 144-Pin SO-DIMM PC 133 Notebook Memory Model CT32M64S8W7E? and is about $30US plus $5 shipping as of 12/2007.

to:

On Newegg.com they sell SODIMMS (for Laptops) I was able to find PC133 Modules that are 256MB - 4 chips, the configuration is listed on the manufacturers web site as 32M X 64bits, CAS 2 the model I found is Crucial 256MB 144-Pin SO-DIMM PC 133 Notebook Memory Model CT32M64S8W7E and is about $30US plus $5 shipping as of 12/2007.

December 31, 2007, at 07:04 AM by Charles Santos -- added note about sources of 512Mbit chips
Added line 76:
December 31, 2007, at 07:04 AM by Charles Santos -- added note about sources of 512Mbit chips
Changed lines 75-79 from:

With 64 MB enabled ("mem=64MB@0x000000") no crashes with memtest

to:

With 64 MB enabled ("mem=64MB@0x000000") no crashes with memtest
Comments on chip sources for 512Mbit chips: - Charles Santos
On Newegg.com they sell SODIMMS (for Laptops) I was able to find PC133? Modules that are 256MB - 4 chips, the configuration is listed on the manufacturers web site as 32M X 64bits, CAS 2 the model I found is Crucial 256MB 144-Pin SO-DIMM PC 133 Notebook Memory Model CT32M64S8W7E? and is about $30US plus $5 shipping as of 12/2007.

November 19, 2007, at 04:34 PM by fcarolo -- formatting
Changed lines 28-29 from:

A good source of chips are PC133 SDRAM modules. 128 Mbit chips can be obtained from a 64 MB module with 4 chips or a 128 MB module with 8 chips; 256 Mbit chips from a 128 MB module with 4 chips or a 256 MB module with 8 chips; 512 Mbit chips from a 256 MB module with 4 chips (I don't know if this exists) or a 512 MB module with 8 chips. They are much cheaper than buying the chips individually (or free if you have some lying around).

to:

A good source of chips are PC133 SDRAM modules. 128 Mbit chips can be obtained from a 64 MB module with 4 chips or a 128 MB module with 8 chips; 256 Mbit chips from a 128 MB module with 4 chips or a 256 MB module with 8 chips; 512 Mbit chips from a 256 MB module with 4 chips (I don't know if this exists) or a 512 MB module with 8 chips. They are much cheaper than buying the chips individually (or free if you have some lying around).

Changed lines 32-33 from:

Comment from Joschi: I just bought a 256MB PC133? module consisting of 4 512Mbit 32Mx16 chips at www.fscomputer.de. Found this by googling for "32Mx16" AND "PC133?".

to:

Comment from Joschi: I just bought a 256MB PC133 module consisting of 4 512Mbit 32Mx16 chips at www.fscomputer.de. Found this by googling for "32Mx16" AND "PC133".

November 16, 2007, at 09:04 AM by caiacoa -- cosmetics too
Added line 69:

\\

Added line 74:

\\

November 16, 2007, at 09:02 AM by caiacoa -- Bug 7760 mentioned
Changed lines 66-73 from:

With changing the boot loader to Apex as 2nd stage boot loader, I was able to detect the memory correctly and use it with Debian, using the instructions here but it crashes due to DMA error when using up to the limit of memory (happens when using rsync).

to:

With changing the boot loader to Apex as 2nd stage boot loader, I was able to detect the memory correctly and use it with Debian, using the instructions here but it crashes due to DMA error when using up to the limit of memory (happens when using rsync).

Comments on a 128MB upgrade (2x512Mbit chips): --caiacoa The DMA errors mentioned above by Rob concerns the 128MB slug too. Please run memtest all (or 128mb) to confirm and report otherwise if its working for you. (crashes when using up to the limit of RAM) Problem is Bug 7760 "Page Allocation Failure on ixp4xx (nslu2) with 128MB RAM" See http://bugzilla.kernel.org/show_bug.cgi?id=7760 With 64 MB enabled ("mem=64MB@0x000000") no crashes with memtest

July 14, 2007, at 05:35 PM by Rob Lockhart -- cosmetics
Added line 65:

\\

July 14, 2007, at 05:34 PM by Rob Lockhart -- my FatSlug experiences
Changed lines 36-39 from:

The RAM chips can be desoldered with 1mm solder wick and a 30 watt iron (any more and you will potentially damage the board).

Once you have them desoldered you may need to pry them off the board as they may be glued.

to:

The RAM chips can be de-soldered with 1mm solder wick and a 30 watt iron (any more and you will potentially damage the board). I would recommend using flux as well; a flux pen works best. That serves to clean the oxidation off both the tip and the pins, and allows maximal heat flow to the pins.

Once you have them de-soldered you may need to pry them off the board as they may be glued.

Added lines 64-65:

Comments on a 256MB upgrade (4x512Mbit chips): --Rob Lockhart With changing the boot loader to Apex as 2nd stage boot loader, I was able to detect the memory correctly and use it with Debian, using the instructions here but it crashes due to DMA error when using up to the limit of memory (happens when using rsync).

April 10, 2007, at 05:59 AM by Rob Lockhart -- boldface warning
Changed lines 3-4 from:

*WARNING Doing this will DEFINITELY VOID YOUR WARRANTY.*

to:

*WARNING Doing this will DEFINITELY VOID YOUR WARRANTY.*

December 06, 2006, at 09:36 PM by chacko --
Changed lines 44-45 from:

Modifications to RedBoot and the Linux kernel are also necessary to enable the usage of the extra RAM. Without these modifications you will only be able to use 32MB.

to:

Modifications to RedBoot and the Linux kernel are also necessary to enable the usage of the extra RAM. Without these modifications you will only be able to use 32MB. See the details of the software side boot loader modifications

December 06, 2006, at 09:25 PM by chacko --
Changed lines 48-49 from:

Without changing the bootloader, I was able to access the lower 64MB by recompiling the kernel alone. I changed the memory parameter of the kernel command line to "mem=64MB@0x000000". I am not sure if this will also work on 64MB and 256MB upgrades.

to:

Without changing the bootloader, I was able to access the lower 64MB by recompiling the kernel alone. I changed the memory parameter of the kernel command line to "mem=64MB@0x000000". I am not sure if this will also work on 64MB and 256MB upgrades. [ ERROR? ... on 128MB and 256MB upgrades ?? ]

December 05, 2006, at 11:53 AM by Phil Endecott -- Add clarification for Chacko. If you still can\'t find them, they\'re the only pair of identical chips on the board :-)
Changed lines 13-14 from:

2 methods of fattening: replace the existing RAM with 2 equal sized but bigger RAM chips or add 2 RAM chips of the existing size "piggy backed" (or do both for maximum ram).

to:

2 methods of fattening: replace the two existing 8Mx16 RAM chips with 2 equal sized but bigger RAM chips or add 2 RAM chips of the existing size "piggy backed" (or do both for maximum ram).

Deleted lines 16-20:

Clarification How many chips are in the original board? Two? Are they 8Mx16? What is the exact part number used in the original? The photo does not show where they are for someone who does not know this particular ram.


Changed lines 36-40 from:

The RAM chips can be desoldered with 1mm solder wick and a 30 watt iron (any more and you will potentially damage the board)

Once you have them desoldered you need to pry them off the board (they are glued) Please observe that on some boards they are not glued.

to:

The RAM chips can be desoldered with 1mm solder wick and a 30 watt iron (any more and you will potentially damage the board).

Once you have them desoldered you may need to pry them off the board as they may be glued.

December 04, 2006, at 07:40 PM by Chacko --
Changed line 18 from:

Clarification How many chips are in the original board? The photo does not show where they are for someone who does not know this particular ram.

to:

Clarification How many chips are in the original board? Two? Are they 8Mx16? What is the exact part number used in the original? The photo does not show where they are for someone who does not know this particular ram.

December 04, 2006, at 07:37 PM by Chacko --
Changed line 18 from:
  • Clarification* How many chips are in the original board? The photo does not show where they are for the uninitiated.
to:

Clarification How many chips are in the original board? The photo does not show where they are for someone who does not know this particular ram.

December 04, 2006, at 07:34 PM by Chacko -- adding clarification question
Added lines 17-21:

  • Clarification* How many chips are in the original board? The photo does not show where they are for the uninitiated.

November 27, 2006, at 02:34 AM by JustRob -- changed APEX bootloader URL
Changed lines 51-52 from:

To access all the installed memory, you will need to change the bootloader and/or modify the kernel. I have used APEX bootloader and it works as expected.

to:

To access all the installed memory, you will need to change the bootloader and/or modify the kernel. I have used APEX bootloader and it works as expected.

November 20, 2006, at 07:15 PM by TPP -- Not all boards have glued chips.
Changed lines 39-40 from:
to:

Please observe that on some boards they are not glued.

August 14, 2006, at 04:04 PM by Micirio -- Comments on a 128MB upgrade (2x512Mbit chips):
Added line 55:

\\

August 14, 2006, at 04:03 PM by Micirio -- Comments on a 128MB upgrade (2x512Mbit chips)
Added lines 54-62:

Comments on a 128MB upgrade (2x512Mbit chips): --Micirio Without changing the bootloader:

  • I was not able to boot a kernel with commandline "mem=128MB@0x000000"
  • I was able to boot a kernel with commandline "mem=64MB@0x000000" - But every time I used more the 32MB, I got a kernel panic

After I changed the bootloader to APEX:

  • I was able to boot a kernel with commandline "mem=128MB@0x000000" - No problems, except the "Badness in dma_free_coherent at arch/arm/mm/consistent.c:351" kernel messages. But this seems to be a known problem of kernel 2.6.16
  • I was able to boot a kernel with commandline "mem=64MB@0x000000" - No problems, everything stable

Fazit: I could not use the 64MB without using APEX

August 12, 2006, at 01:26 AM by plugwash -- note that you can do both
Changed lines 13-14 from:

2 methods of fattening: replace the existing RAM with 2 equal sized but bigger RAM chips or add 2 RAM chips of the existing size "piggy backed".

to:

2 methods of fattening: replace the existing RAM with 2 equal sized but bigger RAM chips or add 2 RAM chips of the existing size "piggy backed" (or do both for maximum ram).

April 16, 2006, at 02:02 PM by kinsa -- additional info
Changed lines 30-31 from:

Note: Most 256 MB modules use 32Mx8 chips instead of 16Mx16. Double check the chips before you buy or install.

to:

Note: Most 256 MB modules use 32Mx8 chips instead of 16Mx16. Double check the chips before you buy or install. The safest option is to look for 128 MB modules with 4 chips.

April 16, 2006, at 10:21 AM by kinsa -- added info on 256MB modules
Added lines 30-31:

Note: Most 256 MB modules use 32Mx8 chips instead of 16Mx16. Double check the chips before you buy or install.

February 07, 2006, at 04:44 AM by kinsa --
Changed lines 44-45 from:

I have succesfully used the extra memory without modifying the Linux kernel by using APEX

 bootloader and openslug firmware-- kinsa?
to:

Comments on a 128MB upgrade (4x256Mbit chips): -- kinsa?

Without changing the bootloader, I was able to access the lower 64MB by recompiling the kernel alone. I changed the memory parameter of the kernel command line to "mem=64MB@0x000000". I am not sure if this will also work on 64MB and 256MB upgrades.

To access all the installed memory, you will need to change the bootloader and/or modify the kernel. I have used APEX bootloader and it works as expected.

If you are using Openslug, then changing the kernel command line ("mem=xxx") in APEX is all that is needed. The last time I checked, Unslung needs a kernel recompile because the command line parameters are hardcoded.

November 15, 2005, at 05:05 AM by joschi --
Added lines 30-31:

Comment from Joschi: I just bought a 256MB PC133? module consisting of 4 512Mbit 32Mx16 chips at www.fscomputer.de. Found this by googling for "32Mx16" AND "PC133?".

November 14, 2005, at 05:11 AM by joschi -- added Chip organisation info from intel developer manual
Changed lines 21-25 from:
memory128 Mbit256 Mbit512 Mbit
64 MB42-
128 MB-42
256 MB--4
to:
memory128 Mbit256 Mbit512 Mbit
64 MB4 Chips
8Mx16
2 Chips
16Mx16
-
128 MB-4 Chips
16Mx16
2 Chips
32Mx16
256 MB--4 Chips
32Mx16
August 16, 2005, at 05:38 AM by kinsa --
Changed line 43 from:
 bootloader -- kinsa?
to:
 bootloader and openslug firmware-- kinsa?
August 04, 2005, at 05:05 AM by kinsa -- added chip source and combinations
Changed lines 13-14 from:

2 methods of fattening: replace the existing RAM with 2 equal sized but bigger RAM chips or add 2 RAM chips of the existing size "piggy backed"

to:

2 methods of fattening: replace the existing RAM with 2 equal sized but bigger RAM chips or add 2 RAM chips of the existing size "piggy backed".

Added lines 17-29:

The following table shows the required number of chips for a given memory configuration:

TotalChip density
memory128 Mbit256 Mbit512 Mbit
64 MB42-
128 MB-42
256 MB--4

If you are using 4 chips then the /CS pin (pin 19) of the 2 "piggy backed" chips should be connected together to the unconnected pin on PR12.

A good source of chips are PC133 SDRAM modules. 128 Mbit chips can be obtained from a 64 MB module with 4 chips or a 128 MB module with 8 chips; 256 Mbit chips from a 128 MB module with 4 chips or a 256 MB module with 8 chips; 512 Mbit chips from a 256 MB module with 4 chips (I don't know if this exists) or a 512 MB module with 8 chips. They are much cheaper than buying the chips individually (or free if you have some lying around).

Added lines 38-39:

Photos are posted at the NSLU2-Linux Yahoo Group (http://groups.yahoo.com/group/nslu2-linux).

Added lines 41-43:

I have succesfully used the extra memory without modifying the Linux kernel by using APEX

 bootloader -- kinsa?
February 01, 2005, at 04:16 AM by rwhitby --
Deleted lines 6-9:

http://www.nslu2-linux.org/wiki/uploads/changes.txt

January 06, 2005, at 10:23 PM by ka6sox --
Added lines 7-10:

http://www.nslu2-linux.org/wiki/uploads/changes.txt

December 10, 2004, at 12:27 AM by tman --
Changed line 3 from:

*WARNING Doing this will DEFINATELY VOID YOUR WARRANTY.*

to:

*WARNING Doing this will DEFINITELY VOID YOUR WARRANTY.*

Changed line 5 from:

There you have been warned...

to:

There, you have been warned...

Changed line 7 from:

Ah..I see you are still here...

to:

Ah.. I see you are still here...

Changed line 13 from:

2 methods of fattening: replace the existing ram with 2 equal sized but bigger RAM chips or add 2 ramchips of the exisiting size "piggy backed"

to:

2 methods of fattening: replace the existing RAM with 2 equal sized but bigger RAM chips or add 2 RAM chips of the existing size "piggy backed"

Changed line 15 from:

ram chips for the slug are always in equal sized pairs.

to:

RAM used must be added in identical pairs and if two banks are being used, must also be the same for both banks. Obviously each chip must be at least 16MB.

Changed line 19 from:

the ram chips can be desoldered with 1mm Solder Wick and a 30watt iron (any more and you will potentially damage the board)

to:

The RAM chips can be desoldered with 1mm solder wick and a 30 watt iron (any more and you will potentially damage the board)

Changed line 21 from:

once you have them desoldered you need to pry them off the board (they are glued)

to:

Once you have them desoldered you need to pry them off the board (they are glued)

Changed lines 23-25 from:

if you don't want to save the existing ram you can cut the leads at the body and more easily unsolder the chip.

to:

If you don't want to save the existing RAM you can cut the leads at the body and more easily unsolder the chip.

Modifications to RedBoot and the Linux kernel are also necessary to enable the usage of the extra RAM. Without these modifications you will only be able to use 32MB.

December 06, 2004, at 01:01 AM by ka6sox --
Added lines 15-16:

ram chips for the slug are always in equal sized pairs.

December 06, 2004, at 01:00 AM by ka6sox --
Added lines 17-21:

the ram chips can be desoldered with 1mm Solder Wick and a 30watt iron (any more and you will potentially damage the board)

once you have them desoldered you need to pry them off the board (they are glued)

if you don't want to save the existing ram you can cut the leads at the body and more easily unsolder the chip.

December 05, 2004, at 11:36 PM by ka6sox --
Changed lines 9-16 from:

the first thing you have to do is open the case (preferably in a somewhat static free area)

to:

The first thing you have to do is open the case (preferably in a somewhat static free area)

Follow the directions to http://www.nslu2-linux.org/wiki/HowTo/OpenTheCase open the case.

2 methods of fattening: replace the existing ram with 2 equal sized but bigger RAM chips or add 2 ramchips of the exisiting size "piggy backed"

This job requires a steady hand and a very small soldering iron tip (<1mm)

December 05, 2004, at 11:31 PM by ka6sox --
Changed lines 1-9 from:

this page is in development

to:

Fattening your Slug is adding more RAM to the slug.

*WARNING Doing this will DEFINATELY VOID YOUR WARRANTY.*

There you have been warned...

Ah..I see you are still here...

the first thing you have to do is open the case (preferably in a somewhat static free area)

December 05, 2004, at 10:20 PM by ka6sox --
Changed line 1 from:

Describe FattenYourSlug here.

to:

this page is in development

Page last modified on June 27, 2008, at 12:04 PM