| Main > Main Forum |
| Weird issue involving my ipac - please help! *SOLVED* |
| << < (2/2) |
| Gatt:
--- Quote from: leapinlew on April 03, 2010, 02:20:23 am ---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? --- End quote --- Now that is really, really, weird. Obviously, the board isn't initializing the PS2 port on a standard boot, but when you enter bios and change something, it's forcing it to revalidate everything and initializing the port. But why is this happening? I *really* can't think of any reason why it might do that. It's not an OS issue, can't be, it has to be an issue with the motherboard. Perhaps even the chipset. I'm not sure what motherboard you have though, so I can't really do any research. Sadly, I don't think you're getting around this one. It actually sounds slightly familiar, I had an Asus board that didn't like Razor mice, if I didn't click the mouse through the whole boot process, it wouldn't power it. The only remaining advice I have... 1. Tap a key through the whole boot process, see if it's powering down the Ps2 port on boot and an input stream forces it to keep it alive. 2. It's a real reach, and I think it's unlikely to work, but check and see if your motherboard manufacturer has drivers for the board itself. I really doubt this will solve the problem, but it's really the only other thing I can think of. Edit: WAIT! Idea! Power management! Atoms are supposed to be lower power chips, so their motherboards should be designed to cut power to anything they can. One other thing I can think of, try disabling power management(ACPI I think it's still called?) in the bios and XP's power management features. It's within the realm of possibility that power management could be at fault. |
| leapinlew:
--- Quote from: Gatt on April 03, 2010, 05:13:58 am --- --- Quote from: leapinlew on April 03, 2010, 02:20:23 am ---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? --- End quote --- Now that is really, really, weird. Obviously, the board isn't initializing the PS2 port on a standard boot, but when you enter bios and change something, it's forcing it to revalidate everything and initializing the port. But why is this happening? I *really* can't think of any reason why it might do that. It's not an OS issue, can't be, it has to be an issue with the motherboard. Perhaps even the chipset. I'm not sure what motherboard you have though, so I can't really do any research. Sadly, I don't think you're getting around this one. It actually sounds slightly familiar, I had an Asus board that didn't like Razor mice, if I didn't click the mouse through the whole boot process, it wouldn't power it. The only remaining advice I have... 1. Tap a key through the whole boot process, see if it's powering down the Ps2 port on boot and an input stream forces it to keep it alive. 2. It's a real reach, and I think it's unlikely to work, but check and see if your motherboard manufacturer has drivers for the board itself. I really doubt this will solve the problem, but it's really the only other thing I can think of. Edit: WAIT! Idea! Power management! Atoms are supposed to be lower power chips, so their motherboards should be designed to cut power to anything they can. One other thing I can think of, try disabling power management(ACPI I think it's still called?) in the bios and XP's power management features. It's within the realm of possibility that power management could be at fault. --- End quote --- GATT! Great idea - how'd you know? I didn't have ACPI in the BIOS to disable, but if I did - I bet it would've worked. I took your suggestion and disabled ACPI in Windows XP using these steps: * Right click on My Computer * Choose Properties * Click the Hardware tab * Choose Device Manager * Double click on Computer. You will see Advanced Configuration And Power Interface (ACPI) PC * Double Click on the ACPI reference * Click the Driver tab * Click Update Driver * Click Next * Choose 'Display a list of the known drivers for this device so that I can choose a specific driver' * Click Next * Choose 'Show all hardware of this device class' * Select Standard PC * Click Next. Windows will display a warning message. Ignore it and click Yes i.e. you want to install the driver despite Microsoft's warning not to do so * Click Next. Windows will upgrade the driver. This takes a few seconds * Click Finish * Close the 'Upgrade Device Driver Wizard' window. Restart your computer when prompted * After restarting, return to the Device Manager and verify that your computer's configuration is now Standard PC and not ACPI That resolved the issue. Weird eh? I burned up a lot of time on this issue. Thanks so much for your help. I've posted the solution here just in case someone searching later finds this thread. |
| Gatt:
You're very welcome, glad to be of service! The Atom tipped me off. I was thinking about it, going into Bios reset something that permitted the PS2 port to be detected, so the port must be good and something must've been shutting it off. Which lead me to thinking about the architecture goals for the Atom, low-power consumption. ACPI was the root of my evil with my Razor Mouse, the Asus board would power it down, so it was possible that ACPI was to blame, especially since the design goals for Atom is to have minimal power consumption. Good idea to post this, wasn't that long ago that someone else had a similiar issue. I suspect as Atom's become more common the issue will be recurring. |
| Navigation |
| Message Index |
| Previous page |