| Summary: | Possible naming issue and EFI boot failure in MGA5B2 (13/13/2014 release) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Vladimir Zawalinski <vzawalin1> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | stephane_oss |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Bug Depends on: | 14438 | ||
| Bug Blocks: | |||
| Attachments: | screenshot of rdsosreport end | ||
|
Description
Vladimir Zawalinski
2015-01-02 13:46:28 CET
Created attachment 5781 [details]
screenshot of rdsosreport end
This may be a regression from MGA5A2, as I was then able to boot to a running live system on the same real hardware environment used above when reporting bug 14330.
Vladimir Zawalinski
2015-01-05 00:38:56 CET
Depends on:
(none) =>
14438 This bug is identical to bug #14367. A workaround is described on https://bugs.mageia.org/show_bug.cgi?id=13694#c10 Could you try the workaround with VBOX and real Hardware ? If the workaround works for each case this bug could be close as duplicate of #14367 CC:
(none) =>
stephane_oss I will try this with round4 of beta 2. If that works I will close this bug. Thanks! If you test Beta2 it would normally work without modification of boot option. This is a duplicate of 14367 and has been fixed in release MGA5B2R4 Status:
NEW =>
RESOLVED |