@darth vader

I think you have got reason when you say that it's not depend from kernel but it's a limitation of the motherboard, but Asus it was not clear it writes in the summary that the mobo supports until 2gb but at page 12 it says
in my language, may it means maybe, but overall if you cannot support 4gb why you put in the bios the option

Dram over 4g remapping...

Anyway it happen something strange in just one time I reboot and Linux read 4 GB...

Hello andros976

I have an Asus A8NE with an FX-57 CPU and 4 x 1 GB DIMM that is now demoted to a secondary machine but has commonly run 64bit MultiLib Slackware. I did for a time also run an earlier 32 bit version w/ PAE enabled custom kernel which also ran just fine, but since you're asking about 64 bit I will address only that. I think your issue may possibly be that you are not using an SMP kernel. Even though you have as I do on that mobo just one core, SMP code fixes a few issues IIRC. In any case just this minute I fired up the ol' Asus A8NE and it has no problems recognizing and using all 4GB or RAM and the main difference other than passing memtest perfectly with zero problems with no added boot options other than that my kernel is SMP.

FWIW it is also a custom low-latency tickless kernel but I had no problems installing from the Slackware Install DVD with the default kernel so I'm thinking you may have either a corroded Ram/Slot connection that needs cleaning (just removing and re-inserting a few times should clean it but I like a little Cramolin type contact cleaner added) or a bad stick or possibly just not the best quality RAM. My RAM FWIW is a matched set of extreme low-latency, but now defunct, OCZ Titanium DDR3-1600.


That said.... The Biggy....
FWIW also I have both S/W and H/W DRAM over 4GB remapping enabled in BIOS even though I have exactly 4GB because that was recommended by ASUS when using any 64bit system, and IIRC back then this especially applied to Windows XP-64 which had limitations imposed on memory addressing due to licensing issues. Since there seems to be no penalty for those 2 settings, why not? It was, after all, the early days of 64bit.

1 members found this post helpful.

@enorbet

I really want to thank you for your answer, but my system still doesnt work .

I have a CPU Athlon 64 bit with one core (like yours), but i've made how you said :

i compiled a kernel SMP enabling in make menuconfig the voice

Processor type and features -> Symmetric multi-processoring support,

Is just this the option to make a kernel SMP , isnt it?

However i enable in BIOS the two voices S/W and H/W DRAM over 4GB,

then BIOS read and makes active 4GB of ram,

but my kernel after loaded itself and says "BIOS data successfull" doesnt start...

Maybe i wrong something ? To make a kernel SMP it's just necessary this option

Processor type and features -> Symmetric multi-processoring support

I dont think that one slot or a module is fault, cause BIOS can read all 4 GB,

the problem is that when i activate the option H/W DRAM over 4GB to let BIOS read and activate all ram,

my kernels dont start, so i have to enable S/W DRAM over 4GB that makes BIOS to read all 4 GB but makes

available for S.O. just 3 GB. I think problem is my motherboard really "ASUS shit" cause you cannot write

in the manual in the summary that support just 2 GB and in another point of manual write that you can istall

4 GB , even if sometimes, you could not read all of them. computer technology is a science not philosophy !!!


@enorbet
let me know if i wronged something i prefer it's my fault and not of my mobo ;-)


Thanks

Greetings again andros976
First, yes enabling symmetric processing is SMP, but it is helpful to explain what fails. Does your kernel not even attempt to start? Do you get any bootloader error messages? Does the kernel panic and where?

Regarding RAM - what total the BIOS recognizes is only the first, very basic step. There is a BIOS option for checking RAM and the option is to choose a fast, cursory test or a repeated deeper test. That's Step 2. Then there is Step 3, Memtest, which you said fails. That can only be a bad connection in the slot or a bad stick and should be the first concern. Any system that cannot pass Memtest has a severe problem. You could try installing just 2GB in 2 slots and rotate the sticks and running Memtest to see if it is a stick or a slot that fails. Do pay attention to the manual's section on which slots are recommended for using just two.

I forget what sets it but I recall that during initial POST the BIOS reports Dual Channel and 128bit only if it is set properly. I know it's a pita but after writing down your BIOS settings you could try Reset to defaults to see if you have a setting that is a problem but I would do the RAM test first since it is very likely that one stick or one slot is faulty.

1 members found this post helpful.

