| Summary: | Since 3.1.2-desktop-0.rc1.1.mga2 can't boot on any new kernels | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Luiz Alberto Saba <las> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | marja11, pmithrandir |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel-3.1.4-2.mga2.src.rpm | CVE: | |
| Status comment: | |||
| Bug Depends on: | |||
| Bug Blocks: | 2120 | ||
|
Description
Luiz Alberto Saba
2011-12-07 01:40:51 CET
Typo... :-( The correct statement is: With 3.1.2-desktop-0.rc1.1.mga2 I CAN boot normally. doest it works with init ? To Manuel Hiebel (Comment #2): I don't understand what do you mean with "works with init"... Can you explain better? I guess you are using systemd no ? Can you reproduce this bug with initscript ? For Manuel Hiebel (Comment #4) As sonn as you teach me how to change from one to another, I'll test it. I really don't know how to do it. whith init=/bin/init maybe seriously I don't really know :/ Significative improvement on the situation!!! Now I can't boot at all :-) Still the errors with systemctl... (obviously I'm writing from another machine) (In reply to comment #7) > Significative improvement on the situation!!! > Now I can't boot at all :-) with the recent update or with using init ? Yesterday's updates... ok great :) (in these days it's more wait and see... :D ) feel free to reopen Status:
NEW =>
RESOLVED I wrote that I CAN'T BOOT at all This is a fix? Status:
RESOLVED =>
REOPENED oups I have misread and I was confuse with your smiley sorry :s Blocks:
(none) =>
2120 Well... Since I had things to do and no machine, I've tried alpha 1. Installs (almost) fine (LONG time "preparing bootloader), but on reboot systemctl rides again and NO BOOT one more time. Anyone has any idea of WHEN systemctl will finally works fine? I will say, try to edit your lanucher, and remove systemd... to see if you have the same issue than me. Procedure : start your machine At grub, press ESC, then OK choose the mageia you want to start, then press e, and e again on the long line. Remove init=...systemd(don't remember exactly what it is) press ENTER press b That procedure will not write the new config on your computer, so another reboot will have the current setting, Does that help ? CC:
(none) =>
pmithrandir @ Luiz Did you try what Pierre suggested? Did it help? What is it like with Mga2a3? Keywords:
(none) =>
NEEDINFO 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:
REOPENED =>
RESOLVED |