Originally posted by: rizorith
But in the end my main problem is I can't make any bios changes and I figure that should supercede everything else.
Originally posted by: mindless1
Originally posted by: rizorith
But in the end my main problem is I can't make any bios changes and I figure that should supercede everything else.
You have E8400, is that on their supported CPU list? They have a v16 beta bios out now that's supposed to improve E8400 support, you might as well try it, what do you have to lose?
http://forum.abit-usa.com/showthread.php?t=122393
Also, leave only one memory module in for the time being till the issues are resolved and clear CMOS with AC power disconnected after flashing the bios. If flashing in dos, use the /wb switch to write a new boot block.
Originally posted by: rizorith
Originally posted by: mindless1
Originally posted by: rizorith
But in the end my main problem is I can't make any bios changes and I figure that should supercede everything else.
You have E8400, is that on their supported CPU list? They have a v16 beta bios out now that's supposed to improve E8400 support, you might as well try it, what do you have to lose?
http://forum.abit-usa.com/showthread.php?t=122393
Also, leave only one memory module in for the time being till the issues are resolved and clear CMOS with AC power disconnected after flashing the bios. If flashing in dos, use the /wb switch to write a new boot block.
Considering nothing is saved on the bios i think it's reasonable that the bios flash will fail and i'll be left with a board i can't RMA. I would try the flash but no one has addressed this issue and I don't know much about it - just using some logic here.
Anyways, this board is pretty annoying in general. The double boot issue seems to be resolved for only some people with newer version. Even the latest bios has double boot issues for some people.
Originally posted by: kalster
I got my board y'day, very impressed, easy overclock of my e660 to 3.2ghz, i had a couple of questions though
my board came with 11 firmware, i used flashmenu to flash to latest but it froze during the verifying stage. I restarted but it would not turn on, so i reset the cmos and it boots back up, the version shows 15, how can i ensure that it froze after it had done flashing the bios
why does the jmicron controller take so long to recognize my pata hdd and dvd drive, any way to shorten this duration, it takes at least 10 seconds to go past that screen
i still have the double posting issue, kinda annoying but I can live with it
Originally posted by: kalster
I got my board y'day, very impressed, easy overclock of my e660 to 3.2ghz, i had a couple of questions though
my board came with 11 firmware, i used flashmenu to flash to latest but it froze during the verifying stage. I restarted but it would not turn on, so i reset the cmos and it boots back up, the version shows 15, how can i ensure that it froze after it had done flashing the bios
why does the jmicron controller take so long to recognize my pata hdd and dvd drive, any way to shorten this duration, it takes at least 10 seconds to go past that screen
i still have the double posting issue, kinda annoying but I can live with it
Originally posted by: mindless1
Originally posted by: kalster
I got my board y'day, very impressed, easy overclock of my e660 to 3.2ghz, i had a couple of questions though
my board came with 11 firmware, i used flashmenu to flash to latest but it froze during the verifying stage. I restarted but it would not turn on, so i reset the cmos and it boots back up, the version shows 15, how can i ensure that it froze after it had done flashing the bios
why does the jmicron controller take so long to recognize my pata hdd and dvd drive, any way to shorten this duration, it takes at least 10 seconds to go past that screen
i still have the double posting issue, kinda annoying but I can live with it
As you have seen, it is generally better not to ever use the Windows flasher unless it's truely required (which is rare). The board will boot a USB flash drive, to plain DOS, that is probably the safest way all around to do it. Yes Windows flashing can work a lot of the time but there isn't usually any good reason to do it, and increases the odds of failure by quite a lot vs doing so in plain DOS.
Since it initialized and POSTed without displaying a checksum error and waiting, every time, odds are very high you have the whole bios flashed, intact. All that really remains is whether you left the /wb switch enabled with the windows flasher so you flashed the boot block, and that when you cleared CMOS you did so with AC power disconnected. If you wanted to be doubly sure you could now boot plain dos and flash v15 again but it seems more like reassurance than necessity.
I was not aware that 16 beta bios did actually do anything more to resolve double-boot issues, can anyone who had ran v15 confirm that there is some new change related to it?
I suspect the lengthly detection for HDD and DVD is because of the DVD, I have a PATA HDD and it only pauses for roughly 3-4 seconds. Is it really a problem? The board does support and seems to function fine using hibernation and S3 suspend state if you need quicker boots, but then hibernation still pauses a little longer than it could due to the JMicron controller. Thank Intel for that, deciding to cut a tiny bit of southbridge cost for themselves and rob us of PATA support because it's not forward looking enough for the elite who throw out all their legacy hardware.
You could use a PCI or PCIe PATA controller card instead, non-RAID type or mode with it for use with ATAPI (DVD) drive, but it would also have a little bit of a hesitation during the boot process. The other solution is abandon PATA drives, it is not likely JMicron's bios module can be signficantly changed by them to shorten the process much so there's nothing Abit can do except allow you to disable the controller entirely.
Originally posted by: Heidfirst
what are you going to use for audio (onboard or discrete sound card)?
The mobo has optical SPDIF out & a SPDIF header on the PCB for connecting to a video card that supports it.
is your gfx card capable of using the SPDIF header?Originally posted by: WEW
I want to use the onboard - but how would i connect it to the tv or my home theater panasonic receiver.
Originally posted by: Heidfirst
what are you going to use for audio (onboard or discrete sound card)?
The mobo has optical SPDIF out & a SPDIF header on the PCB for connecting to a video card that supports it.
Originally posted by: lightfoot3b
I don't know if you missed my first post but I've tried two tested and working power supplies, one ultra (which works great in the other system I've had it in) and an antec (also worked great in another system) and I DON'T have memory in it since I don't get bios beeps but yes, I did try my crucial ballistix and OCZ stuff too. No change. I'm going to try my e2160 in a friends (also new) abit ip35-e this weekend with his psu and v-card and see if it goes. If it does rma'ing the mb. I was hoping someone would have some idea on the starting-stopping-starting and then just sitting there. Thanks for the tips.
Originally posted by: agent2099
Guys would this be a good budget overclockable setup?
ABIT IP35-E LGA 775 Intel P35 ATX Intel Motherboard - Retail
Intel Pentium E2160 Allendale 1.8GHz 1MB L2 Cache LGA 775 65W Dual-Core Processor - Retail
Crucial Ballistix 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory - Retail