Greetings enorbet
thanks for your patience...

well i answer to your questions

With this compiled kernel, the behavior is the same of another not SMP: kernel load , write BIOS data successful and then not continue
black screen.

THERE isnt in my BIOS option to check RAM deeper. I tried memory 2GB in two slot and rotation and memtest doesnt fail.
In reality memtest never fail, just when i enable one option that permit me to use all 4GB , memtest starts and after 4 sec PC reboots.

i show you some screenshots, they demonstrate that ram is good configured infact it recognise always dual channel 128 bit...

Attached Thumbnails

         

Want a tip from a hardware junkie?

Time for a new MoBo, and try to avoid ASUS.

@andros976

BTW, your BIOS is on version 0203, while the latest one is 0502 ...

https://www.asus.com/support/CPU/1/2...0060623113952/

NOT that I encourage you to mess with the BIOS, but updating it sometimes fix hardware issues like you have. But you can study about FLASHROM, with it you can do it from Linux.

BE WARNED that you can destroy your motherboard if you make an error in updating the BIOS.

------------------------------------------------------------
In other hand, looks like you have the memories in dual channel. Then you should have four memories which are identical and very careful paired.

Specially when you do a dual channel on four slots that's very important. Specially on those those old motherboards.

Anyways, IF those memories are not paired, the system will NOT work stable.

I strongly suggest you to disable the dual channel, if you bought the memories in different times, from different lots, etc.

1 members found this post helpful.

Heya andros976
The BIOS option to check RAM in a more thorough manner is on the BOOT tab and called "Quick Boot". By default it is enabled to speed up checks. A "Disable" setting will cause POST checks to increase and take considerably more time to handoff the boot process.

