Hey friends,

When launching either VoidPPC Linux or OSX (Tiger or Leopard) on my Powerbook 5,9, the Dell USB mouse works. It is of model MOCZUL. According to the specifications, it is rated to 5V, 100mA. I'm not sure if this is helpful information.

On the other listed OSes, the mouse emits a blue light. Under MorphOS, there's a very slight occasional flicker of blue light but the mouse never truly works.

I have several of these mice and they all exhibit the same behavior.

Anyone have any ideas here?

Posting the VID/PID would be a good start if you want anyone to investigate.

Please excuse my ignorance. What's that? :)

Vendor and Product IDs. You'll find them in USB settings for the device.

Gotcha. Thanks. They are:

Product ID: 0x4d51
Vendor ID: 0x0461 (Primax Electronics)

Well, it doesn’t look like there is anything special about this device ... what logs does the USB prefs spew out when you plug it in?

Got an amazon link for it? Maybe I could get one and take a look...

No messages at all when plugging/unplugging the mouse. Very strange!

I can probably just mail you one if you like - pm me your shipping info. No big deal.

On Amazon, I believe it's this: https://smile.amazon.com/Dell-6-Button-Perfectly-Connectors-Compatible/dp/B005O239FW/ref=sr_1_3?dchild=1&keywords=dell+moczul+mouse&qid=1595808368&sr=8-3

The mouse actually works fine via a hub, either self-powered or bus-powered. I'll have to see what the pciusb driver does when going online, seems it sets things up in a way that prevents the mouse from booting up. There's no USB transfers at all when it can't start up.

[ Edited by jacadcaps 08.08.2020 - 01:39 ]

Thanks for the update (and the PM). It’s interesting to me that it works in every other OS, so it would seem like MorphOS isn’t signaling to send power to the USB port maybe?

Quote:

When you plug it into Windows, does it work straight away or is it one of these annoying mice where there's a pause while Windows automatically installs a driver?

There should be power to USB ports all of the time on most systems, but I'm aware that with Apple hardware this isn't always the case.

[ Edited by KennyR 08.08.2020 - 11:16 ]

It works w/o special drivers. Works in OF too... Guess this will give me a chance to play with Saleae soon :)

Quote:

It's not that - it's just some mice seem to require a software switch to actually turn on, something the driver does. (Or OpenFirmware, apparently.)

My memory is hazy, but I think I had a Dell mouse back in the 00s that did this.

Edit: Nope, it was an Asus mouse, which came with my laptop.

[ Edited by KennyR 08.08.2020 - 14:41 ]

The full story of my Asus mouse may have nothing to do with OP's problem but it was this:

It worked in BIOS because it was initialised by the BIOS's own "USB Mouse Function" option which enabled USB devices to be used in MS-DOS. Linux also had no problems, with or without this option.

But once Windows had booted, it required the driver to initialise the mouse. This was no problem for me, but when I added other use accounts that were non-admin, the mouse would just sit there, unpowered, because drivers need admin rights to install (even if they were shipped with Windows).

I don't think I ever used that mouse on MorphOS to see what it did, and the Peg1 firmware didn't support mice or boot menu anyway.

I guess that mouse supported HIDBP (BP for boot protocol), but not regular HID - or simply lacked a proper HID descriptor. It's very unfortunate that Microsoft has allowed vendors to make filter drivers that simply correct / fill out a descriptor the standard drivers can understand. That means the device itself may be bogus, but whatever it passes would then be filtered/corrected by the driver...

Finally had a chance to open the Dell mouse and capture the traffic with a logic analyzer. One can clearly see where exactly the mouse crashes... No fix for now but at least I’ve confirmed my suspicion that it is all about timings.

Quote:
Wow!
FYI Linux driver

[ Editiert durch polluks 17.09.2020 - 16:44 ]