Q45MDO does not initialise Promise RAID controller boot ROM

Hi all,
I have an MSI Q45MDO with a Promise EX8350 SATA RAID controller plugged into the PCI-E x16 slot, as I am using the board's onboard graphics for display purposes. However, when the system is booted, the Promise BIOS (which would allow me to configure the attached hard drives) is not displayed.
Does anyone know why this is and how I can get the Promise BIOS to be shown on bootup again?

Your Promise Card is explicitly listed in the Support list for your mainboard:
http://eu.msi.com/uploads/test_report/TR2_1750.pdf
You might wanna contact MSI Technical Support about this.  Maybe they can point you into the right direction:
http://support.msi.com/
Also, get in touch with promise to find out if there is a new BIOS available for your Controller Card.

Similar Messages

  • K9A2 Platinum bios 1.4 or 1.5 Promise RAID fail Boot.

    Ok I have BIOS version 1.3 running fine. I want to upgrade to a bios that officially support the phenom and its power usage. So back in may I try to upgrade to bios 1.4. No good the machine will not boot the RAID set that contains window XP.  :( Reverted back. Contacted support. Not much help... a few weeks pass. Contact support again they send me bios version 1.51. Same issue.  Reverted back to 1.3. Recently I tried the final release of 1.5 with the same issue. 
    Anyone out there using a phenom on the K9A2 and booting with the Promise RAID controller in a striped 0 set ? How did you get it to work with the current bios version. Tech support 'claims'  they have no problem with the bios and that they have tested it with the promise controller booting to XP.
    Thanks,
    Jon Harrell

    Considering the very large files that regularly run through the system and the extra cpus that windows inefficiently uses I doubt a software controller would impact the performance gains significantly. The units we have prep large format presentations and regularly handle very large files. Bandwidth is key. If this was the average desktop or even a web server yes 1 drive would most definitely be faster. But that would be a different subject.
    Although now we might just be considering scraping the whole MSI created mess, and purchasing a hardware solution like that of the quad sata raid in our server.
    But for now:
    Does any one know the perfect combination?
    e.g. Promise driver 1.1.1030.47 !work with Bios 1.50 (promise 2.8.1030.0032)
    Thanks,
    jh

  • Howto use onboard Promise Raid Controller pdc20265 on 694D PRO AR Ver1

    Currently I'm running Win2k on my MSI 694D Pro AR Ver 1.0 board with Bios version W6321VMS.310 and the included Fasttrack-Family Win2k Raid-Controller driver for my Promise Raid Controller pdc20265 with lite bios.
    Due to software updates I'm now absolutely required to switch to Windows XP Prof. However this is the cause for my inquiry:
    I downloaded and installed the latest available Bios version W6321VMS.370 from MSI site.
    On installation of XP I tried to include the pdc20265 Fasttrack raid driver from MSI site to get access to my HD's. However WinXP couldn't find any HD's. Remark: XP with SP1 and VIA 4in1443v.exe installed.
    So I repeated this procedure with the original drivers Fasttrack family and pdc202065 which were attached on floppy. Unfortunately no success as well.
    Then I have put the HD on the Ultra66 channel and installed XP first without raid and ultra 100 support.
    Later I re-enabled the on-board promise device in bios and unfortunately WinXP didn't recoginze the device by itself. So I provided the latest pdc20265 driver from MSI site. XP complained that the driver is not digitally signed. After reboot the promise device reported an error under WinXP.
    I repeated this procedure with the original drivers Fasttrack family and pdc202065 which were attached on floppy. Unfortunately no success as well.
    Why MSI-Site says this pdc20265 driver supports WinXP if there are only the Win2k and WinME,98... drivers included?
    Currently I can't use the promise device at all under WinXP. This means even I don't have an Ultra 100 controler available.
    Has anyone an idea how to install HD's on WinXP with the corresponding promise raid drivers for my pdc20265 onboard chipset?
    I'd really appreciate your help!

    Some of the suggestions I don't understand quite well. Please could you explain further:
    > remove the other two drives leaving the raid pair
    > and cd only
    >
    > put raid 2nd in boot order
    What do you mean with that?
    > reboot press the key you need to get in to raid bios
    > create the array and make it bootable
    array is already created (Note: there is important data on it, can't recreate it! Only Segate 80GB is free and empty)
    I don't want to boot from raid.
    >
    > now boot to cd to install,right at beginning it will say
    > press f6 to install mass storage drive you need the
    > driver on floppy to install it
    I already tried the XP-Install routine to specify additional mass storage drivers. (Note: 1 single 80GB Drive was attached)  Which are the suitable ones? As mentioned I tried the following:
    1. Attached floppy 'Fasttrack family drivers'
    Result: Message: Driver is for Win2k only. Not a single  Harddrive shows for installing XP.
    2. Attached Floppy (Promise Ultra 100 lite, 256 only)
    Result: Driver is for Win2k only. Installation procedure hangs.
    3. Driver from MSI-Site for pdc20265. Same as 2.
    4. Extracting via4in1 drivers and putting WinXPIDE drivers on floppy:
    Result: Installation routine doesn't recoginze drivers on floppy.
    > rest should be the same as normal
    >
    > this should be similar as well
    >
    > http://www.amdforums.com/showindex.php?s=&threadid=146384
    Which is the right driver for WinXP to specify for mass storage device at WinXP installation?

  • IMac does not connect to wifi on boot

    I own an iMac and run it with OS X 10.7.5.  Ever since system update 10.7.3 (February 2012) my mac more often than not does not connect to wifi on boot.  I have to select diagnostics and connect manually.  I did a design of experiment and have now discovered that I do not have this problem if I wait about a minute to log in after the login prompt displays.  I like my mac for it's fast startup.  It is a shame to have to wait unecessarily for it to connect to wifi before logging in.  I kenw this was a problem with the system update and this confirms it.  Does anyone know how to prevent this from happening so I don't have to wait?

    It has been a month now and waiting a minute always works for connecting to my airport extreme on boot.  I was cleaning behind my desk and realized that the ethernet cable was still attached to the back of the iMac even though I had moved the airport upstairs.  I disconnected it.  I also opened network preferences.  The wifi was moved a long time ago to the top for priority, but the inactive ethernet and firewire were still listed.  I removed both the ethernet and firewire so the only connection listed is wifi.  My computer has now found the internet on 4 consecutive boots without waiting.  It appears that having the other two options disrupts the connection process on boot.  I will continue checking over the next week and let you know how it goes.  Wish me luck!

  • Autocomplete does not work after adding controller to LOV

    Hi experts ,
    Autocomplete does not work after adding controller to LOV Region, i have checked the fnd_compatialbe mode it is fine.validation proprty is also false, stilll it is not working.
    can anyone help me its very urgent
    regards
    vamsi

    Hi Tapash,
    This resolved the problem. Many thanks for your help with this it has been driving me mad for the last few days.
    I could not understand why the standard Apps LOV regions had controller's attached to them and the autocomplete would function but with my pages it would not.
    I actually raised a TAR about this and got nothing back so have updated it with the resolution.
    Thanks again.
    Regards,
    David

  • Novell driver for promise raid controller PDC20276

    [size=13]Is there a Novell driver for the promise raid controller on the KT3 Ultra2-R (MS-6380E)  mainboard[/SIZE] this board uses the promise PDC20276 chipset.
    The supplied disk only supports windows ;(
    Can any one advise options thanks  :P

    CapricornC,
    Since you have a KT3 Motherboard and you posted in the nVidia/AMD/SiS Motherboard Forum, I moved the thread to Via Forum for you.
    Good Luck,
    Richard

  • K8N Neo2 + NVRAID + Promise Raid Controller = not working right

    I'm trying to get my Promise Raid card working with nvraid enabled and I've finally given up. It works fine with NVRAID disabled though. I have 2xSata on Raid 0 and 2xIDE on raid 0+1. i also have two other IDE's on non-raid and two atapi cdrom drives. In order for me to use all of my storage devices, i need the promise controller to boot. The Prommise RAID controller's BIOS will not boot with nvraid enabled. WindowsXP detects the drives, but if i try to mount them via PAM (Promise Arry Management), it says one of the drives is corrupt/not working. but if i have both the ide raid hd's on the nvraid w/ sata raid, then it works fine. I just won't be able to use my cdrom drives. if anyone has a fix for this, please let me know. and sorry for the long descriptions. thanks.

    Why don't you go into BIOS and alter the IRQ manually for that PCI card, because probably that card is using the same IRQ as the nVidia one.
    Be well....

  • Promise RAID controller & WinXP - 845 ultra

    I finally got around to connected a couple of drives to the Promise Fasttrack 133 RAID controller.
    When I go into windows.. It finds the controller..
    So if I look in Device Manager, I do see the Promise MBFasttrak 133 Lite..
    But under DISK DRIVES, the Promise 2+0 stripe /raid0 scsi device shows up as an unknown, and if I try to update the drivers.. nothing ever changes..
    The drive(s) does work, more of a comsmetic issue?
     Thank you,
     Fred R

    Some of the suggestions I don't understand quite well. Please could you explain further:
    > remove the other two drives leaving the raid pair
    > and cd only
    >
    > put raid 2nd in boot order
    What do you mean with that?
    > reboot press the key you need to get in to raid bios
    > create the array and make it bootable
    array is already created (Note: there is important data on it, can't recreate it! Only Segate 80GB is free and empty)
    I don't want to boot from raid.
    >
    > now boot to cd to install,right at beginning it will say
    > press f6 to install mass storage drive you need the
    > driver on floppy to install it
    I already tried the XP-Install routine to specify additional mass storage drivers. (Note: 1 single 80GB Drive was attached)  Which are the suitable ones? As mentioned I tried the following:
    1. Attached floppy 'Fasttrack family drivers'
    Result: Message: Driver is for Win2k only. Not a single  Harddrive shows for installing XP.
    2. Attached Floppy (Promise Ultra 100 lite, 256 only)
    Result: Driver is for Win2k only. Installation procedure hangs.
    3. Driver from MSI-Site for pdc20265. Same as 2.
    4. Extracting via4in1 drivers and putting WinXPIDE drivers on floppy:
    Result: Installation routine doesn't recoginze drivers on floppy.
    > rest should be the same as normal
    >
    > this should be similar as well
    >
    > http://www.amdforums.com/showindex.php?s=&threadid=146384
    Which is the right driver for WinXP to specify for mass storage device at WinXP installation?

  • Hard drive configuration with Promise Raid controller

    I plan on running two 30 gig 75GXP drives on the Promise controller in Raid-0 mode.  I also have a 60 gig WD drive that I use for backups and for initial installation.  During installation, I put the Win98SE setup files and all the drivers, apps, backup data, etc. on the WD drive and do a clean install from there.  
    My current (old) board is an Abit KT7-R with the Highpoint raid controller.  Using the Highpoint controller, I am able to put the WD drive as a slave device and the controller treats it as a normal IDE drive.  I'm moving to the 845 Ultra ARU.  From what I've read, if you put a single drive on the Promise controller, it tries to set it up as a Raid drive?  I don't want to risk losing my backup data on the WD drive to some attempt by the Promise controller to "raid" my single drive.  So, where is the best place to put my WD drive so that I can install my system from it?  I'm thinking about putting it as Master on IDE2.  I normally run my CD as Master on IDE1.  Once the installation is complete, I will remove the installation files from the WD drive and use it exclusively for backups.  I have the WD drive in a Vantec EZ-Swap rack, and I normally keep it powered off unless doing a backup.
    So, the plan is to create the Raid-0 array, Fdisk and format the array, and then load Windows from the WD drive, followed by all my applications.  Is Master on IDE-2 the best solution for the WD drive?  

    hi
    not very clued up on raid but it sounds right
    if the wd drive is on its own on that ide do not jumper
    as master you have to have no jumpers if all alone

  • UCS C240 M3 LFF - Not detecting RAID controller/option ROMs at all?

    I've just lodged a service request for this, but as I don't have a service contract I'm not sure how much support I will get from Cisco vs them just replacing the whole unit..
    In any case, It's a LFF C240 M3, dual CPU. It was purchased with an LSI2008 SAS Mez card.
    - Mezz card was installed, and all the drives are lighting up, however I am getting no option ROM to boot/see the drives at all. BIOS shows "PCI-E: M" (I'm assuming this is the mezzanine card) as not populated, however I have the option rom set to enabled for this slot. I have no SCU setting, and no software RAID jumper is installed or being used. I have connected the correct SAS cables from the mezz card to the SAS expander.
    - As well as this, I have two PCI-E SSD's that also have option ROMs - these are detected by OS's, however the option roms are not booting despite them being set in BIOS to load.
    - I also have a 10GBE NIC that IS loading its boot rom. Strangely, if I disable the boot rom for the 10GBe NIC, and Enable the boot rom for the PCI-E SSDs, the 10GBE boot rom still loads (If I disable the PCI-E SSD boot roms, the 10GBe boot rom stops loading)
    There are possibly 2 issues here - One is that the mainboard/mezz card/both are DoA. The other is that the BIOS is buggy, as enabling and disabling PCI-E slot option roms do not seem to correlate with the correct slots/boot at all.
    Any input would be appreciated before I DoA the lot

    Hi Zaira,
    The PCIe SSD is a PCI IDE/AHCI controller that has an SSD connected to it.
    Further research shows that in AHCI mode, the UCS server will boot the option ROM. The PID is
    VEN: 1B21 DEV: 0612 [0106] SATA Controller [PI 01]
    We need to run it in IDE mode however to boot off it. In IDE mode the option ROM does not boot. The PID in IDE mode is:
    VEN: 1B21 DEV: 0611 [0101] IDE Controller [PI 85]
    Both ROMS boot fine in all other servers I have tried (SuperMicro, HP and Intel) so I can only assume the UCS is somehow selectively ignoring this boot rom by the PID?
    Is there anything I can do here?
    Regards,
    Elliott

  • Onboard promise raid-controller and promise add-on sata-controller

    Can anybody help me with the following problem.
    I have 4 SATA hard disks.
    2 Western Digital Raptors and 2 Seagate Barracuda V of 80 gig.
    I would like to do the following:
    I would like to put the 2 raptors in raid-striping for my OS on my onboard raid-controller and use the 2 barracuda's for data and connect them the promise add-on card (promise ultra150 tx2).
    I have the following with this config: the raid-controller is no problem but when i connect a hard-drive to the add-on card, windows won't boot anymore and i have no possibility in the bios to choose to boot from the raid-controller.
    I'm using an MSI K7N2G-ILSR motherboard with the latest MSI-bios.

    I'm having the same problem but I can't switch my drives. I have my 2 200 gig maxtors full of data that i can't let go of. I've installed a new silicon images pci card with 2 sata channels. if i hook up the drives both bios recognize the drives correctly but it tell me invalid system disk. pretty sure that it's reading the pci card, not seeing a os installed and not even looking at my onboard controller. I was told that i can change irq priority, but i can't get it right or it doesn't work. I can install os on pci card but would really rather not. I'm very happy with the setup i have for once.
    msi k7n2 delta promise 376 onboard controller

  • K9A2 *V1* Bios 1.8 - No drivers for Promise RAID controller.

    Does anyone know which set of Promise Raid drivers work with the updated Promise firmware that is part of the 1.8 bios update?
    Version 1.2 of the bios includes Promise version 28.1030.0021 which works with at least 1.1.1030.27 of the promise drivers.
    Version 1.8 of the bios includes Promise version 28.1030.0032 for which I cannot find any working drivers; do they exist? (Vista cannot see the controller and is unable to locate a suitable driver. Trying to use existing promise driver fails since it will not recognise the device)
    Just had a brainwave. On the MSI site, there is an updated driver pack for the Promise controller (this is a V1 board); this version is
    Vista32/64 Ver.: 1.1.1030.47
    Is this the version that is compatible with v1.8 of the bios (and hence 28.1030.0032)?

    Give them a try, they if they work will show soon enough.

  • Final Cut Pro 10.1 does not detect Promise Pegasus

    HI,
    I would like to change my location of where events are stored at for FCPX to my Promise Pegasus (6x3TB, configured to RAID 5), which is what i bought it for, but sadly, my FCPX does NOT detect my Pegasus at all in Library. It does however detect other storage devices like when my SD card is plugged in etc, and my macintosh hd.
    I spent alot of time reading up and googling and some advices say it must be configured to MAC OS Extended (journaled) which, when i checked, it is! So I don't know what's the problem now.
    It is getting very frustrating and I can't seem to get it to work. Would really appreciate if any kind souls can help me out on this!

    Did you solved that isue? I have the same problem.
    Thanks

  • Mac Mini does not detect DVI monitor on boot but does so on awake

    Hi,
    my Mac Mini fails to detect a monitor on the DVI port when it boots (monitor says no signal).
    If I leave it a few minutes to boot, then put it to sleep and awake using the power button, then the display appears.
    This problem does not occur with the DVI-to-VGA adapter, and I have tried with 2 separate DVI monitors (different brands) and cables (both monitors are fine with Windows PCs).
    I have tried various resolutions and color depths, to no avail.
    Any ideas about how to resolve this?

    What brand and model of monitor do you have?

  • After upgrade conky does not display right on first boot

    After i upgraded my arch conky will display on top of all windows when i first boot the machine, until i kill it and restart it then it works perfectly. I am using openbox with no compositing.

    conky reports the same thing as all previous versions, playing with the config did not help and no note of any config changes on conky's website. yes downgrading to conky-1.8.1-1 works for now but world like to fix this as it does not seem to affect my other computer with almost the same hardware and setup.

Maybe you are looking for