Sapphire A9RD580 Bug/Issues/Fixed

*shrug*
youre impressed huh, no :banana::banana::banana::banana:! im getting tired of mb with lots of issues (939dual, a8r-mvp), thats why i got this board! yeah some issues with it originaly but the ami bios should take care of that, but noo. My dvd-drive doesnt even WORK on this board. whats that all about?

Where can i get a hold of that 8mb chip? maybe that original bios could make some thing better...?

btw; i like them too :)

Edit: is this correct:

AMIBIOS
Version 08.00.12
Build: 04/28/06
ID: PRMT_B15

?

That is the one. I would have to agree with Marlowe and suggest a reflash. It should not have cold boot issues.

edit: chip can be had at badflash.com
edit2: are you able to try the dvd drive again on another machine? And does windoze report the drive as working on your Manta?

yeah i suppose i can flash it again. @ 275htt i can turn off the system and then turn it on again. but @300 i have to clear cmos to get it to boot. havent checked exactly where the limit is though.

Windoze? if you mean if the drive is found in "my computer"? then yes. but it wont read the cd. so the logo doesnt change either. just the standard dvd-rom logo...

edit: restart always works fine...

ok, reflashed the bios, lest se if it starts this time....

Edit: nope, nothings changed....

*shrug*
i cant jump straight to 300 either. i tried the nec drive again but i wont work.
lowerer the htt to 200 for the ocasion(?) and when i pumped it up to 300 again it wouldnt boot. have to do 250first then 300...

So just to be sure....

In bios at the Advanced tab, under Hyper Transport Config:

NB HT Link Width is set to Auto or 16bit
RD580 HT Drive Strength is set to Optimal
HT Receiver Comp Ctrl is set to Optimal
RD580 HT PLL Control is set to High Speed


Also for your DVD drive what I meant by Windoze was in Device Manager is it showing it as working properly?

Edit: When you re-flashed did you set bios back to default first?

check for everything! (including edit)

As for the nec, when i tried it again system rebooted instantly the moment i got into windows so i dont know...

will try it in another machine to check that its ok...

This is all i do in bios, this is how my system is running right now:

1. set time date
2. Disable floppy everywhere
3. Prosessor FID to 9x
4. Prosessor VID to 1,35
5. Cpu\ht to 250
6. Memclockmode to Force
7. Memclock value 133
8. Mct timing to manually (though didnt change anything at this speed)
9. Userconfig to manually
10. Read preample to 7
11. Async latency to 9
12. Dram voltage to 2.7
13. All the hyper transport things(800\16\optimal\optimal\high speed)
14. Boot priority
15. Save and exit, and into bios again
16. Change HTT to 300
17. save\exit\boot....

thats all!

ok some good news... kinda.

Cant get my nec drive to work on the other machine too. going to rma it.
Wonder what happend to it?

Try this and report back (make sure you are on the AMI bios and it's flashed correctly)

1) Turn off power
2) Clear cmos
3) Turn on power and start up the system
4) enter cmos menu
5) press F9 to load optimal defaults
6) set fid to x8
7) set vid to 1.35
8) set htt to 300
9) memclock mode to manual and set 100 or 133 (try both if the first one you try fails)
10) dram voltage to 2.7V or whatever the sticks run at
11) HT 1GHz/16/optimal/optimal/high speed
12) HT voltage to 1.3V

Don't touch anything else and try to boot directly to 300 FSB. If this works, then either the memory or CPU isn't stable for some reason. If it doesn't work try the same sequence (start from the beginning again) but with HT settings of 800 MHz/16/optimal/optimal/high speed. This has worked on every Xpress3200 Manta system that I can think of but we never played with Opterons too much.

Report back what your results are. The point here is to try and isolate the problem of not being able to go directly to 300HTT. Once you figure that out, then you can start tweaking out your ram and CPU. Even fall back to one memory stick and try it if you have no luck. We have seen memory "holes" at certain speeds. Sometimes memory runs too slow and will cause strange things the same is true if it runs too fast (obviously).

Quote:

---

Originally Posted by eXa

This is all i do in bios, this is how my system is running right now:

1. set time date
2. Disable floppy everywhere
3. Prosessor FID to 9x
4. Prosessor VID to 1,35
5. Cpu\ht to 250
6. Memclockmode to Force
7. Memclock value 133
8. Mct timing to manually (though didnt change anything at this speed)
9. Userconfig to manually
10. Read preample to 7
11. Async latency to 9
12. Dram voltage to 2.7
13. All the hyper transport things(800\16\optimal\optimal\high speed)
14. Boot priority
15. Save and exit, and into bios again
16. Change HTT to 300
17. save\exit\boot....

