3.5G Memory limit on MSI K8N Athlon 64 Boards

From: General Schvantzkoph (schvantzkoph_at_yahoo.com)
Date: 07/30/05

  • Next message: kermit: "Re: 3.5G Memory limit on MSI K8N Athlon 64 Boards" 
    Date: Fri, 29 Jul 2005 22:24:35 -0400

    This morning I reported that the MSI K8N Neo4 Platinum can only recognize
    3.5G of memory. The MSI website says,

    Due to the South Bridge resource deployment, the system density will only
    be detected up to 3+ GB (not full 4GB) when each DIMM is installed with an
    1GB memory module

    I also have an MSI K8N Neo2 Platinum. I just tried putting 4G into the the
    Neo2 to see if it has the same defect, it does. So it appears that all MSI
    Nforce 3 and Nforce 4 boards are limited to 3.5G.

    Does anyone have a Athlon 64 motherboard that supports the full 4G?

  • Next message: kermit: "Re: 3.5G Memory limit on MSI K8N Athlon 64 Boards"

    Relevant Pages

    • Re: em(4)/82571eb: fifo not dmaed to host memory
      ... my hardware needs the memory access and bus master bits getting set by ... the interface init'ed without a problem and did not complain about MSI ... pcib9: em0 requested memory range 0xfd700000-0xfd7fffff: good ...
      (freebsd-net)
    • Re: PANIC: blockable slep lock (sx) msi @ ....msi.c:374
      ... This can be fixed switching the msi lock to be a spinlock instead than ... think it's OK for memory allocations to fail in this kind of code, ... system start breaking things instead of waiting when memory runs low. ...
      (freebsd-current)
    • Re: [PATCH] Revert sky2 to 0.13a
      ... Unless a fix for msi is at hand, may I suggest for 2.6.16 to revert the msi ... static void msi_set_mask_bit(unsigned int vector, ... a: read 64 bit from memory. ...
      (Linux-Kernel)
    • Re: MSI to memory?
      ... >>device write to memory instead of using MSI for interrupts? ... > location until the MSI write access changes the memory content... ... Who (another cpu??) writes to memory while your CPU is wasting its ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: MSI to memory?
      ... >> device write to memory instead of using MSI for interrupts? ... > location until the MSI write access changes the memory content... ... Another cpu in a smp system ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)