Test platform is a i7 SandyBridge with a removable replaceable hard drive. Primary drive has a Mageia 1 install with Vbox. Test ISO's: Mageia-2-alpha3-i586-DVD.iso Mageia-2-alpha3-x86_64-DVD.iso Burn iso's to DVD Insert blank drive and neither above iso's installers will recognize my USB keyboard and mouse. Same system running Mageia 1 and Vbox, installer of both ISO's recognizes USB keyboard and mouse and launches into a Vbox virtual OS install. Same system runs many other Distros just fine.
Hi thanks for your bug report. can you *attach* the output of lsusb (or lsusb -v) ? Does it work at grub ? at stage 1 ? or none of them ?
Keywords: (none) => NEEDINFO
(In reply to comment #1) > Hi thanks for your bug report. > can you *attach* the output of lsusb (or lsusb -v) ? > > Does it work at grub ? at stage 1 ? or none of them ? lol that would mean that I can use my keyboard to get into a terminal, I can't. Lemme see what happens when the M2A3 Live-CD's appear. It appears that I can get the grub to load faster then the 1 min wait with the keyboard enter key. It's not until I get to the log-in screen that the keyboard and mouse do not work. More testing on my part here. Also I am using a wireless keyboard and mouse. I'm not sure that makes a difference. When I saw this I immediately did an install with the Mageia 1 DVD's and that worked fine on the same platform.
(In reply to comment #2) > (In reply to comment #1) > > > Hi thanks for your bug report. > > can you *attach* the output of lsusb (or lsusb -v) ? > > > > Does it work at grub ? at stage 1 ? or none of them ? > > lol that would mean that I can use my keyboard to > get into a terminal, I can't. Lemme see what happens > when the M2A3 Live-CD's appear. > In another OS ? :) (Sorry and I have still not understand, when the input device don't work)
Source RPM: (none) => drakx-installer-images
(In reply to comment #3) > (Sorry and I have still not understand, when the input device don't work) Today I am going to put some time into this to determine exactly when that occurs. Gimme 24.
Here's the test platform: SandyBridge - Video editing machine ----------------------------------- Intel Core i7-2600K Sandy Bridge 3.4GHz overclocked to 3.8GHz LGA 1155 95W Quad-Core GIGABYTE GA-Z68X-UD3-B3 LGA 1155 Intel Z68 SATA 6Gb/s USB 3.0 ATX Intel Motherboard GIGABYTE GV-N440D3-1GI GeForce GT 440 (Fermi) 1GB 128-bit DDR3 PCI Express 2.0 x16 CORSAIR Vengeance 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Seagate Barracuda ST31000524AS 1TB 7200 RPM SATA 6.0Gb/s 3.5" Internal Hard Drive Sony Optiarc CD/DVD Burner Black SATA Model AD-7260S-0B Thermaltake V9 BlacX Edition with Docking Station Cooler Master Hyper 212 Plus CPU Cooler Kingwin KF-91-BK SATA Mobile Rack Kingwin KF-91-T-BK SATA Mobile Rack Tray Logitech K520 Wireless USB Keyboard & Mouse As you can see the system has a removable replaceable modular hard drive rack & tray. On a 1TB tray is a fully operational and working Mageia 1 install. For now that is my primary video editing system. This is kept up to updates daily. Without saying the wireless mouse and keyboard work just fine. Replace Mageia 1 1GB HD drive tray with a blank 250GB test drive tray. Boot with Mageia-2-alpha3-x86_64-DVD 1. F2 ( Bios ) F12 ( boot menu ) work just fine with keyboard 2. M2A3 64-bit GRUB Selection Screen works just fine with keyboard. I can move the selection up and down on the screen with the up and down arrows on the keyboard. 3. "Please choose a language to use" screen. Mouse courser is at center screen. Neither the Keyboard nor the mouse respond on this screen and I can go no further with the install. Reboot the system back to the 1TB HD with Mageia 1 installed and everything works just fine. Using this exact same system and the same Mageia-2-alpha3-x86_64-DVD.iso file that created the M2A3 DVD I can do a successful install, using the same keyboard and mouse, using VirtualBox.
Ok Any ideas Thierry ?
CC: (none) => thierry.vignaudSource RPM: drakx-installer-images => drakx-installer-stage2
I understand nor your wireless mouse, nor your wireless keyboard respond anymore when you enter the Language choice screen while trying to install after inserting a blank 250 GB test drive tray, but there is no problem doing a virtual box install. Can you please provide the /root/drakx/report.bug.gz of the successful install? (I hope it gives some clue about the other install going wrong) Would be nice to find out whether the unsuccessful install is frozen, or the wireless mouse + keyboard are just not recognized anymore. Do you happen to have a wired mouse and maybe even a wired keyboard to test with? If so, please test.
CC: (none) => marja11
And attach the pci.txt file resulting from running the "lspcidrake -v > pci.txt" command (with either mga2 or mga1)
@ William could you please reply to the previous questions? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
I am waiting for the Beta 1 DVD release of Mageia 2. Once that is officially released I will try again. Please understand that if I still cannot control Mageia 2 Beta 1 with the use of a USB keyboard and mouse I am not going to be able to get any kind of a file as I cannot get into the install because it does not respond to the use of a USB keyboard and mouse. Do note I live in California and probably won't see M2B1 until probably Wed 22 Feb. Thanks in advance for your patience.
@ William Thx for your willingness to try again with Mga2beta If you still have your Mageia 1 install, could you please already attach the pci.txt file resulting from running the commnand (in a konsole/terminal): lspcidrake -v > pci.txt
Summary: M2A3 not handling USB Keyboard & Mouse => M2A3 not handling wireless USB Keyboard & Mouse
Created attachment 1595 [details] Here's the txt file from lspcidrake -v > pci.txt Running 64-bit Mageia 1 just fine with USB Logitech wireless mouse and keyboard
Many thanks for your patience on this. First the test platform: SandyBridge - Video editing machine ----------------------------------- Intel Core i7-2600K Sandy Bridge 3.4GHz overclocked to 3.8GHz LGA 1155 95W Quad-Core GIGABYTE GA-Z68X-UD3-B3 LGA 1155 Intel Z68 SATA 6Gb/s USB 3.0 ATX Intel Motherboard GIGABYTE GV-N440D3-1GI GeForce GT 440 (Fermi) 1GB 128-bit DDR3 PCI Express 2.0 x16 CORSAIR Vengeance 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Seagate Barracuda ST31000524AS 1TB 7200 RPM SATA 6.0Gb/s 3.5" Internal Hard Drive Sony Optiarc CD/DVD Burner Black SATA Model AD-7260S-0B Thermaltake V9 BlacX Edition with Docking Station Cooler Master Hyper 212 Plus CPU Cooler Kingwin KF-91-BK SATA Mobile Rack Kingwin KF-91-T-BK SATA Mobile Rack Tray Logitech K520 Wireless USB Keyboard & Mouse Note the removable replaceable modular hard drive system and USB wireless keyboard and mouse. This system normally runs with a 1TB drive, Mageia 1 64-bit. It is fully functional and detected the USB keyboard and mouse from the install. It continues to run successfully today. Also this system, using other hard drives and live CD's, runs Ubuntu and Puppy Linux. First thing I did for this test was to remove the Mageia 1 1TB HD and replace it with a scratch 80GB drive. Then using a program called killdisk ( killdisk.com ) I completely erased the scratch 80GB hd from beginning to end. Using killdisk you can examine the data on the first track first sector and that is all 0's. Killdisk was successful in using the USB keyboard. I then booted Puppy Linux Live CD ( 5.3.1 ) and using one of its tools, Gparted, I was able to confirm that the 80GB harddrive is blank and "unallocated". Do note that Puppy 5.3.1 fully works with the USB keyboard and mouse on this system. I then mounted the Mageia 2 Beta 1 install DVD Mageia-2-beta1-i586-DVD.iso 32-bit and rebooted the system. The install disk responded to the enter key to immediately start the install process. The install disk successfully gets to the initial install screen as follows: Boot from hard disk Install Mageia 2 ( Cauldron ) Rescue System Memory Test Hardware detection tool and the F functions across the bottom of the screen. All of these selections select with the keyboard up and down keys. I can go to "boot from hard disk" but of course there is nothing on the disk and it hangs. I can using the keyboard up and down keys navigate to the Rescue System selection and start that. But there is nothing on the disk and can't be rescued. I can navigate to the memory test and that works fine with the keyboard. I can navigate to the hardware detection selection and navigate that completely, using the keyboard, through all the features and functions of that selection. Selecting the Install Mageia 2 is successful and it goes through the setup process we see with Mageia 1 or even Cauldron using a PS2 keyboard and mouse or this same system using Mageia 1 and Vbox. The initial install setup process completes and takes you to the first selection page: Installation Language English ( American ) At this point there is a mouse pointer in the center of the screen. There is no response from either the mouse movements nor any of the keys on the keyboard. Removing the Mageia-2-beta1-i586-DVD.iso disk and remounting the killdisk disk I examine again the contents of the first sector, first track of the drive. All zeros, the disk has not been altered. Remounting Puppy Linux 5.3.1 and running GParted the 80GB test disk remains unallocated. Puppy Linux continues to operate with the USB Keyboard and mouse just fine.
CC: (none) => mageia
Maybe a side effect of using udev? We would need someone to test using an usb keyboard _and_ a regular keyboard in order to get logs and see what happens...
CC: (none) => pterjan
Thanks Thierry. What I may try to do here is build a M2B1 system on a removable drive on another system ( I have three that use removable drives ). Once that system is up and running then move it over to this USB only system and see what happens. I've been successful in doing that some in the past. Unfortunately this test system does not have a PS/2 port to connect a conventional keyboard and mouse. I'd hate to see this get into the final release.
(In reply to comment #15) > Thanks Thierry. What I may try to do here is > build a M2B1 system on a removable drive on > another system ( I have three that use > removable drives ). Once that system is up > and running then move it over to this USB > only system and see what happens. This probably won't be needed. I have the same keyboard on one of my system. (In reply to comment #14) > Maybe a side effect of using udev? > We would need someone to test using an usb keyboard _and_ a regular keyboard in > order to get logs and see what happens... Thierry, it's probably easier. This keyboard-and-mouse wireless combo uses the Logitech® Unifying receiver. Since kernel 3.2.0, keyboards and mouses using the Unifying receiver use and need a new kernel module; hid_logitech_dj. I guess this module is missing in the installer.
CC: (none) => lmenut
Created attachment 1622 [details] lspcidrake -v Logitech MK520 with kernel 3.2.6
I confirm; hid_logitech_dj.ko.xz is missing in /modules/3.2.6-desktop-3.mga2. (similar pb in mdv 2009.1 with some other keyboards: https://qa.mandriva.com/show_bug.cgi?id=47167#c16 ...)
Thx Fixed in SVN
Status: NEW => RESOLVEDResolution: (none) => FIXED
Would testing be correct if I used a new version of boot.iso on this platform? Or is the missing module going to be specifically with M2B1 DVD install iso? Many thanks to the Mageia Super Team.
(In reply to comment #19) > Thx > Fixed in SVN (In reply to comment #20) > Would testing be correct if I used > a new version of boot.iso on this > platform? Or is the missing module > going to be specifically with M2B1 > DVD install iso? > > Many thanks to the Mageia Super Team. @ Kenny Fixed in SVN means, that the next time the package to be fixed will be updated, the fix will be in it. Thierry didn't say the fix was pushed. When it is, Mga2b1 DVD won't change, but boot.iso should work OK, then. The fix will surely be in Mga2b2 DVD
@ Thierry do you mind giving a link to the fix in SVN and/or telling when the fixed package is pushed? I didn't manage to find it and I'm very curious what I did wrong (I looked at kernel, did see something about patches that were dropped about 2 days ago, but not which patches. I didn't find anything in drakx-installer-stage2 either)
It has been pushed yesterday evening. It will land on your favorite mirror when it syncs
Testing of M2B2 64-bit today confirms that this bug is resolved. Many thanks to all.
*** Bug 4231 has been marked as a duplicate of this bug. ***
CC: (none) => pdb128