Just an idea but instead of having your BIOS set to auto detect your drive as per default try setting it so the HD is permanently set. If that doesn't help then it sounds like your HD isn't spinning up fast enough.
Hello All,
any one had seen the problem before - what am I doing wrong?
Carputer config
------------------
VIA EPIA EN15000 (BIOS 1.07), 2.5" SATA Seagate 80G, M2-ATX
same behaviour observed with 2.5" IDE drives
Ignition on (no jumpers, C, B, same effect)
-------------------------------------------
In 5 seconds, motherboard starts and boots
HDD is not detected
After pressing RESET, works fine. Windows shuts down normally on POWER
When using common ATX power supply, works normally
Boots on POWER, HDD detected
Which unavoidably leads to following conclusions:
1. M2-ATX is capable of driving setup and it works okay (after RESET)
2. Problem only happens on cold boot
3. Works rock solid stable with any other power unit
4. Jumpers do not seem to affect
5. It is not HDD related
Any one hit the situation before ?
Thanks in advance.
Will contract for C++/Win-Linux/PIC jobs
Just an idea but instead of having your BIOS set to auto detect your drive as per default try setting it so the HD is permanently set. If that doesn't help then it sounds like your HD isn't spinning up fast enough.
Visit my site V8 Scimitar
SP13000, 300GB SATA HD, 1GB DDR. Opus 150, K301 screen, Cisco WIFI, AQmax GPS, RoadRunner and FreeDrive, Sony MEX-R5 head unit. 4 years installed and it just keeps running!
I just bought mine and installed it today and i am having the same problem.
I am running a Jetway 1.5 MB, 512 Ram, 3.5" 120gb ide HDD, DVD Rom, Voom PC Case.
IDE detect timeout BIOS setting would be nice but it is not there in 1.07;
setting delay by means of non-quick boot and lan boot wont help.
it can be something i misunderstood about power unit itself.
Will contract for C++/Win-Linux/PIC jobs
As we noticed, motherboard gets powered up on ignition.
This is not an expected behavior.
Why motherboard getting powered on ignition ? Can it be a PIC bug,
motherboard protocol change that M2-ATX does not understand ?
Or I simply connected it improperly, small simple stupid problem
laying on the surface that I can not see yet ?
Will contract for C++/Win-Linux/PIC jobs
Same coldboot non-detection behaviour observed with following setup:
M2-ATX
flexATX (VIA Chipset) Samuel C3
So this may be result of some incompatiblity or power ramp.
We will very much appreciate any help and/or guidance how to fix.
Will contract for C++/Win-Linux/PIC jobs
Got my new board and it has the same problem. Anymore help will be appriecated. Thanks
This has been my problem since inception. Mine is a Jetway 1.5, 1gig, dvdrom and 2.5HDD. I plan to fix the problem with an opus PS. The M2 is a piece of ultimate crap.
Thank you for the reply. Please do not jump into conclusions yet.
Looking forward for fix and help of manufacturer.
Will contract for C++/Win-Linux/PIC jobs
Bookmarks