Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When installing under VMWare on MacBook Pro buttons are off screen bottom #24

Closed
zslg01 opened this issue Sep 17, 2018 · 6 comments
Closed

When installing under VMWare on MacBook Pro buttons are off screen bottom #24

zslg01 opened this issue Sep 17, 2018 · 6 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
@josemaX @AndiDog @beanpole135 @RodMyers @zslg01 @powernap
@zslg01
Copy link

@zslg01 zslg01 commented Sep 17, 2018

While installing under VMWare on MacBook Pro - Retina, the buttons you need to click to proceed are off screen at the bottom. Makes it hard to continue.
@RodMyers
Copy link
Contributor

@RodMyers RodMyers commented Jan 22, 2019

have you tried with the RELEASE ISO?

@AndiDog
Copy link

@AndiDog AndiDog commented Jan 23, 2019

Same for me using Trident-18.12-RELEASE-x64-20190115.iso

Screenshot

@powernap
Copy link

@powernap powernap commented Apr 9, 2019

I had this issue as well on VMware Workstation 15, but after talking to Ken, I went into advanced options for the VM and changed from BIOS to UEFI and it fixed the issue.

@RodMyers
Copy link
Contributor

@RodMyers RodMyers commented Jul 18, 2019

Same for me using Trident-18.12-RELEASE-x64-20190115.iso

Screenshot

Can you check that out as well?

@RodMyers RodMyers mentioned this issue Jul 18, 2019
Closed
@josemaX
Copy link

@josemaX josemaX commented Jul 23, 2019

Change to UEFI solved this for me in 19.07-20190710.iso

@beanpole135
Copy link
Member

@beanpole135 beanpole135 commented Nov 8, 2019

Closing out this issue due to the move to Void Linux: Completely different backend/installer.

Just for reference though:
Switching to EFI or UEFI boot within VMWare fixes this issue. It appears to be some kind of mismatch in the VMWare/FreeBSD resolution reporting for legacy-boot.

@beanpole135 beanpole135 closed this Nov 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment