| Summary: | M6dev1 Stage 2 installer has lost keyboard & mouse contact | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | William Kenney <wilcal.int> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | ftg, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
William Kenney
2016-01-10 16:53:00 CET
(In reply to Frank Griffin from comment #1) > Also see bug#17140 . Does "mouse" mean a real mouse or a touchpad ? I tried it a couple ways. 1st was with a Logitech wireless keyboard and mouse. When that failed at Stage 2 I went with a real hardware USB keyboard and mouse. Both had the same problem. This was ok a few weeks ago on the same test platform. OK, so between our two bugs we now know that it's a mouse and not a touchpad issue, and that whether or not the keyboard is recognized seems to vary between free and nonfree. Can you test with boot-nonfree.iso and see if the keyboard comes back ? Ok tinkering a little more with this. With the boot-nonfree.iso if you just use the keyboard then that initially works. Touch the mouse then neither the keyboard nor the mouse work anymore. I went back to the boot.iso and once in Stage 2 I only used the keyboard and once I had navigated through a couple steps I was then able to use the mouse. And the keyboard continued to work ok. Something is not right here. Install is continuing as normal. OK, see the latest in bug#17470 , looks like a solution has been found. |