| Summary: | Created boot-image won't boot to login-window if you install using the boot.iso | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | gruescubogdan, mageia, rwobben, thierry.vignaud |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | grub | CVE: | |
| Status comment: | |||
| Attachments: | report.bug.xz from the installed system | ||
|
Description
Kristoffer Grundström
2012-12-10 00:54:39 CET
Is that grub or grub2? Keywords:
(none) =>
NEEDINFO I think this is the same as Bug 8357, I am also affected (tried with boot-nonfree.iso). It happens with grub. If I select grub2 or lilo (tried that using the same boot-nonfree.iso after the first install, but choosing upgrade instead of clean install) it fails to create/save the bootloader altoghether. At least with grub the bootloader is saved so that I can boot into Windows. CC:
(none) =>
gruescubogdan Can you attach the /root/drakx/report.bug.xz of that system? Created attachment 3230 [details]
report.bug.xz from the installed system
I've seen you have been working on this Thierry, therefore I've downloaded a fresh boot-nonfree.iso and updated my currently non-working installation.
The update process was slower than before (it hangs a little at the start of updating packages, then it worked fine). It also pulled the new kernel (version 3.7.0 final). I've chosen grub as bootloader. Update process finished apparently successfully.
At reboot, the boot failed. Tried also to boot with the previous kernel, in this case I get:
dracut Warning: Canceling resume operation. Device not found.
dracut Warning: Could not boot.
dracut Warning: "/dev/disk/by-uuid/(<<comment: long string here>>)" does not exist
Dropping to debug shell
dracut ://#
That's all. Haven't tried a clean install though. If still needed, the archive 'report.bug.xz' is attached.
I think that's a different issue. Please open another bug report against dracut CC:
(none) =>
mageia @Bogdan When opening that bug, can you CC me, and supply the "long string here" value? Also I suspect the string is coming from the kernel command line (either root= or resume=) Can you confirm the UUIDs match? (all on the new bug tho' please :)) (In reply to comment #4) ... > At reboot, the boot failed. ... Now I see that I was wrong here. It works now, I get a working system, but I must wait about a minute till GDM shows up (which is a longer time than usual). During this waiting time, the plymouth theme is not shown and also no text is added on the screen. I should have waited longer ... :) At your request, I filled Bug 8375 for the dracut error (encountered when booting with 3.7.0 rc8 kernel). I plan to wipe my installation and do a clean one, particularly as Beta 1 is at the door. Maybe the problem is fixed also for Kristoffer (the bug reporter), provided that he will do a new install. Can anyone confirm this is still a valid bug for Mageia 2 or Cauldron ? Roelof CC:
(none) =>
r.wobben
Manuel Hiebel
2013-01-21 22:12:01 CET
Status:
NEW =>
UNCONFIRMED no lets close Status:
UNCONFIRMED =>
RESOLVED |