Wait!/boot/loader.conf :
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"
/etc/sysctl.conf :
#security.bsd.see_other_uids=0
vfs.zfs.vdev.min_auto_ashift=12
security.bsd.unprivileged_chroot=1
vfs.usermount=1
/etc/rc.conf :
hostname="FreeBSD"
keymap="uk.kbd"
ifconfig_em0="DHCP"
ifconfig_em0_ipv6="inet6 accept_rtadv"
sshd_enable="YES"
moused_nondefault_enable="NO"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="AUTO"
zfs_enable="YES"
dbus_enable="YES"
seatd_enable="YES"
sddm_enable="YES"
kld_list="nvidia-modeset"
linux_enable="YES"
oss_enable="YES"
bluetooth_enable="YES"
rc.local is empty.. and it dosent freeze with this method..
Did you ADDED
kld_list="snd_envy24ht" AFTER bluetooth_enable="YES" line in your /etc/rc.conf?!IF SO, NEVER ATTEMPT OR EVEN THINK OF DOING SO!
THE 2ND AND LATER SHALL BE IN FORM LIKE BELOW.
Code:
kld_list="${kld_list} snd_envy24ht"
Otherwise, lines except the very last one are overridden and completely ignored.
You already had
nvidia-modeset loaded via kld_list variable in your /etc/rc.conf. And you also have sddm_enable="YES".If the assumptions above are correct, /boot/modules/nvidia-modeset.ko (and /boot/modules/nvidia.ko that is auto-loaded by /boot/modules/nvidia-modeset.ko) should no longer be loaded by adding
kld_list="snd_envy24ht" line after kld_list="nvidia-modeset" line.This is harmless IF YOU ARE NOT USING GRAPHICAL LOGIN MANAGERS LIKE SDDM and this is why I hate graphical login managers.
Maybe what happened would be falling back to generic driver like x11-drivers/xf86-video-scfb (or if you're booting via legacy BIOS and your vty is running sc [not vt] driver, x11-drivers/xf86-video-vesa), thus, sddm cannot find screen and freezes.