Bug reporting thread

[dufresnep]

Yeah... your os is working so fine that users begin to expect their USB keyboard to work out of the box, rather than on the PS/2 driver:
On linux:

The empty slots of the memory card reader:
root@debian:/home/paul# dmesg | grep /dev/sd?
grep: /dev/sdb: No medium found
grep: /dev/sdc: No medium found
grep: /dev/sdd: No medium found
grep: /dev/sde: No medium found

^C
paul@debian:~$ lsusb
Bus 008 Device 005: ID 058f:9380 Alcor Micro Corp. Flash Drive
Bus 008 Device 004: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 04f2:0760 Chicony Electronics Co., Ltd Acer KU-0760 Keyboard
Bus 003 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
paul@debian:~$

[admin]

Hello dufresnep,

Thanks for the report. From the log it looks like the keyboard is detected fine. And if the mouse is fine (looks like it's on the same controller) then the interrupts must be coming through. So this is on real hardware? I ask because you mentioned a virtual machine, and at least with VMware the keyboard is usually presented as a virtual PS2 device, even if your real keyboard is USB. I see that there are some errors there related to PS2 keyboard initialization.

Andy

[dufresnep]

Yes, it is real hardware.
There is an almost 1 min error looping in terminal before the graphical UI kicks in.

[andymc]

Yes, it is real hardware.
There is an almost 1 min error looping in terminal before the graphical UI kicks in.

Yeah sorry about the delay. I'm guessing that it's doing a bunch of retries on the SCSI slots of your card reader, and most of the time is spent rendering and scrolling the error messages.

Is it possible to test out some other USB keyboard on this machine (preferably one that happens to work with Visopsys on some other machine) and see whether it works on this machine? It would help to understand whether the problem the Visopsys code is having is because of the USB controller hardware in this machine, vs. the keyboard device itself.

[dufresnep]

Will test... I intend to disconnect the card reader to see if it eliminates the delay at the beginning.
Yes, I could also test a usb key, or some(s) other(s) keyboard(s).

BTW, I have tried on my Atom based laptop.
Working fine (I think the touchpad and keyboard is like PS/2 keyboard and mouse emulated).
But it mentioned 4 USB unknown devices, reported as being wireless devices.
I guess, it is internal wireless card... but unsure why it would happens 4 times with very minors differences.
So, network was not activated.
And when I do "ifconfig", it says malloc cannot allocate zero bytes (WindowConstruct).

Was trying to use "view" to view visoploader.log (or similar name), but realized that it was not showing because it is binary file (by icon type).
Still, I am a bit curious as why it is a binary file.

BTW, I am very impressed, as this small system supports AHCI (FreeDOS does not seems to do yet), and even seems to know abot BIOS tables (ACPI).

[dufresnep]

On my Quad core CPU:
I disconnected the card reader, and indeed the long delay is gone.

If I connect an other USB key at boot time, then I see it and the content during the live system.
Seems you cannot change the USB key during live mode and expects to see the change in computer window.

I tried an other USB keyboard (Microsoft) but was not seeing it either.
Connecting a PS/2 keyboard works fine.

Speaking of strange things users can do...
While I was having only the USB key on which visopsys is installed and no other drive...
I tried defrag (on the live system)... it told me it was mounted, and needed to be unmounted before defrag.
But once unmounted, defragmentation stop at the very beginning because some files was not found.
And euh... no files at all was found after that... I had to hard reboot.

[dufresnep]

Ok, I just booted with my ACER usb2 keyboard, no card reader, and I am including the specific part of kernel.log.

Aug 1 15:28:58 2019 USB: mouse human interface device 4:1 dev:0a4c, vend:15d9, class:03, sub:01 proto:02 usb:1.10
Aug 1 15:28:58 2019 USB: keyboard human interface device 4:2 dev:0760, vend:04f2, class:03, sub:01 proto:01 usb:2.0
Make me think if usb:2.0 is really supported.

Aug 1 15:28:59 2019 Error::kernelPs2KeyboardDriver.c:inPort60(119):
Aug 1 15:28:59 2019 Timeout reading port 60, port 64=16
Aug 1 15:28:59 2019 Error::kernelPs2KeyboardDriver.c:waitControllerReady(143):
Aug 1 15:28:59 2019 Controller not ready timeout, port 64=16
Aug 1 15:28:59 2019 Error::kernelPs2KeyboardDriver.c:waitControllerReady(143):
Aug 1 15:28:59 2019 Controller not ready timeout, port 64=16
Aug 1 15:28:59 2019 Error::kernelPs2KeyboardDriver.c:waitControllerReady(143):
Aug 1 15:28:59 2019 Controller not ready timeout, port 64=56
Aug 1 15:28:59 2019 Error::kernelPs2KeyboardDriver.c:inPort60(119):
Aug 1 15:28:59 2019 Timeout reading port 60, port 64=56
Aug 1 15:28:59 2019 Error::kernelPs2KeyboardDriver.c:waitControllerReady(143):
Aug 1 15:28:59 2019 Controller not ready timeout, port 64=56
Aug 1 15:28:59 2019 PS/2 keyboard device detected
Aug 1 15:28:59 2019 USB keyboard device detected
Hum, which criteria it used to say that it dtected PS/2 keyboard (just the USB ACER KU-0760 connected)?

Aug 1 15:28:59 2019 "Kingston DataTraveler 3.0" SCSI disk device detected
Other USB key well detected... this is *not* the one on which visopsys is booting from.

[andymc]

If I connect an other USB key at boot time, then I see it and the content during the live system.
Seems you cannot change the USB key during live mode and expects to see the change in computer window.

Hot (un-)plugging is supposed to work, in theory.

I tried an other USB keyboard (Microsoft) but was not seeing it either.

Hmm, well that's starting to point in the direction of the host controller driver, then. Not sure how to proceed really, as debugging something like that remotely can be very iterative, and right now I'm struggling for time.

Speaking of strange things users can do...
While I was having only the USB key on which visopsys is installed and no other drive...
I tried defrag (on the live system)... it told me it was mounted, and needed to be unmounted before defrag.
But once unmounted, defragmentation stop at the very beginning because some files was not found.
And euh... no files at all was found after that... I had to hard reboot.

Yeah, that should probably be something that you're not allowed to do

[andymc]

Aug 1 15:28:58 2019 USB: mouse human interface device 4:1 dev:0a4c, vend:15d9, class:03, sub:01 proto:02 usb:1.10
Aug 1 15:28:58 2019 USB: keyboard human interface device 4:2 dev:0760, vend:04f2, class:03, sub:01 proto:01 usb:2.0
Make me think if usb:2.0 is really supported.

USB 1, 2, and 3 are all supported generally speaking, but I'm not sure I've ever encountered a USB2 keyboard (or mouse) before. Most vendors don't seem to bother going higher than 1.1 for these (usually) low-speed devices. It's possible there's some incorrect assumption in the USB keyboard driver code.

Aug 1 15:28:59 2019 Error::kernelPs2KeyboardDriver.c:waitControllerReady(143):
Aug 1 15:28:59 2019 Controller not ready timeout, port 64=56
Aug 1 15:28:59 2019 PS/2 keyboard device detected
Aug 1 15:28:59 2019 USB keyboard device detected
Hum, which criteria it used to say that it dtected PS/2 keyboard (just the USB ACER KU-0760 connected)?

Well, PS2 keyboard is effectively always 'detected' in the sense that the controller is built into the PC motherboard. The error messages basically reflect the fact that it couldn't get a response from any actual device. I suppose with a bit of sophistication, the code could be made to report no keyboard in that case. OTOH, most people don't read the log file

Aug 1 15:28:59 2019 "Kingston DataTraveler 3.0" SCSI disk device detected
Other USB key well detected... this is *not* the one on which visopsys is booting from.

That's good!

[dufresnep]

For the record here is the info for the USB Microsoft keyboard not working in Visopsys on my Quad-Core:
root@debian:/home/paul# lsusb -v -s 5:3

Code: Select all

paul@debian:~$ su
Password: 
root@debian:/home/paul# lsusb -v -s 5:3

Bus 005 Device 003: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x045e Microsoft Corp.
  idProduct          0x00dd Comfort Curve Keyboard 2000 V1.0
  bcdDevice            1.73
  iManufacturer           1 Microsoft
  iProduct                2 Comfort Curve Keyboard 2000
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x003b
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      1 Keyboard
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      60
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      86
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0000
  (Bus Powered)
root@debian:/home/paul# 

root@debian:/home/paul#

In Visopsys /system/kernel log:
Aug 2 07:18:41 2019 USB: keyboard human interface device 4:2 dev:00dd, vend:045e, class:03, sub:01 proto:01 usb:2.0
...
Aug 2 07:18:41 2019 USB keyboard device detected
...
Aug 2 07:18:41 2019 USB MS command error status 01
...
Aug 2 07:18:43 2019 USB unknown device detected

I am thinking of trying these USB keyboards on my Atom laptop see if this is more about controller or devices itself.