@kronikpillow How did you install the Nvidia drivers when you have installed Antergos. I notice you are using an Nvidia GTX650 Ti so the drivers should be 418.43. I have a newer GTX 1060 and have no issues on Cinnamon desktop. I install Antergos and then installed the Nvidia drivers from the terminal. With most Cinnamon desktops it may come up running in software mode until you install the video drivers for your card.
sudo pacman -S nvidia nvidia -utils lib32-nvidia-lbgl nvidia-settings
You would also have to install nvidia-lts if you have the lts kernel installed.
Just a suggestion in case you are doing something different.
See how it works before you make any changes. I run the Cinnamon desktop because i like it the most and i don’t have any issues but i have also run Gnome and Budgie.
@apeallendes Just a short note to say it my BCM4360 also works with broadcom-wl plus kernel headers installed. I’m not sure if or why the kernel headers are required but it works for me on both either the broadcom-wl or the broadcom-wl-dkms with kernel headers installed.
@developers I too would like to hear from the developers about their vision for Antergos. I truly believe it is the best distribution out there. Some others have automated installer scripts but are more for the advanced users in the terminal. Their desktop choices are also not appealing to that crowd either. I have used and or tried most of the top distros out there and then some on the distro watch list. Antergos is by far the best Linux distribution i have used. I just want the developers to know i support what they have so far achieved and appreciate it immensely.
@apeallendes This is a broadcom BCM4312 so i think you need to install broadcom-wl-dkms (Broadcom 802.11 Linux STA wireless driver)
You will also have to install linux headers for the kernel and also headers for the lts kernel if it is installed.
You can install each from the package manager or from the terminal. It will require you to reboot after in order for wireless to show up. I have a newer Broadcom BCM4360 and it works for me.
sudo pacman -S linux-headers linux-lts-headers
sudo pacman -S broadcom-wl-dkms
@kronikpillow I guess i’m kind of the opposite as i am not a gamer. I don’t like an empty desktop as i do want a few icons and i prefer Firefox over all other browsers. I prefer and use the Cinnamon desktop. As far as the installer goes i have not had that many problems with it other than when there is a problem with something. I have fibre optic to my location so it’s not slow for me. I don’t find it buggy… it’s just the nature of the beast. When there is a problem …there is a problem. I can’t control that. If it’s a software issue…packages… repository or server or the installer because they’ve changed something then it is up to the devs to correct that and i have to wait and or rely on someone else who is involved with Antergos to let us know what the issue is and or someone in the community who has figured out a work around or i figure it out myself if i’m capable by reading and doing. If i have to wipe it out and start over that’s not a problem for me. It doesn’t take that long with this installer…for me if i mess it up by trying something. Everyone’s hardware is different and they may not have the best internet either. It also makes a difference on the brand of USB drives and the software used to burn the ISO and that is where some of the problems come from trying to install. It all has to do with the hardware and or the software. As far as the choices go on the install i don’t have many issues with it. Anything i want to install is available in the update manager after and the installer doesn’t really install much other than what is pre-packaged in the particular desktop you choose. If there is something i don’t use or don’t want i just uninstall it if that’s possible. I don’t really see an issue with it. I like Antergos a lot because i believe in the rolling release model and i like it because it’s Arch based. It just works for me.
I prefer virtual box over vmware and i also find it works very well for what it is. Having said that i would rather have the distribution installed on my computer rather than running virtual. I can install and set up Antergos and add software and tweak in 10 minutes or more. I have tried most other ditros and Antergos is awesome. Every time i have tried a different distro i have always came back to Antergos. It is my favorite. I like the installer. I like the package manager. It just works for me.
@kronikpillow here is the answer you are seeking although this info is a bit dated.
Getting EFI to Boot an OS install CD
64 bit running an a VM with EFI enabled:
- System -> Motherboard -> Extended Features: Enable EFI
- Boot HDD must be attached to SATA controller! IDE, SCSI or SAS will not work (bug report: Ticket #14142)
EFI Boot Screen:
When the UEFI boot screen appears, it should show blkX: and fsX: devices. fsX: are file systems accessible by the boot loader. If the EFI boot partition does not appear as fsX:, the boot manager will not be able to boot. This will happen if the EFI partition is on a disk attached to an IDE, SCSI or SAS controller (see above).
Boot from the EFI boot shell (for Ubuntu system, others may be different):
Once you know what to boot (in my case: efi\ubuntu\grubx64.efi), put this line into a new file startup.nsh in the root directory of the EFI file system. Then, the EFI boot loader will boot it automatically after 5s.
Not sure if this will help you or not. But that’s how EFI works. It looks to the EFI partition to get the path to the boot EFI file for whatever you are booting.
This information comes from a virtual box forum.
@manuel I also found this online.
VMware Player and Workstation
The virtual machine products offered by VMware support UEFI, but BIOS firmware is enabled by default. Furthermore, the VMware products do not provide an option in the GUI for enabling UEFI.
UEFI support must be enabled by manually editing the .VMX file or by using a third-party tool like VM Tweaker.
To manually edit the .VMX file, simply open with a text editor and add the following line and then save:
firmware = “efi”
That’s it — now that particular VM should run with UEFI.
VirtualBox by default uses the BIOS firmware for virtual machines. It supports EFI too, but unfortunately does not support booting UEFI-based system volumes, which includes Windows 8 in UEFI mode. However, if you’d still like to test or use EFI with other operating systems, enabling EFI support is easy. Open the VM settings, select System, and on the Motherboard tab, select Enable EFI (special OSes only).
This is dated late 2014 so i’m not sure if much has changed or not?