thats all!

---

@ Grayskull.....
Could the not being able to boot at 300HTT be related to his cold boot issues?

If the board doesn't cold boot everytime at default settings then something else is wrong.

Quote:

---

Originally Posted by markr

@ Grayskull.....
Could the not being able to boot at 300HTT be related to his cold boot issues?

---

ok, results from initial testing.

did exactely as you said, 1.time, booted and got into bios again but system froze(klock not counting or anything) 2.time, froze @ quiet mode enabled, 3.time, froze in bios again.
4.time, tried 800ht but nothing happened after save&exit. turned the power off and tried booting but nothing happend. just like before... clear cmos.

some more testing.

nb 1,22
ht link 1,3 = no go

nb 1,3
ht link 1,3 = boot but frezes quickly.

nb 1,3 with smal noisy fan
ht link 1,3 = frezes but not quite so fast

nb 1,4 with the fan
ht 1,3 = as we speak!

everything is exactely as you said. exept when i got it working i entered bios again and changed time and boot priority.

Btw: HOLY SH**! :eek:
just figured out why the temp skyrocketed when i got past 1,4v. Somehow i twisted things in my brain and figured that the voltage offset was in 0.02 an so on, not 0.2. So i didnt push 1,43v but 1,7v :confused: scary...

Man i can se those asus folks sitting there... "i told you so, 1,45 max!"
(ref; all asus\asrock boards)

ok a bit more results. tried changing from 8x to 9x. system booted fine and stuff but was unstable. now i have upped the voltage to 1,375 too and it semes fine for now.

Also tried 133 divider on ram (with 8x) but nothing happened after save&exit.

Edit: no wait... wasnt stable. lowered the ht to 800. will se if its stable now!

Edit2:800 semed to do the trick. now ill have to se if i can lower the NB voltage to 1,3 again and remove the fan....

Edit3: lowered the voltage to 1,3 and removed the fan. stable for now. will report back if something happends.

Can you cold boot now with a CMOS clear?

without, Yes. cold boot\warm boot. seemes to boot everytime.
Everytime i have changed something now i have turned the computer off instead
of using restart and it boots!

edit: im guessing its memory related, only using 100divider now. 133 didnt seemed to work the one time i tested. but i havent tested much ram things yet.

just to sum it up.

optimal defaults
Fid 9x
Vid 1,375
Htt 300
Memclock 100
Ram v 2.7 (just to be shure)
HT = 800\16\optimal\optimal\high speed
NB 1,3v no fan
HT link 1,3v

that is what im running right now. will stay so to tomorrow night if it aint something you want me to try first....

tried to get 133divider to work, but i cant.
no matter what i did nothing happened after save&exit.

Also tried doing what greyskull said only i also changed max async latency to 9 and read preample to 7 but nothing happened then too!

Need help to move on!

Tried with one dimm or different ram?

no havent touched the ram yet...

Sounds like the memory is giving problems now...time to tune it. I would first not touch the DDR Memory Drive Strength settings (Level 0-15) at first. First find the best DDR data drive strength setting (% reduced). Then start playing with the DDR Drive Strengths. I would suggest reducing the strengths to begin with one step at a time and go from there. Memtest can be used to get things going.

Please report back what settings you are using now that is stable (using the 100 MHz memory divider for now).

Quote:

---

Originally Posted by eXa

no havent touched the ram yet...

---

Use the ATI system manager...it is your friend and will tell what voltages you are running at...in case your brain has a lapse or you can't add. :) I use it all the time. :D

Quote:

---

Originally Posted by eXa

some more testing.

nb 1,22
ht link 1,3 = no go

nb 1,3
ht link 1,3 = boot but frezes quickly.

nb 1,3 with smal noisy fan
ht link 1,3 = frezes but not quite so fast

nb 1,4 with the fan
ht 1,3 = as we speak!

everything is exactely as you said. exept when i got it working i entered bios again and changed time and boot priority.

Btw: HOLY SH**! :eek:
just figured out why the temp skyrocketed when i got past 1,4v. Somehow i twisted things in my brain and figured that the voltage offset was in 0.02 an so on, not 0.2. So i didnt push 1,43v but 1,7v :confused: scary...

Man i can se those asus folks sitting there... "i told you so, 1,45 max!"
(ref; all asus\asrock boards)

---

ok. will report back in next week probably since ill be gone over the weekend.

Grayskull could you give a brief description of P/Nmos drive strengths and how it relates to O/Cing please?