Com Port Problems.
Apr. 15th, 2006 01:59 amI just went to use the COM ports on my new motherboard for the first time ever, and they don't seem to work. If I connect my router's serial cable to the main server, I can talk to it via minicom, so I know the cable is good and the router is talking. If I connect the same cable to THIS (my desktop machine), then I can't talk to it.
I've looked at the various Windows XP settings, and it claims the COM ports are working fine, but hyperterm doesn't get any response.
I even booted up into Gentoo and tried minicom, in case it was a windows configuration issue. Nothing.
The COM ports are an integral part of the motherboard. There are (AFAICT) no jumpers that might be misset, and no internal cables that might be loose.
Anyone have any ideas of some sort of way to diagnose this problem, other than taking my system into the shop?
---
EDIT: Problem Solved! Although I could find no evidence that it would help, I reflashed my BIOS with the latest version. The COM ports now work, and I can continue with my nefarious scheme!
EDIT2: It just stopped working! Now I'm REALLY puzzled as to what the problem might be.
EDIT III: Okay, it turns out that there are also bugs in hyperterm *headdesk* At least I seem to have it all working consistently now.
I've looked at the various Windows XP settings, and it claims the COM ports are working fine, but hyperterm doesn't get any response.
I even booted up into Gentoo and tried minicom, in case it was a windows configuration issue. Nothing.
The COM ports are an integral part of the motherboard. There are (AFAICT) no jumpers that might be misset, and no internal cables that might be loose.
Anyone have any ideas of some sort of way to diagnose this problem, other than taking my system into the shop?
---
EDIT: Problem Solved! Although I could find no evidence that it would help, I reflashed my BIOS with the latest version. The COM ports now work, and I can continue with my nefarious scheme!
EDIT2: It just stopped working! Now I'm REALLY puzzled as to what the problem might be.
EDIT III: Okay, it turns out that there are also bugs in hyperterm *headdesk* At least I seem to have it all working consistently now.