A slow processor is indeed not ideal to uncompress gziped archives, especially when they are large ( 1+ GB).
Is this related to
https://forums.freebsd.org/threads/minimal-xorg-minimal.101242
Isn't nanoBSD an option for your project?
A slow processor is indeed not ideal to uncompress gziped archives, especially when they are large ( 1+ GB).
Isn't nanoBSD an option for your project?
I can't say I agree with that. I have learned from the masters here. I have no more experience than you do.
I never actually got that working....
The intention is to provide a lightweight rescue environment and having as much information on the screen as possible is very useful and I'm very pleased with the result.
Additional information on the use case; I suspect balanga is using Ventoy (mentioned in other forum threads of his), a mfsBSD rescue disk is relative small (+- 100M).
I would grep for the MFSROOT_MAXSIZE. It looks like there is one set to 200m, which overrides the 4096M.
Changing this value helped and I was able build mfsbsd after including the drm-kmod package.
Obviously the kernel and the drm-kmod kernel module are out of sync. From where did you get the kernel.txz and base.txz? If it is from official RELEASE repositories, then they are outdated.
# cd /usr/src
# make -j <nr_of_cpus> buildworld buildkernel
# cd release
# make kernel.txz base.txz
The packages can be found under /usr/obj/usr/src/amd64.amd64/release# cd /root_dir_of/mfsBSD
# make iso CUSTOM=1 BUILDWORLD=1 BUILDKERNEL=1# If you want to build your own kernel and make you own world, you need to set
# -DCUSTOM or CUSTOM=1
#
# To make buildworld use
# -DCUSTOM -DBUILDWORLD or CUSTOM=1 BUILDWORLD=1
#
# To make buildkernel use
# -DCUSTOM -DBUILDKERNEL or CUSTOM=1 BUILDKERNEL=1
#
# For all of this use
# -DCUSTOM -DBUILDWORLD -DBUILDKERNEL or CUSTOM=1 BUILDKERNEL=1 BUILDWORLD=1To use your own but already built world and kernel, `use CUSTOM=1`.
If you want this script to do `make buildworld` and `make buildkernel` for you,
specify the `BUILDWORLD=1` and `BUILDKERNEL=1` variables to `make`, respectively.
## Examples
1. Disk image
```bash
make BASE=/cdrom/usr/freebsd-dist
make BASE=/cdrom/10.2-RELEASE
make CUSTOM=1 BUILDWORLD=1 BUILDKERNEL=1
```
2. Bootable ISO file:
```bash
make iso BASE=/cdrom/usr/freebsd-dist
make iso BASE=/cdrom/10.2-RELEASE
make iso CUSTOM=1 BUILDWORLD=1 BUILDKERNEL=1I like to have as many lines on the screen as possible. Not sure what you mean by using scfb or vesa, What would I change to enable them?
Assuming X11 (see on the handbook: https://docs.freebsd.org/en/books/handbook/x11/#x-graphic-card-drivers), you install x11-drivers/xf86-video-scfb (UEFI) or x11-drivers/xf86-video-vesa (BIOS) and setup your X to use them (search for: "To configure the SCFB driver in a configuration file" on that page).
If you're referring to the kernel.txz and base.txz distribution sets downloaded from here, those are outdated. They were uploaded on November 28, 2025, when 15.0-RELEASE was released. It’s no surprise you're encountering a version mismatch with drm-kmod if you’ve been using those. As of now, 15.0-RELEASE is at patch level 7 .
Where do I get an up-to-date source tree or can I download the correct kernel from somewhere?
Never used Mfsbsd but I maintain a similar system. It allows a PC to boot from USB and forget the initial boot device. My mfsroot contains 95MB compressed and adds some extra executables that are needed in early boot stage before shell login. After that it loads a basic X.org live environment from uzip image files.
I can generate a CLI-only USB image of this if you want. Creating it needs the entire build system that also includes a working live X.org. Creating a concept minimal mfsroot-based system of this for publication would take me a few days.
If anyone fancies updating the documentation for this, the FreeBSD Project's guide to remote installation using mfsBSD still uses sysinstall(8) which was removed in FreeBSD 10.0.
github.com
Is there any way to download these built files from anwhere?
