Description of problem: Two days ago I upgrade to Mageia 5RC. I tried 3 or 4 times to install. My keyboard did'nt work when i wanted to login. The last one was the right one, keyboard ok. Yesterday, no problem, i boot normally, i set automatic login in MCC and i worked like with Mageia 4. Today, boot ok, automatic login ok, but keyboard doesn't work. Mouse is OK. My grafical environment is KDE. I should add that i can use key board at the boot to select mageia 5. You can see that it works with Windows 8.1... It's life. I could try a fifth install but if it's a bug in release candidate i prefer to share. The computer is Asus All-In-One powered by Intel I5 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Can you somehow get access to the root partition of that install? For instance by using a Live DVD, or (if the keyboard still works after you do that), by booting into "runlevel 3" by appending "systemd.unit=multi-user.target" to the kernel option line in the bootloader menu? If so, please attach the /root/drakx/report.bug.xz from the last install, unless you only ran upgrade installs. If you only upgraded, then fetch /root/drakx/report.bug from the time of the last upgrade install that failed, compress it with "xz report.bug" and then attach report.bug.xz to this bug report. If you do manage to use the keyboard after booting Mageia in text mode, then please also run (as root) "journalctl -a > journalctl-a.txt" and compress it with xz and then attach it to this bug report, too.
CC: (none) => marja11
CC: (none) => thierry.vignaudWhiteboard: (none) => NEEDINFO
A kernel driver might have been split and we may lack it. Can you attach (not paste) the output of "lspcdrake -v" from Mga4?
Source RPM: (none) => drakx-installer-images
Or better from Mga5's live DVD if keyboard works with it.
CC: (none) => tmb
Ping?
Source RPM: drakx-installer-images => drakx-installer-images, kernel
Gilles, could you provide the needed information?
Keywords: (none) => NEEDINFOWhiteboard: NEEDINFO => (none)
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => OLD