Lylat1an wrote on 2024-05-10, 04:30:

I also have a Tripp-Lite 0DT60002 USB to PS/2 converter for this build, but it's also USB 1.x.

what does that mean? Unicomp doesnt work with this adapter either?

Lylat1an wrote on 2024-05-10, 04:30:

My other USB keyboards seem to work with both devices without issue, so I'm guessing my new Unicomp model is USB 2.0

so was I right in Re: "USB keyboard support" not working on FIC (Iston) KA-6100 and you verified its USB .20 or is that still speculation?

Lylat1an wrote on 2024-05-10, 04:30:

USB 2.0, and thus its polling rate is too fast for both the motherboard and converter.

those are two different separate potential issues

rasz_pl wrote on 2024-05-10, 17:38:

Lylat1an wrote on 2024-05-10, 04:30:

I also have a Tripp-Lite 0DT60002 USB to PS/2 converter for this build, but it's also USB 1.x.

what does that mean? Unicomp doesnt work with this adapter either?

That is correct. And I apologize for being unclear, I wrote that just before going to bed after a long day.

rasz_pl wrote on 2024-05-10, 17:38:

Lylat1an wrote on 2024-05-10, 04:30:

My other USB keyboards seem to work with both devices without issue, so I'm guessing my new Unicomp model is USB 2.0

so was I right in Re: "USB keyboard support" not working on FIC (Iston) KA-6100 and you verified its USB .20 or is that still speculation?

I'm waiting to hear back from Unicomp on that one, but at this point I'm pretty sure it's 2.0.

rasz_pl wrote on 2024-05-10, 17:38:

Lylat1an wrote on 2024-05-10, 04:30:

USB 2.0, and thus its polling rate is too fast for both the motherboard and converter.

those are two different separate potential issues

I thought one explained the other. But now that you mention it, a 2.0 device should still work in a 1.x port, but not as fast right?

Lylat1an wrote on 2024-05-10, 19:28:

That is correct.

so there is something weird about it after all

Lylat1an wrote on 2024-05-10, 19:28:

I'm waiting to hear back from Unicomp on that one, but at this point I'm pretty sure it's 2.0.

so you still speculate, how bout you check instead https://www.thesycon.de/eng/usb_descriptordumper.shtml
https://tewarid.github.io/2016/12/12/view-usb … on-windows.html
Another way to test is connecting it thru old USB 1.1 hub.

Lylat1an wrote on 2024-05-10, 19:28:

I thought one explained the other. But now that you mention it, a 2.0 device should still work in a 1.x port, but not as fast right?

no, but I only ever saw gamer hid devices (keyboard/mice) being truly USB 2.0
beyond being USB 2.0, or having something weird in the descriptor (like aforementioned fast pooling rate) it can also use more elaborate messages. As I said in previous thread old Bioses (and old converters) can only care about the most basic HID messages and not understand fancier ones.

rasz_pl wrote on 2024-05-10, 22:50:

Lylat1an wrote on 2024-05-10, 19:28:

That is correct.

so there is something weird about it after all

Sure seems that way.

so you still speculate, how bout you check instead https://www.thesycon.de/eng/usb_descriptordumper.shtml https://tewarid.githu […]
Show full quote

Lylat1an wrote on 2024-05-10, 19:28:

I'm waiting to hear back from Unicomp on that one, but at this point I'm pretty sure it's 2.0.

so you still speculate, how bout you check instead https://www.thesycon.de/eng/usb_descriptordumper.shtml
https://tewarid.github.io/2016/12/12/view-usb … on-windows.html
Another way to test is connecting it thru old USB 1.1 hub.

Here are the results of the TDD dump from Windows 10: It appears to be USB 1.1 compliant...

1Information for device Aristides 2862 (VID=0x17F6 PID=0x2862):
2
3------------------------------
4Connection Information:
5------------------------------
6Device current bus speed: FullSpeed
7Device supports USB 1.1 specification
8Device supports USB 2.0 specification
9Device address: 0x0015
10Current configuration value: 0x01
11Number of open pipes: 1
12
13
14------------------------------
15Device Descriptor:
16------------------------------
170x12	bLength
180x01	bDescriptorType
190x0200	bcdUSB
200x00	bDeviceClass      
210x00	bDeviceSubClass   
220x00	bDeviceProtocol   
230x40	bMaxPacketSize0   (64 bytes)
240x17F6	idVendor
250x2862	idProduct
260x0100	bcdDevice
270x01	iManufacturer   "Unicomp GA LLC"
280x02	iProduct        "Aristides 2862"
290x03	iSerialNumber   "123456"
300x01	bNumConfigurations
31
32
33-------------------------
34Configuration Descriptor:
35-------------------------
360x09	bLength
370x02	bDescriptorType
380x0022	wTotalLength   (34 bytes)
390x01	bNumInterfaces
400x01	bConfigurationValue
410x00	iConfiguration
420xA0	bmAttributes   (Bus-powered Device, Remote-Wakeup)
430x32	bMaxPower      (100 mA)
44
45Interface Descriptor:
46------------------------------
470x09	bLength
480x04	bDescriptorType
490x00	bInterfaceNumber
500x00	bAlternateSetting
510x01	bNumEndPoints
520x03	bInterfaceClass      (Human Interface Device Class)
530x00	bInterfaceSubClass   
540x00	bInterfaceProtocol   
550x00	iInterface
56
57HID Descriptor:
58------------------------------
590x09	bLength
600x21	bDescriptorType

610x0111	bcdHID
620x00	bCountryCode
630x01	bNumDescriptors
640x22	bDescriptorType   (Report descriptor)
650x0043	bDescriptorLength
66
67Endpoint Descriptor:
68------------------------------
690x07	bLength
700x05	bDescriptorType
710x81	bEndpointAddress  (IN endpoint 1)
720x03	bmAttributes      (Transfer: Interrupt / Synch: None / Usage: Data)
730x0010	wMaxPacketSize    (1 x 16 bytes)
740x05	bInterval         (5 frames)
75
76Microsoft OS Descriptor is not available. Error code: 0x0000001F
77
78
79--------------------------------
80String Descriptor Table
81--------------------------------
82Index  LANGID  String
830x00   0x0000  0x0409 
840x01   0x0409  "Unicomp GA LLC"
850x02   0x0409  "Aristides 2862"
860x03   0x0409  "123456"
87
88------------------------------
89
90Connection path for device: 
91USB xHCI Compliant Host Controller
92Root Hub
93Aristides 2862 (VID=0x17F6 PID=0x2862) Port: 2
94
95Running on: Windows 10 or greater (Build Version 19045)
96
97Brought to you by TDD v2.17.0, Feb 23 2021, 14:04:02
98

It looks like it's missing a boot protocol interface, which is the simplified protocol designed specifically for BIOSes to be able to use keyboards and mice.

Im not an expert on USB, but 0x0010 wMaxPacketSize (1 x 16 bytes) suggests its not using the simplified USB keyboard protocol (8 bytes).