hello, i have a question.
i have an raid card that i wanted to use because i have few ports to short (Promise FastTrak TX4650)
but when adding it i get "Warnig have option rom can not be invoke (vendor id:1002h, device id:4393h)"
i resetted bios as some people told me on irc but it didnt help,
my current system,
Amd Phemon 1090T 3.6 Ghz x6
Kingston Hyper X x2 Dual Channel 4 GB (KHX1600C8D3K2/4GX)
GA-890FXA-UD5 (rev. 2.0-2.1)
MSI AMD 5830 TwinFroz 1GB
2x WD5000AAKS 500GB(Raid 0)(System)(ON GRaid Controller)
6x Samsung HD103UJ 1TB
2x WD15EADS 1.5TB
use as external
but thing is the promise card have conflicts with my motherboard , it simply freeze on "scanning drivers"
, i also tryed an older card 2 port Sweex PU101 but that one works fine, except it doesnt reconize the 2tb drivers when bootup the system, so i need to have the 2 external drivers shut down, windows wise they are reconized by the sweex but the trasnfer speed is kind of slow so thats why i tried the promise i had left to but it doesnt want to work,
can you surguest some options ?or maby a way to change the adress that the chips use in memory ?
thx in advacne
Update your motherboards BIOS and update your Promise Card with the latest firmware.
they are upto date, but i guess its like the people say, they use same adress in memory witch the sweex dont do, if there only was a tweak to change that, but i guess i stay with the sweex for now
Maybe try putting the controller card into another slot?
Also try disabling the USB LEGACY SUPPORT option under BIOS.
Turn off RAID in the BIOS, see what happens.
Changing the IRQ assignments to the PCI slots in the motherboard
i see i cant use motherboard controllers in raid
when i put my amd controller in raid i get this http://img846.imageshack.us/f/20110424004.jpg/
and when i put my gigabyte controller in raid it simply freeze on "scanning drivers"
but my os is in raid 0 witch is kind of anoying to go back to single drive now
If you can at this point, return the new controller and get something else. Sounds like a compatibility issue that might not be resolved. You can try contacting Promise, but good luck with that.
Okay.. I've not given up just yet..
vendor id:1002h device id:4393h
1002h ID is ATI.... hmmm
Not sure about device id:4393h... my guess is something with AMD.
4393h is MODE = RAID with RAID 5 option, PCI_CFG 0x40 = 0
Some other stuff I found..not sure what good it is for us..
This register holds a unique 16-bit value assigned to a device.
And combined with the vendor ID it, identifies any PCI device.
4390h for IDE controller, 4391h for AHCI controller, which
uses MS AHCI driver, 4392 for Raid controller, 4393 for Raid5
controller, and 4394 for FC Capable Other Storage Controller.
Bonding option would default/limit for non Raid5 controller.
Note 1: When Raid 5 Bonding option enabled and PCI_CFG
0x40 is 1’b0, Device ID is 4393h. When Raid5 bonding
option is disabled and PCI_CFG 0x40 is 1’b0, Device ID
could be programmed only to 4390/4391/4392h. Attempting to
program Device ID with 4393h when bonding option is
disabled, would result in Device ID become 4392h.
Note 2: To make device ID 0x4394h, software will program an
unlock bit (PCI_CFG 0x40) to 1’b1. Once programmed,
device ID becomes Read-Only. This bit supersedes bonding
option and the writing of device ID field. That is to say, in order
to make device ID 4390, 4391, 4392, 4393, PCI_CFG
0x40 has to be programmed to 1’b0 (default).
Somehow ATI (video card), AMD (chipset) and Promise (raid card) are having a conflict here.
yes i know the vendor id code i googled it and i got this, its AMD SB700/710/750
and as i told,
when enabling raid on the amd chip i get the vendor id error yes, the amd chip use the same ctrl+f option to enter raid bios i guess thats why it cant invoke with the amd controller
but when i disable it the promise card boot normaly,
once i enable any other raid controllers like gigabyte or the esata one i dont get any vendor id errors or any other messages, but promise card freeze at scanning drivers, my guess is , the promise card dont work if any controllers are in raid mode, thing is i use raid 0 for system
but anyway i wont go mess with the bios firmware, if i do something wrong it might not even work anymore
anyway in short ,what can i do to make it work with raid contoroller that is on raid 0
Looking at the error given it points to a conflict with the video card and the AMD onboard chipset Raid5. Perhaps try an older motherboard bios version and see if that helps. Sometimes no matter what you do parts will not be compatible and all you can do is sell them or return them and get something else.
humm i see, well guess i have to get a other one, but selling it, will be hard i have it for like 3 years its not worth anything anymore , and my mobo/raid card had an old bios so i upgraded them to see if it fixed it but no luck so i came asking arround on forums
You might be able to ask Promise and see if they have an answer. Maybe there are pins on the raid card that can be changed to make it work.
humm good thought , i will give it a try ,but how should i start my message ^^;
well promise cant help me and gigabyte dont reply
this is all i ccan show, i dont see any options to chhange IRQ
so if someone might know an option tell me
Copyright 2016 © Godem Online Inc. | Web and server solutions by NewTech Solutions.