order of modules is important perhaps.
I have Asus eeePC which has FreeBSD 11-STABLE on it, loading
radeonkms.ko through
/boot/loader.conf works properly only when I have modules written down in the exact following order:
Code:
kern.vty=vt
radeonkmsfw_PALM_pfp_load="YES"
radeonkms_load="YES"
radeonkmsfw_PALM_me_load="YES"
radeonkmsfw_SUMO_rlc_load="YES"
If I changed this order of modules, all I would get would be white screwed-up picture with random noise in it. Ordering the modules as specified, it works just fine. As would work loading
radeonkms.ko through
/etc/rc.conf.
If you are willing to experiment but attempt did not work out - screen becomes un-readable, reboot the machine. Then hit 3 in BSD boot loader, it makes you enter boot prompt, execute
disable-module i915_kms
and then execute
boot
. Thus you can access machine properly again.
Edit: Dell Latitude E6400 (i915kms)
beginning of
/boot/loader.conf
Code:
kern.vty=vt
kern.vt.fb.default_mode="1440x900"
kern.vt.kbd.reboot=1
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"
drm2_load="YES"
iicbus_load="YES"
iicbb_load="YES"
iic_load="YES"
i915kms_load="YES"
It seems to switch over to 1440x900 (laptop's native resolution) just fine, although few seconds go by it being at 640x480.