• USB ports dead on reboot, requires power cord unplug

    From VanguardLH@21:1/5 to All on Thu Aug 22 09:55:41 2024
    XPost: alt.comp.hardware.pc-homebuilt

    While the following issue seems a hardware issue, I included the Win10 newsgroup in a cross-post to cull expertise from there, too. Lots of
    Win10 users also understand the hardware.

    When I restart Windows (reboot the PC), the USB mouse and keyboard are
    dead. They were okay before the restart (warm reboot), but unusable
    after. This isn't a Windows problem per se since the keyboard is also
    dead during the POST when I try to enter the BIOS system password, so,
    for example, I cannot hit F2 to go into the BIOS screens. Windows
    hasn't loaded yet. It is a hardware problem with the USB ports. While
    I leave my desktop PC powered 24x7, sometimes I have to shutdown, like
    for a Windows update (KB5041580 & KB5042352 done yesterday). To resolve
    the dead USB keyboard and mouse, and after shutting down, I had to
    unplug the power cord for a few seconds, plug it back in, and then tap
    the Power button to start up to get the USB keyboard working again.

    I have the BIOS configured to require a password on boot. This is an
    added deterrent to unauthorized access to my desktop PC. It also
    guarantees that any reboot of the computer won't start unless I'm at the computer. I hate unattended and unexpected reboots, like from Windows
    updates that will, with the Home edition, install an update, and then
    reboot just because the WU client thinks my PC is idle during off-hours
    (there really are no off hours since my computer use is irregular for
    when I'm using it).

    The restart is not a full cold power boot when the USB keyboard is non-functional. This is for a Windows shutdown, or a 4-sec hold on the
    Power button. I'm not in a low-power state, or [hybrid] hibernate
    state. To most users, this would be a power-off state. However, the
    power cord is still connected which means the 5 V standby power is still
    active from the ATX power supply to power the mobo's power-up logic.
    When the desktop PC is powered off, *and* the power cord yanked, is when
    there is a full cold boot: no power to the PSU, so it cannot supply any
    power, like for the 5VSB line to the mobo. It really is fully off, and
    will do a full cold boot.

    This is a new problem. New as in newly experienced. Since I leave my
    desktop PC powered 24x7, then problem started between whenever I
    previously power cycled my PC until yesterday to accommodate a Windows
    update. Keyboard was dead, so I couldn't enter the boot-time password
    to then load Windows. Holding the Power switch to force a power down
    (which, as noted above, is not a full power disconnect) didn't help.
    Had to yank the power cord, wait, plug back in, and then power up to get
    the USB keyboard working again.

    While there was a Windows update which required a Windows restart (aka
    warm reboot), I can't see how that would cause this problem. Windows
    isn't even starting to load on a reboot when the BIOS password prompt
    appears. Not even the POST screen has yet appeared when the BIOS
    password prompt appears. The USB keyboard and mouse have worked before
    during a warm reboot, so this showed up since whenever was my prior
    reboot which was many weeks ago. Before yesterday the USB keyboard and
    mouse would work on a warm reboot, like letting me go into the BIOS
    config, or to enter the BIOS password at the prompt.

    I did try using a different keyboard: the one I was using just prior to replacing it. Didn't like the feel and bounciness of the prior
    keyboard's keys (Kensington), so got a better keyboard (Dell). Old and
    new USB keyboards didn't work. Swapped to a new USB mouse, too, since
    its primary button's switch was bouncing (somemtimes effecting multiple clicks), and I already needed to replace it, but that didn't help. Both
    USB keyboard and USB mouse were dead on a warm reboot, but work on a
    full cold reboot (yanking and plugging back in the power cord).

    Why would USB ports become unresponsive on a warm reboot that were
    working before? Why would yanking the power cord, so the PSU cannot
    even supply 5VSB to the mobo's power-on logic, get the USB ports working
    again?

    In the past, I thought a cold boot would have the CPU (or is it the
    BIOS?) issue a reset signal to all connected devices to start them in a
    known state. That meant I should see the keyboard's LEDs flash when it
    got sent a reset. With this new problem, I don't see the keyboard LEDs
    flash on a cold boot. I see the Numlock LED come on, but that's because
    the BIOS is configured to turn on NumLock on startup.

    The USB keyboard and USB mouse are not plugged into a USB hub. They are plugged into backpanel USB ports attached to the motherboard. All the backpanel USB ports are 3.1 gen 2.

    This mobo does have a PS/2 combo port for mouse and keyboard, but I
    haven't had a PS/2 keyboard for many years. PS/2 is interrupt driven,
    so some gamers prefer it for response speed which is faster than the
    polling hardware protocol used for USB ports, and N-key rollover is more
    robust for PS/2, but again not needed by me (I don't need to press 6
    keys at the same time). I'd have to get USB/PS2 combo mice and
    keyboards to use on the PS/2 port since the devices would need to have
    the hardware protocol conversion built in (a passive adapter won't
    convert a USB device to a PS2 device), or get dedicated PS2-only input
    devices. I have so many USB ports in this rig that I'm unconcerned
    about losing the use of the PS/2 port. All the backpanel USB ports are
    USB 3.1 gen 2. The only USB 2.0 ports are for a drive bay USB hub that connects to a USB2 header on the mobo. I don't want my keyboard and
    mouse cords running to the front of the case to use the drive bay USB
    hub. For a desktop PC, I don't want cordless mice and keyboards. I've
    too often ran into problems inputting when the device's battery ends up
    to low for the device to be reliable, and wireless makes little sense
    for a computer and input devices that never move.

    It's a pain to plug and replug the power cord on a warm reboot. I don't realize it is needed until I warm reboot to get the BIOS prompt to enter
    a password. Oh yeah, unplug, wait a few seconds, plug back in, and then
    tap the Power switch to start booting. This is a new procedure
    requiring a cold (hard) reboot, and a cumbersome and interfering one.

    Remember that this cannot be a Windows problem, because Windows hasn't
    even a glimmer of code running yet. The PC reboots, the BIOS version
    appears, and the computer waits at the BIOS password prompt. Not even
    the POST screen has yet appeared.

    In the BIOS settings, there are the following:

    - USB keyboard/remote power on
    - USB mouse power on

    Those are disabled, by default, and I don't recall ever changing those.
    I don't want the PC waking up between I or someone else happened to
    press a key or accidentally bumped the mouse. My PC is left powered
    24x7. No low-power modes. No hibernate. No reason to have the
    keyboard or mouse wake a computer that should already be awake, and if I
    power off then I want it to stay that way until I press the Power
    button.

    There is a "legacy USB support" which, I think by default, is enabled.
    I thought that was to ensure PS/2 input devices were usable, but the
    help says "Enable or disable Legacy OS support for USB 2.0 devices".
    Whatever is its setting, it's been that way for maybe 4 years, or more,
    for this build.

    I do *NOT* use Fast Boot. That can make it impossible to get into BIOS settings, because the interval is miniscule when I can hit F2, and the
    BIOS may not see me rapidly tapping F2, so it continues loading the OS.
    Fast Boot also precludes booting from a USB storage device. As the
    mobo's manual states, "Fast mode will boot so fast that the only way to
    enter this UEFI Setup Utility is to Clear CMOS or run the Restart to
    UEFI utility in Windows." No thanks. Don't need it. Don't want that.

    I haven't touched UEFI/BIOS settings in a very long time, and I don't
    see any settings that would disable the USB ports on a warm boot versus
    them enabled for a cold boot (a full cold boot where the power cord has
    been unplugged).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Big Al@21:1/5 to VanguardLH on Thu Aug 22 11:34:00 2024
    XPost: alt.comp.hardware.pc-homebuilt

    On 8/22/24 10:55 AM, VanguardLH wrote:
    While the following issue seems a hardware issue, I included the Win10 newsgroup in a cross-post to cull expertise from there, too. Lots of
    Win10 users also understand the hardware.

    When I restart Windows (reboot the PC), the USB mouse and keyboard are
    dead. They were okay before the restart (warm reboot), but unusable
    after. This isn't a Windows problem per se since the keyboard is also
    dead during the POST when I try to enter the BIOS system password, so,
    for example, I cannot hit F2 to go into the BIOS screens. Windows
    hasn't loaded yet. It is a hardware problem with the USB ports. While
    I leave my desktop PC powered 24x7, sometimes I have to shutdown, like
    for a Windows update (KB5041580 & KB5042352 done yesterday). To resolve
    the dead USB keyboard and mouse, and after shutting down, I had to
    unplug the power cord for a few seconds, plug it back in, and then tap
    the Power button to start up to get the USB keyboard working again.

    I have the BIOS configured to require a password on boot. This is an
    added deterrent to unauthorized access to my desktop PC. It also
    guarantees that any reboot of the computer won't start unless I'm at the computer. I hate unattended and unexpected reboots, like from Windows updates that will, with the Home edition, install an update, and then
    reboot just because the WU client thinks my PC is idle during off-hours (there really are no off hours since my computer use is irregular for
    when I'm using it).

    The restart is not a full cold power boot when the USB keyboard is non-functional. This is for a Windows shutdown, or a 4-sec hold on the
    Power button. I'm not in a low-power state, or [hybrid] hibernate
    state. To most users, this would be a power-off state. However, the
    power cord is still connected which means the 5 V standby power is still active from the ATX power supply to power the mobo's power-up logic.
    When the desktop PC is powered off, *and* the power cord yanked, is when there is a full cold boot: no power to the PSU, so it cannot supply any power, like for the 5VSB line to the mobo. It really is fully off, and
    will do a full cold boot.

    This is a new problem. New as in newly experienced. Since I leave my desktop PC powered 24x7, then problem started between whenever I
    previously power cycled my PC until yesterday to accommodate a Windows update. Keyboard was dead, so I couldn't enter the boot-time password
    to then load Windows. Holding the Power switch to force a power down
    (which, as noted above, is not a full power disconnect) didn't help.
    Had to yank the power cord, wait, plug back in, and then power up to get
    the USB keyboard working again.

    While there was a Windows update which required a Windows restart (aka
    warm reboot), I can't see how that would cause this problem. Windows
    isn't even starting to load on a reboot when the BIOS password prompt appears. Not even the POST screen has yet appeared when the BIOS
    password prompt appears. The USB keyboard and mouse have worked before during a warm reboot, so this showed up since whenever was my prior
    reboot which was many weeks ago. Before yesterday the USB keyboard and
    mouse would work on a warm reboot, like letting me go into the BIOS
    config, or to enter the BIOS password at the prompt.

    I did try using a different keyboard: the one I was using just prior to replacing it. Didn't like the feel and bounciness of the prior
    keyboard's keys (Kensington), so got a better keyboard (Dell). Old and
    new USB keyboards didn't work. Swapped to a new USB mouse, too, since
    its primary button's switch was bouncing (somemtimes effecting multiple clicks), and I already needed to replace it, but that didn't help. Both
    USB keyboard and USB mouse were dead on a warm reboot, but work on a
    full cold reboot (yanking and plugging back in the power cord).

    Why would USB ports become unresponsive on a warm reboot that were
    working before? Why would yanking the power cord, so the PSU cannot
    even supply 5VSB to the mobo's power-on logic, get the USB ports working again?

    In the past, I thought a cold boot would have the CPU (or is it the
    BIOS?) issue a reset signal to all connected devices to start them in a
    known state. That meant I should see the keyboard's LEDs flash when it
    got sent a reset. With this new problem, I don't see the keyboard LEDs
    flash on a cold boot. I see the Numlock LED come on, but that's because
    the BIOS is configured to turn on NumLock on startup.

    The USB keyboard and USB mouse are not plugged into a USB hub. They are plugged into backpanel USB ports attached to the motherboard. All the backpanel USB ports are 3.1 gen 2.

    This mobo does have a PS/2 combo port for mouse and keyboard, but I
    haven't had a PS/2 keyboard for many years. PS/2 is interrupt driven,
    so some gamers prefer it for response speed which is faster than the
    polling hardware protocol used for USB ports, and N-key rollover is more robust for PS/2, but again not needed by me (I don't need to press 6
    keys at the same time). I'd have to get USB/PS2 combo mice and
    keyboards to use on the PS/2 port since the devices would need to have
    the hardware protocol conversion built in (a passive adapter won't
    convert a USB device to a PS2 device), or get dedicated PS2-only input devices. I have so many USB ports in this rig that I'm unconcerned
    about losing the use of the PS/2 port. All the backpanel USB ports are
    USB 3.1 gen 2. The only USB 2.0 ports are for a drive bay USB hub that connects to a USB2 header on the mobo. I don't want my keyboard and
    mouse cords running to the front of the case to use the drive bay USB
    hub. For a desktop PC, I don't want cordless mice and keyboards. I've
    too often ran into problems inputting when the device's battery ends up
    to low for the device to be reliable, and wireless makes little sense
    for a computer and input devices that never move.

    It's a pain to plug and replug the power cord on a warm reboot. I don't realize it is needed until I warm reboot to get the BIOS prompt to enter
    a password. Oh yeah, unplug, wait a few seconds, plug back in, and then
    tap the Power switch to start booting. This is a new procedure
    requiring a cold (hard) reboot, and a cumbersome and interfering one.

    Remember that this cannot be a Windows problem, because Windows hasn't
    even a glimmer of code running yet. The PC reboots, the BIOS version appears, and the computer waits at the BIOS password prompt. Not even
    the POST screen has yet appeared.

    In the BIOS settings, there are the following:

    - USB keyboard/remote power on
    - USB mouse power on

    Those are disabled, by default, and I don't recall ever changing those.
    I don't want the PC waking up between I or someone else happened to
    press a key or accidentally bumped the mouse. My PC is left powered
    24x7. No low-power modes. No hibernate. No reason to have the
    keyboard or mouse wake a computer that should already be awake, and if I power off then I want it to stay that way until I press the Power
    button.

    There is a "legacy USB support" which, I think by default, is enabled.
    I thought that was to ensure PS/2 input devices were usable, but the
    help says "Enable or disable Legacy OS support for USB 2.0 devices".
    Whatever is its setting, it's been that way for maybe 4 years, or more,
    for this build.

    I do *NOT* use Fast Boot. That can make it impossible to get into BIOS settings, because the interval is miniscule when I can hit F2, and the
    BIOS may not see me rapidly tapping F2, so it continues loading the OS.
    Fast Boot also precludes booting from a USB storage device. As the
    mobo's manual states, "Fast mode will boot so fast that the only way to
    enter this UEFI Setup Utility is to Clear CMOS or run the Restart to
    UEFI utility in Windows." No thanks. Don't need it. Don't want that.

    I haven't touched UEFI/BIOS settings in a very long time, and I don't
    see any settings that would disable the USB ports on a warm boot versus
    them enabled for a cold boot (a full cold boot where the power cord has
    been unplugged).
    As much as you would hate it, a bios reset to defaults just might fix it. Probably a 1 in 100
    chance but....
    --
    Linux Mint 21.3, Cinnamon 6.0.4, Kernel 5.15.0-119-generic
    Al

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to VanguardLH on Fri Aug 23 03:27:55 2024
    XPost: alt.comp.hardware.pc-homebuilt

    On Thu, 8/22/2024 10:55 AM, VanguardLH wrote:
    While the following issue seems a hardware issue, I included the Win10 newsgroup in a cross-post to cull expertise from there, too. Lots of
    Win10 users also understand the hardware.

    When I restart Windows (reboot the PC), the USB mouse and keyboard are
    dead. They were okay before the restart (warm reboot), but unusable
    after. This isn't a Windows problem per se since the keyboard is also
    dead during the POST when I try to enter the BIOS system password, so,
    for example, I cannot hit F2 to go into the BIOS screens. Windows
    hasn't loaded yet. It is a hardware problem with the USB ports. While
    I leave my desktop PC powered 24x7, sometimes I have to shutdown, like
    for a Windows update (KB5041580 & KB5042352 done yesterday). To resolve
    the dead USB keyboard and mouse, and after shutting down, I had to
    unplug the power cord for a few seconds, plug it back in, and then tap
    the Power button to start up to get the USB keyboard working again.

    I have the BIOS configured to require a password on boot. This is an
    added deterrent to unauthorized access to my desktop PC. It also
    guarantees that any reboot of the computer won't start unless I'm at the computer. I hate unattended and unexpected reboots, like from Windows updates that will, with the Home edition, install an update, and then
    reboot just because the WU client thinks my PC is idle during off-hours (there really are no off hours since my computer use is irregular for
    when I'm using it).

    The restart is not a full cold power boot when the USB keyboard is non-functional. This is for a Windows shutdown, or a 4-sec hold on the
    Power button. I'm not in a low-power state, or [hybrid] hibernate
    state. To most users, this would be a power-off state. However, the
    power cord is still connected which means the 5 V standby power is still active from the ATX power supply to power the mobo's power-up logic.
    When the desktop PC is powered off, *and* the power cord yanked, is when there is a full cold boot: no power to the PSU, so it cannot supply any power, like for the 5VSB line to the mobo. It really is fully off, and
    will do a full cold boot.

    This is a new problem. New as in newly experienced. Since I leave my desktop PC powered 24x7, then problem started between whenever I
    previously power cycled my PC until yesterday to accommodate a Windows update. Keyboard was dead, so I couldn't enter the boot-time password
    to then load Windows. Holding the Power switch to force a power down
    (which, as noted above, is not a full power disconnect) didn't help.
    Had to yank the power cord, wait, plug back in, and then power up to get
    the USB keyboard working again.

    While there was a Windows update which required a Windows restart (aka
    warm reboot), I can't see how that would cause this problem. Windows
    isn't even starting to load on a reboot when the BIOS password prompt appears. Not even the POST screen has yet appeared when the BIOS
    password prompt appears. The USB keyboard and mouse have worked before during a warm reboot, so this showed up since whenever was my prior
    reboot which was many weeks ago. Before yesterday the USB keyboard and
    mouse would work on a warm reboot, like letting me go into the BIOS
    config, or to enter the BIOS password at the prompt.

    I did try using a different keyboard: the one I was using just prior to replacing it. Didn't like the feel and bounciness of the prior
    keyboard's keys (Kensington), so got a better keyboard (Dell). Old and
    new USB keyboards didn't work. Swapped to a new USB mouse, too, since
    its primary button's switch was bouncing (somemtimes effecting multiple clicks), and I already needed to replace it, but that didn't help. Both
    USB keyboard and USB mouse were dead on a warm reboot, but work on a
    full cold reboot (yanking and plugging back in the power cord).

    Why would USB ports become unresponsive on a warm reboot that were
    working before? Why would yanking the power cord, so the PSU cannot
    even supply 5VSB to the mobo's power-on logic, get the USB ports working again?

    In the past, I thought a cold boot would have the CPU (or is it the
    BIOS?) issue a reset signal to all connected devices to start them in a
    known state. That meant I should see the keyboard's LEDs flash when it
    got sent a reset. With this new problem, I don't see the keyboard LEDs
    flash on a cold boot. I see the Numlock LED come on, but that's because
    the BIOS is configured to turn on NumLock on startup.

    The USB keyboard and USB mouse are not plugged into a USB hub. They are plugged into backpanel USB ports attached to the motherboard. All the backpanel USB ports are 3.1 gen 2.

    This mobo does have a PS/2 combo port for mouse and keyboard, but I
    haven't had a PS/2 keyboard for many years. PS/2 is interrupt driven,
    so some gamers prefer it for response speed which is faster than the
    polling hardware protocol used for USB ports, and N-key rollover is more robust for PS/2, but again not needed by me (I don't need to press 6
    keys at the same time). I'd have to get USB/PS2 combo mice and
    keyboards to use on the PS/2 port since the devices would need to have
    the hardware protocol conversion built in (a passive adapter won't
    convert a USB device to a PS2 device), or get dedicated PS2-only input devices. I have so many USB ports in this rig that I'm unconcerned
    about losing the use of the PS/2 port. All the backpanel USB ports are
    USB 3.1 gen 2. The only USB 2.0 ports are for a drive bay USB hub that connects to a USB2 header on the mobo. I don't want my keyboard and
    mouse cords running to the front of the case to use the drive bay USB
    hub. For a desktop PC, I don't want cordless mice and keyboards. I've
    too often ran into problems inputting when the device's battery ends up
    to low for the device to be reliable, and wireless makes little sense
    for a computer and input devices that never move.

    It's a pain to plug and replug the power cord on a warm reboot. I don't realize it is needed until I warm reboot to get the BIOS prompt to enter
    a password. Oh yeah, unplug, wait a few seconds, plug back in, and then
    tap the Power switch to start booting. This is a new procedure
    requiring a cold (hard) reboot, and a cumbersome and interfering one.

    Remember that this cannot be a Windows problem, because Windows hasn't
    even a glimmer of code running yet. The PC reboots, the BIOS version appears, and the computer waits at the BIOS password prompt. Not even
    the POST screen has yet appeared.

    In the BIOS settings, there are the following:

    - USB keyboard/remote power on
    - USB mouse power on

    Those are disabled, by default, and I don't recall ever changing those.
    I don't want the PC waking up between I or someone else happened to
    press a key or accidentally bumped the mouse. My PC is left powered
    24x7. No low-power modes. No hibernate. No reason to have the
    keyboard or mouse wake a computer that should already be awake, and if I power off then I want it to stay that way until I press the Power
    button.

    There is a "legacy USB support" which, I think by default, is enabled.
    I thought that was to ensure PS/2 input devices were usable, but the
    help says "Enable or disable Legacy OS support for USB 2.0 devices".
    Whatever is its setting, it's been that way for maybe 4 years, or more,
    for this build.

    I do *NOT* use Fast Boot. That can make it impossible to get into BIOS settings, because the interval is miniscule when I can hit F2, and the
    BIOS may not see me rapidly tapping F2, so it continues loading the OS.
    Fast Boot also precludes booting from a USB storage device. As the
    mobo's manual states, "Fast mode will boot so fast that the only way to
    enter this UEFI Setup Utility is to Clear CMOS or run the Restart to
    UEFI utility in Windows." No thanks. Don't need it. Don't want that.

    I haven't touched UEFI/BIOS settings in a very long time, and I don't
    see any settings that would disable the USB ports on a warm boot versus
    them enabled for a cold boot (a full cold boot where the power cord has
    been unplugged).


    I'm not aware of any thorough articles on "USB states" or "what
    happens to USB port logic blocks during shutdown or similar non-running states".

    I can find SI4501DY (MOSFET pairs) labeled with "backfeed_cut" on a reference schematic. This might manage to prevent powered USB hubs from dumping 5V
    into a PC when the PC is shut off. There is no suggestion in the schematic
    that these controls are used individually for USB port control.

    There is at least one AMD-based design, where they require a cold reboot
    for a change in USB port enable-ment from BIOS level. Using the control
    in the BIOS, saving settings, then booting right into an OS, results
    in no change in USB port status. So even state-bit-control, appears to be
    of the "one-chance-per-boot-cycle" kind of control. But this is control
    via some USB logic block, whereas fiddling the power path could also be
    used for a result.

    Linux has the ability to "eject" even USB mass storage devices, in such
    a way they cannot be "used" on a subsequent warm boot. You can certainly
    unplug and replug the device, and it is then detect-able and usable again.
    You can also lock the tray on a DVD drive, and even an alternate OS booting right after that, it cannot get the tray open :-/ The button on the front
    does not work either.

    Generally speaking, it's all pretty mysterious, and thanks to search engines today, I can't find *anything* remotely documentary on the topic. I don't
    know whether shoveling a collection of 500 page documents into myself, is
    going to result in an aha moment. USB.org is not going to be helpful in
    putting together a story about "available states devs can use".

    Someone did manage to lose their ports during Windows Update, due to
    something USB driver related. But this was a few years back now.

    https://answers.microsoft.com/en-us/windows/forum/all/all-usb-ports-are-disabled-as-windows-starts-to/41b93c4a-678e-4b4b-8d46-e91087691a9f

    https://support.microsoft.com/en-us/topic/usb-devices-may-stop-working-after-installing-the-february-13-2018-update-kb4074588-8623ea82-98a0-ad8d-5766-5428a6ff7ee7

    USB ports can also be affected by GPO in Enterprise, so pouring epoxy
    in the USB ports isn't the only solution for lockdown.

    As to your opinion about PS/2, PS/2 is an example of a "port that works".
    it works when USB has its knickers in a knot. If you have any vestige
    of it left, it is certainly worth your while to buy any necessary
    adapter so you can use it. I think right now, only one motherboard
    here does not have PS/2, and it was a board bought for powering
    experiments, rather than as a daily driver. Right now, I just set up
    a computer where the back of the motherboard is exposed, and I can
    now stick a finger on the back of the VCore area and get some idea
    how hot the thing is getting.

    [Home project diversion...]

    https://c1.neweggimages.com/ProductImageCompressAll1280/11-854-069-V03.jpg

    ( https://www.newegg.com/black-phanteks-enthoo-pro-atx-full-tower/p/N82E16811854069 )

    [Example of PS/2 wiring information -- mobo user manual may not have confirmation pinout diagram... ]

    http://www.burtonsys.com/PS2_keyboard_and_mouse_mini-DIN-6_connector_pinouts.html

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to Paul on Fri Aug 23 15:09:53 2024
    XPost: alt.comp.hardware.pc-homebuilt

    Paul <nospam@needed.invalid> wrote:

    Linux has the ability to "eject" even USB mass storage devices, in such
    a way they cannot be "used" on a subsequent warm boot. You can certainly unplug and replug the device, and it is then detect-able and usable again.

    The dead USB ports are before any OS loads. On a power cycle (power
    cord left connected), I've tried removing and replugging the USB
    keyboard and USB mouse while sitting at the BIOS prompt for a password,
    but they're still dead. I now have to power down, unplug the power
    cord, wait, replug the power cord, and then power up. This is new
    behavior as of maybe within the last month.

    Not too long ago, like maybe a month, we had a power outage. Yet after
    power was restored, and on power up of the PC, the USB keyboard and USB
    mouse worked. So this problem started since then. The PC is normally
    up 24x7 with no power-saving or hibernate modes, so the only time I need
    a warm reboot is for a Windows or program/driver update. But now a warm
    reboot results in dead USB keyboard and mouse. Instead I have to
    shutdown, unplug and replug the power cord, and then power up. Weird.

    Someone did manage to lose their ports during Windows Update, due to something USB driver related. But this was a few years back now.

    That would be after Windows loaded. The dead USB ports occur before the
    OS load, and even before the POST screen appears. I'm at the BIOS
    password prompt, but the USB keyboard is dead. I'm stuck at the
    password prompt until I power down, unplug and replug the power cord,
    and startup again.

    If the dead USB ports after a Windows update were when the OS loads,
    yeah, I'd look at the updates to see how they might've fucked the USB
    ports. More likely I'd restore from an image backup before the update,
    and wait a month, or more, for Microsoft to fix their fix.

    As for NKRO (N-key rollover) for USB versus PS/2 keyboards, looks like
    that is no longer an argument. For example, the Corsair K100 mechanical
    USB keyboard specs state "Full key (NKRO) with 100% anti-ghosting", but
    does "full" mean all 104 keys, or just 10, or 6, or WHAT? How the hell
    could anyone with 10 fingers, and even adding 10 toes, a nose, and a
    stiffy member press 104 keys at once? I suspect "full NKRO" actually
    means 6KRO (6-key rollover).

    https://www.thekeyboardco.com/blog/index.php/2016/03/what-is-nkro-our-guide-to-rollover-anti-ghosting-and-choosing-the-right-keyboard/

    As to your opinion about PS/2, PS/2 is an example of a "port that works".
    it works when USB has its knickers in a knot. If you have any vestige
    of it left, it is certainly worth your while to buy any necessary
    adapter so you can use it.

    A passive adapter won't change a USB keyboard or mouse into a PS/2
    keyboard or mouse. A hardware converter is needed. Way to expensive to
    buy a separate hardware protocol adapter. Instead you buy a keyboard or
    mouse with the converter built-in, and use the passive adapter to
    physcially adapt between USB connector to PS/2 port. The number of
    USB+PS2 keyboards and mice is dwindling which also limits your choices
    for features.

    Gamer mobos, or really old ones, is about how you nowadays get the PS/2
    port. PS/2 is just a wee bit faster on response than the polling for
    USB. At one time, PS/2 also has a bigger N-key rollover than USB; i.e.,
    you can press more keys at once assuming you can contort your fingers
    that much while coordinating 2 hands on the keyboard.

    https://www.devever.net/~hl/usbnkro

    There still might be a limit for the matrix handling with membrane
    keyboards versus switch keyboards. For example, you might be able to simultaneous press and register the ASDFGHJKL keys, but AZX only
    registers 2 of 3 keys. The construction of the PCB key matrix and the controller dictate if there are exclusions to what is the claimed NKRO
    for a keyboard.

    http://web.archive.org/web/20101117204841/http://geekhack.org/showwiki.php?title=NKey+Rollover+-+Overview+Testing+Methodology+and+Results
    (14-year old archived forum article)

    I had a Rosewill mechanical keyboard, but suffered irrepable physical
    damage. After several years of pounding on it, I broke it, and couldn't
    put some keycaps back on. I don't have it anymore to test. Deciding to
    go cheaper to replace more often (buy a Timex to replace cheaply instead
    of getting a Rolex), I got a Dell KB522 multimedia keyboard. I tested
    the Dell at:

    https://www.mechanical-keyboard.org/key-rollover-test/

    The USB keyboard supports 6KRO. I did not test all possible 6-key
    combinations to see if its PCB matrix or controller didn't handle some
    6-key combos. I did notice 6KRO didn't work with the number keys in the
    top row in the middle section, but worked using the numpad number keys.
    The F-keys also didn't support 6KRO.

    So, I'll have to amend my damnation of USB keyboards to remove the NKRO limitation (robustness depends on the design of the keyboard), and only
    remark hereafter that gamers like PS/2 keyboards better due to faster
    response in handling interrupts instead of incurring USB polling delays.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to Mr. Man-wai Chang on Fri Sep 6 14:36:36 2024
    XPost: alt.comp.hardware.pc-homebuilt

    "Mr. Man-wai Chang" <toylet.toylet@gmail.com> wrote:

    VanguardLH wrote:

    While the following issue seems a hardware issue, I included the
    Win10 newsgroup in a cross-post to cull expertise from there, too.
    Lots of Win10 users also understand the hardware.

    When I restart Windows (reboot the PC), the USB mouse and keyboard
    are dead. They were okay before the restart (warm reboot), but
    unusable after. This isn't a Windows problem per se since the
    keyboard is also dead during the POST when I try to enter the BIOS
    system password, so, for example, I cannot hit F2 to go into the
    BIOS screens. Windows hasn't loaded yet. It is a hardware problem
    with the USB ports. While I leave my desktop PC powered 24x7,
    sometimes I have to shutdown ...

    Shouldn't you have listed the hardware specification of your desktop
    PC?

    A USB keyboard or USB mouse is just another HID device. Even if it has
    extra hardware buttons, those require ancilliary software which is
    irrelevant at the POST screen when trying to get into the BIOS settings
    since the OS hasn't yet loaded to load the ancilliary/macro software.
    I've tried different keyboards and mice with no effect. Multimedia
    keyboards have some pre-defined registry entries, but that's after
    Windows loads to also load its registry. Any ancilliary software
    (macros) to support additional buttons is also loaded after Windows
    loads. This problem occurs before any OS loads, like when trying to hit
    F2 or Del to get into the BIOS settings at the POST screen.

    All USB ports on the desktop PC are USB 3.1. The ones into which the
    USB keyboard and USB mouse are plugged into are next to the PS/2 port,
    and are USB 3.1 Gen1 type A ports.

    Mobo is Asrock Z390 Taichi. 64 GB system RAM. You can find the mobo
    specs at https://www.asrock.com/mb/Intel/Z390%20Taichi/index.asp if you
    really need that level of hardware detail, but I doubt it. After a
    couple months of setting up, I haven't touched the BIOS settings. No
    need to alter BIOS settings after it's all setup.

    CPU is Intel i7 8700 Coffee Lake although I don't see that as relevant.
    The CPU issues a reset signal to all devices on a cold boot, and has
    done so for CPUs dating way over 2 decades ago. This was an April 2019 own-built desktop. No overclocking, and no overvolting. I prefer
    stability over miniscule performance gain.

    As noted, this was not a problem before, only within the last month, so
    this setup worked for about 5 years before this symptom appeared.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)