| Summary: | Impossible to boot Mageia 5 media on an iMac (choice between boot option 1 or 2 with unresponsible keyboard) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Aurélien Murith <aurelienmurith> |
| Component: | Release (media or process) | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | mageia, marja11, sysadmin-bugs, thierry.vignaud, tmb |
| Version: | 5 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Aurélien Murith
2015-06-27 20:16:31 CEST
I don't think we can do anything about it now. You can install Mageia 4 and upgrade it to Mageia 5 over network - this should still work. CC:
(none) =>
mageia I know that Mageia 5 ISOs will probably not be modified (who knows, there has been a 4.1), but I hope this problem will disappear with the next release⦠It's _very_ hard to test if you don't have the specific hardware. And AFAIK Mac does many things differently from PCs. This doesn't mean that it won't work for sure but I wouldn't put too much hope into it.. If you connect an external usb keyboard, does that one work ? CC:
(none) =>
tmb I do use an external usb keyboard : it is a desktop computer, not a laptop. Sorry, for some reason I read macbook instead of imac Could you try to boot either an i586 iso or the dual one so we can see if it's efi issue or not.
Thierry Vignaud
2015-07-31 09:57:10 CEST
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. Feel free to reopen if needed, while supplying the information that was asked for in comment 6 Status:
NEW =>
RESOLVED |