+1 , Old Way i meant DOS...and as said above, i also guess there is a procedure in ASUS website for downgrading, not sure though where i've seen it...
Printable View
+1 , Old Way i meant DOS...and as said above, i also guess there is a procedure in ASUS website for downgrading, not sure though where i've seen it...
i try flash my BIOS from DOS using afudos but same problem
<<the bios is too old or isn't compatible with this mb>>
i use bios : 1402 and 2603 .
http://img.techpowerup.org/101113/IMG_0043.jpg
I don't know which afudos version do you use, but try this one: Link
ok.
i made it with the afudos 207 thnx to sunfire
i use the parameter AFUDOS /ixxxx.rom
afrer reboot my pc don't post i clear cmos several times but nothing.
i fix it!
thanx.
I guess that's it for bios updates for this board ..
There hasn't been a new bois for over 6 months now ,
but until this last bios , we used to get new boises once or twice a month
trust me there has been a halted 3702 bios that was quikly replaced with a 3706 bios, that has disapeared, but it still echo's on the asus site,
http://img225.imageshack.us/img225/7686/image1cs.jpg
You can now get 3702 from japan site, and also on the U.S. site
M4A79 Deluxe 3702 BIOSCode:http://dlcdnet.asus.com/pub/ASUS/mb/socketAM3/M4A79_Deluxe/M4A79-ASUS-Deluxe-3702.zip
Support new CPUs. Please refer to our website at: http://support.asus.com/cpusupport/cpusupport.aspx
HDD Recognition Fails ? You mean disks not found at all, or that it takes much time?
i've a R-0 of WD6400AAKS and they're just finely recognised. It is a matter though that my Gigabyte 790X-DS4 with 3.2.1540.6 scans disks much more faster (2-3 dots passing vs. 10-12 dots at scan with M4A79)
Different things can happen when I turn on my PC. For example:
1. Every disk (2x200 GB RAID-0 and the two 640 GB single disk) recognized within 2-5 dots.
2. Same as 1. but a lot more dots needed. Sometimes I see two(!) rows of dots. This means 1-2 minutes of waiting, but at least, it works.
3. Every disk recognized (after a long wait), but RAID-0 is offline.
4. One or more disks missing from the list.
Option 1 and 2 are really rare, maybe every 5th boot.
I've double checked my drives, all of them, neither is reporting S.M.A.R.T. errors. I don't know what else can I do. I made a request about half year ago to upgrade the RAID Option ROM in the BIOS, but it doesn't seems to be happening at all.
I can understand, that BIOS upgrades on newer boards or/with newer chipsets or/with Socket AM3 are more important, also Sandy Bridge is launched and they (Asus) had to do a lot of work with UEFI, etc. I also don't know how much time is needed to upgrade the RAID Option ROM and test it to be useful and make a beta BIOS. I would try that BIOS for sure. Maybe it won't be helpful at all, but at least I could have said that they have tried to help.
At now, I'm just tired about this :(
finaly we get 3702
...all pics of chew's posts are lost...:(
Why do you need them?
good review?! yeah! it was really useful when you wanted to push your board to the limit :D
Unfortunately google cache didn't helped this time. Try to PM him, maybe he still have the pictures somewhere :shrug:
And? What did you found? :)Quote:
I finally got home and looked at my board....:)
I bumped on a Vdroop mod for M4A79XTD model and wanted to find out if they shared the same controller.. M4A79XTD has an EPU controller and M4A79 has ST L6740L controller...
i know it has been discussed, but for e.g. 1.5125V in BIOS, i get 1.469~1.472 in CPU-Z and as i recall the DMM measurement was close to CPU-Z, not BIOS value...i thought that maybe i tried a vmod...
i'll check again when i have more time...pin No.5 is the Vdroop according to the datasheet, so i'll check the traces and see if i can get somewhere with this...
That's a realy bad vdrop, but it seems that all M4A boards suffer from this. Mine too. Back in that days when I've played with this board I made a sheet with voltages. One column showed the voltages set in the BIOS, and next to it was the real voltages under load. Since then I've moved several times and that paper got lost.
Look what I found: M4A79 Deluxe Vmod
New BIOS 4101 13/4/2011 :
Quote:
M4A79 Deluxe BIOS 4101
1. Improve system stability.
2. Support new CPUs. Please refer to our website at:
http://support.asus.com/cpusupport/c...Language=en-us
3. Enhace compatibility with some USB device
M4A79 Deluxe BIOS 4101
Release date: 2012/01/31
1. Improve system stability.
2. Support new CPUs. Please refer to our website at:
http://support.asus.com/cpusupport/c...Language=en-us
3. Enhace compatibility with some USB device.
I'm so mad now, need to take a brake before I write anything else... :mad:
Edit: I'm slow...
Y u mad ? :p:
RAID ROM still 3.0.1540.59...seems they keep that on the safe side...newer versions had some trouble with SSD's as far as i remember, at least as reported on Gigabyte boards...
I just flashed it, so far so good....
You've got it: RAID Option ROM. That's why I'm mad. Really mad.
Already flashed this BIOS a few days ago, so far so good.
Just few quick questions:
- Are you using RAID or AHCI mode?
- Stock MS AHCI driver or AMD?
- If you are using the one from AMD, which version is it?
You've got it: RAID Option ROM. That's why I'm mad. Really mad.
Already flashed this BIOS a few days ago, so far so good.
Just few quick questions:
- Are you using RAID or AHCI mode?
- Stock MS AHCI driver or AMD?
- If you are using the one from AMD, which version is it?
Not using one, but there are 2 concerns with sb750 an ahci:
1. if Asus didn't fix it as some others did in later bios releases, using msahci will cause a 10-30s pause/delay right when the windows loading screen appears.
2. some sb750 users (me included) complained about the latest amd ahci present on 12.1 (bsod starting windows), whereas the previous 11.12 works ok.
BSOD on 12.1 is probably caused by erratic installer btw, check last posts of this thread here (Greek Forum, use google translation)...use manual .inf installation from device manager...
I have my old installation in 2x WD6400AAKS W7 x64 Raid-0, using 3.2.1540.75...it's too old though and loads of apps installed, so it's slow...disk check from raid rom is fast, however...
New installations include 1x Crucial M4 128GB for XP x64 with 12.1 AHCI (1.2.001.0317, 10/04/2011) and 1x Crucial M4 128GB for Win 7 x64 with 12.1 AHCI (1.2.001.0321, 10/28/2011)...
Never used MSAHCI, maybe just onec to check performance differences. It's true that drivers for raid after .75 and ahci after 11.5 i think had for some reason crappy performance compared to previous ones, even compared to msahci...
current ones are still ok...
BTW 4101 is cool i'm running same settings 24hrs straight and seems to be stable (wasn't expected to be different)
Now I'm using the MS AHCI driver, given up AMD RAID and AHCI driver a long time ago. I had massive data loss in the past and decided to unRAID my drives and stay with the stock MS AHCI driver. These lockups are still common, but not when Windows loads. They just came randomly. The HDD LED on my case starts to glow continuously and I can't access my hard drives for 10-30s when it happens. At least it looks like it doesn't makes my data corrupted.
Interesting, you're not experiencing the problems what I had with RAID. I'm starting to think that my board doesn't likes Samsung HDDs. Don't know why though, never heard any compatibility problems with this board and Samsung hard drives. I feel a bit lost now. My last chance was an upgraded RAID Option ROM to narrow down my problem, but I think Asus are not going to release it for this board. Ever. BIOS modding is way out of my knovledge to do it myself even if it's possible.
Thanks for the answers guys!
If that is of any help for you, i use :
2x WD6400AAKS (Western Digital), 2x ST32000542AS(Seagate Green), 1x HD400LJ (Samsung Spinpoint T133 - retired to an old machine atm)
with my board, no problems at all.
Driver 3.2.1540.75, RaidXpert 3.2.1540.17
The only think happening from time to time, which i think we've discussed in previous page,is the drive scan during boot, which sometimes takes long (2-3 times has complete hang)
Latest Gigabyte 790FX-SB750 boards, also have 3.0.1540.59 and 3.0.9/3.0.A Ahci Rom...i guess that's it, no more Raid updates...
Thanks, but this isn't the case. Translation isn't working very well, but for what I can understand the only user reporting a successful install is running xp64 which uses another driver while the others are stuck.
In the past with my board and some 09 drivers I always had to install via *.inf because the setup wouldn't allow to update it, but it was just some missing hardware id's to match a sb750, before passing installation to the *.inf which had them.
I've made a thread explaining this situation, and I set up ports in combined mode so that the OS drive was in IDE allowing windows to successfully boot, but the remaining 4 ports running in ahci with the latest driver 1.2.001.0321 from 12.1 (where I could check that it was correctly installed on device manager, with all files, registry association and *.inf). What happens is that those ports won't detect any drive, hence why it previously failed to boot. Reverting to 1.2.001.0317 on 11.12 immediately solves it.
But still, as with the 30s msahci delay issue that happened early and sometimes never solved IIRC at least on Giga, Msi and DFI this might be related to specific sb750 boards, as I haven't an Asus M4a79 to check. For that matter, I apologize for this OT.
I've spent days to find a working combination of drivers and RaidXpert without a success. I'm not sure that I want to go through the whole process again. Maybe I will give a shot for that driver+RaidXpert combination.
Googled a few hours and found that the Asus M4A79XTD Evo has RAID Option ROM version 3.0.1540.44.
I knew it! There IS a newer one for Asus boards too!
Well, spent a few days again to try out different driver combinations without success. Anyway, most of my problems appearing before the operating system loads, so it's not really a driver problem. Still have HDD recognition issues even with the latest 4101 BIOS.
I give up.
It's probably caused by the Samsung drives, then..
can't think of any other reason, since i've tried many different drives other than samsungs (except my old HD401LJ) and it works just fine.
I also thinked about that maybe the hard drives are messing with me. A while ago I found firmware updates for them but didn't wanted to upgrade because of the possibility of data loss. Now I did the upgrade but nothing changed. It doesn't matter now...
ps: The only Samsung drive died at me was a HD401LJ :)