15 ms·
Adventures of putting 16 GB of RAM in a motherboard that doesn’t support it
- equalunique 8y agoMy HP N40L "MicroServer" only supports up to 8GB RAM, but I have it running now with 16GB. Sometimes FreeNAS will boot saying there is 16GB, and other times it will boot saying there is only 8GB. I'm unwilling to risk loosing that old reliable system via a potentially dangerous BIOS hack, but it sure would be nice not have to reboot it until I win the lucky 16GB jackpot.
- orev 8y agoI would be concerned that there’s some electrical reason why it’s detected intermittently, and that the extra 8GB could easily disappear while the system is running.
- segfaultbuserr 8y agoLow-level software is responsible for most memory issues, but there are definitely electrical reasons, too. For example, I have a devboard that only support 1 GiB of DDR2 RAM, but it's a 64-bit system and the memory controller on the CPU was supposed to support at least 2 GiB of RAM. Meanwhile, another board that uses the identical chip runs 2 GiB RAM without problems. The engineers of the devboard briefly explained that the problem was electrical. The memory controller itself has inadequate drive strength, adding more RAMs would increase the load on the DDR bus and destabilize the system. On the other hand, the other board had better PCB layout so the problem did not occur.
- equalunique 8y agoI would sure like to find an inexpensive Mini-ITX motherboard in 2019 that could run my 2x8GB sticks of 204-pin DDR3 ECC UDIMMs properly.
- remlov 8y agoHoly smokes. I thought finding an ITX board for 2x8GB sticks of full size 240-pin DDR3 ECC UDIMMs was hard.
- segfaultbuserr 8y agoI have a Mini-ITX board, I noticed that if I activate XMP, the board will cease to work, but it works with 4 GiB of RAM at standard frequency. So it seems memory is a general problem among Mini-ITX boards? Perhaps the reason is that these boards have less available space for routing, fewer layers, and targets a lower price, so they trend to have worse electrical characteristics?
- remlov 8y agoQuality of the PCB and the number of layers definitely plays a factor I'm sure it isn't limited to ITX though. I have noticed compatible differences between super robust Intel ITX boards vs ECS thin and wobbly ITX boards, with the ECS board having more issues, quirks and what not.
- spockz 8y agoI had something similar with my 2011 MBP. I had it running just fine with 16GB of ram even though it officially only supported 8GB. After having the main board replaced because of a defective graphics card I could not run it with more than 8GB without it crashing continuously.
- bluedino 8y agoShould work fine. I wonder if you needed a firmware update?
- mikeash 8y agoI once had a defective 512MB RAM module. Usually it would be detected as a 256MB module and it would work fine. Sometimes it would be detected as a 512MB module, but corrupted data would crash the system within a few minutes.
- jacob019 8y agoYou used to be able to scan memory consistency and pass a kernel parameter to skip bad regions of memory. I ran a system for years with known bad memory that way.
- userbinator 8y ago...and it probably already has, multiple times, but you haven't noticed because you've not used that much RAM. The BIOS does a (relatively) quick memory check in the POST to detect how much memory is actually available, basically by writing a series of patterns to all addresses and then reading them back to confirm; some desktops have a "fast boot" option which mostly skips it (I believe it's something like testing one byte per 4KB instead of every byte), and servers usually have a much more thorough test that can take many minutes. The best way to check whether the memory is functional when 16GB is detected is to run a memory tester like MemTest86.
- fyfy18 8y agoSame here on a N54L. Officially these machines only accept 8GB, but plenty of people say they run fine with 16GB.
- kalleboo 8y agoI've done the same thing with a Synology NAS. Both Synology and the Intel CPU datasheet say it only supports 8 GB of RAM, but put 16 GB in it and it will use it. The Synology web UI only shows 8 GB and it breaks the graph display in the memory usage monitor (although when I first installed it, it used to show 16 GB but after some update, or random reboot, it stopped. Haven't tried rebooting to see if it's just random)
- kstenerud 8y agoAre you sure about that? I bought mine with 16gb a number of years ago and still use it as a NAS + plex server (zfs loves to chew through ram). The wikia page also talks about it: https://n40l.fandom.com/wiki/Memory https://n40l.fandom.com/wiki/Memory
- Spare_account 8y agoThe "supports 16Gb" assertion on the page you've linked to is sourced from another forum page: https://hardforum.com/threads/hp-proliant-microserver-owners-thread.1555868/page-17#post-1038749416 https://hardforum.com/threads/hp-proliant-microserver-owners... > It seems to be confirmed, that these wonderfull little boxen can actually support 16Gb Memory, not the 8Gb HP Says they are limited to. So it would appear that HP doesn't officially support 16Gb, which puts us firmly back in the territory of this post, YMMV, etc.
- gyrgtyn 8y agoI got two from the same guy on craiglist and they already had 16GB and it works everytime. Not sure what he did but I'm glad I wasn't the one fiddling with the BIOS
- ownagefool 8y agoI ran the hacked bios and it worked, for what that's worth. This was when they were fairly new.
- TMWNN 8y agoAs kstenerud said, https://n40l.fandom.com/wiki/Memory https://n40l.fandom.com/wiki/Memory discusses this issue. More accurately, the comments discuss it, with some reporting your issue. I am among those who've never had problems with detecting 16GB; I use two KVR1333D3E9S/8G.
- qwerty456127 8y agoIn good old days of i440BX it usually took just a BIOS update (and some socket rewiring for the latest CPUs) to add support for extra RAM and CPUs...
- frabert 8y agoThat's what it would take in this case as well, it's just that the manufacturer doesn't provide any.
- qwerty456127 8y agoSure. I've commented before I've read the article. Now I see. In fact the BIOSes I've ended up using during the last years of my BX PC (before I've bought a laptop) were community-patched. Now I wonder if it is possible to patch my Dell E5500 to support more than 4 GiBs or if it's actually an unbreakable limitation of its chipset...
- nisa 8y ago8gb should work fine. 16gb probably not.
- dmarlow 8y agoI love articles like these. It's an amazing skill to be able to do what was done here.
- jchw 8y agoLove this. I've got an old Pentium box I thought I was going to have to hack up the BIOS to get larger IDE disks working, but don't you know it the motherboard manufacturer (AOpen) still had the BIOS update files on their site and after updating I could boot 32 GB disks on a board that only claims to support up to 8 GB. I think the lesson is, at least check for BIOS updates before you throw in the towel :) Maybe not everyone needs to go as far as hacking ACPI tables in memory, but it sure sounds like fun.
- anyfoo 8y agoIn that era, you could often just ensure that the BIOS could load the bootloader/kernel by placing it into the region still reachable by the BIOS. OSes like Linux (and anything Windows NT based) practically completely disabled[1] the BIOS anyway, and their own IDE drivers would be recent enough to understand how to address the full disk. It was not uncommon to have a small boot partition at the beginning of the disk for that purpose. [1] Bit of a simplification. In reality, the BIOS being 16bit real mode code meant that you had to jump through very elaborate hoops if you wanted to use it in your protected mode OS in any way, and then for questionable gain.
- jchw 8y agoOh yeah, definitely. I could get it to boot by marking the disk as 8 GB in BIOS, but this had side effects: - I'm using CompactFlash as many do, since it's fast, cheap, and reliable. Some of my CF cards are smaller than 8 GB, and if I hard code it I can't boot with those. - I actually do run OSes on that machine that thunk out to BIOS (Win98 for example.) If I really wanted a computer for useful things, no doubt I'd run Linux on it, but all the same, I've got plenty of smaller computers with unilaterally more power (even a RPi is much faster.) (FWIW: autodetect properly detected the right parameters, it just locked up on boot. My guess is it was some kind of simple integer overflow bug or something.)
- nisa 8y ago> It was not uncommon to have a small boot partition at the beginning of the disk for that purpose. still had to that a few weeks ago because on a dell r720 grub did not want to boot my zfsonlinux rootfs on a 6tb pool - it's either the dell hba controller, grub oder some other limitation but once you go beyond 2tb or 4tb disk I always run into strange behavoir. Maybe UEFI solves that, I don't know.
- zelon88 8y agoNice find! Reminds me of the Dell Vostro 230. It will "officially" support 8GB memory but if you buy 8gb "low density" DIMMs it will accept 16GB just fine. Not nearly as difficult as your setup but similar in nature.
- maaarghk 8y agoI had a similar adventure on the Vostro 230, followed by editing the BIOS to activate the vmx flag so that I could do hardware virtualisation with the Xeon processor that it shipped with!
- randyrand 8y agoI wonder if microsoft would be interested in copying the linux approach. bug report?
- LeonM 8y agoI don't think it's a bug, it's a feature (no pun intended). If there is problem with reported values from a BIOS, it's a good thing Windows does not continue. BIOS issues (such as a RAM address out of the reported range) can lead to unpredictable behaviour. Troubleshooting such issues is next to impossible.
- PaulHoule 8y agoIt's a long term difference between the Unix culture and the Windows NT culture (which date back to VMS) that Windows will give up when things are wrong and Unix will barrel ahead anyway.
- bogomipz 8y agoI'm curious what's the connection between VMS and Windows NT?
- bitwize 8y agoDave Cutler.
- Johnny555 8y agoI'm curious what's the connection between VMS and Windows NT? https://www.itprotoday.com/compute-engines/windows-nt-and-vms-rest-story https://www.itprotoday.com/compute-engines/windows-nt-and-vm...
- lasereyes136 8y agoRead Showstopper it is about the making of Windows NT. It talks about the people that moved for Microsoft from DEC. https://www.amazon.com/Showstopper-Breakneck-Windows-Generation-Microsoft-ebook/dp/B00J5X5E9U/ref=sr_1_fkmrnull_1?keywords=show+stopper+windows+nt&qid=1554405463&s=gateway&sr=8-1-fkmrnull https://www.amazon.com/Showstopper-Breakneck-Windows-Generat...
- Anarch157a 8y agoThe creator of the NT kernel (Dave CUtler) also created VMS while working at DEC. Because of this, NT have a lot in common with VMS.
- bogomipz 8y agoInteresting I never knew this. The links above all look like good reads. Cheers.
- _bxg1 8y agoJust reading this gave me a headache
- _bxg1 8y agoReally? Five downvotes for an innocently tongue-in-cheek comment?
- Dylan16807 8y agoWere you making a joke, or just fake-complaining? Five is not a lot either.
- _bxg1 8y agoMaking a joke about how miserable it is for some of us to deep-dive into systems to get stuff working. I wasn't expecting any upvotes, but it was neither a rude nor an idiotic thing to say, so y'all need to chill.
- zaroth 8y agoIt wasn’t clear you were sympathizing and not actually complaining. For a second I thought you might say the contrast was too low, and which CSS style you had to adjust.
- uranium 8y agoMan, this gave me flashbacks to trying to put 3.5-4GB of RAM into motherboards in 2003. After a bunch of iterations of telling the motherboard manufacturers what we wanted, and having them hack the BIOS to work for exactly one DIMM configuration, then fail on anything else, I eventually gave up expecting most of the BIOS to work at all. I added code to the Linux startup sequence that ignored everything the BIOS said about memory maps, queried what physical DIMMS were there, and rebuilt my maps by hand. It's been so long that I can't tell an e820 map from an MTRR, but this was still a fun read.
- JoshTriplett 8y ago> I added code to the Linux startup sequence that ignored everything the BIOS said about memory maps, queried what physical DIMMS were there, and rebuilt my maps by hand. I'd love to see this code; doing memory management entirely in the OS and ignoring the BIOS sounds like fun (modulo working around BIOS-specific memory reservations so the OS doesn't get its memory stomped on by the BIOS).
- ianai 8y agoPost-UEFI I wish this were more of a viable option.
- josephg 8y agoI agree. I spent some time last year running various scripts to get an NVIDIA GPU working over thunderbolt in windows on a macbook pro. The problem is the DSDT table in many macbooks doesn't allocate enough space for pci-e devices. The NVIDIA driver in windows tries to allocate memory via that table to talk to the eGPU and it fails. For some reason it works fine under MacOS - either macos ignores the DSDT table completely, or it allocates memory a bit differently than windows. In any case, the answer is to use obscure tools to download and patch the DSDT tables to allocate more RAM toward PCI-e. Doing this through UEFI feels very magic. I don't know why so much of this stuff is up to the hardware vendor. Maybe there's a good reason, but I would expect the windows memory manager could do a much better job if it didn't have a bunch of memory range sizes hardcoded by apple.
- d33 8y agoI think I would also run the memtest under the VM to make sure that the memory map is actually all reachable within Linux and doesn't mess anything up.
- Etheryte 8y agoAs far as I can tell, the author did run tests on the memory after finishing: > All I know is it passes my RAM tests.
- d33 8y agoI don't know much about kernel memory management, but if he was booting memtest86+ bare metal, I wouldn't be surprised if he wasn't triggering the same edge cases Linux would do - which is why I'd prefer to make the actual system try to allocate as much memory as possible, use it and see if the results are sane.
- drudru11 8y agoSimple - just run Chrome. It will consume memory like no tomorrow.
- dougg3 8y agoI'm the author of the blog post. My first time here on Hacker News...very cool that it was picked up! I did my memory testing inside of Linux using memtester. I honestly want to do more thorough testing at some point to prove that it's actually working okay. If some of the PCI hardware is still paying attention to that overlapped range, weird stuff could definitely happen.
- balls187 8y agoI love this stuff. I remember custom flashing a motherboard to support a pair of SSD's in RAID-0, and allow it as a boot device.
- madrox 8y agoI remember being 14 years old playing with my NEC PC because IRQ conflicts caused it to reboot at unexpected times. My dad might have fixed it, but he didn't have time so I had to rely on myself if I wanted to play Warcraft ever again. I didn't really know what I was doing, but it was the first time I took something apart trying to figure it out. I explored BIOS and all the hidden parts that Windows tries to hide from casual users. Looking back, that's really where my perseverance in working through hard problems began. I was expecting this to be "Linux roolz, Microsoft droolz," but I really enjoyed this. It's been a while since such simple, fun hardware exploration came across my desk.
- VectorLock 8y agoNow thats the kind of deep dive you don't see very often in the rarified cloud computing world I live in now.
- glvn 8y agoBack in 2012 I had a white MacBook. Apple said it only officially supported 4GB butt there were numerous reports of people getting it to recognize 8GB without issue. Back then I was still in high school and only semi-technical so I thought it was some sort of black magic.
- bluedino 8y agoThe white polycarbonate MacBooks only supported 8GB according to Apple, but 16GB worked fine. Same thing with the 2010+ 13" Unibody MacBooks
- unpixer 8y agoGather 'round, young 'uns: the 1998-vintage Powerbook G3 "PDQ" officially supported only 192 MB of RAM. Unofficially it was possible, if you bought the right DIMMs, to upgrade it to 512 MB. Which I did, just for laughs. (It was also possible, using XPostFacto, to upgrade it past the official OS X 10.2.8. maximum to 10.4.11. But it was so slow it was practically unusable.)
- dev_dull 8y agoI love this line: > All I know is it passes my RAM tests. Since Linux has been working fine with the 16 gigs of RAM installed, I am not too worried. It’s possible I would have problems if I had more PCI/PCIe cards installed or something, but in my use case, it seems to behave fine. Obviously, your mileage may vary I run into this so often. "Look, it works for me. Don't try it at home. Who knows if it keeps working? What can I say I'm going to ride it until the wheels fall off".
- zaroth 8y ago“Just whatever you do, don’t reboot the server.” Said on the last day to the new hire.
- ivanhoe 8y agoWell, it's not like you're in any real danger for trying it, if your system becomes unstable you just take out that extra ram. It's exactly the same as overclocking, your box might not work as stable as before, but you get the extra speed, so thousands of people do it...
- bluedino 8y agoI wonder what the Mac equivalant 'fix' would be? The 2010 15" MacBook Pros only supported 8GB, where the 13" models supported 16GB. They used this same i5 chip.
- satmandu 8y agoSeriously. I tried putting the 16Gb of ram into the 2010 15" mbp, and it would boot into linux, but not macos. Running memtest it was clear that there were issues with accessing ram in various segments, but I didn't have the knowledge to muck around with the acpi tables to see if that would fix it. I'd love to give it another shot if possible.
- somacert 8y agoAs far as I can tell there are three acpi stacks/interpreters Intel, This is the reference, most operating systems use this (linux, freebsd, macos) Microsoft Openbsd, yes the openbsd project is crazy enough to build their own acpi implementation, keep fighting the good fight openbsd. Because have you seen the spec? good lord what a train wreak.
- dclowd9901 8y agoIf I were trying to explain to someone who knew computers but not cars why I would never buy a car with an engine swap, this is exactly the post I would point them to.
- xaduha 8y agoSince it's kind of related to something a wondered about - can you spoof a device ID with those tools? So an operating system just eats it up? I know it's possible with VMs and device passthrough.
- alchemism 8y agoMy Dad bought us an IBM PCjr with 256KB of RAM, which was kind of elite in 1984. But he wanted more. So, he purchased a pair of thick memory expansion board that brought it up to an unheard-of 640KB of RAM. Of course, these slabs generated an impressive amount of heat, so we had to set up a series of cooling fans, or else computations would go awry and weird bugs would appear in programs as it overheated. It had all manner of strange behaviors, and IBM engineers on the support contract would dutifully visit and give us stacks of floppies containing custom builds of MS-DOS to try and help us out when he called about problems with his mods. Today, incidentally, I’m a sysadmin.
- pvg 8y agoThe base PC AT shipped with 256k of RAM in 1984, the Fat Mac with 512KB. I think the elite thing here is not the amount of memory but buying a PC jr and then really committing to trying to upgrade it.
- benj111 8y agoSo was the memory expansion official? I would guess not? But then IBM were supporting it??? OT. I now have visions of young engineers joining IBM with dreams of working on big iron, but ending up in the burbs fixing PC jrs.
- quotemstr 8y agoWith respect to booting with a conflict in the system memory map: the Windows behavior is the right one, IMHO. An operating system shouldn't just ignore self-contradictory system configuration information and try to continue anyway. Who's to say that the resulting behavior is the right one? You're in undefined behavior territory. Failing fast when encountering invalid state, as Windows does, leads to more robustness in the end: fail-fast gets problems fixed, not swept under the rug.
- wtallis 8y agoFail-fast only has a hope of getting the problem fixed if it occurs with popular software within a few months of product launch. In the case of using a motherboard with DIMMs that didn't exist until the MB was obsolete, you're never going to get the vendor to fix it, unless you have a very expensive long-term supply and support contract of the sort that doesn't exist for consumer parts.
- EB66 8y agoWow, I didn't know this was possible... My every day workstation is a Dell Studio 540 from 2009 that I've upgraded to the max in every possible way but without changing the motherboard and case. The only upgrade I haven't pursued (because I thought it was impossible) is bumping up the RAM beyond 8GB. If anyone has experience bumping 2009 era Dell motherboards (in particular the M017G motherboard) beyond 8GB RAM and has any tips to offer, please let me know! If I could bump up the RAM to 16GB, I might be able to keep using my beloved desktop for another 10 years :)
- justinclift 8y agoAs a first step, check your CPU model on ark.intel.com (if it's an Intel): https://ark.intel.com https://ark.intel.com In theory (!) for older generation chips like yours and the one in the article, the maximum listed there (if present) will be correct. For example, for the i5-750 listed in the article it shows 16GB maximum, which the article author was then able to make work: https://ark.intel.com/content/www/us/en/ark/products/42915/intel-core-i5-750-processor-8m-cache-2-66-ghz.html https://ark.intel.com/content/www/us/en/ark/products/42915/i... If yours shows 16GB as well, you may be in luck. :)
- nisa 8y agolooks like it's a Intel G45 chipset - so 16gb should work, however you need to be careful when selecting memory - there might be max size on the chips on memory module (so there are memory modules with 8gb with 8x1gb chips or some with 2x2gb etc.pp. - we had some trouble updating older dells with the newer modules with less chips. It's called low density I think.
- EB66 8y agoI just thought I'd provide a follow-up on this in case someone else with a Dell Studio 540 or Intel G45 chipset tries to upgrade to 16GB memory. It works! I ordered 4 x 4GB 2Rx8 PC2-6400U DDR2-800Mhz 240PIN UDIMM from a business on eBay called Memory Masters and it worked perfectly. No hackery required. My desktop from 2009 now runs with 16GB RAM and will be hopefully be in use for another 10 years :)
- smartmic 8y agoA true hacker. And a wonderful read. Reminds me that the ability to really understand and control your system is one of the biggest achievements and power of Linux and FOSS.
- Florin_Andrei 8y ago> don’t know if the motherboard is actually hardwired to look at those addresses for PCI stuff or what. All I know is it passes my RAM tests. I guess you could allocate a humongous matrix with random cell values and do a CRC or something (once while you're filling it in, and again from square 1) to make sure the values are indeed what you think they are.
- CharlesColeman 8y ago> In order for the document to help me, I clearly needed to find the four error parameters that used to be displayed with the blue screen on older versions of Windows. Windows 10 hides all the information by default, but I discovered that it’s possible to re-enable display of the extra error information by adding an entry to your registry. I hate stuff like this. What's the point of hiding the parameters, instead of tucking them away in the corner of the screen or something? It just makes things needlessly difficult. I know the answer is going to be "but it makes the UI look beautiful and most users don't know what the parameters mean anyway!" Error UIs don't need to be beautiful, they need to be functional. Definitely have a nice, clear user-friendly error message, but keep the overall screen technically informative. I can imagine that the only thing more infuriating than having a computer that won't boot, is having one that won't tell you the problem unless you change registry settings (which you can't, because it can't boot). Leaving the extra information there does not harm, and it give people something to Google if they do run into a problem.
- spuz 8y agoYes. What I can't understand is why this extra diagnostic information is not available with a keyboard shortcut, rather than with a change to the registry. If you get a blue screen on boot, you typically have no way to alter the registry. Holding shift or something would make much more sense.
- tombert 8y agoAbout six years ago I updated a laptop to 16gb of RAM that only officially supported 8gb, and I remember thinking "the greedy manufacturers lied! It works fine!" However, I was running Linux, and now upon reading this I wonder if I would have had the same issues if I had tried booting into Windows.
- Tsiklon 8y agoMy old 2011 MacBook supports only 8GB officially - though the Intel chipset onboard will support 16GB - It's run happily with 16GB of RAM since 2012...
- tombert 8y agoOh yeah, I actually might have had that same model of MacBook, and I also think I put 16gb in there with an SSD; gave it to my brother in law. Amazing how well those things can hold up long term.
- aidos 8y agoThey released a firmware update at one point and it started working with more RAM. I almost jumped for joy at the time.
- saagarjha 8y ago> I clearly needed to find the four error parameters that used to be displayed with the blue screen on older versions of Windows. Windows 10 hides all the information by default A somewhat disappointing trend in user interface design…
- jadar 8y agoI remember messing with ACPI and DSDT when I was into the hackintosh scene. Good times.
- anonlapwarmer 8y agoThe workhorse oldie-but-goodie A1278 MBP mid-2012 non-Retina supports 16 GiB and two SSD's (one in the optical bay, and one in the HDD bay). The Lenovo T480 supports 64 GiB. A 13" hackintosh-friendly laptop with: - dual m.2 slots - WQHD 2560 x 1440 - Thunderbolt 3 - water-resistant keyboard with drains - 9 hours of battery life with the second, extended battery - officially user-serviceable parts/guides - & 64 GB! The iPhone 6S, even with the headphone jack, is IP67 in all but name but didn't sell it as a feature... it has all the gaskets of the 7 but supposedly the headphone jack was an issue... mine's been in the shower a few times for YouTube morning news and still works. You can make any data & charging connector USB-C magnetic & right-angle for $30. https://www.aliexpress.com/item/USB-C-L-Tip-Magnetic-Adapter-5A-87W-Type-C-PD-Dongle-Converter-for-MacBook/32920845652.html?spm=a2g0s.9042311.0.0.27424c4drJr85M https://www.aliexpress.com/item/USB-C-L-Tip-Magnetic-Adapter...
- drudru11 8y agoThx for the tip on the Lenovo. I have been on the lookout for a Linux laptop.
- anonlapwarmer 8y agoVideos from Louis Rossmann convinced me modern MBPs are beyond awful: https://www.youtube.com/user/rossmanngroup https://www.youtube.com/user/rossmanngroup macOS and most apps have nice UX and mostly work well together. Docker usually works on top of the built-in macOS intel-origin hypervisor. (VMware Fusion is another $olid option for $$; had problems with VirtualBox.) What's neat about the T480 is there's an utility on the Windows partition to flash the BIOS startup boot logo from red "Lenovo" to whatever you want.
- drudru11 8y agoIt would be nice if Linux would avoid using any of the BIOS. I wonder if that is possible.
- encore2097 8y agoThis is how hackintoshs boot! Love the independent discovery of ACPI hacking :)
- userbinator 8y agoOne of the things you'll quickly learn from working in IT (and probably other fields) is that "not supported" can mean anything from "physically impossible" to "we don't want you to". In the case of RAM, "physically impossible" would mean something like the CPU not having that many address bits or the PCB traces not routed, but there are a lot of different not-well-advertised configurations of DIMMs available with the same size[1], so it could be that the manufacturer specified a lower maximum just to avoid having to answer subtle questions. For example, 2x8GB may be OK but 1x16GB not. It could also be a "X if Y except Z else B" situation, and they just couldn't be bothered to document all the possible combinations and/or explain the details of the PC system architecture that result in such limitations. To test if all the memory is present (and if it all works correctly), running something like MemTest86 might be sufficient. [1] https://en.wikipedia.org/wiki/Memory_geometry https://en.wikipedia.org/wiki/Memory_geometry
- anonoholic 8y ago> "not supported" can mean anything from "physically impossible" to "we don't want you to" More like: from "physically impossible" to "we haven't tested that" > they just couldn't be bothered to document all the possible combinations Each combination adds exponential testing and documentation requirements. Not tested != doesn't work. But that doesn't make not supporting it malicious. There are practical and financial cost to testing every combination, ultimately born by the consumer.
- HeWhoLurksLate 8y agoMy favorite is when they say "not supported" and it's easy to make it work and is just their way of scaring Enterprise customers to their bread & butter. (One example that comes to mind is a bunch of Rigol oscilloscopes that, even though they have FPGA's on them, can still have more functionality enabled with resistors.)
- SmellyGeekBoy 8y agoAs an owner of a lower-end Rigol oscilloscope, this is very interesting to me...
- ameyv 8y agoBrilliant work! I know this feeling very well..God if i can this everyday at work it would be just amazing...
- comprev 8y agoMy MacBook Pro 13 mid-2010 "officially" only supports 8GB RAM maximum - but I run 16GB - thanks to the research by other folks on the internet related to the Intel hardware inside. The particular brand & model of sticks had to be fairly specific, but can confirm it's been rock solid for 3 years and certainly extended it's useful life for me when money was tight.
- Nr7 8y agoI have a kind of opposite problem on an old Lenovo laptop where Windows boots just fine every time but any Linux distro I try randomly fails to boot with an ACPI error. It's not a RAM issue though. AFAIK there's some bug in the UEFI/BIOS even on the latest version which Windows handles just fine but Linux randomly doesn't. I can boot Linux every time if I disable ACPI at boot but then I lose power management and battery percentage. Latest kernels (can't remember the version exactly, 4.somethingoranother) should handle the issue according to some forum posts I found but it doesn't for me.
- gpvos 8y agoWhat would happen if he removed the second 8GB but forgot to remove the GRUB ACPI table patch?