Just finished fixing this one. Apparently, this is a common issue with all Asus P5 series boards. I first assumed it's a bad BIOS flash or corrupt CMOS settings, as it would go away once after resetting CMOS, but upon the next reboot it would be there again. Same if i changed any BIOS settings and saved them.
I read that people have flashed BIOSes to no luck, and someone pointed towards a transistor on another (older) board, so i proceeded to look for a hardware issue. And i found it. See attachments for fix.
Instructions:
This should apply to *all* boards that exhibit this behavior, obviously the parts may be in a different location. Follow these directions to find it if your board differs:
The rest is the same as above.
I'm also going to tell you what causes the issue to appear in the first place in a follow-up post.
I read that people have flashed BIOSes to no luck, and someone pointed towards a transistor on another (older) board, so i proceeded to look for a hardware issue. And i found it. See attachments for fix.
Instructions:
- Follow directions in pictures
- Clear CMOS
- Power board up, redo all BIOS settings
- Be happy and have a cold one.
This should apply to *all* boards that exhibit this behavior, obviously the parts may be in a different location. Follow these directions to find it if your board differs:
- Remove jumper cap from chassis intrusion connector (if you're reading this, you already found it's of no use anyway).
- With the board powered ON, measure with your voltmeter and find the pin of the chassis intrusion switch connector that has somewhere between 1.7v and 3.3v on it.
- Disconnect board from PSU.
- Use continuity tester function of your DMM and probe on the SOT23 transistors next to the super IO controller, you should find it beeps on one of them.
- Power the board back ON and find a 3.3v supply nearby
- Power board OFF, remove transistor, solder drain connection (it's gonna be the single pad, just like it looks in the picture) to 3.3v supply.
The rest is the same as above.
I'm also going to tell you what causes the issue to appear in the first place in a follow-up post.
Comment