Buongiorno,
spesso nel dual boot tra mac mini e mint 18.2 a 32 bit mi appare una strana schermata che allego e quindi sono costretto a spegnere e riaccendere il mac sperando che non appaia. Che devo fare per toglierla definitivamente?
problemi con dualboot mac mini e mint 18.2
Forum rules
Topics in this forum are automatically closed 6 months after creation.
Topics in this forum are automatically closed 6 months after creation.
-
gianni404
problemi con dualboot mac mini e mint 18.2
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
desperados
- Level 4
- Posts: 280
- Joined: Wed Apr 13, 2016 1:57 am
- Location: Italy
Re: problemi con dualboot mac mini e mint 18.2
non si legge una cippa 
-
gianni404
Re: problemi con dualboot mac mini e mint 18.2
Ok trascrivo il testo :
Per il dual boot uso refit e a volte questo messaggio non appare per cui funziona tutto.Starting legacy loader
Using load options ‘HD’
Error: Not found returned from legacy loader
Error: Not found from LocateDevicePath
Error: Not found from LocateDevicePath
Error: Not found from LocateDevicePath
Error: Not found from LocateDevicePath
Error: Not found from LocateDevicePath
…
Error: Not found from LocateDevicePath
Error: load Error while … out installation volume
The firmware refused to boot from the selected volume. Note that external hard drives are not will_supported by Apple’s firmware for legacy OS booting.
Hit any key to continue (non funziona..)
-
ciuordiss
Re: problemi con dualboot mac mini e mint 18.2
ho trovato questa guida ufficiale di rEFInd Boot Manager
http://www.rodsbooks.com/refind/yosemite.html
dovrebbe esserti utile!
Questi sono gli step:
1)Boot to OS X, using whatever means is available to you. Holding Option (or Alt) while powering up will normally give you Apple's own boot manager, which should enable you to boot to OS X. If your rEFInd installation is currently starting but is not showing an OS X option, skip to step #7; but if rEFInd isn't starting, follow steps #2–7.
2)If you've made changes to /EFI/refind/refind.conf, back it up.
3)Remove the /EFI/refind directory tree; it's useless now, and its presence may cause confusion.
4)Re-install rEFInd, as described in the Installing rEFInd page; but be sure to use the --esp or --ownhfs device-file option. The latter is preferable, but requires either a dedicated partition for rEFInd or an HFS+ data partition that is currently not bootable.
5)Ensure that the partition to which you've installed rEFInd is mounted. The details depend on how you installed it:
If you installed rEFInd to your ESP, typing mkdir /Volumes/esp followed by sudo mount -t msdos /dev/disk0s1 /Volumes/esp will probably work, although in some cases your ESP won't be /dev/disk0s1, so you may need to change this detail.
If you used the --ownhfs device-file installation option, the target partition should already be mounted, normally somewhere under /Volumes. If not, locate it and mount it with Disk Utility or mount.
6)If you backed up your refind.conf file, you can now copy it over your new refind.conf file. You should copy the file to either /Volumes/esp/EFI/refind/ (if you used --esp and mounted the ESP at /Volumes/esp) or to /Volumes/Mountpoint/System/Library/CoreServices/ (if you used a dedicated HFS+ volume; note that Mountpoint will be the name of the volume).
7)Edit your new refind.conf file, which should be located as described in the previous step. In your favorite editor, locate the dont_scan_volumes line, which is commented out with a # symbol at the start of the line by default. Uncomment this line and remove the "Recovery HD" item from the line. Some users report that they need to enter one or two dummy entries, as in dont_scan_volumes foo,bar, to get it to work.
PS: Leggi sempre e comunque la guida ufficiale che è più completa
http://www.rodsbooks.com/refind/yosemite.html
dovrebbe esserti utile!
Questi sono gli step:
1)Boot to OS X, using whatever means is available to you. Holding Option (or Alt) while powering up will normally give you Apple's own boot manager, which should enable you to boot to OS X. If your rEFInd installation is currently starting but is not showing an OS X option, skip to step #7; but if rEFInd isn't starting, follow steps #2–7.
2)If you've made changes to /EFI/refind/refind.conf, back it up.
3)Remove the /EFI/refind directory tree; it's useless now, and its presence may cause confusion.
4)Re-install rEFInd, as described in the Installing rEFInd page; but be sure to use the --esp or --ownhfs device-file option. The latter is preferable, but requires either a dedicated partition for rEFInd or an HFS+ data partition that is currently not bootable.
5)Ensure that the partition to which you've installed rEFInd is mounted. The details depend on how you installed it:
If you installed rEFInd to your ESP, typing mkdir /Volumes/esp followed by sudo mount -t msdos /dev/disk0s1 /Volumes/esp will probably work, although in some cases your ESP won't be /dev/disk0s1, so you may need to change this detail.
If you used the --ownhfs device-file installation option, the target partition should already be mounted, normally somewhere under /Volumes. If not, locate it and mount it with Disk Utility or mount.
6)If you backed up your refind.conf file, you can now copy it over your new refind.conf file. You should copy the file to either /Volumes/esp/EFI/refind/ (if you used --esp and mounted the ESP at /Volumes/esp) or to /Volumes/Mountpoint/System/Library/CoreServices/ (if you used a dedicated HFS+ volume; note that Mountpoint will be the name of the volume).
7)Edit your new refind.conf file, which should be located as described in the previous step. In your favorite editor, locate the dont_scan_volumes line, which is commented out with a # symbol at the start of the line by default. Uncomment this line and remove the "Recovery HD" item from the line. Some users report that they need to enter one or two dummy entries, as in dont_scan_volumes foo,bar, to get it to work.
PS: Leggi sempre e comunque la guida ufficiale che è più completa
Last edited by ciuordiss on Mon Jul 30, 2018 5:45 am, edited 1 time in total.
-
stefanoful
Re: problemi con dualboot mac mini e mint 18.2
Ciao, Ho letto in diversi forum che è un 'problema' legato a Legacy.
Il firmware del Mac non sempre riesce a rilevare la partizione di EFI per l'avvio della seconda unità (hai 2 dischi , corretto?)
Nel caso, potresti utilizzare il boot manager del Mac, come hai fatto per installare Mint da Live, è selezioni il boot di Linux.
Oppure, come riporta il sito di Refit per Legacy Booting: Not Found Error http://refit.sourceforge.net/doc/c4s1_notfound.html
Il firmware del Mac non sempre riesce a rilevare la partizione di EFI per l'avvio della seconda unità (hai 2 dischi , corretto?)
Nel caso, potresti utilizzare il boot manager del Mac, come hai fatto per installare Mint da Live, è selezioni il boot di Linux.
Oppure, come riporta il sito di Refit per Legacy Booting: Not Found Error http://refit.sourceforge.net/doc/c4s1_notfound.html
-
gianni404
Re: problemi con dualboot mac mini e mint 18.2
Grazie delle risposte ma le procedure mi sembrano troppo complicate anche perchè linux l'ho installato sul mac un annetto fa e non ricordo nemmeno come ho fatto quindi continuerò a spegnere e riaccendere il mac quando appare la schermata.