a7v266-e Promise Controller Boot Issue

  • Thread starter Thread starter Aardvark J. Bandersnatch
  • Start date Start date
A

Aardvark J. Bandersnatch

Okay, I've gone through the ASUS site and googled for information. Still no
luck. Hope one of you can help me with these issues.

MB is an A7V266-E. This afternoon I upgraded the processor to the Athlon XP
2400+, and installed my quieter fans. Nothing big. After putting everything
back together and re-booted, there were two problems.

1. The 2400+ is showing up as a straight 2000. If I try to alter either bus
speed or multiplier, either the system locks up on boot or boots back to a
default screen. So far I've not been able to get 2200 or 2400.

2. Before replacing the processor, both hard drives were connected to the
Promise controller, recognized and worked okay. This was not a RAID array.
After replacing the processor, however, neither drive is recognized by the
Promise controller. The system will boot, however, when I put the two drives
onto the EIDE controller.

Any help would be appreciated.

Micheal.
 
Aardvark said:
Okay, I've gone through the ASUS site and googled for information. Still no
luck. Hope one of you can help me with these issues.

MB is an A7V266-E. This afternoon I upgraded the processor to the Athlon XP
2400+, and installed my quieter fans. Nothing big. After putting everything
back together and re-booted, there were two problems.

1. The 2400+ is showing up as a straight 2000. If I try to alter either bus
speed or multiplier, either the system locks up on boot or boots back to a
default screen. So far I've not been able to get 2200 or 2400.

2. Before replacing the processor, both hard drives were connected to the
Promise controller, recognized and worked okay. This was not a RAID array.
After replacing the processor, however, neither drive is recognized by the
Promise controller. The system will boot, however, when I put the two drives
onto the EIDE controller.

Any help would be appreciated.

Micheal.
Click to expand...

If by showing up as 2000 you mean 2000mhz then there is no problem as
that is the rated speed. Otherwise you may need to update your bios. You
can check here-
http://www.asus.com.tw/support/cpusupport/cpusupport.aspx
I would'nt mess with the controller until you have figured out if you
indeed have a problem or after you flash your bios if this is what is
needed.
 
tomcas said:
If by showing up as 2000 you mean 2000mhz then there is no problem as
that is the rated speed. Otherwise you may need to update your bios. You
can check here-
http://www.asus.com.tw/support/cpusupport/cpusupport.aspx
I would'nt mess with the controller until you have figured out if you
indeed have a problem or after you flash your bios if this is what is
needed.
Click to expand...

Indeed, that's what I meant. 200MHz or 2GHz. I'm running the 1015(Beta)Bios
and have been for at least a month without problem, so I don't think it's
the bios. So the processor is working correctly. That leaves the question of
the controller. I wonder what's gone awry withit?
 
As the other poster said, the AMD XP2400 actually runs at 2GHz, or 2000MHz,
not 2.4GHz. Your system is running correctly. AMD labels them XP2400 to
compete with Intel's 2.4GHz CPUs.
 
Aardvark said:
Indeed, that's what I meant. 200MHz or 2GHz. I'm running the
1015(Beta)Bios and have been for at least a month without problem,
so I don't think it's the bios. So the processor is working
correctly. That leaves the question of the controller. I wonder
what's gone awry withit?
Click to expand...
The 2400+ does not, and never will ( except for overclocking ) run at
2400mhz. It runs at 2000mhz which is the designed speed. You can blame
AMD for this one. Their marketing people in their infinite wisdom were
concern about consumer focus on processor speed and that this focus
would hamper sales so some genius came up with an "equivalent clock
speed rating designation". Basic differences in processor pipelines
allow the Pentium to run at much higher clock speeds yet perform tasks
no faster that the slower clock speed AMD. Once again, you do not have a
problem and you should not take any corrective action as there is none.
If you want more info check out these pages-
http://139.95.253.213/SRVS/CGI-BIN/...00000000118436161,K=4826,Sxi=2,Case=obj(1224)
http://139.95.253.213/SRVS/CGI-BIN/...00000000118440617,K=4826,Sxi=2,Case=obj(3511)
 
tomcas said:
[snippage]
[snippage]
The 2400+ does not, and never will ( except for overclocking ) run at
2400mhz. It runs at 2000mhz which is the designed speed. You can blame
AMD for this one. Their marketing people in their infinite wisdom were
concern about consumer focus on processor speed and that this focus
would hamper sales so some genius came up with an "equivalent clock
speed rating designation". Basic differences in processor pipelines
allow the Pentium to run at much higher clock speeds yet perform tasks
no faster that the slower clock speed AMD. Once again, you do not have a
problem and you should not take any corrective action as there is none.
Click to expand...

I *do* have a problem-- the dang Promise controllers don't recognize my two
HDDs. Got any ideas?
 
Aardvark J. Bandersnatch said:
Okay, I've gone through the ASUS site and googled for information. Still no
luck. Hope one of you can help me with these issues.
Click to expand...
2. Before replacing the processor, both hard drives were connected to the
Promise controller, recognized and worked okay. This was not a RAID array.
After replacing the processor, however, neither drive is recognized by the
Promise controller. The system will boot, however, when I put the two drives
onto the EIDE controller.
Click to expand...

simplicity itself: boot from floppy, do FDISK /MBR... done!
both drives now work on the Promise controller.
 
If fdisk can't see the drives on the controller how in the heck can you do
a fdisk /mbr? The mbr is on the fat, right? Not bios!
 
BoB said:
If fdisk can't see the drives on the controller how in the heck can you do
a fdisk /mbr? The mbr is on the fat, right? Not bios!

recognized
Click to expand...

Take the drive off the Promise controller and put it back on the IDE
controller; do fdisk /mbr; reboot; check Device Mangler; shut down; put
drives back on Promise controller; reboot; and all is well with the world.

This too complicated for ya?
..
 
Aardvark J. Bandersnatch said:
Take the drive off the Promise controller and put it back on the IDE
controller; do fdisk /mbr; reboot; check Device Mangler; shut down; put
drives back on Promise controller; reboot; and all is well with the world.

This too complicated for ya?
.
Click to expand...
Now that's one "essential" step, you failed to mention!
Good thing you only hosed the mbr.
 
Back
Top