On Saturday 08 March 2003 07:02 am, Adrian Golumbovici wrote: > I am interested. Of course I am. I want to find out if it really is a > kernel or mobo problem. Unless I can prove that my mobo is not working > right I have no chance of giving it back. If you can help me trace the > exact problem I would be gratefull. I would love to bring back the > motherboard to the shop and buy one with no problem (probably a A7N8X), but > unless I can prove it is not working I have no chance. Unfortunatelly I > know no diagnostics program which could help me prove that. So please help > me trace the problem to the origin. I am not that much of an expert, but > would love to see my system work. I am a programmer myself, but not that > much into hardware level programming and linux is my newfound love (been > fiddling with it for about 2 years now), but never had to go this deep to > trace a problem. > > So please help. > > Best regards, > Adrian
Hmm, OK with vga=788 try linux mem=892M and go up or down in 4M increments until you reach an unbootable (or bootable) situation. At some point in the procedure you should encounter the situation that you receive an error message on the screen about "bad bridge mapping". This would be definitive proof of a broken BIOS, not a faulty motherboard, but rather a design flaw. Most likely you can reproduce crashy behavior in the "other" OS by adding tasks until most of RAM is filled up, if further proof of a motherboard flaw is needed. Civileme
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
