-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keyboard not working in Chrome OS #8
Comments
hey thanks for your feedback This can be caused by a SD Card not mounting, or by a device using the same USB ID on the host machine. Can you post the output of your /var/log/syslog after you plug the WUD ? here's mine:
|
Grabbed them from Chrome://system
input_devices
|
I hope you don't mind I edited your comment for readability. that's a quite crowded bus, but the syslog seems to recognize all the devices advertised byt he WUD. what puzzles me is that part, I'm not sure what to make of it, is that a normal message on Chrome OS or maybe a consequence of the sandboxing?
If the problem is elswhere, it may be interesting to boot the machine while the WUB is plugged in, and observe the device order change. Could it be that Chrome OS requires the user to press a certain key on a keyboard before enabling it, like MacOS does? Sorry about the naive question, I don't know Chrome OS :-) |
No worries, I apologize for the formatting. I don't use github often enough to know the markdown. I did some more testing and it looks like that message is probably unrelated as it does not reappear on different attempts But I did see some possibly interesting logs underneath that I missed.
|
This is a little above my head but if I am understanding this right, ChromeOS might be blocking the keyboard as it is already being used as a mouse or storage drive. I have tried using StopMouse and StopPenDrive commands but keyboard is still not working. Is there possibly a way to disable the mouse and pendrive before flashing so I can test that? Thank you again for all your help. |
this part is interesting:
it means you can eventually play with USB_PID / USB_VID until something is found
the WUD-Ducky has a few commands to start/stop the USB devices, only the 'start*' situations have been tested though The info window in the WebUI should show the different device statuses. |
I am going to put the chromebook in developer mode so I read the the "/usr/share/misc/usb.ids" file. Also I have tried stopping the devices but they come back on with a reboot. |
That file does not exit apparently 🤦♂️ chronos@localhost /usr/share/misc $ ls -l |
Can send mouse commands to ducky plugged into chromebook/box but cant send any keyboard commands at all.
I am using the arduino-esp32-2.0.2 branch
The text was updated successfully, but these errors were encountered: