#1891 closed bug (fixed)
No keyboard or mouse input on real hardware
| Reported by: | salierix | Owned by: | mmlr |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Drivers/USB | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | marcusoverhagen | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
My mouse and keyboard don't work when running Haiku on my machine, however everything is fine when using qemu or vmplayer. I've tried both PS/2 and USB but neither seem to work.
I'll try to get some log output but lacking a mouse or a keyboard makes that kind of tricky...
Change History (12)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
If you have a digital camera, one thing you could do is to enable the console debug mode in the safe mode menu, and then just make a photo of each page of the output; that might help, but the app_server might also be started too early for this.
Eventually, changing the Bootscript to only start the input_server manually might help, too (and not the app_server); I dunno if that works, though.
comment:3 by , 17 years ago
After compiling/installing/booting about 20+ different revisions I tracked the problem all the way to hrev22521 from over 5 months ago. For some reason lacking the ohci driver prevents my ps/2 mouse and keyboard from working and so adding it to the current revision completely fixes the problem.
While I found a workaround to the problem I still have no idea how not having the ohci driver on the image causes this mess, even though I have no usb devices pluged in.
This ticket should remain open for the time being.
comment:4 by , 17 years ago
| Cc: | added |
|---|---|
| Component: | - General → Drivers/USB |
| Owner: | changed from to |
Now that sounds really strange. Seems to be related to the legacy emulation of your BIOS then. I'm just wondering why the safe boot fixes it. Anyway, I'm assigning this to Michael, as it seems to be primarily USB related.
comment:5 by , 17 years ago
Safe mode doesn't "fix it". The only reason I mentioned it was because I wanted to take a look at the log file and safe mode helped with that.
The fact that safe mode works has nothing at all to do with the problem.
comment:6 by , 17 years ago
Following Axel's suggestion on the dev list, setting the usb legacy option in my bios to "disabled" from its previous setting of "enabled" also seems to solve the problem whether the ohci driver is installed or not.
comment:7 by , 17 years ago
I'm experiencing this issue as well, but installing ohci does not fix it. Keyboard and mouse are ps/2, and they work in the bootloader, but not in safe mode or normal mode. Can't disable USB Legacy because my manufacturer has locked down the BIOS severely.
comment:8 by , 17 years ago
I've experienced the same error as Salierix. Adding ohci addon to kernel/busses/usb suddenly allows a PS2 keyboard and mouse to work. nForce 590 motherboard. Weird.
comment:9 by , 17 years ago
| Status: | new → assigned |
|---|
That adding OHCI did change the behaviour when legacy emulation is turned on does not sound so unlikely to me. Installing the OHCI driver (even if it did not actually work) should have caused the BIOS to get kicked off the OHCI controller, disabling legacy emulation. So that either turning legacy emulation off by hand or an installed OHCI driver gives the same behaviour was to be expected.
Anyway, now that the OHCI driver is implemented and present by default, could you please verify if this ticket is still required? If everything works now I'd like to close it. Thanks.
follow-up: 11 comment:10 by , 17 years ago
The issue can now be closed. I've tested it with build R25653, and it works like a charm.
BTW - I've also tested my USB 1.1 backlit keyboard and mouse. It works for the first minute or so, then fails to respond. Reconnecting the keyboard / mouse fixes the issue. Since there has been weekly activity on the USB stack, I'll wait for another week or so before logging a concrete issue.
I might now finally be able to port some of my OpenGL projects to Haiku.
Cheers.
comment:11 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Replying to zenja:
BTW - I've also tested my USB 1.1 backlit keyboard and mouse. It works for the first minute or so, then fails to respond. Reconnecting the keyboard / mouse fixes the issue. Since there has been weekly activity on the USB stack, I'll wait for another week or so before logging a concrete issue.
That might have been fixed (or made worse) through my rewrite of usb_hid. You could try with hrev25658 and up as that should include error handling. Will close this bug now, if there should be further issues with usb_hid please report them in enhancement #2253.
My keyboard seems to work if I boot using the safe mode option.