Abit NF7-S
Hi,
I have really had bad luck with my Abit mobo's so far. When I bought my KT7A-Raid it was really unstable from start. Random lockups and stuff. After some weeks of playing, upgrading BIOSes, VIA divers and stuff I finally got it stable. It seemed that the Southbridge chipset was a bit buggy..
Well, this time I've got an Abit NF7-S v2.0 wich seemed to work just perfect out of the box and I was pretty astonished how easy it was to setup (compared to my last board) . But.. after installation of WinXP and some reboots later it seems that my keyboard and mouse locks up everytime I restart my computer from WinXP and boot it up again. I have to power-off my computer manually and boot it up again to get PS/2 functionality back..
Anyone else of you who got this strange symptom??!
I don't have any other stuff attached in the ports (USB/Firewire etc), but my PS2 mouse & keyboard.
// moOd
I have really had bad luck with my Abit mobo's so far. When I bought my KT7A-Raid it was really unstable from start. Random lockups and stuff. After some weeks of playing, upgrading BIOSes, VIA divers and stuff I finally got it stable. It seemed that the Southbridge chipset was a bit buggy..
Well, this time I've got an Abit NF7-S v2.0 wich seemed to work just perfect out of the box and I was pretty astonished how easy it was to setup (compared to my last board) . But.. after installation of WinXP and some reboots later it seems that my keyboard and mouse locks up everytime I restart my computer from WinXP and boot it up again. I have to power-off my computer manually and boot it up again to get PS/2 functionality back..
Anyone else of you who got this strange symptom??!
I don't have any other stuff attached in the ports (USB/Firewire etc), but my PS2 mouse & keyboard.
// moOd
0
Comments
Funny thing
8)
That is an undocumented feature of KBDPWR1 jumper located on the motherboard near those PS/2 slots.
1-2 (default): PS/2 keyboard/mouse uses 5V dual power. When the system is off, optical mouse LED keeps light, and wake-up by keyboard/mouse function enabled.
2-3: PS/2 keyboard/mouse uses VCC power. When the system is off, optical mouse LED goes out, but wake-up by keyboard/mouse function disabled.
As for the unlabeled jumper near the LAN/USB ports, it is to switch the USB power.
1-2 (default): USB device uses 5V dual power. When the system is off, optical mouse LED keeps light, and wake-up by keyboard/mouse function enabled.
2-3: USB device uses VCC power. When the system is off, optical mouse LED goes out, but wake-up by keyboard/mouse function disabled.
The one and only thing I did to get it working was disabling "Quick Power On Self Test" from BIOS.
Very strange I think, but it's definitively working!
Thanks for all your help & suggestions..
First one I RMA'd and the new board seems fine.
I then ordered a second . . . all way fine until a few days ago when it started doing the same crap the first board did. It is very irritating.
I'm going to try disabling quick POST. We'll see if it works for me too.
Uhmm..
Btw. Another thing that I did, just before the quick POST thing, was clearing CMOS.
After bootup to WinXP it found new hardware (don't know what it found tho, it didn't say).
I don't think this is a Windows related problem, because I had the exact same problem in MS DOS. A reboot with Ctrl+Alt+Del did not help.. I needed to power off my CPU or Reset it with the reset button to get my PS/2's working.
This is a very weird problem!
Did you:
1) Move the jumper and move it back
2) Move it, power on the system, turn off the system and move the jumper back?
3) Remove the battery?
So I get this exactly right: You cleared CMOS. Then on the next boot up you disabled quick POST?
Once you disabled quick POST did you save changes, exit and let it reboot, or did you power down the system after the changes were saved?
1) Shut down the computer
2) Clear CMOS by moving the jumper, power on the system, turn off the system and move the jumper back
3) Load optimized factory defaults in Bios
4) Disable the Quick POST in Bios
5) Save changes
6) Let it bootup in WinXP (without interrupting the memory check at the POST)
Another thing that I'm quite unsure about is if it also rearranged my IRQ's, because my system now uses IRQ's up to IRQ 20. I'm unsure if that was the case before, when it didn't work. That may be normal, I don't know. Havn't just seen it before in my old system (KT7A-Raid)!
I may be mistaken but I thought that could fry your mobo. Are you saying unplug the Power supply then hit power button to clear any left over garbage or with the power supply on?
I've done this many times on more than one board and never had one fry or elicit any unexpected behavior.
The NF7-S Rev2.0 board is already eliciting unexpected behavior, so the jumper issue would be a moot point on this board.
Same here, without any problems.. even if it's not recommended (i just read the manual!)
Optimized defaults.
Fail-safe defaults.
Oh well.
Have you tried to change the KBDPWR1 jumper on your mobo?
I fiddled with it before and I'm not sure in which position I left it..
I'll look up in the manual which one it is and give it a try.
Other than this I *LOVE* this board, but this is extremely annoying.
I then decided about the only thing I had not tried was plugging the keyboard into PS/2 port nearest the bottom of the motherboard and plugging the mouse into the other PS/2 port.
Guess what? I still doesn't work!
JUST KIDDING, IT DOES! It finally works.
Go figure. The mobo was smart enough to WORK FINE w/ the keyboard/mouse plugged in the other way upon an INITIAL BOOT or upon a RESET, but something about the RESTART makes the BIOS not detect that the keyboard and mouse are plugged into different ports.
Oh well. I guess I will *CLEARLY* label those ports on my backplate so as not to do this again. The backplate is marked, but it does not have the individual ports marked, it marks the PS/2 headers collectively as kbd/mouse.
Problem solved!
/me is happy.