Please add a FreeBSD option as it does work on Apple Silicon

P

ParallelsU803

Bit poster
FreeBSD 13 snapshots and 14 snapshots now work correctly on Parallels on Apple Silicon (tested 3 November 2021). Please add a "FreeBSD" option. Right now I am installing with Other Linux and the generic Other does not allow one to add disks so you can't do an install.
 

Attachments

  • Screen Shot 2021-11-03 at 10.16.57.png
    Screen Shot 2021-11-03 at 10.16.57.png
    65.7 KB · Views: 38
I'd like to see arm64 FreeBSD support here too. I've let my parallels subscription expire because of missing FreeBSD support.
 
Networking 'just works' with latest main (14), using the bulitin virtio_pci driver, but this branch is also currently receiving a lot of changes and is not stable.
 
ParallelsU803 said:
FreeBSD 13 snapshots and 14 snapshots now work correctly on Parallels on Apple Silicon (tested 3 November 2021). Please add a "FreeBSD" option. Right now I am installing with Other Linux and the generic Other does not allow one to add disks so you can't do an install.
Click to expand...
I'm trying to install in a MacBook M1 pro 14" with Monterey, Parallels 17.
FreeBSD-13.0-RELEASE-arm64-aarch64-dvd1.iso file.
If I try with "Other" option, I get no network at all.
If I try with "Linux" option, it doesn't install, instead it runs in a loop with apparently errors about "battery"...

Any help, please?
 
Well, eventually I managed to install FreeBSD 13 with the working network:-)
1. the 13 CURRENT doesn't see the virtual network and no network at all, so I installed 13 STABLE 20220203 (here)
2. the network seen is vtnet0, so in /etc/rc.conf I can see
Code: 
ifconfig_vtnet0="DHCP"
ifconfig_vtnet0_ipv6="inet6 accept_rtadv"
lines.
3. To get it working I had to choose "Other" option, otherwise (with "Linux") the boot runs in a loop.
I'm now installing GUI.

So, actually, please, put an option "FreeBSD" for the M1 ARM Parallels.
Thanks.
 
Installed gnome3.
All went apparently ok, but the vile "something has gone wrong" screen instead of the gdm login window.
I followed this guide, as other times, set the /etc/rc.conf and /etc/fstab files correctly, but...
Any help, please?
 

Attachments

  • Schermata 2022-02-06 alle 21.53.35.jpg
    Schermata 2022-02-06 alle 21.53.35.jpg
    57.8 KB · Views: 7
salvomic said:
Installed gnome3.
All went apparently ok, but the vile "something has gone wrong" screen instead of the gdm login window.
I followed this guide, as other times, set the /etc/rc.conf and /etc/fstab files correctly, but...
Any help, please?
Click to expand...
Hello, did you get a graphics desktop to work on your FreeBSD VM?
 
salvomic said:
I've now switched to FreeBSD 13.1 and gnome works well
Click to expand...
Thanks for your quick reply! I'm more of a KDE person, but will be more than happy to try GNOME with FreeBSD 13.1 on a Parallels VM
However, please pardon my ignorance: what metaport did you use to install gnome? As far as I can tell, there's no gnome3 metaport for FreeBSD 13.1 on aarch64.
Thanks *a lot*
 
Thanks!

Did you have to configure the scfb driver?
/usr/local/etc/X11/xorg.conf.d/driver.scfb.conf configured as:
Code:
Section "Device"
Identifier "Card 0"
Driver "scfb"
EndSection
 
This was necessary in FreeBSD 12 and 13.0, but now I didn't need it.
The only problem was the mouse which was stuck at first, then I set this command
Code: 
# /boot/loader.conf
ums_load="YES"
and now it works.
Only the resolution is impossibile to change in M1 ARM and FreeBSD 13.1: always 1024x768 here...
 
Thanks!
Do you recall which command did you use to install gnome3?
$ pkg install gnome-desktop gdm xorg gnome3
Doesn't work for me because FreeBSD couldn't find gnome3
It would seem that the gnome3 meta package is not available for ARM.
 
no,
I did gnome (not gnome3)
$ pkg install gnome-desktop gdm xorg gnome
Click to expand...
than I edited the file /etc/rc.conf
Code: 
gnome_enable="YES"
moused_enable="YES"
dbus_enable="YES"
hald_enable="YES"
gdm_enable="YES"
and file /etc/fstab
Code: 
proc /proc procfs rw 0 0
Eventually /boot/loader.conf
Code: 
ums_load="YES"
because mouse was stuck.
No other, if I well remember.
 
You must log in or register to reply here.
Back
Top