New Abit IP35 Pro with lots of problems

Vogon · 20 Sep 2007 at 09:28

Also try setting the memory timing in the bios to T2, not T1 or auto.

Teaf · 20 Sep 2007 at 09:30

fornowagain said:
AWDFLASH.EXE M629B_11.BIN /py /sn /Wb /cd /cp /cc /CKS

Just wanted to ask about that, forgive my thread intrusion

Is there any reason you use the /Wb option? Just when I downloaded a new BIOS ready for my IP35 Pro coming I noticed that you're recommended options for AwdFlash are different to what Abit have in their runme batch file. Just curious really if it's definetly needed and if it's safe to use, as I'm not sure what it does even with the screeny

garywork · 20 Sep 2007 at 10:28

The /wb worked wonders for me

the abit batch file looks like the styandard one theyve had forever - it really needs updating

i'd go with what fornowagain says - it also does a checksum on the bin file
which the standard abit doesnt

poor show on them not to update it really

i edited the abit batch file in notepad to the above and ran it normally

then you have to check the ram and clock speed are right and your sorted

Muntyness · 20 Sep 2007 at 13:22

Well I've updated the BIOS and still I cant use 4 sticks. Plus I couldn't get through to Abit tech support this morning. :rolleyes:

As far as the memory goes, I tried running them at 2.2v, with the timings set to 5-5-5-18-T2. I also tried 5-5-5-15-T2. Neither setting worked.

Well whatever. I've got Windows installed now, and if worst comes to worst, I can order a new motherboard later in the year and install the extra RAM then. (Though I hope it doesn't come to that.)

Meanwhile I'm going to install programs until the tech line opens, and then I'll try getting through to them again.

split · 20 Sep 2007 at 13:30

Muntyness said:
Well I've updated the BIOS and still I cant use 4 sticks. Plus I couldn't get through to Abit tech support this morning.

As far as the memory goes, I tried running them at 2.2v, with the timings set to 5-5-5-18-T2. I also tried 5-5-5-15-T2. Neither setting worked.

Well whatever. I've got Windows installed now, and if worst comes to worst, I can order a new motherboard later in the year and install the extra RAM then. (Though I hope it doesn't come to that.)

Meanwhile I'm going to install programs until the tech line opens, and then I'll try getting through to them again.

Have you tried memtest yet?
If you do get through it will prolly be the first thing they ask you to do.

fornowagain · 20 Sep 2007 at 13:45

flibby said:
Just wanted to ask about that, forgive my thread intrusion Is there any reason you use the /Wb option? Just when I downloaded a new BIOS ready for my IP35 Pro coming I noticed that you're recommended options for AwdFlash are different to what Abit have in their runme batch file. Just curious really if it's definetly needed and if it's safe to use, as I'm not sure what it does even with the screeny

They don't include a couple of switches they should tbh. The boot block is a small ROM segment that initialises the board and checks the bios is correct before it boots it. Really should be updated along with the new bios. Things like the straps are stored there, so yes flash it. The string also flushes the old bios and checks the integrity. The idea is to get rid of any remnants of the old bios.

Teaf · 20 Sep 2007 at 14:31

Excellent, thanks fornowagain / garywork, will make sure I included you switches you specified in a different post when I flash my board (when I get it, *shakes fist at Parcelfarce*).

Vogon · 20 Sep 2007 at 15:42

I wouldn't be suprised if the problem was the ballixstix (so close sounding to my opinion of them

) After my experiences I wouldn't touch them personally.
Lets hope the bios flash cures it for you

BUFF · 21 Sep 2007 at 11:17

fornowagain said:
They don't include a couple of switches they should tbh. The boot block is a small ROM segment that initialises the board and checks the bios is correct before it boots it. Really should be updated along with the new bios.

not updating it gives you a recovery option though in the event of a failed flash so there is method in their madness

.

fornowagain · 21 Sep 2007 at 14:25

RE: Award bios, personally for repairs and general OCing problems, using it has solved far more problems than it ever caused. Recently had an early board that wouldn't recognise G0 chips without an updated bootblock. Over the years, failed flashes et al (excluding soldered bios boards 'persuaded' to bootblock recover, just hotswap em). Typically the initial bootblock checksum for the floppy call is intact, not that I'd use it given a choice. Its a hell of a lot easier to hotswap the chips, I wish they'd stop soldering them, even top end boards they've started soldering PLCC again :mad:

One for the search engine, lots of good info here for modifing and recovering bios' in case anyones ever looking.

http://www.rebelshavenforum.com/sis...orum;f=52;hardset=0;start_point=0;DaysPrune=0

BUFF · 21 Sep 2007 at 18:29

fornowagain said:
RE: Award bios, personally for repairs and general OC, using it has solved far more problems than it ever caused. Recently had a board that wouldn't recognise G0 chips without an updated bootblock. Over the years, failed flashes et al (excluding soldered bios boards 'persuaded' to bootblock recover, just hotswap em). Typically the initial bootblock checksum for the floppy call is intact, not that I'd use it given a choice.

Nobody chooses to use it

but it often works to recover the BIOS from a failed flash.
http://pages.sbcglobal.net/jefn/bootblock.html

Its a hell of a lot easier to hotswap the chips, I wish they'd stop soldering them, even top end boards they've started soldering PLCC again

so far abit have resisted doing so but still use socketed BIOS chips - their X38 mobos appear to be continuing in this.

fornowagain · 21 Sep 2007 at 19:20

BUFF said:
Nobody chooses to use it but it often works to recover the BIOS from a failed flash.

As I said, if its socket mounted you have a choice. Hotswap and reflash, beg/buy a new chip, bribe someone with EEPROM burner or try recover.

As for recovery, in my experience more often than not, it doesn't. Boards a brick. This ones an old service trick, on the odd repair I've resorted to forcing a checksum error by blocking the bios microcode on the PLCC. Dunno about 'nobody', but my choice is always the trusty hotswap, which does work and is a lot quicker.

Again for reference. If you have a dead board, don't have another to hotswap and fancy a gamble. Look up the pinouts on the PLCC (this one is the common W39V080), short the write enable to address pin (can be any one of them, A10's a start) as the board POSTS, forces a checksum error, give a few beeps (clear the short!) then loads the bios from the floppy.

BUFF said:
so far abit have resisted doing so but still use socketed BIOS chips - their X38 mobos appear to be continuing in this.

Well I wish Asus would do likewise. Come on, how much is a PLCC socket mount compared to a £190 board?

Tbh, I'm not so sure about any method to their madness. What I find really funny is that Abit aren't even consistent. Every time anyone uses the default settings on Flashmenu (assuming they're brave enough to use it) they flash the bootblock, lol.