I have three network profiles. At boot time, when Mageia asks me to choose which one I want to start, I type the corresponding number but nothing happens and the boot process hangs here. It used to work with Mageia 2 RC. I set it as critical as I can't boot anymore in Mageia !
Any workaround to that bug ? I'm stuck with not being able to boot Mageia 2 anymore...
Sorry for the delay responding to this. I was hoping someone more familiar with the usage of network profiles would take this one. More information is required before anyone can help solve this problem. During the boot, edit the kernel options, and remove the options splash and quiet, so you can see the boot messages. Does the boot hang? If so, what are the last messages shown? Does it drop to a command prompt? Specific details are needed.
CC: (none) => davidwhodgins
when pressing escape, I can see the boot messages. It shows the usual network profile selection message, proposing to type one of the numbers corresponding to profiles. But typing any of them does nothing. So, no error message, no command prompt, I'm just stuck to the profile selection question and no way to go further...
How did you install (Live cd, dvd, dual-cd, etc.)? Which desktop manager (gdm, kdm, xdm, etc.)?
Install from DVD, desktop manager kdm. I don't think this is an install problem since I previously did another install from Mageia 2 RC, and the network profile choice worked, until I upgraded some packages (unfortunately I don't remember which ones) and then it did not work anymore. That's why I did a new fresh install from Mageia 2 DVD which had been released in the meantime, hoping it would solve the problem, but it did not.
My best guess at this point, is a missing driver for the keyboard. Try rebuilding the initrd. Boot the dvd into rescue mode, select mount the partitions, then select go to console and enter the following commands. mount /dev /mnt/dev --bind mount /sys /mnt/sys --bind mount /proc /mnt/proc --bind chroot /mnt dracut -f As it's in a chroot, dracut should build a non-hostonly initrd, with more drivers. Then try rebooting and report back if that works or not.
Hi Dave, and thanks a lot, you put me on the right way : - first, I noticed that, if I did not touch the keyboard when the boot process asks me to choose the network profile, after 5 seconds, the boot process continued and achieved properly. (while, as soon as I tried to type something, it was blocked). That let me operate under Mageia 2 without having to use the DVD in rescue mode. - then, I just regenerated the initrd with : mkinitrd --force initrd-3.3.6-server-2.mga2.img 3.3.6-server-2.mga2 - and then, after reboot, the net profile selection was working again ! Solved !
Status: NEW => RESOLVEDResolution: (none) => FIXED
Regenerating the initrd while actually in Mageia 2, would not create a non-hostonly initrd with all of the drivers. I'm wondering, were you using a chroot into Mageia 2 when you installed the updates last weekend? Those updates would have forced a regeneration, of the initrd, and if you were using a chroot, that would have generated a non-hostonly initrd. I'm trying to figure out what broke the previous initrd.
No I never used chroot into Mageia 2. In fact, I first thought some updates were responsible of the problem, but I wonder now if it was not the fact that I installed a debian system on another partition : it made my swap partition reformated, and I noticed in the past with mandriva and mageia 1 that reformating the swap partition had some consequences on the boot process (a one minute timeout at the beginning of the boot process with some message "waiting for something"), until I regenerated the initrd. With Mageia 2, the problem was different, but maybe the cause was the same, since it was solved with the same mkinitrd command ?
That would explain the hang. It's looking for the swap partition using the uuid, which would have changed after being reformatted. Thanks for clarifying the cause.
*** Bug 6695 has been marked as a duplicate of this bug. ***
CC: (none) => nrcefe