Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: CuteBirdy on March 06, 2012, 03:11:30 am
-
I have a X58A-UD7 (rev 1) motherboard, which was working fine on BIOS F9d. Then a new Marvell BIOS firmware came out (2.2.0.1125), that was supposed to improve SATA 3 speeds on the Marvell controller. I did a quick search on forum posts about it, and many people reported it worked OK for them. And I never had BIOS problems in the past. So I flashed it. But it was a huge mistake. Afterwards, my BIOS loading time took 12 seconds longer. It would hang on the "C1h" light indicator, which is "memory check". This is the step just before you see the BIOS on your screen. I tried to remove the Marvell BIOS, but it seems to be an incomplete removal. Because when I installed the Marvell BIOS, there were 7 sections written, but when I tried to uninstall it, it only erased 1 section. I'm afraid the Marvell BIOS installation has corrupted my Gigabyte BIOS, and am very upset!
I've tried to install an older Gigabyte BIOS (F7), but it made no difference. In fact, something weird happened, on the older BIOS, AHCI would not work anymore, it would say "AHCI Bios not installed" when scanning AHCI hard drives at BIOS, and simply hang there. This never happened before I installed the Marvell BIOS! I had to change back to BIOS F9a then F9d, to get AHCI working again.
Another thing I noticed is, the BIOS freeze is shorter if I leave the memory on default 1033mhz (the freeze would then be only 5 seconds, compared to 12 seconds on my usual 1600mhz). Obviously this freeze wasn't happening at all before the Marvell BIOS.
I tried clearing CMOS and even taking the battery out overnight, no difference.
It looks like the Marvell BIOS has corrupted the AHCI Bios AND memory checker on the Gigabyte motherboard. And reflashing the Gigabyte BIOS doesn't correct the problems, because they don't update AHCI Bios or memory checker.
So my question is - is there a way to get a COMPLETE Gigabyte BIOS, which will reflash everything back to factory settings, including the AHCI Bios, and the memory checker?
I got the Marvell BIOS firmware from here:
http://www.station-drivers.com/page/marvell.htm
-
Please flash the latest BIOS again, or whatever latest one you want to use. Then load optimized defaults, save/apply/reboot BACK to the BIOS. Then once in the BIOS again set your SATA settings to what you need to load windows.
Then, go into the Integrated Peripherals BIOS page, and down to the Marvell settings. Find the "SATA3 Firmware Selection Mode" setting and set this to Force. Then save/apply/reboot and let it boot to windows, before windows loads after the IRQ screen you will see it update the Marvell firmware at the top of the screen, that should correct your issues. If not, try the same thing again with no drives connected to the controller.
If that does not help you'll need to ask around at the Station-Drivers forum, as I'm sure others have made the same mistake you did when flashing the complete package. I know many others use those firmware updates, but I believe the read in the forums on some threads where users have posted proper package or instructions on how to properly use the firmware they provide.
Just so you hear it again, as I'm sure others have already told you, the Intel controller is best overall for speed and stability. The Marvell controller ONLY gets faster sequential speeds, and those ONLY matter to benchmarks, and aside from that it is often very unstable, so you are best to use the Intel controller.
-
Thanks for the reply.
I've already done what you suggested. I loaded another BIOS, shut down, press clear CMOS, turn on, load optimized defaults, save, reboot, then adjusted BIOS to my usual settings. No difference!
I also know about the force Marvell option, it flashed the Marvell firmware but again, no difference. Because the corruption is not the Marvell firmware itself, but the AHCI bios and memory checker.
And I can't talk in station-drivers, because everyone there speaks french, I had to use google translate to see what they were even saying. They all use different motherboards to mine too. I keep seeing people referring to station-drivers, as if it's so good, but after this experience I'm avoiding that site forever!!!
Again I ask - because I'm quite sure what the problem is - how do I flash the AHCI Bios and the memory checker BIOS (which are separate from the standard BIOS) with Gigabyte factory default? Why doesn't Gigabyte provide this, so we can make our motherboard completely fresh again? Simply flashing the BIOS Gigabyte provides on their website will leave traces of corrupted junk behind.
To be frank, I think Gigabyte is part to blame for my problem, it says it has "Dual BIOS" suggesting you can go back to a backup BIOS in case things go wrong with the new BIOS, but I was never given this option. Because the motherboard didn't think there was a problem with the new BIOS (even though there was!), it erased the backup BIOS with the new one!
[Oh, and yes I know the Intel controller is still best despite SATA2, I just got a SATA3 SSD and got greedy thinking I might get lucky and have faster bootup times with the new Marvell firmware, boy was I wrong!]
-
The AHCI is an option ROM, not a BIOS, same applies for the memory checker. These could not be changed by the firmware you flashed, only by manually editing them in a BIOS and flashing it, or reflashing the BIOS.
Yes, I know that forum is French, sorry! Have you tried posting your question in English and then also in French in the same thread, if not please do as I'm sure someone can help and they've surely seen this issue before. Did you browse around their forum and find the Marvell firmware threads? If not look, there's probably info about this issue in one of those too.
AHCI BIOS and memory checker are included in the MAIN BIOS as part of the actual BIOS file, they are reflashed anytime you flash the BIOS as the BIOS flashes a complete chip with the new BIOS. I could change out the ROM for you, but that wouldn't help, it would just flash a new ROM in with the BIOS flash, same as the regular BIOS flashing does.
Please clear the DMI pool, this may help! Flash a normal regular BIOS using FlashSPI with the /c switch at the end of the command, or flash using @BIOS and check the Clear DMI Pool option before you browse to the BIOS file and flash it.
If that does not help, unplug the PSU from the board, press and hold the power on switch for one minute, then remove the battery and place a jumper or other short on the Clear CMOS Pins. Then let it sit like that for 12+ hours. Then connect the PSU back, remove the jumper and put the battery back in. Then do the optimized default dance.
If you want to kick in the dual BIOS recovery manually you can! Here's how, see the end of my second post here, for the PSU trick
http://forums.tweaktown.com/gigabyte/27576-bios-flashing-how-qflash-guide.html
Gigabyte is not to blame for you flashing some un-official firmware into your board from a random site that isn't even in a language you speak. I'm not trying to sound mean or anything like that, but you can't blame Gigabyte for your own errors.
Remove all USB items from the board when you next try to start it, that may be slowing the memory checking process. Also remove all devices from the Marvell ports until you sort this out.
The memory checking process is not a separate BIOS or anything like you are thinking, it is all included in the main BIOS, same applies to the AHCI ROM's. There is an Intel AHCI ROM, and the Marvell firmware ROM contains both it's RAID module and AHCI module, which are both flashed when you force the Marvell update, the Intel one is reflashed as part of the main BIOS every time you update it. None are separate at all, except the Marvell as it goes onto it's own chip.
What you probably need to do is properly flash the firmware you originally were trying to do, as I've known many users update theirs that way. I'll lookup the correct procedure for you to do that, or find one of those users and contact them for you.
When you downloaded the firmware, did you download the untouched one or the MOD one?
-
From the readme file, it looks like you can totally erase the Marvell BIOS via
type 'go -b -e' Erase only BIOS
type 'go -e' Erase every sector
type 'go -b -e' Erase only BIOS
type 'go -x -e' Erase only Firmware on MAGNI
I would try that, then reflash the BIOS and set Force on the firmware and that should erase what you put in there and correct it and flash back in the Gigabyte one.
If you want to wait a little bit, please do, as I have contacted someone who mentioned updating theirs and liking the outcome, so maybe they know where the thread is with users who've had issues. Hopefully he will get back to us later today!
Also, it looks like this is the main thread there for Marvell flashing, and some users are asking questions in English so you may get along ok asking, but I'd also include a french translation just in case. And of course browse through here from a web translator like Live or Google
http://www.station-drivers.com/forum/viewtopic.php?f=32&t=2876&sid=43f6652761bbc8b9e324ce771c836c54
A member here may be able to help as well, as I see he's posted there often, so you may want to PM him as well
http://forum.giga-byte.co.uk/index.php?action=profile;u=3723
-
Thanks again for the quick reply! I've made a post on the station-drivers forum like you suggested, will see if anyone replies: http://www.station-drivers.com/forum/viewtopic.php?f=43&t=3666
If flashing the Gigabyte MAIN BIOS updates the AHCI bios and memory checker like you said, then why is it that when I revert back to Bios F7 (an earlier BIOS) using @BIOS, with clear DMI pool, there was a weird thing happening - it said "AHCI Bios not found" when scanning for AHCI hard drives? Now, I was using Bios F7 before for a long time, and NEVER had this problem. It only became a problem after installing the new Marvell firmware. Interestingly, the Marvell firmware was specifically titled "AHCI" too. Piecing all this together, I can only conclude that the Marvell firmware has done something to the AHCI on the motherboard, which a fresh flash of a Gigabyte main Bios was unable to correct. And of course, the memory checker is still slow after flashing a new Gigabyte main Bios.
I did clear the DMI pool, I used @Bios first, then I read somewhere that FlashSPI was supposed to be the best method, so I tried that too - no difference.
Regarding your advice on unplugging PSU & remove battery etc - I did that, except not for 12+hours, it was for overnight, so 9 hours. Will that extra 3 hours make a difference - I think unlikely? Also I couldn't find a place to put a jumper on the Clear CMOS pins, instead I just pressed the Clear CMOS button for a minute... and besides, if we take out the battery for 9 hours, isn't that enough also?
I did remove all USB items from the board, turned off legacy USB, still no difference...
When I downloaded the firmware from station-drivers, there was only 1 version, inside it is a marvell firmware for AHCI and one for IDE. I used the AHCI one.
Basically, the Marvell firmware has done something weird to the computer, which a fresh flash of numerous Gigabyte main Bios's can't fix. What could possibly be causing the problem, if you say that the main Bios is supposed to refresh everything completely??
-
See my edits above, in case you missed any of the info I was just editing in.
AHCI BIOS not found always shows if you do not have a CD/DVD player connected, or if you do not have any drives in AHCI mode connected, that is a normal message and has nothing to do with what you think.
Trust me, today is not my first day, and I modify BIOSes all the time, I know what is in there and what isn't. ;)
Yes, the Marvell ROM (Included in the BIOS) has an IDE, AHCI, and RAID section. When you flashed you must have corrupted some or all of it, I'm not sure as I wasn't there watching ;D The AHCI message you are seeing is from the Intel controller anyway, not the Marvell one, see here is the file it's from, taken out of a X58 BIOS
(http://i.imgur.com/CzAw0.png)
Please try the extended clear CMOS as I mentioned, it may not help but often when there is major issues it can. As for your 9 hours vs. 12, ya that probably isin't going to make a difference now that you say that. You probably just need to erase and get the correct firmware flashed into the Marvell BIOS chip, so none of that may help until you do. If you did not remove the battery and unplug the PSU, and drain power ect as I mentioned then no, clearing the CMOS via the button is not the same. Sorry, I forgot there isn't a jumper on this board, haven't used mine in a while.
I believe the problem is you have the wrong firmware flashed into the Marvell ROM, and or corrupted it. Force option in the BIOS should have reflashed it, but it's possible you flashed something additional in there that the BIOS force option is not erasing, that's why I mentioned above the erase all sectors is what i thought would work, because that seems to me to mean erase EVERYTHING, then force back in correct firmware via the Gigabyte BIOS would relash in everything that should be there properly.
Hopefully someone will help us get this sorted out for you, or the erase will work if you end up trying it! Don't let this frustrate you too much anymore, I have one of these boards and it worse comes to worse I will do to mine what you did to yours, and then I'm fairly confident I can fix it, then I'll tell you what I did so you can fix yours.
-
From the readme file, it looks like you can totally erase the Marvell BIOS via
type 'go -b -e' Erase only BIOS
type 'go -e' Erase every sector
type 'go -b -e' Erase only BIOS
type 'go -x -e' Erase only Firmware on MAGNI
I would try that, then reflash the BIOS and set Force on the firmware and that should erase what you put in there and correct it and flash back in the Gigabyte one.
If you want to wait a little bit, please do, as I have contacted someone who mentioned updating theirs and liking the outcome, so maybe they know where the thread is with users who've had issues. Hopefully he will get back to us later today!
Also, it looks like this is the main thread there for Marvell flashing, and some users are asking questions in English so you may get along ok asking, but I'd also include a french translation just in case. And of course browse through here from a web translator like Live or Google
http://www.station-drivers.com/forum/viewtopic.php?f=32&t=2876&sid=43f6652761bbc8b9e324ce771c836c54
A member here may be able to help as well, as I see he's posted there often, so you may want to PM him as well
http://forum.giga-byte.co.uk/index.php?action=profile;u=3723
Interesting, the readme file that came with the Marvell bios didn't say "go -e" was an option, closest was "go -b -e". I think this is worth a try! I'll probably try it tomorrow (after checking this forum again) , will report results when I've tried.
Sure, your friend's input would be most welcome. I've posted in that thread you suggested, in English first, if not enough reply I'll translate to French :)
-
Sorry, see my edits above again! :D
I would go ahead and edit your post over there right now, so it included French and English just in case. I contacted a member here from there, and a member on another forum, if they can't help I'd say go ahead with the erase all sectors because then it will be blank, and if that doesn't correct it with a Force flash from within the MAIN BIOS I'll be able to help you properly flash with the other Marvell firmwares. I'm sure there's just a special method you are supposed to use, like only flash this part, or don't flash that part, ect and from your comment about 7 parts getting flashed that makes me think it was probably all when it should have been only certain ones.
Again, see my edits above, don't worry - we'll get this sorted out!
-
OK, I've been doing what you suggested - "go -e" to erase the Marvell firmware. It went through 7 sections rather than just 1 this time. But it came up with some kind of error message for 6 sections, something like "Autoload not found!". But at the end it said "Erase complete". Not sure what this implies. But, I went ahead and tried reflashing Gigabyte BIOS F9d with Flashspi /c - it still had the same slow memory checking problem. Then I flashed Gigabyte Bios F7 with @Bios with clear DMI, and, it still has the same problem as before, namely, "AHCI Bios not found". In other words, there is no difference, after doing "Go -e". Argh!
I know something is not right, because I never got the "AHCI Bios not found" error message before, on that same Gigabyte Bios.
Which edits were you refering to?
OK I'll convert my English post on station-drivers to French now...
-
Not sure which edit's you missed, we were both replying at the same time and I was editing so read all my comments again just to be sure :D
Also be sure to PM F5BJR here as I mentioned and linked above, he helps a lot in that thread over at Station Drivers, so I'm sure he can help!
As for the AHCI BIOS not found, that look like an edit you missed, see my comments on that and the image above. That is the Intel AHCI ROM, maybe you just never noticed it before or weren't using Intel AHCI, or had a CD and HDD connected before (And don't now). That is a common message, for the Intel controller. It's most commonly seen when the Intel controller is set to IDE mode or RAID sometimes too, if set to AHCI mode and drives are connected it will say AHCI BIOS installed, usually but not always as the Intel controller and it's message text is often translated funny :D
Haha, I know it used to say "This Will Take Few Minutes" at startup and I always laughed on that one.
You only flashed the AHCI Marvell updater right, not the IDE one? Also, can you please provide the exact link to the file you download
-
Wow that was scary, I decided to try flashing the very first Gigabyte Bios for this motherboard (F2), to see if it made a difference, and right after flashing, my computer would not boot up! It would power up, then power off after 3 seconds, then power up again after 3 seconds, then off again etc. I turned it off, waited for some minutes, tried again, and it powered up fine after that. Is this something strange?
With this F2 Gigabyte Bios, I am getting no memory checking freezes, which is great! BUT I can't use the Intel AHCI ROM at all, with AHCI enabled in BIOS it will just freeze when detecting my hard drive. I have to disconnect the hard drive, then it says "AHCI not found" or "not installed". While it might be a common message for you, I don't think the freezing when detecting a hard drive is common? Please note, this AHCI problem is not about the Marvell, but about the Intel! So it looks like the Marvell AHCI firmware messed up the Intel AHCI firmware bigtime, which a fresh Bios installation can't even fix...
The exact download of the Marvell firmware I used, is the disk icon to the left of the words "Firmware pour MV-91xx Version 2.2.0.1125 New 05/01/12", on the page I linked in my original post up above. I'd link the file itself, but station-drivers website is not allowing me to right click on the icon to get the direct link!
I installed only the AHCI one, not the IDE. I installed it when I had AHCI enabled in BIOS (so, Intel AHCI), but when I had IDE enabled for Marvell SATA3.
I'll try to message that person you mentioned now... thanks
-
Go back to the latest BIOS, and stop playing around for now until we hear back from someone with some experience on this, hopefully that will be F5BJR later today! Yes that can be common to hang after a BIOS update like that, luckily your CPU was supported by that old BIOS or you would have to get another CPU to update the BIOS again. So please stop playing for now :D
Again, the AHCI ROM is a part of the BIOS, the flash you did cannot change that. However, some BIOSes do not allow both controllers to be in RAID mode, and older BIOSes like you mention could have all kinds of unknown undocumented errors because they are old and rarely used so no one reports the bugs as they have already been fixed in later BIOSes.
So flash back to the latest BIOS and wait please. And YES, that is a common Intel AHCI message on all boards at random times, settings, and configurations (It has nothing to do with the situation at hand)! :D Trust me, I help Gigabyte users all day every day!
As for the link over there, ya I hate that! Firefox will let ya copy though, so please confirm for me that this is the exact one, so I have the same files you do when and if I have to brick mine to try and fix this for you.
http://www.station-drivers.com/telechargement/marvell/sata/marvell_91xx_bios_2.2.0.1125(www.station-drivers.com).zip
On your edit comment, thanks! I think that may be part of the issue why the flash failed for you, you need to have Marvell AHCI enabled when you flash Marvell AHCI firmware. The real way to update the Marvell firmware on these boards is by inserting it into your BIOS, which I can do for you later if you want, but you need to get the controller working again first :)
-
OK I'll stop playing around, as you put it :) I'm going to reflash back to latest BIOS right after this message, but that would mean having the memory check freeze coming back, that's OK since we're working on a fix :)
Sorry I just noticed you edited a previous post with pics about the "AHCI Bios Not Found" message, I now understand it's not a message to worry about. But it is certainly a problem though, that the BIOS froze completely when a drive is connected to the Intel AHCI, right after the "wait few seconds" message. This happened with BIOS F2 and F7. Doesn't happen with F9 BIOS, but F9 BIOS suffers from slow memory check as mentioned.
Yes, I confirm that link you posted (http://www.station-drivers.com/telechargement/marvell/sata/marvell_91xx_bios_2.2.0.1125(www.station-drivers.com).zip)) is the one I used. (http://www.station-drivers.com)
-
On your edit comment, thanks! I think that may be part of the issue why the flash failed for you, you need to have Marvell AHCI enabled when you flash Marvell AHCI firmware. The real way to update the Marvell firmware on these boards is by inserting it into your BIOS, which I can do for you later if you want, but you need to get the controller working again first :)
I didn't know that before, I thought it would update the Marvell AHCI even if I didn't have it enabled at the time. But the Marvell firmware should rightly have picked this up and stopped automatically, rather than proceeding to alter Intel AHCI and maybe memory checker!
My priority is currently to get memory checker running properly again, so there is no slow boot problem... not sure if I'm game enough to update the Marvell later, but we shall see :)
-
Remove ALL USB Devices, printers, hubs, ect and set BIOS option Legacy USB Storage (Or legacy USB detect) to disabled (Integrated Peripherals), that may help with the memory checking speed, but it may not as it may just be slow because while that's running the board is also trying to load the Marvell options which are failing.
I only said the Marvell needs to be in AHCI when you update the AHCI because that's how you should do it, it has nothing to do with Intel AHCI and cannot affect that at all. Marvell is it's own chip, Intel AHCI is inside the Gigabyte BIOS, totally separate from the Marvell chip and thus the Intel AHCI cannot be touched by the Marvell flasher. You are just reading too deep into all of this :) Anything can slow anything else down on the boards booting procedure, but the failed flash isn't because it messed up anything else other than the Marvell chip's firmware itself.
Just use your computer as you normally would, with as little down time as possible so you don't have to worry about booting up so often. Then wait until we can find out more, or if no one has any ideas I'll try to brick mine for you and then see if I can fix it. I don't use the Marvell controller anyway, nor that board for anything other than testing and helping others on stuff like this, so I have no problem trying to purposefully brick that controller to try and help you!
Sit back and wait, let's see if we can get some help and advice on this from others before moving any further.
-
Remove ALL USB Devices, printers, hubs, ect and set BIOS option Legacy USB Storage (Or legacy USB detect) to disabled (Integrated Peripherals), that may help with the memory checking speed, but it may not as it may just be slow because while that's running the board is also trying to load the Marvell options which are failing.
Those things I did before, but didn't make memory checking any faster. I remember reading you advising someone to take off their scanner, and set Legacy off, and it helped him, but not my case, probably because (like you said) the board's trying to load Marvell stuff that are failing.
I only said the Marvell needs to be in AHCI when you update the AHCI because that's how you should do it, it has nothing to do with Intel AHCI and cannot affect that at all. Marvell is it's own chip, Intel AHCI is inside the Gigabyte BIOS, totally separate from the Marvell chip and thus the Intel AHCI cannot be touched by the Marvell flasher. You are just reading too deep into all of this :) Anything can slow anything else down on the boards booting procedure, but the failed flash isn't because it messed up anything else other than the Marvell chip's firmware itself.
Hmm ok, but if that's the case, why when I revert to an older BIOS, like F7 or F2, I can't get the BIOS to boot when a hard drive is connected under AHCI mode? It just freezes after the "wait a few seconds" line, and nothing happens. But, maybe this is not a problem with the Intel AHCI, but a conflict with the Marvell things that were loading incorrectly during the memory checking stage... who knows.
Just use your computer as you normally would, with as little down time as possible so you don't have to worry about booting up so often. Then wait until we can find out more, or if no one has any ideas I'll try to brick mine for you and then see if I can fix it. I don't use the Marvell controller anyway, nor that board for anything other than testing and helping others on stuff like this, so I have no problem trying to purposefully brick that controller to try and help you!
Sit back and wait, let's see if we can get some help and advice on this from others before moving any further.
I'm lucky to have someone as helpful as you attending to my problem, risking your own board to help others :) thanks so much. OK I'll sit back and relax, computer is running fine right now except for the slow memory checking stage, ironically the amount of time I've spent on this problem probably exceeds the total extra time that the bootup takes for the life of the board. Going to bed now, will keep my eye on this thread when you or others chime in!
-
*
Station drivers firmwares are not for BIOS but for PCI-e Sata Host Adpater card with 88SE9128 as this :
http://www.ioisata.com/products/Host-Adapter/S3-PCIE1XG202.htm
Pierre
-
Thanks F5BJR, I thought that as well, however I have seen many users including Gigabyte board users flash that firmware successfully. Or at least they say so, maybe the ones I see mention this are lying out their rear's?
Do you know how this user can recover from the incorrect flash? Or is he going to have to send his board in so they can reflash it via eprom flashing, or just give up use of the Marvell controller and deal with the other issues this has caused?
-
I'm happy to give up use of the Marvell controller, I just want to get normal booting times again.
Problem is right now, even if I disable the Marvell ports in BIOS and don't use the Marvell, I get the problems.
In addition to the slow memory checking stage I mentioned earlier, I notice now the "quick boot" function you can enable under BIOS, might not be working properly anymore: after I do a hard reset or turn off/turn on the computer, the BIOS will scan memory again, even though I have "quick boot" on. Isn't quick boot supposed to skip the memory scan after the first successful scan? If I do a soft reset however (control alt delete), the quick boot seems to work, because BIOS doesn't say "checking memory" or to that effect, so it's a little faster. But still slow due to the freezing.
I'm afraid sending the board in for warranty, won't be feasible :( can I do the "eprom flash" myself?
The Marvell firmware doesn't say it's meant for the PCI-E device, nor is it mentioned under the station-drivers page, and the firmware doesn't look for the correct hardware before doing the flash.... it is a dangerous tool!
-
*
If you have a GA-X58A-UD5 with 8SE9128 as me you can flash
but only the embedded firmware ( little eeprom 8 pins )
In the BIOS you have 2 * options for running the Marvell port :
1 - using this firmware
2 - using the normal BIOS firmware
3 - also the possibility to copy the firmware in BIOS to the 88SE9128 firmware
**
Another solution but risky is to modify the BIOS with CBROM32 !!
Pierre
-> for restore original
- reflash your motherboard BIOS and use BIOS option to copy Marvell firmware part in the little eeprom if BIOS update not automactly
-
Pierre,
Thank you for your replies and help on this!!
He has already tried reflashing the BIOS, and tried the Force Marvell Firmwrare update from within the BIOS, it does not correct the issue. The X58A-UD7 does have the 9128 Marvell controller, same as the UD5 you mention, that is why I said I've seen heard users say they've flashed these board successfully, and now you agree and say it is possible as well.
So did he flash incorrectly, or if not why did it fail for him? He said he used the AHCI go.bat file, but the Marvell controller was in IDE mode. Do you think that was the cause of the problem? If so, do you think if he flashes it again, with Marvell AHCI mode enabled, it will correct it?
I can modify a BIOS for him just fine with Cbrom, I've done it many times for others and myself, but the issue is he can't even get Force BIOS option to fix it with a normal un-modified BIOS. He says he did that, and it does update the firmware like it should, but does not correct the issue. So I was thinking that when he flashed AHCI firmware while in IDE mode that caused the issue, do you think a reflash in AHCI mode will correct it?
Also, what did you mean by this comment? " but only the embedded firmware ( little eeprom 8 pins ) "
Can we flash the firmware offered at Station-Drivers to motherboard onboard Marvell controller SE9182 or not? You said no before, and now yes, but then you mentioned embedded, so I'm confused if you mean yes or no for flashing the firmware from there or not. These boards DO have the exact same Marvell controller as your UD5 model.
I am willing to flash my board to test various version for him, but I need to know for sure if it should be possible or not, and you said you do with your UD5, so it sounds like it! Although, I'm not sure I'll be able to brick mine like he did, if it's supposed to work then it will probably work fine for me and I wont have any problems, so wont be able to further help this user? :-\
Hopefully if he reflashes in AHCI mode as I'll mention below it will correct the issue
@ CuteBirdy,
Have you tried reflashing that same firmware yet, but in AHCI mode for the Marvell controller? How about flashing the next older version Firmware instead? I've seen many users have issues with various versions, so maybe it's just the version you tried that's causing the issues? This is definitely worth checking, sorry I forgot to think of that earlier! If you do flash an older version, be sure to set AHCI mode for the Marvell when you flash the AHCI firmware.
What does the controller currently do itself, is it failing? I mean does it work properly in AHCI mode, and IDE? What about RAID?
Do you have other memory to try with, to rule out your current memory as a possible cause of the slow memory check issue? If not, I know you said you removed all USB Devices, are you sure about that? I meant USB Keyboard and mouse too, remove all USB device and see if that stops the memory check slow down.
-
Hmm, no I haven't tried reflashing the Marvell AHCI firmware with Marvell AHCI enabled in BIOS yet, because I'm so afraid of it making the motherboard even slower. But if you insist, I can try it later in a few hours.
As for flashing older firmwares, I have tried F7 (the latest stable BIOS) and F2 (the first BIOS for the motherboard), both yielded exactly the same results - namely - no noticeable memory freeze, but when I enable Intel AHCI, the whole BIOS freezes to a total stop as it's scanning for a AHCI hard drive I connected.
To summarise, we have 2 outcomes:
- Flash BIOS F9+ (what I'm using now): Memory check for 6gb (3x2gb) 1600mhz RAM takes an unreasonably long time, up to 16 seconds, and "quick boot" feature doesn't work properly. But having hard drive connected to Intel AHCI port (when enabled) has no problem.
- Flash BIOS F2 or F7: Memory check no problem. But hard drive connected to Intel AHCI port (when enabled) causes BIOS to freeze.
You suggested flashing the "next older" Bios, you mean F6? If F2 and F7 don't work, doesn't it suggest it will be the same for all BIOSes in between?
Something just occurred to me. BIOS F9+ is a bigger bios than normal. While BIOS F2 to F7 are normal size. Could this be why I am getting 2 different alternative problems, a sign of what the problem is? Could the Marvell firmware be writing in the wrong sections, because it thought the BIOS size was normal, when in fact it was bigger? (At the time I flashed the Marvell, I was using F9d)
You ask me how is my controller currently. Which controller? Intel or Marvell? Intel - it fails only when I'm on BIOS F2 or F7, it is fine when I'm on BIOS F9+. Marvell - it is fine on any of the BIOS, maybe because it hasn't been touched by the new firmware yet.
As for other memory to test with - I don't have. But I'll tell you what I've done. I have 3 sticks of memory (triple channel). I checked with memtest86, no problem. Also I have tried switching the sticks around the slots, as well as leaving only 1 stick plugged in at a time, for each stick. The problem still exists. It cannot be that all 3 sticks of memory have become faulty, all at one time. And, before I installed the Marvell firmware, the memory all worked fine. So I really don't think it's the memory problem. Although worth noting, the memory freeze duration depends on the number of sticks plugged in, so for example when only 1 stick is plugged in (2gb) the freeze isn't as long, but still noticeable.
Regarding USB devices - yes, everything USB was removed, still had the slowdown. My keyboard is a USB keyboard but I have a USB to PS2 converter plugged into the PS2 slot (I did this so I can use the "power on" button on the keyboard to turn the computer on). So, I believe the keyboard is seen by the computer as a PS2 device. Ive been using the keyboard this way for years, with no problems.
-
I meant flashing older Marvell firmwares, you know, not the latest version.
Motherboard BIOS, always use the latest
As for the BIOS sizes, no that is normal, and has nothing to do with the firmwares. The only reason you may be seeing differences between versions is just how each version differs in doing things. Just keep on the latest BIOS.
And I would go ahead and try flashing in that same Marvell firmware you used before, the AHCI one, but this time with the Marvell controller in AHCI mode. If that does not help, try an older version of the Marvell firmware.
When I asked about controller, yes, I'd like to know about both. Is Intel AHCI bootable with hard drives attached, and is Marvell ports bootable with hard drives attached, in AHCI mode, IDE mode, and RAID mode (you'll need two disks and a RAID created to test that, so probably not feasible).
Ohh, sorry, I reply as I read. So, BOTH Intel and Marvell contrllers function fine? In AHCI or IDE mode? Really? If so, then there is nothing wrong with yoru Marvell controller at all! And the flash probably went fine, you can verify the firmware version in windows with Marvell Tray installed, of from the Marvell RAID BIOS, set RAID on Intel and AHCI on Marvell, reboot and go back to the Marvell and set raid or enter the RAID ROM for it in the BIOS, version will also be shown there.
If both controllers are working properly, as it sounds like you are saying, then there is no controller or firmware issues. The memory issue would could be anything, and since you don't have other memory to test with you wont know if it's due to your memory until you can test other memory. The firmware cannot be incorrectly flashed if the Marvell controller is working properly, so it sounds like we are both maybe wasting time thinking about this as it sounds like it works from what you just said!
You are right, it's not very ideal that all of your memory went bad at once, but it would be nice if you could borrow a single stick from someone for testing. You are using ONLY the white slots correct? If you are testing 1, 2, or 3 sticks you must use the white slots only. Just saying, I know you probably are because otherwise it's usually not bootable in the blue slots unless the white ones are already full.
Hope Pierre will reply in depth to my questions above, so I can consider flashing to test this for you! It's not that I wont or don't want to test, I'd just rather not get out the board, remove my current board, setup the other, ect all for nothing if you have already properly flashed the firmware and it's installed as expected, or would rather not do all that if there is no way it can flash on these boards (IE you never had a firmware failure on flash because updater does not work on these boards, thus fail is impossible) Hard to say because he said you can't do it, then next reply he said you can on 9128 UD5 boards which is the same chip and PCB as UD7 boards. So hope he will confirm yes or no, and you confirm my thoughts on your firmware flash actually taking, because it sounds a lot like it did properly now from all your comments tonight.
Please install Marvell Tray and then look in these sections and see what firmware you have installed, and tell us if any of it looks like the updated version you tried flashing, or confirm within the BIOS RAID module itself in the Integrated Peripherals section
(http://i.imgur.com/CsLZX.png)
-
Huh, now you are saying there is no problem? Why? Wow this is complicated to explain, I'll try again...
AFTER THE MARVELL 2.2.0.1125 AHCI firmware update, on my X58A-UD7 rev 1.0, bios F9d - while Marvell was set to IDE (not AHCI):
1) Intel controller is working fine (both IDE and AHCI), when I keep BIOS F9d. BUT when I changed BIOS to F7 or F2 (to get rid of the memory freeze), the Intel controller was NOT fine when set to AHCI, it would freeze when scanning any connected hard drive at BIOS stage (but fine on IDE). In other words, the Intel controller was fine only when I have the stupid slow memory scanner problem!
2) Marvell controller I didn't actually test (both IDE and AHCI), like I didn't plug a hard drive into it to test, and I didn't look for version numbers of the Marvell in Windows. Because I didn't really care about the Marvell anymore. I don't plan to be using the Marvell after all that trouble, I just want to get the problem 1 above (Intel controller problem) fixed, together with the slow memory scanning problem, because those things are weird problems that Marvell shouldn't have interfered with! However, I enabled (under BIOS) Marvell for IDE and later AHCI, and booting up was fine with both settings. The Marvell controller didn't freeze the BIOS, unlike the Intel controller.
You say there is no problem with the Marvell - but there is: the Intel controller problem, and the slow memory scanning problem, happened straight after flashing the Marvell firmware, and can't be fixed even after reflashing Gigabyte BIOS back many times!
So I'm not trying to get the Marvell to work. I'm trying to fix what the Marvell firmware update screwed up.
You blame it on the memory - but why all 3 of my memory sticks go bad at once? Why so coincidentally it happens right after the Marvell update? And if it's just my memory problem, why is there another weird thing happening, the Intel AHCI not working when running F7 bios? (And yes, I put the RAM in the white slots, that's obvious)
All these weird things happen straight after the Marvell update! That's how I know the problems are caused by the Marvell. Even though the Marvell itself might be working properly after the flash, it has stuffed up my board's memory scanner (when it's running bios F9d) and Intel AHCI (when it's running bios F7 or lower).
-
Sorry, I don't have time for a big reply this time. Please stay on the latest BIOS, if you want to use older BIOS that's fine, but not suggested at all due to older BIOSes often having various issues and they do not include the latest fixes and computability enhancements. All these BIOS flashes, are you shutting down and clearing CMOS fully after you flash? If not that could be the reason of some of the problems. Can you please post a list of your hardware as well, since we are now dealing with other hardware issues, thanks!
I understood you issues, you are not understanding that the Marvell flash or Marvell ROM cannot affect the Intel one or memory check like you are thinking. The Marvell ROM can only affect the Intel one, when they are both in RAID, and that is only for certain BIOS versions.
It's great you are not trying to get the Marvell to work, as it's not too great of a controller. Arrrr why did you do this in the first place then? :D I know why, I'm just kidding - we all need a good laugh sometimes to help keep it cool :D
Please don't be getting mad or frustrated with me, I do understand the issues you are having, and am willing to help by trying to do the same to my board, but you need to understand the issues as you just put them have nothing to do with Marvell firmware. It's just coincidence that they appeared at the same time you did that, it has to be. Yes, things do happen like that, that's why the word was created, and it happens to us all throughout our lives, often called irony instead of coincidence and we hate it because of that. Of course the BIOS version differences may make the issues appear differently, but it sounds like they are there no matter what to me. So can you please install the Marvell Tray for me, and show me your firmware version currently installed, so I know if I need to flash mine in order to try and help you sort this out.
I did not blame anything, I'm only trying to help you sort it out by suggesting testing other things which can possibly lead to the issues you mentioned.
Please do an Extended Clear CMOS, with the latest BIOS you have been using up until this flashing incident. To do that unplug your PSU from the wall or the motherboard, or switch it off in the rear. Then press and hold the case power on button for one minute, then press and hold the clear CMOS for one minute, then remove the CMOS battery and let the board sit overnight or at least 8-12 hours. I know that may sound odd to you, but this is how you often can fix very odd issues such as this. Please do it that amount of time, anything less and it may not work. But, you can try a short CMOS clear first and see if that helps, if not do the long clear please, so we can see if it corrects your Intel AHCI problem.
When you try the board again, please connect your hard drive to SATAII_0 and CD/DVD drive to SATAII_5. Hopefully this will clear that up! Before or after all that I'd also like to see your Marvell info like I posted above, so please install Marvell Tray, just so I can verify if the update did indeed do through properly, thanks!
-
*
For me i use BIOS modified with CBROM32
But only for the fun because i connect rarely disks to this port !!
I use always in RAID mode
Pierre
full firmware content for modify BIOS with CBROM32 ( rename zip to rar )
-
Thanks Pierre, but I already know how to do it with CBROM too. I just wanted confirmation from you, that it's possible to do with the flasher that comes with the Statio-Driver Firmwares.
However, I believe he flashed OK now, he just needs to verify for me, then I will test the exact procedure he used, and see if I also get the same errors and issues with the memory scan at startup, and the Intel AHCI functionality.
@ CuteBirdy
I forgot to mention this earlier this morning, please also go into your BIOS in the Integrated Peripherals section and disable Legacy USB Storage Detect, this may help with the slow memory scan at startup, even if you do not have USB devices connected. And about those, also be sure you remove and front ones too, including card readers or hubs, just in case that's what is causing the memory scan to slow.
-
Yes after each BIOS flash, I am shutting down computer, pressing clear CMOS, turn on, load optimized settings, then enter my own changes.
My hardware is: i7 920; 6gb (2 x 3gb) GSkill NQ 1600mhz DDR3; WD 1tb blue; ATI Radeon 4850; Vantec 600W ION2+
I am not using RAID at all.
If Marvell flash cannot affect the Intel or memory check, then what else can? I didn't do anything else to my computer at the time when the memory check problem happened.
I didn't really need the Marvell, but tried to get it working, because I had a new SATA3 SSD to test, was curious if it could work better on Marvell SATA3 than Intel SATA2.
I'm not mad or frustrated at you, I know you are trying to help, it's just so hard to find what the problem is.
I installed the Marvell tray, right now it doesn't say anything (no device showing) because remember, I had just done "go -e" which erased the Marvell firmware. I still need to do what you asked, that is, install the Marvell again (sigh I hope no new problems reinstalling it), plug a HDD in the Marvell, then see what the tray says. Will tell you when I get the chance to do it (within an hour).
I've done a short CMOS clear, no difference. Will do an extended CMOS clear tonight, and report tomorrow.
HDD is currently connected to SATAII_1, will switch to SATAII_0 soon.
BIOS already has SATA0-3 mode set to "Native" (not sure if that's what you recommend). "USB storage", I have tried both "enabled" and "disabled", but no difference. I currently leave USB storage as "enabled" because I need it to recognise my USB stick, which contains the marvell firmware I need to flash soon. In case you ask, no i currently have no USB stick connected to the computer, I already said, even with no USB devices connected at all, I get the memory slow problem. (but as mentioned, no memory slow problem with older BIOS, but then instead I'll get Intel AHCI problem)
-
Thanks for the further info! Did you try an extended clear CMOS yet as I mentioned above? If not please try it tonight while you sleep.
I told you what can affect that, USB items, memory errors, faulty drives, CD/DVD drives, KB/Mouse, ect. Anything you connect to the board can affect it really.
No, SSD 6Gb/s will not work better on the Marvell anyway, just so you know :D Thanks, I'm glad to see you are not mad or frustrated with me, I wasn't sure from your last post so I was hoping not!
Ahh ya, that would be why the Tray software isn't working then! Go ahead and flash again with the Station-Driver files, if those are what you want me to test, if you don't care about that and don't want me to test, then you can just use force from the BIOS and flash in the version that's included in the BIOS.
No rush on any of that about the controller, as I may not be online much longer tonight anyway.
Native enabled or disabled shouldn't matter, but it could I suppose. Try both ways on that and see if it affects your memory scan speeds or not.
-
OK I have installed the Marvell firmware again.
This time, I have the Marvell port enabled beforehand, with AHCI. So it is the "correct" flash procedure.
After flashing, I get this on the Marvell tray:
http://i.imgur.com/zWYOm.png
Which looks to be all OK.
I've plugged the harddrive in the Marvell slot, and it boots and works fine too.
Also, I had hard drive in SATA2_0 slot just now for testing, it made no difference, still have memory freeze problem.
Two bad things happened though :( right after the Marvell flash I just did:
1) When I shut down the computer, then turned it back on again, the computer turned off by itself during the memory check stage, then on again, saying overclocking failed and it was changing memory speed from 1600mhz back to 1333mhz. I then changed it back to 1600mhz, and it rebooted fine after that.
2) Now when I do "control alt delete" to restart the computer, the memory freeze is longer than when I hard reset the computer and turn it back on. Remember my first posts, I was saying, "control alt delete" reset would not have the memory scan slowing down as much as a hard reset? That's no longer true.
So, weird things happening to memory again, coincidentally happens right after a Marvell flash...
I think there is only 1 last thing left to try on my end, that is, the extended CMOS reset procedure. I'll do it tonight. Somehow I am not hopeful... perhaps you might be able to install the marvell firmware in the way I did it, and see if it slows down your memory scan too? ;)
-
Nice to see, thanks! Yeap, it shows the updated firmware version, so the flash does indeed go through properly!
Can you please borrow another single stick of memory from somewhere to test with? Hope so!
Yes, do the extended clear CMOS and see if that helps. I'll go ahead and setup my board tonight or tomorrow and do the flash, I'll be using the latest beta BIOS though, so in case that matters you might want to update to it as well (F9d)
http://www.fileden.com/files/2009/12/20/2696817/X58AUD7.9d.zip
http://forums.tweaktown.com/gigabyte/28441-gigabyte-latest-beta-bios.html
If it all works for me, then it'll have to be your memory or some other hardware you have causing the issue. I will video my flashing the Firmware, then show the BIOS settings and info, ect, and then booting into windows. I may have to upload multiple videos though, or cut them together, because the only digital video device I have here has a very small memory card in it (Like 4.5-5 minutes worth for video I think). But just wanted to let you know I'll do a video just so you know I'm actually testing this for you and not just saying that!
-
Hey, so you're actually going to do it... thanks :) you are a hero.
You don't really have to video it, I believe whatever you say, but it might be useful to see how things went for you.
I don't have another stick of RAM, I am thinking of buying more (6gb is too little) but still not sure what's best. I should have new RAM in a few weeks. But from my experiences, I really don't think it's the RAM that is faulty, can't have all 3 sticks go bad at once, it is more likely a fault with the motherboard if anything.
I'll let you know tomorrow whether extended clear CMOS works.
When I flashed my board with the marvell firmware "CPUAHCI" the first time, I had the latest BIOS too (F9d), I am aware of Tweaktown latest bioses. So, if you flash on your F9d, it should be the same as me (remember also I flashed it when my Marvell ports was set to IDE under Integrated Peripherals, but I really don't think this makes a difference in the end). Please watch out for any slowdown in your memory scan! And, if you feel like it, you could also try reflashing Gigabyte bios back to F7 (after installing the Marvell), and see if you get the same Intel AHCI problem as I did.
-
Yes, I told you I would test it for you! And now that I know the flash actually worked properly for you, I need to test it for you so you can see something else must be causing these issues for you and not the firmware update itself.
I'll video it, no problem, I normally would do that anyway in case someone asks to see the testing process. And since this is a odd issue, I'd like you to see it works fine for me, as I believe I shouldn't have any issues with it. If I do though, we'll know there's a problem with the BIOS itself, or updating the firmware like that is the cause.
As for memory, can't you borrow a single stick from any other systems in your house, or a friends? No need to buy another set, as you are right it probably isn't likely that all memory went bad at once unless it was storming or something that night this initially happened. And if that was the cause and it was a power spike, you'd have other issues like dead PSU and CPU too :D
So I will do it in this order.
1. Flash to F9d - do optimized dance
2. Start video, F12 to boot menu, then to DOS to flash firmware on video
3. Reboot to BIOS on video, show BIOS Marvell settings and USB, memory, ect OC settings.
4. Save/apply/reboot to windows on video to show memory scan
5. In windows show Marvell Tray Info on video
6. Shut down windows on video
7 Start system from fully powered down state on video to show memory check once more.
As for the F7 issue, no need as I wouldn't ever suggest using a old BIOS anyway, so you shouldn't either :D
-
OK, board is dusted off now, 980X going in and then tear-down and rebuild in progress.
Hope to have some answers for you shortly, maybe an hour or so, but vid will take a while to upload after that as my connection sucks :D)!
-
*
Thanks Pierre, but I already know how to do it with CBROM too. I just wanted confirmation from you, that it's possible to do with the flasher that comes with the Station-Driver Firmwares.
*
yes you can temporary flash with station-driver firmware , in this case go.bat flash a little 8 pins special EEPROM and not BIOS EEPROM
but that is temporary because for the GigaByte mothercard the BIOS flash after the little EEPROM with the embedded firmware
after modify with CBROM32 you are sure that the firmware and BIOS are with the same Marvell firmware version
Pierre
-
Grrrrrrrrrrrr! This might have to wait for a few hours, or until later today :( I can't find my camera that does video!
I think we have a cheap camcorder somewhere too, so if I can't find the camera I'll hopefully be able to dig out the camcorder. And I don't want to get into this until I have one or the other, so it has to wait until I find one. Don't worry though, I'll get it done today for sure as I have everything ready and waiting now!
@ Pierre Thanks for your continued replies!
BIOS only flashes if you set force though in BIOS, so if you don't set then the normal firmware (on-Chip) from Station Drivers would stay flashed in correct?
We are not trying to modify BIOS with firmware now (We don't care what version is used anymore) and, we already know how to do that. The issue is this user already flashed with Station Driver firmware. So now, we are not trying to verify that works, which we have via Marvell Tray info, and verify if that process is causing his other issues or not.
-
There's no rush don't worry, if you can't do it today can do it tomorrow or day after. My problem is not that urgent :)
No, there was no power spike or bad weather at the time I did the flash or when the memory scan problems appeared.
I have friends with DDR3 memory but it's not nice to ask them to lend me their stick, it means opening up their computer and if later their computer has problems, they might think I did it! I still don't think it's my memory though, because remember, if I flash with older BIOS, the memory scans with no problem, but instead there is a problem with Intel AHCI.
Your steps look fine to me, I'm sure you know what you're doing :) Just a suggestion... in your Step 1, maybe you can try to simulate my starting condition as much as possible, so:
1) set BIOS Integrated Peripherals: Intel = AHCI mode, and Marvell = IDE mode. (I know the Marvell should be set to AHCI before the Marvell flash, but I only did this afterwards with the 2nd marvell flash)
2) set MIT - memory speed = whatever your DDR3 memory speed is, in my case it was 1600mhz rather than the default 1033mhz. Because the slow memory scan problem happens when memory speed is set to a speed faster than default.
But if you don't want to simulate my starting condition (maybe you want to do a video about the right way to flash, not the wrong way lol), then up to you...
Haven't done extended CMOS clear yet, will do that just before I go to sleep.
-
Ya, I see what you mean about borrowing the memory from a friend!
I thought about your first suggestion there, but then I realized it shouldn't matter since you see the same issue after reflashing in AHCI. But ya, I'll go ahead and do it that way just in case it matters since you also thought about that too!
I planned to set my memory to 2000 anyway actually, so it'll be overclocked!
Thanks for being patient on this, I'll try to get it done this morning, if not I'll do it tonight before I get back into the forums!
-
OK!! Testing DONE!!
I find ZERO issues, and this is why I always want to do videos in instances like this, so you know I am being true and honest!
I created 3 videos, however I did have to make some changes to the hardware mentioned. I had to use my trusty 920 CPU instead of 980X, because my 980X wasn't playing nicely with this board. I'm an extreme overclocker (Frozen motherboard, CPU, memory), and the last time I used my 980X is was -73C and pushed past 1.7V, and that's been done 100 times to it, so needless to say it's been through a tough life :D Anyway, it wasn't playing nicely with my UD7, so I had to use my 920. And the 920 is an ES, so only memory multipliers are 6+8, so I could not test with 2000Mhz as I mentioned, but I did set 200 Bclk and x8 memory, so I tested at 1600 as you mentioned
(http://i.imgur.com/PQmDm.png)
I tested as we mentioned earlier, Marvell set to IDE for the flash, and that went just fine aside from the errors you mentioned before, but that's all in the videos. I tested rebooting, hard reboot, boot from full power down, ect, plenty of testing and the memory scanner never slowed down at all! I also tested with Intel in AHCI, and Marvell in IDE and HCI. I also tested quick boot on and off, and while thinking of that for you, I also tested control alt delete mid way through windows loading, and it reminded me of your comment about the memory scanner sometimes being skipped like with Quick boot. That happens often, depending on how you reboot (Even from windows can do it), and sometimes when you save/exit out of the BIOS it can happen, various times that happens but generally never on a cold bootup unless you have quick boot enabled
And I thought of one more thing while I did all this testing, that may help you with the memory scanner!! You know the 1, 2, 3 boot order, if you aren't sure it's in Advanced BIOS I believe and I show this in the video. At first I left it on defaults, but then I noticed it was like that during one of my visits to the BIOS, so I set my normal, 1 hard drive, 2, 3 disabled. And that's what I think might help you, as I've seen it help people in the past when USB devices weren't to blame for slow startups, sometimes that is. So set that to 1 - hard drive, 2 - disabled, 3 - disabled and see if it helps at all.
Since those videos are HUGE and my connection is TERRIBLE upload speed. I'll have to process them and remove the sound, and try to shave off some of the size in camtasia studio. Hopefully I can get them all down to about 15-20MB, and that will take me about maybe an hour or more to upload, not sure as I haven't uploaded anything over 1-2MB in a long time :D
Anyway they will be coming, unedited except for audio removal, and I'll probably resize them or change the codecs whichever will help me get them to a reasonable size. I could upload them as is, but that would take at least 7+ hours, and often when uploading my connection will drop, so I can only upload huge files like that to FTP servers where I can resume uploads, and I don't have access to one right now. If you do, and you want the unedited videos I'll upload them for you, you'll just have to get me FTP access somewhere. No worries though, I'm a very honest guy when it comes to things like this, so if you don't have a server or FTP account anywhere, you'll be able to tell even with my smaller edited videos that they haven't been edited to screw with them in anyway.
I had to use a old camera (5 MP Sony Cybershot DSC-P92), so the quality isn't going to be great, hopefully it's good enough for you to see everything was fine in all my testing! And the reason for the 3 videos is the memory stick is only 128MB in that camera!! Haha :D
I'll post the videos later today once I've got them done and uploaded, in the meantime try my tip above and see if it helps!
Haha, Damnit man! I just realized all three videos I had auto focus on, so they are all always trying to auto focus. Ohh well, they are uploading now, it's pretty decent video for this camera, but if you need me to redo them all without auto focus I can tonight.
* Edit 3 *
Videos uploaded!!
http://www.mediafire.com/?td8ckkrcbam4bky
* Edit 4 *
Sorry, I also just realized that I had the board set to RAID before using AHCI, so AHCI BIOS is installed in those videos!
However, as I mentioned before that AHCI BIOS is not installed message is normal! Here, check out the video I posted for this world record a while back, it shows that same message too!
http://www.xtremesystems.org/forums/showthread.php?273091-Gigabyte-X58A-OC-Takes-X58-Bclk-World-Record-276.42-Bclk!!
This is completely normally and it depends on what mode you are in, have used, what hard drives and CD drives are connected where, if you've cleared CMOS in-between, flashed BIOS, ect. Tons of things, it does not matter either way what that says, and if you need me to make it say not installed on this board in a new video let me know and I'll get-r-done when I get a chance.
-
Thanks for the tests. Since nobody in station-drivers has also shared a similar experience to mine, I can only conclude that my memory scanner problems aren't caused by the Marvell firmware.
I did 2 extended CMOS resets (turn off computer, take out power plug, press power on for a min, press clear cmos for a min, take battery out, leave overnight, put battery back in, turn on computer, load optimized settings). And I still have the memory scanner problem.
Since it is unlikely all 3 sticks of my RAM went faulty at the same time, I think maybe there is some kind of incompatibility issue between my RAM and the Gigabyte motherboard.
-
No problem, I told you I would test for you, and I always do when promised!!
Can you test with an actual PS/2 keyboard, that way there isn't any USB items connected. I know it should be PS/2 with the adapter, but best to try with actual just in case.
Other than that, I'd say please try to find or borrow another single stick of memory to test with, or buy a cheap set of 2x2GB, you can always use them as spares or keep for backup. You can probably find a set of 2x2GB for less than $30, I saw a set of 8GB kingstons for $15 shipped the other day!
Which exact kit do you have? Please link or give the model #, I'll look around and see if I can find any known issues.
-
I have this RAM:
F3-12800CL9T-6GBNQ
http://www.gskill.com/products.php?index=110
-
Ahhh! Not that kit again! :o ;D
I got into a big huff with G.Skill over this a while back over those, so I'll only drop a few threads on you without saying anything personally (There are more, but these are the larger ones)
http://forums.tweaktown.com/gigabyte/39003-x58a-ud3r-missing-memory-only-1600mhz-29.html
http://forums.tweaktown.com/gigabyte/36659-ga-x58a-ud7-official-thread-33.html#post362574
Please try to find some other sticks to test with, even if you can only borrow a single stick, that way you'll at least be able to find out if your memory is causing this issue.
-
OOh OK, didn't know there were issues with that RAM! I'm thinking of buying some 4 x 8gb RAM, any idea which brand and model will play nice with my X58A-UD7? The only brands with reasonable prices are GSkill or Corsair...
Sorry for the slow replies, have been busy with stuff other than troubleshooting my computer :)
-
I highly suggest sticking with kits of 3 on X58!! And ideally only use as much memory as you actually need, to avoid issues.
I would suggest a 3x2GB kit really, but if you must have 12GB go with 3x4GB. No worries about slow replies! I'm often busy and don't get to reply until it's late myself, so I know what you mean!
-
I read on the manual, that is is OK to use kits of 2 or 4, on this motherboard. It will just work in double channel instead of triple channel. Is that correct?
The reason I'm thinking of buying a kit of 4, rather than kit of 3, is for upgrade considerations. It looks like all future Intel chipsets will be using double or quad channel RAM. For example, LGA 2011 is using quad channel, and Ivy Bridge will be double channel. When I upgrade the motherboard and CPU later, it will be nice if I can transfer my RAM to the new platform, which a kit of 3 won't!
-
By the way, just letting you know, I did another quick test on the Marvell firmware. I confirm it DOES permanently change parts of the Gigabyte BIOS which the main Gigabyte BIOS does not cover when flashed.
For example, I did "go -e" (to erase the Marvell firmware). It deleted the 7 sections. Then my computer can't boot anymore, problems with both IDE and AHCI devices. Reflashed the main Gigabyte BIOS, same problem (which shows the main Gigabyte BIOS doesn't include all the IDE and AHCI bios stuff). I had to flash back the Marvell firmware with "go" to get it working again.
Anyway, since you can't reproduce my problem, I guess we have to leave it at that, until another person experiences the same things as I do :)
-
Yes, you can use dual channel if you want, but a kit of four is an add configuration as well. I would go with a 2x4GB kit, unless you absolutely need more than 8GB.
The issue you experienced with erasing the Marvell Firmware causes the board to stall looking for that controller, as it's enabled by default, so that may be why it doesn't work properly for you until you fix it. It just flashes or erases the full or sectioned parts of the Marvell firmware, nothing to do with the Gigabyte BIOS or IDE/AHCI controllers in the Gigabyte BIOS, but the lack of firmware in the Marvell controller likely does cause issue since the BIOS would be looking to load that ROM and Firmware at the same time or before the normal other hard drive controller.
I think your issue will be fixed with other memory, unless something else is causing your slow memory scan. I tested with two different kits that day I tested, no memory scan issues or anything else as you can see in the video. Go with 8GB or 6GB/12GB, you can always sell the 6GB/12GB kit if you want to go dual or quad in the future, or use 4GB/8GB of that and keep one as spare
-
Finally, what are the best image, flasher and parameters to upgrade the Marvell 88SE9128 chipset?
I tried to flash the latest found at station-drivers from a bootable USB but it doesn't do anything, I guess it doesn't recognize the chipset.
I have a Gygabyte GA-X58-UD3R motherboard.
Regards