locked
anyone else trying to run WHS on an AMD 690 chipset based mobo? RRS feed

  • General discussion

  • Hi,

    I've installed WHS on a Gigabyte GA-MA69GM-S2H and run into some problems

    1) Unable to change 690 to SATA/AHCI mode
    - tried to 'install' drivers during WHS install but never prompted for drivers via F6 during setup even though only 2 devices present = SATA 300 Seagate HDD and 1 SATA conn'd DVD-RW (Samsung 203)
    - unable to simply change BIOS setting to SATA/AHCI
    will not complete boot to WHS - sys reboots during WHS logo screen w/black background
    - unable to install driver to WHS via update driver
    - unable to manually install driver, but I'm inexperienced with this in a 2003 environment and may need to check my process
    -- I think I saw a message about drivers not being "signed" although the text was specifically different and I know it matters, but my recall at the moment is fuzzy

    2) Misc AMD specific drivers & utils not happy to install or run
    - Cool 'N' Quiet seemed to install, but appears not to be running
    tried changing power settings to anything other than default named setting and still don't see/hear the slowdown (I'm using a speed controlled fan that does slow down if the hw has XP installed instead of WHS)
    - Dual CPU optimizations may not have installed; fuzzy notes
    - CPU dashboard util won't install

    I intend to re-install later and re-try some things while taking better notes (the above was my 1st install on this hw), but I'm curious if anyone else has tried an AMD 690 mobo or even the various AMD CPU drivers and found issues like mine. My searches here and with google yielded almost 0 hits, so I'm throwing this out there as a initial cry of "ouch!"

    Thanks!

    Monday, August 27, 2007 7:20 PM

