Description of problem: After doing an install of Mageia 4, Alpha 3, Gnome , at the first boot, when it comes to ... " Reached target Host and Network Name Lookups " a pop-up window appears, to help you configure a network connection. But there, the mouse and the keyboard don't respond, and the system stays like that, frozen. If you reboot, the same thing happens again and again. Version-Release number of selected component (if applicable): - Mageia 4, Alpha 3, LiveDVD, Gnome, 32bit, 1.4GB iso - Install from a memory card to a Lenovo netbook How reproducible: - Everytime Reproducible: Steps to Reproduce:
Created attachment 4414 [details] screenshot
CC: (none) => ennael1, mageia, thierry.vignaud, tmb
Priority: Normal => release_blocker
Whiteboard: (none) => 4alpha3
Looks like bug #11377 but after install. Could be udev or kmod
Source RPM: (none) => drakx-finish-install
Created attachment 4425 [details] screenshot after Live KDE DVD install The same thing happens after doing an install from KDE DVD (Mageia 4, Alpha 3, LiveDVD, KDE, 32bit, 1.4GB iso)
For what is worth, this Lenovo netbook has a touchscreen. Of course that doesn't respond either, nor does the touchpad.
Please stop testing that and test latest boot.iso from your preferred mirror. eg: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/install/images/
I just tried i586 boot.iso and boot-nonfree.iso, but I couldn't go on with the installation because I was not able to connect to the internet.
For the record, the installer issue (bug #11377) is now fixed (was due to new kernel).
It turns out it must be a GRUB thing. I was placing GRUB in " / " (sda9), so as not to risk ruining my previous installation of GRUB, and making my default Mageia 3 system (sda7) unbootable. Now, I placed GRUB in the beginning of the disk " Western Digital... " (sda ?), while making a new Mageia 3 installation on sda9. It, now, boots normally. Previously I had tried with Mageia 3 Mageia 2 Mageia 1 Live installations, and placing the GRUB in " /" (sda9). In all cases, the system would not boot, like in Cauldron. So it is fair to say, that if I try to make a new Cauldron installation, and install the GRUB in "Western Digital...", that it will boot normally. For the moment, I will keep the alternative Mageia 3 installation. I need to check some wi-fi issues.
(In reply to nikos papadopoulos from comment #8) Do you check if the hard drive is error free? It might be a bad block that causes the problem. Also, is this bug valid with latest Beta?
CC: (none) => tarakbumba
Any update on that bug? Please give a feedback in the coming days. Without any answer we will close that bug for now
Another user had the same problem. As I understood, he was istalling Mageia 4 on sdb disk, placing grub on sdb, as well. His system could not start the graphical enviroment. http://www.flickr.com/photos/104797541@N02/11709286246/ He, now, installed Mageia on sda (with grub on sda), and the system works properly. Here is the forum thread... http://www.mageia-gr.org/forum/viewtopic.php?f=2&t=298
That problem reported above is related to devices not showing up. Typically this is caused by stale entries in /etc/fstab that are not marked with nofail. Such devices are considered to be critical to the system (due to not having nofail option) and thus you are dropped into a fixup mode. Can you still reproduce the original problem? If so can you give exact instructions?
Quote: "Can you still reproduce the original problem?" A while ago I did a mistake, irrelevant to this bug, and made my system unbootable. Thankfully, after three hours, I managed to make it start. But, I concluded that experimenting with my single computer is not that smart... Quote: "If so can you give exact instructions?" You install Mageia on a partition, let's say "sdb3", and, during Mageia's installation, you choose "sdb3" for GRUB, as well. You might(?) already have another, previous, GRUB installed on "sda". Some more thoughts: If this bug is not to be fixed, shouldn't the user, somehow, be discouraged from using any other option than "sda" for GRUB, during the installation of Mageia? Or should the user have an option not to install GRUB, at all? Would this make the system unbootable?
(In reply to nikos papadopoulos from comment #13) > > Some more thoughts: > If this bug is not to be fixed, > shouldn't the user, somehow, be discouraged > from using any other option than "sda" for GRUB, > during the installation of Mageia? Why? If you want a multiboot setup and you have a preferred existing bootloader, then install Mageia's grub to the root partition of Mageia and add another entry in your existing bootloader to chainload Mageia's grub. > > Or should the user have an option not to install GRUB, at all? > Would this make the system unbootable? Yes it would for the new Mageia installation, if you don't manually create bootloader entries to Mageia initrd&kernel in an existing bootloader. As the technical issues with the installer have been fixed per Thierry's comment, can we close this bug? This is not a bug, but a question about bootloader configuration. I'd therefore close this bug.
CC: (none) => doktor5000
> Why? If you want a multiboot setup and you have a preferred existing bootloader, then install Mageia's grub to the root partition of Mageia and add another entry in your existing bootloader to chainload Mageia's grub. This will make your new Mageia installation NOT to be able to go to graphic mode. Please read the bug and the comments again ;). > Yes it would for the new Mageia installation, if you don't manually create bootloader entries to Mageia initrd&kernel in an existing bootloader. While making the new/parallel/ installation, if you don't choose to place Grub in sda, and you choose to place it in Mageia's root (for example sda9), then your new system doesn't go into graphic mode, when booting. Of course you create a new entry in the old Grub pointing at your new Mageia. But then this bug comes in...
(In reply to nikos papadopoulos from comment #15) > > Why? If you want a multiboot setup and you have a preferred existing bootloader, then install Mageia's grub to the root partition of Mageia and add another entry in your existing bootloader to chainload Mageia's grub. > > This will make your new Mageia installation NOT to be able to go to graphic > mode. Please read the bug and the comments again ;). Sorry I simply don't understand your issue so can't reproduce it. Seems you have an understanding problem about how to configure the bootloader. > > Yes it would for the new Mageia installation, if you don't manually create bootloader entries to Mageia initrd&kernel in an existing bootloader. > > While making the new/parallel/ installation, if you don't choose to place > Grub in sda, and you choose to place it in Mageia's root (for example sda9), > then your new system doesn't go into graphic mode, when booting. Of course > you create a new entry in the old Grub pointing at your new Mageia. But then > this bug comes in... Depends what the existing system uses as bootloader. But this cannot be solved by Mageia. See also https://wiki.mageia.org/en/Mageia_2_Errata#Installing_Mageia_next_to_a_GRUB2_based_distribution and https://wiki.mageia.org/en/Mageia_2_Errata#Mageia_boot_fails_when_dual_booted_from_a_GRUB2_system This is expected, so this bug should be closed.
> Sorry I simply don't understand your issue so can't reproduce it. Hey, no reason to feel bad about it. Thank you for your time, anyway. > Depends what the existing system uses as bootloader. But this cannot be solved by Mageia. See also https://wiki.mageia.org/en/Mageia_2_Errata#Installing_Mageia_next_to_a_GRUB2_based_distribution and https://wiki.mageia.org/en/Mageia_2_Errata#Mageia_boot_fails_when_dual_booted_from_a_GRUB2_system Could you please add the above in Mageia 4's errata, as well, so others can avoid misconfiguring Grub (like myself)? https://wiki.mageia.org/en/Mageia_4_Errata#Installer_Issues Unfortunately, as you have seen, I don't have the technical knowledge on Grub to do it myself. You seem to know these things a lot better. I don't think it will take you more than 5 minutes. Thanks, again, for your time.
Has been added to Mageia 4 Errata, closing.
Status: NEW => RESOLVEDResolution: (none) => INVALID