> Fajar Priyanto wrote: > <------------------- [ SNIP ] -------------> > > Actually I checked my system's BIOS and it checked the entire RAM and > reported no error as I guessed but I found out something interesting. > When the system crashes it shows a report page and it also says that > there is some conflicts or something like that to load interrupt table > for 1394 Firewire port. Now, I think the mndk 10.1 is not enhanced yet > to work with Firewire ports. Don't you think ? > The BIOS RAM test isn't much of a test. It will find a fried RAM chip, but that is about it. I have had RAM that passes the BIOS test with flying colors, but shows bad locations when you run memtest86 on it. You may even be able to boot your OS with it, but end up with strange crashes. So don't take the BIOS memory test as proof that the memory is good. (Think of it this way - the BIOS test is like starting a car - just because the engine starts doesn't mean there is nothing wrong with it...)
This isn't to say there is something wrong with your RAM - just that the BIOS test is worthless as far as testing memory. The problem with Firewire interupts is a better indication of what is wrong. Firewire is supported, so it being there is not the problem. The fix may be in the apic or acpi settings as others have said. Or you may be able to get it to work by changing the Plug and Play OS setting in the BIOS, if your BIOS has this setting. If it doesn't have a setting for Plug and Play OS, or P&P OS, look for some reference to booting windows. There are a couple of ways the BIOS writers ask the same question... Mikkel -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup.
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
