Jump to content

Search the Community

Showing results for tags 'linux'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 🤴 Donators Room
    • DSDT Patch Requests
  • 🇬🇧 English
    • NEWS Releases & Updates
    • All About Hackintosh - Database
    • macOS Full Installer Database from Apple
    • Olarila Vanilla Images
    • Guides and Tutorials
    • Hackintosh EFI Folder Collection
    • macOS
    • Olarila Apps
    • Hardware
    • Olarila Buyer's Guide
    • DSDT & Patch Requests
    • Olarila Hackintosh Machines
    • Mods & Overclocking
    • Hackintosh Photos, Screenshots and Benchmarks
    • Buying Thoughts, Reviews, and Recommendations
    • Themes & Wallpapers
    • Apple World
    • 👉 Donate
  • 🇧🇷 Português
    • Novos Lançamentos & Atualizações
    • Aplicativos & Apps Úteis
    • Guias & Tutoriais Hackintosh
    • DSDT & Pedidos de Patch
    • macOS BR
    • Hardware BR
    • Discussão geral

Categories

  • Files
  • Bootloader
  • DSDT
  • Utils & Software
  • Clover Folders

Categories

  • Articles

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


CPU


Motherboard


GPU


INTERESTS


OCCUPATION


ICQ


WEBSITE


YAHOO


AOL


LOCATION


FACEBOOK


GOOGLEPLUS


SKYPE


TWITTER


YOUTUBE