So do I understand correctly that you removed 2 sticks, ran Memtest on 2 of them (lets call them "A" and "B", passed, then swapped one of those 2 sticks out for one not tested so instead of "AB" you tested with "AC" and so on until each combination was tested? BUT it fails when all 4 are in place? That would suggest to me that a slot may be bad or that the RAM doesn't qualify for ASUS standards. I'm referring to this section in your manual

....and yes I would definitely recommend a BIOS update unless you've never done that before. If you follow ASUS's instructions and don't get impatient their recommended utility works a treat. I've updated mine several times. Just take your time and be thorough with the exception of if you have a non-matching set of RAM sticks. In that case the hardware is the problem and possibly not the BIOS version. Obviously if you are considering a new MOBO then it's a great opportunity to learn BIOS firmware update procedure but the choice is yours.

FWIW mine is a matching Quad set, all bought as a set at the same time, from same vendor..

EDIT: After seeing Darth's post I decided to add that he is correct.... !!effectively correct!!, but not perfectly accurate. Although people call it "Bricking" when a BIOS update fails, that doesn't mean it is in fact rendered as a brick never to boot ever again... in most cases anyway. Most mobos have replaceable CMOS chips AND an un-eraseable BOOT BLOCK or at least one unaffected by flashing. One of those methods can fix a "bricked" mobo but it is, I admit, a bit of a pita... but doable... not exactly "destroyed"

1 members found this post helpful.

Breaking News!

I managed to find the precise manual of that poor A8N-SLI SE motherboard:

http://ftp.tekwind.co.jp/pub/asustw/...A8N-SLI_SE.pdf

Also, that site contains the BIOS-es, up to:

http://ftp.tekwind.co.jp/pub/asustw/...E/A8NSE502.zip

Finally, reading the manual, looks like the motherboard has an emergency system for BIOS crash (when the owner do naughty things) via a CDROM or a floppy.

So, even the OP royally mess with the BIOS flashing, he have a way to recover the motherboard without electronics engineering.

Maybe it is the time for him to go there: https://www.flashrom.org/Flashrom ?

I really want to thanks all for your help and your considerations.

Now i would make the point of situation:

i could say my problem it isn't a software problem , infact i tried several compiled kernels and at the last i tried windows too.

The problem depends exclusively from my motherboard. I'm disgusted from Asus

it has created a really lousy card just for its commercial purposes. At the first i had problem with GPU fan...low quality fan

and now this...

Infact for me it's not conceivable in the page XII of the manual's summary saiys

And then at chapter 2.4.2

The ram installed are 4 modules DIMM 400 PC3200 unbuffered CAS latency 3
The mobo recognizes them infact i tried the slow ram check at boot (I found it)
and no error for 4 GB... problems begins when s.o. starts. Infact, like my screenshot
demonstrate the mobo needs to be configurated in the way RAM availableb are less than 4 GB
For me was more correct if in the manual ASUS wrote clearly , SUPPORT UP TWO GB and stop !!

Before this, I used 4 banks of 512 mb and no problem , so the ram slot of the mobo are not broken.

I tested every new bank alone and no problem...

I dont think to update BIOS can resolve my problem infact the
firmware update description says

in reality i would try to update BIOS but if my mobo die , i have to buy a new mobo that supports
my old AMD socket 939 and my RAM, and i dont want to spend for this antiquated hardware.

There is another choise too, the ram i bought are not qualified from asus, but problem is
i bought ram now in 2018, that mobo and manual are from 2005...

If i decide to update BIOS or re-buy ram i will say.

You if have new ideas write me again

thanks

Hello again andros976. I think the last 2 lines above from the manual are the "gotcha".

I highlighted what I suspect is the problem and I think why this is reflected in Memtest failure. The BIOS can recognize it but not implement it. I agree with you that it is lamentable that manufacturers don't update exact brand/model RAM that is compatible but that would certainly raise the price of mobos. It's cheaper for ASUS and others to just move on. In the case of ASUS's A8-NE I found it rather easy to match RAM at the time since I just bought the best RAM I could find that had the older, simpler chip configurations. By contrast I bought an Intel board from the same era and did the same, not once but twice! each time failing. I finally contacted Intel who told me to specifically get Budget RAM. It needed to be very simple and of older design. I was very nervous since I hadn't returned the 2 sets I'd bought but I did what he said and to my surprise it ran. In fact, it ran great! I was happily surprised at how solid and snappy it turned out to be. I still have the other two sets though and I'd gladly send both of them to you to try out free of charge but I suspect shipping would be expensive.

What the Intel tech explained to me was that matching RAM chips to I/O chipsets is crucial and it isn't a given that top notch quality will always work... if the configuration mismatches in any way other than faster and even that can be a problem. It's not like dumb hardware like an old car engine where a bigger, better carburetor will almost always give more power but at least it will still work. Software in combination with hardware can be very specific.

I think you will have to try to find either an exact brand and model approved by ASUS or take the risk of simply insuring it doesn't fit into those last two "no-no" lines and hope for the best... and/or update the BIOS which still may just solve the problem though it's not mentioned ..... or, maybe last resort, do what manufacturers do and move on to newer technology. Here it is possible to get brand name motherboard/cpu combos with CPUs of the i3 3.6 GHz quality that also support the latest USB and SATA speeds, etc for well under $300 USD and non brand names for well under $200 USD.

Hi, i come back !

i think you take the target ! The problem is that the only memory certified are 3 models...So if your ram is not one of them
it 's unprobably it will work (i think) . I put a screenshot of certified DDR400 1 GB RAM.

Then i'm trying to buy the first one certified Kingston and give back the actual modules.

I will update you if the new one will work.

Thanks for your help

Attached Thumbnails

 

I really want to express all my disappoint again ASUS !!!
I bought another modules of RAM, this time i take ASUS certified RAM , the first one of the list

Kingston KVR400X64C3A/1G

They dont work too !!! I dont know what i have to think...

Hello again, andros976. Sorry to hear trouble continues. It may be that since you bought exactly what ASUS recommended that they will take the RAM back. However before I would do that, I'd update the BIOS. It really isn't hard for anyone who just bothers to read the instructions through. It would be impossible for me to pin an exact number on the times I've done BIOS updates but it is at least 100, possibly as much as 200 times. I can't say I've never created any problems but I was doing some very wild experimentation for awhile, using different brands BIOS images for different boards but with similar chipsets and even some hot-swapping to boot with one CMOS, yank it after booting, and popping in another similar CMOS chip to flash it. Still I never once created a problem I couldn't fix.. Just read and follow all the directions step by step. If you feel uncomfortable try it on some older mobo. If you don't currently have one, people give away and even throw away working PCs all the time. Some areas have Free Classified pamphlets, message boards, and there's always friends and family. Somehow, some way, you can manage the update and possibly fix this issue or at the very least learn a valuable skill.

Ok I would try, Could you support me to update BIOS. Tell me what I have to do