Description of problem: After upgrade to kernel-desktop-3.4.24-3.mga2-1-1.mga2, Mageia 2 broken startup and syslog says: Jan 18 11:32:32 acer systemd[1]: plymouth-quit-wait.service operation timed out. Terminating. Jan 18 11:32:32 acer systemd[1]: Unit plymouth-quit-wait.service entered failed state. Jan 18 11:32:33 acer systemd[1]: Startup finished in 699ms 320us (kernel) + 5s 403ms 795us (initrd) + 1min 5s 87ms 594us (userspace) = 1min 11s 190ms 709us. Version-Release number of selected component (if applicable): kernel-desktop-3.4.24-3.mga2-1-1.mga2 How reproducible: Steps to Reproduce: 1. 2. 3.
What is the graphics card you are using on that system? Is it possible that some modules didn't get updated along with the kernel?
Keywords: (none) => NEEDINFOCC: (none) => sander.lepik
(In reply to comment #1) > What is the graphics card you are using on that system? Is it possible that > some modules didn't get updated along with the kernel? You are wright! I have NVIDIA GeForce FX series board and had "nouveau" driver working fine in kernel-desktop-3.3.8-2.mga2-1-1.mga2. I compiled the new drive from package supplied by Nvidia and all are working. Thank You.
(adding tmb for point hum this 'bug')
CC: (none) => tmbSummary: Mageia 2 can't startup after upgrade to kernel-desktop-3.4.24-3.mga2-1-1.mga2 => Mageia 2 can't startup after upgrade to kernel-desktop-3.4.24-3.mga2-1-1.mga2 (NVIDIA card)
(In reply to comment #2) > (In reply to comment #1) > > What is the graphics card you are using on that system? Is it possible that > > some modules didn't get updated along with the kernel? > > You are wright! > > I have NVIDIA GeForce FX series board and had "nouveau" driver working fine in > kernel-desktop-3.3.8-2.mga2-1-1.mga2. > > I compiled the new drive from package supplied by Nvidia and all are working. Did you have this one installed on the 3.3.8 kernel too ?
No. In 3.3.8 kernel I didn't had compiled the drive from Nvidia. I had the the drive supplied by Mageia 2 installer.
Do you have nonfree medias enabled? Nonfree Release & Nonfree Updates
CC: (none) => eeeemail
Yes, I have both.
You need know that I just tried run XFdrake and it works fine too.
I think it is not relevant because the drive that XFdrake put in xorg.conf is the same I had compiled from NVIDIA package...
I have the same exact problem with Mageia 2. Its an onboard Geforce 8400. This is a fresh install. Put in all updates all was working until I put the Nvidia drivers in. It hung at the same location as posted. Booted into fail safe run XFdrake switched to the nv driver without starting the display manager. Then loaded the driver from Nvidia. Now I have a working system. I have had the same problem with all the Nvidia drivers from Mageia on a different system with the same MB.
CC: (none) => rbcourt
CC: (none) => adrien.daugabel+mga
Hi, Same problem on x86_64 arch.
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Resolution: (none) => OLDStatus: NEW => RESOLVED