Found 2 results

  1. Avoiding EFI Multiboot Problems With GRUB2 and Linux/MacOS/Windows Note that not every combination of installed and otherwise boot capable devices (spinning rust, SSD, NVMe) will be selectively recognized by the BIOS as bootable. BIOS and/or hardware and/or firmware limitations may determine which devices can be used together. Operating system contraints can also be a factor. So do the research first for hardware and software compatibility, and make sure that the BIOS and firmwares are up to date. Create a FAT32 ESP (suggest 400 MB) on your intended boot device, and verify that the BIOS is configured to boot from that device. For those who have multiple SSD devices, each with an installed operating system, including at least one drive with linux installed, and complaining that the linux bootloader, GRUB2, overwrites the ESP, the following information may be of help in resolving your issues. Note that if you are not using GRUB2 as your main bootloader, it does not need to be installed on the ESP. This is a choice for you to make when you are installing linux. If, however, you wish to use GRUB2 as your main bootloader, you can avoid multiboot problems by installing both linux and GRUB2 to the same partition. Once installed, open a linux terminal session and create an efi directory (if one does not already exist): sudo mkdir /boot/efi next, mount your ESP to the efi directory: sudo mount /dev/sda1 /boot/efi (verify your FAT32 ESP partition number with "sudo fdisk -l") next, install GRUB2 boot parameters to the ESP: sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Linux --recheck --no-floppy --debug note that the parameter --bootloader-id=Linux will produce an ESP entry named Linux. You can change the name to suit your taste. There should be an ESP linux file tree entry that includes grub.cfg. Within grub.cfg, xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx is the partition UUID of the linux installation, and in this example, hd0 and gpt2 are the GRUB2 hard drive number and partition number, respectively, pertaining to the linux installation: search.fs_uuid xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx root hd0,gpt2 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg if no installation errors were reported, you can now unmount the ESP: sudo umount -l /dev/sda1 Once you have installed GRUB2 parameters to the ESP using this method, designating GRUB2 as your main bootloader, the GRUB2 boot menu will be located in the linux partition file tree as follows: boot/grub/grub.cfg Note that now, when updating the GRUB2 boot menu for your linux installation (for example, by installing a new kernel or manually updating with update-grub), the updated boot menu is written to the linux partition, and not the ESP. This means that even if you are not using GRUB2 as your main boot loader, linux updates should not overwrite the ESP. Alternatively, if you are using Open Core as your main boot loader you can create a custom boot menu entry to chainload the GRUB2 bootloader: <key>Entries</key> <array> <dict> <key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> <key>Comment</key> <string></string> <key>Enabled</key> <true/> <key>Name</key> <string>GRUB2</string> <key>Path</key> <string>the PciRoot data for your configuration goes here</string> <key>TextMode</key> <false/> </dict> </array> If, however, you do decide to use GRUB2 as your main boot loader, you can add custom entries to boot linux, macOS, and windows following the instructions here: https://www.olarila.com/topic/15309-updated-big-surmonterey-tipsobservations/
  2. Hello all, [If this post is in the wrong place I will gladly remove!] I've decided that it's about the time that I start a new Hackintosh build. My last build, Project Ageha, has served me well and to a certain extent continues to do so, but things have changed quite a bit and it can't keep up with my needs as of late. For my new build, I am shooting for a bit of a different setup compared to a traditional Hackintosh rig. What I am essentially wanting to do is build a Linux machine and will subsequently use virtual machines for macOS and Windows. The idea is simple enough I suppose, but I know alot of things have changed in the Hackintoshing space since my last build, so I am trying to bring myself back up to speed. Red Hat and Arch Linux are my flavors of choice, just fyi. My desire for this new build is that it would be my "work hard, play hard" machine. Part of my job requires that I create very demanding and advanced graphical renders of structures, sometimes quite large in volume. That said, time-frame is a big deal for me. The sooner I can complete one job the better, so I can move on to the next one. Also, on the side, I do some mid to high end hobbyist video editing with Premiere Pro and After Effects. I usually work with 4k60fps footage, and don't really see myself going above that for some time. Again, speedy render times are appreciated for this as well. I almost exclusively use macOS for the things I've listed above. Which would, of course, leave Windows for my "play hard". Gaming and other entertainment will be the primary function of the Windows VM. Now, for my ideal build to become a successful reality, I believe, hinges almost completely on the capabilities of two very important components. The CPU and the GPU. After doing only a surface amount of research, I have found that NVIDIA is effectively no longer a player in the game for macOS. Can't say that I'm surprised, writing was on the wall long ago imo. As further research detailed, however, I found that there is a way to use two different GPUs to accommodate macOS's restrictions. Enabling me to have my cake and eat it too, so to speak. I know that was a rather lengthy discourse to get to my question, but I wanted to lay some groundwork first so you know where my headspace is. So now, here's where I need some advice. Firstly, if I am not mistaken, for a build such as the one I'm shooting for, a beefy CPU is surely not only recommended but probably required. Since I want to run VMs, I was thinking the more cores the better, which caused my mind to automatically go to AMD's Threadripper. I saw that this was an overall not recommended idea, though technically possible. Not sure if there are any Xeons on the level of Threadrippers out there yet, but furthermore I am not sure that going with either of those options is recommended. So given what I've planned to use this new computer for, which CPU would be recommended? GPUs on the hand, I believe I have narrowed it down. For macOS I am between one of the following four cards. Radeon Pro WX 7100 Radeon Pro WX 8200 Radeon Pro WX 9100 Radeon Pro VII All seem to be right up the alley of what I'm looking for to do my work. And, if I'm not mistaken, they are all compatible with macOS. So, happy days there. I'm just not sure which I should pull the trigger on. Biggest areas of interest that they all differ are Compute Units(CUs), VRAM amount, VRAM type/speed, memory bandwidth, and memory interface. Not sure if I should just go balls-to-the-wall and get the Radeon Pro VII, which dominates in all said areas of interest. The word "overkill" comes to mind though. I don't think that there will ever be a time that I will make use of all of the 6 displays it is capable of outputting to though, 3 or 4 max. For Windows. I'm almost certainly going to use an RTX 3090, mostly because it is closely on hand (lucky me). Only reason I wouldn't is because of it causing some issue for the rest of my build. On a final note, I would like to know if it would be possible to run both macOS and Windows at the same time, given the proper hardware was in use. Not sure if I'd ever do this, but I was just curious. Extreme example: gaming while waiting for a render to finish. Again I know this is probably a far shot but just wanted to know. If you read all of this, thanks for bearing with my long-windedness. Hopefully it all made sense. Hopeful to hear your advice! -KingK TL;DR I am wanting to build a Hackintosh running Linux, macOS and Windows. Linux being the base of the machine, macOS and Windows will run in separate virtual machines. My job requires that I create demanding and advanced graphical renders, sometime large scale. I also do mid to high end video editing using Adobe software. I do all of this work in macOS. I use windows to game and for other entertainment. Please help me chose a suitable CPU and GPU for this build. Not sure what CPU to choose. My GPU prospects are: macOS: Radeon Pro WX 7100 Radeon Pro WX 8200 Radeon Pro WX 9100 Radeon Pro VII Windows: RTX 3090 (plan to use it since I have it unless it causes problems with the build) Thanks for your time.
×
  • Create New...