Description of problem: I can't boot any Mageia 5 media on a 2006 iMac (white model with an Intel Core2 Duo processor). Mageia 4 media used to boot without problem. I suppose it has something to do with the new UEFI support, because iMacs use EFI (but not U-EFI). I have had the same problem with other distributions after they had added UEFI support. When I boot, I get a black screen with a few lines text asking me whether I want to choose the boot option 1 or 2. The fact is : I can't choose anything. I tried to use any key of my keyboard, but nothing happened. How reproducible: It happens anytime you try to boot some Mageia media on a white-series iMac. Steps to Reproduce: 1.Try to boot some Mageia media on a white-series iMac. 2.Try again. 3.Get annoyed because you cannot use Mageia on your machine. Reproducible: Steps to Reproduce:
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.
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaudSummary: Impossible to boot Mageia 5 media on an iMac => Impossible to boot Mageia 5 media on an iMac (choice between boot option 1 or 2 with unresponsible keyboard)
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 => RESOLVEDCC: (none) => marja11Resolution: (none) => OLD