A computer components & hardware forum. HardwareBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » HardwareBanter forum » Motherboards » Asus Motherboards
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

P4PE Promise 376 SATA/RAID onboard controller disappeared from BIOS!



 
 
Thread Tools Display Modes
  #1  
Old July 5th 04, 12:27 PM
SGT
external usenet poster
 
Posts: n/a
Default P4PE Promise 376 SATA/RAID onboard controller disappeared from BIOS!


P4PE Promise 376 SATA/RAID onboard controller disappeared from BIOS! :-(

What to do?

Used to work!
  #2  
Old July 6th 04, 05:41 AM
Paul
external usenet poster
 
Posts: n/a
Default

In article , SGT wrote:

P4PE Promise 376 SATA/RAID onboard controller disappeared from BIOS! :-(

What to do?

Used to work!


The PDC20376 could be defective, and is not being enumerated
properly at POST. If the chip cannot be seen, there is no
reason for the RAID BIOS to load at POST.

The more likely reason, is the bit that controls enabling the
chip has changed.

1) The first thing you could try, is write down all the custom
settings you have made in the BIOS setup. Then, go to the
Exit menu, and select Load Setup Defaults. This will attempt
to restore the factory defaults for the BIOS, and should
cause the PDC20376 to be enabled.

When the computer POSTs again, re-enter the BIOS and restore
your settings. When the computer POSTs a second time,
see if the RAID BIOS loads.

2) If that doesn't work, you could try clearing the CMOS. Be sure
to unplug the computer before trying this procedure, as failure
to remove +5VSB feeding the motherboard, can lead to damage to
a component when using the CLRTC jumper.

When the computer POSTs, you will probably need to reset the
clock. If the clock setting isn't zapped, then the CMOS wasn't
reset.

3) If that doesn't work, reflashing the BIOS chip is the third
thing I would try. Sometimes a portion of the flash chip gets
corrupted, and reflashing the chip clears the DMI/ESCD area, as
well as refreshing the code in the rest of the flash chip.
The best way is to use a floppy based approach to flashing,
reading any warnings listed in the "More" link on the Asus
download page, for whatever BIOS you plan on flashing.

http://www.asus.com.tw/support/downl...=P4PE&Type=All
aflash221.zip (program to flash the BIOS, if using the DOS method)
p4pe1007.zip (latest release flash file)

You can use EZflash, by pressing alt f2, or you can prepare
a DOS boot disk, and use aflash that way. Either of those two
methods is safer than using a Windows tool.

In terms of the code in the BIOS chip, there are two sections.
The mini boot loader is in the "boot block". This is a small
code segment, that implements CrashFree among other things. If
you flash the BIOS and select "N" when asked whether you want to
flash the "boot block", then if the flash fails, you can always
use EZflash to try again. Selecting "Y" for both the boot block
and the main body of the flash code, means you have no "safety
net" if the flash fails.

I'm not certain if the interface is exactly the same, between
aflash and EZflash. I would examine both methods, by getting them
to show their interfaces, and I would select the method that
offers the option to say "N" to flashing the boot block.

There are many versions of P4PE board, so make sure that you
download a matching BIOS from the correct download page.

When flashing the BIOS, you computer should be in its most
stable configuration. For example, if your floppy is getting
read errors, this would be a bad time to be reading the BIOS
code from the floppy. Similarly, if you are an overclocker,
and you are constantly getting memory errors, this could
ruin the flash. Check the memory with memtest86 from memtest.org,
just to make sure your computer is healthy in the memory
department.

After flashing is complete, when the computer POSTs again,
enter the Exit menu and select "Load Setup Defaults". That
is to make sure any stored data structures get refreshed to
match whatever version of BIOS you happen to have flashed.

If, despite all this preparation, the board won't POST after
the flash, there is always badflash.com .

HTH,
Paul
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Asus A8V Deluxe Promise RAID Controller @#$%@! Peter van der Goes AMD x86-64 Processors 10 December 30th 04 04:01 PM
pc problems after g card upgrade + sp2 ben reed Homebuilt PC's 9 November 30th 04 01:04 AM
P4PE Promise Controller Driver for Linux Joe Piscapo Asus Motherboards 2 April 30th 04 07:41 PM
P4PE , Hard Drive not detected on the on board promise controller Arthur Asus Motherboards 3 January 7th 04 09:53 AM
DAW & Windows XP RAID Tips, ProTools error -9086 Giganews Asus Motherboards 0 October 24th 03 06:45 AM


All times are GMT +1. The time now is 04:29 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 HardwareBanter.
The comments are property of their posters.