but have you connected the KVM to the USB-port dedicated for the keyboard?
and can you use your keyboard in CFE?
Can you share the connections schematic again please?
If I read your posts correctly, your connections looks like this:
- Keyboard connected to the Mouse port of the CS1784A, - Mouse connecte to the keyboard port of the CS1784A - USB Kable (port xx) from the CS1784A to a USB port of the X1000 which is not the dedicated Keyboard port.
On the X1000, the USB part of the cable to the KVM switch is in the lower port of the first column (i.e the one closest to the sound sockets).
I'm not sure what the USB port dedicated for the keyboard is on the X1000, isn't that just one of two in the first column? There are (IIRC) no markings of where to connect the keyboard on the X1000 backplate.
The other end of the cable is connected to port 4 of the KVM (USB, DVI DL, and sound play/rec).
My mouse (receiver) is in the keyboard socket on the back of the KVM.
My keyboard is in the USB2.0 socket below the mouse and keyboard sockets on the back of the KVM.
I guess it boils down to this question (and thanks for all the input)...
Will the CS1784A allow me to plug in one keyboard and one mouse (I can experiment with which USB ports are actually best) and allow me to switch their use between the X5000 and X1000, also working with CFE (X1000) and UBOOT (X5000) whether cold booting, warm booting, one computer on at the time, both on at the time?
That's what I'm doing, see the above description for the X1000. My X5000/40 is connected to port 3, and in port 2 I have a pc dual-booting Debian and Win7Pro.
I do have the issue that after having used Debian Linux and returning to AmigaOS or Windows, I have to pull the mouse receiver out of the KVM switch for some seconds and re-insert it, because until I do, the mouse pointer won't move. The keyboard is not affected.
This is probably something Debian does, because it wasn't always so. I think it started after upgrading Debian to Bookworm. I intend to upgrade it to Trixie soon, we'll see if it changes things.
But as for X1000 and X5000, I have no problems. Keyboard working fine in UBoot/CFE as well.
@rjd324 I'm using a fine mix of bundled cables and off-the-shelf USB and DVI cables without problem.
Only known issue for me is that the initial mouse button state some times reports buttons pressed. So sometimes my Amigas will boot into the Early Startup instead of to Workbench. This can be remedied, though, by setting a UBoot variables for the AmigaOS bootmouse driver to ignore initial mouse button state. The only side effect of this is that you then have to move the mouse while pressing both mouse buttons if you really need to enter the Early Startup at some time.
I think maybe my firmware is already 1.0.077 or more, because the buttons seem to already function like that for me. Now that you mention it, I remember reading something about it before.
At some point when I get time, I will try checking my KVM switch's firmware version and also update it to the latest firmware, but that will probably not be until some time in the new year.
As for why it works so strangely on your X1000, I don't know. I don't see such behaviour on mine. But I'm no "Voodoo master" .
Best regards,
Niels
During the weekend I would like to replicate your exact configuration here. It bugs me that it does not work.
I hope you have some spare time to reply to questions and find out why it works on your machine and not mine.
Would you mind sharing your CFE vars settings for starters?
The User Manual for the X1000 says that when facing the USB connectors, the port at the bottom far left is reserved for the Keyboard. I can confirm that this is the case with the CFE version I have on my board (PAS-2.0.30). Only a keyboard connected to that port (no KVM in-between) will work on CFE. Of course keyboards will work on every other port once the OS has booted.
And I am using that port for the USB cable coming from the KVM switch, so both keyboard and mouse are seen through that cable, and there is a KVM switch in between.
I'm not sure that comment in the manual should necessarily be taken as the golden truth, for instance I guess KVM switches behave differently, so some may be causing problems, while others manage to seem transparent to the system.