All replies

  • Speednut,

    1. You will not be able to install SATA drivers in the installation process. The bios setting shuold be legacy/IDE when referiing to the SATA drives. Once the install is complete you can update the AHCI drivers.

    2. Most dekstop type utilities will not install such as sound drivers or possibly the CPU dashboard due top this being based on a server O/S

    Good luck,

    Bryan
    Monday, August 27, 2007 8:15 PM
  • In addition to what Bryan has said, you should try to obtain drivers for Windows Server 2003, rather than Windows XP, where possible. In some cases, an XP driver won't even work.

    Cool'N'Quiet should work as long as the BIOS is set up properly, but it's a server, so you won't see the same level of benefit as on a desktop.
    Monday, August 27, 2007 8:25 PM
    Moderator
  • Thanks for the quick replies...

    I guess I needed to do more to highlight some of the failures in the original text. I tend to say 5 things in one message, so skimmers may miss how much I really tried before the 1st post.

    I did try to update/install to SATA post-install, and that's when the sys reboots at the black & logo screen, so no go.

    As for utils and which driver model, at least 2 of the drivers I'm refering to are called out by AMD as being installers specifically for both 2003 and XP, so I'm not missing the obvious there.

    I'm very experienced at general hardware setup and driver updating, and don't mind if I have to pry open an installer to find the drivers inside if I really really have to, but the setup.exe's in this case are not compressed in a manner that non-developer utils like 7zip and WinRAR will decompress just to peek at contents, and I'm not one to just jam any old file into an OS and think it's stable.

    So having searched here on 690 and found nothing, I was hoping to see if there's others where we could help ourselves.

    But, if anyone has instructions on how to get something semi-generic like mass storage drivers to load when attempts to add/install the inf, update the driver or other manual updates fail, then I'm sure I still can learn and welcome the help. 

    Oddly, I've double checked my methods via instructions on how-to for other win 2003 server versions and those didn't help, since there appears to be a layer of driver verification sturdier than mere driver signing going on.

    For example, the AMD CPU uses a CPU driver that AMD publishes as being newer than what's in the ISO, and even newer than what came with the mobo on CD. amdk8.[inf, sys, cat] files don't install/update even for selecting the updated files.

    Anyone else seen this?

    Thanks,

    Monday, August 27, 2007 9:27 PM
  • SpeedNut,

     

    I have a 690G motherboard- possibly the same one, or else very similar model; sorry I can't be more specific at the moment but I am away from my system at the moment.

     

    I had trouble getting WHS installed when the BIOS was set to AHCI; changing to native IDE let the install work fine. I then went back into the BIOS and changed it to AHCI. WHS could no longer see the SATA drives (the primary was IDE so no probs booting); had to install the ATi chipset drivers to get the drives seen and re-added; there was no data on the drive as it was a fresh install.

     

    From what I have experienced, it's not really worth setting it to AHCI (the drives don't come up SATA in the console anyway), so unless you need the drives set to AHCI I'd leave it at native IDE.

     

    Hope this helps a little,

     

    Davo

     

    Edit: I have a Gigabyte GA-MA69G-S3H motherboard which is an AMD 690G board. I also had issues with the audio and so disabled it in the BIOS (no need for audio in the server)

    Tuesday, August 28, 2007 3:27 AM
  • I disagree that getting AHCI is NOT important, since ACHI is required for NCQ mode (which optimizes hard drive write speed, and thus fractionally would optimize backup times, minimize power usage, and drive life).


    An update:

    It took modifiying the inf file (temporarily) to get Win 2003 to install the SATA/AHCI drivers, which then identified the controller as a AHCI / RAID device and reduced the IDE devices counts down by one each (primary, secondary)
    (I'm not sure that's quite correct behavior, since I thought all 4 SATA ports shared the same controller and can be used in one RAID, but since I don't have any other drives in the WHS system temporarily, I can't verify)

    Even after having both the ATI IDE controller installed simultaneously with ATI/AMD ACHI/RAID SCSI controller in WHS, rebooting and selecting the mode of the SATA drive to AHCI still causes WHS to crash in loops as soon as boot goes to the Windows 2003 Server black background (in both non-IDE modes: AHCI and RAID). This is the same behavior that occurs without the AHCI drivers loaded, so no change.

    I suspect crashing is due to the fact that the SATA controller uses different HW ID's depending on the mode in BIOS.

    So next is to try install during build...

    There are some other non-SATA gotcha's remaining, like the fact the latest AMD CPU drivers won't load, but I'll post about those elsewhere if others are interested.
    Wednesday, August 29, 2007 2:03 AM
  •  SpeedNut wrote:
    I disagree that getting AHCI is NOT important, since ACHI is required for NCQ mode (which optimizes hard drive write speed, and thus fractionally would optimize backup times, minimize power usage, and drive life).


    Fair enough.

     

     SpeedNut wrote:
    There are some other non-SATA gotcha's remaining, like the fact the latest AMD CPU drivers won't load, but I'll post about those elsewhere if others are interested.

     

    What trouble did you have installing the AMD drivers? I installed the v1.3.2.16 driver available at the bottom of this page on my 690G board without any problems (from memory), but I don't have the exact same board as you nor have I had as many issues as you seem to have had with crashing- sorry I can't be of more help.

     

    With the AHCI drivers, did you get the new version of the chipset drivers off the Gigabyte site? I used the 8.38 version off the gigabyte site, installing using device manager rather than the install package. Sorry, but I think I'm grasping at straws: you seem to have explored the usual.

     

    Sorry I can't be of more help,

     

    Davo

    Wednesday, August 29, 2007 5:45 AM
  • I don't have this particular chipset but here are some ideas I have based on other drivers.

     

    Edit the file svr_2003\i386\txtsetup.sif file with the following information:

    In the [SourceDisksFiles] section add the following line:

    ahcix86.sys = 1,,,,,,3_,4,1

    In the [HardwareIdsDatabase] section add the following lines:

    PCI\VEN_1002&DEV_4380&SUBSYS_E0361631 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_303117AA = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_303217AA = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_0C8D105B = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_82881043 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_01FA1028 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_02061028 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_73251462 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_73241462 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_110A1734 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_02041028 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_01231025 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_01241025 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_602A1509 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_602B1509 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_80121854 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_80131854 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_2C311509 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_595016F3 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_595216F3 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_240E174B = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_2410174B = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_240D174B = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_500017F2 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_60101695 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_73281462 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_73291462 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_14F21043 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_2A52103C = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_2A51103C = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_13E810CF = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_30C2103C = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_2A4E103C = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_2A4F103C = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_01FC1028 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_01FD1028 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_604C107B = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_B0051458 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_10D11734 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_600F1695 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_600E1695 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_21231019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_21241019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_43811019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_43821019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_100415BD = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_100515BD = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_0611A0A0 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_0614A0A0 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_21341019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_21351019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_21361019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_21811019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_21821019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_21411019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_21421019 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_72431462 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_72441462 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_71741462 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_71751462 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_B0031458 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_D6028086 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_43811849 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_43821849 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_280A103C = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_2814103C = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_82311043 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_82321043 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_43811002 = "ahcix86"
    PCI\VEN_1002&DEV_4380&SUBSYS_43821002 = "ahcix86"

    In the [SCSI.load] section add the following line:

    ahcix86 = ahcix86.sys,4

    In the [SCSI] section add the following line:

    ahcix86 = "ATI AHCI Compatible RAID Controller"

    Compress ahcix86.sys with makecab and place the file ahcix86.sy_ in the SVR_2003\i386 directory

    create the directory files\drivers\ahcix86 and place the followinf files in it:

    • ahcix86.cat
    • ahcix86.inf
    • ahcix86.sys

     

    Let me know if this works

    Wednesday, August 29, 2007 5:48 PM
  •  

    ochhh

     

    I am ready to buy a Asus M2A-VM HDMI with the 690 chipset. + AMD Athlonx2 EE 2Ghz (45TDP)

    to start with I am adding 2 sata 750GB WD

     

    But I am not a hardware expert so reading trough this makes me wonder. Should I buy the mobo??

     

    Is there any better solution. (I like the 690 because it don't cost to much, and low power.

     

    (will Disable Sound and video in the BIOS lower the power (and heate) 

     

     

    regards

    Henrik

     

     

    Thursday, August 30, 2007 10:00 AM
  •  Henrikthoegersen wrote:

     

    ochhh

     

    I am ready to buy a Asus M2A-VM HDMI with the 690 chipset. + AMD Athlonx2 EE 2Ghz (45TDP)

    to start with I am adding 2 sata 750GB WD

     

    But I am not a hardware expert so reading trough this makes me wonder. Should I buy the mobo??

     

    Is there any better solution. (I like the 690 because it don't cost to much, and low power.

     

    (will Disable Sound and video in the BIOS lower the power (and heate) 

     

     

    regards

    Henrik

     

     

     

    You will be fine... I started to go with the gigabit board since newegg had good votes for it, but the update site did not have a lot on windows 2003 info... I decided to pass. (note: windows home server is based on windows 2003.) 

     

    Your sound should be okay as well... you have a different driver than the one the gigabit has.  Asus even has a sound driver updates for windows 2003.  Asus even allow for the utilities programs to work under win 2003...

     

    And no, you won't save anything by disablinging the sound in the bios.  Doubt if you would ever need sound, but who knows what ad-ons might show up ;-)  I need sound since I'll be running a virtual pc in my home server... this will be a double-duty pc for me running my music and such through the virtual pc. 

    Thursday, August 30, 2007 1:32 PM
  •  

    I have had my Asus M2A-VM with the 690 chipset since April 07. It is the non HDMI version, and I have not had any issues with it. My plan was to use this computer as a dedicated server from the start, so I didnt need  HDMI, and it was about $15 cheaper at the time.   I think it is a nice board, and it has been solid and stable from the start. It runs 24x7. 

     

    I have been running WHS on it since early May, and I have not had any issues with WHS running on the hardware.    I am not running Raid, nor have I tried it.  I had not planned on running an array.  I am taking advantage of WHS folder duplication.

     

    The Cool n quiet feature is enabled in the BIOS, so I assume that means it is working or it should be working.  But I dont know for certain.  The software is loaded.

     

    Henrik, I would recommend the mb.

     

    Roger

    Friday, August 31, 2007 1:26 AM
  •  Henrikthoegersen wrote:

    Is there any better solution. (I like the 690 because it don't cost to much, and low power.

     

    I was considuring buying a 690G based motherboard but decided against it due to the fact that AMD/ATI have not supported server OSs on some of their desktop products. Instead I was planning to to use an Intel 946GZ however when I made my purchase there were no 946GZ boards with GbE so i settled for a 945GZ.

    Friday, August 31, 2007 1:52 AM
  •  Bezalel Geretz wrote:
     Henrikthoegersen wrote:

    Is there any better solution. (I like the 690 because it don't cost to much, and low power.

     

    I was considuring buying a 690G based motherboard but decided against it due to the fact that AMD/ATI have not supported server OSs on some of their desktop products. Instead I was planning to to use an Intel 946GZ however when I made my purchase there were no 946GZ boards with GbE so i settled for a 945GZ.

     

    You are correct to a certain degree...amd/ati does have support for server OSs, but it is up to the mobo manuafactures to put together mobos that support both server and home users.  This seems to be a crapshoot with 690 mobos.  Either you get lucky or do your homework to ensure you will have a mobo that will load all drivers for windows 2003. 

     

    As I'm sure someone famous once said, "This is a different ball game."  lol

     

    I like the "air" of this thread, to list mobos that will work fine with windows home server aka windows 2003. 

    Friday, August 31, 2007 3:24 AM
  • I have the Asus M2A-VM HDMI which is the 690 Chipset and I have been running WHS for about 4 months 24x7 with no problems at all. All the drivers you need for Server 2003 are available. I have been very impressed with this motherboard considering its quite cheap. A few more SATA ports would be nice but thats the only down side I can see. Definately recommended.

    Regards
    Friday, August 31, 2007 11:34 PM
  • Just finished with the final build of my home server... went with a a cheap, but great mobo:  Foxconn A690GM2MA-8KRS2H AM2 AMD 690G Micro ATX AMD Motherboard.  This mobo is $42 over at newegg, plus free shipping... most of the people that has had issues seem to be doing raid, or having memory issues....  This is a good board....

     

    No issues on the drivers, everything installed without a hitch.  Placed the CD in the tray, said a prayer, and started installing.  Once I installed all the drivers, I rebooted... everything showed up fine, and no issues in device manager. 

    Saturday, September 1, 2007 4:26 AM
  • I too am using the GA-MA69GM-S2H Mobo for the HomeServer and it is working great.  Although, I have one problem with the drivers.  I cannot seem to get the audio drivers to load (Audio Device on High Definition Audio Bus).  Has anyone been able to get this to work?

     

    You are probably wondering why I need it for a server, but it is a server/media player, so I require audio out.

     

    Thanks for your help Smile

    Friday, December 28, 2007 3:35 AM
  • You may never get the audio drivers to load. (I didn't, though it was a different motherboard.) But before you give up, have you tried running the installer in Windows XP compatibility mode?
    Friday, December 28, 2007 4:18 AM
    Moderator
  • Installed WHS with minimal probs using AHCI on GA-MA69G.

    1. Download W2k3 sata/raid driver, available on support page
    2. Set bios to AHCI
    3. Run WHS setup, don't bother adding drivers during initial setup screen, it doesn't work
    4. When computer reboots to blue DOS setup screen, press F6 and load drivers. They can only be loaded from drive a:, I used a usb floppy drive.
    Tuesday, January 8, 2008 11:31 AM
  • Hi,

    on my machine I can't boot the WHS dvd if AHCI is enabled. But I've managed to install the AHCI drivers for my Asus M2A-VM HDMI board (also AMD 690 chipset based) using this procedure:

    1. Create SATA driver floppy disk using the tool provided on the Asus CD (or download the tool from the Asus support site)
    2. In bios set SATA mode to IDE
    3. Run WHS setup, don't bother adding drivers during initial setup screen, it doesn't work
    2. When computer reboots first time, enter bios and set SATA mode to AHCI
    4. Computer reboots to blue DOS setup screen, press F6 and load drivers. They can only be loaded from drive a:.

    I tried this only during a reinstallation, but a new install should work the same.

    Ciao,
      Steffen
    Tuesday, January 8, 2008 2:44 PM
  • To install the sound drivers for my Asus M2A-VM HDMI the following procedure worked for me:

    1. Install HDMI card supplied with the board
    2. Enable HDMI sound in the bios (HDMI Support -> On, HDMI Audio -> Enabled)
    3. Install WHS
    4. Install network driver from Asus CD to enable internet access.
    5. Download and install microsoft updates for WHS (this includes a driver for High Definition Audio Bus).
    6. Install sound driver from Asus CD.

    While I've got sound working, I'm still struggling to install the ATI display drivers AND a tool to configure to drivers to enable TV-out (I want to use the machine to record and view tv shows using gbpvr). Does anybody found a working replacement for Catalyst Control Center, which doesn't seem to work with Windows Server 2003?

    Currently I'm thinking about to install Windows XP on the machine to have better display driver support, run gbpvr on XP and use VMWare to run WHS on the same machine (on dedicated physical disks, not virtuals disks). Does anyone have experience with such a scenario?

    Ciao,
      Steffen
    Tuesday, January 8, 2008 3:07 PM
  • I also considering enabling AHCI on my GA-MA69GM-S2H but on an already working WHS, not as part of initial installation.

     

    Has anybody tried it? All the links I can find suggest it's a very problematic thing to do post-install on a Vista machine. I can't find any similar advice/warnings/experience for doing the BIOS AHCI change post-installation on a WS2003R2 system, much less on a WHS variant of that.

     

    Anybody got any thoughts?

     

    Tuesday, January 8, 2008 8:27 PM
  • Actually, it turns out to be really simple on Vista with Intel ICH9R AHCI. There is even lots of guidance out there for XP/Intel.

     

    2K3R2/AMD? approximately zero. XP/AMD? approximately zero.

     

    Any MediaSmart owners out there: what chipset is that? Does it run AHCI? If so, what driver? Any hint what the .INF that installed the driver looked like?

     

    To the folks earlier in the thread that got AHCI running on AMD600 chipsets at initial installation: any hints like what driver it's running and device ID number and so forth would be greatfully appreciated...

     

    There was also a discussion earlier in the thread re. hacking on .CAB files. Any more pointers would be appreciated...

     

    Anybody done a repair installation of "F6" drivers on WHS? Any hints from that angle?

    Wednesday, January 9, 2008 5:49 AM
  •  Dick Watson wrote:

    I also considering enabling AHCI on my GA-MA69GM-S2H but on an already working WHS, not as part of initial installation.

     

    At least for my Windows Home Server running a Gigabyte GA-MA69GM-S2H with an SB600, this was the trick: http://forum.gigabyte.de/cgi-bin/sbb/sbb.cgi?&a=show&forum=2&show=2290.

    Thursday, January 10, 2008 2:36 AM
  • I have noticed no real performance improvement with AHCI enabled. However, with AHCI enabled some SMART info such as disk temps is not available.
    Monday, February 11, 2008 11:23 AM
  • The real problem here is the lack of professionalism displayed by AMD.

     

    Intel takes ownership of its chipsets and provides the ultimate reference copies of all software on its website, available for all to download and encompassing all operating systems.  There is no problem making WHS work on Intel because no matter whose board you buy you can go to Intel for the proper drivers.

     

    AMD doesn't even acknowledge that it makes chipsets from a support point of view.   Go into support on their website and you will find nothing no matter how hard you search.  They have pushed support off to their assemblers and the board makers care about drivers for approximately the first 15 seconds after they create the board, when they are making the CD to package with the board.  Thus my Asus M2A-VM 690G board I bought a month ago has drivers over a year out of date, and WHS? Forget about it, they do not even have Windows 2003 RAID.  I have had to steal drivers off of the Giga-byte and Foxconn sites to make WHS work.  This is all rather insulting considering I know for a fact that ALL of the driver software for the HP AMD based WHS offering was written by AMD.

     

    Until AMD starts acting like a real company and supplying drivers on their website I seriously suggest you use Intel products for WHS.  I will be buying no more AMD products until they do since I believe in RAID 1 for internal drives on desktop computers (I have seen too many drive failures).  I can not continue the pain of trying to do RAID on AMD chipsets.

     

    If you already have M2A-VM board you can use what I did.  Boot from Asus CD and create driver floppy (it must be a floppy, sorry).  Install drive pair, set to RAID in bios and ctrl/f into RAID configuration setting up RAID 1.  Boot and install WHS from DVD, when asked supply floppy, you will have to search to proper directory.  When it reboots you will probably miss hitting F6 and get a BSOD, either reset or power cycle and hit F6 and load RAID drivers from floppy.  When it is done installing, set it up and install all drivers from Asus CD.  With automatic updates off, register the computer with Microsoft and download and install the 43 (at this point) updates most importantly Service pack 1 and High Definition Audio update.  Now go to the Giga-byte or Foxconn site and grab the latest Windows 2003 RAID software and install.

     

    This way you do not have to deal  with drive  rebuild since RAID1 was active during install.

     

    T

     

    Monday, August 18, 2008 9:51 PM
  •  
    ssiebert said:

    Hi,

    on my machine I can't boot the WHS dvd if AHCI is enabled. But I've managed to install the AHCI drivers for my Asus M2A-VM HDMI board (also AMD 690 chipset based) using this procedure:

    1. Create SATA driver floppy disk using the tool provided on the Asus CD (or download the tool from the Asus support site)
    2. In bios set SATA mode to IDE
    3. Run WHS setup, don't bother adding drivers during initial setup screen, it doesn't work
    2. When computer reboots first time, enter bios and set SATA mode to AHCI
    4. Computer reboots to blue DOS setup screen, press F6 and load drivers. They can only be loaded from drive a:.

    I tried this only during a reinstallation, but a new install should work the same.

    Ciao,
      Steffen

    I have a setup using AHCI mode. I had a sys drive failing, so wanted to replace the drive and do a reinstall. I tried your method during a reinstall, but don't get the ability to perform a re-install. WHS only allows a New Installation. WHS does not natively support AHCI, evidently, but if it worked on a install, why not on a re-install. I'm stuck in an endless loop, with no option to proceed!

    It should be stated very clearly DO NOT USE AHCI FOR WHS, or you will be royally screw**!!

    Tuesday, December 23, 2008 7:06 AM
  • I just stumbled back upon this thread. Not to defend AMD, but to maybe help out people like TechToys who haven't found the motherlode of drivers at AMD--since they hide them--try this link: http://wwwd.amd.com/AMD/SReleaseF.nsf/softwarepages/DriversbyDeviceChipset?OpenDocument.
    Tuesday, January 6, 2009 5:14 PM