Main > Main Forum
Weird issue involving my ipac - please help! *SOLVED*
leapinlew:
I'm having an issue with my PS2 ipac and computer that I can only describe as weird. 9 times out of 10 it doesn't register keystrokes and neither does the keyboard pass through once it gets in game. I'm able to get into the Bios using the F2 key, but once it boots into Mala... nothing. If I exit Mala (using a USB keyboard and mouse), windows doesn't report any errors. If I open the notepad - still nothing from the ipac or the pass through. Here is what I've done so far:
1. Hooked iPac to a different computer. No issues. Keyboard passthrough worked fine. Loaded winipac utility and keypresses registered as normal. For kicks, I restored all the defaults but I don't think it changed anything since it was a new ipac I just started using a few hours ago.
2. Hooked ipac to my computer and it doesn't register keystrokes either through the CP or through a passthrough keyboard.
3. I started thinking it was a physical issue with my PS2 keyboard port on the mobo, so I changed the motherboard out with a brand new one (I had some spares). Same issue. It seems that something happens when windows loads up? I don't know... 1 out of 10 boots and it'll work as normal.
I'm running out of ideas. Any thoughts?
Gatt:
I never thought I'd type this again after Windows XP released but...
This sounds to me like an IRQ issue. Sounds to me like the introduction of the Ipac and/or just your PS2 port is somehow ending up in conflict with some other piece of hardware.
I suppose it's also possible it's a driver issue with the PS2 port.
Either way, control panel -> Device Manager, and start searching through there to see if there's an issue (The view tab will let you switch between device types and resources), check the PS2 port entry under device types, and then, if necessary, start tracing the IRQ's in resources to see if the PS2 port and something else are fighting over the same IRQ. I really wouldn't be surprised if some sound-card-type-thing is grabbing the IRQ, used to be that sound caused all kinds of problems with IRQ's and hardware.
Let us know.
*When the system powers on, it starts with a limited set of resources, when Windows boots it adds all kinds of extra hardware like sound and video cards, so it's possible that system is hardwiring the PS2 port to IRQ X and then Windows is going "Ah hell, who uses PS2 ports today? We'll put the sound chip on that IRQ, there's no way there'll be a problem!". So you get a PS2 that works on power-on but fails when Windows boots.
leapinlew:
--- Quote from: Gatt on April 02, 2010, 04:31:22 am ---I never thought I'd type this again after Windows XP released but...
This sounds to me like an IRQ issue. Sounds to me like the introduction of the Ipac and/or just your PS2 port is somehow ending up in conflict with some other piece of hardware.
I suppose it's also possible it's a driver issue with the PS2 port.
Either way, control panel -> Device Manager, and start searching through there to see if there's an issue (The view tab will let you switch between device types and resources), check the PS2 port entry under device types, and then, if necessary, start tracing the IRQ's in resources to see if the PS2 port and something else are fighting over the same IRQ. I really wouldn't be surprised if some sound-card-type-thing is grabbing the IRQ, used to be that sound caused all kinds of problems with IRQ's and hardware.
Let us know.
*When the system powers on, it starts with a limited set of resources, when Windows boots it adds all kinds of extra hardware like sound and video cards, so it's possible that system is hardwiring the PS2 port to IRQ X and then Windows is going "Ah hell, who uses PS2 ports today? We'll put the sound chip on that IRQ, there's no way there'll be a problem!". So you get a PS2 that works on power-on but fails when Windows boots.
--- End quote ---
I'm very familiar with IRQ issues. I did peek at the device manager, but didn't spend much time there. I will now. Thanks for your suggestion - sounds promising.
I also have a PCI add-in card to add PS2 ports. I'm going to drop that in and see how it goes. Thanks.
leapinlew:
It's not an IRQ issue... this thing is driving me crazy!
I've tried the following:
Unplugged everything from the ipac except the pass through keyboard
A different mobo
PCI addin card with a PS2 port (keyboard works, but pass through on ipac doesn't)
A different PS2 cable
reloading the OS
A different ipac from a known working machine. (which really sucked to take apart)
I mean... what esle can I try?
I'm using a Intel Atom chip and Tiny XP. I've used this same setup before.
leapinlew:
Another hint....
Remember how I said it works 1 out of 10 times? Well, I can get it to work everytime if I go into the BIOS and change a setting in the BIOS. For example, if I go into the bios and change anything it works.
I went to Intels site and got the latest bios upgrade. Upgraded it successfully, and it still has the same issue of not working unless I go into the bios and make a change. Does this make sense to anyone?
Navigation
[0] Message Index
[#] Next page
Go to full version